DRAFT_CSoF PWS_DRAFT.docx
DOCX document 83 KB Posted
- Attached to
- Combat System of the Future (CSoF)
- Solicitation number
- N66604-26-R-0494
About this file
This is a Performance Work Statement (PWS) for a Cost Plus Fixed Fee (CPFF) and Cost Only Indefinite Delivery, Indefinite Quantity contract supporting submarine Combat System of the Future (CSoF) development. The Naval Undersea Warfare Center Division Newport (NUWCDIVNPT) intends to award this sole-source requirement to Mikel, Inc. (CAGE Code 5A6D6, Middletown, RI) under SBIR Phase III, with an anticipated 537,600 labor hours over five years. The contract applies to current and future submarine platforms including Los Angeles-class, Seawolf-class, Virginia-class, Columbia-class, SSN(X), Ohio-class, and AUKUS submarines. The NAICS code is 541715 (engineering services) with a 1,000-employee size standard.
The PWS defines eleven primary task areas: (1) Combat System Concept Evaluation including wargaming and tactical evaluation; (2) Systems Engineering for requirements definition, architecture development, and design reviews; (3) Computer Software Programming, Design, Development and Maintenance utilizing IEEE/EIA standards; (4) Hardware Engineering and technical support for sensor integration; (5) Engineering Design, Development and Evaluation including ECPs, RFVs, and Level of Repair Analyses; (6) Modeling and Simulation for combat control systems; (7) Test and Evaluation at laboratory and at-sea locations; (8) Integrated Logistics Support and Fleet Support including failure analysis; (9) Cyber Security with qualified workforce maintaining DoD 8570.01-M certifications; (10) Submarine Combat System Operator Training and Qualification; and (11) Program Support including CONOPs development. Performance locations include NUWCDIVNPT Kings Bay and Bangor, contractor facilities at Lockheed Martin (Manassas, Virginia and Mitchell Field, New York), General Dynamics (Manassels, Virginia and Groton, Connecticut), and various military ranges and fleet sites. Multiple government sponsors are identified including UWDC, AUTO, SPORTS, USFFC, and numerous Program Executive Offices and Program Management Offices. Security requirements include SIPRNET, NNPI, U-NNPI, SCI, NATO, FGI, and CUI handling. The RFP is anticipated for posting by end of September 2026.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| DRAFT_Sections LM - CSOF SBIR Phase III_DRAFT.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
v4.11_JULY2026
PERFORMANCE WORK STATEMENT (PWS)
Combat Systems of the Future (CSoF)
Background This SBIR Phase III effort stems from the development of automated detection and tracking systems for passive and active acoustic signals utilizing Bayesian and Artificial Intelligence. These capabilities were initially established under two SBIR initiatives: SBIR N02-025 (“Combat Systems of the Future”) for active intercept ranging and SBIR N05-149 (“Non-Collinear Wavefront Curvature Ranging”) for passive bearings-only tracking. Under these foundational efforts, advanced detection technologies were created to correlate signals received on submarine hydrophone arrays against time histories of known and hypothesized signals. This detection capability is paired with tracking technologies that convert acoustic time-of-arrival data into either bearings for passive tracking (N05-149) or a range for active intercept (N02-025). The system subsequently processes these bearings over time using an AI-directed search across all potential target tracks to accurately determine a contact's position and velocity over ground.
Today, this matured SBIR technology provides critical capability enhancements for Anti-Submarine Warfare (ASW) in both Test and Evaluation (T&E) and tactical operational scenarios. When deployed as a portable undersea tracking range, the system calculates the geodetic position of submerged platforms in passive or active modes. This delivers essential "ground truth" data required to support the developmental and operational testing of U.S. and allied Fleet submarines and related systems. Operationally, the technology serves as an underwater position fix system that enables precise undersea positioning in GPS-denied environments. This capability facilitates submerged waypoint and chokepoint navigation, cross-domain messaging, and overall improved navigational accuracy for a wide array of submerged platforms, including submarines, SEAL Delivery Vehicles (SDVs), Unmanned Underwater Vehicles (UUVs), and weapon systems.
The intent of this SBIR Phase III effort is to leverage the technology of passive and active tracking on the platforms to expand beyond the current application within SONAR (BQQ-10) into the rest of the Combat Systems (e.g. Combat Control, Imaging (IMG), Electronic Warfare (EW), Communications (Comms), weapons, and Navigation). In Subsea and Seabed Warfare (SSW), the entire seafloor is considered a platform/system which renders this technology a critical asset for mission success in that arena. Leveraging this technology for active and passive ranging of platforms, vehicles, weapons, and sensors is critical to possess theater-level operational control of that area of water space for performing multiple SSW mission sets.
The contractor is leveraging inventions and computer software from SBIR Phase II efforts. Phase II had two main efforts for CSoF. First, delivering a top-down mission driven manning analysis and definition. Second, definition, prototyping, and evaluation of key architecture capabilities. Both efforts develop revolutionary ideas that improve the warfighters’ ability to ingest information quickly and respond with accurate solutions that are necessary to ensure mission success and safety of ship.
To achieve this, the effort will begin with a detailed analysis of selected mission scenarios. For each mission, the decision-making processes will be mapped by identifying critical decisions that must be made, the sequence of those decisions, and the conditions under which they occur. Following this, the necessary tasks, data inputs, and information flows required to support each decision point will be thoroughly defined.
Using the results of this analysis, a scalable and modular functional architecture will be developed. This architecture will support the integration of emerging and advanced technologies—such as artificial intelligence, machine learning, and advanced data analytics—for specific roles within the system, particularly where automation can provide the most operational benefit.
Special emphasis will be placed on human-systems integration to ensure that the resulting design not only complements but also enhances operator situational awareness, decision confidence, and system usability in high-stress environments.
The final deliverable will include a functional data fusion prototype of the CSoF . This prototype will be rigorously evaluated using both simulated environments and live at-sea test data (as available) to assess performance improvements in areas such as sensor fusion, threat detection, decision support, and system responsiveness. The insights from these evaluations will inform further development and potential transition to operational platforms.
Places of Performance
Services shall be performed at both Contractor and Government Sites.
Travel is required during performance. Locations of Travel may include shipyards, platforms, military ranges, fleet experimentation sites, and the following Government and contractor locations:
NUWCDIVNPT Kings Bay On-site Office (OSO) NUWCDIVNPT Bangor On-Site Office (OSO) Undersea Warfighting Development Center Tactical Advisory Group (UWDC TAG), Groton, Connecticut Lockheed Martin, Manassas, Virginia Lockheed Martin, Mitchell Field, New York General Dynamics Mission Systems, Manassas, Virginia General Dynamics Electric Boat Cooperation, Groton, Connecticut Authorized Users Combat Systems Department, Code 25, Code 15, and Code 75, of the Naval Undersea Warfare Center, Division Newport is authorized to use this contract.
Sponsors Undersea Warfighting Development Command (UWDC); Advanced Undersea Technology Office (AUTO); Sonar Positional Reporting System (SPORTS); United States Fleet Forces Command (USFFC); Direct Report Portfolio Manager (DRPM) Submarine; PAE Aviation; PAE RAS; PAE Mission Systems; PAE Munitions; PAE Maritime; PAE Marine Corps; Program Executive Office (PEO); Program Management Office (PMS) 397; PEO PMS 396; PMS 340; PMS 390; PMS 394; Future Submarines Project Office (PMS 351); PMS 425; PMS 401; PMS 404; PMS 406; PMS 408; PMS 415; PMS 420; PMS 392; PMS 435; PMS 450; PMS 485; PMS495; PMW 770; PMW 160; PMW 150; PMW 130; PMW 120; PMA 280; Integrated Warfare Systems (IWS) 5; IWS 6; Strategic Systems Program (SSP); Program Management Activity (PMA) 280; SUB 073; SUB-S; Naval Supply Systems Command (NAVSUP); AUKUS Program Office; Office of Naval Research (ONR); Defense Advanced Research Projects Agency (DARPA); The Strategic Capabilities Office (SCO); International Programs Types of Funding Operations and Maintenance, Navy (O&MN);
Other Procurement, Navy (OPN);
NUWC Overhead/Service Cost Center Navy Working Capital Funds (NWCF);
National Sea-Based Deterrence Fund (NSBDF);
Research, Development, Test, and Evaluation (RDT&E);
Shipbuilding and Conversion, Navy (SCN); and Foreign Military Sales (FMS) Scope This Performance Work Statement (PWS) supports the development, assessment, integration, and enhancement of submarine Combat System of the Future (CSoF) across all current and future submarine platforms. These platforms include, but are not limited to, Los Angeles-class, Seawolf class, Virginia-class, Columbia-class, SSN(X), OHIO-class, and AUKUS submarines. The Contractor shall apply advanced system engineering, software and hardware development, modeling and simulation, testing and evaluation, cyber and integrated logistics support to ensure these platforms meet evolving warfighting requirements. This includes support for integrating and enhancing Strike capabilities aligned with submarine mission requirements, in coordination with PMA-280. This scope encompasses continued development of technologies initiated under prior SBIR efforts and it enables work applicable to all submarine CSoF supported by sponsors listed in Section 1.3.
This PWS defines the efforts necessary for the Contractor to provide engineering services, products and support for existing and future Combat Systems for all sponsors listed in PWS section 1.3. It provides for additional research and combat system development and processing and further leverages the other work conducted under SBIR N05-149 and SBIR N02-025 in the areas of automated detection, tracking of passive/active acoustic signals, organic sensor & signal processing, tactical control/sensor level data fusion, Off board sensor data fusion, web enabled GIS, Time of Arrival Estimation, AI Contact Classification and state estimation target motion analysis/tactical picture development, weapon employment, and tactical decision aids. The PWS also allows for system engineering, system architecture, concept of operations and test and evaluation work to be performed in support of continued combat system development and SSW system development for studies to determine the combat system and ship impact of new sensor and weapon/vehicles technologies.
Applicable Documents The contractor shall perform the tasking required in Section 4.0 in accordance with (IAW) the below Applicable Documents (ADs).
| Number |
| Name |
| Revision Number / Date |
| Task Number |
| 3.1 |
| DoD Issuances |
| 3.1.1 |
| Chairman of the Joint Chiefs Staff Manual (CJCSM) 3170.01I |
| 1/23/2015 |
| ALL |
| 3.1.2 |
| MIL-STD-961E, Change 2 Military Standard Specification Practices |
| 1/9/2014 |
| ALL |
| 3.1.3 |
| MIL-STD-31000B DoD Standard Practice, Technical Data Packages |
| 10/31/2018 |
| ALL |
| 3.1.4 |
| MIL-STD-1397C Input / Output Interfaces, Standard Digital Data, Navy Systems |
| 6/1/1995 |
| ALL |
| 3.1.5 |
| MIL-HDBK-454B General Guidelines for Electronic Equipment |
| 4/15/2007 |
| ALL |
| 3.1.6 |
| NAVSEA S9070-AA-MME-010/SSN/SSBN, Technical Requirements Manual for Temporary Submarine Alterations, Third Revision, ACN-1 |
| 8/25/2010 |
| ALL |
| 3.1.7 |
| MIL-STD-461G Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment |
| 12/11/2015 |
| ALL |
| 3.1.8 |
| MIL-STD-882E System Safety Program Requirements |
| 5/11/2012 |
| ALL |
| 3.1.9 |
| MIL-STD-1472G Human Engineering |
| 1/11/2012 |
| ALL |
| 3.1.10 |
| DOD Instruction 5000.02 “Operation of the Defense Acquisition System” |
| 1/7/2015 |
| ALL |
| 3.1.11 |
| MIL-STD-1399, Section 300B, Electric Power, Alternating Current |
| 4/24/2008 |
| ALL |
| 3.1.12 |
| SSPINST 4423.66B, Determination of Trident Equipment/Component Military Essentiality Code (MEC) |
| 4/23/1999 |
| ALL |
| 3.1.13 |
| DoD Guide for Achieving Reliability, Availability, and Maintainability (U) |
| 8/3/2005 |
| ALL |
| 3.1.14 |
| The Under Secretary of Defense (USD) Memorandum for Secretaries of the Military Department Directors of the Defense Agencies Deputy Under Secretary of Defense (A&T) Reliability, Availability, and Maintainability (RAM) Policy Memo (U) |
| 7/21/2008 |
| ALL |
| 3.1.15 |
| MIL-HDBK-189C, DoD Handbook, Reliability Growth Management (U) |
| 6/14/2011 |
| ALL |
| 3.1.16 |
| Office of the Under Secretary of Defense, Memorandum for Secretaries of the Military Departments, Subject: Implementation of Life Cycle Sustainment (LCS) Outcome Metrics Data Reporting Memo (U) |
| 12/11/2008 |
| ALL |
| 3.1.17 |
| Department of Defense Reliability, Availability, Maintainability, and Cost Rationale Report Manual. Washington, DC: Office of the Secretary of Defense |
| 2/28/2017 |
| ALL |
| 3.1.18 |
| MIL-HDBK-217F, Reliability Prediction of Electronic Equipment |
| 12/2/1991 |
| ALL |
| 3.1.19 |
| Risk Management Guide for DoD Acquisition |
| 8/2006 |
| ALL |
| 3.1.20 |
| DODI 8500.01, Cybersecurity, 14March 2014 |
| 3/14/2014 |
| ALL |
| 3.1.21 |
| DODM 5200.01 Information Security Program: Overview, Classification, and Declassification 24 February 2012 |
| 2/24/2012 |
| ALL |
| 3.1.22 |
| DODI 8510.01, Risk Management Framework (RMF) for DOD Information Technology (IT), 12 March 2014 |
| 3/12/2014 |
| ALL |
| 3.1.23 |
| DoD 8570.01-M, Information Assurance Workforce Improvement Program, Change 4 |
| 11/10/2015 |
| ALL |
| 3.1.24 |
| SECNAV M-5239.2, Cyberspace Information Technology And Cybersecurity Workforce Management And Qualification Manual, (As amended20 May 2020 by DoN CIO Memorandum) |
| 06/2016 |
| ALL |
| 3.1.25 |
| 25 DoD Directive 8140.01, Cyberspace Workforce Management |
| 10/05/2020 |
| ALL |
| 3.1.26 |
| DoD Instruction 8140.02, Identification, Tracking, And Reporting Of Cyberspace Workforce Requirements |
| 12/21/2021 |
| ALL |
| 3.1.27 |
| DoD Manual 8140.03, Cyberspace Workforce Qualification And Management Program |
| 05/15/2023 |
| ALL |
| 3.2 |
| Navy Issuances |
| 3.2.1 |
| Program Executive Officer Integrated Warfare Systems (PEO IWS) Deputy Commander Naval Sea Systems Command Warfare Systems Engineering Directorate (NAVSEA 05H) Technical Review Manual (TRM) |
| 12/18/2009 |
| ALL |
| 3.2.2 |
| NUWCDIVNPTINST 5200.4H |
Publications and Presentations Guide
| 6/2/2014 |
| ALL |
| 3.2.3 |
| Submarine Warfare Federated Tactical Systems (SWFTS) Systems Engineering Baseline Management Process |
| 3/15/2019 |
| ALL |
| 3.2.4 |
| Submarine Warfare Federated Tactical Systems (SWFTS) Integration and Test Process |
| 1/29/2019 |
| ALL |
| 3.2.5 |
| Submarine Warfare Federated Tactical Systems (SWFTS) Technology Insertion Process |
| 8/10/2017 |
| ALL |
| 3.3 |
| Classified Information Handling |
| 3.3.1 |
| DoDM 5200.01, Vol 1, DoD Information Security Program |
| Change 2, 07/28/2020 |
| ALL |
| 3.3.2 |
| DoDM 5200.01, Vol 2, DoD Information Security Program |
| Change 4, 07/28/2020 |
| ALL |
| 3.3.3 |
| DoDM 5200.01, Vol 3, DoD Information Security Program |
| Change 3, 07/28/2020 |
| ALL |
| 3.3.4 |
| DoDM 5200.48 Controlled Unclassified Information |
| 03/06/2020 |
| ALL |
| 3.3.5 |
| NUWCDIVNPTINST 4000.1B Receipt, Delivery, Inspection, and Shipment of Material |
| 11 September 2023 |
| ALL |
| 3.3.6 |
| NAVSEA M-5510.1, NAVESA Security Program Manual |
| 07/2022 |
| ALL |
| 3.3.7 |
| NSWCHQ/NUWCHWINST 5510.1, Security Program Manual |
| 11/09/2020 |
| ALL |
| 3.3.8 |
| NUWCDIVNPT 5500.4, NUWCDIVNPT Command Security Manual |
| 04/19/2023 |
| ALL |
| 3.3.9 |
| Naval Undersea Warfare Center Division Newport Critical Information and Indicators List (CIIL) |
| 10/22/2025 |
| All |
| 3.3.10 |
| CMS-1B, DoN COMSEC Policy and Procedures |
| 03/31/2025 |
| 4.2, 4.4, 4.7 |
| 3.3.11 |
| OPNAVINST 2221.5, Release of COMSEC Material to U.S. Industrial Firms under Contract to USN. |
| Change 4, 11/10/2015 |
| 4.2, 4.4, 4.7 |
| 3.3.12 |
| NUWCDIVNPTINST 2280.1H Local Handling and Accountability of COMSEC Materials |
| 12/12/2022 |
| 4.2, 4.4, 4.7 |
| 3.3.13 |
| NUWCDIVNPTINST 2280.2H COMSEC Emergency Action Plan |
| 03/24/2021 |
| 4.2, 4.4, 4.7 |
| 3.3.14 |
| NAVFAC P-307 Management of Weight Handling Equipment |
| 01/2025 |
| 4.7 |
| 3.3.15 |
| NUWC INSTR 5100.14g NUWC WHE Instruction |
4.7
Technical Requirements The objective of this Phase III effort is to develop on the Phase II SBIR N00024-11-C-6295 for a command-and-control system and associated concept of operations to achieve improved automation, reduced manning, and improved performance over current CSoF and apply this technology to the efforts for Los Angeles, Seawolf, Virginia, SSN(X), Columbia, Ohio, and AUKUS submarine classes.
The Contractor shall perform the following tasks to apply advanced system engineering, software and hardware development, modeling and simulation, testing and evaluation, cyber and integrated logistics support for further development of CSoF.
In accordance with Task Order (TO) Statements of Work (SOWs), Applicable Documents (ADs), and using Government Furnished Information (GFI), the contractor shall provide the services below. The ADs are relevant to the tasks and subtasks for which they are identified in Section 3.0.
Combat System Concept Evaluation
The contractor shall provide systems engineering, innovation engineering, and subject matter expertise in support of a wide range of submarine-related activities, including but not limited to concept development, technology exploration, wargaming exercises, tactical evaluation, and mission-focused workshops. These efforts shall support current and future capability development across all submarine platforms and SSW systems, with particular emphasis on Los Angeles, Virginia, SSN(X), Columbia, Ohio, and AUKUS-class submarines.
The contractor shall support the evaluation and integration of Non-Propulsion Electronic Systems (NPES), as well as systems that interface with, enable, or enhance NPES functionality. This includes the use of analytical methods, modeling and simulation tools, and submarine operational expertise to assess platform performance, tactical employment, and overall mission effectiveness in relation to NPES and its peripheral systems.
The contractor shall be responsible for planning, facilitating, and executing meetings involving Government and contractor stakeholders. These meetings shall provide a cross-functional, cross-organizational forum for assessing current challenges, identifying emerging capability needs, and building a shared vision for system-of-systems solutions aligned with evolving mission requirements. The specific nature of these meetings shall be defined at the task order level.
The contractor shall document the outcomes of these meetings, including technical assessments, integration opportunities, and actionable recommendations for capability development, ensuring that deliverables remain adaptable to future engineering, innovation, and integration efforts across all submarine platforms.
Deliverables: Technical Report – Study/Services (CDRL A00E) System Engineering
The contractor shall participate in the Systems Engineering activities for new and future combat control systems. This task extends systems engineering and architecture development performed under N00024-11-6295, refining and scaling established combat system architectures to support CSoF integration across current and future submarine platforms.
These activities shall include, but not be limited to, the following:
a) Definition of Common Requirements – Collaborate with stakeholders to define, validate, refine, and reuse system-level requirements that support interoperability across diverse platforms.
b) Definition and Design of the Common Infrastructure/Architecture – Develop a modular, scalable architecture that supports integration of emerging technologies and aligns with Navy standards for open systems design.
c) Enterprise Service Bus (ESB) Requirements – Identify and document functional and performance requirements for an ESB to enable secure, real-time data exchange and orchestration among distributed combat system components.
d) Scalable Computing Data Center Requirements – Define performance thresholds, hardware and software interface requirements, and redundancy strategies to support mission-critical operations under varying load conditions.
e) Definition and Design of the Common Human Systems Interface (HSI) – Participate in the design of intuitive and adaptable HSI components that enhance operator situational awareness, decision-making efficiency, and system accessibility across user roles.
f) Design Data Fusion Approach for Tactical Control – Define data fusion frameworks which augment tactical decision-making by integrating multi-source sensor data to improve threat detection, classification, and response time.
g) Associated Reviews and Coordination Meetings – Attend and contribute to technical exchange meetings (TEMs), system design reviews (SDRs), preliminary design reviews (PDRs), critical design reviews (CDRs), and cross-platform coordination sessions to ensure alignment of efforts across engineering teams and stakeholders.
h) Verification, Validation, and Accreditation (VV&A) Activities – Develop test plans, test procedures, and evaluation criteria for Government approval to ensure the system meets operational requirements and is suitable for deployment.
i) Risk Management and Trade Study Analysis – Identify technical risks, conduct trade-off studies, and propose mitigation strategies to guide engineering decisions that balance cost, schedule, and performance.
j) Documentation and Configuration Management Support – Thoroughly document and version control all engineering contributions in alignment with programmatic configuration management processes provided as GFI in the appropriate government system.
Deliverables: Test Plan and Procedure (CDRL A002); Design Test Inspection Reports (CDRL A003), Technical Report – Study/Services (CDRL A00E), Configuration Management Plan (CDRL A00G) Computer Software Programming, Design, Development, and Maintenance
The Contractor shall update the Software Development Plan (SDP) and tailor the plan to correspond to the updated system requirements of CSoF.
The contractor shall define a general SDP appropriate for the computer software effort to be performed under this contract. The SDP shall, at a minimum:
(1) Define the contractor's proposed life cycle model and the processes used as a part of that model. In this context, the term "life cycle model" is as defined in IEEE/EIA Std. 12207.0;
(2) Contain the information defined by IEEE/EIA Std. 12207.1, section 5.2.1 (generic content) and the Plans and Procedures in Table 1 of IEEE/EIA Std. 12207.1. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted;
(3) Identify the specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification.
(4) Document all processes applicable to the system to be acquired, including the Primary, Supporting, and Organizational life cycle processes as defined by IEEE/EIA Std. 12207 as appropriate. Such processes shall be equivalent to those articulated by CMMI®;
(5) Be in accordance with the framework defined in IEEE/EIA Std. 12207.0, including, but not limited to, defining the processes, the activities to be performed as a part of the processes, the tasks that support the activities, and the techniques and tools to be used to perform the tasks;
(6) Contain a level of information sufficient to allow the use of the SDP as the full guidance for the developers. In accordance with section 6.5.3a of IEEE/EIA Std. 12207.1, such information shall, at a minimum, contain specific standards, methods, tools, actions, reuse strategy, and responsibility associated with the development and qualification of all requirements, including safety and security.
The Contractor shall design, develop, update, maintain, and document vehicle, targets and simulator software.
The Contractor shall develop software test plans, and software test descriptions. The Contractor shall test and evaluate the system software and document these evaluations in software test reports. The Contractor will update test plans and descriptions as the software changes based off the results of test and evaluation as part of the configuration control of all software.
The Contractor shall review software code and documentation for submarine combat control development programs. The Contractor shall analyze the software for suitability, function, performance, and potential hazard, risk, and other safety issues. The Contractor shall provide analysis reports to summarize the results of each assessment.
Deliverables: Software Development Plan (CDRL A001); Software Test Plan and Procedure (CDRL A002); Software Test Inspection Report (CDRL A003); Developmental Design Drawings/Models Associated Lists (CDRL A004); Model and Simulation Software Documentation (CDRL A005); Software Test Description (CDRL A006); and Safety Assessment Report (CDRL A007).
Hardware Engineering and Technical Support
The Contractor shall provide engineering and technical-scientific support to include theoretical study and investigation, experimentation, data collection, analysis, hardware identification and repair, design, drafting (sketches, drawings), fabrication, prototyping, testing, modeling, evaluation, and integration of sensor components or systems. The Contractor shall develop work plans, training materials, integration modifications, and test and evaluation of prototypes and systems as specified in the Task Order.
The Contractor shall evaluate emerging technologies—whether developed commercially or by the Government—for potential application within Combat Control systems, Non-Propulsion Electronic Systems (NPES), and systems that interface with, enable, or enhance NPES functionality. This includes support for the integration or installation of computer and computer-related equipment and components, along with associated physical, mechanical, electrical, electronic, and software-based hardware.
Deliverables: Technical Report – Study/Services (CDRL A00E) Engineering Design, Development, and Evaluation
The Contractor shall develop Engineering Change Proposals (ECPs) to address deficiencies and improvements in technologies, systems, and subsystems under review, including those associated with or supporting Non-Propulsion Electronic Systems (NPES), and submit them to the Government. The Contractor shall also prepare and deliver Requests for Variances (RFVs), Notices of Revisions (NORs), and Specification Change Notices (SCNs) as specified in the Task Order.
The Contractor shall conduct Level of Repair Analyses (LORA) for submarine Combat System of the Future (CSF) and related systems on submarines and SSW systems. These analyses shall encompass both deployed and in-laboratory systems and include risk analysis, system architecture reliability and availability assessments, dynamics evaluations, and life cycle support analysis. The Contractor shall document these findings in a comprehensive Level of Repair Analysis Report for Government review.
Based on the results of these analyses and with Government approval, the Contractor shall design, engineer, assemble, fabricate, obtain, and integrate prototype systems, subsystems, circuitry, hardware enclosures, racks, mounts, and associated interfacing hardware. This includes technologies that are part of, or interface with, NPES or support its integration. The Contractor shall provide a complete design package addressing new technologies and novel applications of existing technologies required to meet evolving operational needs. The design package shall include conceptual drawings, development drawings, and product drawings. Upon Government approval, the Contractor shall produce simulation models of the design and generate supporting technical media such as posters, graphics, presentations, and two- and three-dimensional (2D/3D) models to illustrate the system or subsystem design.
The Contractor shall develop and submit a test plan and procedures for the developmental testing of prototype systems. Upon Government approval of the test plan, the Contractor shall participate in a Test Readiness Review (TRR) led by the Government. Following Government approval at the TRR, the Contractor shall conduct laboratory-based developmental testing of the prototypes and document the results in a detailed developmental test report.
The Contractor shall modify, refurbish, repair, and upgrade existing CSoF and associated components, including circuit boards, commercial-off-the-shelf (COTS) items, legacy equipment, and materials, as well as systems that integrate with or enhance NPES capabilities across current and future submarine platforms.
Deliverables: Development Test Plan and Procedure (CDRL A002); Test Inspection Report (CDRL A003); Developmental Design Drawings/Models and Associated Lists (CDRL A004); Engineering Change Proposal (CDRL A008); Request for Variance (CDRL A009); Notice of Revision (CDRL A00A); Specification Change Notice (CDRL A00B); Level of Repair Analysis Report (CDRL A00C); System/Design Trade Study Report (CDRL A00D); Technical Report – Study/Services (CDRL A00E) Modeling and Simulation
The Contractor shall develop upgrade, maintain, and operate submarine combat control simulation tools and environments utilizing procedures provided as GFI.
The Contractor shall troubleshoot and remedy any system anomalies that arise within combat control software and hardware during a simulation and document these in a simulation report. The simulation report shall include recommended changes to the system to improve or enhance performance.
The Contractor shall develop a Human Systems Integration (HSI) planning report, detailing how the program will meet HSI programmatic requirements and standards for Los Angeles, Seawolf, Virginia, SSN(X), Columbia, Ohio, and AUKUS submarines and SSW systems. The Contractor shall describe how the system will optimize human performance by meeting the needs of the human operators, maintainers, and support personnel. The Contractor shall include the following considerations in the report: Manpower, Personnel, and Training (MPT); human factors engineering; personnel survivability; habitability; safety; and environmental. The report shall include a plan for the integration of HSI requirements within the systems engineering, logistics, technology development, and resource management processes, including a summary of the HSI risks and supporting mitigation plans.
Deliverables: System/Design Trade Study Report (CDRL A00D); Technical Report – Study/Services (CDRL A00E); Human Systems Integration Planning Report (CDRL A00F).
Test and Evaluation (T&E)
The contractor shall develop operational use cases and scenarios using the models and prototype designs developed in section 4.3, 4.4, and 4.5 using submarine employment and SSW systems subject matter experts. The contractor shall support test execution–virtually, dockside, and at-sea– and data collection and analysis. Upon receipt of program plans and requirements provided as GFI, the Contractor shall conduct test planning and execution at the vehicle-systems level. The Contractor shall develop test plans, operations orders and procedures to detail the schedule, logistics, and data recording requirements for each event scheduled. In the test plan, the Contractor shall provide the standards, checklists, validation materials, procedures, technical measures of performance, and tasks necessary to conduct product assurance, quality assurance, safety, reliability, and maintainability of the testing. The Contractor shall check the availability of required Government services (including crane, range, lab, and boats), and determine software and data recording requirements. The Contractor shall integrate the test components developed for at-sea test environments. The Contractor shall submit the test plan for Government review and approval prior to conducting any tests.
Upon Government approval of the Contractor’s test plan or receipt of a test plan provided as GFI, the Contractor shall conduct operational tests to measure effectiveness of identified technologies, systems, and subsystems designs. If individual Task Orders identify that Government-provided services (crane, range, lab and boats) are not available for the scheduled test, the Contractor shall provide crane, range, lab, and boat services required for testing. The Contractor shall verify that the crane provided is certified to handle the vehicle being tested. The Contractor shall operate Contractor-provided boats during at-sea tests; the Government will operate all Government-owned boats. The Contractor shall operate Contractor-provided cranes during testing; the Government will operate all Government-owned cranes. Prior to WHE operation, the Contractor shall obtain and maintain the proper training certification and medical physicals as required in ADs 3.3.14 and 3.3.15. The Contractor must be qualified to operate the Category III Cranes IAW ADs 3.3.14 and 3.3.15. The Contractor shall immediately report all crane mishaps, near misses and equipment failures or breakdowns, and immediately stop operations upon the occurrence of a mishap, near miss, equipment failure or breakdown. While operating cranes, the Contractor shall maintain proof of Crane Operator License on their person IAW AD 3.3.14 section 8 and AD 3.3.15. While conducting the operational test, the Contractor shall monitor the test, collect, and record data, and provide detailed test reports to document specification requirements of the software or equipment being tested and maintained.
Deliverables: Operational Test Plan & Procedure (CDRL A002); Operational Test Inspection Report (CDRL A003).
Integrated Logistics Support (ILS) and Fleet Support
The Contractor shall track, coordinate, and maintain the supply logistical procedures and functions for the submarine systems, as well as the associated laboratories and facilities. The Contractor shall establish and maintain an inventory of all components necessary for the execution of the tasking at the task order level.
The Contractor shall provide Fleet support for delivered and deployed submarine Combat System of the Future (CSF). The Contractor shall field trouble calls from the Fleet and conduct failure analysis to identify the source of the problem. The Contractor shall recommend solutions to the Fleet customer. The Contractor shall perform repairs and provide walk-through technical assistance for delivered or deployed Fleet systems. The Contractor shall confirm resolution of the issue with the Fleet customer. The Contractor shall document repairs and confirmation of resolutions in failure analysis reports.
Deliverables: Technical Report – Study/Services (CDRL A00E); Failure Summary and Analysis Report (CDRL A00J), Integrated Logistics Support Plan (CDRL A00H) Cyber Security
The Contractor shall provide a Cyber Security Work Force (CWF). The Contractor shall provide security and mission assurance for the development, operation, management, and enforcement of Cyber Security policies, as well as the implementation of security measures and procedures for Information Systems associated with Navy tactical and tactical support systems. The Contractor shall maintain and update Information Assurance (IA) security planning and accreditation documentation to support ongoing system sustainment and modernization efforts. The Contractor shall meet and maintain the certification and educational requirements required by the Cyber Security Work Force in accordance with DoD directives.
The Contractor shall conduct studies and analyses of new IA and IT trends, policies, and regulations, and investigate the feasibility of applying new cybersecurity solutions and technologies into existing submarine infrastructure and architecture. The Contractor shall provide recommendations for improvement in IA-related hardware, software, and peripherals to the Government for consideration in future upgrade strategies. The Contractor shall also conduct program protection planning in coordination with other system security disciplines.
In support of in-service engineering, the Contractor shall assess cybersecurity risks associated with system lifecycle activities, including engineering changes, software modifications, hardware refreshes, and configuration management. The Contractor shall evaluate the cybersecurity impact on existing shipboard and submarine systems resulting from engineering changes and propose updates to performance specifications and interface requirements to maintain appropriate cybersecurity posture.
The Contractor shall support the development and execution of Test Plans and Test Procedures for all cybersecurity-related test and integration events. The Contractor shall design, prototype, and assess hardware and software solutions that address known vulnerabilities, meet cybersecurity system requirements, and protect against anticipated threats. The Contractor shall submit technical reports detailing effectiveness and improvement recommendations.
The Contractor shall attend Technical and Design Reviews to collect system requirement information, identify cybersecurity non-compliance, and provide recommendations for satisfying current and future cybersecurity requirements. The contractor shall document meeting minutes and technical inputs deliver them to the Government.
The Contractor shall perform cybersecurity testing during Test and Evaluation (T&E) events led by the Government to identify and mitigate vulnerabilities that impact the operational resilience of Navy systems. Upon receipt of Government Furnished Information (GFI), the Contractor shall prepare and deliver Test Schedules, Integration Plans, Requirements Verification Matrices, and Test Completion Reports.
The Contractor shall analyze cybersecurity systems engineering content within Engineering Change Proposals, System Change Notices, and Document Change Notices, ensuring proper functional flow down and alignment with Baseline Requirements Documents and Key Information Security Requirements. Non-compliance findings shall be documented in monthly analysis reports.
The Contractor shall, upon receipt of GFI, provide technical assessments to identify cybersecurity gaps and emergent risks that impact the Navy's tactical and tactical support systems architecture. Recommendations and mitigations shall be documented in Cybersecurity Gap Analysis Reports. In addition, the Contractor shall provide analyses of cyber threats identified by the Government, offering mitigation strategies and resilience techniques via technical reports and briefings Deliverables: Test Plan and Procedure (CDRL A002); Technical Report (CDRL A00E); Meeting Minutes (CDRL A00X); Monthly Analysis Report (CDRL A00X) Submarine Combat System Operator Training and Qualification
The Contractor shall train submarine CSoF operators on the system SOPs and all applicable health and safety guidelines and requirements at a Government facility or at a Contractor provided location. If instructional material, lesson plans and qualification criteria do not already exist for a given system, the Contractor shall develop and provide these materials for Government review and approval. If instructional material, lesson plans and qualification criteria do already exist for a given system, the Contractor shall update and provide them for Government review and approval.
The Contractor shall provide CSoF training and certification to Government personnel.
Deliverables: Technical Report – Study/Services (CDRL A00E) Program Support The Contractor shall provide and deliver recommendations, input, and analysis regarding Concept of Operations (CONOPs), field operations, and technical data calls for Government review. Documentation for review may include trade studies and state-of-the-art assessments, technical input, and evaluations regarding current requirements or requirements under development by the Government. After review, the contractor shall provide a recommendation detailing whether this SIBR Phase III CSoF technology is applicable to the reviewed requirements. The Contractor shall use a format or database to compile, archive, and maintain a library of program documentation.
Deliverables: Technical Report – Study/Services (CDRL A00E)
4.12 Cyberspace/Cyber Workforce (CWF)
4.12.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.12.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: Cyber Security Workforce (CWF) Report (CDRL A00K)
1.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: Contractor Status Technical Report (CDRL A00L)
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.25, 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.26 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, NNPI
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: Training Status Technical Report (CDRL A00M)
Government Furnished Information The following Government Furnished Information (GFI) will be made available under this contract/task order.
| Number |
| Title |
| Applicable PWS Task Number |
| 6.1 |
| Columbia Program documents, including CDDs, Functional Requirements Documents (FRDs), SRVMs, CONOPS, Operational Mission Scenarios, Mission Profiles, Failure Definition and Scoring Criteria, RAM Program Plans, Technical Objectives and Guidelines, ship specifications, technology development plans, and system design and analysis documents |
| 4.1,4.2,4.3,4.4 |
| 6.2 |
| VIRGINIA Class program documents, including Operational Requirements Document (ORD), CDDs, FRDs, SRVMs, CONOPS, Operational Mission Scenarios, Mission Profiles, RAM Plans (RAMP), Life Cycle Support Plans (LCSP), Technical Objectives and Guidelines, ship specifications, technology development plans, and system design and analysis documents |
| 4.1,4.2,4.3,4.4 |
| 6.3 |
| Columbia Class and VIRGINIA Class platform-level Systems Engineering Plans (SEP) (for the applicable phase of each program) |
| 4.1,4.2 |
| 6.4 |
| NPES Drawing Packages and NPES Engineering Notes |
| 4.3,4.4 |
| 6.5 |
| Engineering notes, reports, drawings, action items, schedules, associated technical & administrative data and required formats for reports, presentations and other documentation (to be provided as available) |
| 4.3,4.4,4.5,4.8 |
| 6.6 |
| Requirements documents for all NPES Government Furnished Equipment (GFE) subsystems, including CDDs, subsystem performance specifications, and system requirements verification matrices |
| 4.1,4.2,4.3,4.4,4.5,4.11 |
| 6.7 |
| Program assessments (e.g. PDR, CDR) documentation packages and action item lists & results (to be provided as available) |
| 4.1,4.2,4.5,4.11 |
| 6.8 |
| VIRGINIA Class platform-level test (e.g. TECHEVAL, OPEVAL, Developmental Tests, Operational Assessments) documentation for NPES subsystems |
| 4.2,4.3,4.4,4.5 |
| 6.9 |
| IETMs for all NPES GFE subsystems |
| 4.3,4.4,4.8 |
| 6.10 |
| Concept of Operations (CONOPS) and Concept of Operations Exercise (COOPEX) documentation for NPES and NPES subsystems (to be provided as available) |
| All |
| 6.11 |
| Operator’s manuals for NPES subsystems (to be provided as available) |
| All |
| 6.12 |
| Inter-subsystem Interface Requirement Specifications (IRS), Interface Design Documents (IDD) Interface Control Drawings (ICD) and Coordination Documents (to be provided as available) |
| All |
| 6.13 |
| Test plans, procedures, and reports (to be provided as available) |
| 4.3,4.4,4.5 |
| 6.14 |
| Integration plans, procedures, and reports (to be provided as available) |
| 4.3,4.4,4.5 |
| 6.15 |
| Installation plans, procedures, and reports (to be provided as available) |
| 4.3,4.4,4.5 |
| 6.16 |
| Configuration Management Plans (platform-level) |
| 4.1,4.2,4.7,4.8 |
| 6.17 |
| Alteration documents (e.g. TEMPALTS, ShipAlts) |
| 4.3,4.4,4.5,4.7,4.8 |
| 6.18 |
| Emergent Technology Descriptions |
| All |
| 6.19 |
| Emergent Issue Definitions |
| All |
| 6.20 |
| Risk Management Plans and databases and reports (to be provided as available) |
| 4.5,4.9,4.10,4.11 |
| 6.21 |
| Problem reports |
| 4.1,4.2,4.3,4.4,4.5,4.9,4.10,4.11 |
| 6.22 |
| Submarine Warfare Federated Tactical Systems (SWFTS) Systems Engineering Baseline Management Process |
| 4.1,4.2,4.3,4.4,4.5,4.9,4.10,4.11 |
| 6.23 |
| Submarine Warfare Federated Tactical Systems (SWFTS) Integration and Test Process |
| 4.1,4.2,4.3,4.4,4.5,4.9,4.10,4.11 |
| 6.24 |
| Monthly CWF Report template |
| 4.12 |
| 6.25 |
| Training Completion Status Report |
| 5.2.3 |
| 6.26 |
| DRAFT Limited Audience Training Applicability List |
| 5.2.4 |
| 6.27 |
| Programmatic Configuration Management Processes |
| 4.2 |
Government Furnished Property The Government may provide Government Furnished Property (GFP) as listed in Attachment X. 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 A00N.
Deliverable: Government Property (GP) Inventory Report CDRL A00N
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 contractor to perform task(s) 4.2, 4.4, and 4.7.
Justification: The contractor supports test execution and system integration for submarine combat control systems, which involves handling classified communications over tactical networks during at-sea and lab-based testing. Access to COMSEC is necessary to ensure proper configuration, testing, and troubleshooting of secure communication links in simulated and operational environments.
Restricted Data (RD) RD is required for the contractor to perform task(s) 4.2, 4.4, and 4.7.
Justification: While the contractor does not engage directly with nuclear weapon design, system-level integration and engineering of Combat System of the Future (CSF) on nuclear-powered submarines require awareness of RD-controlled design constraints in adjacent systems and environmental considerations affecting electronics and integration zones.
Critical Nuclear Weapon Design Information (CNWDI) CNWDI is required for the contractor to perform task(s) 4.2, 4.4, and 4.7.
Justification:…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .