Attachment 2- USW DSS IDIQ Draft RFI SOW_final_2.pdf

N0002426R5208 Attachment 2

Page 1 of

22 22

Commander Naval Sea Systems Command

1333 Isaac Hull Avenue, SE

Washington DC, 20376-0005

BASIC CONTRACT STATEMENT OF WORK

FOR

Integrated Warfare Systems Undersea Systems (IWS 5)

Solicitation No.: N0002426R5208

Contract No.: TBD

Undersea Warfare Decision Support System (USW-DSS) Indefinite-

Delivery Indefinite-Quantity (IDIQ) Multiple Award Contract (MAC)

23 September 2025

Page 2 of

STATEMENT OF WORK

(Scientific and Engineering Support for Advanced Electronic Warfare)

Table of Contents

1 Introduction

1.1 Background

1.2 Scope

2 General Requirements

2.1 Non-Personal Services

2.2 Business Relations

2.3 Contract Administration and Management

3 Functional Areas and Task Descriptions

3.1 Program Management and Systems Engineering Support

3.2 Software/Hardware Development and Integration (including integration of GFP)

3.3 USW Tool Set / Command and Control (C2) Software Development

3.4 USW DSS Special Development Items

3.5 Test And Evaluation

3.6 Training

3.7 Installation Support

3.8 Procurement of Commercial Off-The-Shelf (COTS) Products

3.9 Administrative and Program Support

4 Special Requirements

4.1 Security

5 Deliverables/Schedule

6 Technical Point of Contact

7 Data

8 Government Furnished Property

9 Delivery/Task Order Process

9.1 General

9.2 Competitive Ordering Process

9.3 Delivery Orders/ Task Orders

9.4 Unauthorized Work

9.5 Task Funding Restrictions

9.6 Ordering Authority

Page 3 of

1 Introduction

This Statement of Work (SOW) describes the programmatic and system engineering support to be provided to the Integrated Warfare Systems Undersea Systems (IWS 5) of the Naval Sea Systems

Command (NAVSEA), Washington, DC. NAVSEA requires highly specialized experience in the areas of integrated undersea sensors and sonar processing for submarine and surface ship combat systems as well as integrated Anti-Submarine Warfare (ASW) command and control systems for surface ships and aircraft carriers that can complement the Government acquisition team.

1.1 Background

AN/UYQ-100 Undersea Warfare Decision Support System (USW DSS) is the Navy program of record

(PoR) undersea warfare (USW) and Anti-Submarine Warfare (ASW) command and control (C2) system supporting the warfighter. USW DSS provides an integrated, near-real time, net-centric common tactical picture (CTP) and common operational picture (COP) for ashore and afloat warfighters. USW DSS users include Commander Task Force (CTF)/Theater USW Commander (TUSWC) headquarters, Submarine

Operating Authority (SUBOPAUTH), Naval Oceanographic Office (NAVO), Unmanned Undersea Vehicle

Oceanography Command (UUV OC), embarked group Sea Combat Commander (SCC), and CVN, DDG and FFG platforms. On afloat platforms, USW DSS software is virtualized for portability and hosted on the

Consolidated Afloat Networks and Enterprise Services (CANES) infrastructure . For support and ashore nodes, USW DSS software is hosted on commercial-off-the-shelf (COTS) hardware.

1.2 Scope

USW DSS enables effective planning and execution of USW/ASW operations and mission objectives, optimizes placement of platforms and sensors for exploitation of the environment, manages available resources, balances operations versus risk, and provides a clear vulnerability assessment of the operational environment. USW DSS shortens C2 decision processes for detection-to-engagement across multiple platforms, including those with low bandwidth communications or intermittent connectivity.

Tactical data such as tracks, assignments, environmental, and sensor processing data is exchanged and ingested into USW DSS through platform specific interfaces such as the AN/SQQ-89(V) Surface Ship

ASW Combat System acoustic sensor integration on the ship combat system, GCCS-M, and Aircraft

Carrier-Tactical Support Center (CV-TSC). USW DSS processes this and other tactical data for intelligent dissemination to unit and theater level platforms in support of an enhanced USW/ASW tactical picture.

USW DSS follows a Continuous Improvement/Continuous Deployment (CI/CD) model, leveraging multiple Development and Secure cloud Operational (DevSecOps) environments to produce software upgrades twice a year via Capability Drops (CDs). This acquisition will support the continued development, integration, test, delivery, and incorporation of critical enhancements to USW and ASW capabilities into the existing USW DSS Program of Record (PoR).

Contractors shall be required to deliver the software and hardware Technical Data Packages (TDPs) and technical documentation necessary to meet the development of each USW DSS Capability Drop. The

Government maintains data rights to use the USW DSS Technical Data (TD), Computer Software (CS), and Computer Software Documentation (CSD) as specified in DFARS 252.277-7014(c)(1-4). The data will be used for the sole purpose of development, testing, and integration of current and future USW

DSS systems. Where allowable, the data obtained under these data rights will be used to pursue future full and open competition in future contract initiatives.

The major technical areas that will be addressed are:

• Program Management and Systems Engineering Support

Page 4 of

• Software/Hardware Development and Integration (including integration of GFP)

• USW Tool sets / Command and Control (C2) Software Development

• USW DSS Special Development Items

• Test and Evaluation

• Training

• GFP/GFE Provisioning(Procurement of Commercial Off-The-Shelf (COTS) Products)

• Installation Support

2 General Requirements

At the Delivery Order (DO) and Task Order (TO) level the contractor shall have its support team in place and fully functioning within 30 days of contract award.

At the DO/TO level the contractor must execute the scope of work in a manner that provides for high quality, timely services while incorporating the proper mix and the most effective use of personnel.

2.1 Non-Personal Services

The Government will neither supervise Contractor employees nor control the method by which the

Contractor performs the required tasks. The Government will not assign tasks to, or prepare work schedules for, individual Contractor employees.

The Contractor shall be responsible for managing its employees and guarding against any actions that are of the nature of personal services, or give the perception of personal services as defined in FAR Part 37 -

Service Contracting.

The Contractor shall notify the Contracting Officer (KO) if any Government requested actions constitute, or are perceived to constitute, personal services.

2.2 Business Relations

The Contractor shall integrate and coordinate all activity needed to execute this contract at the DO/TO level.

2.3 Contract Administration and Management

The following subsections specify requirements for contract management and Contractor personnel administration at the DO/TO level.

2.3.1 Contract Management

The Contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to this contract.

2.3.2 Personnel Administration

The Contractor shall assign a single point of contact, also known as the Program Manager (PM), who will work closely with the Government KO and Contracting Officers Representative (COR), as applicable.

The Contractor PM will ultimately be responsible for ensuring that the Contractor’s performance meets all Government contracting requirements within cost and schedule. The PM must have the requisite authority for full control over all company resources necessary for contract performance. As appropriate, the role of the PM may be a full time management position, or a collateral duty assigned to a technical team member.

Page 5 of

The Contractor shall make necessary travel arrangements for Contractor employees.

2.3.3 Contract Administration

The Contractor shall establish processes and assign appropriate resources to effectively administer the contract.

The Contractor shall respond to Government requests for contractual actions within five working days.

3 Functional Areas and Task Descriptions

Efforts within this section are to be accomplished on both classified and unclassified computer networks and may require Contractor personnel to have access to information up to and including Top Secret (TS) and Sensitive Compartmented Information (SCI) classification levels as well as Alternative

Compensatory Control Measure (ACCM) controlled information.

3.1 Program Management and Systems Engineering Support

The contractor shall provide program management and systems engineering support for Theater Undersea

Warfare (TUSW) initiatives, including planning, scheduling, and milestone development for all performers. This support encompasses:

• Stakeholder Engagement: Refine stakeholder inputs (fleet operators, program office, SMEs) and provide research results in a final report and presentations. Summarize progress and consult with

IWS 5 and stakeholders for feedback and research focus adjustments.

• Systems Engineering Products: Develop Needs Statements, Use Cases, Requirements, and models, adjusting development focus based on IWS 5 and TUSW stakeholder feedback.

• Integrated Logistics Support (ILS)/Integrated Product Support (IPS): Develop ILS/IPS products for fleet-deployed systems.

• Technical Data Package (TDP):

• Develop and maintain a TDP containing software design descriptions, architecture diagrams, and installation guides.

• Software Product Package (SPP):

• Develop and maintain an SPP containing all developed software (executable binary, source code, scripts, rpms), related notes, and documentation.

• Data Management and Agile Development:

• Manage technical documentation, source code, and agile epics/stories/sprint tasking (up to

CUI) in Naval LIFT Dev Tools (or alternative government-provided location). Use agile software development processes, working with the government as the product owner.

• Interface with government personnel, partners, and customers to discuss data extractions, engineering solutions, and operational needs. Document meetings with minutes and monthly status reports.

• Software Development Life Cycle (SDLC):

Page 6 of

• Meet SOW requirements and objectives within available funding. If the government lacks an established SDLC, implement and document a suitable model, including the people, process, tools, and methodologies.

• Requirements Management:

• Functional Requirements: Develop, manage, and analyze functional requirements

(capability, data sources/processing/products, application behavior) in a requirements tool.

Generate a Requirements Traceability Matrix (RTM) and use it throughout the SDLC for verification, validation, and cybersecurity compliance.

• Non-Functional Requirements: Develop, manage, and analyze non-functional requirements

(security, reliability, availability, maintainability, usability, scalability) in a requirements tool.

• System Architecture Development: Develop a system architecture (documented in a System

Architecture Description (SAD)) that describes the system, environment, interfaces, and major components. Include COTS, GOTS, and OSS software used. The SAD will include diagrams, accompanying narrative that describes the desired attributes and behavior of each element, as well as the associated requirement that each element is assigned to satisfy, and a brief description of any license or data rights requirement associated with a system element.

• System Design: Develop system design artifacts (data schemas, screen mock-ups, interface design descriptions, flow diagrams, activity diagrams, block diagrams, sequence diagrams, and ad hoc descriptions of how system behavior is to be implemented) aligned with the model–view–controller

(MVC) paradigm. Place design artifacts under version control and make them available for review at the government's request.

• System Development: Perform software system development according to the chosen SDLC model

(e.g., agile Scrum). Use an agile project management tool to manage development tasks and follow a schedule for frequent, routine software development. Organize teams to accomplish development tasks, and decompose tasks into manageable units of work. Use a version control system for secure and collaborative software development.

• System Integration: Perform system integration tasks in an environment that emulates the operational environment. Establish separate development, test, and pre-production environments.

Ensure systems are installed, configured, operated, and maintained consistently with the operational environment. Ensure communication networks, communication protocols, cybersecurity devices and profiles, and account resources and permissions are established and configured so that mission aids can exchange data communications with all required external systems. Ensure that each system is loaded and configured with relevant operational data to provide a high-fidelity integration and test environment that resembles the operational environment as closely as possible.

• System Delivery/Deployment: Develop a process for secure and repeatable delivery/deployment of computer software configuration items (CSCIs). Include executable artifacts, installation/configuration instructions, reference data, and necessary manuals. Develop a strategy for automated delivery/deployment, implementing if requested by the government.

• Schedule Management: Develop and maintain an Integrated Master Schedule (IMS) showing relationships among milestones, activities, and tasks. Update the IMS as work progresses, alerting the government to potential milestone risks. Ensure continuous government access to the IMS. Report project schedule monthly in the Monthly Status Report.

• Cost Management: Use a cost management system to define, monitor, manage, and report on the

Page 7 of use of task resources. Relate planned costs to IMS tasks using a Contract Work Breakdown Structure

(CWBS). Provide timely, accurate, and complete insight into planned, actual, and cumulative costs.

Report cost management monthly in the Monthly Status Report.

• Technical Performance Management: Use Jira to monitor and manage technical task performance, tracking progress, assignments, completion criteria, issues, and relationships between tasks. Manage resource allocation and monitor overall resource performance. Update the IMS consistently. Identify performance shortfalls, determine causes, implement corrective actions, and track performance exceeding expectation to institutionalize success. Report technical management monthly in the

Monthly Status Report.

• Configuration Management: Practice configuration management consistent with corporate policies.

Use separate version control systems for source artifacts (e.g., Git), executable artifacts (e.g., Nexus), and other artifacts (e.g., Confluence). Establish, record, update, audit, and report on baselines.

Support independent configuration management entities.

• Reporting and Meetings:

• Document activities, risks, issues, and resolutions in a monthly Contractor's Progress, Status, and Management Report.

• Provide financial expenditure status in a monthly Status of Funds Report.

• Support Program Management Reviews (PMRs), In-Process Reviews (IPRs), and Technical

Interchange Meetings (TIMs), providing agendas, meeting minutes, and presentations as directed. Provide Technical Studies/Reports as directed. Support other informal reviews and meetings as directed by the government Program Manager (PM).

• Quality Assurance: Implement quality assurance processes consistent with corporate policies. Use quality control processes to ensure delivered artifacts meet requirements, are delivered on time, and meet government quality expectations. Conduct periodic audits of internal processes. Ensure independence of quality assurance personnel.

• Standards Compliance: Ensure all development and maintenance efforts adhere to Quality Control and Configuration Management processes consistent with DoD and industry standards.

• Security Clearance: The Contractor will require access to attend meetings and discussions at the

Secret and or above levels.

• Travel: Conduct travel per the Government schedule. Deliver a Trip Report within 10 days of completing each trip.

3.2 Software/Hardware Development and Integration (including integration of GFP)

The Contractor shall provide needed expertise with integrating software developed by third-party developers (from Navy Laboratories, Academia, Industry, or Warfare Centers) into USW DSS and integrating USW DSS with external systems. This area also includes provisioning of development, test, and integration environments and facilities, both on-premises and virtual. Additional support includes research and development for technology refreshment (TR), technology insertion (TI), and software virtualization, containerization, and deployment technologies.

• IAAS and Integration: Develop IAAS products, including USW DSS integration into Navy

CANES, enterprise hypervisor environments (supporting VMs and containers), and Cross Domain

Solutions/Multi-Level Security.

Page 8 of

• OS Hardening and Patching: Implement automated OS (RHEL & Windows) hardening and patching for minimal user intervention.

• Patch Management Functional Requirements:

o Scanning: Automated, scheduled, and on-demand vulnerability scanning with detailed reporting.

o Download & Verification: Secure patch downloads from trusted sources, verifying integrity with notifications of corruption.

o Deployment & Installation: Silent, scheduled, rolling, and selective patch installations that minimize downtime and avoid interrupting critical operations.

o Rollback & Recovery: Rollback mechanism with logging and failure notifications.

o User & Administrative Controls: Centralized control, self-service patching, role-based access control, and policy-based patch management.

• Patch Management Non-Functional Requirements:

o Security: Secure channels (TLS/SSL), code-signing verification, and multi-factor authentication (MFA).

o Performance & Scalability: Efficient patch distribution, optimized bandwidth (delta updates), and minimal performance impact.

o Compliance & Auditing: Logging for ISO 27001, NIST, CIS, HIPAA compliance with exportable audit reports.

o Integration & Compatibility: Support for Windows, macOS, Linux, virtualized/cloud environments (AWS, Azure, VMWare), Active Directory (AD), ITSM tools via API, and

EDR solutions. (Examples of Automated Patch Deployment Tools: Microsoft Windows

Update & WSUS (Windows patching), Red Hat Satellite & Ubuntu Landscape (Linux patch management), IBM BigFix (Enterprise patch automation), ManageEngine Patch Manager

Plus, Automox (Cloud-native automated patching), and Ivanti Patch Management.)

▪ Software Build System and Support: Design and maintain a software build system for multiple external performers. Maintain a development and test lab, provide virtual environments to remote users, and offer on-site and remote installation support. Provide technical integration support for USW DSS systems in new network environments.

▪ TUSW C2 Analysis (Inspection): Conduct inspections in collaboration with decision support tool developers to analyze TUSW Command and Control procedures, processes, and perspectives.

▪ TUSW C2 Analysis (Research): Conduct research in collaboration with decision support tool developers to analyze TUSW Command and Control procedures, processes, and perspectives. Document and present findings to key stakeholders.

• Waterspace, ASW, UFS Software Development & Maintenance:

o Development: Define and develop software capabilities. Automate installation and

Page 9 of configuration. Install, configure, and verify software using automation code. Implement requirements with associated work items. Identify and resolve bugs. Support software development and integration using a common environment. Participate in iterative software development events (planning, reviews, retrospectives, SCRUMs, demos).

o Maintenance: Update software capabilities. Upgrade automation for installation and configuration. Install, configure, and verify software updates using automation code.

Modernize requirements with associated work items. Identify and resolve bugs. Support software maintenance and upgrade using a common environment. Participate in iterative software upgrade events (planning, reviews, retrospectives, SCRUMs, demos).

3.3 USW Tool Set / Command and Control (C2) Software Development

The contractor will develop and maintain software for USW DSS integration with the Common Track

Manager (CTM), including Analytics for CTM (ACTM). This includes:

• Development and integration support for MMS track exchange within and between USW DSS systems.

• Software design, feature development, and bug fixes for the AN/SQQ-Q89 and USW DSS interface.

• Software to support tactical data sharing between the US Navy and allied navies using USW DSS.

• User-facing and backend tools for track exchange between USW DSS systems and US Navy submarines.

• Integrating CTM into a multi-level secure Data Framework for Maritime Operations Centers of the

Future (DF-MOTF) environment.

• ASW CTM Software Enhancements:

o Develop algorithms for identifying patterns in historical ASW track data for future AI/ML systems.

o Create algorithms to assist operators in identifying Prevention of Mutual Interference (PMI) areas.

o Upgrade CTM adapters to ingest Thresher air tracks from multiple sources using KSQL.

Limit data distribution to essential fields.

o Develop a new CTM correlator to ingest data from a National Allsource Fusion Tracking

System (NAFTS) feed.

o Enhance the ASW Knowledge Base (KB) with more data (e.g., NID) and optimize

PostgreSQL queries for faster retrieval.

o Add support for storing and retrieving long-term track history.

o Continue software development to transfer KB data over MMS, integrating Broadcast-MMS into Adaptor-MMS.

o Enhance CTM to assign ambiguous reports to specific tracks, allowing operator verification.

o Continue development of negative search algorithms to forecast ship locations based on historical data.

o Continue development of the Blue-Green Optimizer (BGO) and expand it to include USMC

Page 10 of air space planning.

• DF-MOTF CTM Integration: Integrate CTM with Keycloak, update track view, enable track updates and correlation in an MLS environment, integrate CTM with ATLANTIS, and modify MMS to work in an MLS environment.

• Tactical and Mission Aids:

o Battle Management Aids (BMAs):

▪ Develop Battle Management Aids (BMAs) to support Composite Warfare

Commanders (CWCs) by providing advanced data processing, analysis, and fusion capabilities for improved decision-making. BMA will build on existing USW-DSS investments and support joint forces, including AMDC, ASWC, SUWC, STWC, and

IOC, while considering expeditionary maneuver warfare (EMW) and METOC. The objective is to integrate advanced optimization techniques and decision analytics for optimal force planning and allocation across all domains in near-real-time, addressing peer regional adversaries.

▪ BMA will be delivered in three technology sets:

▪ CWC plan/re-plan and force allocation optimization.

▪ CWC execution and synchronization monitoring and assessment.

▪ CWC composable battle management decision support.

▪ BMA will identify conflicts, optimize force allocation, monitor execution, and resolve conflicts across warfare areas. BMA requires User-Facing Services (UFS) for multi-dimensional decision support.

• CWC Execution Monitoring: Develop visualizations representing battle management context for rapid re-planning decisions.

• CWC Decision Support: Develop visualizations for interacting with higher-dimension optimization spaces on 2D displays, such as a "halo" concept linking objects to relevant data from external systems.

o Plan Execution Monitoring: Develop planning data models and data services to aggregate information on friendly forces (blue entities). Define task sequencing

(predecessors/successors) to support execution monitoring.

• Tactical Decision Aids (TDAs):

o TDA Development and Integration: Develop and integrate algorithmic planning decision aids as directed by WasP and AASW user-centered design analysis, addressing errors identified during testing.

o TDA Maintenance: Upgrade algorithmic planning decision aids as directed by WasP and

AASW user-centered analysis, addressing errors identified during testing.

• User-Facing Services (UFS):

o UFS Development and Integration: Design, develop, and integrate reusable, web-based user interface components using modern best practices. Refactor legacy USW-DSS user interfaces, visualizations, and supporting services to best-practice design patterns. Assist in

Page 11 of the development of web-based geospatial information system (GIS) displays.

o UFS Maintenance: Maintain, update, and modernize reusable web-based user interface components using modern best practices. Modernize legacy USW-DSS user interfaces, visualizations, and supporting services. Maintain web-based GIS displays.

• C2 Tools:

o The contractor will improve, correct, and integrate software for the TACSIT application in

USW DSS. Provide designs, recommendations, software enhancements, and bug fixes for the

Web DSS CTP. Provide software improvements and designs to support operator management of contacts of interest in the USW DSS Contact Log. Deliver software designs and implement requested features for managing Case Files in USW DSS. Plan for integrations with external systems (e.g., Warchest) and provide integration recommendations to government engineers.

• ASW User Interfaces / User-Facing Services (UFS):

o Refactor adaptive anti-submarine warfare (AASW) analytics and user-facing services (UFS) components to integrate them with the open-source geospatial GeoServer platform (replacing

CJMTK). Integrate UFS components and AASW widgets with Keycloak for identity and access management (IDAM). Integrate UFS components and AASW widgets with an MLS security context, providing CRUD data access. Automate deployment and configuration.

Integrate UFS and AASW containers (OCI) on the MLS-enabled and Kubernetes-based Red

Hat OpenShift hybrid cloud platform. Plan for future UFS refactoring to leverage new analytics and DF-MOTF integration. Develop a generalized UFS framework integrated with the MLS security context for new applications.

• ASW Software Extensions, Transition, and Maintenance:

o Extend and customize Adaptive ASW Software, Web DSS, Contact Log, and Case Files to support USW DSS use cases. Develop custom ASW UIs and extend them to support analytic enhancements. Extend backend services and ingest to support analytic enhancements.

Support the transition and integration of Adaptive ASW Software, Web DSS, Contact Log, and Case Files into the USW DSS architecture. Transition ASW UIs to integrate within USW

DSS user interfaces. Develop and modify extensions of ASW data ingest and backend services. Engineer the path forward for incorporating components within the USW DSS architecture and user experience. Upgrade/modify software to meet Information Assurance

(IA) requirements. Perform maintenance and bug fixes. Optimize UIs and backend services.

Update services to support security and information assurance. Document and update system engineering diagrams. Support government coordination of meetings and incremental deliveries. Monitor and track bugs and new feature requests.

• Long Range Targeting:

o The contractor will conduct research in collaboration with decision support tool developers supporting TUSW decision-making to analyze procedures, processes, and perspectives related to the conduct of long range targeting. The contractor will summarize progress and consult with IWS 5 and TUSW stakeholders to receive feedback and adjust the research focus as needed. The contractor shall continue research in collaboration with IWS 5 and decision support tool developers supporting TUSW decision-making to analyze procedures, processes, and perspectives related to the conduct of long range targeting. The contractor will document the results of the research in a final report and presented to key TUSW stakeholders.

This task may require access to TS/SCI level data.

Page 12 of

3.4 USW DSS Special Development Items

The Contractor shall conduct studies and analyses as directed by the Government to support requirements development, design trade-offs, concept of operations, technology exploration, system performance and, ship installations for the following items:

• Adaptive USW Development: Continue collaborative development with decision support tool developers to analyze water space management procedures and adaptive USW technology employment. Integrate AWS and WaSP CTM enhancements into ACS.

• Cloud Migration & Analytics: Provide expertise to migrate software from VMs to ACS Openshift containers. Develop cloud analytics for report/track association and conflict resolution using all available cloud data. Maintain AWS and WaSP CTM enhancements in ACS.

• Algorithm Development & Maintenance: Maintain ASW CTM enhancements, develop algorithms for AI/ML systems, and continue software development to transfer KB data over MMS, integrating

Broadcast-MMS into Adaptor-MMS. Enhance CTM to facilitate ambiguous report assignment to specific tracks, and develop negative search algorithms to forecast ship locations based on historical data.

• WaSP CTM Enhancements: Maintain WaSP CTM software and incorporate government-directed enhancements.

• Waterspace Management Action Area Algorithms: Develop algorithms to identify waterspace management areas and rules for rapid hostile submarine engagement while preventing friendly submarine attacks. These algorithms will serve as the basis for future AI/ML systems, identifying

ASWFA, SAA, SPA, SSL, JTAA, and SGSA.

• CDS Data Transfer: Develop software to support one-way (up) transfer of OTH-G, OPSKED, and

SUBNOTE messages across the CDS, updating the OTH-G format if necessary. Support MMS-encapsulated Waterspace object transfers through CDS.

• MMS Testing: Conduct formal testing of MMS processing and PMI/WSM message distribution, including route planning algorithm validation and AI/ML capabilities.

• WaSP Object Transfer & Algorithm Improvement: Continue software development for WaSP object transfer via MMS. Identify new algorithms to improve operator usability, including anti-collision algorithms for route planning and movement prediction. Algorithms must account for conflicts, events, and moving havens. Verify interference algorithm accuracy and safety rule adherence under all conditions. Implement exhaustive search-based "block" method to validate existing linear regression.

• WaSP-ET:

o Purpose: Enhance PMI by supporting WSM within a TASW planning and execution context.

o Architecture: Utilize a service-oriented architecture with data, service, and user-facing tiers connected via RESTful web services.

o Data Tier Refactoring: Refactor the data tier to a hybrid relational and document-store approach for interoperability across theater area-planning components.

Page 13 of o Service Tier Function: The service tier will orchestrate information flow across the system's architecture.

o UI Development: Develop the UI as React web applications in JavaScript (ES6).

o Map Integration: Integrate with a web-map abstraction framework to improve water space visualization, aligning with Minerva capabilities.

• WasP-ET Expansion: Expand WasP to support a broader theater-oriented WasP-ET capability according to the following schedule:

o Extensible TASW Area-Planning Capability: Build an extensible TASW area-planning capability for defining, storing, and serving areas and area assignments, including PMI and

WSM, with interoperability with CPD and SPA calculators. Create ability to define areas from permanent-area grid systems and assign those areas to units for specified time periods.

Begin work on an extensible plan validator.

o COA Visualization and Message Generation: Continue work on extensible plan validator.

Augment area-planning capability with course of action (COA) visualization and reconstruction to further inform both planning and execution monitoring. Seek a common

WSM message format and create message generation capability that directs WSM assignments and plans.

o AI/ML Based Route Generation: Further enhance area-planning capability with AI/ML-based route generation to recommend routes for both surface ships and submarines based on

AASW current and future heatmaps, adversary sensor capability, and Acoustic Terrain

Representation (ATR) model that seek to minimize the chance of detection by adversary submarines. Further add ability to recommend a PMI and WSM scheme that supports offensive and defensive search plan produced by CPD.

• GIS Map Support: Implement GIS map support in WasP-ET using common web-client-side messaging strategies to coordinate multiple visualizations. Use the existing USW DSS Map because its plug-in–based architecture makes it extensible for inclusion of new features that can be developed in parallel with little to no impact across projects. Using the USW DSS Map will also accelerate the anticipated transition to USW DSS.

• S&T Challenges in USW Area Planning: Develop capabilities that address science and technology

(S&T) challenges in the area of USW area planning. This task includes effort to automate

CONFIDENT (Conflict Identification) performance and to optimize it through parallelization, including narrow phase and moving haven geometry calculations. Expand area editors to account for multiple depth strata and area-relationship rulesets and shall refactor the multi-strata data model introduced by WaSP to include these new entities, properties, and corresponding constraints. Support efforts to expand CONFIDENT from a PMI interference-check algorithm to a WSM Plan validity-check algorithm by incorporating WSM geometry interaction rulesets. Develop tools to draw specific

WSM geometries on the map and will establish an alerting framework (framework candidates include work inherited from Distributed Common Ground System–Navy [DCGS-N] Increment 2 [Inc. 2]) in support of execution monitoring. Refactor the unit management capability to integrate with the Order of Battle (OOB) Entity Knowledge Base (KB). Support efforts to add WSM grids to the Naval

Research Laboratory - Stennis (NRL-S) Chart Server and shall participate in global grid initiatives

(e.g., GARS). Resurrect map search capabilities, including gazetteers, tracks, and entities. Implement an audit trail of changes at the user level, shall implement WSM message generation, and shall migrate from Digital Nautical Chart (DNC), Multi-mission Advanced Tactical Terminal (MATT), and Tactical Ocean Data (TOD)-2 to Electronic Navigational Chart (ENC).

Page 14 of

• METOC Integration: Support the integration of capabilities that address S&T challenges in the area of meteorology and oceanography (METOC) services and analytics. This task includes effort to integrate a METOC server, chart server, and tile server through optimization of application programming interfaces (APIs) that meet the interface and performance requirements of tactical decision aids (TDAs). Support extending the METOC server to account for new products, including bottom sediment type, bottom loss, ambient noise, and information drawn from other Oceanographic and Atmospheric Master Library (OAML) databases. Support refactoring the Chart server to support

SM-ENC. All data visualizations will be developed to ensure that their effective use is intuitive to

WasP-ET operators. Support developing capability to generate new products from existing environmental products, including Acoustic Parameters (APARMS), Acoustic Path Availability

(APA), ATR, and Acoustic Performance Surface (APS). Examples include sound speed clustering, and re-engineered versions of existing products to reduce product generation time, improve compatibility with TDAs, and align with target software architectures.

• OOB Entity KB Integration: Support the integration of capabilities that address S&T challenges in the area of OOB Entity KB. This task includes effort to review AMS, Modernized Integrated

Database (MIDB), and Military Equipment and Parametric Engineering Database (MEPED) data for relevant additions and changes. Support developing capability to ingest and fuse data from the

Platform Sensor Database (PSDB) and provide for the persistence of WSM specific entities that can be assigned common, stable identifiers. Also, when applicable, support the linking of these entities to platforms. Support modeling theater-level command relationships (operational control [OPCON], tactical control [TACON]) between KB entities, and shall support developing UFS widgets and services to edit and manage them. Support enhancing SOs and the KB for object-level authorization and row-level security, and publishing entities as indexed geospatial layers. Integrate the replication and synchronization of the KB and support providing capability to enable local edits that are exempt from KB replication and synchronization.

• Track, Contact, Case Management, and Correlation: Support the integration of capabilities that address S&T challenges in the area of track, contact, case management, and correlation. This task includes effort to update the Secret Internet Protocol Router Network (SIPRNet)–based Thresher interface to improve real-time performance ingestion. Configure and harden two-way MMS with

Commander Pacific Fleet (CPF) COP. Support implementing long-term history leveraging the

TimescaleDB and PostGIS features in PostgreSQL. Integrate with contact management and assessed track positions to supplement COP and track history, including auto-correlation of contact reports to tracks. Support developing the capability to ingest multisource data from Minotaur and to ingest Joint

Range Extension Application Protocol (JREAP)-C messages. Support updating the contact report model and management features to be ASW Common Data Model (ACDM) compliant, ensuring that the updates are consistent with both USW-DSS and DF-MOTF requirements. Support developing a

Zone Combiner launchpad application that correlates tracks from multiple sources. Support developing DSS-to-DSS track exchange using MMS and shall support TRK integration with CTM to leverage contact reports for analysis. Leverage Case File history for tactical situation (TACSIT) display. Support developing a web-based track view using Aeolus, preceded by bringing the display-server web service into the current ecosystem.

• Semi-Structured Contact Data Comprehension: Support the integration of capabilities that address

S&T challenges in the area of comprehension of semi-structured contact data. This task includes effort to ingest, parse, and process sensor reports from 9-line messages, acoustic intelligence

(ACINT) reports, static sensors, and sonobuoys (e.g., Commander Task Force [CTF]-72 chat).

Support developing techniques to comprehend chat data that contain misspellings or that deviate from standard format into usable data models and shall support developing tools to allow for manual entry of contacts into the database.

• Containerization: Develop capabilities that address S&T challenges in the area of containerization.

Page 15 of

This task includes effort to package WasP-ET, UFS, METOC services, OOB Entity KB, CTM, and

AASW as images based on a widely adopted container specification such as OCI, to store the images in an image repository, and to develop OpenShift deployment configurations that enable an

OpenShift runtime to automatically deploy the images as containers when it detects new images pushed to the image repository.

• WasP-ET Replication and Synchronization: Support integration of capabilities that address S&T challenges in the area of WasP-ET replication and synchronization. This task includes effort to implement multisite MMS for PMI, WSM, and reference areas.

• Target Estimation and Search Planning: Support integration of capabilities that address S&T challenges in the area of target estimation and search planning. This task includes effort to extend

ILRT to deliver the results of negative searches from both active and passive sensors to target tracking heatmap visualizations, ensuring that developed functionality supports an analyst’s ability to interpret how the negative search sensor reports influence heatmap predictions. Support developing enhancements that incorporate multiple sensors, including buoy fields, in a single session. Use different fidelity sensor models Cumulative Probability of Detection (CPD) TDA (CTDA), Scalable

Tactical Propagation Loss Engine (STAPLE) Toolkit [STK]) to incorporate the effects of sensor reports in ILRT forecasts. Support developing ingest tools that scrape chat feeds for sensor reports to support more automated inclusion of negative search sensor report messages. Integrate and use sensor data (PSDB) for entity acoustic characteristics and integrate the predictions from different tracking tools (ILRT, TRK) into a single coherent forecasting tool for use in USW-DSS. Support developing a theater search planning capability for the TUSWC that combines threat density from ILRT with probability of detection (PD) from STK and CTDA to determine platform PD on each area allocation.

• Integration with ONR Projects: Ensure WasP-ET development enables integration with the following related Office of Naval Research (ONR) projects:

o TMPLAR: automated tool that reliably routes assets from one location to another, while optimizing stealth and sensor performance.

o Chatbot: continuously monitors chat rooms for events of interest, resolves references across rooms, and links event-related information. The events will be published to the map for visualization and enrich cases, contact messages, and tracks.

o Case reconstruction: Using newly discovered contact data, environmental data, and historical case data in the system, as it applies to a case’s time span, create tools and analytics to perform forensic reconstruction of adversary movement.

o AASW and ML: This project seeks to convert tactics, training, and procedures (TTPs) to machine-readable language; leverage adversaries’ TTPs to enhance target estimation capabilities of AASW; and apply ML to case reconstruction to inform future predictions for similar red activity.

• Threat Analytics Tools:

o Adaptive ASW Support: Conduct research in collaboration with decision support tool developers supporting TUSW decision-making to analyze procedures, processes, and perspectives related to the conduct of water space management and the employment of adaptive ASW technologies.

o TRK / AOU Support: Support TRK / AOU/ ASW / ECOA Projection, Mission Planning, Area Planning, CDP, Mission Planning, Create and Share and METOC.

Page 16 of

• Supportability Engineering and Configuration Management:

o Software Infrastructure Maintenance: Maintain the software infrastructure including the

Jenkins build server to perform continuous integration, automated testing, software version control, installation package generation, and patch creation.

o Code Quality Inspection: Incorporate SonarQube (if directed) to continuously inspect code quality and security, analyze guidance, and correct deficiencies.

o Ansible Playbook Management: Maintain and update Ansible playbooks for software configuration and deployment.

o MLS GCCS FE CTM COP Implementation: Support implementation of an MLS-enabled

GCCS FE CTM COP at each MOC, including synchronized components. Support data labeling, UI integration, AASW capabilities, and containerization. Support a lab demonstration of SWFTS labeled data in TCML and surveys for future MLS integration.

• Support for Logistics and Sustainment: Support ashore platforms, afloat platforms, and installations support

3.5 Test And Evaluation

The Contractor shall design, develop, and maintain test and evaluation activities consist of engineering support to the Government for testing of USW DSS systems under operational relevant scenarios and subject to various system configuration baselines. Support shall be required for shore and sea-based testing, technology demonstrations, system experiments, and operation assessments. Test support includes test planning, test procedure generation and execution, trouble report processing, performance analysis tools, test simulation/stimulation tools, focused regression testing, data archiving for algorithm assessments, and reporting of test results. Test and Evaluation support also requires provision of testing facilities and virtual environments for formal testing of systems.

3.6 Training

The contractor shall provide on-site post-installation training to system operators to explain the differences between the older version and the newly installed version of the system. The contractor shall conduct a Training System Requirements Analysis (TSRA). The contractor shall identify and codify new focal capabilities for USW DSS. The contractor shall develop prototype lessons. The contractor shall utilize task flows and TSRA reports to develop Modernization Training curriculum. The contractor shall develop an initial Personal Qualification Standards (PQS) or Job Qualification

Requirement (JQR). The contractor shall conduct a wholeness review of all formal courses that will need revisions/changes based on a new BL/CD. The contractor shall support additional training initiatives as required.

• Analysis: Conduct a Job Duty Task Analysis (JDTA) whereby operator and maintainer tasking are defined, decomposed, structured, and assigned key attributes. The data (tasks, task attributes, Training Task Analysis (TTA), existing interventions, and Knowledge, Skills, Abilities, Tools, and Resources (KSATRs)) derived from this TA will serve as the source for determining workload, building learning objectives for curriculum development, and improving operator and maintainer training. The contractor shall:

o Facilitate workshops in accordance with NAVEDTRA 142 (series) with representatives from relevant joint commands, training centers, and operational units.

Page 17 of o Decompose duties into measurable tasks and subtasks.

o Define task conditions, standards, and performance criteria.

o Determine the knowledge, skills, abilities, and tools required to perform each task.

o Establish linkages between KSATs and operational readiness objectives.

o Identify gaps in current training and recommend mitigation strategies.

• Conduct a Training System Requirements Analysis (TSRA): The contractor shall conduct a comprehensive TSRA to identify, define, and document the training needs associated with the operational deployment and sustainment of USW DSS for both afloat and ashore use cases. The

TSRA shall:

o Serve as the foundational element for the development of an effective and integrated training solution that supports mission readiness and performance objectives.

o Evaluate operational tasks, system capabilities, and user roles to determine the scope and nature of required training.

o Decompose mission-critical tasks into subtasks and performance standards to identify training gaps and instructional requirements.

o Characterize target learner populations by experience level, job function, and learning preferences to inform instructional design.

o Develop measurable learning objectives aligned with operational performance standards and system functionality.

o Assess and recommend appropriate training media (e.g., instructor-led, eLearning, simulation) and delivery platforms based on cost, effectiveness, and scalability. Identify technical and functional requirements for integrating training systems with operational platforms, Learning Management Systems (LMS), and other support infrastructure.

o Ensure training solutions meet applicable standards, including DoD Instructions, cybersecurity protocols, and accessibility requirements.

• Personnel: The contractor shall provide personnel available in the San Diego, Norfolk, Mayport, Pearl Harbor, Everett, Yokosuka, and Rota area to conduct modernization training onboard ships that are receiving a new USWDSS variant. The modernization training for Base Year includes, but is not limited to, modernization training events lasting 1-3 weeks to include basic system familiarization training, which addresses the training gap between schoolhouse curriculum and the specific shipboard content received.

o The contractor shall provide personnel available in the San Diego, Norfolk, Pearl Harbor, Everett, Yokosuka, Italy and Bahrain area to conduct modernization training onboard

TUSWCs that are receiving a new USWDSS variant. The modernization training for

Base Year includes, but is not limited to, modernization training events lasting 1-3 weeks to include basic system familiarization training, which addresses the training gap between schoolhouse curriculum and the specific shipboard content received.

• Configuration: The contractor shall review the configuration of the equipment for the new USW

DSS system and perform an analysis of the tasks required for active duty personnel to perform maintenance (preventive, corrective, trouble shooting), classify the tasks by the knowledge/skill

Page 18 of area, and recommend personnel level when unique requirements are identified. The contractor shall provide curriculum development and cadre training support to SCSTC San Diego in San

Diego, CA and Information Warfare Training Detachment, San Diego, CA. The contractor shall interface with fleet representatives and the Training Manager in scheduling training for active duty personnel. The contractor shall assist SCSTC San Diego in the modification of formal course material based on the results of the Training System Requirements Analysis.

3.7 Installation Support

The Contractor shall design and develop technical engineering services for installation support on

Continental Unites States (CONUS) and Outside Continental Unites States (OCONUS) locations. Support shall include installation of software upgrades or reloads, hardware upgrades, new systems, training systems, and development/test systems at both afloat and ashore platforms.

3.8 Procurement of Commercial Off-The-Shelf…