Navy ERP Program Development

(1)

D

2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If

applicable)

51 02-Jul-2012 1300231777,1300273705,1300273707,1300273 N/A

6. ISSUED BY CODE _N00039 7. ADMINISTERED BY (If other than Item 6) CODE _S2404A

SPAWAR HQ DCMA Manassas

4301 Pacific Highway 10500 BATTLEVIEW PARKWAY, SUITE 200

San Diego CA 92110 MANASSAS VA 20109-2342

[email protected] 703-946-0123

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State, and Zip Code) 9A. AMENDMENT OF SOLICITATION NO.

General Dynamics Information Technology, Inc. 3211 Jermantown Road

Fairfax VA 22030-2844 9B. DATED (SEE ITEM 11)

[X]

10A. MODIFICATION OF CONTRACT/ORDER NO.

N00178-04-D-4012-EH01

10B. DATED (SEE ITEM 13)

21-Jun-2006

CAGE

CODE 07MU1

FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

[ ]

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

[ ]

is extended,

[ ]

is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing Items 8 and 15, and returning one (1) copy of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

SEE SECTION G

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS, IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(*) A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

[ ]

[ ] _{B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office,}

appropriation date, etc.)SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

[ ] C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF: [X] D. OTHER (Specify type of modification and authority)

'Allotment of Funds' clause

E. IMPORTANT: Contractor [ X ] is not, [ ] is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

SEE PAGE 2

15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

15B. CONTRACTOR/OFFEROR 15C. DATE SIGNED

Dave Bodner, Contracting Officer

16B. UNITED STATES OF AMERICA 16C. DATE SIGNE

(Signature of person authorized to sign)

NSN 7540-01-152-8070

PREVIOUS EDITION UNUSABLE

BY

30-105

/s/Dave Bodner

(Signature of Contracting Officer)

02-Jul-2012

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

(2)

$ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $

GENERAL INFORMATION

The purpose of this modification is to:

Obligate FY12 O&MN funding in the amount of $88,142 for ODCs on SLIN 610001 – ACRN A1 Obligate Award Fee Earned in the amount of $ for the final award fee period.

Affected SLINs: 4005AA, 4005EA, 4005FA, 4005GA, 4005HA, 4005JA

SECTION B – SUPPLIES OR S ERVICES AND PRICES/COSTS

Funding is obligated as follows:

Funding Funding Funding Funding A d d e d A d d e d A d d e d

A d d e d FY12FY12FY12FY12 SLIN

SLIN SLIN

SLIN ACRNACRNACRNACRN CostCostCostCost Fixed FeeFixed FeeFixed FeeFixed Fee TotalTotalTotalTotal FROM FROM FROM FROM 410001 410001 410001 410001 A1A1A1A1 $212,138 610001 610001 610001 610001 A1A1A1A1 $255,254 $0 $255,254 $467,392 $467,392 $467,392$467,392 BY BY BYBY 410001 410001 410001 410001 A1A1A1A1 $0 $0 $0 610001 610001 610001 610001 A1A1A1A1 $88,142 $0 $88,142 $88,142 $88,142 $88,142 $88,142 $0$0$0$0 $88,142$88,142$88,142$88,142 T O T O T O T O 410001 410001 410001 410001 A1A1A1A1 $212,138 610001 610001 610001 610001 A1A1A1A1 $343,396 $0 $343,396 $542,123 $542,123 $542,123 $542,123 $13,411$13,411$13,411$13,411 $555,534$555,534$555,534$555,534 Funding Funding Funding Funding A d d e d A d d e d A d d e d

A d d e d FY11FY11FY11FY11 SLIN

SLIN SLIN

SLIN ACRNACRNACRNACRN CostCostCostCost B a s e F e eB a s e F e eB a s e F e eB a s e F e e

Cost +Cost +Cost +Cost + B a s e F e e B a s e F e e B a s e F e e B a s e F e e Award Award Award Award Fee Pool*Fee Pool*Fee Pool*Fee Pool*

Award Fee Award Fee Award Fee Award Fee Earned** Earned**

Earned**Earned** Total***Total***Total***Total*** FROM FROM FROM FROM 4005AA 4005AA 4005AA 4005AA BHBHBHBH $4,177,638 $ $ $4,382,075 4005EA 4005EA 4005EA 4005EA BLBLBLBL $34,743 $ $ $36,221 4005FA 4005FA 4005FA 4005FA BMBMBMBM $33,620 $ $0 $33,620 4005GA 4005GA 4005GA 4005GA BNBNBNBN $80,070 $ $0 $80,070 4005HA 4005HA 4005HA 4005HA AOAOAOAO $15,991 $ $0 $15,991 $0 $311,157 4005AA 4005AA 4005AA 4005AA BHBHBHBH $0 $0 $0 ($ 4005EA 4005EA 4005EA 4005EA BLBLBLBL $0 $0 $0 ($ 4005FA 4005FA 4005FA 4005FA BMBMBMBM $0 $0 $0 ($ 4005GA 4005GA 4005GA 4005GA BNBNBNBN $0 $0 $0 ($ 4005HA 4005HA 4005HA 4005HA AOAOAOAO $0 $0 $0 ($ 4005JA 4005JA 4005JA 4005JA BPBPBPBP $311,157

BY

4005JA 4005JA 4005JA 4005JA BPBPBPBP $0 $0 $0 ($ TOTAL TOTAL TOTAL TOTAL $0$0$0$0 $0$0$0$0 $0$0$0$0 ($($($($ $$$$ $$$$ T O T O T O T O 4005AA 4005AA 4005AA 4005AA BHBHBHBH $4,177,638 $0 4005EA 4005EA 4005EA 4005EA BLBLBLBL $34,743 $0 4005FA 4005FA 4005FA 4005FA BMBMBMBM $33,620 $0 4005GA 4005GA 4005GA 4005GA BNBNBNBN $ $ $80,070 $0

(3)

4005HA 4005HA 4005HA 4005HA AOAOAOAO $15,991 $0 $ $ 4005JA 4005JA 4005JA 4005JA BPBPBPBP $311,157 $0 $ $ Funding Funding Funding Funding Increase: Increase: Increase: Increase: From $74,815,217.62 By $123,646.00 To $74,938,863.62

The Line of Accounting information is hereby changed as follows:

The total amount of funds obligated to the task is hereby increased from $74,815,217.62 by $123,646.00 to

$74,938,863.62.

CLIN/SLIN

Type Of Fund

From ($)

By ($)

To ($)

4005AA

O&MN,N

4,382,075.00

12,193.00

4,394,268.00

4005EA

O&MN,N

36,221.00

325.00 36,546.00

4005FA

WCF

33,620.00

1,752.00

35,372.00

4005GA

WCF

80,070.00

4,176.00

84,246.00

4005HA

WCF

15,991.00

833.00 16,824.00

4005JA

O&MN,N

311,157.00

16,225.00

327,382.00

610001

O&MN,N

255,254.00

88,142.00

343,396.00

(4)

--- --- --- ---- --- --- --- ---

SECTION B SUPPLIES OR SERVICES AND PRICES

CLIN - SUPPLIES OR SERVICES For Cost Type Items:

Item Supplies/Services Qty Unit Est.Cost Base Fee Award Fee CPAF

1000 Base Year FY 06 $

1000AA System engineer 1.0 LO $283,562.00

support and IT Architecture, including help desk architect in accordance with paragraph 2.2.2 and section 2.2.8.1 of the Statement of Objectives (SOO). (O&MN,N)

1000AB Systems Engineer 1.0 LO $419,093.00

support and IT architecture, including help desk architect in acordance with paragraph 2.2.2 and section 2.2.8.1 of the Statement of Objectives (O&MN,N)

1000BA QA Test and IT 1.0 LO $358,624.00

Development Support in accordance with paragraphs 2.2.3 and 2.2.4, and section 2.2.8.2 of the Statement of Objectives (SOO). (RDT&E) 1000BB QA Test and IT 1.0 LO $39,105.00 Development Support in accordance with paragraphs 2.2.3 and 2.2.4, and section 2.2.8.2 of the Statement of Objectives (RDT&E)

1000CA SASG, FFC, and 1.0 LO $56,447.00

Release Management Support in accordance with paragrah 2.2.1, 2.2.5, and 2.2.7 of the Statement of Objectives (SOO). (O&MN,N) 1000CB SASG, FCC and 1.0 LO $127,886.00 Release Management

(5)

Support in accordance with paragraphs 2.2.1, 2.2.5 and 2.2.7 of the Statement of Objectives (O&MN,N) 1000EA IV&V in accordance with paragraph 2.2.6 of the Statement of Objectives (SOO) (OMN) (O&MN,N) 1001 FY 07 Options

1001AA System engineer support and IT Architecture, including help desk architect in accordance with paragraph 2.2.2 and section 2.2.8.1 of the Statement of Objectives (SOO). (O&MN,N) 1001BA IT Development in Support in accordance with paragraphs 2.2.3, 2.2.4, and 2.2.8.2 of the Statement of Objectives (SOO) (RDT&E) (RDT&E) 1001BB QA Test and IT Development in Support in accordance with paragraphs 2.2.3, 2.2.4, and 2.2.8.2 of the Statement of Objectives (SOO) (RDT&E) (RDT&E) 1001BC QA Test Support in accordance with paragraphs 2.2.3, 2.2.4, and 2.2.8.2 of the Statement of Objectives (SOO) (RDT&E) (RDT&E) 1001CA SASG, FFC, and

Release Management Support in accordance with paragrah 2.2.1, 2.2.5, and 2.2.7 of the Statement of Objectives (SOO). (O&MN,N) 1001DA Project Management 1.0 LO $90,707.00 $ 1.0 LO $2,966,350.00 1.0 LO $1,672,107.00 1.0 LO $314,195.00 1.0 LO $1,753,310.00 1.0 LO $1,052,893.00 1.0 LO $ $1,572,948.00

(6)

Support in accordance with paragraph 2.1 of the Statement of Objectives (SOO). (O&MN,N) 1001EA IV&V in accordance with paragraph 2.2.6 of the Statement of Objectives (SOO). (O&MN,N) 1001FA Facilities Management Support (O&MN,N) 1001GA Government Oversight Support Labor (OMN) (O&MN,N) 1001HA Facilities-use Support Labor (OMN) (O&MN,N) 1001JA Non-Test/QA Support Labor (para 2.2.3, 2.2.4, and 2.2.8.2) (RDTEN) (RDT&E) 1001KA Test-Quality Assurance Travel (RDTEN) (RDT&E) 1002 FY 08 Options 1002AA Government Oversight Support Labor (OMN) (See Note A) (O&MN,N) 1002BA Facilities-use

Support Labor (OMN) (See Note A) (O&MN,N) 1002CA Non-Test/QA Suppo0rt Labor (para 2.2.3, 2.2.4, and 2.2.8.2) (RDTEN)(See Note A) (RDT&E) 1002DA Test-Quality Assurance Labor (RDTEN) (See Note A) (RDT&E) 1002EA Government

Oversight Support Labor (See Note A) (O&MN,N) 1002FA Facilities Use

Support Labor (See Note A) (O&MN,N) 1002GA Non-Test QA 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 LO $930,094.00 LO LO LO LO $ $ $ $69,406.00 $762,591.00 $48,560.00 $630,613.00 LO LO LO $ $ $ $ $587,433.00 $2,027,385.00 $48,560.00 $992,147.00 LO LO LO LO $ $ $ $ $655,406.00 $6,355,855.00 $493,801.00 $884,233.00

(7)

Support Labor (para 2.2.3, 2.2.4, and 2.2.8.2)(See Note A) (RDT&E) 1002HA Test Quality

Assurance Labor (See Note A) (RDT&E) 1003 FY 09 Options 1003AA Government Oversight Support Labor (OMN)(See Note A) (O&MN,N) 1003BA Facilities-use Support Labor (OMN) (See Note A) (O&MN,N) 1003CA Non-Test/QA Support Labor (para 2.2.3, 2.2.4, and 2.2.8.2) (RDTEN)(See Note A) (RDT&E) 1003DA Test-Quality Assurance Labor (RDTEN) (See Note A) (RDT&E)

1004 FY 10 Options

1004AA Government Oversight Support Labor (OMN) (See Note A) (O&MN,N) 1004BA Facilities-use

Support Labor (OMN) (See Note A) (O&MN,N) 1004CA Non-Test/QA Support Labor (para 2.2.3, 2.2.4, and 2.2.8.2) (RDTEN) (See Note A) (RDT&E) 1004CB Award Fee for

1004CA (RDT&E) 1004DA Test-Quality

Assurance Labor (RDTEN) (See Note A) (RDT&E) 1004DB Award Fee for

1004DA (RDT&E) 1004EA SLIN 1004EA for

FY10 OMN ECP Funding (O&MN,N) 1004FA RDT&E (DW)Labor

Funding (RDT&E) 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 LO $1,055,882.00 LO $ $ $9,975,166.16 LO $780,303.00 LO $ $2,214,972.00 LO $ $2,843,343.84 LO $ $ $12,579,044.00 LO $ $948,330.00 LO $508,716.00 LO LO $ $28,623.00 $618,072.00 LO LO LO $ $35,481.00 $85,000.00 $123,869.00

(8)

--- --- --- ---- ---

1004GA SLIN 1004GA for 1.0 LO $10,957.00

FY10 NAWC AD-TSD-ORL Labor Funding (WCF)

1004HA SLIN 1004HA for 1.0 LO $ $276,944.00

FY10 NAVSUP ECP Labor Funding. (OTHER)

1004JA SLIN 1004JA for 1.0 LO $172,786.00

Planning and Strategy for Financial Extension. (O&MN,N)

For ODC Items:

Item Supplies/Services Qty Unit Est. Cost

3000 Other Direct $13,950,088.00 Costs FY06 through FY10 3000BB Travel in 1.0 LO $9,327.00 accordance with the Statment of Objectives (SOO). (O&MN,R) 3000BC Travel in 1.0 LO $82,463.00 accordance with the Statment of Objectives (SOO). (RDT&E)

3000CA Other ODC charges 1.0 LO $32,004.00

not included in the Facilities charges, and including office supplies and non-capitalized equipment. (O&MN,N) 3000CB ODCs 1.0 LO $4,002.00 (non-facilities use) (OMN) (O&MN,N) 3000DB Travel in 1.0 LO $72,662.00 accordance with Statement of Objectives (O&MN,R) 3000DC Travel in 1.0 LO $426,621.00 accordance with Statement of Objectives (RDT&E) 3000DD Travel in 1.0 LO $117,332.00 accordance with Statement of Objectives (RDT&E) 3000DE Travel in 1.0 LO $306,693.00 accordance w/ SoO

(9)

(OMN) (O&MN,N) 3000DF Government Oversight Support OMN Travel (O&MN,N) 3000DG Non-Test/QA Support Travel (para 2.2.3, 2.2.4, and 2.2.8.2) (RDTEN) (RDT&E) 3000DH Test-Quality Assurance Travel (RDTEN) (RDT&E) 3000EA ODCs (non-facilities-u se) (OMN)(See Note A) (O&MN,N) 3000FA Government Oversight Support OMN Travel (See Note A) (O&MN,N) 3000FB Non-test/QA Support Travel (para 2.2.3, 2.2.4 and 2.2.8.2) (RDTEN) (See Note A) (RDT&E) 3000FC Test-Quality Assurance Travel (RDTEN) (See Note A) (RDT&E) 3000FD Government

Oversight Support Travel (See Note A) (O&MN,N) 3000FE Non-test QA Support Travel (See Note A) (RDT&E) 3000FF Test Quality Assurance Travel (See Note A) (RDT&E) 3000FG ODCs, Non-facilities Use (See Note A) (O&MN,N)

3000FH Facilities use Support ODCs (See Note A) (O&MN,N) 3000GA ODCs (non-facilities-u se) (OMN)(See Note A) (O&MN,N) 3000HA Government Oversight Support OMN Travel (See Note A) (O&MN,N) 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 LO LO LO LO LO LO LO LO LO LO LO LO LO LO $12,616.00 $49,041.00 $84,759.00 $4,003.00 $243,294.00 $83,705.00 $110,594.00 $263,862.00 $97,347.00 $83,682.00 $40,018.00 $2,455,105.00 $10,000.00 $332,680.00

(10)

3000HB Non-test/QA Support Travel (para 2.2.3, 2.2.4, and 2.2.8.2) (RDTEN)(See Note A) (RDT&E) 1.0 LO $157,000.00 3000HC Test-Quality Assurance Travel (RDTEN) (See Note A) (RDT&E)

1.0 LO $160,500.00

3000LA Other Direct Costs for Facilities IAW Setion 8.0 of the SOO. (TBD) 1.0 LO $534,197.00 3000LB Facilities-use Support ODCs (OMN) (O&MN,N) 1.0 LO $154,590.00 3000MA Facilities-use Support ODCs (OMN) (See Note A) (O&MN,N) 1.0 LO $89,503.00 3000MB Facilities-Use Support ODCs (OMN)(See Note A) (O&MN,N) 1.0 LO $60,000.00 3000NA Facilities-use Support ODCs (OMN) (See Note A) (O&MN,N)

1.0 LO $3,537,600.00

3000PA ODCs

(non-facilities-u se) (OMN) (See Note A) (O&MN,N)

1.0 LO $30,889.00

3000QA Government Oversight Support OMN Travel (See Note A) (O&MN,N) 1.0 LO $306,290.00 3000QB Non-test/QA Support Travel (para 2.2.3, 2.2.4, and 2.2.8.2) (RDTEN)(See Note A) (RDT&E) 1.0 LO $86,532.00 3000QC Test-Quality Assurance Travel (RDTEN)(See Note A) (RDT&E) 1.0 LO $69,445.00 3000QD RDT&E (DW) Funding (RDT&E) 1.0 LO $5,000.00 3000RA Facilities-use Support ODCs (OMN)(See Note A) (O&MN,N) 1.0 LO $3,836,732.00

For Cost Type Items:

(11)

--- --- --- ---- --- --- --- --- --- --- --- ---- --- --- --- --- ---- --- 4005

4005AA Originally CLIN 1.0 LO $

1004AA in FY10. For 3 month extension starting 1 October. (O&MN,N)

4005BA Originally CLIN 1.0 LO $

1004BA in FY10. For 3 month extension starting 1 October. (O&MN,N)

4005CA Originally CLIN 1.0 LO $0.00

1004CA in FY10. For 3 month extension starting 1 October. (RDT&E)

4005DA FY11 NAVSUP WCF 1.0 LO $

(WCF)

4005EA OM&N Upgrade 1.0 LO $

(CHARM efforts) (O&MN,N)

4005FA FY11 NAVSUP ECP 1.0 LO $

(WCF)

4005GA NAVSUP Deployment 1.0 LH $

(WCF)

4005HA NAVSEA ECP (WCF) 1.0 LO $

4005JA Government 1.0 LO $

Oversight Support Labor (OMN) (O&MN,N)

4100 Facilities 1.0 LO $

support (O&MN,N) 410001 Facilities

Services (O&MN,N)

For ODC Items:

6005 $682,704.00

6005AA Originally CLIN 1.0 LO $158,329.00

3000QA in FY10. For 3 month extension starting 1 October. (O&MN,N)

6005BA Originally CLIN 1.0 LO $278,379.00

3000RA in FY10. For 3 month extension starting 1 $ $7,228,646.00 $127,000.00 $0.00 $0.00 $0.00 $1,923,411.00 $36,559.00 $35,376.00 $84,254.00 $16,826.00 $362,415.00 Fixed Fee CPFF --- --- $212,138.00

(12)

October. (O&MN,N)

6005CA Originally CLIN 1.0 LO $0.00

3000QB in FY10. For 3 month extension starting 1 October. (RDT&E)

6005DA FY11 NAVSUP WCF 1.0 LO $73,496.00

(WCF)

6005FA FY11 NAVSUP ECP 1.0 LO $1,000.00

(WCF)

6005JA ODC in support of 1.0 LO $4,500.00

SLIN 4005JA (O&MN,N)

6005KA ODC in support of 1.0 LO $167,000.00

Facilities (O&MN,N) 6100 ODCs in support 1.0 LO $343,397.00 of CLIN 4100 (O&MN,N) 610001 Facilities Services (O&MN,N)

NOTE A - Option item to which the option clause in SECTION I-2 applies and which is to be supplied only if and to the extent said option is exercised. CONTRACT TYPE SUMMARY FOR PAYMENT OFFICE (COST TYPE) (NAVSEA) (FEB 1997)

● Item 1000 is cost type

● Item 3000 is cost only

*[Delete the following section if the procurement contains no SLIN of type 1, 4, or 7.]* PAYMENTS OF FEE(S) (LEVEL OF EFFORT) (NAVSEA) (MAY 1993)

(a) For purposes of this delivery order, "fee" means "fixed fee" in cost-plus-fixed-fee level of effort type delivery orders.

(b) The Government shall make payments to the Contractor, subject to and in accordance with the clause in this contract entitled "FIXED FEE" (FAR 52.216-8) or "INCENTIVE FEE", (FAR 52.216-10), as applicable. Such payments shall be equal to TBD% of the allowable cost of each invoice submitted by and payable to the Contractor pursuant to the clause of this contract entitled "ALLOWABLE COST AND PAYMENT" (FAR 52.216-7), subject to the withholding terms and conditions of the "FIXED FEE" or "INCENTIVE FEE" clause, as applicable (percentage of fee is based on fee dollars divided by estimated cost dollars, including facilities capital cost of money). Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract.

(c) The fee(s) specified in SECTION B, and payment thereof, is subject to adjustment pursuant to paragraph (g) of the special contract requirement entitled "LEVEL OF EFFORT." If the fee(s) is reduced and the reduced fee(s) is less than the sum of all fee payments made to the Contractor under this contract, the Contractor shall repay the excess amount to the Government. If the final adjusted fee exceeds all fee payments made to the contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this contract at the time of the discontinuance of work.

(d) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) in accordance with the "LEVEL OF EFFORT" special contract requirement, or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.

(13)

SECTION C DESCRIPTIONS AND SPECIFICATIONS

Statement of Objectives

Navy Enterprise Resource Planning (ERP)

Laboratory Professional Services

1.0 PURPOSE

Work to be performed under this contract will support the Navy Enterprise Resource Planning (ERP) Program Management Office Laboratory in Annapolis, Maryland. The contractor’s efforts will focus on providing technical program support for realization and deployment of a future Navy ERP solution.

1.1 BACKGROUND

In response to becoming more efficient in the light of downsizing and decreasing budgets, the Navy established the Revolution in Business Affairs Commercial Business Practices Executive Steering Group (ESG) in 1998.

The ESG assessed the performance and value of Enterprise Resource Planning (ERP) systems as implemented in the commercial environment. ERP is about re-engineering our business processes using the latest commercial technology. It enables end-to-end product management and provides for major improvements in supply chain management. ERP produces financial information that is tied directly to the work, resulting in more complete and accurate information. The ESG concluded that the department should pursue ERP. Based on this conclusion, they directed the formation of four limited production systems to address functionality in Program Management, Working Capitol Fund Management, Regional Maintenance, and Aviation Supply and Maintenance. Each pilot was directed to use a commercial implementation approach versus the traditional defense software development process. All four ERP limited production systems independently selected the ERP software product SAP as the basis for their system solution. The goals of these limited production systems were to provide improved decision information, improve efficiency and effectiveness though re-engineered business processes and improve cost management.

These limited production systems are enabling financial, maintenance, supply, human resources and program management processes in an integrated environment, and will eliminate dozens of incompatible computer databases. As individual ERP limited production systems, they have proven that the embedded commercial best processes are a catalyst for business process reengineering; that these processes can be adopted for Navy operations; that the COTS software can successfully run Navy business; and that the return on investment can be individually achieved.

Given the demonstrated successes of the four limited production systems, on 2 August 2002 ASN(RD&A) directed the convergence of the limited production systems. This was based on the need to develop a true end-to end capability. The limited production systems, which are already showing benefits, have even greater potential when integrated across the aviation, maritime/C4I, and supply product lines. The potential for supply chain, acquisition, and information technology efficiencies is higher when the limited production systems are converged in a single integrated solution. Navy ERP convergence will reduce overall cost and provide improved benefits, improve responsiveness to the Fleet, improve architectural alignment and interoperability within the Navy, facilitate end-to-end product management and force Navy-wide standard processes. Navy ERP will improve current and future readiness, provide Navy leadership more accurate and timely information for decision making, establish common business practices, reduce legacy applications and systems redundancy, which will

substantially reduce overall operating cost.

To accomplish this, the Navy immediately commenced addressing DoD architectures and began coordinating with OSD(C) and DUSD(L) on architectural alignment. The Navy ERP architecture is in alignment with the Future Logistics Enterprise (FLE) and is developing a process to ensure alignment with the OSD(C) Financial

(14)

Management Enterprise Architecture (FMEA).

On 17 December 2002, SECNAV and CNO declared support for the convergence effort and on 30 January 2003, ASN(RD&A) directed the standup of a Navy ERP Program Management Office. In accordance with this direction, new pilot functionality work has stopped.

The current convergence plan is to configure a single solution that encompasses all the functionality of the original limited production systems. In parallel with this, the required functionality not currently addressed by the limited production systems will begin to be assessed.

1.2 SCOPE

The scope of this effort is to provide highly technical professional support services to ensure the successful design, development, test and deployment of Navy ERP solutions. Services required are focused on supporting the Government in its oversight of the systems integrator and other contractors involved in building, delivering and sustaining software releases. Services to be provided include:

· participating on integrated product teams within the program, Navy and DoD;

· supporting the program’s Strategies, Architecture and Standards Group and System Engineer;

· delivering general program and administrative support to the Annapolis laboratory;

· structuring, operating and analyzing the program’s earned value management system and integrated master schedule;

· supporting Program interface with the Fleet, other Navy elements, OSD, OMB and the commercial sector;

· performing analyses, evaluating and analyzing ERP solution products, and supporting independent verification and validation related tasks;

· researching and recommending tools to improve program management and technical performance;

· reviewing and analyzing highly technical program deliverables and recommending conditions, if any, of Government acceptance;

· and, performing modifications to technical data.

1.3 LOCATION

The work accomplished under this contract will primarily take place at Government-provided facilities in

Annapolis, Maryland. In the event that the facilities option is exercised, work will then be performed at contractor proposed sites as stated in offeror’s proposals. Contractor proposed sites shall be in accordance with Section 8.0 of the SOO.

2.0 SPECIFIC TASKS

2.1 LABORATORY PROJECT MANAGEMENT SUPPORT

The contractor shall provide management and technical expertise to the Navy ERP Technical Director, Team Leads and staff members to ensure that the program meets its goals and objectives and that all deliverables are of the highest professional quality and are delivered in accordance with agreed upon dates/milestones.

(15)

2.1.1.1 Activity: Program Support

Performance Objectives

1. The contractor shall facilitate Integrated Product Team (IPT) meetings, special advisory boards, off-site meetings, working groups, audit teams, etc.

2. The contractor shall analyze, evaluate and prepare program briefs, reports and correspondence.

3. The contractor shall review, assess and monitor integrated program plan and production reports and recommend resolution of execution and production problems.

4. The contractor shall develop and maintain performance measurements/metrics for the laboratory efforts.

Performance Deliverable

1. Monthly Status Report (A021): The Monthly Status Report must address support of the Performance

Objectives described above, particularly in relation to the program office Integrated Master Schedule. The report should include quantitative and qualitative (See Performance Standard) measures of performance.

Performance Standard

1. Timeliness. Contractor shall deliver products within deadlines identified by the task manager. No more than 2% of all reports and products may be delivered to the appropriate Government contact later than the specified time period.

2. Accuracy. Products shall be factually accurate, complete, and in accordance with Navy standards and policies, as well as other standards and deliverables as mutually agreed to by both the Government and contractor. No more than 2% of products will require rework to correct inaccuracies.

3. Quality. Products shall be free of spelling and grammatical errors, formatted appropriately, and fully coordinated with any stakeholders. No more than 2% of products will have quality deficiencies.

4. Compatibility. All products must be fully compatible with the Navy Marine Corps Intranet (NMCI) format for Microsoft Word, Excel, PowerPoint, Access, Program Manager and other application programs used by the Program. No product will be incompatible with the program’s standard applications.

Monitoring Method

1. Government review and assessment of deliverables and products.

2. Monthly reports.

2.1.2 Program Planning and Scheduling

2.1.2.1 Activity: Integrated Project Plan – Master Schedule Support (Lab)

1. The contractor shall update and maintain the Navy ERP Program’s Integrated Master Schedule (IMS).

2. The contractor shall incorporate the System Integrator and other contract support tasks and effort into the Government’s integrated master schedule.

(16)

Government adherence to the IMS. The contractor shall identify the program’s critical path and major risks to program performance, cost and schedule. Recommendations will be made to resolve any issues.

Monitoring Methods

2. Monthly reports.

2.1.3 Risk Assessment

2.1.3.1 Activity: Risk Studies and Monitoring

1. The contractor shall review labor usage/availability and schedule to evaluate/analyze potential schedule risk and assess the impacts.

2. The contractor shall monitor defined risks for major deviations that occur and make recommendations for mitigation.

3. The contractor shall perform tradeoff studies and conduct risk assessments.

4. The contractor shall prepare risk assessment analyses, studies, recommendations, documents, and updates to documents.

(17)

Monitoring Method

2. Monthly reports.

2.1.4.1 Administrative Support

2.1.4 Activity: Administrative Support

1. The contractor shall be proficient in Microsoft Office including MS Word, MS PowerPoint, MS Excel, MS Project, and MS Outlook (Adobe Acrobat Exchange).

2. The contractor shall maintain a consumption log of office supplies and materials.

3. The contractor shall develop and maintain a schedule of laboratory technical, programmatic and administrative events and meetings. These schedules shall be updated as requested or, at a minimum, weekly.

4. The contractor shall maintain and track action items.

5. The contractor shall provide courier(s) up to a secret level, for the delivery of classified and unclassified material.

6. The contractor shall provide orientation to laboratory staff members on the office tools.

7. The contractor shall prepare travel arrangements and travel documents for government laboratory personnel.

8. The contractor shall manage the development, coordination and distribution of program office master calendars. Distribute weekly.

9. The contractor shall perform official mail distribution. These services include developing and implementing policy and procedures in coordination with the United States Postal Service (USPS) and special courier agencies such as Federal Express, Airborne, and United Parcel Service. The contractor shall establish procedures for security of mail pick-up and delivery, plan for continuity of mail and distribution systems to include maintaining USPS postage meter and official mail and distribution boxes.

(18)

10. The contractor shall serve as the approving authority for new and revised local hardcopy and electronic forms, and maintain a master file of current forms and a method for keeping forms current. The contractor shall develop a method for keeping local publications current.

11. The contractor shall ensure all electronic forms and publications are available on a designated network area.

12. The contractor shall develop procedures for office security and management of classified material.

13. The contractor shall develop continuity of operations plans, emergency evacuation and other force protection plans in accordance with current policies.

Performance Deliverables

Monitoring Method

2. Monthly reports.

2.2 LABORATORY TECHNICAL SUPPORT

The contractor shall provide professional staff with the necessary technical expertise to perform the following representative tasks:

2.2.1 Strategies, Architecture, and Standards Group

The Navy ERP Program Strategies, Architecture, and Standards Group (SASG) has the responsibility, authority and accountability (RAA) to design and align the Navy ERP Program architecture with existing DoD and US Navy architectures, as well as emerging architectures within DoD, including those with Joint Service application. This RAA includes the establishment and enforcement of implementation and sustainment standards and strategies associated with the Navy ERP architecture.

The SASG was established to develop, maintain and oversee the Navy ERP architecture and standards and to coordinate interaction and cooperation with DoD and Navy-level architecture and standards groups, such as DoN CIO, OSD Core Business Mission Area Managers, Investment Review Boards, and other OSD groups who

(19)

have interest in Navy ERP business practices.

During design development and as the Navy ERP architecture matures, the SASG will consult with Navy

Functional Area Managers (FAM’s), Navy-level Business Process Owners, the OSD staff, and other stakeholders to ensure that the Navy ERP architecture aligns with the upper-level architectures and their associated

requirements, policies and plans.

2.2.1.1 Activity: Full-time Support Staff. The SASG Support Staff is responsible for supporting the SASG Chairman. They will provide support to facilitate the completion of deliverables for the SASG. They will work closely with the SASG Chairman to ensure the strategies, standards and architectures developed by the SASG support the requirements of the Navy ERP Program. Program support personnel will also provide administrative support to the SASG Chairman in all external stakeholders interface requirements as required.

The contractor shall perform the following tasks:

1. Provide administrative support to SASG Chairman in developing Navy ERP Program architectures, strategies and standards.

2. Provide technical and administrative support to SASG Chairman for interface efforts with internal and external organizations.

3. Provide administrative support in responding to data calls concerning strategies, architectures, and standards issues as directed by SASG Chairman.

4. Ensure SASG deliverables and other important documents are properly maintained and archived as defined by Navy ERP Program Control.

5. Create briefs and/or whitepapers as directed by SASG Chairman.

6. Serve as liaison with all other Navy ERP Program administrative support personnel, and external organization administrative personnel, as required to support SASG objectives.

7. Perform other duties as directed by SASG Chairman.

(20)

Microsoft Word, Excel, PowerPoint, Access, Program Manager and other application programs used by the Program. No product will be incompatible with the program’s standard applications.

Monitoring Method

2. Monthly reports.

2.2.1.2. Activity: Architecture Alignment. This task area is responsible for the management and coordination of all Navy ERP alignment efforts external to the program. The alignment manager support requires a link between the Navy ERP Program and all external constituents in the architecture arena.

1. Establish relationships with all relevant external parties related to architecture alignment.

2. Audit, review, and approve tasks and deliverables of the Architecture Alignment Team.

3. Provide guidance to the Navy ERP Program on developments and requirements emerging from the external architecture initiatives.

4. Coordinate with SASG Chairman and other SASG managers on external architectural issues.

5. Participate in architecture related conferences, presentations and site visits.

6. Ensure the Navy is informed and working diligently in areas related to architecture alignment and compliance.

7. Coordinate and communicate with the Enterprise Architecture Manager on external business process design, technical infrastructure and information assurance architectural decisions. This provides information flow from external stakeholders to internal business process teams.

8. Coordinate alignment of the Navy ERP infrastructure and security architecture with associated DoD and DoN requirements, including the overall DoN and OSD Enterprise architectures.

(21)

Monitoring Method

2. Monthly reports.

2.2.1.3 Activity: Functional/Technical Alignment: This task area is responsible for developing and maintaining a relationship with OSD business area staff, Navy FAMs, DoN CIO, and other services in regard to architecture alignment. The Functional/Technical Alignment support will require several functional/technical liaisons to work directly with their OSD and Navy FAM counterparts in the different functional areas. The functional areas include Acquisition, Logistics, Budgeting, Finance, Human Resources, Technical, and Installations and Environments. In addition to the functional counterparts, support staff will need to work directly with the DoN CIO architects for the system and technical architectural requirements.

1. Establish relationships with all OSD business area staff, Navy FAMs, and DoN CIO personnel related to existing architectures and current architectural alignment efforts.

2. Provide guidance and set standards for the assigned liaison staffs to pursue alignment efforts with their respective functional and technical counterparts.

3. Audit, review, and approve tasks and deliverables of the assigned liaison staff.

4. Coordinate the efforts of all of the liaisons to ensure proper integration across the functional areas.

5. Ensure the alignment schedule is monitored and the SASG’s obligations are met.

6. Provide feedback to the Navy ERP program on business processes, functional requirements, technical infrastructure and security systems initiatives emerging from the OSD business areas.

7. Consult with OSD business area staffs and DoN CIO during the development of their architectures.

8. Represent the Navy ERP Program in OSD business area and FAM meetings.

1. Accuracy. Products shall be factually accurate, complete, and in accordance with Navy standards and policies, as well as other standards and deliverables as mutually agreed to by both the Government and contractor. No

(22)

more than 2% of products will require rework to correct inaccuracies.

Monitoring Method

2. Monthly reports.

2.2.1.4 Activity: Legacy System Sunset Planning. This task area is responsible for working with all of the Navy-level FAM’s to understand and comply with the Navy’s Legacy System Rationalization Process. The support staff assigned in this area will be responsible for educating OSD business area staffs and Navy FAM’s about the Navy ERP solution being implemented by the Navy ERP Program and responding to inquiries or

recommendations pertaining to replacing legacy systems with ERP.

1. Establish active relationships with functional and technical counterparts.

2. Provide feedback to the to the Functional/Technical Alignment staff on activities and interactions with their functional/technical counterparts.

3. Interact with OSD business area staff working groups and the DoN CIO architects during the design and development of their architectures.

4. Work closely with all of the FAM’s to coordinate the Legacy System Rationalization Process, and coordinate with the RICE Liaison on matters pertaining to external interfaces.

(23)

Microsoft Word, Excel, PowerPoint, Access, Program Manager and other application programs used by the Program. No product will be incompatible with the program’s standard applications.

Monitoring Method

2. Monthly reports.

2.2.1.5 Activity: Architecture Collaboration. This task area is responsible for developing relationships with the various DoD Services and Agencies and commercial industry groups. Participation and communication are very important for the Navy ERP Program at these working groups. The bi-directional interface is critical to the success of the program as tremendous knowledge exchange occurs within the working group sessions.

1. Establish relationships with all DoD Services and agencies and commercial committees and/or working groups on architectural initiatives.

2. Audit, review and approve tasks and deliverables of the Collaboration Liaisons.

3. Provide feedback to the Navy ERP Program on the latest initiatives, business practices and technologies emerging from the public and private sectors.

Monitoring Method

(24)

2.2.1.6 Activity: DEIG, ESG, CIT, Other Federal Initiatives Liaison Support. This task area is responsible for representing the Navy ERP Program at meetings and working groups of these external groups and educating the other participants about the programs’ initiatives and accomplishments. Conversely, the liaisons will seek and report relevant information back to the Navy ERP Program.

1. Actively participate on public and private sector committees and/or working groups related to ERP and architectures.

2. Provide feedback to the SASG on the vision, activities and participants of the various initiatives.

3. Perform research and develop white papers on the latest policies, regulations, legislation, etc affecting the architecture arena.

Monitoring Method

2. Monthly reports.

2.2.1.7 Activity: Enterprise Data. This task area is responsible for coordinating the activities of the Operational Data Management, Analytical Data Management and Knowledge Management to ensure that all strategies, architectures, and standards are identified to support data enterprise mapping, warehousing, and knowledge management within the Navy ERP program. Staff in this area will work closely with the Business Process Manager, Master Data Team and the Strategies, Architecture, and Standards Group to define all data and data management requirements for Navy ERP.

(25)

1. Ensure that standards are identified for the storage, use and maintenance of enterprise data.

2. Coordinate with other DoD agencies to ensure DoN Navy standards are considered in the development of interfaces with the Navy’s ERP system.

3. Participate with OSD and DoN to identify authoritative data sources and data users within the Navy and DoD.

4. Work with other Navy data managers to maintain the Navy DISR.

5. Identify and coordinate requirements for operational data, analytical data and knowledge management.

6. Provide enterprise data development progress reports, in contractor format, to the SASG.

Monitoring Method

2. Monthly reports.

2.2.2 System Engineer Support

2.2.2.1 Activity: Support the System Engineer

1. Architecture Establishment and Maintenance: The contractor shall perform the following tasks:

a. Assist the SE in the design, development and maintenance of the Navy’s ERP Architecture using the ARIS Toolset™.

(26)

Navy ERP architecture to the associated DoD and Navy requirements, including the Business Enterprise Architecture (BEA), the Global Information Grid (GIG), the Net-centric Operations Warfare (NCOW) Reference Model, and other emerging architectures.

c. Provide assistance in the various system compliance assessments mandated by external parties.

d. Evaluate support tools.

e. Develop physical data base standards and transition.

f. Develop Business Warehouse Strategy.

g. Develop Enterprise Portal Strategy.

h. Analyze, report and recommend changes to the appropriate databases to maintain interface capability to technical data for interoperability and implementation to configuration management systems.

2. Architecture Configuration Management Support: The contractor shall perform the following

tasks:

a. Assist the SE in the configuration management and control of Navy ERP’s Global Templates.

b. Architectural View Development & Support: Provide support to develop, document and maintain the operational, system, and technical architecture views in ARIS.

3. Interface Control Document Support: The contractor shall support the development of, or updates to, Interface Control Documents (ICD’s) between the Navy ERP Program and legacy system owners for interfaces and data conversions.

(27)

2. Monthly reports.

2.2.2.2 Activity: Architecture Enhancement & Reusability

1. Assist the Navy in further development and enhancement of the Navy ERP architecture to meet other emerging requirements from the various Program Teams

2. Cross Integration Scenario Development: - Assist the Navy in the development and documentation of integrated business and test scenarios. This task includes the facilitation of integration workshops to

develop/update business process scenarios at various levels of detail. The scenarios at a high level will depict the Navy’s business, and at a lower level will be used to test the integration of the solution.

3. Work with other project team members to gather detailed information about the process design and the impact on the roles and the organizations affected (for example, information on the transactions owned by particular roles).

4. Develop standards for System View Documentation.

Monitoring Method

2. Monthly reports.

(28)

1. Methodology & Tool Support: This task entails: (1) facilitation and proctoring of all ARIS/ASAP activities in order to ensure that a consistent and integrated approach is being followed (2) enforcement of standards to ensure architecture consistency and integrity, (3) the development of new solutions for architecture design and documentation, and (4) the development of a migration strategy from ASAP to Solution Manager, if required.

2. Basic ARIS Training: The contractor shall provide an overview of basic ARIS modeling concepts, ARIS methods, and web-based navigation skills as requested. Additionally, the contractor shall provide selected Navy ERP government personnel (designated as modelers) with ARIS basic training including modeling, reporting and database management as requested.

3. ARIS Advanced Methods Training: The contractor shall provide selected Navy ERP government personnel with ARIS Advanced Training including an overview of the ARIS advanced concepts and methods, database administration, user management and advanced reporting skills as requested.

4. ASAP/Solution Manager Training: The contractor shall provide an overview of the ASAP and Solution Manager tools as they relate to the scoping and managing of Navy ERP’s Global Template Version 1.0.

Monitoring Method

2. Monthly reports.

2.2.2.4 Activity: CCB/CMB Support

1. Coordinate review of efforts among principals of the Configuration Management Boards (CMBs) and Configuration Control Board (CCBs).

(29)

2. Maintain the Configuration Management plan.

3. Review and comment on engineering change proposals (ECPs), System Change Requests (SCRs) involving software and hardware.

4. Develop and review configuration management/control documentation.

5. Develop and review documentation for Functional and Physical Audits as well as prepare and perform audits.

6. Coordinate the implementation of the Configuration Management Plan.

7. Develop and review draft revisions to the Configuration Items (CI) List.

8. Review, recommend and implement Configuration Management Tools such as, but not limited: Document Management Tool, Software/Hardware Change request/management Tool and Version Control Tool.

Monitoring Method

2. Monthly reports.

2.2.2.5 Activity: Applications/IT Standards and Architecture

Performance Objectives:

In concert with the SE and Logistics Plans, the Contractor shall support the Government in the design and development and sustainment of IT architecture to include all hardware and software components of the Navy ERP system, as well as the customer facing support provided via the Help Desk.