Attachment 1 - Statement of Work for the United States Marine Corps (USMC) Marine Common Aircrew Trainer (MCAT) FY24 Modernization Program (SOW 230027).pdf

CUI SOW 230027

4 March 2024

CUI

STATEMENT OF WORK

FOR

THE UNITED STATES MARINE CORPS (USMC)

MARINE COMMON AIRCREW TRAINER (MCAT)

FY24 MODERNIZATION PROGRAM

DEPARTMENT OF THE NAVY

NAVAL AIR WARFARE CENTER

TRAINING SYSTEMS DIVISION

12211 SCIENCE DRIVE

ORLANDO, FL 32826

APPROVED BY: DATE:

Kent Campbell Program Manager

APPROVED BY: DATE:

Cattien Nguyen USMC Engineering Branch Head

APPROVED BY: DATE:

Howie Hiser Assistant Program Manager Logistics (APML)

DISTRIBUTION STATEMENT D - Distribution authorized to U.S. Government Agencies and their U.S. DoD Contractors Only (Administrative or Operational Use) (23 OCT 2023). Other requests for this document shall be referred to the Commanding Officer, Naval Air Warfare Center Training Systems Division (NAWCTSD), 12211 Science Drive, Orlando, FL 32826.

DESTRUCTION NOTICE - For unclassified, limited distribution documents, destroy by a method that prevents disclosure contents or reconstruction of the document.

Controlled by: United States Department of the Navy

Controlled by: Naval Air Warfare Center Training System Division CUI Category: Controlled Technical Information

Distribution/Dissemination Control: Distribution Statement D POC: chris.willis@navy.mil

CUI

Revision History

Revision Affected Paragraph(s) Changes

Initial Release ii

Table of Contents

Section Title Page

1. SCOPE

1.1 Goals and Objectives

1.2 Background

1.3 Identification

1.4 Definitions

1.4.1 Commercial Item

1.4.2 Commercially Available Off-The-Shelf (COTS) Item

1.4.3 Computer Software

1.4.4 Computational Subsystem

1.4.5 Computational System

1.4.6 Days

1.4.7 Enclosure

1.4.8 Initial Support Kit (ISK)

1.4.9 Non-Developmental Item (NDI)

1.4.10 Terms Pertaining to the Evaluation and Utilization of Logistics

Product Data (LPD)

1.4.10.1 Essentiality Code (EC)

1.4.10.2 Item Name/Nomenclature

1.4.10.3 Long-Lead Item

1.4.10.4 Manufacturer’s Commercial and Government Entity (CAGE) Code

1.4.10.5 Mean Time Between Failures (MTBF)

1.4.10.6 Modifying Government Furnished Data

1.4.10.7 National Stock Number National Item Identification Number

(NSN/NIIN)

1.4.10.8 Original Equipment Manufacturer’s Part Number (OEM/P/N)

1.4.10.9 Parts Availability Code (PAC)

1.4.10.10 Provisioning List Item Sequence Number (PLISN)

1.4.10.11 Provisioning Remarks

1.4.10.12 Quantity Per End Item (QPEI)

1.4.10.13 Replacing Government Furnished Data

1.4.10.14 Supplementing Government Furnished Data

1.4.10.15 Supporting Data

1.4.10.16 Total Quantity Recommended (TQR)

1.4.10.17 Type of Change Code (TOCC)

1.4.10.18 Unit of Issue (UI)

1.4.10.19 Using Government Furnished Data

1.4.11 Trainer Peculiar Equipment (TPE)

2. APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 Non-Government Documents

3. REQUIREMENTS

3.1 General Requirements

Table of Contents

Section Title Page iii

CUI

3.1.1 MCAT MP Tech Refresh

3.1.2 MCAT DV 2H166A-2 Relocated from K-Bay to YUMA

3.1.3 Provisioning Item Orders

3.2 Detailed Tasks

3.2.1 Program Management

3.2.1.1 Work Planning and Scheduling

3.2.1.2 Program Planning

3.2.1.3 Life Cycle Mode Management

3.2.1.4 Infrastructure Management

3.2.1.5 Program Assessment and Control

3.2.1.6 Subcontractor Management and Reporting

3.2.1.6.1 Integrated Product Teams (IPTs)

3.2.1.7 Risk Management

3.2.1.8 Quality Management

3.2.1.8.1 Control of Government Furnished Equipment (GFE) and

Government Furnished Information (GFI)

3.2.1.8.2 Use of Contractor’s Inspection Equipment

3.2.1.9 Configuration Management (CM)

3.2.1.9.1 Configuration Control

3.2.1.9.2 Change Management

3.2.1.10 Configuration Identification Process (CIP)

3.2.1.10.1 Configuration Status Accounting

3.2.1.10.2 Configuration Audits

3.2.1.11 Information Management

3.2.1.12 Data Management

3.2.1.13 Transmission of Controlled Unclassified Information (CUI) via E-mail

3.2.2 Security

3.2.2.1 Classified Processing and Access to Classified Systems

3.2.2.2 Operation Security (OPSEC)

3.2.2.3 Unclassified Contractor-Owned Network Security – Safeguarding of CUI

3.2.2.4 Cyber Incident and Compromise Reporting

3.2.2.5 Access to DoD Installations, Government Information, and IT

Systems- Personal Security Background Checks and Defense Biometric Identification System

3.2.2.6 Personnel Security—Reporting of Adverse or Derogatory Information Related to Contractors

3.2.2.7 Government-Issued Personal Identification Credentials

3.2.2.7.1 Personnel Security – Background Checks

3.2.2.7.2 Cybersecurity Personnel Requirements for Accessing Government

Information Technology (IT) Systems - Credentialing Standards

3.2.2.7.3 Unclassified Contractor–Owned Network Security

iv

CUI

3.2.2.7.4 Information Security Requirements for Protection of Unclassified DoD Information on Non-DoD Systems

3.2.2.8 Contractor “Out-processing” Policy

3.2.2.9 Supply Chain Risk Management (SCRM) for National Security

Systems

3.2.2.10 Protection of Unclassified DoD Information on Non-DoD Systems

3.2.3 Cybersecurity

3.2.3.1 Initial Cybersecurity RMF Meeting

3.2.3.2 Cybersecurity Certification and Accreditation Support

3.2.3.3 Cybersecurity Compliance

3.2.3.4 Cybersecurity/Information Assurance (IA) Vulnerability

Management Program (IAVMP)

3.2.3.5 Cybersecurity Training

3.2.3.6 Contractor Cybersecurity Training and Certification

3.2.3.7 Travel and Modification of the MCAT

3.2.4 Systems Engineering Processes

3.2.4.1 System Requirements Analysis

3.2.4.2 Traceability

3.2.4.3 System Architectural Design

3.2.4.4 System Implementation

3.2.4.5 System Integration

3.2.4.6 System Verification

3.2.4.7 System Transition

3.2.4.8 Software Requirements Analysis

3.2.4.9 Software Architectural Design

3.2.4.9.1 Software Product Detailed Design

3.2.4.10 Software Systems Assessment (SSA)

3.2.4.10.1 Media and Storage Devices

3.2.4.10.2 Distributed Version Control System (DVCS)

3.2.4.10.3 Software Media Marking

3.2.4.10.4 Software Integration Readiness Meeting (SIRM)

3.2.5 Reliability and Maintainability (R&M) Engineering

3.2.5.1 Failure Reporting, Analysis and Corrective Action System

(FRACAS)

3.2.5.2 R&M Predictions

3.2.6 Human Factors Engineering (HFE)

3.2.7 Conferences and Reviews

3.2.7.1 Post Award Conference (PAC)

3.2.7.1.1 PAC Entry Criteria

3.2.7.1.2 PAC Completion Criteria

3.2.7.2 In-Process Reviews (IPRs)

3.2.7.2.1 System Requirements Review-II/System Functional Review (SRR-

II/SFR) (IPR)

3.2.7.2.1.1 SRR-II/SFR(IPR) Entry Criteria

v

CUI

3.2.7.2.1.2 SRR-II/SFR(IPR) Completion Criteria

3.2.7.2.2 Critical Design Review (CDR) (IPR)

3.2.7.2.2.1 CDR (IPR) Entry Criteria

3.2.7.2.2.2 CDR (IPR) Completion Criteria

3.2.7.2.3 Test Readiness Review (TRR)

3.2.7.3 Logistics Conferences and Reviews

3.2.7.3.1 Logistics Guidance Conference (LGC)

3.2.7.3.2 Training Program Orientation Conference (TPOC)

3.2.7.3.3 Provisioning Item Selection Conference (PISC)

3.2.7.3.3.1 PISC Entry Criteria

3.2.7.3.3.2 PISC Completion Criteria

3.2.7.3.4 Integrated Logistics Support Verification (ILSV) Conference

3.2.8 Commercial and Non-Developmental Items (CaNDI)

3.2.9 Parts Standardization

3.2.9.1 Parts Management

3.2.9.1.1 Exempt Hardware

3.2.9.1.2 System Hardware Warranties

3.2.10 System Safety Tasks

3.2.11 Product Assurance Audits and Inspections

3.2.12 System Test and Evaluation (T&E)

3.2.12.1 Responsibility for Tests and Inspections

3.2.12.2 Test Authority

3.2.12.3 Test Resources and Facilities

3.2.12.4 Test Methods

3.2.12.5 Test Criteria

3.2.12.6 Not Used

3.2.12.7 Technical Documentation/Drawing Updates

3.2.12.8 Trainer Facilities Reports (TFR)

3.2.12.9 Alignment

3.2.12.10 Testing Suspension

3.2.12.11 Regression Testing

3.2.12.12 Software and Hardware Changes During Government Testing

3.2.12.13 System Trouble Report (STR) and NAVAIR Deficiency Report

(DR) Reporting System

3.2.12.14 STR Severity Reporting System

3.2.12.15 System Trouble Review Board (STRB)

3.2.12.16 STR Adjudication

3.2.12.17 T&E Program Components

3.2.12.17.1 Baseline Configuration Audit (BCA)

3.2.12.17.2 Functional Configuration Audit (FCA)

3.2.12.17.2.1 Pre-Relocation Inspection/Test for Device 2H166A-2

3.2.12.17.2.2 Pre-Modification Inspection (PMI)

vi

CUI

3.2.12.17.2.3 DT-C1 (Contractor Testing at First Assigned Device Location & Device 2H166A-2 Post-Move to Yuma, AZ)

3.2.12.17.2.4 Test Readiness Review (TRR)

3.2.12.17.2.4.1 TRR Entry Criteria

3.2.12.17.2.4.2 TRR Completion Criteria

3.2.12.17.2.5 IT-C1 (Joint Contractor/Government Formal Testing at First

Assigned Device Location & Device 2H166A-2 Post-Move to Yuma, AZ)

3.2.12.17.2.6 IT-C1 (Joint Contractor/Government Formal Testing at First Assigned Device Location & Device 2H166A-2 Post-Move to Yuma, AZ) Completion Criteria

3.2.12.17.2.7 TRR IPR

3.2.12.17.2.8 TRR IPR Entry Criteria

3.2.12.17.2.9 TRR IPR Completion Criteria

3.2.12.17.2.10 IT-C2 (Joint Contractor/Government Follow-up Testing at

Remaining Locations)

3.2.12.17.2.10.1 IT-C2 (Joint Contractor/Government Follow-up Testing at

Remaining Locations) Completion Criteria

3.2.12.17.3 Integrated Logistics Support Verification (ILSV)

3.2.13 Integrated Logistics Support (ILS) Program

3.2.13.1 Maintenance Planning

3.2.13.2 Supportability Analysis

3.2.13.3 Training Device Inventory Checklist/Record (TDICL/R)

3.2.13.4 Bill of Materials (BOM) for Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management

3.2.13.5 Buy Through the Prime

3.2.13.6 DMSMS Management Plan

3.2.13.7 Inventory Management

3.2.13.8 Parts Procurement

3.2.13.9 Provisioning

3.2.13.10 Logistics Product Data (LPD)

3.2.13.11 Engineering Data for Provisioning (EDFP)

3.2.13.12 Technical Data Package (TDP)

3.2.13.12.1 TDP Validation

3.2.13.12.2 TD Verification

3.2.13.12.3 COTS License Rights

3.2.13.12.4 Third Party Copyrighted Data

3.2.13.13 Contractor Logistics Support (CLS)

3.2.13.13.1 Instructor/Operator Training

3.2.13.13.2 Equipment and Material Disposal

3.2.14 Packaging, Handling, Storage, and Transportation

3.2.15 Facility Clean Up

3.2.15.1 Hazardous Materials (HAZMAT)/Wastes

3.2.16 Safety

vii

CUI

3.2.17 Disassembly, Packaging and Relocation

3.2.17.1 Trainer Disassembly

3.2.18 Re-Assembly and Installation

3.2.18.1 Installation

3.2.18.2 Reassemble

3.2.19 Supplies

3.2.20 Cabling

3.2.21 Hoses and Tubes

3.2.21.1 Cabling and Hoses

3.2.21.2 Cable and Hose Marking

3.2.21.3 Shielding and Grounding

3.2.22 Facility Requirements

3.2.22.1 Site Survey/Analyses

3.2.22.2 Trainer Installation

3.2.22.3 Trainer Installation Support

3.2.23 Item Unique Identification (IUID) Assignment

Appendices Appendix Title Page A Abbreviations and Acronyms

Statement of Work For

The United States Marine Corps Marine Common Aircrew Trainer (MCAT)

FY24 Modernization Program (MP)

1. SCOPE

This Statement of Work (SOW) establishes the contractor tasks to modernize seven Marine Common Aircrew Trainer (MCAT) devices (2H166A-1, 2H166A-2, 2H166A-3, 2H166A-4, 2H166A-5, 2H166A-6, and 2H166B-1) and relocate device 2H166A-2.

1.1 Goals and Objectives

The overarching goals and objectives of the MCAT MP are to provide the products, engineering, and logistics to conduct Marine Corps distributed training through the integration of USMC Aviation Training Systems (MC ATS) with USMC ground training systems, Department of Defense training systems and distributed networks in the continental/contiguous United States (CONUS) and outside the CONUS (OCONUS).

1.2 Background

The MCAT provides realistic and relevant training for enlisted aircrew (EAC) of CH-53E, MV- 22B, and UH-1Y aircraft via simulation-based training systems. The MCAT enables the integration of functional cabin crew station positions for the current CH-53E, MV-22B, and UH- 1Y inventory of Marine Corps vertical lift aircraft.

1.3 Identification

For the purposes of this SOW, unless otherwise specified, the terms MCAT, trainers, trainer system, training system, system(s) device (DV), and training device are equivalent and refer to the following DVs:

a. DV 2H166A-1 located at MCAS, MATSS New River, Jacksonville, NC;

b. DV 2H166A-6 located at MCAS, MATSS New River, Jacksonville, NC;

c. DV 2H166A-3 located at MCAS, MATSS Miramar, San Diego, CA;

d. DV 2H166A-5 located at MCAS, MATSS Miramar, San Diego, CA;

e. DV 2H166A-2 located at MCAS, MATSS Kaneohe Bay, Kailua, HI;

f. DV 2H166B-1 located at MCAS, MATSS Camp Pendleton, Oceanside, CA; and

g. DV 2H166A-4 located at MCAS, MATSS Futenma, Okinawa, JP.

1.4 Definitions

The following definitions apply to this SOW.

CUI

1.4.1 Commercial Item

Commercial item is defined per Federal Acquisition Regulations (FAR) FAR 2.101, “Commercial Item”.

1.4.2 Commercially Available Off-The-Shelf (COTS) Item

COTS is defined per FAR 2.101, “COTS”.

1.4.3 Computer Software

Computer software is defined as computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae, and related material that would enable the software to be reproduced, recreated, or recompiled.

1.4.4 Computational Subsystem

A computational subsystem, also referred to as computer subsystem is a programmable electronic device that can store, retrieve, and perform prescribed mathematical and logical operations.

1.4.5 Computational System

A computational system is one or more computational subsystems, their peripheral devices, and network equipment working synergistically to satisfy a set of requirements.

1.4.6 Days

Days is defined per FAR 33.101, “Days”, unless indicated otherwise.

1.4.7 Enclosure

Enclosure is defined as the supporting structure that houses the training device and provides interface with the Government furnished facility (GFF) for the 2H166A series of MCAT devices.

1.4.8 Initial Support Kit (ISK)

The ISK includes

a. The initial spares (repairable items) and repair parts that are manufactured, subcontracted, or modified by the prime contractor having the design control responsibility.

b. The initial spares that support vendor hardware utilized by the device, which can be procured on the open market or from established sources and for which the prime contractor is not the design activity.

c. Support items that are not an integral part of an end item, but are required to inspect, test, calibrate, service, repair, or overhaul the end item, which are manufactured, subcontracted, or modified by the prime contractor having the design control responsibility.

d. Items required for support of the trainer system (excluding common hand tools), which can be procured on the open market or from established sources and for which the prime contractor is not the design activity.

CUI

1.4.9 Non-Developmental Item (NDI)

NDI is defined per FAR 2.101, “NDI”.

1.4.10 Terms Pertaining to the Evaluation and Utilization of Logistics Product Data (LPD)

1.4.10.1 Essentiality Code (EC)

EC is a numeric code to indicate the degree to which the failure of the part affects the ability of the end item to perform its intended operation as indicated below:

a. Failure to this part will render the end item inoperable.

b. Failure to this part will not render the training system inoperable, but will reduce the training capability of the system by over 50%.

c. Failure to this part will not render the training system inoperable, but will reduce the training capability of the system by less than 50%.

d. Failure to this part will not render the training system inoperable, but procurement time of a replacement item may cause an extended period of trainer down time that exceeds 6 months.

1.4.10.2 Item Name/Nomenclature

An identifying noun with appropriate adjective modifier, as contained in Cataloging Handbook H6. Item names contained in Cataloging Handbook H6 cannot be abbreviated unless approved by the requiring authority.

1.4.10.3 Long-Lead Item

The computed or expected time interval expressed in months between placement of a new contract and shipment of the first deliverable quantity.

1.4.10.4 Manufacturer’s Commercial and Government Entity (CAGE) Code

A five-character code assigned by the Defense Logistics Information Service (DLIS) to the design control activity or actual Manufacturer/Supply Company of an item as contained in the Cataloging Handbook H4/H8 Series.

1.4.10.5 Mean Time Between Failures (MTBF)

Mean time between failures (MTBF) for a particular interval is calculated by dividing total functional life of a population of an item by total number of failures within the population during the measurement interval. The definition holds for time, rounds, miles, events, or other measure of life units. MTBF is documented as technical and operational characteristics. Technical parameters reflect the technical reliability that the system/equipment must demonstrate. In determining these parameter values, all failures and resultant actions to restore the item will be considered (e.g., a broken tail light is a technical, but not operational characteristic). Operational parameters reflect operational RAM characteristics that the system must demonstrate. Only operational mission failures and the resultant tasks are included (e.g., engine failure will result in mission abort that is an operational and technical failure). The contractor shall obtain approval

CUI

from Government integrated product team (IPT) on formula(s) to derive MTBF and MTTR calculations not supplied by item manufactures. MTBF should be expressed in hours.

1.4.10.6 Modifying Government Furnished Data

The process of making changes to Government furnished source data in order to make it suitable to meet the requirements of the contract.

1.4.10.7 National Stock Number National Item Identification Number (NSN/NIIN)

A NIIN provides a unique identification of an item of supply within a specified FSC. The combination of the two identifiers (FSC and NIIN) constitutes the NSN. The nine digit NIIN is made up of a two-digit NATO Codification Bureau (NCB) code indicating the assigning country (e.g., the United States uses “00” and “01”) and the final seven digits are assigned sequentially and have no inherent significance. The NIIN relates to one and only one item of supply within the codifying country. It can consist of one or many “items of production” (i.e., a product of a specific manufacturer) having equivalent “fundamental characteristics”.

1.4.10.8 Original Equipment Manufacturer’s Part Number (OEM/P/N)

The actual Original Equipment Manufacturer’s part, model or drawing number used by the manufacturer to identify their item of supply.

1.4.10.9 Parts Availability Code (PAC)

A numeric code showing the manufacturer’s estimated time before the part is discontinued and unavailable as indicated below:

a. 1 - 6 months,

b. 7 - 12 months,

c. 1 - 2 years,

d. 2 - 5 years, and

e. greater than 5 years.

1.4.10.10 Provisioning List Item Sequence Number (PLISN)

An alpha numeric sequentially assigned value for each item contained in the system/equipment breakdown (EXAMPLE-A001-Cockpit, B001-Visual, C001-IOS, etc.). This alpha numeric format will allow for separate System Sorting. Once a PLISN NUMBER has been assigned to an item, that number may not be used again.

1.4.10.11 Provisioning Remarks

Narrative clarification of provided data or any information required for procurement of the item.

1.4.10.12 Quantity Per End Item (QPEI)

The quantity per end item of the system/end item as a model (“A” indentured) item. Exception:

If the item does not have a next higher assembly (NHA), the quantity per end item should be

CUI

blank. The total number of times the line item is used in the complete system/equipment. If the quantity is unknown or cannot be determined specify the quantity by “V” (variable) or as specified by the provisioning activity.

1.4.10.13 Replacing Government Furnished Data

The process of substituting source data present in the Government-furnished datasets with contractor-provided source data that meets or exceed the requirements of the contract.

1.4.10.14 Supplementing Government Furnished Data

The process of augmenting the Government-furnished datasets with contractor-provided source data in order to obtain source data that is needed to meet the requirements of the contract and is not present in the Government-furnished datasets.

1.4.10.15 Supporting Data

Reference to data that provides definitive information on the supportability, reliability, maintainability, availability of the item. For COTS items, an active hyperlink to manufactures’ data sheets may be provided.

1.4.10.16 Total Quantity Recommended (TQR)

A recommended quantity of items required to support a specific number of applications for a specific period of time. The applications may be to a weapon system, end item, component, or combinations thereof, which are contained in the applicable contract.

1.4.10.17 Type of Change Code (TOCC)

This block, which is blank on initial submissions of provisioning data, and shall be used as a type of change code to indicate deletions, modifications, typographical error, quantity changes (increase, decrease), and limited part applications as follows:

a. A - Added item.

b. D - Indicates a deleted item.

c. G - Deletion of a data element.

d. L - Item is replaced during production and support of the old part may be required for prior production quantities.

e. M - Indicates a modified item. Required to identify entries for those items changed as a result of administrative or engineering requirements (not for initial entry of NSN) before or during production.

f. P - Prime contractor’s reference number.

g. Cage Code.

h. Manufacturer’s reference number.

i. Item name.

j. Other date elements, as may be subsequently defined, wherein the hardware is not affected.

CUI

k. Q - Used to make quantity field changes.

l. T - Used to make a typographical error correction.

1.4.10.18 Unit of Issue (UI)

A code that indicates the UI quantity of an item. The UI quantity is the managing activity's established accounting unit upon which the smallest unit pack is based, or accountable records are maintained, and requirements are computed. For applicable codes see DLA Cataloging Data and Transaction Standards, Volume 10, Table 53.

1.4.10.19 Using Government Furnished Data

The process of utilizing Government furnished source data ‘as-is’ (i.e., as furnished by the Government) without modification.

1.4.11 Trainer Peculiar Equipment (TPE)

The following types of equipment are defined as TPE:

a. Trainer equipment which has not been classified by the Government as a Commercial

Item, Government-Furnished Equipment (GFE), NDI, or Contractor Acquired Operational Equipment (CAOE).

b. Commercial item, NDI, GFE, or CAOE, that

(1) needs other than Minor Modifications (see FAR 2.101) or modifications which are not of a type customarily available in the commercial marketplace to meet the requirements of the contract, or

(2) does not have sufficient existing product documentation for Government logistics support.

2. APPLICABLE DOCUMENTS

The following documents of the issue listed form a part of this SOW to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this SOW, the contents of this SOW take precedence. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained. The documents listed herein may be updated to the latest applicable revision under the SOW.

2.1 Government Documents

SPECIFICATIONS, STANDARDS, HANDBOOKS AND REGULATIONS

Naval Air Systems Command

PRF 230028 - Performance Specification for United States Marine Corps MCAT FY24 Modernization Program, dated 24 October 2023

PMA-205 CMP - PMA205 Configuration Management Plan for Naval Aviation Training Systems and Ranges, dated May 2023

PMA-205 CMP Addendum C-

10-1 USMC MCAT

- PMA205 Configuration Management (CM) Plan Addendum for the Marine Common Aircrew Trainer

(The above documents will be provided as Government-Furnished Information (GFI))

DoD Handbooks MIL-HDBK-217F, Notice 2 - Reliability Prediction of Electronic Equipment, dated

28 February 1995 MIL-HDBK-472, Notice 1 - Maintainability Prediction, dated 26 May 2020 ((Copies of these documents are available online at http://quicksearch.dla.mil, or from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094.)

Chief of Naval Operations (OPNAV) Instructions

OPNAVINST 11010.20J - Navy Facilities Projects (Above instructions are available at: https://www.secnav.navy.mil/doni/opnav.aspx/Directives/)

Code of Federal Regulations (CFR)

22 CFR, Parts 120 – 130 - Foreign Relations, Chapter I – Department of State, Subchapter M – International Traffic in Arms Regulations

29 CFR 1910.147 - The control of hazardous energy (lockout/tagout) (The above documents are available from the following sources:

Occupational Safety and Health Administration (OSHA) standards are downloadable from https://www.osha.gov/law-regs.html CFRs are downloadable from https://www.ecfr.gov/)

Defense Federal Acquisition Regulations Supplement (DFARS)

DFARS 252.204-7012 - Safeguarding Covered Defense Information and Cyber Incident Reporting

DFARS 252.211-7003 - Item Unique Identification and Valuation (January 2023)

DFARS 252.227-7015 - Technical Data-Commercial Items

DFARS 252.227-7017 - Identification and Assertion of Use, Release, or Disclosure Restrictions

DFARS 252.227-7030 - Technical Data-Withholding of Payment

DFARS 252.227-7037 - Validation of Restrictive Markings on Technical Data

DFARS 252.239-7018 - Supply Chain Risk (February 2019)

Department of the Army Manuals EM-385-1-1 - U.S. Army Corps of Engineers Safety and Health

Requirements Manual 2008 (Copy of this document is available online at http://www.publications.usace.army.mil/Portals/76/Publications/EngineerManuals/EM_385-1-1.pdf)

CUI

DoD Guide RIO Management Guide - Department of Defense Risk, Issue, and Opportunity

(RIO) Management Guide for Defense Acquisition Programs, September 2023

DoD Security and Cybersecurity Instructions, Manuals, Policy Memos, and Guidance Documents

CNSSD 505 - Committee on National Security Systems (CNSS) Directive - Supply Chain Risk Management, dated 26 July, 2017

CNSSI 1253 - Committee on National Security Systems (CNSS) Instruction - Security Categorization and Control Selection for National Security Systems, dated 27 March 2014

DoDI 5200.39 - Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E), dated 15 Oct 2018

DoDI 8510.01

DoDI 8520.02

Risk Management Framework (RMF) for DoD Systems, dated 19 July 2022

Public Key Infrastructure (PKI) and Public Key (PK) Enabling, dated 18 May 2023

DoD 8570.01-M - Information Assurance Workforce Improvement Program, Incorporating Change 4, dated 10 November

NIST SP 800-147B - BIOS Protection Guidelines for Servers, dated October 29, 2014

NIST SP 800-37,

Revision 2

- Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy, dated December, 2018

NIST SP 800-53,

Revision 5

- Security and Privacy Controls for Federal Information Systems and Organizations, dated September 2020

NIST 800-171,

Revision 2

- Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, dated February

(Copies of the above security documents are downloadable from https://csrc.nist.gov/presentations/2017/committee-on-national-security-systems-(cnss)-dire, https://www.cnss.gov/CNSS/issuances/instructions.cfm, https://www.esd.whs.mil/directives/issuances/dodi/, https://www.nist.gov/search?s=NIST%20SP%20800-147B&index=www-nist-gov-publications)

DoD Unified Facilities Criteria Program UFGS - United Facilities Guide Specifications UFC - Unified Facilities Criteria (The above documents are downloadable from http://www.wbdg.org/references/pa_dod.php)

CUI

Federal Acquisition Regulations (FAR)

FAR 2.101 - Definitions

FAR 52.204-9 - Personal Identity Verification of Contractor Personnel

FAR 52.222-54 - Employment Eligibility Verification (FAR Clauses are downloadable from https://www.acquisition.gov/browse/index/far)

Naval Air Systems Command (NAVAIR) Documents

NAVAIRINST 3905.1A - Test Reporting Policy For Air vehicles, Air Vehicle Weapons, and Air Vehicle Installed Systems Tests, dated January 17th, 2018

NAVAIRINST 3960.4C - Project Test Plan Policy for Testing Air Vehicles, Air Vehicle Weapons, and Air Vehicle Installed Systems, dated April 9th, 2013.

NAVAIRINST 4130.1F - NAVAIR Configuration Management Policy Manual, dated April 6, 2021

(NAVAIR Instructions are downloadable fromhttps://myteam.navair.navy.mil/km/71/Directives)

U.S. Code

Title 10, Section 2451 - 2456 - Defense Standardization Program

(U.S. Code is downloadable from http://uscode.house.gov/search/criteria.shtml)

2.2 Non-Government Documents

INDUSTRY STANDARDS

SAE International/Electronic Industries Alliance (EIA) SAE EIA-649C - Configuration Management Standard SAE EIA-649-1A - Configuration Management Requirements for Defense

Contracts (Copies of the above document are available from www.ansi.org)

American National Standards Institute (ANSI)/American Society for Quality (ASQ)/International Organization for Standardization (ISO)

ANSI/ASQ/ISO 9000-2015 - Quality Management Systems – Fundamentals and Vocabulary

ANSI/ASQ/ISO 9001-2015 - Quality Management Systems - Requirements

ANSI/ASQ/ISO 9004-2018 - Quality Management Systems – Guidelines for Performance Improvements

(Copy of the above document is available from www.iso.org)

CUI

3. REQUIREMENTS

3.1 General Requirements

a. Unless otherwise specified, requirements in this SOW shall be applicable to all MCAT devices. The contractor shall perform the work required by this contract in accordance with this SOW and PRF 230028.

3.1.1 MCAT MP Tech Refresh

The contractor shall

a. upgrade the computational subsystems to meet the cybersecurity compliance requirements in PRF 230028;

b. meet the Instructor Operator Station (IOS) upgrade requirements in PRF 230028;

c. upgrade the emergency procedure (EP) functionality/trainability IAW the requirements in

PRF 230028;

d. meet the interoperability requirements in PRF 230028;

e. meet the Video Support Computer (VSC) functionality requirements in PRF 230028;

f. upgrade the visual system (VS) to meet the visual performance and functional requirements in PRF 230028;

g. prepare the Synthetic Environment Database Design Document (SEDDD) IAW the

CDRL A008;

h. replace the image generator (IG) with a new IG that meets the performance and functional requirements in PRF 230028;

i. upgrade the audio/aural cue system to meet the requirements in PRF 230028;

j. plan, coordinate, and conduct flight model characteristics working group meetings IAW

3.2.1 and 3.2.1.6.1 to provide a forum for the IPT to discuss, review, influence, and evaluate updates to the ownship and wingman flight characteristics of all MCAT T/M/S aircraft IAW PRF 230028;

k. upgrade the MCAT system hardware to meet the requirements in PRF 230028;

l. address the electronic component overheating concerns IAW the requirements in PRF

230028;

m. inspect the MCAT enclosure roof and reseal all MCAT enclosure roof seams and all water leak paths IAW the requirements in PRF 230028.

n. provide spare parts IAW 3.2.7.3.3; and

o. provide Contractor Logistics Support (CLS) IAW 3.2.13.13.

3.1.2 MCAT DV 2H166A-2 Relocated from K-Bay to YUMA

b. The contractor shall

a. relocate MCAT DV 2H166A-2 and its appurtenant equipment (hereafter referred to as trainer or device) from its current location aboard Marine Corps Air Station (MCAS) Kaneohe Bay, HI to the new location aboard MCAS Yuma, AZ;

b. conduct a site survey at MCAS Yuma, AZ and MCAS Kaneohe Bay, HI IAW 3.2.22.1;

c. provide personnel, packing material, supplies, permits, transportation, and all other materials and resources necessary to inspect, inventory, safely disassemble, transport, reassemble, install, test, and restore the trainer to a Ready-for-Training (RFT) condition at the MCAS Yuma, AZ location;

CUI

d. provide the Government a detailed schedule illustrating planned start and completion dates for all of the steps required in the performance of the device relocation IAW 3.2.1.1;

e. meet the 2H166A-2 training device relocation (TDR) start and completion dates IAW section F of the contract;

f. dismantle, pack, and transport the trainer and all supporting equipment.

g. use enclosure shipping panels and support bars, stored with the trainer at Kaneohe Bay, when shipping the enclosure sections;

h. reinstall the trainer at the gaining site IAW the following, or as otherwise required;

replace the Environmental Control Units (ECU) with new units that provide adequate cooling, heating, and humidity control for the Enclosure and training system IAW requirements in PRF 230028;

obtain a crane service lift plan and Federal Aviation Association (FAA) Obstruction Evaluation (OE) authorization to extend crane within close proximity to airfield;

provide the FAA OE authorization to Government no later than (NLT) 30 days prior to planned crane operations at site;

ensure prior coordination of trainer shipping and trucking is conducted in a timely manner so as not to delay project schedule;

ensure all workmanship and materials used is in compliance with best commercial standards;

ensure all electrical work connecting with facility electrical power is performed IAW requirements in PRF 230028 and local/base regulations;

ensure assembly and installation of container and contents on site meets all local wind load and seismic regulations;

be responsible for physical security of all Government property during all relocation activities required by this SOW;

be responsible for the loss or damage of any trainer and equipment relocated under the provisions of this SOW;

ensure replaced parts, if any, are identical in form, fit and function to parts that were lost or damaged;

ensure all hazardous waste/hazardous materials is properly disposed of, all tools and extraneous hardware has been removed from the site, and the trainer is in a RFT state prior to conduct of the Integrated Logistics Support Verification (ILSV); and ensure the performance interval between the disassembly start date and the install complete date remains constant, exclusive of any storage time that may be required by the Government (Note: Planned disassembly start and install completion dates may shift due to construction time for modification (MOD) of trainer facilities, and Fleet training requirements.).

3.1.3 Provisioning Item Orders

a. order, receive, inspect, test, store, package, and deliver provisioned items selected at the

Provisioning Item Selection Conference (PISC); and

b. time procurement of hardware so that the government receives hardware within OEM warranty period.

CUI

3.2 Detailed Tasks

3.2.1 Program Management

The contractor shall

a. organize, coordinate, and control the program activities to ensure compliance with the contract requirements and the timely delivery of the required product and services;

b. provide 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 specification PRF 230028;

c. collect and analyze the progress of the work performed and costs incurred under the contract; and

d. prepare the Contractor’s Progress, Status, and Management Report (CPSMR) IAW the Contract Data Requirements List (CDRL) (B001).

3.2.1.1 Work Planning and Scheduling

The contractor shall

a. develop, implement, control, and maintain an Integrated Master Schedule (IMS) which presents the contractor’s and subcontractors’ plans and schedules to meet the requirements of the contract;

b. develop a tiered scheduling system showing the program milestones, prerequisite events, critical paths, conferences, reviews, data submittals, and deliveries;

c. integrate all required deliverables and subcontractor schedules into the contractor’s IMS;

d. construct the IMS to ensure that the program milestones are on track and to ensure that deliveries meet the requirements of the contract;

e. ensure contractor schedule information delivered to the Government or presented at program reviews originate from the IMS;

f. perform analyses of the IMS tasks, compare the IMS tasks to the schedule baseline, report potential and existing problem areas, and recommend corrective actions to eliminate or reduce schedule impact;

g. revise the IMS to reflect requirement changes that occur during the course of performance;

h. use the IMS as a day-to-day execution tool to assess progress in meeting program requirements; and

i. prepare the IMS and report as part of the Integrated Program Management Data and Analysis Report (IPMDAR) IAW the CDRL (B002).

3.2.1.2 Program Planning

a. identify objectives and constraints of the contract;

b. establish a work breakdown structure based on the system architecture;

c. define achievement criteria for the life cycle stages delivery dates and dependencies on external resources; and

d. define roles, responsibilities, accountabilities and authorities.

CUI

3.2.1.3 Life Cycle Mode Management

The contractor shall define, maintain, and assure availability of policies, life cycle processes, life cycle models, and procedures.

3.2.1.4 Infrastructure Management

The contractor shall provide the infrastructure and services to support organization and program objectives throughout the life cycle of the contract.

3.2.1.5 Program Assessment and Control

The contractor shall track the status of the program, technical, and process performance to ensure the performance is in accordance with the plans and schedules that satisfy the technical objectives.

3.2.1.6 Subcontractor Management and Reporting

The contractor shall

a. ensure that the award of subcontracts align with the program schedule;

b. monitor the subcontractor's staffing plans and the execution of those staffing plans to the required levels with the required skills;

c. reserve the right for the contractor and Government to send personnel into the subcontractor’s facilities to monitor and evaluate subcontracted activities; and

d. ensure that the subcontractor’s efforts are accomplished per the contractual requirements, including the requirements for technical, quality, configuration management, and risk processes.

3.2.1.6.1 Integrated Product Teams (IPTs)

The contractor shall

a. define, implement, and maintain an IPT structure for the duration of the contract;

b. define the composition, structure, membership, roles, and responsibilities of the IPT with

Government input;

c. provide a co-chair at the IPT meeting conducted jointly between the contractor and the

Government; and

d. participate in IPT meetings to occur biweekly for the duration of the contract.

3.2.1.7 Risk Management

a. conduct risk management reviews to allow program systematic control of the uncertainty in the program’s ability to meet cost, schedule, and performance requirements;

b. provide the Government visibility into the contractor’s tools, assessment, mitigation, and control techniques;

c. perform risk management activities and tasks to identify, analyze, treat and monitor the risk continually;

d. participate in the Government Risk Working Group (RWG) established for the program;

CUI

e. present and discuss the status of risks and issue items, risk and issue mitigation plans, and risk and issue mitigation steps during all scheduled conferences and reviews IAW risk and issue management in RIO Management Guide;

f. present and discuss watch items during all scheduled conferences and reviews; and

g. report risk information, data, and analysis in the IPMDAR IAW the CDRL (B002).

3.2.1.8 Quality Management

a. have a quality management process to ensure that the products and implementations of the life cycle meet contractor quality objectives and Government requirements; and

b. define, document, manage and apply a quality management process IAW

ANSI/ASQ/ISO 9001-2015 (or equivalent Quality Management System (QMS)).

(1) The contractor may use ANSI/ASQ/ISO 9000-2015 and ANSI/ASQ/ISO 9004-2018 for guidance.

3.2.1.8.1 Control of Government Furnished Equipment (GFE) and Government Furnished Information (GFI)

The contractor shall perform the following tasks to control GFE and GFI as part of the quality management process:

a. examine upon receipt to detect damage,

b. provide storage that precludes deterioration,

c. examine prior to installation to detect damage,

d. identify and protect from improper use or disposition, and

e. verify and audit quantities.

3.2.1.8.2 Use of Contractor’s Inspection Equipment

a. make measuring and testing devices available for use by the Government to determine conformance with contract requirements;

b. provide the personnel to operate such devices and to verify calibration, accuracy, and condition; and

c. deliver to the Government measuring and testing devices procured with Government funding.

3.2.1.9 Configuration Management (CM)

The contractor shall

a. define, document, manage, and apply a CM process IAW SAE EIA-649C, NAVAIRINST 4130.1F, PMA-205 CMP, and the PMA-205 CMP Addendum C-10-1

USMC MCAT.

b. provide the Government with accessibility and visibility to the contractor’s CM tools, assessment, and control techniques; and

CUI

c. place Government-furnished software (GFS), GFE, GFI, NDI, commercial item software, and the items associated documentation under CM upon receipt.

3.2.1.9.1 Configuration Control

The contractor shall control the hardware, software, and documentation product baseline configuration and changes to the product baseline.

3.2.1.9.2 Change Management

The contractor shall

a. control the established product baseline, including any potential changes, using a contractor change process and engineering release process IAW SAE EIA-649-1A;

b. submit proposed changes that impact the established product baseline to the Government for approval;

c. submit an Engineering Change Proposal (ECP) IAW the CDRL (A006); and

d. submit a Request for Variance (RFV) IAW the CDRL (A007).

3.2.1.10 Configuration Identification Process (CIP)

The contractor shall

a. use a documented process for configuration identification,

b. uniquely identify each configuration item (CI),

c. determine the types of configuration documentation required by each CI,

d. establish a configuration identification structure and hierarchy that identifies at least the following:

(1) part number – serial number and location, and

e. prepare the Baseline Description Document (BDD) IAW the CDRL (D001).

3.2.1.10.1 Configuration Status Accounting

The contractor shall define, manage, and apply a process to accomplish configuration status accounting.

3.2.1.10.2 Configuration Audits

The contractor shall conduct functional configuration audits (FCAs) and an Integrated Logistics Support Verification (ILSV).

3.2.1.11 Information Management

a. define items and the strategy for information management;

b. define the content, formats and structure of information items;

c. designate authorities and responsibilities for information management; and

d. maintain information items, their storage records, and record the status of information.

CUI

3.2.1.12 Data Management

The contractor shall

a. develop, manage, and implement a data management process to ensure the delivery of contractually required data;

b. establish and implement procedures to manage the configuration of contractually required data during the life of the contract;

c. ensure that the development and storage media is compatible with the Government’s requirements for the format and media type of the deliverables; and

d. utilize a data management system that is accessible to the Government.

3.2.1.13 Transmission of Controlled Unclassified Information (CUI) via E-mail

a. use approved encryption to appropriate levels for safeguard of the electronic transmission of CUI via e-mail; and ensure that when transmitting CUI over non-secure e-mail (e.g. not connected to the Navy Marine Corps Intranet (NMCI) through Broadband Unclassified Remote Access System/Virtual Private network), those transmissions are encrypted using DoD Public Key Infrastructure (PKI), or an approved DoD External Certificate Authority, IAW DoDI 8520.02

3.2.2 Security

a. abide by the applied security requirements specified herein and apply them to subcontractors;

b. comply with applicable on-site security regulations related to government installation and facility access; and

c. maintain security clearance eligibility commensurate for contractor personnel with the level of classification of the work performed as annotated in the contract's DD-254, Contract Security Classification Specification Form.

3.2.2.1 Classified Processing and Access to Classified Systems

The contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled in accordance with the appropriate designation (Controlled Unclassified Information (CUI), legacy For Official Use Only (FOUO), Covered Defense Information). Distribution is authorized to the Requiring Office's Organization and supported activity only. Other requests for deliverables under this contract shall be referred to the Technical Point of Contact (TPOC) of this contract for approval. CUI including Legacy FOUO and Covered Defense Information (meeting the definition of DFARS 252.204-7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoD Instruction 5200.48, CUI available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF. Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24 (Distribution Statements on

CUI

Technical Documents), and have this statement displayed per DoDI 5230.24, Enclosure 3. Any controlled unclassified information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. government authority. Proposed public releases shall be submitted in accordance with the DD-254 attached to this contract for approval prior to release through PEO (T), Public Affairs Office, 47123 Buse Road, RADM William A.

Moffett Building, Patuxent River, MD 20670-1547 and include the completed NAVAIR FORM

5720.10. Technical Documents shall have this statement displayed per DoDI 5230.24, Enclosure 3.

3.2.2.2 Operation Security (OPSEC)

The contractor shall

a. develop, implement, and maintain an OPSEC program, which may include Information

Assurance and Communications Security (COMSEC), IAW National Security Decision Directive (NSDD) 298 to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the contractor and any subcontractor during performance of the contract;

b. be responsible for the subcontractor implementation of OPSEC requirements;

c. include in the OPSEC program the following:

(1) assignment of responsibility for OPSEC direction and implementation;

(2) issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures;

(3) establishment of OPSEC education and awareness training to include Basic OPSEC training, produced by the Interagency OPSEC Support Staff (IOSS), IAW OPSE1301 OPSEC Fundamentals;

(4) provisions for management, annual review, and evaluation of OPSEC programs; and

(5) flow down of OPSEC requirements to subcontractors when applicable.

d. comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts while performing aboard NAVAIR or NAVAIR sites;

e. include OPSEC as part of its ongoing security awareness program and take all required agency training;

f. be responsive to the supporting OPSEC manager on a non-interference basis;

g. protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the RO and contractor in support of the mission;

h. apply the Risk Management Framework guidelines to federal information systems to include conducting the activities of security categorization, security control selection and implementation, security control assessment, information system authorization, and security control monitoring as specified in NIST SP 800-37, Revision 2; and

i. prepare the OPSEC Plan IAW the CDRL (B006).

3.2.2.3 Unclassified Contractor-Owned Network Security – Safeguarding of CUI

The contractor and subcontractor(s) (when applicable) shall

CUI

a. safeguard against unauthorized access and disclosure of CUI resident on or transiting through contractor unclassified information systems;

b. take means (defense-in-depth measures) necessary to protect the confidentiality, integrity, and availability of Government CUI;

c. manage and maintain contractor-owned unclassified information technology (IT) network assets used to process U.S. Government CUI (sensitive information) IAW the following:

(1) DFARS 252.204-7012;

(2) security requirements in NIST 800-171, Revision 2; and notify the DoD Chief

Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST 800-171, Revision 2.

not implemented at the time of contract award; or

(3) Implement an alternative but equally effective security measures used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection accepted in writing by an authorized representative of the DoD CIO; and

d. apply other information systems security measures when the contractor reasonably determines that information systems security measures, in addition to those identified in paragraph (b)(1) of DFARS 252.204-7012, are required to provide adequate security in a dynamic environment based on an assessed risk or vulnerability.

3.2.2.4 Cyber Incident and Compromise Reporting

a. report to the DoD cyber incidents that affect CUI resident on or transiting contractor unclassified information systems set forth IAW DFARS 252.204-7012; and

b. provide the report to the NAWCTSD Contracting Officer, NAWCTSD Security

Manager, and the NAWCTSD Information Systems Security Manager (ISSM).

3.2.2.5 Access to DoD Installations, Government Information, and IT Systems- Personal Security Background Checks and Defense Biometric Identification System

The contractor shall

a. use the Common Access Card (CAC) as the principal identity credential for…