SSG Draft SOW.docx

Synthetic Signature Generation (SSG) Services

DRAFT STATEMENT OF WORK

The information herein is provided for market research purposes. The information reflects the most current information available, but is subject to change based on market research responses received. Potential offerors who are interested in this procurement are strongly encouraged to fill out a market research questionnaire and provide feedback on the draft Statement of Work requirements. The Government is particularly interested in identifying any requirements that industry believes are overly restrictive.

1.0 SCOPE

1.1 INTRODUCTION

Naval Surface Warfare Center Carderock (NSWCCD) Fleet Signatures Systems Division’s (Code 76) mission is to design, develop, and support systems used for the measurement, acquisition, processing, and analysis of ship signature data. Code 76 designs hardware and software for signature characterizations, signal processing, signal imaging, and advanced algorithm development. Advanced, unconventional signal processing techniques are used to assess the vulnerability of ship signatures for exploitation by threat sensors. In addition, Code 76 designs, develops, and supports the operating fleet’s signature data collection, processing, and analysis systems, thereby ensuring commonality and interchangeability of data and systems.

1.2 BACKGROUND

This Statement of Work (SOW) provides scientific, engineering, and technical services required for the design, development, fabrication, integration, test, fleet implementation, and maintenance of Synthetic Signature Generation (SSG) based simulation systems. The Government requires support system installations and updates required for the following five categories of Navy fleet training systems: Submarine Team, Navigation, Surface, Surveillance, and On-Board. The Government requires design, development, integration, testing, delivery, installation, and maintenance of fielded systems. The Government requires technical engineering support for simulation and training system capabilities to existing fleet on‐site maintenance personnel for the operational systems. The Government also requires support for tactical testing and analysis system configurations for common simulation and tactical subsystems utilized in these trainers. Developed systems must provide combat system training capability fielded in conjunction with tactical system updates to fleet units. Each of the training systems is described in Section 4.

The Government requires work with the Tactical Systems Integrator, the Acoustic and Visual Simulation Developer and the Signature Trainers Scenario Control (STSC) Developer (separately contracted efforts) as part of an Integrated Product Team (IPT) led by the Government Program Manager (PM). The Tactical Systems Integrator develops tactical sonar configuration to be utilized within fleet training systems, as well as the hardware and software interfaces for the tactical sonar systems to be integrated into the training, testing, and analysis systems. For shore trainers, the Tactical Systems Integrator provides the Government with the tactical system configuration, interface hardware, and interface software required to join the stimulations and the tactical system as Government Furnished Property (GFP) for use by the Contractor. The Acoustic and Visual simulation Developer provides software development builds utilizing the All World Environment Simulation (AWESIM) and Periscope Simulation (PSIM) software baselines to meet Fleet training requirements for simulation of acoustic and imaging tactical systems. The STSC Developer provides Acoustic Instructor Control (AIC) development builds required to build, edit and run training scenarios.

IPTs are utilized to coordinate training system development across program office, warfare center, contractors, and representatives. The Government requires participation and support in the IPT process, as well as documentation of the process and decisions in support of SSG trainers.

Training systems installations and updates shall follow the process in OPNAVINST 1500.76D for preparation of Training System Installation Plans (TSIPs). Development and delivery of documentation of fielded systems will be required to support the TSIP process for acceptance of fleet training systems by the training command.

2.0 APPLICABLE DOCUMENTS

The following documents are provided as attachments in Section J, or are available upon request during performance of the contract:

OPNAVINST 3502.5C

(22 APR 2025)

Policy For Managing the Life Cycle Support of the Submarine Training System Program

OPNAVINST 1500.76E

(14 MAY 2025)

Navy Systems, Training Requirements, and Management

MIL-STD-31000C

(3 FEB 2025)

Department of Defense Standard Practice Technical Data Packages

DoDM 8140.03

(15 FEB 2023)

Cyberspace Workforce Qualification and Management Program

DoDM 8570.01 (Change 4, 10 NOV 2015) Information Assurance Workforce Improvement Program

CARDEROCKDIVINST 5510.12A

(13 MAR 2025)

Classified Information Systems Removable Media Policy

3.0 ACRONYMNS

4.0 REQUIREMENTS

4.1 GENERAL REQUIREMENTS

The Contractor shall perform the following general contract requirements to support the technical requirements in Section 4.2.

4.1.1 COLLABORATIVE DEVELOPMENT ENVIRONMENT

To ensure the program’s continued success, the Contractor shall work collaboratively with a consortium of Government (including U.S. Navy and Navy Laboratories), industry partners, and Academia. The Contractor shall participate in and support the SSG training system IPT process across NSWCCD management and systems engineering team, tactical integration team, and simulation integration team and in support of fielding and maintenance of completed SSG training systems to fleet sites.

4.1.2 INTEGRATED DATA ENVIRONMENT

The Contractor shall utilize an integrated (electronic) data environment for electronic exchange of contract-related data and data products. The data environment may be Government provided, Contractor provided, or a combination of both. For the Government-provided data environment segments, the Contractor shall abide by all access control regulations and policies. For Contractor-provided segments, the Contractor shall provide the Government, authorized contractors, and designated program teammates electronic access to that segment of the integrated development environment throughout the term of the contract.

Controlled Unclassified Information (CUI), Security Classification Guides (SCG), and other distribution statement-controlled documents, are not authorized for public release and cannot be placed on a publicly accessible web site or web server. The Contractor shall digitally sign all emails containing such information or attachments if transmitting within Navy networks, and digitally sign and encrypt if transmitting outside a Navy network to an approved contractor email address. The Contractor is strictly prohibited from transmitting CUI to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.).

4.1.3 DESIGN, DISCLOSURE, INTELLECTUAL PROPERTY AND DATA RIGHTS

The contractor shall utilize and maintain a process that provides design disclosure directly to authorized third party developers via electronic access to in-process design documentation and computer test software for all software to be developed or updated under this contract. The contractor shall support an open-source initiative with other participants within the Signatures Training Systems development community.

4.1.4 INTEGRATED PRODUCT TEAM PARTICIPATION

The Contractor shall participate in IPTs. The Contractor shall support the Government in developing IPT charters. These IPTs shall integrate schedule and performance data to provide a global perspective with detailed insight into the managerial and technical aspects impacting Government and industry. The Contractor shall provide representatives to each IPT with the appropriate level of expertise and degree of authority and responsibility to make decisions on behalf of the Contractor.

IPT support shall also include coordination with other on‐site signature decision systems contractor personnel operating in support of Code 73 programs to ensure effective coordination of Carderock facilities, hardware and software systems. As part of the IPTs, the Contractor shall perform the following functions:

a. Monitor and report subsystem status and program.

b. Identify, collect, analyze, and report appropriate metrics for measurement of cost/schedule contract, engineering, and production progress.

c. Jointly evaluate and manage resolution of major issues (including obsolescence) associated with hardware and software engineering, integration, test, and installation activities.

d. Verify that data provided by the contractor’s design disclosure process to third party developers is current, complete, and accurate.

e. Jointly evaluate and manage configuration management and maintenance of training systems development networks and Engineering Development Models (EDMs) at NSWCCD; and

f. Additional functions as determined by the specific IPT charter.

4.1.5 PROBLEM REPORTING SYSTEMS

If a Government-provided system is not available, the Contractor shall utilize a commercially available software issue tracking system (e.g., Jira) to track Problem Trouble Reports (PTRs) for the identification, tracking, and resolution of all hardware, software, integration, and logistics problems or deficiencies. The Contractor shall provide the Government, authorized contractors, and designated program teammates electronic access to its software issue tracking system and associated project data throughout the term of the contract. Where supported program offices have existing problem tracking systems for embedded training systems capabilities within sonar and combat systems, the Contractor shall track and correlate all externally documented test problems back to the common issue task tracking system.

4.1.6 INFORMATION ASSURANCE (IA)

The Contractor shall implement and apply safeguards for information and information technology (IT) resources in accordance with the specifications provided in the Contract Security Classification Specification (DD FORM 254). The information and IT resources must be maintained at an appropriate level of confidentiality, integrity, availability, authentication, and non-repudiation based upon mission criticality, level of required IA and classification or sensitivity level of information entered, processed, stored, or transmitted for Navy Systems. The Contractor shall support and maintain the signature simulations development networks and EDMs in compliance with cybersecurity accreditation and maintenance procedures. The Contractor shall safeguard information and information systems using multi-disciplined defensive layers, as well as sound administrative and operational practices. The Contractor shall provide security data management for all classified media supporting signatures trainers programs and manage all material utilized for signature trainer programs on-site at NSWCCD via Code 764 classified Base Inventory Tracking System (BITS) satellite library. All personnel preforming IA/ Cyberspace workforce (CWF) duties shall be fully qualified upon the start of the period of performance and maintain their certifications throughout the life of the contract.

4.2 TECHNICAL REQUIREMENTS

To support the entire range of potential tasks envisioned under this contract, this section of the SOW supports the conduct of design, development, integration, testing, and technology insertion (TI)/refreshment, engineering services, field engineering services, and system support. The services identified in this section of the SOW shall be as tasked under specific task orders (TOs) executed during performance of this contract.

4.2.1 TASK AREA 1: SUBMARINE TEAM TRAINER SUPPORT

Support of Submarine Team Trainers shall include system development and updates for the Submarine Multi‐Mission Team Trainer (SMMTT), Common Operational Analysis and Employment Trainer (COAET), Sonar Employment Trainer (SET), with fielding to fleet training sites in Norfolk, VA; San Diego, CA; Groton, CT; Pearl Harbor, HI; Bangor, WA; Kings Bay, GA; Guam; Australia; Suitland, MD; Orlando, FL; Manassas, VA; Bethesda, MD; and Newport, RI, Visual simulation subsystems are also used in support of BYG-1 trainers for the Royal Australian Navy (RAN) in Freemantle, AUS. Submarine simulation and training configurations are also supported for Acoustic Intelligence (ACINT) specialist training at the Office of Naval Intelligence (ONI) in Suitland, MD and testing and analysis configurations at navy labs and tactical systems integrator sites. Submarine Team Training Systems are developed and delivered for PEO UWS TR, AUKUS and Columbia Program Offices.

The contractor shall manage and support SSG based systems for Submarine fleet training, testing, and analysis for shore‐based trainer configurations.

4.2.1.1 The contractor shall investigate, design, and develop new and improved submarine simulation capabilities and training system configurations for improving trainer realism and in support of new tactical system sensors and capabilities being implemented in the fleet. Simulation improvements shall be designed to support common application across fleet training, testing, and analysis systems.

4.2.1.2 The contractor shall engineer, procure, and produce training systems configurations and provide upgrade and modification of fleet systems. Systems engineering support shall include testing and verification of trainer configurations with support for systems and software delivery to systems integrators and installation at fleet training sites.

4.2.1.3 The contractor shall maintain simulation and training systems for submarine team trainer configurations and provide TIs and engineering modifications to update and improve testing, analysis, and training configurations of submarine configurations.

4.2.2 TASK AREA 2: NAVIGATION TRAINER & VISUALIZATION SUPPORT

Support of Navigation Trainers shall include development and updates for the Submarine Bridge Trainer (SBT), and Integrated Submarine Piloting and Navigation (ISPAN) trainer and Virtual Reality Submarine (VRSub) configurations. Submarine navigation trainers are installed in common Submarine Learning Facility locations with the Submarine Team Trainers. Travel for system integration testing is also required for Navigation trainers in Newport, RI and Orlando, FL.

The contractor shall manage and support SSG based systems for Navigation Trainers and Visual Simulation systems required for Navy training, testing, and analysis configurations.

4.2.2.1 The contractor shall investigate, design, and develop new and improved visual simulation capabilities and navigation training system configurations for improving trainer realism and in support of new tactical system sensors and capabilities being implemented in the fleet. Simulation improvements shall be designed to support common application across fleet training, testing, and analysis systems.

4.2.2.2 The contractor shall engineer, procure, and produce visual simulation and navigation training system configurations and provide upgrade and modification of fleet systems. Systems engineering support shall include testing and verification of trainer configurations with support for systems and software delivery to systems integrators and installation at fleet training sites.

4.2.2.3 The contractor shall maintain visual simulation and navigation training system configurations and provide TIs and engineering modifications to update and improve testing, analysis, and training configurations.

4.2.3 TASK AREA 3: SURFACE TRAINER SUPPORT

Support of surface ship trainer configurations are required for the Combined Integrated Air Missile Defense (IAMD) and Anti-Submarine Warfare (ASW) Trainer (CIAT) and the ASW Tactical Employment Trainer (ATET) which shall field to fleet training sites in Dahlgren, VA; San Diego CA; Norfolk, VA; Mayport, FL, Pearl Harbor, HI; Spain; and Japan.

The contractor shall manage and support SSG based simulation systems for ASW and Combat System Surface Ship Trainers required for Navy training, testing, and analysis configurations.

4.2.3.1 The contractor shall investigate, design, and develop new and improved simulation capabilities and surface ship training system configurations for improving trainer realism and in support of new tactical system sensors and capabilities being implemented in the fleet. Simulation improvements shall be designed to support common application across fleet training, testing, and analysis systems

4.2.3.2 The contractor shall engineer, procure, and produce simulation and surface ship training system configurations and provide upgrade and modification of fleet systems. Systems engineering support shall include testing and verification of trainer configurations with support for systems and software delivery to systems integrators and installation at fleet training sites.

4.2.3.3 The contractor shall maintain simulation and surface ship training system configurations and provide TIs and engineering modifications to update and improve testing, analysis, and training configurations.

4.2.4 TASK AREA 4: INTEGRATED UNDERSEA SURVEILLANCE SYSTEM (IUSS) TRAINER SUPPORT Support of Integrated Undersea Surveillance System (IUSS) trainer configurations are required for the Surveillance Towed Array Sensor System (SURTASS) Team Trainer (STT) and the Integrated Common Processor Training Device (ICPTD) which supports towed and fixed sensor sonar training at Whidbey Island, WA and Dam Neck, VA with integration testing support in Manassas, VA. Surveillance training systems configurations also require integration of common AWESIM acoustic simulation for stand-alone training applications.

The contractor shall manage and support SSG based simulation systems for IUSS Trainers required for Navy training, testing, and analysis configurations.

4.2.4.1 The contractor shall investigate, design, and develop new and improved simulation capabilities and IUSS training system configurations for improving trainer realism and in support of new tactical system sensors and capabilities being implemented in the fleet. Simulation improvements shall be designed to support common application across fleet training, testing, and analysis systems.

4.2.4.2 The contractor shall engineer, procure, and produce simulation and IUSS training system configurations and provide upgrade and modification of fleet systems. Systems engineering support shall include testing and verification of trainer configurations with support for systems and software delivery to systems integrators and installation at fleet training sites.

4.2.4.3 The contractor shall maintain simulation and IUSS training system configurations and provide TIs and engineering modifications to update and improve testing, analysis, and training configurations.

4.2.5 TASK AREA 5: ON-BOARD TRAINER SUPPORT

Support for embedded on-board training systems includes updates to the Surface ASW Synthetic Trainer (SAST) which is developed as a subsystem of the AN/SQQ-89 A(V)15 sonar. This also includes support of Foreign Military Sales (FMS) configurations of the AN/SQQ-89 A(V)15 under program office direction. Submarine simulation and training configurations also support embedded on-board training configurations of the AWESIM acoustic simulation on submarines within the AN/BQQ-10 sonar and PSIM visual simulation within the AN/BVY-1 Integrated Submarine Imaging System and AN/BYG-1 Combat Control System. Embedded acoustic simulation capabilities are also supported within the ICP surveillance sonar system. System integration and testing configurations for these systems must be supported in Bethesda, MD; Dahlgren, VA; Newport, RI; Manassas, VA; and program designated integration and testing sites.

The contractor shall manage and support SSG based simulation systems for on-board trainers embedded within fleet tactical systems required for Navy training, testing, and analysis configurations.

4.2.5.1 The contractor shall investigate, design, and develop new and improved simulation capabilities and on-board training system configurations for improving trainer realism and in support of new tactical system sensors and capabilities being implemented in the fleet. Simulation improvements shall be designed to support common application across fleet training, testing, and analysis systems.

4.2.5.2 The contractor shall engineer, procure, and produce simulation and on-board training system configurations and provide upgrade and modification of fleet systems. Systems engineering support shall include testing and verification of trainer configurations with support for systems and software delivery to systems integrators and support for validation within tactical sites.

4.2.5.3 The contractor shall maintain simulation and on-board training system configurations and provide TIs and engineering modifications to update and improve testing, analysis, and training configurations.

4.2.6 TASK AREA 6: COORDINATED SIMULATION SYSTEMS SUPPORT

The contractor shall manage and support SSG based simulation systems, trainers, testing, and analysis configurations leveraged from submarine, surface, and surveillance training system configurations. This includes engineering support of SSG Trainers utilized for training of ONI ACINT specialists, acoustic and environmental analysts, and ASW air platforms requiring coordinated and common acoustic and visual simulation with the Navy strike group platforms they are supporting. The contractor shall investigate, design, and develop new and improved simulation capabilities and training system configurations for improving trainer realism and in support of new tactical system sensors and capabilities being implemented in the fleet. Simulation improvements shall be designed to support common application across fleet training, testing, and analysis systems.

4.2.6.1 The contractor shall engineer, procure, and produce simulation and training system configurations and provide upgrade and modification of fleet systems. Systems engineering support shall include testing and verification of trainer configurations with support for systems and software delivery to systems integrators and support for validation within tactical systems.

4.2.6.2 The contractor shall maintain simulation and training system configurations and provide TIs and engineering modifications to update and improve testing, analysis, and training configurations.

4.2.6.3 The contractor shall provide acoustic signature analysis for support of developing realistic representations of the threat signature characteristics as seen through current navy sonar systems and sensors. The contractor shall provide an individual capable of attending ONI ACINT Mission Briefings for understanding and modeling of target characteristics appropriate to combat systems team training requirements. This individual shall require a Top Secret (TS) clearance to be utilized when attending meetings at ONI in Suitland, MD.

4.3 OTHER TECHNOLOGY SUPPORT SERVICES

The contractor shall provide the following support services in direct support of the SSG training systems implemented and maintained under sections 4.2 above.

4.3.1 GRAPHICAL USER INTERFACES (GUIS)

The Contractor shall investigate, recommend, design, and implement GUIS in support of SSG trainer startup, shutdown, maintenance and troubleshooting.

4.3.2 SOFTWARE ENGINEERING MANAGEMENT

The Contractor shall provide software engineering management in support of trainer products. This shall include planning the development and release of trainer systems; documenting trainer systems; designing and implementing automated requirements tracking and trouble tracking capabilities; and planning future interfaces with external systems. The Contractor shall utilize task tracking software, such as Jira and Confluence, for proper documentation and tracking of requirements, development tasks, software and system corrections, and installation of systems.

4.3.3 SOFTWARE MAINTENANCE

The contractor shall conduct software maintenance in support of SSG trainer systems. The contractor shall extend the AWESIM and PSIM software baseline for maintenance of the acoustic and visual simulation integrated into SSG trainer systems. This shall include system administration and configuration management support. It also shall include the implementation and documentation of all IA requirements. The contractor shall support maintenance and administration of Jira and Confluence software systems in support of all NSWCCD Prototype Development Facility (PDF) systems and projects.

4.3.4 HARDWARE MAINTENANCE

The contractor shall conduct hardware preventive maintenance, hardware repair, installation, parts sparing, parts inventorying, and shipping to support delivered and development SSG Trainer systems. The contractor shall also support tracking of hardware supporting all development and production systems. It also shall include the implementation and documentation of all IA requirements and PDF network maintenance to acquire and maintain IA accreditations.

4.3.5 SYSTEM INFORMATION ASSURANCE (IA)

The contractor shall provide IA support, maintenance, and configuration control for the SSG trainer development systems located at NSWCCD, contractor development facilities and fleet site installations prior to turnover. The contractor shall provide system/network administration support as appropriate, to include network and system administration support, server and workstation setup, maintenance support, patch management, and scanning and remediation of systems for IA testing to support approval and maintenance of SSG trainer development and fielded systems. Support shall include the implementation and documentation of all IA requirements for delivered SSG trainer systems and SSG trainer development systems. The contractor shall ensure that IA is provided for SSG Trainer systems in accordance with all current Department of Defense (DoD) and Department of Navy (DoN) policies, procedures, and statutes. The contractor shall provide tracking and support of Certification and Accreditation (C&A) efforts, support for IA Workforce management, and overall coordination of IT/IA approvals for SSG trainer systems. The contractor is further responsible for ensuring that the certifications and certification status of all contractor personnel performing IA functions as described in DoD 8570.01‐M (IA Workforce Improvement Program) are in compliance with the manual and are identified, documented, and tracked. Support shall also include training materials and presentation to ensure all prime contractor and subcontractor personnel are compliant with security and IA policies for NSWCCD facilities.

4.3.6 SOFTWARE ENGINEERING

The contractor shall provide general software engineering support for the design, prototyping, and implementation of SSG trainer products. This shall include proper documentation of software coding and use of software configuration management tools to ensure all software modifications are managed and committed to source code repositories at NSWCCD.

4.3.7 SOFTWARE INTEGRATION AND TESTING

The contractor shall provide both onsite and offsite software integration and testing support for SSG trainer products. This shall include delivery of test plans for system builds and deliveries and shall also include documentation of completed testing and concurrence by Navy representatives.

4.3.8 INTELLIGENCE INFORMATION SUPPORT

The contractor shall provide intelligence services to access threat acoustic intelligence information to generate and maintain threat databases for use in signature simulation systems. Contractor personnel must ensure data used in surface, submarine, surveillance, and similar signature simulation systems includes real world data and reference to events while maintaining control of sensitive information. The contractor shall provide personnel with a Top Secret security clearance to support roughly a full-time equivalent (FTE) with knowledge of threat signatures, capabilities, and characteristics in support of simulated threat development for combat systems trainers.

4.3.9 FLEET TRAINING

The contractor shall provide training services to the Fleet in support of products they have developed for the trainers. This shall include both system and operational training for turn-over and acceptance of new or updated training systems capabilities.

4.3.10 TRAINING CONTENT

The contractor shall develop training content for training systems. This shall consist of basic, intermediate, and advanced training for both officer and enlisted personnel. Content may consist of introduction, explanation, scenario development, testing, and remedial training. Training content may also consist of development of refresher training for compliance with Navy facilities, hardware inventory, IA, or security policies.

4.3.11 PROGRAM SUPPORT

The contractor shall provide administrative, budgetary, and presentation support for development and fielding of SSG training systems. The contractor shall provide technical system engineering analysis, review and liaison for hardware and software of training facility trainer/training systems. The contractor shall provide technical scope presentations in support of program office requests for SSG training. The contractor shall provide impact analysis reports for all SSG training systems, hardware and software describing technical progress, and identification of potential problem areas. Documentation of system deliveries shall include at a minimum program office designated approvals such as TSIP for fielded SSG training support.

4.4 FLEET TRAINING SYSTEM DOCUMENTATION REQUIREMENTS

The contractor shall provide the following documentation and reports in direct support of the SSG training systems implemented and maintained under sections 4.2 above.

4.4.1 SYSTEM SPECIFIC DOCUMENTS

System specification documents shall be provided for documentation of system capabilities and new development by individual TOs. These are expected to include a Software Development Plan (SDP) describing the planned development of new system functionality; the System/Subsystem Specification describing the system level requirements; the Software Requirements Specification detailing the primary software module design and implementation requirements; and the Interface Requirements Specification detailing the internal and external interface requirements within software modules and with external subsystems.

4.4.2 SYSTEM DELIVERABLE DOCUMENTS

System deliverable documents shall be provided for documentation and delivery of fleet installations by the individual TOs. These are expected to include a Software Product Specification which shall summarize the capabilities of the delivered product; Test Procedures utilized to validate system performance prior to and again during installation; Test/Inspection Report which shall document results of testing and deficiencies; and Training System Installation Plans for coordination of program office, trainer developer, and fleet training site. Software version description (SVD) must be identified and describe the software version consisting of one or more Computer Software Configurations Items (CSCI’s) for use of release, track and control of software version.

System Deliverable Documents shall include an installation summary report with all Navy signed documents indicating successful testing and acceptance of the fielded systems back to the Government PM and Contracting Officer’s Representative (COR) upon completion of trainer installations or primary updates.

4.4.3 TECHNICAL REPORTS

Technical reports (CDRL A002) may be required for system or data analysis. This shall also include maintaining and updating Prototype Development Network and EDM hardware and network documentation and configuration management.

4.4.4 SYSTEM AND SOFTWARE TECHNICAL DOCUMENTATION

Existing Technical Data Package (TDP) documentation shall be updated and maintained under this contract (CDRL A015). Technical documentation shall be provided to clearly document simulation and training system software architecture and implementation. This documentation shall include physical system architecture to include hardware and networking interfaces, dependencies, and configurations. This documentation shall also include all software subsystem architecture, functionality, internal, and external interfaces. Technical documentation for new training system configurations developed under this contract shall be provided at a level to allow Government modification and configuration management of existing and future software upgrades. Each new training system configuration developed under this contract shall require a new delta TDP to define any changes in system or software design and implementation from the baseline and current TDP packages for that training system variant.

The contractor engineering team shall provide TDP content, and the contractor shall provide appropriate technical writing, technical editing, graphics, and desktop publishing by the editing team to complete the documentation package and maintain format consistency with existing TDP documents.

Delivery schedules for TDP package updates shall be specified in the TOs and to support “as-built” documentation shall follow the initial installation of a new training system configuration. An average delta TDP package for a new training system configuration can be estimated at 185 pages and an average of six TDP packages per year are expected based on historical estimates and anticipated build schedules across the five types of trainer configurations supported under this contract.

The TDP for each Trainer Build shall provide the Technical Product details with design and implementation documented at the system and subsystem level to provide sufficient insight into the system and software architecture to allow new developers to support future maintenance and updates of these complex training systems. TDP documents shall reference the government furnished baseline documentation and TDPs for subsequent builds shall document the differences which are specific to the updated build or platform configuration as compared to the reference. Only the differences to the referenced TDP need to be documented. In a TDP's delivery, the referenced material does not need to be included in either the electronic or the hard copy submission.

4.5 PROGRAM MANAGEMENT

4.5.1 PROGRAM MANAGEMENT STRUCTURE

The contractor shall appoint a primary Program Manager (PM) to act as the focal point for communications between the contractor and Government. The PM shall have overall responsibility for accomplishing the efforts under each TO. To support the coordinated training system development efforts across submarine and surface/surveillance program offices supported under this contract, the contractor shall provide senior PMs assigned to each of these domains. Based on the scope of the tasking the PM shall assign designated Project Leads to support program and technical management support for each project who shall be responsible for coordination of tasking from the development teams and tracking of all external dependencies required to meet program deliverables and schedules. Development team leaders shall be required to support a minimum of Acoustic Simulation, Visual Simulation, and Systems Engineering development teams. Integration leads shall be assigned to coordinate project integration and testing events.

4.5.2 INTEGRATED PROGRAM MANAGEMENT

The contractor shall perform business management functions to ensure contracting related actions are provided for production orders that meet established need dates of the Government.

The contractor shall provide internal management functions, including technical direction, risk management, administration, and planning for all activities within this contract. The contractor shall provide program planning, budget allocations, cost control, cost estimates, and status reporting for tasks associated with this contract. The contractor shall be responsible for coordination with the Contracting Officer, Program Office, and other agencies in the execution of this contract.

4.5.3 PROGRESS, STATUS AND MANAGEMENT REPORT

The contractor shall maintain technical and financial status and generate Progress, Status, and Management Reports. The financial status shall include the Estimate at Completion (EAC), Actuals to Date (ATD), Estimate to Complete (ETC), amount funded, and outlooks for when additional funding is required for tasks as identified in the TOs. Status shall contain the current status of all orders including required, estimated, and actual delivery dates. Monthly status shall include technical status and progress of tasks toward deliverables and identification of risk areas. Content for technical reporting can be coordinated with data documented through the electronic Integrated Data Environment (IDE).

4.5.4 TASK TRACKING

The contractor shall support requirements analysis efforts across programs supported under this contract and shall maintain task decomposition and task tracking. An existing signature training system data environment utilizing Atlassian Jira and Confluence software packages shall be provided as GFI. The contractor shall support the hosting and maintenance of the Jira task tracking database with access provided to contractor personnel on the development team, along with Government, and partnering contractors and organizations as approved via the NSWCCD COR and PM. Resource planning and schedule tracking shall be correlated across the program portfolio, project teams, and development teams to track tasking and progress of execution at the software and system development level. Monthly financial and technical reporting shall be supported by Jira task tracking data. The contractor shall update and maintain the Jira tracking data during the execution of the contract and report status in weekly management meetings.

4.5.5 PROGRAM PLANNING

The contractor shall develop, maintain, and deliver original and revised Task Management Plans (CDRL A003) for all contract efforts, planned events, milestones, and activities related to each project delivery. Each trainer build shall include resourcing and scheduling for interim integration events to support periodic development testing prior to final build and performance verification testing.

4.5.6 REVIEWS

The contractor shall coordinate, schedule, prepare for, conduct, facilitate, participate, and host reviews, meetings, and conferences. The contractor shall provide agendas (CDRL A004), presentation materials (CDRL A005), action items, action item status, and meeting minutes (CDRL A006). The agendas and meeting minutes shall be reviewed jointly between the Government and contractor and distributed electronically by the contractor. Minutes of the meetings shall be kept by the contractor unless otherwise directed by the Government. Minutes shall include a summary of discussions, copies of handouts or graphics, and a listing of action items, and shall be distributed electronically.

The contractor shall develop and maintain an action item status and tracking system for all reviews to ensure actions are assigned to specific individuals, due dates are established, and accurate status is provided to the Government.

The contractor shall support sponsor program reviews by supported training system program offices (expected once every three months per major submarine, surface, and surveillance system program office). The contractor shall support monthly program management meetings regarding contract status. These reviews shall be used to assess the contractor’s progress and status and provide review of financial reporting to assess cost and schedule performance. Technical management meetings shall occur weekly and rotate on a tri-weekly schedule to cover submarine program status, surface program status, and development team status.

For the tri-weekly technical reviews, the contractor shall provide, at a minimum, comprehensive status of:

a. Design and technical issues

b. Integration and interoperability issues

c. Hardware and computer software engineering

d. Risk analysis activities

e. Test and evaluation activities

f. Development and EDM facility status

g. Accreditation status and maintenance efforts

h. Installation planning

i. Logistics development and support efforts

j. Configuration management activities for software, hardware, and data

For the monthly program management and financial reviews, the contractor shall provide at a minimum, comprehensive status of:

a. Efforts authorized under delivery and TOs

b. Manpower utilization projection/actual (three-month history, nine-month future)

c. Review of remaining funding and expected burn rates of funding and labor hours

d. Review and any invoicing questions from the COR

e. Data items delivery schedule

f. Government Furnished Property/Information (GFP/I) status

5.0 DELIVERABLES

5.1 The Contractor shall provide the following deliverables with this effort. Deliverables under the TOs shall be provided in accordance with the Contract Data Requirements Lists (CDRL, DD Form 1423) and supporting Data Item Descriptions (DIDs). All CDRLs are provided as an attachment in Section J.

5.2 The Contractor shall deliver to the Government all systems, equipment, other hardware, software, and technical data procured or developed under this contract at the completion of the TOs, unless otherwise specified.

6.0 PLACE OF PERFORMANCE

The principal place of performance shall be the NSWCCD (West Bethesda, MD) and the contractor facilities for all work at or below SECRET. The Government will provide Contractors working at Government facilities identification/access cards, a workstation (desk, computer) with access to the internet, printer, facsimile, and telephone line, for official use. The contractor must have facilities within 35 driving miles or1 hour commute time, whichever is greater, of NSWCCD, which meets the safeguarding requirements specified by DD FORM 254. The facilities shall be 8,000 square feet or greater, consisting of large-scale computer system development, storage and shipping spaces. The facility shall have at least 12 Kilovolt-Amperes (kVA) of uninterruptable power supply and 150 tons of nominal cooling.

7.0 SECURITY REQUIREMENTS

7.1 The attached DD Form 254, DoD Contract Security Classification, itemizes the security classification requirements for this contract. All key and non-key Contractor personnel supporting these TOs must have at least a current SECRET clearance. Specific person may require TOP SECRET clearance, as specified in the Personal Qualifications (Section J, Attachment XX).

7.2 The Contractor shall not disseminate or publicly disclose any information provided by the Government developed under this TO, or relating to the items to be delivered and services to be performed without the Contracting Officer’s (CO’s) prior approval. Dissemination or public disclosure includes permitting access to such information by anyone without proper clearance and need to know, including any foreign nationals, publication of technical or scientific papers, advertising, or any other proposed public release. The Contractor shall physically protect such information to prevent access by any unauthorized person or entity.

7.3 The Contractor shall require Secret Internet Protocol Router Network (SIPRNet) to access and communicate classified information associated with the TO.

7.4 The Contractor shall require access to Alternative Compensatory Control Measures (ACCM) data and documentation as part of the contract tasking. The government shall specify the data and documentation which require ACCM access, and with government concurrence, contractor personnel with verified need to know will be trained and granted ACCM access.

8.0 TRAVEL

8.1 Contractor personnel may be required to travel to US Navy ships, shipyards, Government facilities, and other Contractor facilities in the Continental United States (CONUS) and Outside the Continental United States (OCONUS). Locations will be determined by the Government and are subject to change. Contractor personnel performing services OCONUS shall maintain a valid U.S. Passport with no fewer than six months remaining until expiration.

1. CONUS Travel includes, but is not limited to:

a. Norfolk, VA

b. San Diego, CA

c. Groton, CT

d. Bangor, WA

e. Kings Bay, GA

f. Suitland, MD

g. Dahlgren, VA

h. Mayport, FL

i. Orlando, FL

j. Whidbey Island, WA

k. Dam Neck, VA

l. Manassas, VA

m. Bethesda, MD

n. Washington, DC

o. Newport, RI

2. OCONUS Travel includes, but is not limited to:

a. Pearl Harbor, HI

b. Guam

c. Australia

d. Japan

e. Spain

8.2 The Contractor shall coordinate travel with the COR, and obtain authorization for travel from the COR prior to incurring any travel costs. Actual travel expenses will be permitted in accordance with the Joint Travel Regulations (JTR) and must be pre-approved by the COR. Estimates of travel costs that are proposed must be reviewed/ approved by the COR. A complete breakdown of all estimated travel charges shall be provided to the COR as requested. If approved, the COR will provide a written authorization to the Contractor to proceed with travel, provided travel funds exist for the task. Authorized travel costs incurred by the Contractor personnel in support of tasks issued hereunder are allowable and reimbursable in accordance with Federal Acquisition Regulation (FAR) 31.205-46.

9.0 TRANSITION PERIOD

A 60-to-90-day transition period is scheduled upon award (phase-in) and the 30-day period immediately prior to contract end date (phase-out) to allow for orderly contract transition. To maximize the effectiveness of the transition process, an initial meeting between the PCO (or its delegated representative) and Contract Managers for both contractors shall be held to address phase-in and phase-out requirements and responsibilities not later than five (5) days into the phase in/phase out period. Subsequent meetings will be held as determined by the PCO but not less than weekly thereafter.

9.1 PHASE-IN

During the phase-in period, incoming Contractor personnel will be permitted to observe current operations of the outgoing contractor and Government personnel pertaining to the contract.