SOFAST-E_DO0001_SOW.doc

PEO-STRI-12-W083

W900KK-13-R-0002

Attachment 2 30 October 2012

STATEMENT OF WORK

FOR THE

160th Special Operations Aviation Regiment (Airborne) (SOAR(A)) Special Operations Forces Aviation Systems Trainers – Enhancements (SOFAST-E)

Delivery Order 0001

Prepared by

U.S. Army PEO Simulation, Training and Instrumentation (PEO STRI)

12350 Research Parkway

Orlando, FL 32826-3276

Revision History

Table of Contents

Section Title Page

11.

SCOPE

11.1 Background

12.

Applicable Documents

12.1 Government Documents

23.

REQUIREMENTS

23.1 General

23.1.1 Program Management

23.1.2 Delivery Order Work Scheduling

23.1.3 Certification Test and Evaluation (CT&E)

23.1.3.1 CT&E Readiness Review and IA Scan Reports

23.1.4 Hardware and Software Purchase

23.2 Delivery Order Tasks

23.2.1 Trainer Modification Tasks

33.2.1.1 Instructor Operator Station (IOS) Graphical User Interface (GUI) for the MH-47-2 Combat Mission Simulator (CMS)

33.2.1.2 IOS GUI for the MH-60-2 CMS

33.2.1.3 ASTi Telestra 4 Installation

43.2.1.4 MH-47-2 Combat Mission Simulator (CMS) Block 2.3 Update [OPTION]

53.2.1.5 MH-47-2 Stimulated CAAS environment conversion [OPTION]

53.2.1.6 SOA Common Avionics Architecture System (CAAS) Upgrade/ Concurrency [OPTION]

83.2.1.7 Miscellaneous Updates

93.2.1.8 MH-47-2 CMS Visual Systems Upgrade [OPTION]

93.2.1.9 MH-47-2 CMS Special Operations Forces Tactical Environment (SOFTAC) [OPTION]

93.2.1.10 Simulation Interoperability

103.2.2 Systems Engineering Processes

103.2.2.1 System Requirements Definition

103.2.2.2 System Requirements Analysis and Traceability

103.2.2.3 System Architectural Design

103.2.2.4 Software Development

123.2.2.5 Reliability and Maintainability (R&M) Engineering

123.2.3 Conferences and Reviews

123.2.4 Commercial and Non-Developmental Items (CaNDI)

123.2.5 Parts Standardization

123.2.5.1 Parts Management

123.2.6 System Safety Tasks

133.2.6.1 Safety Assessment (SA)

133.2.7 Electrostatic Discharge control

133.2.8 Quality Management System Requirements

133.2.9 Product Assurance Audits and Inspections

133.2.10 System Test and Evaluation (T&E)

133.2.10.1 Test Methods

133.2.10.2 Test Criteria

133.2.10.3 In-process Inspections

143.2.10.4 Test Readiness Review (TRR)

153.2.10.5 Government Acceptance Testing (GAT)

173.2.10.6 Physical Configuration Audit (PCA)

173.2.10.7 Logistics Support Analysis

183.2.10.8 Training

193.2.11 Software Configuration Management (SCM) Program

193.2.11.1 Configuration Control

193.2.12 Associate Contractor Agreements (ACA)

193.2.13 Software Licensing and Distribution Agreements

193.2.14 Facility Requirements

193.2.14.1 Facility Engineering Analysis

193.2.14.2 Equipment Installation and Removal

193.2.15 Item Unique Identification (IUID) Assignment

Statement of Work

For the 160th Special Operations Aviation Regiment (Airborne) [SOAR(A)]

Special Operations Forces Aviation Systems Trainers – Enhancements (SOFAST-E) Delivery Order 0001

1. SCOPE

This Statement of Work (SOW) establishes the Delivery Order (DO) 0001contractor tasks for the modifications to be made to the Special Operations Aviation MH-47-2 CMS, the MH-60-2 CMS and the Exercise Management Control (EMC) located at the 160th Special Operations Aviation Regiment [SOAR(A)] Ft. Campbell, KY. This effort will update the Instructor Operation Station (IOS) Graphical User Interface (GUI) on both devices mentioned above, and will upgrade the currently installed Telestra system with the ASTi Telestra 4. The contractor shall not assume that any of the OPTIONs listed below will be exercised at the time of DO 0001 contract award.

Unless otherwise noted in this DO SOW, requirements for DO 0001 are defined in the Basic SOFAST-E SOW, PEO-STRI-12-W030. In case of a conflict between the requirements and documents cited herein and the Basic SOFAST-E SOW, this DO SOW will take precedence.

1.1 Background

The 160th SOAR (A) flight simulation and mission rehearsal facilities presently use a mix of simulators, simulation applications, and mission rehearsal systems that exist at various stages of concurrency and compatibility with Regimental operational capabilities and configurations. The Army Special Operations Aviation (ARSOA) flight training systems, flight simulation, and mission rehearsal master plan requires that these simulators, simulations, and mission rehearsal systems be as common as possible and capable of supporting current mission profiles, including but not limited to interoperability between devices while staying current with operational systems enhancements and upgrades.

2. Applicable Documents The document(s) referenced below are in addition to those referenced in the Basic SOW.

2.1 Government Documents

PRF-PT-00577

Performance Specification for the 160th SOAR(A) Special Operations Forces Aviations Systems Trainers – Enhancements, Delivery Order 0001

3. REQUIREMENTS

3.1 General

All General requirements identified in the Basic SOW, as well as the following general requirements specific to this DO shall apply.

3.1.1 Program Management

See Basic SOW paragraph 3.1.1 for reference. The contractor shall prepare the Contractor’s Progress, Status, and Management Report (CPSMR) in accordance with (IAW) the Contract Data Requirements List (CDRL). (DI-MGMT-80227)

3.1.2 Delivery Order Work Scheduling

The contractor shall develop, implement, control, and maintain an Integrated Master Schedule (IMS) that presents the plans and schedules to meet the requirements of this contract. The contractor shall document the planning and scheduling effort, related Government responsibilities, and any interaction required for the development and delivery efforts associated with the training products. The contractor shall develop and document a tiered scheduling system based on the CWBS elements showing all program milestones and prerequisite events, conferences, reviews, data submittals, and deliveries. Contract deliverables and subcontractor schedules shall be integrated into the IMS. The contractor shall construct the IMS to assure that these milestones are met and to assure deliveries as required by the contract. The contractor shall prepare the IMS in accordance with (IAW) the CDRL. (DI-MGMT-81650)

3.1.3 Certification Test and Evaluation (CT&E)

3.1.3.1 CT&E Readiness Review and IA Scan Reports

See Basic SOW paragraph 3.1.4.5.1 for reference. The contractor shall prepare the IA Scan Reports IAW the CDRL (DI-MISC-80711A)

3.1.4 Hardware and Software Purchase

See Basic SOW paragraph 3.1.8 for reference. All software (developed, Government Off-The-Shelf (GOTS) or Commercial-Off-The-Shelf (COTS)) shall be delivered IAW the CDRL. (DI-MCCR-80700)

3.2 Delivery Order Tasks

The following comprise a list of identified tasks for this Delivery Order.

3.2.1 Trainer Modification Tasks

The contractor shall design, develop, fabricate, integrate, deliver, install, and test the trainer modifications specified in this DO SOW and its associated Specification (PRF-PT-00577). The contractor shall ensure that no current capabilities are lost or diminished as a result of any trainer modifications. The tasks outlined below other than those clearly identified as OPTION shall be accomplished in a non-interference basis (work around existing training schedule where training is not impacted).

Once the OPTIONs are exercised, the contractor may assume that the CMS will be available 24/7 for modifications.

3.2.1.1 Instructor Operator Station (IOS) Graphical User Interface (GUI) for the MH-47-2 Combat Mission Simulator (CMS)

The contractor shall integrate and test the IOS GUI common to the LASAR CMS and the Legacy Upgrade Effort (LUE) into the MH-47-2 CMS.

3.2.1.2 IOS GUI for the MH-60-2 CMS

The contractor shall integrate and test the IOS GUI common to the LASAR CMS and the Legacy Upgrade Effort (LUE) into the MH-60-2 CMS.

3.2.1.3 ASTi Telestra 4 Installation

The contractor shall remove the existing ASTi Digital Audio Communication System (DACS) from the MH-47-2 CMS and replace it with an ASTi Telestra 4 system. The contractor shall also remove the existing ASTi DACS from the Exercise Management Control (EMC) and replace it with the ASTi Telestra 4. The new ASTi Telestra 4 system will interface with and allow communication between the MH-47-2 CMS, the MH-60-2 CMS (which already has a Telestra 4), the EMC and the BSTS (which already has a Telestra 4), in both standalone and interoperability modes. The contractor shall make sure that no current capability is lost or diminished.

3.2.1.3.1 MH-47-2 Code Generation, Modeling, and Tuning

The contractor shall update, integrate, and test the Code Generation, Modeling, and Tuning for the Telestra on the MH-47-2 CMS with the T4 Target platform IAW this SOW and Specification PRF-PT-00577.

3.2.1.3.2 MH-47-2 Wiring

The contractor shall replace, integrate, and test the MH-47-2 Wiring for the Telestra on the MH-47-2 CMS with the T4 Target platform in IAW this SOW and Specification PRF-PT-00577.

3.2.1.3.3 MH-47-2 Integration

The contractor shall calibrate and test the Digital Voice Response System (DVRS) audio, Voice Operated (VOX) and aural cues/warnings for the Telestra on the MH-47-2 CMS with the T4 Target platform IAW this SOW and Specification PRF-PT-00577. The contractor shall run the appropriate Acceptance Test Procedures for standalone and networked capabilities.

3.2.1.3.4 EMC, Host Code, Radio Modeling

The contractor shall convert the DACS model to a T4 model IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.3.4.1 EMC re-wire

The contractor shall add a new Audio Communications Environment (ACE) Net Switch to the EMC and perform the same wiring modifications as in paragraph 3.2.1.3.2 and in accordance with this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.3.4.2 EMC integration

The contractor shall test the communications to/from the EMC IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.3.4.3 CMS and EMC Communication

After completion of the ASTi T4 upgrade to the MH-47-2 CMS and EMC, the contractor shall test communication between the EMC, MH-47-2 CMS, and MH-60-2 CMS in both standalone and networked mode IAW this DO SOW and associated Specification (PRF-PT-00577).

3.2.1.4 MH-47-2 Combat Mission Simulator (CMS) Block 2.3 Update [OPTION] The contractor shall update the MH-47-2 CMS to the MH-47-2 aircraft Block 2.3 configuration including any applicable Modification Work Orders (MWOs) implementing the functionality listed below.

3.2.1.4.1 Miscellaneous Panel

The contractor shall remove the existing Miscellaneous Panel located on the canted console and replace it with a Miscellaneous Panel updated to the Block 2.3 configuration and functionality IAW PRF-PT-00577.

3.2.1.4.2 AN/ARC-231 Multiband Radio

The contractor shall update the existing version of the AN/ARC-231 Multiband Radio simulation to the latest version. The contractor shall remove the AN/ARC-164 and AN/ARC-186 radio functionality and replace it with two instances of the latest version of the AN/ARC-231 Multiband Radio simulation which are fully integrated with the SOA CAAS IAW PRF-PT-00577.

3.2.1.4.2.1 AN/ARC-231 Dual Fill Panel

The contractor shall procure, install, integrate and test a second AN/ARC-231 Dual Fill Panel located in the center console as per the design basis aircraft and IAW PRF-PT-00577.

3.2.1.4.3 Low Profile Control Audio Panel (LPCAP)

The contractor shall procure, install, integrate and test the LPCAPs IAW PRF-PT-00577. The contractor shall install five (5) LPCAP guards as per the design basis aircraft.

3.2.1.4.4 Digital Intercom Communication System (DICS) and Flight Director (FD) Lighting Control Panel

The contractor shall remove the existing AUX ICS Lighting Panel located in the overhead switch panel and replace it with the DICS Lighting Control Panel IAW PRF-PT-00577.

3.2.1.4.5 Interior Lighting Control Panel

The contractor shall remove the existing Interior Lighting Control Panel located in the overhead console and replace it with the Interior Lighting Control Panel updated to the Block 2.2 configuration and functionality IAW PRF-PT-00577. The contractor shall remove the overhead console floodlights (2 each). The contractor shall ensure the wiring is removed if practical. If it is not practical to remove the wiring, the contractor shall ensure the wiring is safely terminated.

3.2.1.4.6 Anti-Ice Control Panel with Manual Continuous Ignition System (MCIS) The contractor shall remove the existing Anti-Ice Control Panel located in the overhead switch panel and replace it with the Anti-Ice Control Panel with MCIS updated to the Block 2.2 configuration and functionality IAW PRF-PT-00577

3.2.1.4.7 Battery Condition Warning Status Panel

The contractor shall integrate and test the Battery Condition Warning Status Panel located in the center console IAW PRF-PR-00577.

3.2.1.4.8 Pilot & Copilot Cockpit Stalk Lights

The contractor shall integrate and test the Pilot & Copilot stalk lights located under the glareshield IAW PRF-PF-00577.

3.2.1.5 MH-47-2 Stimulated CAAS environment conversion [OPTION] The contractor shall convert the current simulated Special Operation Aviation (SOA) CAAS environment in the MH-47-2 CMS to a stimulated SOA CAAS environment.

3.2.1.6 SOA Common Avionics Architecture System (CAAS) Upgrade/ Concurrency [OPTION]

The contractor shall integrate the latest SOA CAAS update available at the Delivery Order Option award, into the MH-47-2 CMS as required to maintain airframe concurrency. The primary integration strategy will be a “stimulated” approach, although a “simulated” strategy may be applicable and may include but not be limited to the following;

3.2.1.6.1 MH-47 CMS CAAS Re-host Architecture Upgrade

The contractor shall recapitalize all of the computers which drive and are associated with the CMS CAAS functionality including but not limited to Multi-Function Displays (MFDs) and Control Display Units (CDUs) on the MH-47 CMS in order to support the integration of the latest version of SOA CAAS on a stimulated architecture. The contractor shall conduct the design, procurement, integration, and test of new state of the art CAAS Re-host Architecture computational systems to replace the current systems on the MH-47 CMS. All host computer interfaces for download, configuration, Built-in-Test (BIT), and Daily Operational Readiness Test (DORT) shall be updated.

3.2.1.6.2 MH-47-2 CMS Circuit Breaker Update

The contractor shall update, integrate, and test any and all circuit breaker panels that may need to be modified as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577. The contractor shall ensure that no current capabilities are lost or diminished and that any potential and adverse effects to ongoing training evolutions are mitigated during the circuit breaker update effort.

3.2.1.6.3 MH-47-2 CMS Integrated Warning, Caution, Advisory (Voice) [IWCA(V)] Update The contractor shall update, integrate, and test any and all IWCA(V) systems that may need to be modified as a result of the SOA CAAS upgrade to the MH-47-2 CMS , IAW this SOW and PEOSTRI Specification PRF-PT-00577. The contractor shall ensure that no current capabilities are lost or diminished and that any potential and adverse effects to ongoing training evolutions are mitigated during the IWCA(V) update effort.

3.2.1.6.4 MH-47-2 CMS P3I Embedded GPS & INS (EGI) Update

The contractor shall update, integrate, and test any and all EGI systems that may need to be modified as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577. The contractor shall ensure that no current capabilities are lost or diminished and that any potential and adverse effects to ongoing training evolutions are mitigated during the EGI update effort.

3.2.1.6.5 MH-47-2 CMS Radar Systems

3.2.1.6.5.1 MH-47-2 CMS Multi-mode RADAR (MMR) Update

The contractor shall update, integrate, and test any and all MMR systems that may need to be modified as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577. The contractor shall ensure that no current capabilities are lost or diminished and that any potential and adverse effects to ongoing training evolutions are mitigated during the MMR update effort.

3.2.1.6.6 MH-47-2 CMS Aircraft Survivability Equipment (ASE)

3.2.1.6.6.1 MH-47-2 CMS Aircraft Survivability Equipment (ASE) Update

The contractor shall update, integrate, and test any and all ASE suite systems that may need to be modified as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577. The contractor shall ensure that no current capabilities are lost or diminished and that any potential and adverse effects to ongoing training evolutions are mitigated during the ASE update effort.

3.2.1.6.6.2 MH-47-2 CMS Aircraft Survivability Equipment (ASE) Correction The contractor shall correct, integrate, and test Threat Intervisibility indications that need to be modified as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.6.6.3 Hostile Fire Indicator (HFI)

The contractor shall ensure the HFI is incorporated and that it reacts with the computer generated forces simulated ballistic models with the same functional indications as seen in the cockpit instrumentation as per the design basis aircraft.

3.2.1.6.6.3.1 Hostile Fire Indicator (HFI): LWS HFI Selection

The contractor shall integrate and test the creation of an “off/on” selection on the ASE Control Page for the LWS HFI functionality only as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.6.6.3.2 HFI: CWMS HFI Power Selection

The contractor shall integrate and test the creation of an “off/on” selection on the ASE Control Page for the CMWS HFI functionality only as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.6.6.4 Common Missile Warning System (CMWS) INS DATA status change The contractor shall integrate and test the change of the "FULL" status of CMWS INS DATA to "EGI 1" when MSM is sending EGI 1 data and "EGI 2" when EGI 2 data is being sent as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.6.6.5 Helicopter Alert and Threat Termination – Acoustic (HALTT-A)

The contractor will ensure that the latest SIRFC update will be installed with the additional Hostile Fire Indicator system incorporated to react with the Computer Generated Forces simulated ballistics models with the same functional indications as is seen in the cockpit instrumentation as the design basis aircraft.

3.2.1.6.6.6 Complete status/software reporting of LWR and ASC HFI

The contractor shall integrate and test the implementation of status and software version reporting for the Ethernet LWR (AVR-2B) and ASC HFI (HALTT-A – page flow only) as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.6.6.7 Incorporate EGI Autoreversion logic for SIRFC and HALTT-A The contractor shall integrate and test the modification of the EGI Autoreversion logic for SIRFC and HALTT-A (page flow only with respect to HALTT-A) as a result of the SOA CAAS upgrade to the MH-47-2 CMS and MH-60M CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.6.6.8 Advanced Survivability Equipment (ASE): Change source/status of HFI DETECT bit for the CMWS The contractor shall integrate and test the change of the source/status of the HFI DETECT bit for the CMWS as a result of the SOA CAAS 6.5 upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.6.6.9 Remove CMWS HFI control/status when SA 23 is not present The contractor shall integrate and test the change of Remove CMWS HFI control/status when SA 23 is not present and the capability to set the SA23 bit ON or OFF as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.6.6.10 Change timing on the High Speed Data Missile Warning Symbol

The contractor shall integrate and test the change to the timing on the HSD Missile Warning Symbol as a result of the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.6.7 MH-47-2 CMS Digital Automatic Flight Control System (DAFCS) Upgrade The contractor shall simulate, integrate and test the DAFCS into the MH-47-2 CMS in conjunction with the SOA CAAS update, IAW with this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.1.6.8 MH-47-2 CMS AN/ARS-6(V)12 Personnel Locator System (PLS) Radio Model

The contractor shall update, integrate, and test the current AN/ARS-6(V)12 PLS radio model to provide full SOA CAAS interface and stand-alone aircraft radio functionality into the MH-47-2 CMS IAW this SOW and PEOSTRI Specification PRF-PT-00577. The contractor shall upgrade the threat environment models in support of the radio upgrade, to include any necessary changes to the Computer Generated Forces threat models behaviors or attached equipment that is necessary to support the use and functionality of the radio upgrades. The contractor shall ensure that no current capabilities are lost or diminished and that any potential and adverse effects to ongoing training evolutions are mitigated during the AN/ARS-6(V)12 PLS radio model integration effort.

3.2.1.6.9 MH-47-2 CMS Instructor/Operator Station (IOS) Malfunctions

The contractor shall integrate and test any and all necessary changes to the current IOS malfunctions, and add the functionality of any new malfunctions resulting from the integration of SOA CAAS into the CMS.

3.2.1.6.10 MH-47-2 CMS Health and Usage Monitoring System (HUMS)

The contractor shall integrate and test any and all necessary changes to each HUMS resulting from the SOA CAAS upgrade to the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577. The contractor shall ensure that no current capabilities are lost or diminished and that any potential and adverse effects to ongoing training evolutions are mitigated during the HUMS effort.

3.2.1.7 Miscellaneous Updates

3.2.1.7.1 MH-47-2 CMS, Engine Flight Performance Model (EFPM) Update [OPTION] The contractor shall integrate and test the Engine Flight Performance Model (EFPM) updates in the MH-47-2 CMS, IAW this SOW and PEOSTRI Specification PRF-PT-00577. The contractor shall ensure that no current capabilities are lost or diminished and that any potential and adverse effects to ongoing training evolutions are mitigated during the EFPM update effort.

3.2.1.7.2 MH-47-2 Guidance Control Point (GCP) [OPTION]

The contractor shall integrate and test the GCP functionality into the correct lever arm for the location of each EGI in accordance with this SOW and specification PRF-PT-00577.

3.2.1.7.3 Thrust Control Lever (TCL) [OPTION]

The contractor shall integrate and test the “MARK” button functionality into both the MH-47G pilot’s and copilot’s TCL in accordance with this SOW and specification PRF-PT-00577.

3.2.1.7.4 AN/ZSQ-2 Electro Optical Sensor (EOS) [OPTION]

The contractor shall update the EOS model. This updating may include, but not be limited to, the following attributes for the MH-47-2 CMS, the EOS shall function as the design basis aircraft:

a. The EOS shall display the current modeled software load.

b. The EOS shall default to Infra Red-Image Intensifier (IRI2) for the MH-47G/ Assault version.

c. The EOS shall have the capability to capture and record video to the DTU-7100. The recorded video shall be displayed on any selected multi-function display (MFD).

3.2.1.8 MH-47-2 CMS Visual Systems Upgrade [OPTION]

The contractor shall upgrade all MH-47-2 CMS visual systems/subsystems, to include the removal and replacement of the currently installed Image Generators (IGs) and projectors in the MH-47-2 CMS with the 160th common visual solution IGs and projectors IAW PRF-PT-00577. The contractor shall determine whether the existing Mylar system needs to be replaced or refurbished in order to extend the life cycle of the current Mylar system and reduce the time it takes to draw the Mylar system into its operational shape after a power event.

3.2.1.9 MH-47-2 CMS Special Operations Forces Tactical Environment (SOFTAC) [OPTION] The contractor shall replace the existing MH-47-2 CMS Synthetic Tactical Real-time Interactive Virtual Environment (STRIVE) framework with the 160th SOAR common solution for the tactical environment SOFTAC. SOFTAC shall provide a high fidelity physics‐based real time simulation model for a variety of threat systems, sensors, and weapons. SOFTAC shall provide a Distributed Interactive Simulation (DIS) gateway to enable virtual and constructive networked training. SOFTAC shall provide the capability of running on a secure classified environment.

3.2.1.9.1 Suite of Integrated Radio Frequency Countermeasures (SIRFC) The contractor shall maintain concurrency of the SIRFC, to include but not limited to, updating the SIRFC to the latest configuration and software load as per the design basis aircraft for the MH-47-2 CMS. If the SOFTAC option is exercised, the contractor shall integrate the list of computer generated forces (CGF) from SOFTAC to include any new entities required to test the full spectrum of SIRFC. These additional entities shall have the correct electronic signatures modeled and shall interact appropriately with all facets of the SIRFC.

3.2.1.10 Simulation Interoperability

The contractor shall ensure the baseline internal and external simulation interoperability shall not be degraded by the incorporation of the respective enhancements made to the applicable CMS.

The contractor shall test the applicable interoperability requirements with the other systems to which the affected CMS can connect.

3.2.2 Systems Engineering Processes

All of the Basic SOW paragraph 3.2.2 and subparagraphs apply unless otherwise noted.

3.2.2.1 System Requirements Definition

The purpose of the system requirements definition process is to define the requirements for a system that can provide the performance defined in this SOW and PEOSTRI Specification PRF-PT-00577.

3.2.2.2 System Requirements Analysis and Traceability

The contractor shall perform and document an analysis to verify that all requirements from the DO 0001 PEO STRI Specification PRF-PT-00577 and this SOW are met and are traceable to each configuration item and subsequent lower level units of decomposition. The contractor shall develop a Requirements Traceability/Verification Matrix (RTVM) to document the results of this task. The contractor shall present an updated RTVM at the Systems Requirement Review (SRR) and any subsequent design review event. The contractor shall prepare the RTVM IAW the CDRL. (DI-MISC-80711A)

3.2.2.3 System Architectural Design

The purpose of the system architectural design process is to identify which system requirements should be allocated to which segments (subsystems) of the system. The contractor shall define, document, manage, and apply a system architectural design process IAW DO 0001Specification PRF-PT-00577 and this SOW. The contractor shall place links to the system architectural design in the RTVM to accomplish bi-directional traceability. The contractor shall prepare System/Subsystem Design Description (SSDD) and the Interface Control Document (ICD) IAW the CDRLs (DI-IPSC 81432A, and DI-CMAN-81248A respectively). The contractor shall prepare the Product Drawings/Models and Associated Lists IAW the CDRL (DI-SESS-81000D).

3.2.2.4 Software Development

The contractor shall analyze, design, code, integrate, install and test the upgraded software to meet the requirements of the DO 0001 Specification PRF-PT-00577 and this SOW. The computer programs and data shall comprise real-time programs, computation and system support programs. The contractor shall develop the system software and firmware IAW recognized industry standards and an internally documented process. The code shall make extensive use of comments, both inline and at the beginning of significant pieces of logic, so that third-party engineers can understand and maintain the code without additional documentation. In addition, each source code file shall contain a standardized header block that provides at least the following details: module name, module description, and revision history. The design shall incorporate features that promote ease of operation, IA, ease of software maintenance, ease of future updates and modifications and also any smart designs that can justify a reduction in the amount of documentation. All software changes will be managed using agreed upon configuration processes and procedures. Software changes will be submitted to and approved by the Government prior to incorporation into system baselines. The contractor shall ensure that all new, revised or modified software is incorporated in the systems. The contractor shall update existing documentation to reflect the incorporation of the modifications IAW the CDRL (DI‑ADMN‑80925). All new, modified and commercial software shall be delivered IAW the CDRL (DI-MCCR-80700).

3.2.2.4.1 Software Product

The contractor shall define, document, control, maintain, validate, and prepare the trainer software. The contractor shall deliver the software, and databases required to meet the performance defined in this SOW and further refined in this SOW and Specification PRF-PT-00577. The contractor shall deliver the non-Commercial Item software with corresponding source code, build tools, build procedures, executable code, configuration information, and build procedures. The contractor shall deliver the Commercial Item software with the associated vendor manuals, documentation, physical media, warranty information, licenses, and installation procedures. The contractor shall transfer to the Government at device acceptance, the Commercial Item software licenses. The contractor shall prepare the Scientific and Technical Report (Software Product Specification [SPS]) IAW the CDRL (DI-IPSC-81441A).

3.2.2.4.1.1 Installation and Configuration Procedures

The contractor shall develop, document, control, maintain, validate, and prepare the installation and configuration procedures IAW PEO STRI Specification PRF-PT-00577. The contractor shall prepare installation and configuration procedures for each computational subsystem acquired as a tightly integrated, ready to use turnkey system. Turnkey describes a Commercial Item that is pre-built, in which everything needed is put together by a vendor and sold as a bundle. Examples of turnkey subsystems include Commercial Item control loaders, aural cueing, and image generators. The contractor shall develop installation and configuration procedures:

a. For configuring applicable computer hardware settings such as in a BIOS or firmware

b. For restoring the system software, such as the operating system, applications and data, to the original delivered configuration.

c. For configuring the system software for use within the training device, such as user accounts, network connectivity, and information assurance controls

d. That consist of detailed descriptive action to be performed; the expected result following the action; and an area to document abnormalities, discrepancies, errors, and pass/fail status

e. That ensure that complex sequences of installation and configuration actions are broken down into discrete steps

f. That can be accomplished without referring to external documentation

g. That include listing the physical software media required to perform the installation and configuration procedure

h. That include Commercial Item software activation data, such as serial numbers and key codes

i. Provide a government-approved Firmware Support Manual (FSM) IAW the CDRL (DI-IPSC-81448A)

3.2.2.5 Reliability and Maintainability (R&M) Engineering

The contractor shall establish and maintain active and effective R&M programs that meet program objectives. The R&M programs shall ensure that Commercial Items, Non Developmental Items (NDI), and Trainer Peculiar Equipment (TPE) to be delivered to the Government as a result of the required trainer modifications, meet the R&M requirements specified in the individual DO Specification PRF-PT-00577 and this SOW. The contractor shall include the R&M programs as topics of discussion during the scheduled program reviews.

3.2.2.5.1 Reliability and Maintainability (R&M) Predictions

The contractor shall develop R&M predictions for the trainer modification equipment to examine the probability, early in the program, that the R&M requirements of DO 0001Specification PRF-PT-00577 and this SOW will be met with the proposed design. The specification may be used as guidance for reliability prediction methods and MIL HDBK 472 may be used as guidance for the maintainability prediction methods. Manufacturer’s data, documented engineering analysis, and verifiable field data, may be used as sources of failure rate, Mean-Time-Between-Failures (MTBF), and Mean-Time-To-Repair (MTTR) data. The contractor shall update the R&M predictions throughout the duration of the contract and shall present the prediction results at the scheduled program design reviews.

3.2.3 Conferences and Reviews

All of the Basic SOW paragraph 3.2.3 and subparagraphs apply unless otherwise noted.

The contractor shall prepare the Conference Agenda, Conference Minutes, and Presentation Material for the conferences and reviews IAW the CDRL (DI-ADMN-81250A).

3.2.4 Commercial and Non-Developmental Items (CaNDI)

See Basic SOW paragraph 3.2.4

3.2.5 Parts Standardization

See Basic SOW paragraph 3.2.5.

3.2.5.1 Parts Management

The contractor shall establish a parts management program, IAW the contractor’s standard procedure, which ensures that the training system modifications meet the performance requirements specified in DO 0001Specification PRF-PT-00577 and this SOW, with the lowest life cycle cost.

3.2.6 System Safety Tasks

The contractor shall establish and maintain an active and effective System Safety Program (SSP) that meets program objectives and ensures that the modified training system meets the system safety requirements specified in DO 0001Specification PRF-PT-00577 and this SOW. The main objectives of the SSP shall be to identify, document, analyze, and resolve (i.e., eliminate or reduce the associated risk to a level acceptable to the Government) safety hazards to both personnel and equipment. The contractor shall include system safety as a topic of discussion during the scheduled program reviews.

3.2.6.1 Safety Assessment (SA)

See Basic SOW paragraph 3.2.6.1.

The contractor shall prepare a Safety Assessment Report (SAR) IAW the CDRL (DI-SAFT-80102B).

3.2.7 Electrostatic Discharge control

See Basic SOW paragraph 3.2.7.

3.2.8 Quality Management System Requirements

See Basic SOW paragraph 3.2.8 and subparagraphs.

3.2.9 Product Assurance Audits and Inspections

See Basic SOW paragraph 3.2.9.

3.2.10 System Test and Evaluation (T&E)

All of the Basic SOW paragraph 3.2.10, and subparagraphs apply to this SOW unless otherwise noted.

The contractor shall update existing documentation to reflect the incorporation of the modifications IAW the CDRL. (DI-ADMN-80925)

3.2.10.1 Test Methods

See Basic SOW paragraph 3.2.10.4 The contractor shall prepare the Revisions to Existing Government Documents (TP) and the Test/Inspection Report IAW the CDRLs (DI-NDTI-80603A & DI-NDTI-80809B, respectively).

3.2.10.2 Test Criteria

See Basic SOW paragraph 3.2.10.5.

The contractor shall prepare the Revisions to Existing Government Documents (TCR) IAW the CDRL (DI-MISC-81281).

3.2.10.3 In-process Inspections

The contractor shall perform in-process inspections including: visual, electrical, and mechanical examinations and testing of materials, subassemblies, parts, and accessories (including purchased items) that may be required to assure conformance to the requirements of DO 0001Specification PRF-PT-00577 and this SOW.

3.2.10.3.1 Functional Configuration Audit (FCA)

The FCA shall include the tests, assessments, inspections, demonstrations, and verifications specified in the individual DO Specification PRF-PT-00577and this SOW, and shall be performed to demonstrate that training system performance satisfies requirements in DO 0001Specification PRF-PT-00577 and this SOW. The FCA tests shall be performed IAW the Government-accepted Test Plan (TP). The tests shall exercise the modified trainer at the subsystem, system, intersystem, and combined trainer system levels. The tests shall be designed to validate the simulation and stimulation performance throughout the entire performance envelope, in the required configurations and modes of operation. The tests shall exercise the simulation and stimulation in the most complex and demanding computational configurations. Tests shall be conducted without alignment or adjustment of controls, other than the accessible controls employed for normal trainer operation. No repairs or adjustments, other than those authorized by the Government test director, will be permitted during the conduct of tests. If repairs or adjustments are required, the test in question, and other tests whose results may be affected thereby, shall be repeated after repairs or adjustments have been made. The FCA shall include tests developed to evaluate the integration of GFE and their interfaces with other trainer equipment. The FCA shall consist of the following T&E components.

3.2.10.4 Test Readiness Review (TRR)

TRR will be conducted by the Government, following completion of Contractor Verification Testing (CVT) and after the TRR entry criteria specified below in 3.2.10.4.1.1 have been met. The purpose of the TRR is to determine trainer readiness for the GAT. The contractor shall provide the resources, including facilities, equipment, and personnel necessary to support the TRR. The TRR will include a review of the T&E program, including the test results, presentation of contractor certification of test readiness, and open deficiencies remaining from CVT. The contractor shall present a cross-reference matrix, in contractor’s format; to verify that DO 0001Specification PRF-PT-00577 and this SOW requirements have been tested. The TRR shall include a contractor-conducted, Government-witnessed demonstration of trainer stability for testing. The trainer stability demonstration shall consist of the performance of a stress test IAW the verification requirements of DO 0001Specification PRF-PT-00577 and this SOW. The TRR will be repeated until the trainer has been determined by the Government to be acceptable for commencement of the Conformance Inspections. During the TRR, the following shall be reviewed and discussed:

a. Trainer test procedures

b. Updated RTVM to verify specification requirements have been tested

c. Contractor test log

d. CVT test results (including SI test results) and deficiencies

e. Test discrepancy reporting process and applicable test discrepancy report form to be used during GAT

f. Identification of software test tools to be used during GAT

g. Summary of software problems status

h. Status of spare capacities, such as CPU (timing), memory capacity, and disk storage

i. Mission exercises

j. Logistic Support

3.2.10.4.1.1 TRR Entry Criteria

The entry criteria for TRR shall consist of Government concurrence with the following:

a. The CVT tests have been run as evidenced by the existence of contractor test logs, TP execution entries, and related DR records.

b. DRs are fully documented (number, severity, status, system, recommendation, etc.)

c. No Priority “A” or “B” DR’s open unless agreed to by the Government.

d. Only a small percentage of Priority “C” DR’s open unless agreed to by the Government. This small percentage shall be addressed at an IPT meeting or by management prior to conducting TRR

e. There is documented evidence that demonstrates that a complete run of the Government-accepted TP has been accomplished from start to finish during CVT, without segregation of elements of individual tests.

f. The above documents and data are available prior to the start of the TRR.

3.2.10.4.1.2 TRR Exit Criteria

The exit criteria for TRR shall consist of Government concurrence with the following:

a. Contractor test logs and records demonstrate that a complete run of the TP has been executed, as evidenced by the following:

(1) Contractor has provided a copy of the updated tests results, with red-lines (when necessary), as recorded in the contractual test documentation.

(2) Contractor has provided applicable personnel names and functions for team members involved in contractor testing.

(3) Contractual CM processes have been followed, and contractor generated CM logs are available for Government review/inspection. Baseline configuration has been established.

(4) System stability for testing has been demonstrated. System crashes have been recorded denoting cause of each crash and recovery time measured from system crash to resuming testing.

b. Contractor has demonstrated that the test equipment needed to execute the complete TP was used, functions properly, is in calibration, and is currently available and working.

c. Contractor’s Test Director has certified in writing that contractor testing has been completed and that the trainer is ready for Government Final Inspection.

d. Agreed plan for Government testing has been established and TP has been accepted by the Government.

e. TP red-lines have been incorporated and the testing documentation is ready for use and annotation of results.

f. DR database has been setup for tracking deficiencies and control of DRs has been transferred to the Government.

3.2.10.5 Government Acceptance Testing (GAT)

GAT will commence upon notification by the COR that the TRR exit criteria have been met. GAT will be conducted on-site by a joint Contractor/Government test team and will consist of tests conducted to verify compliance with the specified performance requirements. GAT will be conducted IAW the Government-accepted TP (revised to include corrections made during CVT) and other Government-accepted test plans. The contractor shall provide the Government with a copy of this revised TP prior to GAT. Testing will commence with the establishment of a software baseline resulting from a software cold-start performed IAW the cold start requirements specified in this SOW, the verification requirements of the individual DO Specification PRF-PT-00577, and the Government-accepted TP. Following the cold-start, the Government will perform the IA verifications IAW the verification requirements of DO 0001 Specification PRF-PT-00577 and this SOW, and the Government-accepted TP. Deficiency correction verification and validation, including additional cold-starts, will be at the discretion of the Government. The typical test schedule may consist of a 10-hour test day followed by the contractor’s deficiency clean-up and trainer maintenance periods. The contractor shall provide the resources, personnel, and equipment necessary to support the tests. Hardware and software configuration item testing and design documentation verification and validation will be conducted as an integral part of Government Final Inspection. The Government reserves the right to perform such additional tests as deemed necessary to ensure compliance with the specified requirements. Deficiencies found during Government Final Inspection shall be corrected by the contractor and verified by the Government test team prior to Government acceptance of the modified trainer.

3.2.10.5.1 GAT Entry Criteria

The entry criteria for GAT shall include the following:

a. Agreed plan for GAT has been established and Acceptance Test Procedure (ATP) has been accepted by the Government.

b. Post-ship and installation have been accomplished successfully, and all systems are integrated, operational, and ready for testing.

c. Post-ship baseline configuration has been recorded and re-established. Contractual and industry standard CM processes have been followed, and contractor generated CM logs are available for Government review/inspection.

d. On-site CVT was completed successfully. All DR’s have been corrected and closed unless agreed to by the Government.

e. TRR exit criteria have been met.

f. Contractor test personnel are available to work with the Government, when required, in the execution of testing during GAT

g. System stability has been demonstrated as acceptable by the Government.

h. Contractor’s QA representative has certified in writing that the training system is ready for GAT.

3.2.10.5.2 GAT Exit Criteria

The exit criteria for Government Final Inspection shall consist of Government concurrence with the following:

a. A cold-start has been successfully performed to establish final software baseline.

b. Deficiencies identified have been documented, categorized for severity, and tracked to final resolution (DR sign-off and dismissal).

c. Priority A, B and C deficiencies have been corrected.

d. A complete TP test has been run after the final DR ready for re-test, within acceptable regression testing guidelines as determined by the Government.

e. Government mission testing has been performed successfully.

f. A copy of the final TP test results has been provided with the results recorded in the contractual testing documentation, including date/time of final results, and red-lines (when necessary).

g. CM baseline (software and hardware) has been maintained throughout DR correction. CM deficiencies identified during Government Final Inspection have been corrected.

h. GAT has demonstrated that the test and support equipment necessary to execute the complete TP testing were used, documented, in calibration, and functioned properly.

i. Required QA standards have been satisfied and achieved.

j. Contractor’s QA representative, Contractor’s test manager, and Government’s test director have signed off testing as complete.

3.2.10.6 Physical Configuration Audit (PCA)

Physical Configuration Audit (PCA) will consist of non-functional examinations performed IAW the Government-accepted TP to demonstrate that the modified trainer as-built design satisfies 0001 Specification PRF-PT-00577 and this SOW requirements, and that the deliverable hardware and software documentation accurately reflect the configuration items. The contractor shall perform a planning effort for the PCA. The contractor shall develop and document in the TP, the test procedures to perform the PCA examinations. The contractor shall record the results of the PCA examinations in the Test/Inspection Report. Non-deliverable documents may be in contractor format and will be examined only to determine contractor compliance with CM requirements. The PCA will be conducted by a Government team on the as-built trainer with power off. The contractor shall certify, prior to the start of PCA examinations, that the electrical power, including Uninterruptible Power Systems (UPS), have been disconnected, that the training system has been de-energized, and that the pneumatic and hydraulic system pressures have been released. The contractor shall comply with the OSHA lockout-tagout requirements specified in 0001 Specification PRF-PT-00577 and this SOW. The contractor shall provide the personnel and equipment necessary to support the Government-conducted examinations. The contractor shall be responsible for the disassembly of trainer equipment and for providing access to areas of the trainer not normally accessible. The Government reserves the right to perform other examinations deemed necessary to determine compliance with the individual DO Specification and the corresponding SOW and design documentation requirements.

3.2.10.7 Logistics Support Analysis

All of the Basic SOW paragraph 3.2.10.16 and subparagraphs apply to this SOW unless otherwise noted.

3.2.10.7.1 Supportability Analysis and Logistics Management Product Data See Basic SOW paragraph 3.2.10.16.1.

The contractor shall prepare the Logistics Product Data, proposed spare parts lists and Logistics Product Data Summaries IAW DIDs (DI-SESS-81758, DI-SESS-81759). The contractor shall document the following in a database:

a. All input data and their corresponding value and source of the data.

b. Operational scenario modeled, assumptions made, constraints assumed, and non-economic factors imposed.

c. Maintenance alternatives considered.

d. Analytical method and models used to perform the economic evaluations.

e. Discussion of the sensitivity evaluation performed and results obtained

3.2.10.7.2 Operator’s Manual

An operator's manual shall be prepared detailing installation, preventive maintenance and use of the CMS. This manual shall be submitted IAW the CDRL. (DI-SESS-81527B)

3.2.10.7.3 Maintenance Manual

A maintenance manual shall be prepared detailing installation, fault isolation and maintenance procedures for the CMS training system. This manual shall be submitted IAW the CDRL. (DI-ILSS-80872)

3.2.10.7.4 Commercial Manuals

The contractor shall provide documentation (i.e., manual(s)) for all Commercial Off-The-Shelf (COTS) equipment used in the system. The documentation shall include supplemental data as applicable. The documentation, at a minimum, shall contain operating instructions and maintenance data to support the planned level of maintenance. The documentation shall be submitted IAW the CDRL. (DI-TMSS-80527B)

3.2.10.7.5 Publications in Process Reviews (IPRs)

See Basic SOW paragraph 3.2.10.17.4

3.2.10.7.6 Publications Validation

See Basic SOW paragraph 3.2.10.17.5 for reference.

The contractor shall prepare the Validation Report IAW the CDRL (DI-CMAN-80792A)

3.2.10.8 Training

See Basic SOW paragraph 3.2.10.18

3.2.10.8.1 Instructor and Operator Training

See Basic SOW paragraph 3.2.10.18.1 for reference.

An Instructor Utilization Handbook (IUH) shall be delivered IAW the CDRL. (DI-SESS-81527B)

3.2.10.8.2 Maintenance Training

See Basic SOW paragraph 3.2.10.18.2 for reference.

The contractor shall prepare the Training Materials and the Training Conduct Support Document IAW the CDRLs (DI-ILSS-80872) Training Materials, (DI-SESS-81523B) Training Conduct Support Document

3.2.11 Software Configuration Management (SCM) Program

All of the Basic…