RFP_N00024-18-R-5102_Amendment_0001_with_highlights.docx

N0002418R5102

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 18-Jun-2018 02:00 PM to 09-Jul-2018 02:00 PM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 3002

The CLIN extended description has changed from:

Review, update, and modify CS Space Arrangements, CS Installation Control Drawings, CS Interface Control DrawingsOption Year 2See Note B

To:

Review, update, and modify CS Space Arrangements, CS Installation Control Drawings, CS Interface Control DrawingsOption Year 3See Note B

CLIN 4012

The option status has changed from No Status to Option.

CLIN 5012

CLIN 6012

CLIN 7012

CLIN 8012

CLIN 9012

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

SECTION C

SECTION C – DESCRIPTIONS/SPECIFICATIONS/WORK STATEMENT

1.0 INTRODUCTION

1.1 SCOPE

This Statement of Work (SOW) sets forth the efforts required for the Guided Missile Frigate (FFG(X)) Combat System (CS) Ship Integration and Test (SI&T), which includes (1) development and assessment of the CS related Test Procedures; to modify and update the CS Master Test Plan (MTP), and to modify and update the CS Test Sequence Network (TSN); (2) review, update and propose modifications to the Shipbuilding Contractor developed FFG(X) CS Space Arrangement, CS Installation Control Drawings, and CS Interface Control Drawings where the initial shipbuilder design negatively impacts the performance, and to develop complete end-to-end FFG(X) CS Interface Control Drawings; (3) perform CS Ship Integration and Test Planning; (4) conduct Waterfront Integration and Test of the FFG(X) CS and Combat System Support Equipment (CSSE) at the system and subsystem levels for all FFG(X) Class Ships; (5) support Government Test Teams in conducting the FFG(X) CS Ship Test and Trials Program to also include Post Delivery Test and Trials (PDT&T) and post-delivery support for new ship construction; (6) personnel management, program management, planning, training, and other efforts required to effectively support the execution of FFG(X) CS SI&T efforts during the ship construction, test and trials, and post-delivery periods; and (7) engineering studies to include feasibility studies as tasked by the Government for possible CS improvements.

CLIN 0001- CS Test Procedures, CS TSN, and CS MTP: The Contractor shall develop, modify, and update the CS Test Procedures in accordance with the Test Stage Matrix and Test Stage Summary Descriptions. The Contractor shall also review, update, and modify the MTP and TSN provided by the Government in accordance with Paragraph 3.4.

CLIN 0002 (1002-9002)- CS Space Arrangement, CS Installation and Interface Control Drawings (As specified in each TI): The Contractor shall review, update, and modify the CS Space Arrangements, CS Installation Drawings, and CS Interface Controls Drawings, which includes CS Topside for all FFG(X) Ships. The Contractor shall also develop, modify, and update complete end-to-end FFG(X) CS Interface Control Drawings in accordance with Paragraph 3.5.

CLIN 0003 (1003-9003)- CS Ship Integration Engineering and Test Planning (As specified in each TI):

The Contractor shall review and analyze CS designs and ensure that the CS Enclave is integrated with the shared boundary interfaces. The Contractor shall also perform CS Test Planning for FFG(X) and assist the Shipbuilder during the CS Ship Installation and Integration in accordance with Paragraph 3.6.

CLIN 0004 (2004-9004)- New Construction CS Waterfront Integration and Test (As specified in each TI): The Contractor shall ensure that the CS is integrated with the ship systems by providing on -site support activities, CS Test Coordination & Conduct, CS Alignment, and CS Engineering and Test Execution in accordance with Paragraph 3.7.

CLIN 0005 (5005-9005)- Post Delivery Test and Trials (PDT&Ts) Support Engineering (As specified in each TI): 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 in accordance with Paragraph 3.8.

CLIN 0006 (1006-9006)- Engineering Services (As specified in each TI): 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 the test documents in accordance with Paragraph 3.9.

CLIN 0007 (1007-9007)- Other Direct Costs (ODCs) and Incidental Materials: This CLIN includes ODCs and Incidental Materials for work performed under CLINs 0001-0006 and associated Option CLINs if exercised in accordance with Paragraph 3.10.

CLIN 0008- Provisioned Item Order (PIO): This CLIN includes PIO to support the efforts under CLINs 0001-0006 and associated Option CLINs if exercised in accordance with Paragraph 3.11.

CLIN 0009- Data (Not Separately Priced): 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 in accordance with Paragraph 3.12.

CLIN 0010- Enhanced Data Rights: Enhanced Data Rights for those items of Commercial and Non-Commercial Technical Data (TD), Computer Software, and Computer Software Documentation (CSD) which the Offeror provided an option price for the Government to exercise and procure greater rights than its list of asserted restrictions. See Paragraph 3.13 Enhanced Data Rights and Attachment J-12 in accordance with Paragraph 3.13.

CLIN 0011- Program Management, Process and Standards, and Performance and Reporting Requirements: The Contractor shall develop program management and performance documents in accordance with Paragraph 3.1.

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

The following documents are applicable to the tasks described herein and are for use by the Contractor as general guidance in the fulfillment of those tasks unless referenced by a TI as required.

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 http://doni.daps.dla.mil/default.aspx

Requests for copies of documents not available from either source should be directed to the Procuring Contracting Officer.

Note: The Contractor shall verify and use the most current version of the document if the current version listed below is found to be an older version.

2.1 MILITARY STANDARDS

Environmental and Type II-Internally Excited)

02 Nov 2005

Control of Electromagnetic Interference (EMI) Characteristics of Subsystems and Equipment

11 Dec 2015

Equipment, and Systems, Requirements for

20 Jun 2017

Tests 15 Apr 2014

Systems 01 Dec 2010

Electromagnetic Compatibility and Safety

12 Aug 2014

MIL-HDBK-1785

NOT 1

* Previous versions of MIL-STD-461 may apply based on system procurement date.

2.2 NAVSEA REGULATIONS, DIRECTIVES, AND INSTRUCTIONS

2.3 DEPARTMENT OF DEFENSE (DOD) STANDARDS/INSTRUCTIONS

2.4 OTHER DOCUMENTS

COMNAVSURFPAC/

COMNAVSURFLANT

TSRA Instruction 4700.1A

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 of this SOW.

The requirements of this SOW are divided between Completion Tasks, and Level of Effort (LOE) Tasks.

The requirements described under paragraphs 3.1 and 3.2, include identification of applicability for the Completion and LOE efforts included in this SOW.

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

3.1.1 PROGRAM MANAGEMENT PLAN (PMP)

(Completion Tasks applicable to CLIN 0001, 0009, and 0011)

The Contractor shall establish and maintain a PM process that ensures all work associated with this SOW is clearly and concisely demonstrated and meets all technical objectives within the Contractor’s established cost and schedule baselines. PM processes shall include appropriate metrics and tracking processes to allow clear visibility into the program and to ensure the program remains within cost and schedule. The Contractor shall designate a Program Manager who will be accountable and responsible for all work conducted within this contract and ensure that all work is planned and executed in a manner that will achieve all management, technical, logistics, budget, and schedule objectives.

The Contractor shall develop a PMP, in accordance with CDRL A001. The PMP shall support the Government schedule requirements in accordance with the CS Support to FFG(X) Notional Ship Schedule, Attachment J-3. The PMP shall demonstrate that the program structure is executable within schedule and cost constraints. The PMP shall correlate with the SOW and Work Breakdown Structure (WBS), Attachment J-4. The PMP shall include, but not 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).

3.1.1.1 UPDATE PROGRAM MANAGEMENT PLAN (PMP)

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 5005- 9005, 0006-9006, and 0009)

The Contractor shall update the PMP for unplanned work as directed by a TI in accordance with CDRL A001.

CDRL A001, Management Plan, Program Management Plan (PMP)

3.1.2 SUBCONTRACTOR/SUPPLIER MANAGEMENT

(Completion Tasks applicable to CLINs 0001 and 0011)

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.2.1 SUBCONTRACTOR/SUPPLIER MANAGEMENT

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 5005- 9005, and 0006-9006)

As directed by a TI, the Contractor shall be responsible for the performance of its subcontractors/suppliers and shall implement appropriate management actions relative to subcontractor/supplier performance for any unplanned work. 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.3 SYSTEM SECURITY PROGRAM

(Completion Tasks applicable to CLIN 0001, 0009, and 0011)

Using the MIL-HDBK-1785 (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 A001 and DoD 5220.22-M and MIL-HDBK-1785 as guidance, and consistent with the FFG(X) Security Classification Guide and all appropriate security instructions.

All Contractor personnel accessing classified information or material associated with this contract must be United States citizens and shall have and maintain at a minimum a final SECRET security clearance at time of contract award.

Contractor requires SIPRNET access to review and transmit classified information related to the FFG(X) 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 to accommodate the use of secure and effective communications with its subcontractors and the Government.

CDRL A001, Management Plan, Program Management Plan (PMP)

3.1.3.1 UPDATE SECURITY MANAGEMENT PLAN (SMP)

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 5005- 9005, 0006-9006, and 0009)

The Contractor shall provide update to the SMP, which is part of the PMP as directed by a TI in accordance with CDRL A001.

CDRL A001, Management Plan, Program Management Plan (PMP)

3.1.4 QUALITY ASSURANCE PROGRAM PLAN (QAPP)

(Completion Tasks applicable to CLINs 0001, 0009, and 0011)

The Contractor shall develop an effective QAPP in accordance with CDRL A003 for supplies and services to include, but not limited to, technical documentation, computer software, and hardware. 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 plan shall include timely review of documents received, noting deficiencies back to the Government in accordance with CDRL A004. The Contractor’s QAPP shall include, but not limited to, the following QA functions, which summarizes some of the key requirements for an acceptable QAPP:

a. The Contractor shall provide and update a quality system, ensuring all data submitted to the Government for acceptance, is technically correct and conforms to contractual requirements. The Contractor shall include statistical process control techniques as an integral part of the quality system, when applicable. The Contractor techniques shall be used as a means of fostering continuous process improvement and to provide information on which to make decisions about corrective action and change procedures. The Contractor shall ensure this requirement is flowed down and applies to data procured from subcontractors or vendors, as well as the data generated or processed by the Contractor.

b. The Contractor shall execute the inspections and tests required to substantiate the quality of the data throughout all areas of contract performance, (e.g., generation, validation, packaging, and delivery).

c. The Contractor's quality system procedures shall be made available for review by the Government before starting data preparation and throughout the life of this contract. The quality system shall be prescribed by clear, complete, and current instructions and include criteria for approval and rejection of data.

d. Contractor personnel performing quality functions shall have well-defined responsibilities, sufficient authority, and the organizational freedom to evaluate data quality and identify problems, and to start, recommend, or direct corrective action.

e. The Contractor's management activity shall review the status and adequacy of the quality system and the quality program regularly to ensure correct technical data is being generated and delivered to the Government.

f. The Contractor's quality program requirements shall ensure compliance with procedures governing the preparation and control of technical data in accordance with the contractual requirements. In addition, the Contractor shall perform management reviews to ensure full compliance with regards to appropriately marking deliverables and non-deliverables.

g. The Contractor shall provide deficiency report submissions in accordance with CDRL A004 on each occurrence of deficiency.

h. The Contractor shall take prompt action to correct conditions that have resulted or could result, in data being submitted to the Government that is not in conformance with contractual requirements. Corrective actions shall include:

1. Review of existing records indicating the types and number of inspections made, the types and number of deficiencies found, items of data rejected, the corrective actions taken, and the quantities of data items approved.

2. Review and revise, where necessary, existing procedures for conducting future or follow-up corrective actions. These revised procedures shall monitor and increase the effectiveness of corrective actions to prevent the recurrence of discrepancies.

CDRL A003, Quality Assurance Program Plan (QAPP) CDRL A004, Government Furnished Information (GFI) Deficiency Report, Document Deficiency Report

3.1.4.1 UPDATE QAPP

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 5005- 9005, 0006-9006, and 0009)

The Contractor shall update the QAPP an accordance with CDRL A003 as directed by a TI.

CDRL A003, Quality Assurance Program Plan (QAPP)

3.1.5 CYBERSECURITY

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004-9004, 0006-9006, and 0009)

This will be performed as directed by a TI.

The Contractor shall conduct Cybersecurity tests in accordance with the CS Test Procedures generated per the CS Test Stage Matrix as listed in Attachment J-10. All tests shall comply with all current DoD Cybersecurity directives, instructions, and National Institute of Standards and Technology (NIST) Special Publications listed in Section 2.0. The Contractor shall integrate, test capabilities, and provide proper support equipment and conduct Cybersecurity testing to obtain and maintain Cybersecurity accreditation for the CS Enclave in accordance with the Cybersecurity Checklist, Attachment J-5. The CS Enclave is defined as the entire CS and all of its contents to include the CS boundary defense capabilities, networks, CMS, all CS elements, sub-components, and inter-connections. After conducting the tests, the Contractor shall provide a report of recommended actions including maintaining, updating, scanning, and patching the CS Enclave. The report shall be prepared in accordance with CDRL A027. Additionally, the Contractor shall ensure Cybersecurity Capabilities in the CS Enclave meet the required CS certification in accordance with CNSSI 1253, NIST SP 800-53 Rev 4, and NIST SP 800-53A Rev. 4.

The Contractor shall integrate enclave assessment and authorization events into the IMS and CS MTP. Also, the Contractor shall ensure Cross Domain Solution (CDS) is included in the CS MTP and CS Test Procedures. Further, the Contractor shall also follow DoDI 8500.01, Cybersecurity, DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), NAVSEA 9400.2-AM, business rules set by the NAVSEA Echelon II and the Functional Authorizing Official (FAO), and Cybersecurity Checklist, Attachment J-5.

CDRL A027, Naval Aviation Cybersecurity Test Report, CS SI&T Cybersecurity Test Report

3.1.5.1 CONDUCTING CYBERSECURITY TESTING

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004-9004, 0006-9006, and 0009)

This will be performed as directed by a TI.

The Contractor shall plan and conduct Cybersecurity testing in the presence of a Government witness as directed by the COR to show conformance to Security Controls and Capabilities per the FFG(X) CS Enclave Cybersecurity Integration and Test Procedures. The Contractor shall obtain validation of the tests and report from the Government and perform the tasks identified in the Cybersecurity Checklist. The Contractor shall notify the Government within sixty (60) calendar days prior to a Cybersecurity Test Event and make accommodations for the Government to witness Cybersecurity testing.

The Contractor shall deliver a Cybersecurity Test Report after the completion of the Cybersecurity Testing in accordance with CDRL A027. The report shall demonstrate compliance with the Cybersecurity Integration and Test Procedures and report on the status and findings of the events and procedures listed in the Cybersecurity Test Plan.

CDRL A027, Naval Aviation Cybersecurity Test Report, CS SI&T Cybersecurity Test Report

3.1.5.1.1 DEVELOPMENT OF CYBERSECURITY TEST PLAN

(Completion Tasks applicable to CLIN 0001, 0009, and 0011)

The Contractor shall develop a Cybersecurity Test Plan, in accordance with CDRL A028. The test events portion described in this plan shall be included in the MTP as well. The Cybersecurity Test Plan shall be detailed in order to generate repeatable test results using identical test configurations, test conditions, and tools. The Cybersecurity Test Plan shall specify personnel responsibilities, testing schedules, and required resources to facilitate all Cybersecurity test events.

CDRL A028, Naval Aviation Cybersecurity Test Plan, CS SI&T Cybersecurity Test Plan

3.1.5.1.1.1 UPDATE CYBERSECURITY TEST PLAN

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004-9004, 0006-9006, and 0009)

The Contractor shall update the Cybersecurity Test Plan as directed by a TI.

CDRL A028, Naval Aviation Cybersecurity Test Plan, CS SI&T Cybersecurity Test Plan

3.1.5.1.2 CYBERSECURITY PRE-SOFTWARE INSTALLATION TASKS

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004-9004, and 0006-9006)

This will be performed as directed by a TI.

The Contractor shall, prior to software installation and integration and testing, verify that the placement of host and physical items conforms to CS Space Arrangement drawings, verify that all host and network devices are properly connected, and are able to successfully boot to an operational status. The Contractor shall also verify that proper software and hardware has been received in accordance with DD Form 1149 and verify that the hardware and software has received Authorization to Operate (ATO), or Interim Authorization to Operate (IATO), or Interim Authorization to Test (IATT) from the Navy Authorizing Official (NAO) at Fleet Cyber Command.

Additionally, the Contractor shall verify that system license keys/serial numbers/product keys have been provided to the Site License Allocation Spreadsheet located in the Integrated Logistics Support (ILS) package.

3.1.5.1.3 SOFTWARE LOAD VERIFICATION

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004-9004, and 0006-9006)

This will be performed as directed by a TI.

The Contractor shall, during Software Load Verification, provide a report that verifies the system has an active connection to a Host Based Security System (HBSS) and verify that HBSS agents are installed and security suite is running properly. The Contractor shall also verify that the systems within the CS Enclave are communicating with an enclave-level Assured Compliance Assessment Solution (ACAS) Security Center (SC), conduct ACAS scans to ensure that system is up to date on all software, firmware, and patches, and verify that it has the capability to export and deliver the results of scans. Additionally, the Contractor shall verify that appropriate workstations have the most current patches installed, are properly configured in accordance with Defense Information Systems Agency (DISA), Security Technical Implementation Guides (STIG) requirements, and verify that ship’s force is able to initiate and complete periodic scans of the network from the appropriate Security Center.

3.1.5.1.4 SYSTEM FUNCTIONAL TESTS

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004-9004, and 0006-9006)

This will be performed as directed by a TI.

During the System Functional Test, the Contractor shall perform a Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) port scan of the entire CS Enclave to identify all hosts with TCP & UDP services are running or in a listening state and to identify any unnecessary open ports or running services. The Contractor shall also perform an Operating System Detection and Stack Fingerprinting test, and perform the following verifications and validations:

1. Verify all Public Key Infrastructure (PKI) enabled hosts are configured to operating system requirements and functionality.

2. Verify all network device ports are configured to operational system requirements (i.e., sticky MAC learning, port limitations).

3. Verify all Access Control Lists (ACLs) are present and configured for operation.

4. Verify all devices, ports, and connections meet light-off test requirements and can be configured per System Operation Manual settings.

5. Verify all network devices pass a Pre-Installation Test and Check Out (PITCO).

6. Verify the network devices are configured with the appropriate approved OS/firmware versions.

7. Verify the routing protocols are configured properly for all network routers to ensure bidirectional connectivity.

8. Verify the routing protocol configurations do not use clear text for authentication.

9. Verify all network devices communicate over an authenticated channel.

10. Verify network connectivity for all network devices and endpoints.

11. Verify the Enterprise Storage Solution functionality for critical storage devices and components meet Program and DoD Requirements.

12. Verify all applicable enclave-level system connectivity with external interfaces.

13. Validate all operational modes, controls, expected outputs, and other system requirements are functional.

14. Verify proper firewall setup to block different threats (i.e., Denial of Service (DOS), distributed DOS, and application/port exploits) in accordance with DISA STIGs.

15. Verify the firewall blocks unauthorized remote access.

3.1.5.2 VERIFICATION SCANNING

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004-9004, 0006-9006, and 0009)

This will be performed as directed by a TI.

The Contractor shall scan the CS Enclave for software and hardware verification. The Contractor shall perform these scans in pairs. The first is after installation and the second is after completion of installation and integration testing. The Contractor shall repeat both scans only if the software for the CS changed or updated. The Contractor shall report these findings in a Cybersecurity Test Report, CDRL A027.

CDRL A027, Naval Aviation Cybersecurity Test Report, CS SI&T Cybersecurity Test Report

3.1.5.3 VERIFICATION OF NETWORKS AND CYBERSECURITY ITEMS

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004-9004, 0006-9006, and 0009)

This will be performed as directed by a TI.

The Contractor shall perform all the checks and verifications as listed in the Networks and Cybersecurity Checklist, Attachment J-5, in the presence of a Government representative, which will serve as a witness. The Contractor shall execute STIGs and SRGs (Security Requirements Guides). The Contractor shall document all findings, results, and STIGs in a Cybersecurity Test Report, CDRL A027.

CDRL A027, Naval Aviation Cybersecurity Test Report, CS SI&T Cybersecurity Test Report

3.1.5.4 CYBERSAFE VALIDATION TESTING

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004-9004, and 0006-9006)

This will be performed as directed by a TI.

The Contractor shall conduct CyberSafe testing to ensure that the CS Enclave is compliant with CyberSafe requirements. The CyberSafe testing shall be done in accordance with CyberSafe OPNAV INST 5239.22, SECNAV INST 5239.22, DoD and DoN policies and procedures, and the Cybersecurity Checklist. The CyberSafe testing results shall be included in the Cybersecurity Test Report.

3.1.6 ENVIRONMENTAL SAFETY AND OCUPATIONAL HEALTH (ESOH)

The Contractor shall execute an ESOH Program and deliver reports as described in the subparagraphs below.

3.1.6.1 SAFETY AND OCCUPATIONAL HEALTH

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004 -9004, 0006-9006, and 0009)

This will be performed as directed by a TI.

The Contractor shall identify and evaluate safety and personnel health hazards, define risk levels, and establish a safety program in accordance with MIL-STD-882 that manages the probability and severity of all hazards associated with integration testing, use, and maintenance of the FFG(X) CS equipment. The Contractor shall also identify and evaluate personnel’s health and equipment hazards, define risk levels, and establish mitigations through safety analysis and regulatory requirement evaluations. Further, the Contractor shall ensure that appropriate modifications (if necessary) are carried out in the CS equipment procedures and test activities to manage the probability and severity of all hazards, and maintain continual compliance with ESOH requirements. The Health Hazard Assessment Report (HHAR) shall be developed and delivered by the Contractor in accordance with CDRL A005.

CDRL A005, Health Hazard Assessment Report (HHAR)

3.1.6.2 HAZARDOUS MATERIAL (HAZMAT)

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004 -9004, 0006-9006, and 0009)

This will be performed as directed by a TI.

The Contractor, specifically for SI&T requirements, shall evaluate and manage the selection, use, and disposal of HAZMAT consistent with ESOH regulatory requirements and program cost, schedule, and performance goals. The Contractor shall develop and implement plans and procedures for life cycle identification, tracking, storing, handling, packaging, transporting, and disposing of such material if needed for SI&T and where avoidance of HAZMAT is unreasonably expensive or unavoidable in accordance with CDRL A006, Hazardous Material Management Program (HMMP) Plan.

The Contractor shall comply with all environmental protection measures identified in Environmental Planning documentation during tests and ensure that testing is conducted in compliance with applicable Federal, State, and Local Environmental and Safety Statutes, Laws, Regulations and facility permitting requirements.

CDRL A006, Hazardous Material Management Program (HMMP) Plan

3.2 PROCESSES AND STANDARDS

3.2.1 DATA MANAGEMENT AND INTEGRATED DATA ENVIRONMENT (IDE)

(Completion Tasks applicable to 0001, 0009, and 0011)

The Contractor shall implement a Data Management Program utilizing two separate Integrated IDE structures. One of the structures is the Contractor IDE; this shall be established and implemented with both unclassified and classified IDE portals. This IDE (both classified and unclassified) 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 work week.

The other structure is the Government IDE and it will be via the Government provided unclassified Integrated Product Data Management (iPDM). This Government IDE (iPDM) shall be the formal delivery method for all CDRL deliverables.

The purpose of the IDE environment is to create a seamless, collaborative data environment for the Contractor and Government team which contains all pertinent 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 (CDRL A001).

The Contractor shall provide the Government team access to all data listed in the Data Accession List (DAL) by actively using the Contractor IDE. All items posted to the Contractor IDE, such as drafts of deliverables that are not final versions, shall be considered as drafts until formally posted into the iPDM. Once final, data deliveries are posted to iPDM and shall be considered delivered for the purposes of meeting the CDRL requirements. 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 DAL shall contain the list of all data generated in support of this contract and be prepared in accordance with the DAL (CDRL A007). The Government reserves the right to witness all Contractor efforts to accomplish the SOW requirements and maintains the right to comment on the processes.

All 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-11, 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 Integrated Product Teams (IPT).

CDRL A001, Management Plan, Program Management Plan (PMP) CDRL A007, Data Accession List (DAL)

3.2.1.1 DATA MANAGEMENT AND INTEGRATED DATA ENVIRONMENT (IDE)

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 5005- 9005, 0006-9006, 0009, 0010)

The Contractor shall implement a Data Management Program utilizing two separate Integrated IDE structures in accordance with paragraph 3.2.1 above as directed by a TI.

CDRL A001, Management Plan, Program Management Plan (PMP) CDRL A007, Data Accession List (DAL)

3.2.2 CONFIGURATION MANAGEMENT (CM)

(Completion Tasks applicable to CLINs 0001, 0009 and 0011)

For all CS upgrades within the new construction funding window, the Contractor shall provide and maintain a Configuration Management Program Plan in accordance with CDRL A026 based on existing approved plans of the current PEO IWS 8.0 Configuration Management Plan (CMP) provided in Attachment J-6. The Contractor shall participate and serve as a third-party to Configuration Control Boards (CCBs).

CDRL A026, Configuration Management Program Plan

3.2.2.1 UPDATE CM PROGRAM PLAN

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 0006-9006, and 0009)

The Contractor shall update to the CM Program Plan in accordance with CDRL A026 as directed by a TI.

CDRL A026, Configuration Management Program Plan

3.2.2.2 CONFIGURATION MANAGEMENT (CM) SUPPORT

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 0006-9006, and 0009)

This will be performed as directed by a TI.

The CM program shall support the shipboard installation, integration, and test of equipment comprising the Combat System for FFG(X) Class ships.

The Contractor shall maintain configuration status records that identify approved Engineering Change Proposals (ECPs) (CDRL A008), Specification Change Notices (SCNs) (CDRL A009), 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 also the following:

a. 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.

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

c. Participate in all CCB meetings.

CDRL A008, Engineering Change Proposal CDRL A009, Specification Change Notice

3.2.2.3 CONFIGURATION DEFINITION DOCUMENTS

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 0006-9006, and 0009)

The Contractor shall provide a CS Baseline Definition Document, Configuration Identification Baseline Report for this baseline development in accordance with CDRL A010 as directed by a TI.

CDRL A010, Baseline Description Document, Configuration Identification Baseline Report

3.2.2.4 SOFTWARE CONFIGURATION MANAGEMENT AND CONTROL SUPPORT

(LOE Tasks applicable to CLINs to include Options if exercised, 0003-9003, 2004 -9004, 0006-9006, and 0009)

This will be performed as directed by a TI.

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

The Contractor shall provide Test Observation Reports (TORs) in accordance with CDRL A011 to document the discrepancies found during the testing and validation efforts. The Contractor shall also provide recommendations to the Government in support of software change request development for valid TORs in accordance with the classification in Attachment J-7. The Contractor shall 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 change requests and TOR data in accordance with the designated classification level imposed by the Government classification guidance.

The Contractor shall provide recommendations for ECPs and developed in accordance with CDRL A008 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 A012. 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.

CDRL A008, Engineering Change Proposal (ECP) CDRL A011, Scientific and Technical Reports, TORs CDRL A012, Revision to Existing Government Documents

3.3 CONTRACT PERFORMANCE AND REPORTING REQUIREMENTS

3.3.1 PROGRAM AND TECHNICAL REVIEWS

3.3.1.1 KICK-OFF MEETING

3.3.1.1.1 POST AWARD KICK-OFF MEETING

(Completion Tasks applicable to CLINs 0001, 0009, and 0011)

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-8, and related Resource Distribution Table (RDT), Attachment J-9. The Government and the Contractor shall work together to develop or update charters for IPT, as required. The Contractor shall prepare an agenda, meeting minutes, and presentation materials in support of the meetings in accordance with CDRLs A013, A014 and A015 respectively.

CDRL A013, Conference Agenda CDRL A014, Report, Record of Meetings/Minutes CDRL A015, Presentation Material

3.3.1.1.2 TECHNICAL INSTRUCTION KICK-OFF MEETING

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 5005- 9005, 0006-9006, and 0009)

This will be performed as directed by a TI.

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 A013, A014 and A015 respectively.

CDRL A013, Conference Agenda CDRL A014, Report, Record of Meetings/Minutes CDRL A015, Presentation Material

3.3.1.2 QUARTERLY PROGRAM MANAGEMENT REVIEWS:

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 5005- 9005, 0006-9006, and 0009)

This will be performed as directed by a TI.

The Contractor shall conduct quarterly Program Management Reviews (PMRs), which may be conducted via a virtual collaborative environment or other Government-approved means. The PMR shall be documented with agendas, minutes, and presentation materials in accordance with CDRLs A013, A014 and A015 respectively. The PMR shall include, 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 evaluate 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 A013, Conference Agenda CDRL A014, Report, Record of Meetings/Minutes CDRL A015, Presentation Material

3.3.1.3 RISK MANAGEMENT

(Completion Tasks applicable to CLINs 0001, 0009, and 0011)

The Contractor shall provide a Risk Management Plan in accordance with CDRL A016 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.

CDRL A016, Contractor’s Risk Management Plan

3.3.1.3.1 UPDATE RISK MANAGEMENT PLAN

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 0006-9006, and 0009)

The Contractor shall update the Risk Management Plan in accordance with CDRL A016 as directed by a TI.

CDRL A016, Contractor’s Risk Management Plan

3.3.2 BUSINESS AND FINANCIAL MANAGEMENT

(Completion Tasks applicable to CLINs 0001, 0009 and 0011)

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 IPMR to include the 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 A021. 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 A017.

CDRL A017, Contractor’s Progress, Status, And Management Report CDRL A021, Contract Funds Status Report (CFSR)

3.3.2.1 BUSINESS AND FINANCIAL MANAGEMENT

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 5005- 9005, 0006-9006, 0007-9007, 0008, and 0009)

The Contractor shall establish, maintain, and use in the performance of this contract, a cost management system in accordance with Paragraph 3.3.2 above as directed by a TI.

3.3.2.2 CONTRACT WORK BREAKDOWN STRUCTURE (CWBS)

(Completion Tasks applicable to CLINs 0001, 0009, and 0011)

The Contractor shall generate a CWBS in accordance with CDRL A018 and shall be consistent with DoD Manual 5000.04-M-1, CSDR Manual and MIL-STD-881C, Department of Defense Standard, WBS for Defense Material Items. In addition, the Contractor shall develop the CWBS in accordance with the Government WBS, Attachment J-4. The Contractor shall update the CWBS to accommodate changes to the program as applicable. All revisions to the CWBS shall require approval of the Government prior to implementation. The Contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, performance, and technical performance status to the Government.

CDRL A018, Contract Work Breakdown Structure (CWBS)

3.3.2.2.1 CONTRACT WORK BREAKDOWN STRUCTURE (CWBS)

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 5005- 9005, 0006-9006, 0007-9007, 0008, and 0009)

The Contractor shall generate a CWBS in accordance with Paragraph 3.3.2.2 above as directed by a TI.

3.3.2.3 INTEGRATED PROGRAM MANAGEMENT REPORT (IPMR)

(Completion Tasks applicable to CLINs 0001, 0009, and 0011)

The Contractor shall deliver an IPMR to the Government in accordance with CDRL A002. The IPMR presents 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.

The Contractor shall also deliver a tailored IPMR and provide financial status and comply only with IPMR Formats one (1), three (3), four (4), five (5), and six (6) in accordance with CDRL A022 to measure cost and schedule performance. Each specific TI will indicate the appropriate format applicable, but EVMS will not apply to any of the LOE CLINs.

CDRL A002, Integrated Program Management Report (IPMR) CDRL A022, Integrated Program Management Report (IPMR), Tailored IPMR

3.3.2.3.1 INTEGRATED PROGRAM MANAGEMENT REPORT (IPMR)

(LOE Tasks applicable to CLINs to include Options if exercised, 0002-9002, 0003-9003, 2004 -9004, 5005- 9005, 0006-9006, 0007-9007, 0008, and 0009)

The Contractor shall deliver an IPMR…