Attachment 4 SOW.pdf

v4.2_FEBRUARY2025

STATEMENT OF WORK (SOW)/PERFORMANCE WORK STATEMENT (PWS)

Data Processing Subsystem In Service Engineering

1.0 Background

The Naval Undersea Warfare Center (NUWC) Division, Newport (NUWCDIVNPT) Code 2522 is assigned by Naval Sea Systems Command (NAVSEA) to provide Ohio Class Submarine Command and Control System/Non- Propulsion Electronics System /Data Processing Subsystem (CCS/NPES/DPS) Level III Engineering. Level III Engineering includes assisting NAVSEA and the Ohio Class Submarine CCS/NPES/DPS system engineers with the responsibility, authority, and accountability for the direction, control, and decisions inherent in the planning, programming, budgeting, design, development, engineering, and implementation of the Ohio Class Submarine CCS/NPES/DPS Program.

1.1 Places of Performance

Naval Undersea Warfare Center Newport, Puget Sound Naval Shipyard, Naval Submarine Base Bangor, Naval Submarine Base King's Bay, OHIO Class Submarines (SSBN/SSGN)

1.2 Authorized Users

-NUWC Code 2522, 259, 2524

1.3 Sponsors

-PMS 396

1.4 Types of Funding

-OMN, OPN

2.0 Scope

The Contractor shall provide technical engineering services and subsystem level life cycle maintenance responsibilities for the OHIO Class CCS/DPS/NPES in support of NUWC Code 2522. The Contractor shall provide technical product-oriented services pertaining to the engineering, analysis, testing, and evaluation of operational OHIO Class submarines and shore sites that perform training, refit, and maintenance activities. Operational OHIO Class submarines shall include all SSGNs platforms and any applicable SSBN platform. The tasking performed shall be in accordance with (IAW) the Applicable Documents listed in Section 3. using Government Furnished Information (GFI) identified in Section 5.

Travel locations include NUWC Newport, Rhode Island, and may include the submarine bases in Bangor, Washington and King’s Bay, Georgia.

Tasking and deliverables shall be in accordance with requirements defined in Section 4.

2.1 Program or Systems Supported

-Strategic Submarine SSBN/SSGN, DPS

3.0 Applicable Documents

The contractor shall perform the tasking required in Section 4.0 in accordance with (IAW) the below Applicable Documents (ADs).

NUMBER TITLE

3.1 MIL-STD-1397B Input/Output Interfaces, Standard Digital Data, Navy Systems

3.2 MIL-STD-52779A Software Quality Assurance Program Requirement

3.3 IEEE/EIA/ISO 12207.0 Standard for Information Technology – Software Life Cycle Processes

3.4 0900-074-4010 Interface Design Specification for the Trident Submarine Ohio Class Command and Control System Common Requirements for Inter-subsystem Computer Program Interfaces CCS Specification

3.5 T9410-D1-SPN-010 System Specification for the Trident Submarine Ohio Class Command and Control System Functional & Allocated Requirements Specification

3.6 TE687-AX-PPS-H10 Ohio Class Guided Missile Submarine Non- Propulsion Electronics System Data Processing Subsystem Mission Critical Workstation Software Requirements Specification

3.7 T9410-GB-PLN-010 Ohio Class (SSBN/SSGN) Command and Control System and Non-Propulsion Electronics System Configuration Management Plan

3.8 TE687-BY-SCM-0100 Trident Submarine Ohio Class Command and Control System Software Delivery Requirements

3.9 T9410-AB-PRO-010/020 Trident CCS Problem Reporting System (TCPRS) Procedures and Program Plan, Volumes 1 and 2

3.10 T9401-BU-PRO-010 Trident CCS Modification (TCMOD) System Procedures and Plan

3.11 T9410-GB-PRO-010 OHIO Class (SSBN/SSGN) Command and Control System (CCS) and Non-Propulsion Electronics System (NPES) Modification Development Standard Operating Procedure

(SOP)

3.12 T9410-AX-CCD-010 SSBN 726 Class Submarine CCS Boundary Definition Document

3.13 TE687-BX-PRO-010/CMPA Trident Submarine Ohio Class Command and Control System (CCS) Computer Program Configuration Management / Product Assurance (CM/PA) Procedures

3.14 N/A DON Information Security Program Regulation SECNAVINST 5510.36

3.15 TE687-BN-PLN-M10 OHIO Class Guided Missile Submarine (SSGN) Non- Propulsion Electronics System (NPES) Software Development Plan for the Data Processing Subsystem (DPS) Mission Critical Workstation (MCW)

3.16 SE610-NV-MMO-A10 Technical Manual Operation and Maintenance Instructions for Computer Set AN/UYK-43(V)

3.17 TE687-EZ-MMO-010 Technical Manual for Submarine Workstation (OL-651(P)) Description, Operation, and Maintenance

3.18 TE687-C9-OMI-J10 Interactive Electronic Technical Manual For AN/UYQ-70(V) Data Processing System (DPS) Multi-Function Server (MFS) Description, Operation, And Maintenance

3.19 N/A Information Assurance Vulnerability Technical Advisory (IAVA) Assessment Process

3.20 TE687-AX-PPS-H10 OHIO Class Guided Missile Submarine (SSGN) Non- Propulsion Electronics System (NPES) Data Processing Subsystem (DPS) Mission Critical Workstation (MCW) Software Requirements Specification (SRS)

3.21 TE687-AX-SUM-H10 OHIO Class Guided Missile Submarine (SSGN) Non- Propulsion Electronics System (NPES) Data Processing Subsystem (DPS) Mission Critical Workstation (MCW) Software User’s Manual (SUM)

4.0 Technical Requirements

The following tasks shall be accomplished by the Contractor using the Government Furnished Information in Section 5. in accordance with the Applicable Documents in Section 3. All tasks shall be performed within the scope of this Statement of Work.

4.1 Operational Life Cycle Support Maintenance (SSGN/SSBN Hardware, SSGN/SSBN Software & SSGN/SSBN Documentation)

In accordance with Applicable Documents 3.2, 3.3, 3.6, 3.7, 3.9, 3.15 and using GFI 6.7, 6.8 and 6.9, the Contractor shall provide technical product-oriented engineering services pertaining to the engineering, analysis, testing and life cycle maintenance responsibilities for the Data Processing Subsystem (DPS), and the OHIO Class Non-Propulsion Electronics System (NPES) [OMN].

In accordance with Applicable Documents 3.1, 3.16, 3.17, and 3.18 and using GFI 6.8 and 6.11, the Contractor shall repair equipment located at TRIDENT Trainer Facilities located at Kings Bay, Georgia and Bangor, Washington when requested. [OMN]

In accordance with Applicable Documents 3.7, 3.10, and 3.11 and using GFI 6.2, 6.5, and 6.6, the Contractor shall perform Non-Propulsion Electronics System (NPES) Operational Verification and Evaluation (NOVE) tests onboard SSBN and SSGN. [OPN]

In accordance with Applicable Documents 3.2, 3.3, and 3.8, the Contractor shall develop Data Processing Subsystem (DPS) software, as required, based on Fleet requirements.

[OMN]

4.2 Revision Development and Advanced Planning

In accordance with Applicable Documents 3.3 through 3.6, 3.15 and using GFI 6.1, 6.2, 6.5,

6.6 and 6.8, the Contractor shall review and assess potential DPS shipboard and shore-based hardware and/or software impacts associated with proposed CCS/NPES upgrades and prepare and provide an implementation approach white paper for any alteration impacting DPS shipboard and shore-based software or hardware products. [OPN]

In accordance with Applicable Documents 3.3 and 3.15 and using GFI 6.1 and 6.2, the Contractor shall conduct formal DPS assessment testing for a proposed software revision.

The contractor shall prepare and deliver formal daily test reports and a final DPS Verification Testing (DVT) Report. [OMN]

In accordance with Applicable Documents 3.11, 3.13 and using GFI 6.1, 6.2, 6.4 and 6.8 the Contractor shall install the government approved DPS product(s) on SSGN hulls and at land-based facilities as requested. Installation shall include a technical test report that details all associated activities. [OMN]

In accordance with Applicable Documents 3.11 and 3.13 and using GFI 6.1,6.2, 6.4 and 6.8, the Contractor shall conduct testing of the government approved DPS product(s) on SSGN hulls and at land-based facilities as requested. Testing shall include a technical test report that details all associated activities. [OMN]

If requested, using GFI 6.1, 6.10, and 6.11 the Contractor shall participate in; Ohio Class Modernization Platform Integration Team (PIT) meetings, technical briefings and coordination briefing, and working group meetings representing the DPS. [OMN]

Deliverable(s):

Technical Report-Study/Services CDRL A001 Acceptance Test Report CDRL A002

5.0 Progress Reports

The contractor shall submit Monthly Progress and Financial Reports. These reports shall document the technical and financial status and may be submitted in the contractor’s format.

Deliverable(s):

Contract Status Report CDRL A003

5.2 Training

None

6.0 Government Furnished Information

6.1 Ohio Class Alteration Status Report

6.2 Ohio Class NPES Modernization Schedule

6.3 TRIDENT SSBN/SSGN System Engineering Calendar

6.4 TRIDENT Life Cycle Support Facility 12-Month Planning Schedule

6.5 CCS/NPES Alteration Documentation (e.g. TEMPALT, SHIPALT)

6.6 CCS/NPES Change Documentation (e.g., ECI, TECI, EC, BCR)

6.7 Patrol reports & naval messages

6.8 Letters/e-mails from the sites

6.9 LCSF test reports

6.10 Meeting announcements/emails

6.11 NUWC Fiscal Year (FY) DPS Overhaul Individual Task Planning Sheet (ITPS)

7.0 Government Furnished Property

None

8.0 Quality Surveillance and Performance Standards

The Government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, review of monthly progress reports, and review of deliverables.

9.0 Information and Communication Technology (ICT) Accessibility Requirements

The Government has determined that this procurement is an exception to the Information and Communication Technology (ICT) Accessibility Standards (36 C.F.R. Part 1194, Appendix A).

Notwithstanding that an exception exists, the Contractor may furnish items or services provided under this contract that comply with the ICT Accessibility Standards (36 C.F.R. Part 1194, Appendix A).

Exception #1 national security for (Strategic Submarine SSBN/SSGN)

10.0 Security Compliance

10.1 Program Protection

SECURITY: All Contractor personnel shall adhere to the Security provisions of 32 CFR Part 117

– National Industrial Security Program Operating Manual (NISPOM) and the security requirements of the attached DD254. While performing work at a Government Facility, Contractor personnel shall comply with the security regulations of the host facility. Applicable FAR, DFARS, NMCARS clauses, and NAVSEA text shall be adhered to in the performance of this contract. Security incidents shall be promptly reported through the companies Facility Security Officer (FSO), to the Contracting Officer’s Representative (COR), Technical Point of Contact (TPOC), and the Cognizant Security Office to NUWCDIVNPT Security.

NATO

NATO is required for the contractor to perform task(s) 4.1, 4.2. SIPRNET includes NATO information.

SIPRNET

SIPRNET is required for the contractor to perform task(s) 4.[X]]. [insert unclassified justification for access].

10.2 Operations Security (OPSEC)

OPSEC is a process that identifies critical information to determine if friendly actions can be observed by adversary intelligence systems, determines if information obtained by adversaries could be interpreted to be useful to them, and then executes selected measures that eliminate or reduce adversary exploitation of friendly critical information.

The Contractor shall develop and implement, and update and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the Contractor and any subcontractor during performance of the contract.

The Contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. The Contractor developed OPSEC program may include Information Assurance and Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security Presidential Memorandum (NSPM) 28, and at a minimum shall include:

1) Assignment of responsibility for OPSEC direction and implementation.

2) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

3) Establishment of OPSEC education and awareness training.

4) Provisions for management, annual review, and evaluation of OPSEC programs.

5) Flow down of OPSEC requirements to subcontractors when applicable.

While performing aboard Government sites, the contractor shall: comply with all OPSEC instructions and policies; include OPSEC as part of its ongoing security awareness program and take all required Agency training; Be responsive to the Supporting OPSEC Manager on a non-interference basis; and Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the Requiring Organization and contractor in support of the mission.

10.3 Electronic Spillage

Electronic Spillage (ES) is defined as a situation where information of higher classification than a system is authorized to process is introduced into that system, intentionally or otherwise. If a Contractor is determined to be responsible for an ES, all direct and indirect costs incurred by the Government for ES remediation will be charged to the Contractor.