SOFAST-E_Basic_SOW.doc

PEO-STRI-12-W030

W900KK-13-R-0003

Attachment 1

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)

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

11.2 Objectives

12.

Applicable Documents

12.1 Government Documents

22.2 Non-Government Documents

22.3 Department of Defense Directives

22.4 Department of Defense Instructions

22.5 Other Government Documents, Drawings, and Publications

23.

REQUIREMENTS

23.1 General

23.1.1 Program Management

33.1.1.1 Technical and Management Work Planning

33.1.1.2 Development of a Contract Work Breakdown Structure (CWBS)

33.1.1.3 Work Scheduling

33.1.1.4 Financial Management

43.1.1.5 Risk Management

43.1.1.6 Contractor Manpower Reporting Application (CMRA)

43.1.2 Integrated Product Teams (IPTs)

53.1.3 Security

63.1.3.1 Operations Security (OPSEC)

63.1.4 Information Assurance (IA)

63.1.4.1 IA Process

63.1.4.2 IA Controls

63.1.4.3 IA Control Review

73.1.4.4 IA Scan (s)

73.1.4.4.1 Certification Test and Evaluation (CT&E)

73.1.4.4.1.1 CT&E Readiness Review and IA Scan Reports

73.1.4.4.2 CT&E Event

73.1.4.4.3 Personnel Security Requirements for Accessing Government Information Technology (IT) Systems

73.1.5 Government Furnished Information (GFI)

83.1.6 Government Furnished Equipment (GFE)

83.1.7 Government Purpose Rights (GPR)

83.1.7.1 Minimum Software and Technical Data Rights

93.1.8 Hardware and Software Purchase

93.1.8.1 Warranties, Licenses and Maintenance Agreements

93.2 Detailed Tasks

103.2.1 Trainer Modification Tasks

103.2.1.1 MH-47 Combat Mission Simulator (CMS) BLOCK Updates

103.2.1.2 ASTi Telestra 4 Installation

103.2.1.3 Simulated to Stimulated Common Avionics Architecture System (CAAS) Study for current MH-47/MH-60 CMS

103.2.1.4 MH-47 Stimulated CAAS Environment Conversion

103.2.1.5 MH-60 Stimulated CAAS environment conversion

103.2.1.6 MH-47 Visual Systems Upgrade

103.2.1.7 MH-60 Visual Systems Upgrade

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

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

113.2.1.10 Special Operations Forces Tactical Environment (SOFTAC) – MH-47 CMS

113.2.1.11

SOFTAC – MH-60 CMS

113.2.1.12 A/MH-6M Desk Top Trainer (DTT) Upgrade

113.2.1.13 LASAR CMS BLOCK Updates

113.2.1.14 LASAR CMS Miscellaneous Upgrades

113.2.1.15

MH-60 CMS

113.2.1.15.1 MH-60 CMS Full Authority Digital Engine Control (FADEC) Model Update

123.2.1.16 MH-60 CMS g-Meter Installation

123.2.1.17 Suite of Integrated Radio Frequency Countermeasures (SIRFC)

123.2.1.18 VHF/UHF LOS/SATCOM Radio

123.2.1.19 AN/ZSQ-2 Electro Optical Sensor (EOS)

123.2.1.20 SOA Common Avionics Architecture System (CAAS) Upgrade/ Concurrency

123.2.1.21 MH-47 CMS, MH-60 CMS and MH-47/MH-60 Health and Usage Monitoring System (HUMS)

123.2.1.22 MH-47 CMS, and MH-60 CMS Engine Flight Performance Model (EFPM) Update

123.2.1.23 MH-47 CMS and MH-60 CMS AN/ARS-6(V)12 Personnel Locator System (PLS) Radio Model

133.2.1.24 MH-47 CMS Unique Changes

133.2.1.25 MH-60 CMS Unique Changes

133.2.1.26 MH-60 CMS and MH-47 CMS Instructor/Operator Station (IOS) Malfunctions

133.2.1.27 MH-47/MH-60 Desktop Trainer (DTT)

133.2.1.28 MH-47 CMS and MH-60 CMS CAAS Re-host Architecture Upgrade

133.2.1.29 Simulation Interoperability

133.2.1.30 High Definition Non-Motion Flight Simulators (Outstation)

133.2.1.30.1 Interim Contractor Support (ICS)

143.2.1.30.1.1 Mission Capability

143.2.1.30.1.2 Mission Capability Calculation

143.2.1.30.1.3 Contracted Mission Time

143.2.1.30.1.4 Engineering Support Availability

153.2.1.30.1.4.1 Engineering Support Availability Calculation

153.2.1.30.1.5 Contracted Engineering Support Time

153.2.1.30.1.6 Scheduled External Engineering Notification

153.2.1.30.2 Transition Phase Out

163.2.2 Systems Engineering Processes

163.2.2.1 System Requirements Definition

163.2.2.2 System Requirements Analysis and Traceability

163.2.2.3 System Architectural Design

163.2.2.4 System Integration

163.2.2.5 System Qualification Testing

173.2.2.6 Software Development

173.2.2.6.1 Software Installation

173.2.2.6.2 Software Product

173.2.2.6.2.1 Installation and Configuration Procedures

183.2.2.6.2.2 Media and Storage Devices

183.2.2.6.2.3 Automated Processes

183.2.2.6.2.4 Contractor Execution

193.2.2.7 Aircraft/Combat System Configuration Concurrency Management

193.2.2.8 Reliability and Maintainability (R&M) Engineering

193.2.2.8.1 Failure Reporting, Analysis and Corrective Action System (FRACAS)

193.2.2.8.2 Reliability and Maintainability (R&M) Predictions

193.2.2.9 Human Factors Engineering

203.2.3 Conferences and Reviews

203.2.3.1 Post Award Conference (PAC)

213.2.3.1.1 PAC Entry Criteria

213.2.3.1.2 PAC Exit Criteria

213.2.3.2 System Requirements Review/System Functional Review

223.2.3.2.1 SRR/SFR Entry Criteria

223.2.3.2.2 SRR/SFR Exit Criteria

233.2.3.3 Preliminary Design Review (PDR)

233.2.3.3.1 PDR Entry Criteria

233.2.3.3.2 PDR Exit Criteria

233.2.3.4 Critical Design Review (CDR)

243.2.3.4.1 CDR Entry Criteria

243.2.3.4.2 CDR Exit Criteria

243.2.3.5 Engineering Design Review (EDR)

243.2.3.6 Integrated Product Team (IPT) Meetings

253.2.3.7 In-Process Reviews (IPR)

253.2.3.8 Test Readiness Review (TRR) Conferences

253.2.4 Commercial and Non-Developmental Items (CaNDI)

253.2.5 Parts Standardization

253.2.5.1 Parts Management

253.2.5.1.1 Exempt Hardware

263.2.6 System Safety Tasks

263.2.6.1 Safety Assessment (SA)

263.2.7 Electrostatic Discharge Control

263.2.8 Quality Management System Requirements

273.2.8.1 Control of GFE

273.2.8.2 Use of Contractor’s Inspection Equipment

273.2.8.3 Inspection and Test Records

273.2.9 Product Assurance Audits and Inspections

273.2.10 System Test and Evaluation (T&E)

283.2.10.1 Responsibility for Tests

283.2.10.2 Test Authority

283.2.10.3 Test Resources and Facilities

283.2.10.4 Test Methods

283.2.10.5 Test Criteria

293.2.10.6 Tolerance Data

293.2.10.7 Alignment

293.2.10.8 Test Log

293.2.10.9 Changes During Testing

293.2.10.9.1 Software Changes During Government Testing

293.2.10.10 Changes After Testing

303.2.10.11 T&E Deficiency Reporting System

303.2.10.11.1 Deficiency Report (DR) Categories

303.2.10.12 T&E Program Components

303.2.10.12.1 Baseline Configuration Audit

313.2.10.12.2 In-Process Inspections

313.2.10.12.3 Conformance Inspections

313.2.10.12.3.1 Functional Configuration Audit

313.2.10.13 Contractor Verification Testing

323.2.10.13.1 Test Readiness Review

323.2.10.13.1.1 TRR Entry Criteria

333.2.10.13.1.2 TRR Exit Criteria

333.2.10.14 Government Acceptance Testing (GAT)

343.2.10.14.1 GAT Entry Criteria

343.2.10.14.2 GAT Exit Criteria

353.2.10.15 Physical Configuration Audit (PCA)

353.2.10.16 Logistics Support Analysis

353.2.10.16.1 Supportability Analysis and Logistics Management Information

353.2.10.16.2 Transition

363.2.10.17 Technical Publications

363.2.10.17.1 Operator’s Manual

363.2.10.17.2 Maintenance Manual

363.2.10.17.3 Commercial Manuals

363.2.10.17.4 Publications in Process Reviews (IPRs)

373.2.10.17.5 Publications Validation

373.2.10.18 Training

373.2.10.18.1 Instructor and Operator Training

383.2.10.18.2 Maintenance Training

383.2.11 Software Configuration Management (SCM) Program

383.2.11.1 Government Participation in SCM Control Board

383.2.11.2 Software Build Schedules

383.2.11.3 CM Documentation

393.2.11.4 Configuration Control

393.2.12 Associate Contractor Agreements (ACA)

403.2.13 Software Licensing and Distribution Agreements

403.2.14 Facility Requirements

403.2.14.1 On-Site Safety

403.2.14.2 Hazardous Materials

403.2.14.3 Raised Access Floor

403.2.14.4 Facility Engineering Analysis

403.2.14.5 Facility Modifications

413.2.14.6 Equipment Installation and Removal

413.2.14.6.1 Modification Approach

413.2.14.6.2 Modification Tools and Test Equipment

413.2.14.6.3 Modification Spares.

413.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)

1. SCOPE

This Statement of Work (SOW) establishes the contractor tasks for the modifications to be made to the Special Operations Aviation suite of Combat Mission Simulators (CMSs), to include the Light Assault/Attack Reconfigurable (LASAR) A/MH-6M CMS, all of the MH-60 CMSs, and all of the MH-47 CMSs located at the 160th Special Operations Aviation Regiment [SOAR(A)] Ft. Campbell, KY. This includes all peripheral equipment and capabilities that support live, virtual and constructive training including the Exercise Management Control (EMC), the Mission Rehearsal Operations Center (MROC), Storage Area Network (SAN), Desk Top Trainers (DTT), and associated systems.

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 capable of supporting current mission profiles and stay current with operational systems enhancements and upgrades.

1.2 Objectives

The objective of this on-going effort is to fully support SOAR(A) training operations to include, concurrency and functionality enhancements to the suite of Combat Mission Simulators (CMSs) and related devices with the respective aircraft platforms, and the production/fielding of outstation simulation capability to minimize burdens of consolidated training throughput and maximize the training effectiveness of tenant battalions.

2. Applicable Documents The following documents of issue shown on the document summary list form a part of this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of the SOW shall be the governing requirement.

2.1 Government Documents

MIL-STD-130N

Identification Marking of U.S. Military Property

MIL-STD-31000

Technical Data Package

MIL-HDBK-470A

Notice 1 Designing and Developing Maintainable Products and Systems PEO STRI Basic Accreditation Manual (BAM) - Appendix D DIACAP Stand-alone System IA Process

DIACAP Implementation Plan (DIP) for Standalone System for Mission Assurance Category (MAC) II, Confidentially Level Secret. The Standalone DIP has 32 controls.

2.2 Non-Government Documents

ISO 9001:2008

Quality Management Systems

ISO 18000-7

Radio Frequency Identification (RFID) for item management

IEEE 12207:2008

System and Software Engineering Processes

GEIA-STD-0007-A

Logistics Product Data

GEIA-HB-0007-A

Handbook and Guide for Logistics Product Data

2.3 Department of Defense Directives

DODD 8570.01

Information Assurance (IA) Training, Certification, and Workforce Management

2.4 Department of Defense Instructions

DODI 5000.2

Operation of the Defense Acquisition System

2.5 Other Government Documents, Drawings, and Publications

DISR

Department of Defense (DoD) Information Technology Standards Registry National Security Telecommunications and Information Systems Security

Policy (NSTISSP) No. 11, Subject: National Policy Governing the Acquisition of Information Assurance (IA) and IA-Enabled Information Technology (IT) Products.

AR 380-5

Department of the Army Information Security Program

AR 25-2

Information Assurance AR 25-2 BBP 08-CO-M-0001, Information Technology Contingency Plans and Testing.

DA PAM 25-1-2, Information Technology Contingency Planning, 16 November 2006

AFARS 5139.01, Acquisition of Information Technology

3. REQUIREMENTS

3.1 General

3.1.1 Program Management

The contractor shall organize, coordinate, and control the program activities to ensure compliance with the contract requirements and the timely delivery of the required modifications and related products and services. The contractor shall provide the necessary program management, systems engineering, design engineering, materials, services, equipment, facilities, testing, technical, logistics, manufacturing, and clerical support for the efforts described in this SOW and further refined in the individual DO SOW and Specification. The contractor shall measure, monitor and assess the progress of the work performed and costs incurred under the contract. The government expects the structure of program management for this contract to be streamlined, responsive, flexible, and able to make decisions without unnecessary delays from staffing or bureaucratic processes. When applicable the government will use an Integrated Product Team (IPT) approach to fulfilling requirements on this contract.

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.1.1 Technical and Management Work Planning

The contractor shall develop and maintain a plan to formulate its management and technical approach to ensure compliance with the contract requirements and the timely delivery of the required products and services. The contractor shall identify and document events, accomplishments, and criteria pursuant to successful completion of the work efforts as defined in each Delivery Order (DO).

3.1.1.2 Development of a Contract Work Breakdown Structure (CWBS) The contractor shall develop and maintain a CWBS and a CWBS dictionary that defines the work structures required to perform this contract. The CWBS shall serve as the framework for contract planning, budgeting, and reporting of cost, schedule, and performance. The CWBS shall be extended to lower levels representing the scope of this SOW and which represent the plan to accomplish the entire contract work scope consistent with internal organizations and processes. The CWBS dictionary shall define and describe each element of the CWBS. The CWBS and dictionary shall be updated as changes occur.

3.1.1.3 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 the interaction for the efforts required for development and delivery of 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 individual DO IMS to assure that these milestones are met and to assure deliveries as required by the contract. The contractor shall prepare the IMS IAW the Data Item Description (DID). (DI-MGMT-81650)

3.1.1.4 Financial Management

The contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The contractor shall document and track the status of all appropriated funds associated with the contract, and each DO under the contract, to include payments, cancellations and invoices against each contract line item and sub-line item. The contractor shall document and track to levels which represent how they plan to accomplish the entire contract work scope and which are consistent with internal organizations and processes. These documents shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status. The contractor shall identify major elements of subcontracted work.

3.1.1.5 Risk Management

The contractor shall conduct risk management to systematically control the uncertainty in the project’s ability to meet cost, schedule, supportability and performance objectives. The contractor shall conduct that part of risk management that directly impacts the technical effort and involves risk-management preparation, risk identification, risk assessment, risk-handling option assessment, risk analysis, risk mitigation and risk control, including but not limited to scheduling of manpower requirements when more than one DO is awarded. Risk management to product requirement objectives shall be covered at all program and technical reviews, and at any time the contractor identifies a potential impact to cost, schedule, and performance in a given DO. Early identification of risk, proactive measures to mitigate it, and communication with the Government are expected. The contractor shall use their internal risk management tools to perform risk management. The contractor shall provide Government insight into the contractor’s tools, assessment, mitigation, and control techniques. The contractor shall document risk management as part of the CPSMR.

3.1.1.6 Contractor Manpower Reporting Application (CMRA)

The contractor and all subcontractors shall create an account and input data for all services performed under this contract within CMRA, to include all delivery/task orders issued against this contract. This input is required to be accomplished on a Government fiscal year basis (1st of October though 30th of September).

3.1.2 Integrated Product Teams (IPTs)

The contractor shall define, document, implement, and maintain an IPT structure for the duration of the contract and as required by individual DOs. The purpose of an IPT is to bring together the functions that have a stake in the performance of a product or process and concurrently make integrated decisions affecting that product or process. IPT membership will consist of multi-functional stakeholders working together with a product-oriented focus. Each IPT will be empowered to make critical life cycle decisions regarding each product or process within their purview. IPTs will be applied at various levels ranging from the overall structure of an organization to informal groups functioning across existing units. The IPTs listed below may be established for this program and as required by the individual delivery task/order mutually agreed upon by the contractor and the Government. Each IPT will consist of Government and contractor personnel. Each IPT will publish an agenda before each meeting. Each IPT will record and maintain meeting minutes. IPT minutes shall be shared among and between the other IPTs. Examples of IPTs that may be required per the requirements in each DO are:

a. Management IPT. The purpose of the Management IPT is to manage and control all efforts related to the development, delivery, and initial support of the modifications to the affected CMS. The IPT shall coordinate the activities of all other IPTs formed for this program. Risk Management is a primary focus of this IPT.

b. Systems Engineering, Integration, Test and Evaluation IPT (SEIT IPT). The purpose of the SEIT IPT is to review and discuss design information (including technical documentation), technical planning, systems engineering, integration, and testing and verification requirements and supportability issues. The SEIT IPT shall identify and resolve potential problem areas related to the modification to the affected CMS.

c. Software IPT (SW IPT). The purpose of the SW IPT is to review and discuss software design information (including technical documentation) and software related issues. The SW IPT shall identify and resolve potential problem areas related to the affected CMS software.

d. Integrated Logistics Support IPT (ILS IPT). The purpose of the ILS IPT is to review and discuss reliability and maintainability engineering, maintenance planning, supply support, technical publications and training related issues. The ILS IPT shall identify and resolve potential problem areas related to the affected CMS logistics analysis and support.

e. Data Resolution IPT (DR IPT). The purpose of the DR IPT shall be to review and discuss data issues as necessary to meet the specified fidelity requirements. The DR IPT participants shall include Government representatives, appropriate technical experts from other Government agencies, and contractor technical personnel. The DR IPT shall provide a forum for reconciling issues such as aircraft data sources, the quantity/quality of data to be used, data reduction methods required to accurately describe the characteristics of the design basis aircraft in terms of simulator specific parameters, and other data issues as necessary to meet the specified fidelity requirements.

3.1.3 Security

The security requirements specified herein shall apply to the prime contractor and all subcontractors. In general, the contractor shall use discretion concerning all matters on site involving the systems, equipment, and relationships concerning the customer. This includes, but is not limited to written, electronic, and verbal communication, marketing and advertising work or products referencing the customer, and also applies to all subcontract organizations.

All contractor personnel working at the 160th SOAR(A) facilities shall be U.S. citizens, and possess and maintain an active Secret security clearance. Submission of an individual without a clearance must be approved by the Government point of contact at the 160th SOAR(A) Fort Campbell, KY. The Government will assist in obtaining badges and access cards as necessary.

The contractor shall safeguard all classified information and meet all Security and Information Assurance requirements identified in the DD Form 254. The contractor shall enforce these safeguards throughout the life of the contract including the transport, delivery/fielding phases, and storage.

The contractor shall have a classified facility clearance in the event that they need to perform any work at their facility which requires the use of classified data. The contractor may be required to have a Sensitive Compartment Information Facility (SCIF), in the event one is required the contractor can leverage from a subcontractor SCIF if one already exists.

The contractor shall observe discretion when handling all information dealing with this contract, its customers, and facilities. Even if deemed Unclassified, conversations outside the workplace, specific reference to the customers, and any other exchange of information not required for the effort, should be kept to a minimum.

3.1.3.1 Operations Security (OPSEC)

The contractor shall provide and enforce OPSEC protection for all classified and sensitive information. Security policy, procedures, and requirements for classified information are provided in DoD 5220.22-M. The contractor shall safeguard all sensitive and critical program information IAW 160th SOAR(A) Operations Security (OPSEC) policy. The contractor shall enforce these safeguards throughout the life of the contract from development through support.

3.1.4 Information Assurance (IA)

3.1.4.1 IA Process

The contractor shall establish an IA process IAW the PEO STRI Basic Accreditation Manual (BAM). The contractor shall develop and maintain a robust information assurance process to guide the system’s design, document IA decisions, and identify and implement IA requirements. The contractor shall assist the government in the preparation of IA system documentation. The contractor shall establish configuration management of the product baseline, implement operational system security control measures and support IA certification testing. The contractor shall identify and use IA approved solutions to include IA approved operating systems, IA approved network devices, and IA approved software.

3.1.4.2 IA Controls

The contractor shall implement IA controls and take action to address inherent system vulnerabilities and weaknesses. The contractor shall ensure that all Port Protocol Service (PPS) not required in the operation of the system have been disabled or shut down and implement “deny all, permit by exception” (DAPE) enforcement for all PPS not being used by the system. The contractor shall plan and implement IA e.g. using Security Technical Implementation Guides (STIG), and government approved IA scanning tools, as required for Standalone, MAC II classified, along with the corresponding IA Controls as identified in the Standalone DoD Information Assurance Certification and Accreditation Process (DIACAP) Implementation Plan (DIP).

3.1.4.3 IA Control Review

The contractor shall support an IA Control Review / DIACAP Implementation Plan Review (DIPR) held at least 10 working days prior to the Critical Design Review (CDR). The IA Control Review/DIPR shall address at a minimum:

· Update on DIP

· Update Preliminary Data Flow and Accreditation Boundary Diagram

· Update on the hardware/software lists and procurement action

· Update on contractor IA training as applicable and the use of IA Scanning tools

· Update on design and system integration schedule

3.1.4.4 IA Scan (s)

During system development the contractor shall periodically scan the system using the latest DoD approved scanning tools. The contractor shall maintain Information Assurance Vulnerability Alert (IAVA) compliance of the system baseline(s), and provide software patch updates to the government as required throughout the life of the delivery order.

3.1.4.4.1 Certification Test and Evaluation (CT&E)

3.1.4.4.1.1 CT&E Readiness Review and IA Scan Reports

The contractor shall support a CT&E Readiness Review held no more than 7-14 working days prior to the CT&E Event. The CT&E Readiness Review and Scan Report shall address at a minimum:

· Final IA Scans Report of the system

· Corrective actions taken and written analysis of any open deficiencies

· Update of IA system documents

· Finalization of travel arrangement in support of the CT&E event The contractor shall prepare the IA Scan Reports IAW the DID (DI-MISC-80711A)

3.1.4.4.2 CT&E Event

The contractor shall support the CT&E event. The CT&E event is conducted by the IA independent certifier to assess the overall security posture of the system prior to Government Acceptance Test (GAT). The status of the results for all assigned IA controls and security requirements are complied and discussed with the contractor. The contractor shall provide support to address the findings from the CT&E events to the Government’s satisfaction after the Scorecard is tabulated, and assist the government in the preparation of the Plan of Action and Milestone (POA&M).

3.1.4.4.3 Personnel Security Requirements for Accessing Government Information Technology (IT) Systems

The contractor shall comply with the Information Assurance and Personnel Security Requirements for Accessing Government Information Technology (IT) Systems.

3.1.5 Government Furnished Information (GFI)

The Government will provide agreed upon technical data necessary to accomplish the objectives of this SOW based on the contractor’s proposal. Any Government technical data, above and beyond that which is stated in the formal attachment to the negotiated base award, shall be specified and the terms for delivery negotiated, per the award of each DO. In the event that technical data is requested after order award, the Government shall NOT be responsible for providing this data in a timely manner nor will it be held liable for any subsequent cost/schedule/performance delays, or other negative program impacts caused by the lack of, or delay, in acquiring said data. Requests for additional GFI made after order award shall not be approved without prior determination and formal consent from the Government Procuring Contracting Officer (PCO). If, upon determination by the PCO, the specific technical data cannot be provided in a timely manner, the contractor shall be responsible for securing the technical data via alternate data collection or generation methods. Additionally, the Government will not be held responsible for any cost, schedule delays, or other negative program impacts due to GFI that the contractor can independently gain access to, but elects not to out of convenience. Upon completion of performance for all delivery/task orders under this contract which utilize GFI, it shall be the contractor’s responsibility to properly pack and deliver all GFI to the Government designated location and/or to facilitate disposition with the designated ACO administering this contract.

3.1.6 Government Furnished Equipment (GFE)

The Government will provide agreed upon equipment necessary to accomplish the objectives of this SOW based on the contractor’s proposal. Any Government equipment, above and beyond that which is stated in the formal attachment to the negotiated base award, shall be specified and the terms for delivery negotiated, per the award of each DO. In the event that equipment is requested after order award the Government shall NOT be responsible for providing this data in a timely manner nor will it be held liable for any subsequent cost/schedule/performance delays, or other negative program impacts caused by the lack of, or delay in, acquiring said data. Requests for additional GFE made after order award shall not be approved without prior determination and formal consent from the PCO. If, upon determination by the PCO, the specific GFE cannot be provided in a timely manner, the contractor shall be responsible for securing the equipment via alternate materiel sources or providers, or manufacturing methods. Additionally, the Government will not be held responsible for any cost, schedule delays, or other negative program impacts due to GFE that the contractor can gain access to independently, but elects not to out of convenience. Upon completion of performance for all delivery/task orders under this contract which utilize GFE, it shall be the contractor’s responsibility to properly pack and deliver all GFE to the Government designated location and/or to facilitate disposition with the designated ACO administering this contract.

3.1.7 Government Purpose Rights (GPR)

The contractor shall provide sufficient rights in technical data, both software and hardware, such that the Government can maintain and modify the system(s) using government personnel and third party contractors. The Government is sensitive to proprietary implications on the family of systems supporting special operations aviation. The contractor shall analyze feasible non-proprietary solutions and incorporate them when applicable to the effort. This includes, but is not limited to, software rights, data, source codes, drawings, warranties, and integration efforts.

3.1.7.1 Minimum Software and Technical Data Rights

The contractor shall provide technical solutions that provide a minimum of Government Purpose Rights for any software or technical data developed on this program as specified in DFARS 252.227-7013 Rights in technical data – Noncommercial items and DFARS 252.227-7014 – Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation. The Government shall retain Government Purpose rights for a five year period beginning on the date of Government acceptance. Upon expiration of the five-year period, the Government shall have unlimited rights in any applicable technical data.

3.1.8 Hardware and Software Purchase

The contractor shall purchase all Commercial Off-The-Shelf (COTS) desktop, notebook, computers and video teleconferencing equipment, by using Computer Hardware, Enterprise Software and Solutions (CHESS) website (https://chess.army.mil) in compliance with AFARS 5139.01; The contractor shall use CHESS as the Primary Source for Procuring Commercial Information Technology (IT) Hardware and Software. The Army has mandated the Universal Gold Master (UGM) as the Windows-based standard operating system. UGM license can be obtained from CHESS or Softmart (http://www.softmart.com). If UGM cannot be used, (contractor shall provide written explanation as to why UGM cannot be used.) an IA approved operating system shall be configured IAW the latest DISA Security Technical Implementation Guides (STIG), written for that operating system.

For hardware and software products not available through CHESS or Softmart, the contractor shall select the IA validated products from one of the links below.

1. Common Criteria Certified Products http://www.commoncriteriaportal.org/products.html

2. The Common Criteria Evaluation and Validation Scheme - NIAP Validated Product List http://www.niap-ccevs.org/cc-scheme/vpl/

3. Approved Products List Integrated Tracking System (APLITS) – CAC Card is required.

https://aplits.disa.mil/processAPList.do *There will be no wavier issued by the Government for unapproved IA products.

All software (developed, Government Off-The-Shelf (GOTS) or Commercial-Off-The-Shelf (COTS)) shall be delivered IAW the DID. (DI-MCCR-80700)

3.1.8.1 Warranties, Licenses and Maintenance Agreements

Standard commercial warranties shall be made available to the Government. The Contractor shall offer manufacturer extended warranties for products on this contract, where applicable and available, IAW AMS T3.10.4 (5d Commercial Items). Warranties shall be effective from the time of Government acceptance (when possible), to be specified per individual order. Extended warranties will be made available at the time of product purchase.

Warranties, licenses and maintenance agreements shall be in support of the products offered under this contract. Warranties, licenses and maintenance agreements for related items not purchased under this contract that expire within the term of this contract may be reinstated or renewed under this contract.

3.2 Detailed Tasks

The following comprise a list of identified tasks for this contract which will be further delineated at the individual DO level. Due to emerging technologies, unscheduled changes to airframe configurations to meet mission needs and other un-forecasted events, the contractor shall be able to rapidly and efficiently support these requirements as they arise and under the terms dictated in individual DO documentation. This list is not inclusive of every required task required under this contract; there may be tasks required to support ARSOA training requirements that fall within the scope, but not specifically outlined herein.

3.2.1 Trainer Modification Tasks

The contractor shall design, develop, fabricate, integrate, deliver, install, and test the trainer modifications specified in the DO/Task SOW and its associated Specification. The contractor shall ensure that no current capabilities are lost or diminished as a result of any trainer modifications. These tasks include, but are not limited to, the following:

3.2.1.1 MH-47 Combat Mission Simulator (CMS) BLOCK Updates

The contractor shall update the MH-47 CMS to the most current MH-47 aircraft BLOCK configuration implementing the functionality listed below.

3.2.1.2 ASTi Telestra 4 Installation

The contractor shall remove the existing ASTi Digital Audio Communication System (DACS) from the MH-47 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.

3.2.1.3 Simulated to Stimulated Common Avionics Architecture System (CAAS) Study for current MH-47/MH-60 CMS

The contractor shall conduct a study to identify the necessary tasks required to accomplish a conversion of the CMSs with simulated CAAS architecture and hardware to a stimulated CAAS environment IAW the individual DO Specification and the corresponding SOW .

3.2.1.4 MH-47 Stimulated CAAS Environment Conversion

The contractor shall convert the current simulated Special Operation Aviation (SOA) CAAS environment in the MH-47 CMS to a stimulated SOA CAAS environment.

3.2.1.5 MH-60 Stimulated CAAS environment conversion

The contractor shall convert the current simulated SOA CAAS environment in the MH-60 CMS to a stimulated SOA CAAS environment.

3.2.1.6 MH-47 Visual Systems Upgrade

The contractor shall upgrade all visual systems/subsystems, to include but not limited to the removal and replacement the currently installed Image Generators (IGs) and projectors in the MH-47 simulators with the 160th common visual solution IGs and Projectors, IAW the individual DO Specification and the corresponding SOW.

3.2.1.7 MH-60 Visual Systems Upgrade

The contractor shall upgrade all visual systems/subsystems, to include but not limited to the removal and replacement the currently installed Image Generators (IGs) and projectors in the MH-60 simulators with the 160th common visual solution IGs and Projectors, IAW the individual DO Specification and the corresponding SOW.

3.2.1.8 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 IAW the individual DO Specification and the corresponding SOW.

3.2.1.9 Instructor Operator Station (IOS) Graphical User Interface (GUI) for the MH-60-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-60-2 CMS IAW the individual DO Specification and the corresponding SOW.

3.2.1.10 Special Operations Forces Tactical Environment (SOFTAC) – MH-47 CMS

The contractor shall replace the existing MH-47 CMS Computer Generated Forces/ Semi Automated Forces (CGF/SAF) control with the 160th SOAR common solution for the tactical environment.

3.2.1.11 SOFTAC – MH-60 CMS

The contractor shall replace the existing MH-60 CMS Computer Generated Forces/ Semi Automated Forces (CGF/SAF) control with the 160th SOAR common solution for the tactical environment.

3.2.1.12 A/MH-6M Desk Top Trainer (DTT) Upgrade

The contractor shall upgrade the A/MH-6M DTT IAW the individual DO Specification and corresponding SOW.

3.2.1.13 LASAR CMS BLOCK Updates

The contractor shall update the LASAR CMS to the required A/MH-6M aircraft BLOCK configuration implementing the functionality listed in the individual DO SOW and respective Specification.

3.2.1.14 LASAR CMS Miscellaneous Upgrades

The contractor shall update the LASAR CMS by implementing the required functionality changes as identified in the individual DO Specification and corresponding SOW.

3.2.1.15 MH-60 CMS

3.2.1.15.1 MH-60 CMS Full Authority Digital Engine Control (FADEC) Model Update The contractor shall maintain concurrency of the FADEC Model, to include but not limited to the updating, integration and testing of the latest FADEC software version and related functionality to include FADEC training modes into the MH-60 CMS FADEC model, IAW the individual DO Specification and corresponding SOW.

3.2.1.16 MH-60 CMS g-Meter Installation

The contractor shall install a simulated g-Meter into the MH-60 CMS IAW the individual DO Specification and corresponding SOW. The g-Meter shall function as in the design basis aircraft.

3.2.1.17 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 CMSs and MH-60 CMSs, IAW the individual DO Specification and corresponding SOW.

3.2.1.18 VHF/UHF LOS/SATCOM Radio

The contractor shall maintain concurrency of the VHF/UHF LOS/SATCOM Radio, to include but not limited to, the upgrade of the ARC-231 model to the latest configuration and software load in the MH-47 CMS, LASAR CMS and MH-60 CMS, IAW the individual DO Specification and corresponding SOW.

3.2.1.19 AN/ZSQ-2 Electro Optical Sensor (EOS)

The contractor shall update the EOS model IAW the individual DO Specification and corresponding SOW.

3.2.1.20 SOA Common Avionics Architecture System (CAAS) Upgrade/ Concurrency

The contractor shall integrate SOA CAAS updates into the MH-47 and MH-60 CMS’s as required to maintain airframe concurrency IAW the individual DO Specification and corresponding SOW. The primary integration strategy will be a “stimulated” approach, although a “simulated” strategy may be applicable.

3.2.1.21 MH-47 CMS, MH-60 CMS and MH-47/MH-60 Health and Usage Monitoring System (HUMS)

The contractor shall integrate and test any and all necessary changes to each HUMS resulting from the Integration of the latest version SOA CAAS into the MH-47 CMS, MH-60 CMS IAW the individual DO Specification and corresponding SOW.

3.2.1.22 MH-47 CMS, and MH-60 CMS Engine Flight Performance Model (EFPM) Update

The contractor shall maintain concurrency of the EFPM. This may include, but not limited to integrate and test the Engine Flight Performance Model (EFPM) updates in the MH-47 CMS, and MH-60 CMS IAW the individual DO SOW and associated Specification.

3.2.1.23 MH-47 CMS and MH-60 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 CMS and MH-60 CMS IAW the individual DO Specification and corresponding SOW.

3.2.1.24 MH-47 CMS Unique Changes

The contractor shall integrate and test changes unique to the MH-47 CMS as a result of SOA CAAS upgrades IAW the individual DO Specification and corresponding SOW.

3.2.1.25 MH-60 CMS Unique Changes

The contractor shall integrate and test changes unique to the MH-60 CMS as a result of SOA CAAS upgrades IAW the individual DO Specification and corresponding SOW.

3.2.1.26 MH-60 CMS and MH-47 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 latest SOA CAAS version into the CMS IAW the individual DO Specification and corresponding SOW.

3.2.1.27 MH-47/MH-60 Desktop Trainer (DTT)

The current version of the MH-47/MH-60 DTT shall be updated with the functionality resulting from the implementation of the latest version of SOA CAAS IAW the individual DO Specification and corresponding SOW.

3.2.1.28 MH-47 CMS and MH-60 CMS CAAS Re-host Architecture Upgrade

The contractor shall recapitalize all of the computers which drive and are associated with the CMS CAAS functionality IAW with the individual DO Specification and corresponding SOW.

3.2.1.29 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 IAW the individual DO Specification and corresponding SOW.

3.2.1.30 High Definition Non-Motion Flight Simulators (Outstation) The contractor shall design, build, integrate and test a non-motion MH-47 CMS and MH-60 CMS for outstation use IAW the individual DO Specification and corresponding SOW. The Outstation simulators will be delivered/installed in the west coast and east coast, not in Ft Campbell, KY.

The contractor design shall leverage from the full motion CMSs installed at Ft Campbell, KY, to provide as much hardware and software commonality as possible. These simulators shall not be deployable.

3.2.1.30.1 Interim Contractor Support (ICS)

Interim Contractor Support may be necessary in the event that a DO is awarded for Outstation Simulation. The contractor shall perform the tasks necessary to operate, maintain and support the fielded systems as defined by each specific DO. This ICS shall be for an interim period, not to exceed twelve (12) months or until adequate transition of this responsibility can be achieved. The contractor shall provide all supplies, services, materials and system/configuration management necessary to perform (ICS). The contractor shall provide all operational site support, hardware, software maintenance and spares maintenance. The contractor shall maintain a high level of security awareness commensurable with the Mission Assurance Category (MAC) and Confidentiality Level. The contractor shall implement the Army approved Information Assurance Vulnerability Management program during the ICS period and shall assist in compliance reporting. (DI-MGMT-80227, DI-MISC-80711A)

3.2.1.30.1.1 Mission Capability

The contractor shall meet or exceed the Available Mission Capability Rate of 95% for supported systems and equipment. The contractor shall perform a special analysis in the event the 95% mission capability rate is not attained to determine the cause and the corrective action required to prevent a recurrence. The contractor shall prepare the Contractor Device Performance Report (CDPR) IAW the DID. (DI-ILSS-80191D)

3.2.1.30.1.2 Mission Capability Calculation

The contractor shall populate, verify and validate the Unit Level Logistics System-Aviation (ULLS-A) system input daily to ensure accuracy in the calculation of mission capable rates. The formula to determine the monthly and yearly mission capability rates is as follows:

A0 = [(x+y-z) / (x+y)]*100 = %

Where:

x = Site Core Operational hours (8 hrs a day, 5 days a week) y = Surge directed/authorized hours (Outside the Core hours) z = Hours that the systems and equipment are scheduled to be in a full or operational readiness state (Core hrs and Surge hrs) but unable to support the required mission rehearsal, training, simulation, exercise, testing or demonstration efforts.

3.2.1.30.1.3 Contracted Mission Time

The Contracted Mission Time (CMT) is eight (8) hours per day, five days per week (Monday – Friday). The contractor shall perform logistic, maintenance and specified operational support on systems and equipment to support site requirements. The contractor shall operate and maintain areas and systems and equipment of the facilities in a safe, responsible manner. The contractor shall provide operational personnel to include management personnel and technicians. In support of training development, the contractor shall support mission rehearsal, training exercises, demonstrations, tests, and experiments. The contractor shall prepare the Contractor Device Performance Report (CDPR) IAW the CDRL. (DI-ILSS-80191D)

3.2.1.30.1.4 Engineering Support Availability

The contractor shall meet or exceed the engineering support availability rate of 90% for supported systems and equipment. The contractor shall perform a special analysis in the event the 90% engineering support availability rate is not attained to determine the cause and the corrective action required to prevent a recurrence. The contractor shall prepare the Contractor Device Performance Report (CDPR) IAW the CDRL. (DI-ILSS-80191D)

3.2.1.30.1.4.1 Engineering Support Availability Calculation

The contractor shall populate, verify and validate the ULLS-A system input daily to ensure accuracy in the calculation of mission capable rates. The formula to determine the monthly and yearly engineering support availability rates is as follows:

A0 = [(x-y) / (x)]*100 = %

Where:

x = Scheduled External Engineering hours (based on scheduled engineering modifications) y = Hours that the systems and equipment are unavailable to support scheduled external engineering efforts.

3.2.1.30.1.5 Contracted Engineering Support Time

The contractor shall perform logistic, maintenance and specified support on systems and equipment to support site engineering requirements. The contractor shall operate and maintain areas and systems and equipment of the facilities in a safe, responsible manner. The contractor shall provide operational personnel to include management personnel and technicians, in support of systems modifications and upgrades. The contractor shall prepare the Contractor Device Performance Report (CDPR) IAW the CDRL. (DI-ILSS-80191D)

3.2.1.30.1.6 Scheduled External Engineering Notification

The Government will identify scheduled external engineering hours not less than 72 hours in advance of the requirement. Scheduled external engineering hours may include weekend or third shift hours. External engineering is conducted or performed by a third party contractor.

3.2.1.30.2 Transition Phase Out

During the last 60 days of the DO the contractor shall provide support to ensure a smooth transition and minimize any impact on the operational readiness and capabilities of the Training Aids, Devices, Simulator and Simulations (TADSS). The contractor shall provide access to site, Life Cycle Contractor Support (LCCS) activities, and to all documentation on a not-to-interfere basis during the new contract transition phase-in period. The contractor shall retain full responsibility for the TADSS until completion of the phase-out period. Prior to the expiration of the DO, a Government and contractor team shall jointly inventory all Government Furnished Property (GFP) and GFI during the phase-out period. The contractor shall be responsible for supplying replacements for missing or damaged items at the end of the contract performance period. The contractor shall also provide an accurate listing of parts at vendors for repair. The contractor shall certify the inventory after completion of the inventory. If any GFP item (s) are not repaired or replaced in the required transition period the Government may initiate action to have the item(s) repaired or replaced at the contractor expense. These costs will be withheld from the monthly maintenance contract line items in the contract. The contractor shall prepare the Physical Inventories Report (PIR) IAW the CDRL. (DI-MGMT-80259)

3.2.2 Systems Engineering Processes

The contractor shall use the system engineering processes to define the requirements for the system, to transform the requirements into an effective product, and to verify and validate the functionality of the delivered product. The contractor shall perform the following tasks listed below.

3.2.2.1 System Requirements Definition

The purpose of…