N0016719R0002_Amendment_0004_Conform_Copy.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 15 Jan 2019

X

A X B X C X D

EX

X

G F 84 - 96

97 - 123 X H 124 - 132

JOHN.G.MULCAHY@NAVY.MIL

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

DO-C9 1 132

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

N00167 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and

Building 42, Room 302 conditions contained in this solicitation.

10. FOR INFORMATION

CALL:

A. NAME (NO COLLECT CALLS)

JOHN MULCAHY 301-227-1206

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 4

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

5 - 28

J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 32 - 37 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 38 - 43 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

44 - 81

PART II - CONTRACT CLAUSES

NAVAL SURFACE WARFARE CENTER CARDEROCK

CODE 0225, JOHN MULCAHY

301-227-1206, JOHN.G.MULCAHY@NAVY.MIL

9500 MACARTHUR BLVD

WEST BETHESDA MD 20817

301-227-1206

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

82 - 83

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

07 Nov 2018

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

N0016719R0002

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 420,480 Hours LOE Services

CPFF

Signature Trainer Support in accordance with the Statement of Work (SOW).

Fee shall be paid in accordance with Contract Clause HQ B-2-0015 Alternate I.

The Ordering Period for this CLIN is specified in Section F.

FOB: Destination

PSC CD: AC34

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

0002 1 Lot ODCs for CLIN 0001

COST

Other Direct Costs (ODCs) inclusive of materials and travel to support CLIN 0001.

The Ordering Period for this CLIN is specified in Section F.

PSC CD: AC34

0003 1 Lot Data

Data in accordance with the CDRLs (Exhibit A). Data is Not Separately Priced

(NSP).

The Ordering Period for this CLIN is specified in Section F.

CLAUSES INCORPORATED BY FULL TEXT

HQ B-2-0004 EXPEDITING CONTRACT CLOSEOUT (NAVSEA) (DEC 1995)

(a) As part of the negotiated fixed price or total estimated amount of this contract, both the Government and the Contractor have agreed to waive any entitlement that otherwise might accrue to either party in any residual dollar amount of $500 or less at the time of final contract closeout. The term "residual dollar amount" shall include all money that would otherwise be owed to either party at the end of the contract, except that, amounts connected in any way with taxation, allegations of fraud and/or antitrust violations shall be excluded. For purposes of determining residual dollar amounts, offsets of money owed by one party against money that would otherwise be paid by that party may be considered to the extent permitted by law.

(b) This agreement to waive entitlement to residual dollar amounts has been considered by both parties. It is agreed that the administrative costs for either party associated with collecting such small dollar amounts could exceed the amount to be recovered.

HQ B-2-0020 TRAVEL COSTS - ALTERNATE I (NAVSEA) (APR 2015)

(a) Except as otherwise provided herein, the Contractor shall be reimbursed for its actual travel costs in accordance with FAR 31.205-46. The costs to be reimbursed shall be those costs determined to be allowable, allocable and reasonable by the Procuring Contracting Officer, Administrative Contracting Officer or their duly authorized representative, as advised by DCAA.

(b) Reimbursable travel costs include only that travel performed from the Contractor's facility to the worksite, in and around the worksite, and from the worksite to the Contractor's facility.

(c) Relocation costs and travel costs incidental to relocation are allowable to the extent provided in FAR 31.205-35;

however, Contracting Officer approval shall be required prior to incurring relocation expenses and travel costs incidental to relocation.

(d) The Contractor shall not be reimbursed for the following daily local travel costs:

(i) travel at U.S. Military Installations where Government transportation is available,

(ii) travel performed for personal convenience/errands, including commuting to and from work, and

(iii) travel costs incurred in the replacement of personnel when such replacement is accomplished for the Contractor's or employee's convenience.

MINIMUM QUANTITY

In accordance with clause 52.216-22, the minimum quantity under this contract is 5,000 hours.

Section C - Descriptions and Specifications

STATEMENT OF WORK

1.0 INTRODUCTION

Naval Surface Warfare Center Carderock (NSWCCD) Signature Measurement Technologies and Systems Division’s (Code 73) mission is to design, develop, and support systems used for the measurement, acquisition, processing, and analysis of ship signature data. Code 73 is responsible for designing hardware and software requirements for signature characterizations, signal processing, signal imaging, and advanced algorithm development. Code 73 also assesses the vulnerability of ship signatures for exploitation by threat sensors utilizing advanced, unconventional signal processing techniques. Code 73 designs, develops, and supports systems used by the operating fleet support activities for the acquisition, processing, and analysis of signature data, while also ensuring commonality and interchangeability of data and systems. Additionally, Code 73 develops the techniques and processing for the collection, acquisition, processing, and analysis of signature data under deployed conditions by fleet personnel.

The scope of the effort discussed herein, shall require the contractor to provide scientific, engineering, and technical services required for the design, development, fabrication, integration, test, fleet implementation, and maintenance of Synthetic Signature Generation (SSG) simulation and training systems. These high fidelity fleet training systems requiring acoustic and visual simulation shall utilize and extend All World Environment Simulation (AWESIM) acoustic simulation and the Periscope Simulation (PSIM) visual simulation developed and maintained by NSWCCD for SSG applications in training, testing, and analysis systems. The contractor for this effort shall be designated as the Simulation and Training Systems Integrator (STSI).

2.0 SCOPE

Services provided through this contract require the contractor to support system installations and updates required for five categories of fleet training systems. This includes the Submarine Team, Navigation, Surface, Surveillance, and On-Board training systems. The contractor shall provide overall design, development, integration, test, delivery, installation, and maintenance support of fielded systems used to provide training for the Navy. The contractor shall provide technical engineering support for simulation and training system capabilities to existing fleet on‐site maintenance personnel for the operational systems. Common simulation and tactical subsystems utilized in these trainers are also required for support in some tactical testing and analysis system configurations.

Developed systems must provide combat system training capability fielded in conjunction with tactical system updates to fleet units.

1. Submarine Team Training Systems 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; Freemantle, Australia;

Suitland, MD; Orlando, FL; Austin, TX; 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. Travel to Austin, TX, may be required for subsystem integration events with the Applied Research Lab, University of Texas.

2. Navigation Training Systems

Support of Navigation Trainers shall include development and updates for the Submarine Bridge Trainer (SBT), Submarine Piloting and Navigation (SPAN) trainer, and Virtual Reality Sub (VRSUB) trainer configurations. Real-time visual simulation development utilizing the PSIM subsystem shall also be supported in surface ship and Unmanned Aerial Vehicle (UAV) applications leveraging the efforts of submarine navigation trainers. 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.

3. Surface Training Systems Support of surface ship trainer configurations are required for the Combined Integrated Air Missile Defense (IAMD), Anti-Submarine Warfare (ASW) Trainer (CIAT), and AN/SQQ89 Part Task Trainer (89 PTT) which shall field to fleet training sites in Dahlgren, VA; San Diego CA; Norfolk, VA; Mayport, FL, Pearl Harbor, HI; and Yokosuka, Japan. Additional surface trainer configurations utilizing common AWESIM acoustic simulation components and acoustic modeling components shall also support part task trainers for surface ship officer training.

4. Surveillance Training Systems

Support of Integrated Undersea Surveillance System (IUSS) trainer configurations are required for the Surveillance Towed Array Sensor System (SURTASS) Team Trainer (STT), the Integrated Common Processor Training Device (ICPTD), and the Sonar Target Injection (STI) which support 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.

5. On-Board Training Systems 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. 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 be required to work with the sonar Tactical Systems Integrator (TSI) (separately contracted effort) as part of an Integrated Product Team (IPT) led by the Government Program Manager (PM). The TSI will develop the 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 TSI shall provide 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 STSI.

IPTs shall be utilized to coordinate training system development across program office, warfare center, contractors, and fleet representatives. The contractor shall participate and support the IPT process and provide the appropriate documentation of process and decisions in support of SSG trainers.

Training systems installations and updates shall follow the process in OPNAVINST 11102.2 for preparation of Training System Installation Plans (TSIPs). The contractor shall be responsible for all development and delivery of documentation of fielded systems required to support the TSIP process for acceptance of fleet training systems by the training command.

3.0 Reference Documents

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

Document Name Description

DD FORM 254

(Apr 2018)

DOD CONTRACT SECURITY CLASSIFICATION SPECIFICATION

(Attachment 1)

OPNAV

INSTRUCTION

3502.5B

(16 MAY 2014)

POLICY FOR MANAGING THE LIFE CYCLE SUPPORT OF THE

SUBMARINE TRAINING SYSTEM PROGRAM (Attachment 2)

OPNAV

INSTRUCTION

11102.2

( 31 OCT 2007)

TRAINING SYSTEMS INSTALLATION AND TRANSFER (Attachment 3)

MIL-STD-31000A

(26 Feb 2013)

DEPARTMENT OF DEFENSE STANDARD PRACTICE TECHNICAL DATA

PACKAGES (Attachment 4)

DoD 8570.01‐M

(12 DEC 2017)

IA Workforce Improvement Program (Attachment 5)

TDP-TI10 SMMTT

(May 2016)

TECHNICAL DATA PACKAGE FOR TI10 SUBMARINE MULTI-MISSION

TEAM TRAINER (available upon request)

TDP-TI14 SMMTT

(August 2017)

TECHNICAL DATA PACKAGE FOR TI14 SUBMARINE MULTI-MISSION

TEAM TRAINER (available upon request)

TDP-SBT

(May 2017)

TECHNICAL DATA PACKAGE FOR SUBMARINE BRIDGE TRAINER

(available upon request)

TDP-ACB13 SAST

(March 2017)

TECHNICAL DATA PACKAGE FOR TI14 ACB13 SURFACE ASW

SYNTHETIC TRAINER (available upon request)

TDP-V1.1 CIAT

(July 2017)

TECHNICAL DATA PACKAGE FOR CIAT (available upon request)

TDP-TI10 STT

(March 2017)

TECHNICAL DATA PACKAGE for TI10 SURTASS TEAM TRAINER (available upon request)

4.0 GENERAL REQUIREMENTS

To support the entire range of potential tasks envisioned under this contract, this section of the SOW discusses general contract requirements that are to be applied during performance of the technical requirements outlined in Section 5.0

4.1 COLLABORATIVE DEVELOPMENT ENVIRONMENT

To ensure continued success of the program, the contractor shall be required to work in a collaborative environment with a consortium of partners including the U.S. Navy, Navy Laboratories, Academia, and industry partners to ensure continued success of the program.

4.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 segments of the data environment that are Government provided, contractors shall abide by all access control regulations and policies. For segments that are contractor provided, the contractor shall provide the Government and Government support Contractors and designated program teammates electronic access to that segment of the integrated development environment throughout the term of the contract.

The contractor shall be responsible for the digital generation, receipt, and electronic delivery of data in accordance with the CDRLs. All data shall be developed, managed, used, and delivered/exchanged electronically to the greatest extent practical. Data shall be stored/disseminated in a non-proprietary format, compatible with DoD standard software tools. Data archives may be requested throughout and at the end of the contract term.

Controlled Unclassified Information (CUI) such as FOUO, 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. All emails containing such information or attachments must be digitally signed if being transmitted within Navy networks, and digitally signed and encrypted if being transmitted outside a Navy network to an approved contractor email address. Transmission of CUI to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.) is strictly prohibited.

4.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 Signature Training Systems development community.

4.4 INTEGRATED PRODUCT TEAM PARTICIPATION

The contractor shall participate in joint IPTs as required. 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 its partners. 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.

The contractor shall participate and support the SSG training system IPT process and provide appropriate documentation of process and decisions 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. IPT support shall also include coordination with other on‐site Tactical Signature Guidance (TSG) systems contractor personnel operating in support of Code 73 programs to ensure effective coordination of NSWCCD facilities, hardware and software systems.

As part of the IPTs, the contractor shall have responsibility for the following functions:

a. Monitoring and reporting subsystem status and program;

b. Identification, collection, analysis, and reporting of appropriate metrics for measurement of cost/schedule contract, engineering, and production progress;

c. Joint evaluation and management resolution of major issues (including obsolescence) associated with hardware and software engineering, integration, test, and installation activities;

d. Verification that the contractor’s design disclosure process is providing data that is current, complete, and accurate to third party developers;

e. Joint evaluation and management of the configuration management and maintenance of training systems development networks and Engineering Development Models (EDMs) at NSWCCD; and

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

4.5 PROBLEM REPORTING SYSTEMS

The contractor shall utilize a common commercial off-the-shelf (COTS) software package from Atlassian, Inc.

called Jira. The Jira task tracking system shall be utilized 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 and Government support contractors and designated program teammates electronic access to its problem reporting 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 PTR tracking in Jira for all signature training systems.

4.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 is responsible for supporting and maintaining the signature simulations development networks and EDMs in compliance with cybersecurity accreditation and maintenance procedures. The contractor shall safeguard information and information systems through the use of multi-disciplined defensive layers, as well as sound administrative and operational practices. The contractor shall provide security data management for all classified media supporting signature trainer programs and manage all material utilized for signature trainer programs on-site at NSWCCD via the Code 734 classified Base Inventory Tracking System (BITS) satellite library.

5.0 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, 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 as required.

5.1 SUBMARINE TEAM TRAINER SUPPORT

The contractor shall manage and support SSG systems for Submarine combat system team training, testing, and analysis for shore‐based trainer configurations. Specifics shall be detailed in individual TOs.

5.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.

5.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.

5.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.

5.2 NAVIGATION TRAINER & VISUALIZATION SUPPORT

The contractor shall manage and support SSG systems for Navigation Trainers and Visual Simulation systems required for Navy training, testing, and analysis configurations. Specifics shall be detailed in individual TOs.

5.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.

5.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.

5.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.

5.3 SURFACE TRAINER SUPPORT

The contractor shall manage and support SSG simulation systems ASW and Combat System Surface Ship Trainers required for Navy training, testing, and analysis configurations. Specifics shall be detailed in individual TOs.

5.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.

5.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.

5.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.

5.4 INTEGRATED UNDERSEA SURVEILLANCE SYSTEM (IUSS) TRAINER SUPPORT

The contractor shall manage and support SSG simulation systems for IUSS Trainers required for Navy training, testing, and analysis configurations. Specifics shall be detailed in individual TOs.

5.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.

5.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.

5.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.

5.5 ON-BOARD TRAINER SUPPORT

The contractor shall manage and support SSG simulation systems for on-board trainers embedded within fleet tactical systems required for Navy training, testing, and analysis configurations. Specifics shall be detailed in individual TOs.

5.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.

5.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.

5.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.

5.6 COORDINATED SIMULATION SYSTEMS SUPPORT

The contractor shall manage and support SSG simulation systems, trainers, testing, and analysis configurations leveraged from submarine, surface, and surveillance training system configurations. This includes support for training of Office of Naval Intelligence (ONI) Acoustic Intelligence (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. Specifics shall be detailed in individual TOs.

5.6.1 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.

5.6.2 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.

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

5.6.4 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)/Sensitive Compartmented Information (SCI) clearance to be utilized when attending meetings at ONI in Suitland, MD.

5.7 SUPPORT TECHNOLOGIES

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

5.7.1 GRAPHICAL USER INTERFACE (GUI)

The contractor shall investigate, recommend, design, and implement GUI in support of SSG training systems.

5.7.2 SOFTWARE ENGINEERING MANAGEMENT

The contractor shall provide software engineering management in support of trainer products. This shall include the planning of the development and of the releases of trainer systems; documentation of trainer systems; the design and implementation of automated requirements tracking and trouble tracking capabilities; and the planning of 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.

5.7.3 SOFTWARE MAINTENANCE

The contractor shall conduct software maintenance in support of 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.

5.7.4 HARDWARE MAINTENANCE

The contractor shall conduct hardware preventive maintenance, hardware repair, installation, parts sparing, parts inventorying, and shipping to support delivered SSG Training systems and EDMs at NSWCCD. 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.

5.7.5 SYSTEM 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 at site.

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 DoD and 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.

5.7.6 SOFTWARE ENGINEERING

The contractor shall provide general software engineering support as required 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.

5.7.7 SOFTWARE INTEGRATION AND TESTING

The contractor shall provide both onsite and offsite software integration and testing support as required 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 (CDRL A012).

5.7.8 INTELLIGENCE INFORMATION SUPPORT

The contractor shall access threat acoustic intelligence information from the Office of Naval Intelligence to generate and maintain threat databases for use in signature simulation systems. Contractor personnel are required to ensure data used in surface, submarine, surveillance, and similar signature simulation systems can include real world data and reference to events while maintaining control of sensitive information. The majority of acoustic intelligence information will be at the non-SCI level. A single TS/SCI billet will be required to support a limited number of hours with knowledge of threat signatures, capabilities, and characteristics at the TS/SCI Security Clearance level in support of simulated threat development for combat systems trainers.

5.7.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 as required for turn-over and acceptance of new or updated training systems capabilities.

5.7.10 TRAINING CONTENT

The contractor shall develop content as appropriate for training systems. This shall consist of basic, intermediate, and advanced training for both officer and enlisted training. 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.

5.7.11 PROGRAM SUPPORT

The contractor shall provide administrative, budgetary, and presentation support as required 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.

5.8 FLEET TRAINING SYSTEM DOCUMENTATION REQUIREMENTS

5.8.1 SYSTEM SPECIFIC DOCUMENTS

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

5.8.2 SYSTEM DELIVERABLE DOCUMENTS

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

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 (CDRL A002)

5.8.3 TECHNICAL REPORTS

Technical reports 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

(CDRL A002)

5.8.4 SYSTEM AND SOFTWARE TECHNICAL DOCUMENTATION

Existing Technical Data Package (TDP) documentation shall be updated and maintained under this contract (CDRL A015). The technical documentation shall 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 in order 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.

6.0 PROGRAM MANAGEMENT

6.1 PROGRAM MANAGEMENT STRUCTURE

The contractor shall appoint a Senior Program Manager III (PM3) to act as the focal point for communications between the contractor and Government. The PM3 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 Program Manager II (PM2) assigned to each of these submarine and surface/surveillance domains. Based on the scope of the tasking the PM3 shall assign designated Technical Project Managers (PM1) to support project and technical management support for each major project area (Submarine Team, Navigation, Surface, IUSS, and On-board Trainers). The PM1s shall be responsible for coordination of tasking from the development teams and tracking of all external dependencies required to meet program deliverables and schedules. Engineering development team leads 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.

6.2 INTEGRATED PROGRAM MANAGEMENT

The contractor shall perform business management functions to ensure production orders meet established need dates of the Government.

Required functions include 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.

6.3 PROGRESS, STATUS AND MANAGEMENT REPORT

The contractor shall maintain technical and financial status and generate Progress, Status, and Management Reports (CDRL A001). 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, as necessary, 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, 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.

6.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.

6.5 PROGRAM PLANNING

The contractor shall develop, maintain, and deliver original and revisions of the Task Management Plan (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.

6.6 PHASE-IN AND PHASE-OUT

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. In order 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, and subsequent meetings will be held as determined by the PCO but not less than weekly thereafter.

6.6.1 PHASE-IN

During the phase in period, incoming contractor personnel will be permitted to observe current operations of the outgoing contractor. The incoming contractor shall ensure that its phase-in operations do not hinder or interfere with normal operations of the phase-out contractor, and that maximum effort is made to avoid loss of productivity. By the end of the phase-in period, the incoming contractor shall have assumed full responsibility for all work requirements under the contract. The incoming contractor shall be 100 percent staffed by no later than 60 days after contract award.

6.6.2 PHASE-OUT

During the 30 day period immediately prior to the end of this contract, if the contractor is not awarded the subsequent contract for these services, the contractor shall permit his successor to observe and become familiar with any and all operations under this contract. The contractor shall remain responsible and liable for the completion of all requirements of this contract and TOs through the final day of this contract. The contractor shall not defer any requirements for the purpose of avoiding responsibility and transferring such responsibility to the successor contractor or the Government. The contractor shall fully cooperate with the successor contractor and the Government, and shall not interfere with their work or duties.

6.6.3 PHASE-OUT PLAN

The contractor shall provide the PCO with a phase-out plan no later than 60 days prior to the contract end date (CDRL A018). This plan shall detail disposition action for all equipment, and documentation with moderate Government input, outlining the contractor's approach to fulfill the requirements of this contract and applying all relevant factors and information gathered throughout the performance of the contract.

6.7 REVIEWS

The contractor shall coordinate, schedule, make preparations for, conduct, facilitate, participate, and host reviews, meetings, and conferences as required.