CUI_PCS_SOW.docx

v4.7_OCTOBER2025

STATEMENT OF WORK (SOW)

Submarine Portable Launch System

1.0 Background

The Submarine Combat and Weapons Control Program Office (PMS 425) is the acquisition lead for the Submarine Combat Control System (CCS) and Submarine Launcher programs. The Program Management Office (PMO) is responsible for the design, testing and fielding of these systems across all variants of United States Navy (USN) submarines. Naval Undersea Warfare Center, Division Newport (NUWCDIVNPT) Code 25 supports PMS425 as the Submarine CCS Technical Direction Agent (TDA), In-Service Engineering Agent (ISEA) and Installation lead, and has been in this role for decades starting with AN/BYG-1 predecessor programs including the MK 117 and 118 Fire Control Systems (FCS), Combat Control System (CCS) MK I and CCS MK2 systems. These roles involve tasking inclusive of prototyping hardware and software for future payload integration into the CCS and Launchers, executing land based and at-sea testing of future concepts and production baselines, executing systems engineering activities, test & evaluation activities and fielding and sustainment of these systems.

This contract will focus on modifying the payload control system (PCS) technology to adapt the CCS to new payload interfaces planned for submarine introduction. Code 25 is the Subject Matter Expert (SME) for the CCS and launcher interfaces and with this Small Business Innovation Research (SBIR) technology will have the capability to execute the future prototyping tasking being requested by the PMO and various payload sponsors to accelerate program of record capability integration and fleet fielding.

Code 25 requires the evolutionary development of the PCS technology to address new capabilities on the horizon for integration into the submarine CCS. The technology needs to be modified to work with the newest modernizations of the tactical PCS baselines. These baselines are established as part of the Advance Processor Build (APB) process. Every two years, a PCS baseline with new and improved capabilities is released to the Fleet. Implementation of these capabilities affects underlying software architecture and infrastructure. The PCS technology is built on this architecture and accordingly needs to be modified in order to enable payload integration prototypes.

1.1 Places of Performance

NUWCDIVNPT, Newport, RI and Contractor facility at Middletown, RI

1.2 Authorized Users

NUWCDIVNPT Codes 25, 34, 45, and 85 are authorized to place task orders on this contract.

1.3 Sponsors

The Government anticipates that the following sponsors will fund task orders on this contract: PMS 351, PMS 394, PMS 397, PMS 404, PMS 406, PMS 415, PMS 425, PMS 450, Commonwealth of Australia, PEO-SUB International, SP-C, SP04, Strategic Capabilities Office (SCO), Office of Naval Research (ONR), PMA201, PMA280, PMA281, AUKUS A&I, IWS-3, and PMW 770.

1.4 Types of Funding

The Government anticipates that the following types of money will be used to fund task orders on this contract: Research, Development, Test and Evaluation (RDT&E); Special Deposits (SPDP); Other Procurement, Navy (OPN); Weapons Procurement, Navy (WPN); Operation & Maintenance, Navy (O&MN); Foreign Military Sales (FMS); Ship Construction and Conversion, Navy (SCN); National Sea-Based Deterrence Fund (NSBDF); and NUWCDIVNPT Overhead (OH).

2.0 Scope

The contractor shall perform architecture development, interface specification development and modification, prototype development, software/hardware integration and testing, capstone demonstration to further develop PCS Technology and CSA-PI Data Interface (CDI) software to enable payload integration prototypes, and early platform installation, test, and analysis efforts to validate technology advancements.

2.1 Program or Systems Supported

The scope of the effort includes modifications of AN/BYG-1 and CDI software, for:

(a) Each Advanced Processor Build (APB),

(b) Each Technical Insertion Hardware (TIH),

(c) The payloads being integrated with PCS,

(d) The payloads integrating with PCS interface protocols, and

(e) The payloads integrating with the Non-Propulsion Electronic Systems (NPES)

3.0 Applicable Documents

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

Assurance Workforce Improvement Program Change 4, 10 November 4.7

Division Newport Critical Information and Indicators List

(CIIL)

4.0 Technical Requirements

The following tasks shall be accomplished in accordance with Government Specifications and Standards in Section 3.0. The Contractor shall perform tasks using Government Furnished Information (GFI) identified in Section 6.0. Specific requirements will be identified in the task order statements of work.

4.1 Concept of Operations (CONOPS) and Top-Level Requirement (TLR) Development

Upon receipt of a task order, the contractor shall modify existing payload mission CONOPs, provided as GFI, to capture performance characteristics and limitations of the payload that is planned for integration. In the CONOPs, the contractor shall identify requirements for targeting, pre-launch, launch, and post-launch, as well as potential impacts to safety, security, and data classification and retention, on the representative combat system and platform identified in the task order. The contractor shall attend payload systems engineering working group meetings to gather information regarding design and CONOPs constraints.

Deliverable: The contractor shall deliver revised CONOPs in accordance with CDRL A001 (DI-ADMN-80925A).

Upon Government approval of the CONOPs, the contractor shall recommend TLRs for capabilities of new payloads and submarine variants interfacing with CDI software. In the TLR, the contractor shall include software interface requirements in terms of both objective and threshold requirements. The contractor shall provide a detailed analysis of the potential impacts of the TLRs to existing systems and the CDI software. In the analysis, the contractor shall discuss: recommended production combat system design changes; impacts to existing interfaces; and any new CDI software changes.

Deliverable: The contractor shall deliver TLR in accordance with CDRL A002 (DI-MISC-80652) and Technical Report in accordance with CDRL A003 (DI-MISC-80508B).

4.2 Architecture Development

Upon Government approval of TLR and in preparation for design reviews, the contractor shall provide a CDI software architecture design package, which shall include software components (identifying open source and proprietary components), abstraction layers, software development kits (SDKs), and application program interfaces (APIs). The contractor shall also provide combat system implementation approaches and software integration plans in the architecture design package. The contractor shall provide a read-ahead of the architecture design package one week in advance of scheduled design review. At the design review, the contractor shall present the architecture design package, and record meeting minutes and action items assigned. The contractor shall track action items for closure.

Deliverable: The contractor shall deliver CDI Software Architecture Design Package in accordance with CDRL A004 (DI-SESS-82176) and Meeting Minutes in accordance with CDRL A005 (DI-ADMN-81505).

4.3 Software Development

In accordance with Clause C-227-H007, the contractor shall prepare a Software Development Plan (SDP) for Government review and concurrence for computer software developed and maintained under this contract. The contractor shall identify any changes, modifications, additions or substitutions to the SDP, and upon Government concurrence, update the SDP for the specific computer software throughout the life of this contract.

Upon closure of the design review and Government approval of the architecture design package, and using Combat System software provided as GFI:

· The contractor shall update existing CDI software code for compatibility with the existing payload control system, applicable variants, and launcher systems.

· The contractor shall present status of software development at working group meetings and software design reviews.

· The contractor shall deliver source code, software documentation, developer notes, and development environment.

· The contractor shall implement information assurance into the software design in accordance with Applicable Document 3.10.

· The contractor shall develop and maintain a problem trouble report (PTR) tracker.

· The contractor shall provide updates of PTR status at Configuration Control Board (CCB) meetings and provide a list of recommended PTR adjudications.

· Upon Government approval, the contractor shall adjudicate PTRs identified as approved-to-fix.

Deliverable: The contractor shall deliver Software Development Plan in accordance with CDRL A006 (DI-IPSC-81427B), CDI Source Code in accordance with CDRL A007 (DI-IPSC-81488), PTR Tracker in accordance with CDRL A008 (DI-MISC-80508B), and PTR Adjudications in accordance with CDRL A009 (DI-MISC-80508B).

4.4 Hardware/Software Integration and Testing

The contractor shall develop and deliver simulator/stimulator software and prototype hardware (as required) for validation of the CDI software for the portable launch system. The contractor shall deliver simulator/stimulator software code, simulator/stimulator software design and user documentation, and any prototype hardware required for the integration and installation prior to Government evaluation.

The contractor shall develop, deliver, integrate, and install prototype hardware and software in an Engineering Development Module (EDM) laboratory at NUWCDIVNPT to support formal evaluation of the new design to be performed by the Government. The contractor shall provide peripheral equipment to be used during the development and testing of the CDI Software. The contractor shall develop test plans and procedures to validate that the software meets the approved TLRs. The contractor shall develop, or recommend revisions to, design documents, test plans, and procedures to demonstrate adjudication of completed PTRs that were generated from 4.3 tasking. In accordance with Government approved test plans and procedures, the contractor shall test the software and deliver test reports.

Deliverable: The contractor shall deliver Simulator/Stimulator Software Code in accordance with CDRL A00A (DI-IPSC-81488), Simulator/Stimulator Software Design and User Documentation in accordance with CDRL A00B (DI-AVCS-80700A), Test Plans and Procedures in accordance with CDRL A00C (DI-SESS-81704), and Test Reports in accordance with CDRL A00D (DI-NDTI-80809).

4.5 Capstone Demonstration

The contractor shall demonstrate the full end-to-end thread for mission areas of the payload defined in the CONOPs in a formal Concept of Operations Exercise (COOPEX) for the portable launch system. Upon completion of the COOPEX, the contractor shall document the results of the COOPEX and deliver a formal report detailing the results of all testing and post-test analysis. In the report, the contractor shall identify any limitations and impacts to other subsystems and identify operational and security impacts of the current concept design. The contractor shall include recommended changes or modifications to design, requirements, or the CONOPS in the report.

Deliverable: The contractor shall deliver Capstone Report in accordance with CDRL A00E (DI-MISC 80508B).

4.6 Shipboard Demonstration

4.6.1 Alterations

Once the Capstone Demonstration is completed and the Government concurs that software/hardware PTR is acceptable, the contractor shall review the GFI (shipboard alteration data packages for Ship Alterations (SHIPALTs), Temporary Alterations (TEMPALTs), Engineering Change Instructions (ECI), and Temporary Engineering Change Instructions (TECIs)) and provide recommendations for improvement to shipboard installation efforts. Additionally, upon Government review and approval of recommendations, the contractor shall update the alteration TDPs to encompass the approved recommendations.

Deliverable: The contractor shall deliver Updated Alteration Technical Data Packages in accordance with CDRL A00F (DI-SESS-80776B), User’s and Operating Guides in accordance with CDRL A00G (DI-MISC-80508B), Test Plans in accordance with CDRL A00H (DI-NDTI-80566A).

4.6.2 Installation and Checkout

As identified in a Government installation schedule, provided as GFI, and upon receipt of approved shipboard alteration data packages, provided as GFI, the contractor shall perform installation and checkout of demonstration systems.

Deliverable: The contractor shall deliver System Operational Verification report in accordance with CDRL A00J (DI-NDTI-80809B), Trip Reports in accordance with CDRL A00K (DI-MISC-81943).

4.6.3 Demonstration of Software/Hardware

In accordance with Government approved Test Plans and Procedures, the contractor shall perform dockside and at-sea test periods to conduct system performance assessments of the portable launch system to include the collection of necessary data required to assess the system.

Deliverable: The contractor shall deliver Trip Reports in accordance with CDRL A00K (DI-MISC-81943).

4.6.4 Analysis and Recommendations

Upon completion of shipboard demonstrations, the contractor shall review post-mission analysis data, provided as GFI, and perform analysis, assessments, and recommendations for system improvements.

Deliverable: The contractor shall deliver Test Reports in accordance with A00J (DI-NDTI-80809B).

4.7 Cyberspace/Cyber Workforce (CWF)

4.7.1 Cyberspace Qualifications

Per DFARS 252.239-7001 ‘Information Assurance Contracting Training and Certification,’ all personnel performing cyber functions must be trained and qualified. In addition, personnel shall maintain the appropriate security clearance per SECNAV M-5510.30C to perform the tasks associated with their assigned positions.

Note: DFARS uses Information Assurance (IA) which is the old title and acronym; it has been replaced by Cyberspace/Cyber Workforce (CWF).

The contractor is required to earn and maintain appropriate baseline certification as identified in DOD 8570.01-M for the position and tasking being performed.

If privileged access is required, the contractor shall complete a privileged access agreement, SECNAV 5239/1, and submit it to the COR. Contractors have up to 6 months to obtain applicable operating system and computing environment training or the account(s) will be suspended. The contractor shall provide a copy of the certificate(s) of completion to the COR.

4.7.2 Cyberspace Reporting

The contractor shall provide a list of all personnel assigned to the contract performing cyber functions as a part of a monthly CWF Report. The report shall include employee name, contract number, the applicable CWF category and level, required certifications and fulfillment status. Note that Contractor CWF personnel must receive designation approval in writing by the Commanding Officer, or the C-ISSM via “By Direction” authority, prior to performing CWF functions.

The contractor shall submit new hire information for tasking requiring cyber functions to the COR at least seven (7) days prior to the new hire employee beginning performance of any cyber functions. New hire information shall include name, contract number, list of applicable cyber functions category, level, required certifications and fulfillment status, as well as a copy of the baseline certification documentation. Per DFARS 252.239-7001(c), “Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions, and therefore may not be allowed to charge to the contract.

Deliverable: The Contractor shall deliver a monthly CWF Report in accordance with CDRL A00L (DI-MGMT-82160).

4.8 Meeting Support

The contractor shall attend Working Group meetings to gather necessary information about any planned system modifications to allow for payload integration. For all relevant meetings as identified in a Government meeting schedule, provided as GFI, the contractor shall coordinate, attend, prepare agendas and briefing material, take minutes and track actions.

Deliverable: The contractor shall deliver Presentation Material in accordance with CDRL A00M (DI-ADMN-81373). Meeting Minutes in accordance with CDRL A005 (DI-ADMN-81505)

5.0 Progress Reports

5.1 Contract Status Report

The Contractor shall prepare a Contractor’s Status Report that indicates the progress of work, status of the program(s), and existing or potential problem areas for all assigned tasks. The Contractor shall submit the Contract Status Report for the same timeframe as each invoice submitted in the Wide Area Workflow (WAWF) Module of the Procurement Integrated Enterprise Environment (PIEE).

Deliverable: The contractor shall deliver Contractor’s Status Reports in accordance with CDRL A00N – DI-MGMT-81991.

5.2 Training

5.2.1 The Contractor shall require all Contractor employees performing work at any NUWC Division Newport site, who has a Common Access Card (CAC) and an NMCI Account, to complete all required Mandatory trainings.

5.2.2 The Contractor shall require Contractor employees to complete any applicable Limited Audience required training(s). Note: Limited Audience required training(s) may be applicable regardless of performance site location.

5.2.3 The Contractor shall fill out and submit to the Government the Training Completion Status Report, GFI 6.10, affirming all Mandatory training and any applicable Limited Audience required training(s) are completed. The required training and required training schedule is available at the following website: [WILL BE PROVIDED AT AWARD] under Mandatory Training Instructions. See the .pdf Mandatory Training Instruction – Contractors Only.

5.2.4 The Contractor shall validate the Government’s DRAFT Limited Audience Training Applicability List GFI 6.10 for accuracy and completeness and submit to the Government a finalized Limited Audience Training Applicability List. The following Limited Audience required training(s) are applicable to this requirement:

NATO

5.2.5 The Training Completion Status Report and Limited Audience Training Applicability List shall include the contract number, contactor employee name, specific training course title and identification number, and completion date for all contractor employees asserting training completion. Contact the COR identified in Section G if additional access instructions are needed. If specific training questions arise, contact the POC listed for the training in the above-specified .pdf(s).

Deliverable: The contractor shall deliver Training Status Reports in accordance with CDRL A00P (DI-MISC-80508B).

6.0 Government Furnished Information

The following Government Furnished Information (GFI) will be made available under this contract.

Integrated Master Schedule (IMS) 4.1, 4.2, 4.3, 4.4, 4.5, 4.6

(TMPC) Integrated Master Schedule

(IMS)

4.1, 4.2, 4.3, 4.4, 4.5, 4.6

Craft Operating Procedures 4.1, 4.2, 4.3, 4.4, 4.5, 4.6

Group (VSRWG) Charter, 13 August 2015

4.1, 4.2, 4.3, 4.4, 4.5

Capability Concept Specification and Requirements Documents 4.1, 4.2, 4.3, 4.4, 4.5

7.0 Government Furnished Property

The Government may provide Government Furnished Property (GFP) as listed in Attachment 2. The contractor shall adhere to DFARS Clause 252.245–7005 for the management and reporting of Government Property and shall use the GFP Module of the Procurement Integrated Enterprise Environment (PIEE) as specified in the clause. In addition, the Contractor shall prepare and submit a Government Property (GP) Inventory Report to capture GFP status IAW CDRL A00Q (DI-MGMT-80441D).

Deliverable: The contractor shall deliver Government Property (GP) Inventory Reports in accordance with CDRL A00Q.

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. Contractor performance will be evaluated in the areas of technical quality, cost control, schedule/timeliness, management, and regulatory compliance as follows:

· Technical Quality: The government will evaluate technical quality using the criteria defined in the Performance Requirements Summary Table (PRST), Attachment X;

· Cost Control: The government will evaluate the contractor’s effectiveness in forecasting, managing, and controlling actual costs in comparison to negotiated costs;

· Schedule/Timeliness: The government will evaluate the contractor’s ability to meet negotiated milestones and delivery schedules;

· Management: The government will evaluate the contractor’s ability to integrate and coordinate all activities needed to execute the contract;

· Regulatory Compliance: The government will evaluate the contractor’s compliance with the terms and conditions of the contract relating to applicable regulations and codes.

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 United States Submarines.

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.

Communications Security (COMSEC) COMSEC is required for the contractors to perform tasks 4.1-4.8.

The contractor shall primarily use COMSEC access at NUWCDIVNPT facilities and while performing work aboard naval vessels.

Restricted Data (RD) RD is required for the contractor to perform tasks 4.1-4.4, 4.8.

The contractor shall use RD access for payload information required for performance specification and interface development.

Critical Nuclear Weapon Design Information (CNWDI) CNWDI is required for the contractor to perform tasks 4.1-4.4, 4.8.

The contractor shall use CNWDI access for payload information required for performance specification and interface development.

Formerly Restricted Data (FRD) FRD is required for the contractor to perform tasks 4.1-4.4, 4.8.

The contractor shall use FRD access for payload information required for performance specification and interface development.

Sensitive Compartmented Information (SCI) SCI is required for the contractor to perform tasks 4.1-4.8.

The contractor shall use SCI access to perform services in support of all SOW tasks.

Non-Sensitive Compartmented Information (non-SCI) Non-SCI is required for the contractor to perform tasks 4.1-4.8.

The contractor shall use Non-SCI access to perform services in support of all SOW tasks.

North Atlantic Treaty Organization (NATO) Information NATO information is required for the contractor to perform tasks 4.1-4.8.

The contractor shall use NATO access for payload information required for performance specification and interface development, software development, and testing.

Foreign Government Information (FGI) FGI is required for the contractor to perform tasks 4.1-4.8.

The contractor shall use FGI access for payload information required for performance specification and interface development, software development, and testing.

Secret Internet Protocol Router Network (SIPRNET) SIPRNET is required for the contractor to perform tasks 4.1-4.8.

The contractor shall use SIPRNET access to perform services in support of all SOW tasks.

Controlled Unclassified Information (CUI) including Legacy FOUO and Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoD Instruction 5200.48, CUI available at:

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF. Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) in accordance with DoDI 5230.24 (Distribution Statements on Technical Documents); and DoDI 5230.24, Enclosure 3 Procedures, available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/523024p.pdf

INFORMATION SECURITY: If the work is performed at the Contractor's facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with National Industrial Security Program Operating Manual (NISPOM) codifying 32 CFR Part 117, NISPOM Rule, and SECNAV M-5510.36B. If the work is performed at the Government's facility, the Contractor shall comply with facility policy.

CUI INCIDENT REPORTING AND RESPONSE: The Contractor shall promptly report any unauthorized, inadvertent, or illegal release or disclosure of CUI to the Contracting Officer’s Representative / Technical Point of Contact (TPOC), Procuring Contracting Officer, and the Security Office. Contractor personnel shall coordinate this effort through the relevant industry site FSO.

PUBLIC RELEASE: Any controlled unclassified information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through the appropriate U.S. Government Office.

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.