N00024-21-R-5211 A002.pdf

N0002420NR4900201

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

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

FAR (48 CFR) 53.243

The purpose of this Amendment is to:

1)Section B: Revise CLIN 0018; Change B-215-H002 to full text 2)Section C: Revise SOW C.3.5.11, C.3.6.3, and C.3.7.2.4 3)Section I: Delete DFARS 252.209-7007 4)Section J: Revise Attachment J-3, Delete Attachments J-36 and J-37 5)Section L: Revise Section L.2.1, L.3.1.1, L.3.1.2, L.3.5, L.3.6.4, L.3.6.4.2, and L.3.6.5 6)Section M: Revise Section M.1.5.1

1. CONTRACT ID CODE PAGE OF PAGES

S 1 73

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

16C. DATE SIGNED

BY 18-Jun-2020

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N0002421R5211

X 9B. DATED (SEE ITEM 11)

22-May-2020

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer 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 1 copies 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 ACKNOWLEDGMENT 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)

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:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor 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.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

18-Jun-2020

CODE

NAVAL SEA SYSTEMS COMMAND

1333 ISAAC HULL AVENUE SE

WASHINGTON NAVY YARD DC 20376

N00024 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002421R5211

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0018

The CLIN extended description has changed from:

In support of CLINs 0001 through 0013, and 0017Not to Exceed (NTE) Value- $2,554,000See Note B

To:

In support of CLINs 0004 through 0013, and 0017Not to Exceed (NTE) Value- $2,554,000See Note B

The following were previously included by reference and are now included by full text:

B-215-H002 REFUNDS (SPARES AND SUPPORT EQUIPMENT) (NAVSEA) (OCT 2018)

(a) In the event that the price of a spare part or item of support equipment delivered under this contract significantly exceeds its intrinsic value, the Contractor agrees to refund the difference. Refunds will not be made to recoup the amount of cost decreases that occur over time due to productivity gains (excluding economic purchase quantity considerations) or changes in market conditions.

(b) For purposes of this requirement, the intrinsic value of an item is defined as follows:

(1) If the item is one which is sold or is substantially similar or functionally equivalent to one that is sold in substantial quantities to the general public, intrinsic value is the established catalog or market price, plus the value of any unique requirements, including delivery terms, inspection, packaging, or labeling.

(2) If there is no comparable item sold in substantial quantities to the general public, intrinsic value is defined as the price an individual would expect to pay for the item based upon an economic purchase quantity as defined in FAR 52.207-4, plus the value of any unique requirements, including delivery terms, inspection, packaging or labeling.

(c) At any time up to two years after delivery of a spare part or item of support equipment, the Contracting Officer may notify the Contractor that based on all information available at the time of the notice, the price of the part or item apparently exceeds its intrinsic value.

(d) If notified in accordance with paragraph (c) above, the Contractor agrees to enter into good faith negotiations with the Government to determine if, and in what amount, the Government is entitled to a refund.

(e) If agreement pursuant to paragraph (d) above cannot be reached, and the Navy's return of the new or unused item to the Contractor is practical, the Navy, subject to the Contractor's agreement, may elect to return the item to the Contractor.

Upon return of the item to its original point of Government acceptance, the Contractor shall refund in full the price paid.

If no agreement pursuant to paragraph (d) above is reached, and return of the item by the Navy is impractical, the Contracting Officer may, with the approval of the Head of the Contracting Activity, issue a Contracting Officer's final decision on the matter, subject to Contractor appeal as provided in the "Disputes" clause (FAR 52.233-1).

(f) The Contractor shall make refunds, as required under this requirement, in accordance with instructions from the Contracting Officer.

(g) The Contractor shall not be liable for a refund if the Contractor advised the Contracting Officer in a timely manner that the price it would propose for a spare part or item of support equipment exceeded its intrinsic value, and with such advice, specified the estimated proposed price, the estimated intrinsic value and known alternative sources or item, if any, that can meet the requirement.

(h) This requirement does not apply to any spare parts or items of support equipment whose price is determined through adequate price competition. This requirement also does not apply to any spare part or item of support equipment if the Contractor submitted, and certified the currency, accuracy and completeness of, cost or pricing data applicable to the item.

(End of text)

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

1.0 INTRODUCTION

1.1 SCOPE

This Statement of Work (SOW) sets forth the efforts required for the Small Surface Combatant Combat System Ship Integration and Test (SSC CS SI&T), which includes Lethality and Survivability (L&S) upgrade of the Freedom and Independence Littoral Combat Ship (LCS) variants after Ship delivery and all CS integration on Large Unmanned Surface Vessel (LUSV) both before and after Ship delivery. The SSC CS SI&T effort includes (1) providing program management, planning, training, and other efforts required to effectively support the execution of CS SI&T efforts; (2) development, assessment, modification, and update of CS related Test Procedures, CS Master Test Plan (MTP), and CS Test Sequence Network (TSN); (3) review, development, assessment, modification, and update of CS Space Arrangement drawings, CS Installation Control Drawings and CS Interface Control Drawings to include end-to-end CS Interface Control Drawings; (4) performance of CS Ship Integration and Test Planning; (5) performance of Waterfront Integration and Test of the CS and Combat System Support Equipment (CSSE) at the system and subsystem levels; (6) providing support to Government Test Teams in conducting the CS Ship Test and Trials Program; and (7) engineering studies to include feasibility studies as tasked by the Government for CS improvements.

CLIN 0001 – Develop Program Management Documents, in accordance with Paragraph 3.1.13: The Contractor shall develop program management and performance documents.

CLIN 0002- LCS Freedom Develop CS Test Procedures, CS Test Sequence Network (TSN), & CS Master Test Plan (MTP), in accordance with Paragraph 3.2: The Contractor shall develop, modify, and update the CS Test Procedures, MTP, and TSN.

CLIN 0003 - LCS Independence Develop CS Test Procedures, CS Test Sequence Network, & CS Master Test Plan, in accordance with Paragraph 3.2: The Contractor shall develop, modify, and update the CS Test Procedures, MTP, and TSN.

CLIN 0004 (1004-6004) - LUSV Develop CS Test Procedures, CS Test Sequence Network (TSN), & CS Master Test Plan (MTP), in accordance with Paragraph 3.3: The Contractor shall develop, modify, and update the CS Test Procedures, MTP, and TSN.

CLIN 0005 (1005-9005) - Develop LCS Freedom CS Space Arrangement Drawings, CS Installation and Interface Control Drawings, in accordance with Paragraph 3.4: The Contractor shall review, develop, update, and modify the CS Space Arrangements, CS Installation Drawings, and CS Interface Controls Drawings, which includes CS Topside and below deck. The Contractor shall also develop, modify, and update complete end-to-end CS Interface Control Drawings.

CLIN 0006 (1006-9006) - Develop LCS Independence CS Space Arrangement Drawings, CS Installation and Interface Control Drawings, in accordance with Paragraph 3.4: The Contractor shall review, develop, update, and modify the CS Space Arrangements, CS Installation Drawings, CS Interface Controls Drawings, and Ship Installation Drawings (SIDs), which includes CS Topside and below deck. The Contractor shall also develop, modify, and update complete end-to-end CS Interface Control Drawings.

CLIN 0007 (1007-9007) - Develop LUSV CS Space Arrangement Drawings, CS Installation and Interface Control Drawings, in accordance with Paragraph 3.4: The Contractor shall review, develop, and provide recommendations as necessary to the new CS Space Arrangements, CS Installation Drawings, CS Interface Controls Drawings, and Ship Installation Drawings (SIDs), which includes CS Topside and below deck. The Contractor shall also review, develop, and provide recommendations as necessary to the complete end-to-end LUSV CS Interface Control Drawings.

CLIN 0008 (1008-9008) - LCS Freedom CS Ship Integration Engineering and Test Planning, in accordance with Paragraph 3.5: The Contractor shall review and analyze CS designs and ensure that intra CS Enclave and inter enclaves are integrated. The Contractor shall also perform CS Test Planning for LCS and assist the Shipyard and Alteration Installation Team (AIT) during the CS Ship Installation and Integration.

CLIN 0009 (1009-9009) - LCS Independence CS Ship Integration Engineering and Test Planning, in accordance with Paragraph 3.5: The Contractor shall review and analyze CS designs and ensure that intra CS Enclave and inter enclaves are integrated. The Contractor shall also perform CS Test Planning for LCS and assist the Shipyard and AIT during the CS Ship Installation and Integration.

CLIN 0010 (1010-9010) - LUSV CS Ship Integration Engineering and Test Planning, in accordance with Paragraph

3.5 (The Contractor shall review and analyze CS designs and ensure that all CS are integrated. The Contractor shall also perform CS Test Planning and assist the Shipbuilder during the CS Ship Installation and Integration.

CLIN 0011 (1011-9011) - LCS Freedom CS Waterfront Integration and Test, in accordance with Paragraph 3.6: The Contractor shall integrate CS with the ship systems by providing required expertise to perform integration and test, CS Test Coordination, CS Alignment, and CS Engineering and Test Execution.

CLIN 0012 (1012-9012) - LCS Independence CS Waterfront Integration and Test, in accordance with Paragraph 3.6: The Contractor shall integrate CS with the ship systems by providing required expertise to perform integration and test, CS Test Coordination, CS Alignment, and CS Engineering and Test Execution.

CLIN 0013 (1013-9013) - LUSV CS Waterfront Integration and Test, in accordance with Paragraph 3.6: The Contractor shall integrate CS with the ship systems by providing required expertise to perform integration and test, CS Test Coordination, CS Alignment, and CS Engineering and Test Execution.

CLIN 2014 (3014-9014) - LCS Freedom Post Delivery and Post-Industrial CS Tests and Trials Support, in accordance with Paragraph 3.7: The Contractor shall monitor, coordinate, and provide on-site (ship and shore) support for Combat System Ship Qualification Trials (CSSQTs), Developmental Testing (DT), Operational Test (OT), and CS modifications or special testing.

CLIN 2015 (3015-9015) - LCS Independence Post Delivery and Post-Industrial CS Tests and Trials Support, in accordance with Paragraph 3.7: The Contractor shall monitor, coordinate, and provide on-site (ship and shore) support for Combat System Ship Qualification Trials (CSSQTs), Developmental Testing (DT), Operational Test (OT), and CS modifications or special testing.

CLIN 2016 (3016-9016) - LUSV Post Delivery and Post-Industrial CS Tests and Trials Support, in accordance with Paragraph 3.7: The Contractor shall monitor, coordinate, and provide on-site (ship and shore) support for Combat System Ship Qualification Trials (CSSQTs), Developmental Testing (DT), Operational Test (OT), and CS modifications or special testing.

CLIN 0017 (1017-9017) - Engineering Services, in accordance with Paragraph 3.8: The Contractor shall provide engineering services to include but not limited to, conducting and supporting feasibility studies, data analysis, test and evaluation, safety, Failure Review Boards (FRBs), project engineering, and revising, updating, and modifying documents. The Contractor shall also provide in-service support to LUSV ships as specified in the TI.

CLIN 0018 (1018-9018)- Other Direct Costs (ODCs) and Incidental Materials, in accordance with Paragraph 3.9:

This Contract Line Item Number (CLIN) includes ODCs and Incidental Materials for work performed under CLINs 0004, 0005, 0006, 0007, 0008, 0009, 0010, 0011, 0012, 0013, 0017, and Option CLINs if exercised, 1004-6004, 1005-9005, 1006-9006, 1007-9007, 1008-9008, 1009-9009, 1010-9010, 1011-9011, 1012-9012, 1013-9013, 1017- 9017, 2014-9014, 2015-9015, and 2016-9016.

CLIN 0019 - Provisioned Item Orders (PIO), in accordance with Paragraph 3.10: This CLIN includes PIO to support the efforts under CLINs 0004, 0005, 0006, 0007, 0008, 0009, 0010, 0011, 0012, 0013, and Option CLINs if exercised, 1005-9005, 1006-9006, 1007-9007, 1008-9008, 1009-9009, 1010-9010, 1011-9011, 1012-9012, 1013- 9013, 2014-9014, 2015-915, and 2016-9016.

CLIN 0020 - Data CLIN (Not Separately Priced), in accordance with Paragraph 3.11: The data to be furnished hereunder shall be prepared and delivered in accordance with the Contract Data Requirements List (CDRL), DD Form 1423, Section J, Exhibit A/Exhibit B, attached hereto.

CLIN 0021 - Data Rights Buy-Out, in accordance with Paragraph 3.12: and Attachment J-25B.

2.0 APPLICABLE DOCUMENTS (Applicable to all Contract Line Item Numbers (CLINs)

The following documents in paragraphs 2.1-2.4 are applicable to the tasks described herein and are for use by the Contractor as general guidance in the fulfillment to integrate products onto the Ship under this contract unless referenced otherwise in this SOW as mandatory use or as instructed in a TI.

Copies of military specifications and standards and DoD adopted non-Government standards may be obtained in accordance with Federal Acquisition Regulation (FAR) 52.211-1 through 52.211-4. Copies of non-Government publications cited in this solicitation, if listed in the DoD Index of Specifications and Standards (DoDISS) or the Acquisition Streamlining and Standardization Information System Tool (ASSIST) may be obtained from:

a. ASSIST database via the Internet at http://quicksearch.dla.mil/

b. DoD issuances http://www.dtic.mil/whs/directives/

c. DoN issuances https://www.secnav.navy.mil/doni/default.aspx

Requests for copies of documents not available from either source should be directed to the Contracting Officer Representative (COR).

https://www.secnav.navy.mil/doni/default.aspx

Note: The contractor shall verify and use the current version unless previous versions of these documents may apply to the Ship Baseline (based on system procurement date).

2.1 MILITARY STANDARDS

2.2 NAVSEA REGULATIONS, DIRECTIVES, AND INSTRUCTIONS

NAVSEA 9093.1D Combat System Ship Qualification Trials for Surface Ships 30 Aug 2006

NAVSEA S9095 AD-

TRQ-010/TSTP

Total Ship Test Program Manual Mar 1995

NAVSEA 9400.2-AM NAVSEA Platform Information Technology-Control Systems Cybersecurity Governance and Guidance Technology-Control Systems

20 Sep 2016

PEOIWSINST 4130.C PEO IWS Enterprise Configuration Control Process May 2017 PEOIWSINST 5239.1 PEO IWS Surface Navy Combat System Cybersecurity 31 May 2016 PEOIWSINST 5000.8 Risk Management Policy 13 Jan 2014

2.3 DEPARTMENT OF DEFENSE (DOD) STANDARDS/INSTRUCTIONS

DoDI 5000.2, Change 4 Operation of Defense Acquisition System 31 Aug 2018

MIL-STD-167-1A Mechanical Vibrations of Shipboard Equipment (Type I- Environmental and Type II-Internally Excited)

02 Nov 2005

MIL-STD-461G Department of Defense Interface Standard-Requirements for the Control of Electromagnetic Interference (EMI) Characteristics of Subsystems and Equipment

11 Dec 2015

MIL-STD-1605A Procedures for Conducting a Shipboard EMI Survey 12 Aug 2014 MIL-STD-882E System Safety 11 May 2012 MIL-DTL-901E Shock Tests, H.I. (High Impact) Shipboard Machinery

Equipment, and Systems, Requirements for

20 Jun 2017

MIL-STD-810H Environmental Engineering Considerations and Laboratory Tests

31 Jan 2019

MIL-STD-464C Electromagnetic Environmental Effects, Requirements for Systems

01 Dec 2010

MIL-STD-1399C Interface Standard for Shipboard Systems 02 Feb 1988 MIL-D-23140D Drawings, Installation Control, for Electronic Equipment 30 Apr 1992 MIL-STD-1310H Shipboard Bonding, Grounding, and Other Techniques for

Electromagnetic Compatibility and Safety

12 Aug 2014

MIL-STD-2042C Fiber Optic Cable Topology Installation Method for Surface Ships and Submarines

18 Oct 2016

MIL-STD-31000B Technical Data Packages 31 Oct 2018

MIL-STD-2106A Development of Shipboard Industrial Test Procedures 04 Jun 2014

MIL-HDBK-1785

NOT 2

System Security Engineering Program Management Requirements

11 Feb 2019

MIL-STD-881D Work Breakdown Structures for Defense Material Items 19 Jun 2018

DoD 5000.2-R Mandatory Procedures for Major Defense Acquisition Programs (MDAPS) and Major Automated Information System (MAIS) Acquisition Programs

05 Apr 2002

DoD 5000.04-M-1 Cost and Software Data Reporting (CSDR) Manual 04 Nov 2011 DoD 5220.22-M National Industrial Security Program Operating Manual 1 Aug 2018 DODI 8500.01 Cybersecurity 14 Mar 2014 DODI 8510.01 Risk Management Framework (RMF) for DOD Information

Technology (IT) 28 Jul 2017

2.4 OTHER DOCUMENTS

COMNAVSURFPAC/

COMNAVSURFLANT

TSRA Instruction 4700.1B

Total Ships Readiness Assessment (TSRA) 23 Jan 2017

NIST SP 800-53A, Rev

Assessing Security and Privacy Controls in Federal Information Systems and Organization

18 Dec 2014

NIST SP 800-53, Rev 4 Security and Privacy Controls for Federal Information Systems and Organizations

22 Jan 2015

CNSSI 1253 Security Categorization and Control Selection for National Security Systems

27 Mar 2014

SECNAVINST 5239.22 Department of the Navy Cybersecurity Safety Program 15 Nov 2016

OPNAVINST 5239.22 Chief of Naval Operations Cybersecurity Safety (CYBERSAFE) Program

Draft (14 Jul 2017)

SECTION C: PART 1 – CONTRACT LINE ITEM DESCRIPTION

3.0 STATEMENT OF WORK REQUIREMENTS

In performance of this contract, the Contractor shall fulfill the requirements in accordance with all applicable documents, exhibits, and attachments listed in Section J.

In accordance with C-242-H003 TECHNICAL INSTRUCTIONS (NAVSEA) (OCT 2018), the Contracting Officer’s Representative (COR) or the PCO will issue Technical Instructions (TI) on the LOE CLINs after contract award that provide for further clarification and technical details for the efforts to be performed under subparagraphs mentioned below. The tasks mentioned herein on the LOE CLINs shall be performed as directed by each TI.

3.1 PROGRAM MANAGEMENT, PROCESS, STANDARDS, AND PERFORMANCE AND REPORTING

REQUIREMENTS (APPLICABLE TO ALL CLINS)

The Contractor shall communicate and document its plans, processes and approaches to meet Small Surface Combatants Combat System Ship Integration and Test (SSC CS SI&T) requirements, which includes both LCS and LUSV Class ships. The Contractor shall use a management approach appropriate for planning, scheduling, technical, cost, risk, and quality monitoring/reporting, to facilitate Government reviews.

The Contractor shall prepare and deliver Monthly Progress and Status Reports, including financial reports in accordance with CDRL A001. Monthly reports may reference material as presented at program reviews if previously delivered via an Integrated Data Environment (IDE).

The Contractor shall make available to Government personnel all data used on or produced in support of this contract. The Government reserves the right to witness all Contractor efforts to accomplish the SOW requirements and maintains the right to comment on processes. The Contractor shall provide notice 30 calendar days in advance of any events, tests, or activity that the Government identifies as a specific item of interest in the appropriate TI.

The Contractor shall provide and maintain two (2) facilities, one for each homeport that are within a 30 minute drive; West coast (Naval Base San Diego) and East Coast (Naval Station Mayport) for LCS Freedom and LCS Independence and at least one facility to accommodate LUSV. Each facility shall accommodate at least ten (10) personnel throughout the performance period of the contract. Each facility shall include, at a minimum, desks, chairs, high-speed broadband internet access, access to filing space, and conference rooms/amenities. Each facility shall also include a color printer with printing/copying/scanning capabilities, and telephone (unlimited local and long distance) with one dedicated line for the fax machine.

CDRL A001 Contractor’s Progress, Status and Management Report

3.1.1 PROGRAM MANAGER (PM) (Applicable to all CLINs)

The Contractor shall assign a single PM who is specifically charged with the responsibility for the planning, execution, and control of all aspects of this contract, and for directing in-house and subcontractor’s efforts. The PM shall also establish, implement and maintain a management system and organization that shall plan, organize, control, and oversee activities relating to this contract. The PM shall ensure all work conducted is planned and executed in a manner that achieves all management, technical, logistics, budget, and schedule objectives. The PM shall have the necessary authority to utilize the company’s resources to assure the efforts in the SOW are accomplished. The PM shall also function as the primary interface with the Government’s representatives on all matters pertaining to this contract.

3.1.2 PROGRAM MANAGEMENT PLAN (PMP) (Applicable to all CLINs)

The Contractor shall develop and maintain a PMP that will apply to the SSCs, in accordance with CDRL A002. The PMP shall support the Government schedule requirements in accordance with the CS Support to LCS Freedom, LCS Independence, and LUSV Notional Ship Schedules, Attachment J-1, Attachment J-2, and Attachment J-3 respectively. The PMP shall demonstrate that the program structure is executable within schedule and cost constraints. The PMP shall correlate with the SOW and Contract Work Breakdown Structure (CWBS). The PMP shall include, but not be limited to: 1) any assumptions/guidelines and a dictionary of definitions for selected events used within the accomplishment criteria; 2) listing of all events, significant accomplishments, and criteria; 3) description of the purpose, contract entrance criteria to subcontracts, expected results, and proposed contractual closure criteria for each event. A direct and traceable correlation shall exist between events in the PMP and Integrated Master Schedule (IMS). The Contractor shall update the PMP as necessary throughout the life of the contract and as directed by a TI.

CDRL A002 Management Plan, Program Management Plan (PMP)

3.1.3 SUBCONTRACTOR/SUPPLIER MANAGEMENT (Applicable to all CLINs)

The Contractor shall be responsible for the performance of its subcontractors/suppliers and shall implement appropriate management actions relative to subcontractor/supplier performance. Further, unless specified elsewhere, the Contractor shall flow down requirements of this contract (as applicable) to all subcontractors. The Prime Contractor shall be accountable for the subcontractor’s/supplier’s compliance and shall be responsible for ensuring all deliverable products comply with contractual requirements.

3.1.4 SYSTEM SECURITY PROGRAM (Applicable to all CLINs)

Using the MIL-HDBK-1785 as a guide (DOD SYSTEM SECURITY ENGINEERING PROGRAM MANAGEMENT REQUIREMENTS) and DoD 5220.22-M, "National Industrial Security Program Operating Manual," the Contractor shall establish a System Security-Engineering Program that identifies, evaluates, and proposes solutions for eliminating or mitigating system vulnerabilities to known or postulated threats.

The Contractor shall develop, execute, and maintain a comprehensive Security Management Plan (SMP), as part of the PMP, in accordance with CDRL A002, and DoD 5220.22-M and MIL-HDBK-1785 as guidance, and consistent with the LCS and LUSV Security Classification Guides and all appropriate security instructions.

All Contractor personnel accessing classified information or material associated with and/or performing classified work relative to the contract must be United States citizens and shall have and maintain at a minimum a final SECRET security clearance.

The Contractor requires SIPRNET access to review and transmit classified information related to the SSC Combat System to perform this contract.

The Contractor shall adhere to Government and program regulations, policies, and procedures controlling the access of program facilities, information and systems by visitors. All Contractor personnel requiring access to the Government workspaces shall complete a National Agency Check (NAC).

An active SECRET Facility Clearance (FCL) is required for performance on this contract. The Contractor must have a Safeguarding Level of SECRET.

Communications Security (COMSEC): The Contractor requires COMSEC account to accommodate the use of secure communications with its subcontractors and the Government.

The Contractor will require access to Controlled Unclassified Information (CUI) (Formerly for Official Use Only Information) with developers and integrators in order to receive, store, and generate controlled classified information.

The Contractor shall assist in developing classified Small Surface Combatant Combat System Ship Integration and Test Program documentation to be provided via email and written reports. The test documentation shall support the Lethality and Survivability upgrades of the Small Surface Combatants which include the in-service LCS Freedom and Independence variants and the new construction Large Unmanned Surface Vessel (LUSV) class ships. In this capacity, the Contractor shall generate and be in receipt of classified material.

CDRL A002 Management Plan, Program Management Plan (PMP)

3.1.4.1 OPERATIONS SECURITY PROGRAM PLAN (Applicable to all CLINs)

The Contractor shall develop, implement and maintain an Operations Security (OPSEC) Program Plan as part of the PMP in accordance with CDRL A002 to protect classified and sensitive unclassified activities, information, equipment and material used or developed by the Contractor and any subcontractor during the performance of this Contract. The OPSEC Program Plan shall include physical security and access control that ensures that foreign nationals and others without a need to know and appropriate clearance cannot physically access (or visually observe) or electronically access SSC CS SI&T information and equipment. The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements of this Contract. All Contractor and subcontractor OPSEC programs shall be in full compliance with the latest version of the National Industrial Security Program Operating Manual (NISPOM). The Contractor shall also follow Contract Security Classification Specification, DD Form 254, Attachment J-7. The Contractor shall update the plan as necessary throughout the life of the contract or as directed by a TI.

CDRL A002 Management Plan, Program Management Plan (PMP)

3.1.5 PROGRAM MANAGEMENT MEETINGS AND TECHNICAL REVIEWS

3.1.5.1 POST AWARD KICK-OFF MEETING (Applicable to CLINs 0001, 0002, 0003, and 0020)

The Contractor shall provide a detailed briefing on its overall management and contract execution strategy at the Post-Award Kick-off Meeting within two (2) weeks of contract award. The Contractor shall also include a discussion of the Contractor’s standard Cost and Software Data Reporting (CSDR) process that satisfies the guidelines contained in the DoD 5000.04-M-1, CSDR Manual, and the requirements in the Government-approved CSDR Plan, DD Form 2794, Attachment J-5, and related Resource Distribution Table (RDT), Attachment J-6. The Government and the Contractor shall work together to develop or update charters for Integrated Product Teams (IPTs), as required. The Contractor shall prepare an agenda, meeting minutes, and presentation materials in support of the meetings in accordance with CDRLs A003, A004 and A005 respectively.

CDRL A003 Conference Agenda CDRL A004 Report, Record of Meetings/Minutes CDRL A005 Presentation Material

3.1.5.2 TECHNICAL INSTRUCTION (TI) KICK-OFF MEETING (Applicable to CLINs, including Options if exercised, 0004-6004, 0005-9005, 0006-9006, 0007-9007, 0008-9008, 0009-9009, 0010-9010, 0011-9011, 0012- 9012, 0013-9013, 0017-9017, and 0018-9018)

Separate Kick-Off Meetings may also be required by the Government when TIs are issued on high-risk or high-technical interest task(s) and/or if Options are exercised. If a separate kick-off meeting is required, the Contractor shall provide a detailed briefing on its management and execution strategy and shall prepare an agenda, meeting minutes, and presentation materials in support of the meetings, in accordance with CDRLs A003, A004 and A005 respectively.

CDRL A003 Conference Agenda CDRL A004 Report, Record of Meetings/Minutes CDRL A005 Presentation Material

3.1.5.3 QUARTERLY PROGRAM REVIEWS (Applicable to all CLINs)

The Contractor shall conduct Quarterly Program Reviews (QPRs), which may be conducted via a virtual collaborative environment or other Government-approved means. The QPR shall be documented with agendas, minutes, and presentation materials in accordance with CDRLs A003, A004 and A005 respectively. Additionally, the QPR shall include as it applies, but not be limited to the following:

a. Ensuring a mutual understanding of the objectives and scope of the work.

b. Addressing Technical Instructions.

c. Reviewing progress to-date.

d. Reviewing project deliverables.

e. Validating detailed work plans.

f. Confirming resolved issues and management of outstanding issues. This shall include status of significant problems faced by the Program Manager and current plans to resolve the problems or mitigate their impacts.

g. Identifying and evaluating risk factors and address areas where risk has changed.

h. Identifying cost and schedule variance in a combined manner for all Contractor WBS elements at the third indenture level. The presentation should identify the data points that are considered “out of tolerance” from Integrated Program Management Report (IPMR) criteria.

i. Identifying problems with Government documents during the quarter, including impacts and solutions.

CDRL A003 Conference Agenda CDRL A004 Report, Record of Meetings/Minutes CDRL A005 Presentation Material

3.1.6 RISK MANAGEMENT PLAN (Applicable to all CLINs)

The Contractor shall develop and maintain a Risk Management Plan in accordance with CDRL A006 and PEO IWS Instruction 5000.8. The Contractor’s plan shall define steps to identify, respond, analyze, and mitigate risks. The plan will be used to monitor management, cost, and schedule of the contract efforts to assess the impact to the program. The plan shall be updated as necessary throughout the life of the contract or as directed by a TI.

CDRL A006 Contractor’s Risk Management Plan

3.1.7 BUSINESS AND FINANCIAL MANAGEMENT (Applicable to all CLINs)

The Contractor shall establish, maintain, and use in the performance of this contract, a cost management system linked to, and supported by the Contractor’s management processes and in accordance with the Integrated Program Management Report (IPMR) to include the Integrated Master Schedule (IMS), Contract Work Breakdown Structure (CWBS), change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these products shall provide for early indication of cost and schedule problems, and their relation to technical achievement. The Contractor shall report program cost and schedule status in accordance with CDRL A007. The Contractor shall provide a reconciliation of the Contract Funds Status Report (CFSR) with the IPMR as an addendum. Also, the Contractor shall prepare and provide Monthly Progress and Status Reporting in accordance with CDRL A001.

CDRL A001 Contractor’s Progress, Status, And Management Report CDRL A007 Contract Funds Status Report (CFSR)

3.1.7.1 CONTRACT WORK BREAKDOWN STRUCTURE (CWBS) (Applicable to all CLINs)

The Contractor shall develop and update the CWBS in accordance with CDRL A008 and the Government WBS, Attachment J-4 as directed by a TI. The CWBS shall be consistent with DoD Manual 5000.04-M-1, CSDR Manual and MIL-STD-881D, Department of Defense Standard, WBS for Defense Material Items. All revisions to the CWBS shall require approval of the Government prior to implementation. The Contractor shall use the CWBS as the structure and the common link that unifies the planning, scheduling, cost estimating, budgeting, contracting and performance reporting disciplines. The CWBS shall provide clear traceability of work efforts and end products.

CDRL A008 Contract Work Breakdown Structure (CWBS)

3.1.7.2 INTEGRATED PROGRAM MANAGEMENT REPORT (IPMR) (Applicable to all CLINs)

The Contractor shall deliver an IPMR as directed by a TI and prepared in accordance with CDRL A009. The IPMR shall provide data for measuring contract cost and schedule performance. The IPMR shall clearly distinguish the performance data associated with each CLIN, as well as each TI, executed under this contract. Each TI will provide further detail on IPMR requirements specific to the individual TI, as applicable. Specific details may include, but are not limited to, reporting format, frequency of delivery, and CWBS level of reporting.

CDRL A009 Integrated Program Management Report (IPMR)

3.1.7.3 PROGRAM INTEGRATED MASTER SCHEDULE (IMS) (Applicable to all CLINs)

The Contractor shall deliver and maintain a resource-loaded IMS in accordance with CDRL A009 for program control, status monitoring, and reporting purposes. The IMS shall use the CWBS for tracing all work to be performed on this contract. The IMS shall identify all tasks that are required and shall allocate resources to and designate responsibility within the program for each task. The IMS shall be detailed enough to support Government extraction of detailed Contractor functional level planning to incorporate coincident Government Program level activities. The IMS shall clearly distinguish the schedule data associated with each CLIN, as well as each TI, executed under this contract. Each TI will provide further detail on IMS reporting requirements specific to the individual TI, as applicable. Specific details may include, but are not limited to, reporting format, frequency of delivery, and CWBS level of reporting. The Contractor shall flow down IMS reporting requirements to all subcontractor(s) which meet the reporting thresholds as defined in DoD 5000.2. The IMS from the subcontractor(s) shall be integrated with the prime Contractor’s scheduled events.

CDRL A009 Integrated Program Management Report (IPMR)

3.1.7.4 COST AND SOFTWARE DATA REPORTING (CSDR) (Applicable to all CLINs)

Per DFARS 252.234-7004, “Cost and Software Data Reporting System” (CSDRS), the Contractor shall establish, deliver, implement, and maintain a CSDRS. The Contractor shall follow the CSDR Plan to identify the required reports and systematically collect and report actual contract costs to provide the Government with needed data to estimate future costs. The Contractor shall provide these reports for all contracts and subcontracts over $50 million in accordance with the Cost and Hour Report (Flexfile) (CDRL A010), Quantity data Report (CDRL A011), and the Contractor Business Data Report, DD Form 1921-3 (CDRL A034). These reports shall be aligned with the Government approved CSDR Plan (Attachment J-5).

The Contractor shall identify any subcontractor(s) at any tier with a subcontract that exceeds $50 million, by providing comments on the RDT (Attachment J-6) of the subcontractor(s), or, if have not been selected, the subcontracted efforts in this category and provide to the Government. If, for subcontracts that exceed $50 million, the Contractor changes subcontractors or makes new subcontract awards, the Contractor shall notify the Government.

CDRL A010 Cost and Hour Report (Flexfile), Contractor Cost Reporting (CCDR) CDRL A011 Quantity Data Report, Contractor Cost Data Reporting (CCDR) CDRL A034 Contractor Business Data Report (DD Form 1921-3), Contractor Cost Reporting (CCDR)

3.1.7.5 CONTRACT FUNDS STATUS REPORT (CFSR) (Applicable to all CLINs)

The Contractor shall report financial data as CFSR in accordance with CDRL A007 using a Defense Contracting Auditing Agency (DCAA) approved accounting system that operates in accordance with accepted commercial accounting standards. The Contractor shall flow down CFSR reporting requirements to all subcontractor(s) who meet the reporting thresholds as defined in DoD 5000.2.

CDRL A007 Contract Funds Status Report (CFSR), DD Form 1586

3.1.7.6 EARNED VALUE MANAGEMENT (Applicable to Completions CLINs, 0001, 0002, 0003)

In the performance of this contract, the Contractor shall establish, maintain, and use an integrated performance management system. Central to this integrated system, the Contractor shall use a validated Earned Value Management System (EVMS) per DFARS 252.234-7002, “Earned Value Management System (Deviation 2015- O0017),” subject to DFARS 252.242-7005, “Contractor Business Systems,” and the EVMS guidelines contained in ANSI/EIA-748. To establish the integrated performance management system, the EVMS shall be linked to and supported by the Contractor’s management processes and business systems. The Contractor shall flow down EVMS requirements to subcontractors that meet the thresholds and criteria prescribed in DoDI 5000.02.

The Contractor and all applicable subcontractors shall use an EVMS that has been certified by the Defense Contract Management Agency (DCMA) Center of Excellence. If the Contractor and/or subcontractors do not have a DoD-validated EVMS, the Contractor shall provide a plan of action and milestones that establishes the path to EVMS compliance. Additionally, if required by the Government, the Contractor shall initiate an EVMS certification review within one hundred and fifty (150) days of contract award. The Contractor and its subcontractors shall be responsive to DCMA Center of Excellence requirements to achieve EVMS certification no later than six (6) months from the date of contract award.

3.1.8 DATA MANAGEMENT AND INTEGRATED DATA ENVIRONMENT (IDE) (Applicable to all CLINs)

The Contractor shall maintain records in all areas of work performed under this contract. The Contractor shall be responsible for the development and management of all documentation generated under this contract and shall implement a Data Management Program (Contractor IDE) in order to maintain files of record to include reproducible copies (including original, as appropriate) of all data that is generated under this contract.

The purpose of the IDE environment is to create a seamless, collaborative data environment for the Contractor and Government team which contains all data about the project throughout its development and delivery. This Data Management Program, including IDE structure, format, processes, and procedures, shall be documented as part of the contract PMP.

The Contractor IDE shall support 25 Government seats for access to the classified IDE and 25 Government seats for access to the unclassified IDE. This IDE shall host all working-level data (i.e. not formal CDRL delivery data) used on or produced in support of this contract, including cost, schedule, and technical data. Data hosted on the Contractor established portal shall be publishable and discoverable. In addition, all data used on or produced in support of this contract shall be made available to Government personnel through its secure unclassified and classified IDE with no less than 95% annual availability during the workweek. The Contractor shall grant Government team access to the Contractor IDE. All items posted in the Contractor IDE, such as drafts of deliverables that are not final versions, shall be considered as drafts until formally posted into the Government IDE, Integrated Product Data Management (iPDM).

The Government IDE (iPDM) provides a secure data repository for data exchange and storage with the necessary access control for data protection in conjunction with a collaborative environment. Data deliverables posted in iPDM shall be the formal delivery method for all CDRL deliverables. All data developed and delivered (draft or final) under this contract shall be in accordance with the DFARS Data Rights clauses (DFARS 252.227-7013 and 252.227-7014). The Data Accession List (DAL) shall contain the list of all data generated in support of this contract and be prepared in accordance with CDRL A012. In accordance with Department of Defense (DoD) requirements, the iPDM is configured to use the Public Key Infrastructure (PKI) certificate to verify user identity. This certificate may be provided by a DoD-issued Common Access Card (CAC). The Contractor will be required to submit a request to obtain a CAC in order to access and upload deliverables in iPDM.

All official data and deliverables will be retained in iPDM. The Contractor shall use iPDM to upload and directly deliver all contract data deliverables to the Government. All data uploaded in iPDM by the Contractor shall include associated attributes and shall be saved in Government defined formats and locations. The Government will provide official correspondence such as approval/disapproval letters, comments, and recommendations back to the Contractor via Disposition Letters on all CDRLs.

Any deliverables, products, and Non-commercial Technical Data and Non-commercial Computer Software developed under this contract shall be delivered with Government Purpose Rights in accordance with DFARS 252.227-7013 and 252.227-7014 and appropriately marked as such unless a waiver has been submitted and approved by the Contracting Officer. In this context, technical data and CS developed under this contract do not include embedded open source or Commercial Off-The-Shelf (COTS) software products. A report verifying the appropriate markings, including security classification and data rights, shall be delivered with the product.

The Contractor shall comply with the requirements of the DD Form 254, Attachment J-7, for implementation and to ensure proper safeguarding of classified materials, events and processes. This will include documentation developed by the Contractor or received in support of working groups and IPTs.

CDRL A012 Data Accession List (DAL)

3.1.9 CONFIGURATION MANAGEMENT (CM) (Applicable to all CLINs)

The Contractor shall develop Configuration Management Program Plan (CMPP), CM definition reports, and CM Control Support reports. The Contractor shall also update the CMPP throughout the life of the contract as necessary and as directed by Technical Instruction (TI).

3.1.9.1 CONFIGURATION MANAGEMENT PROGRAM PLAN (CMPP)

The Contractor shall develop a Configuration Management Program Plan (CMPP) in accordance with CDRL A013 and update as necessary as directed by a TI. The CMPP shall be aligned with the approved plans of the PEO IWS

8.0 Configuration Management Plan (CMP) provided in Attachment J-8. The CMPP shall include the shipboard installation, integration, and test of equipment comprising the Combat System for LCS and LUSV Class ships.

CDRL A013, Configuration Management Program Plan (MIL-STD-3046)

3.1.9.2 CONFIGURATION DEFINITION (Applicable to all CLINs)

The Contractor shall provide a Configuration Identification Baseline Report, which includes CM Definition for the LCS baselines and LUSV baseline development in accordance with CDRL A016 as directed by a TI.

CDRL A016 Baseline Description Document, Configuration Identification Baseline Report

3.1.9.3 CONFIGURATION MANAGEMENT AND CONTROL SUPPORT (Applicable to all CLINs)

The Contractor shall provide change impact assessments, as requested, during the test and integration period for software/hardware change requests.

The Contractor shall provide Test Observation Reports (TORs) in accordance with CDRL A017 to document the discrepancies found during the testing and validation efforts. The Contractor shall also provide recommendations to the Government in support of software/hardware change request development for valid TORs in accordance with the TOR Classification in Attachment J-9. The Contractor shall participate and serve as a third party to Configuration Control Boards (CCBs and provide the results to support outputs at boards/events such as, but not limited to, PEO IWS 8.0 Software Configuration Control Boards (SCCBs), CS Mission Readiness Assessments (MRAs), and/or Combat System Certification Panels (CSCPs).

The Contractor shall maintain and control software/hardware change requests and TOR data in accordance with the designated classification level imposed by the Government classification guidance. The Contractor will be provided access to the Government TOR database for each LCS variant and LUSV.

The Contractor shall provide recommendations for ECPs and developed in accordance with CDRL A014 as required against baselined program artifacts. The Contractor shall also support development of Engineering Change Requests (ECRs), ECPs, Ship Change Documents (SCDs), and SCCB package generation to allow for delivery and installation of changes to the ship.

When documenting changes to an existing software baseline technical documentation, which impacts testing and/or test documentation using “Revisions to Existing Documents,” the Contractor shall document in accordance with CDRL A018. The Contractor shall document changes using a consistent method and format as used to document the previous configuration or baseline, and export requirements using a Requirements Management Tool.

The Contractor shall maintain configuration status records that identify approved Engineering Change Proposals (ECPs), Specification Change Notices (SCNs) (CDRL A015) and other revisions to the technical documentation that impacts the test documentation. The Contractor shall also support transition of status accounting data, delivered equipment, and computer programs to the authorized Combat System CM database for PEO IWS 8.0.

The Contractor shall perform Class I and Class II system-level change assessments as requested. The Government will provide the final determination on whether changes are Class I or Class II.

The Contractor shall provide adjudication recommendations to PEO IWS 8.0 (Class I) or (Original Equipment Manufacturer (OEM) (Class II) ECPs as the SI&T representative.

CDRL A014 Engineering Change Proposal (ECP) CDRL A015 Specification Change Notice (SCN) CDRL A017 Scientific and Technical Reports, TORs CDRL A018 Revisions to Existing Government Documents

3.1.10 QUALITY ASSURANCE PROGRAM PLAN (QAPP) (Applicable to all CLINs)

The Contractor shall develop and maintain a QAPP in accordance with CDRL A019 for supplies and services to include, but not limited to, technical documentation, computer software, and hardware. The plan shall also include timely review of documents received and annotation of deficiencies for Government review. The plan will be updated as necessary throughout the life of the contract and as directed by a TI. The Contractor shall document their Quality Assurance Program (QAP) in the QAPP. The Contractor’s approved QAPP shall apply to documentation associated with the technical products and associated CDRLs. The Contractor’s QAPP shall include, but not be limited to the following QA functions, which summarizes some of the key requirements for an acceptable QAPP:

a. The Contractor…