Att 1 SOW 210044 Rev A H-1.pdf

CUI

SOW 210044A

18 July 2022

STATEMENT OF WORK

FOR

UNITED STATES MARINE CORPS

H-1 TRAINING DEVICES

TRAINING DEVICE MODERNIZATION PROGRAM (TDMP)

Prepared by

NAVAL AIR WARFARE CENTER

TRAINING SYSTEMS DIVISION

For

DEPARTMENT OF THE NAVY,

PROGRAM EXECUTIVE OFFICE (PEO)

AVIATION COMMON SYSTEMS AND COMMERICAL SERVICES (CS)/PMA-205

NAVAL AVIATION TRAINING SYSTEMS AND RANGES

X X Dan Shannon Susan Marie Carr PMA205 USMC Level 1 IPTL, COMNAVAIRSYCOM Program Manager, H-1 Training Systems

DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense (DoD) and US DoD Contractors only; (Administrative and Operational Use Only) (10 February 2022). Other requests shall be referred to Department of Navy, PEO (CS)/PMA-205, 47123 Buse Road, RADM William A. Moffett Building, Patuxent River, Maryland, 20670-1547

Controlled by: Department of Navy Controlled by: NAWCTSD CUI Category: CTI, CONTRACT Distribution/Dissemination Control: FEDCON

POC: Steve Coln, stephen.c.coln.civ@us.navy.mil

CUI SOW 210044A

ii

Revision History

Revision Affected Paragraph(s)

Changes

A

Title Modified title to accurately reflect program name.

1. Added Lot 7 and Lot 8 definitions to the devices listed in the scope.

2.1 Removed the program management risk acceptance letter.

2.1 Added TM-NAWCAD-AB21300-H1-2021-01-21.0 to the

document list

2.1 Added CDS52866 Control Loading AH-1Z Aircraft

Measurement Report

3.1.2.1 Added full name of FOUO.

3.1.3.1 Added full name of USMC.

3.2.1.7.6.1 Added tasking to update the UH-1Y flight control

mechanical characteristics data.

3.2.1.7.6.2 Added tasking to update the AH-1Z flight control

mechanical characteristics data.

3.2.1.7.11 Added tasking to replace cockpit panels, faceplates for the avionics systems, and other worn cockpit hardware.

3.2.1.14 c. Added ‘MCAS’ to the location name.

3.2.1.16.1 Added device numbers in the requirement for clarity.

3.2.2.12.g Removed the program management risk acceptance letter.

3.2.3.3.2 a. Clarified PDR requirement to include all devices under one

PDR.

3.2.3.3.2.2 Changed “CDR” to “PDR”

3.2.3.3.3 a. Identified 2 CDRs required, 1 for Lot 7 devices and 1 for

Lot 8 devices.

3.2.3.3.3.1 Changed from “…that the CDR entry criteria…’ to “…that the entry criteria…”

3.2.3.8.1 Corrected formatting of list to match the document.

3.2.8.5 Removed “Government furnishment of baseline test

procedures” and “The contractor shall prepare the TP Visual System (TPVS) IAW the CDRL” iii

CUI

Table of Contents Section Title Page

1. SCOPE

1.1 Definitions

1.1.1 Commercial Item

1.1.2 Initial Support Kit (ISK)

1.1.3 Non-Developmental Item (NDI)

1.1.4 Trainer-Peculiar Equipment (TPE)

1.1.5 Electromagnetic Environment (EME)

1.1.6 Electromagnetic Compatibility (EMC)

1.1.7 Electromagnetic Interference (EMI)

1.1.8 Electrostatic Discharge (ESD)

1.1.9 Lightning Effects

1.1.10 Electrical Bonding

1.1.11 Modifications

1.1.12 Optical Surfaces

2. APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 Non-Government Documents

3. REQUIREMENTS

3.1 General

3.1.1 Program Management

3.1.1.1 Program Planning

3.1.1.1.1 Life Cycle Model Management

3.1.1.1.2 Infrastructure Management

3.1.1.1.3 Program Assessment and Control

3.1.1.1.4 Program Decision Management

3.1.1.1.5 Work Planning and Scheduling

3.1.1.3 Integrated Product Teams (IPTs)

3.1.1.4 Risk Management

3.1.1.5 Quality Management

3.1.1.5.1 Control of Government-Furnished Equipment (GFE)

3.1.1.5.2 GFE Tracking and Reporting Requirements

3.1.1.5.3 Use of Contractor’s Inspection Equipment

3.1.1.6 Configuration Management (CM)

3.1.1.6.1 Change Management

3.1.1.6.2 Configuration Status Accounting

3.1.1.6.3 Configuration Audits

3.1.1.7 Information Management

3.1.1.7.1 Online Information Exchange

3.1.1.7.2 Data Management

3.1.1.8 Program Measurement

3.1.1.9 Cost and Software Data Reporting (CSDR)

3.1.1.9.1 Contractor Cost Data Reporting (CCDR)

3.1.2 Security

3.1.2.1 Classified Processing and Access to Classified Systems

Table of Contents Section Title Page iv

CUI

3.1.2.2 Operations Security (OPSEC)

3.1.2.3 Unclassified Contractor-Owned Network Security - Safeguarding of Unclassified Controlled Technical Information

3.1.2.4 Cyber Incident and Compromise Reporting

3.1.2.5 Access to DoD Installations, Government Information, and IT

Systems - Personnel Security Background Checks

3.1.2.6 Personnel Security – Background Checks

3.1.2.7 International Traffic and Arms Regulation

3.1.2.8 Personnel Security – Reporting of Adverse or Derogatory

Information related to Contractors

3.1.2.9 Government-Issued Personal Identification Credentials

3.1.2.10 Contractor “Out-processing” Policy

3.1.2.11 Supply Chain Risk Management (SCRM) For National Security

Systems

3.1.2.12 Protection of Critical Program Information (CPI)

3.1.2.13 Transmission of CUI via e-mail

3.1.2.14 Transmission of Controlled Unclassified Information (CUI) via

DoD SAFE

3.1.3 Cybersecurity

3.1.3.1 Initial Cybersecurity RMF Meeting

3.1.3.2 Cybersecurity Certification and Accreditation Support

3.1.3.3 Cybersecurity Compliance

3.1.3.4 Cybersecurity Vulnerability Management Program (CVMP)

3.1.3.5 Cybersecurity Training

3.1.3.6 Contractor Cybersecurity Training and Certification

3.1.4 Telephone/Internet Access

3.2 Detailed Tasks

3.2.1 Trainer Modification Tasks

3.2.1.1 Pre-existing Training System Deficiencies

3.2.1.2 Computational Systems

3.2.1.2.1 Operating System Upgrades

3.2.1.2.2 Computational System Upgrade and Replacement

3.2.1.2.3 Input/Output (I/O) Subsystems Modification

3.2.1.2.4 Keyboard Video Mouse (KVM) Upgrade

3.2.1.2.5 DiGuy Removal

3.2.1.3 Visual System

3.2.1.3.1 Visual System Tasks Applicable to All Devices

3.2.1.3.1.1 Visual Display System (VDS) Display Devices, Components, and

Interfaces Replacement and Modifications

3.2.1.3.1.2 Image Generator (IG) Replacement and Associated Hardware and

Software Modifications

3.2.1.3.1.3 Alignment and Test Patterns (A&TPs) and Synthetic Environment

Visual and Sensor Databases (DBs) and Moving Models (MMs) Content and Associated Software Modifications

3.2.1.3.1.3.1 Deliverable Runtime Visual and Sensor DBs, MMs, and A&TPs

Table of Contents Section Title Page v

CUI

3.2.1.3.1.3.1.1 Visual and Sensor DBs, MMs, and A&TPs Purposely Published for this TDM from Government-Furnished and Contractor- Provided Source Data

3.2.1.3.1.3.1.2 Visual and Sensor DBs, MMs, and A&TPs from Existing, Contractor-Provided Runtime Products

3.2.1.3.1.3.2 Deliverable Visual and Sensor DBs, MMs, and A&TPs Source Data

3.2.1.3.1.3.3 Synthetic Environment Database Design Document (SEDDD)

3.2.1.3.2 Visual System Tasks Applicable to Specific Devices

3.2.1.3.2.1 Display Device Surface Cleaning

3.2.1.3.2.2 2F196-1 Collimating Mirror Evaluation

3.2.1.3.2.3 AH-1Z FTD (Device 2F227-2) display screen gain coating refurbishment

3.2.1.3.2.4 Display system testing and maintenance support devices and tools

3.2.1.3.2.4.1 Display system maintenance-support hoisting devices

3.2.1.4 Link 16

3.2.1.4.1 Link 16 Communication System Hardware

3.2.1.4.2 Link 16 Communcation System Software

3.2.1.5 Daily Operational Readiness Test (DORT)

3.2.1.6 Instructor–Operator Station (IOS)

3.2.1.6.1 IOS Software

3.2.1.6.2 IOS Monitor Replacement

3.2.1.7 Cockpit and Flight Controls

3.2.1.7.1 Cockpit Electromagnetic Mapping

3.2.1.7.2 Multi-Functional Display (MFD)

3.2.1.7.3 Cockpit Monitoring System (CMS)

3.2.1.7.3.1 CMS Helmet Mounted Sight Display (HMSD) symbology

3.2.1.7.4 Aero Models

3.2.1.7.4.1 COPTER Government Purpose Rights (GPR) Aero Model

3.2.1.7.4.2 Manned Flight Simulator (MFS) Aero Model

3.2.1.7.5 Throttles

3.2.1.7.5.1 Trainers with OEM aircraft collective/throttle inceptors

3.2.1.7.5.2 Trainers with Non-OEM aircraft collective/throttle inceptors

3.2.1.7.6 Control Loading System (CLS) Upgrade and Refurbishment

3.2.1.7.6.1 UH-1Y flight control criteria data update

3.2.1.7.6.2 AH-1Z flight control criteria data update

3.2.1.7.7 Secondary Motion System (six DOF Cockpit Shaker)

3.2.1.7.7.1 Secondary Motion Engineering Analysis Study

3.2.1.7.7.2 Secondary Motion Refurbishment

3.2.1.7.8 Cockpit Jump Seat

3.2.1.7.9 Safety Rails

3.2.1.7.10 2F215-1 Motion System

3.2.1.7.11 Cockpit hardware

3.2.1.7.12 UH-1Y windshield

3.2.1.8 External Lighting Control Panels

Table of Contents Section Title Page vi

CUI

3.2.1.9 Simulated Winds

3.2.1.10 Automated Test Guide (ATG) Modification

3.2.1.11 External Load Aerodynamics

3.2.1.12 USMC Tactical Environment Network (TEn) Integration

3.2.1.12.1 TEn Projector

3.2.1.13 Use of Government Furnished ASTi Models

3.2.1.14 Trainer Containerization and Relocation

3.2.1.14.1 Container Design

3.2.1.14.2 Grounding System

3.2.1.15 Technology Refresh Mission Computer (TRMC)

3.2.1.16 Aviation Distributed Virtual Training Environment (ADVTE)

Connectivity

3.2.1.16.1 2F227-1 and 2F196B-3 ADVTE connectivity

3.2.2 Systems Engineering Processes

3.2.2.1 System Requirements Definition

3.2.2.2 System Requirements Analysis

3.2.2.3 Traceability

3.2.2.4 System Architectural Design

3.2.2.5 Software Requirements Analysis

3.2.2.6 Software Architectural Design

3.2.2.7 Software Product Design

3.2.2.8 System Integration

3.2.2.9 System Qualification Testing

3.2.2.10 Device Transition

3.2.2.10.1 Cold Start Process

3.2.2.10.1.1 Software Product Execution

3.2.2.10.1.2 Media and Storage Devices

3.2.2.10.1.3 Software License(s)

3.2.2.10.1.4 Software Media Marking

3.2.2.11 System Validation

3.2.2.12 Electromagnetic Environmental Effects (E3) Engineering

3.2.2.13 Reliability and Maintainability (R&M) Engineering

3.2.2.13.1 Failure Reporting, Analysis and Corrective Action System

(FRACAS)

3.2.2.13.2 R&M Predictions

3.2.2.14 Human Factors Engineering (HFE)

3.2.3 Conferences and Reviews

3.2.3.1 Post Award Conference (PAC)

3.2.3.1.1 Logistics Guidance Conference (LGC)

3.2.3.1.2 Technical Documentation Orientation Conference (TDOC)

3.2.3.1.3 PAC Entry Criteria

3.2.3.1.4 PAC Completion Criteria

3.2.3.2 Technical Interchange Meetings (TIMs)

3.2.3.3 Systems Engineering Technical Reviews (SETR)

Table of Contents Section Title Page vii

CUI

3.2.3.3.1 System Requirements Review-II/System Functional Review

(SRRII/SFR)

3.2.3.3.1.1 SRR-II/SFR Entry Criteria

3.2.3.3.1.2 SRR-II/SFR Completion Criteria

3.2.3.3.2 Preliminary Design Review (PDR)

3.2.3.3.2.1 PDR Entry Criteria

3.2.3.3.2.2 PDR Completion Criteria

3.2.3.3.3 Critical Design Review (CDR)

3.2.3.3.3.1 CDR Entry Criteria

3.2.3.3.3.2 CDR Completion Criteria

3.2.3.3.4 TRR Conferences

3.2.3.4 Program Management IPT Meetings

3.2.3.5 In-Process Reviews

3.2.3.6 Working Groups (WGs)

3.2.3.6.1 Database Working Groups (DBWGs)

3.2.3.6.2 Wind, Turbulence and Reduced Visibility Environment (RVE)

Working Groups (WTRVEWGs)

3.2.3.7 Training System Sparing Product Data (TSSPD)

3.2.3.8 Provisioning Item Selection Conference (PISC)

3.2.3.8.1 PISC Entry Criteria

3.2.3.8.2 PISC Completion Criteria

3.2.3.9 Technical Documentation IPR

3.2.3.10 Technical Documentation (TD) In-Process Reviews (TD IPR)

3.2.3.11 Integrated Logistics Support Verification (ILSV) Conference

3.2.4 Commercial and Non-Developmental Items (CaNDI)

3.2.4.1 Provisioned Items

3.2.5 Parts Standardization

3.2.5.1 Parts Management

3.2.5.1.1 Exempt Hardware

3.2.6 System Safety Tasks

3.2.6.1 Safety Assessment (SA)

3.2.7 Product Assurance Audits and Inspections

3.2.8 Test and Evaluation (T&E)

3.2.8.1 Responsibility for Tests

3.2.8.2 Test Authority

3.2.8.3 T&E Program Planning

3.2.8.4 Test Resources and Facilities

3.2.8.5 Test Methods

3.2.8.6 Test Criteria

3.2.8.7 Tolerance Data

3.2.8.8 Alignment

3.2.8.9 Testing Interruptions due to Safety Concerns

3.2.8.10 Test Suspension

3.2.8.11 Test Log

3.2.8.12 Changes During Testing

Table of Contents Section Title Page viii

CUI

3.2.8.12.1 Software Changes During Government Testing

3.2.8.13 Changes After Testing

3.2.8.14 T&E Technical Issue Report System

3.2.8.14.1 System Trouble Report (STR)

3.2.8.14.2 Discrepancy Review Board (DRB)

3.2.8.14.2.1 System Trouble Report Adjudication

3.2.8.14.3 Test Reporting

3.2.8.15 T&E Program Components

3.2.8.15.1 Baseline Configuration Audit (BCA)

3.2.8.15.2 On-site Pre-modification Inspection

3.2.8.15.3 DT-C1 Contractor Preliminary Inspection (CPI)

3.2.8.15.4 Test Readiness Review

3.2.8.15.4.1 TRR Entry Criteria

3.2.8.15.4.2 TRR Completion Criteria

3.2.8.15.5 Conformance Inspections

3.2.8.15.5.1 Functional Configuration Audit

3.2.8.15.5.1.1 IT-C1 (Integrated Final Inspection)

3.2.8.15.5.1.1.1 IT-C1 (IFI) Completion Criteria

3.2.8.15.5.2 Physical Configuration Audit (PCA)

3.2.8.15.5.2.1 Final PCA (FPCA)

3.2.8.15.5.2.1.1 FPCA Entry/Completion Criteria

3.2.9 Integrated Logistics Support (ILS) Program

3.2.9.1 Maintenance Planning (MP)

3.2.9.2 Maintenance Concept

3.2.9.3 Maintenance Concept Skill Requirements

3.2.9.4 Training System Maintenance and Provisioning Factors

3.2.9.5 Inventory Management

3.2.9.6 Technical Documentation (TD) and Technical Manuals (TMs)

3.2.9.6.1 Validation of TD and TMs

3.2.9.6.2 Verification of TMs

3.2.9.7 Instructor-Operator Training

3.2.9.8 Maintenance Training (Device Maintainer Training)

3.2.9.9 Original Equipment Manufacture Training (OEM)

3.2.9.10 Initial Operational Capability (IOC)

3.2.9.10.1 On-Site IOC

3.2.9.10.2 Contractor Personnel Responsibilities

3.2.9.10.3 Replenishment

3.2.9.10.4 Depot Repair of Items

3.2.9.10.5 On-site Reporting

3.2.9.11 Material Support

3.2.9.11.1 Logistics Product Data (LPD)

3.2.9.11.1.1 Engineering Data for Provisioning

3.2.9.12 Initial Support Kit (ISK)

3.2.9.12.1 Buy Through the Prime

Table of Contents Section Title Page ix

CUI

3.2.9.12.2 Failed Spare Items

3.2.9.13 Obsolescence Management/Diminishing Manufacturing Sources

Material Shortages (DMSMS)

3.2.9.13.1 Obsolescence Management Planning

3.2.9.13.2 Bill of Materials (BOM) for Logisitics and Supply Chain Risk

Management

3.2.10 Facility Requirements

3.2.10.1 Site Survey

3.2.10.2 Facilities Modification

3.2.10.3 Grounding

3.2.10.4 Product Installation

3.2.10.5 Removal/Disposal of Excess Equipment and Hazardous Material

3.2.10.6 Facility Repairs

3.2.10.7 Disposal of Debris

3.2.10.8 Product Installation Support

3.2.10.9 Safety

3.2.11 IUID Assignment

3.2.12 Relocation of Training Devices 2F196B-3, 2F227-1 located at

Kaneohe Bay, HI

3.2.12.1 Trainer Relocation Planning

3.2.12.2 Facility/Containerized Analysis

3.2.12.3 Trainer Relocation Test and Evaluation (T&E) Program

Components

3.2.12.3.1 Pre-Move Inspection/Test

3.2.12.3.2 Post-Move Inspection/Test

3.2.12.3.3 Contractor Preliminary Inspection (CPI)

3.2.12.4 Technical Documentation and Drawing Updates

3.2.12.5 Electrical

3.2.12.6 Storage

3.2.12.7 Facility Clean Up

3.2.12.8 Hazardous Materials/Wastes

3.2.12.9 Disassembly, Packaging and Relocation

3.2.12.9.1 Trainer Disassembly

3.2.12.9.2 Packaging

3.2.12.9.3 Shipping

3.2.12.19 Device 2F196B-3 and 2F227-1 Trainers Re-Assembly, Modification and Installation

3.2.12.20 Installation

3.2.12.21 Supplies

3.2.12.21.1 Cabling, Tubes, and Hoses

3.2.12.21.2 Cable, Tube, and Hose marking

3.2.12.21.3 Shielding and Grounding

CUI

Statement of Work For

The United States Marine Corps Training Devices AH-1Z and UH-1Y

Training Device Modernization (TDM)

1. SCOPE

The purpose of the TDM is to increase training systems supportability, reduce total life cycle support costs and obsolescence, and enhance flight crew training. This statement of work (SOW) establishes the contractor tasks to upgrade, modify, design, test, deliver, and produce H-1 Flight Training Devices (FTDs) and Full Flight Simulator (FFS) for

a. the Lot 7 devices, defined as

(1) 2F196-1 UH-1Y FTD, Marine Corp Air Station (MCAS) New River, NC;

(2) 2F197B-2 AH-1Z FTD, MCAS New River, NC;

(3) 2F226-1 UH-1Y FTD, MCAS New River, NC;

(4) 2F227-2 AH-1Z FTD, MCAS New River, NC;

(5) 2F196B-3 UH-1Y FTD, MCAS Kanoehe Bay, HI;

(6) 2F227-1 AH-1Z FTD, MCAS Kanoehe Bay, HI; and

(7) 2F226-2 UH-1Y FTD, MCAS Belle Chasse LA;

b. the Lot 8, defined as

(1) 2F227-4 AH-1Z FTD, MCAS Belle Chasse, LA;

(2) 2F196B-4 UH-1Y FTD, MCAS McGuire, NJ;

(3) 2F227-3 AH-1Z FTD, MCAS McGuire, NJ;

(4) 2F196B-2 UH-1Y FTD, MCAS Camp Pendleton, CA;

(5) 2F197-1 AH-1Z FTD, MCAS Camp Pendleton, CA;

(6) 2F206-1 UH-1Y FTD, MCAS Camp Pendleton, CA;

(7) 2F215-1 AH-1Z FFS, MCAS Camp Pendleton, CA;

(8) 2F226-3 UH-1Y FTD, MCAS Futenma, JP; and

(9) 2F227-5 AH-1Z FTD, MCAS Futenma, JP.

1.1 Definitions

The following definitions apply to this SOW.

1.1.1 Commercial Item

Commercial Item is defined in the Federal Acquisition Regulations (FAR), Part 2.101.

1.1.2 Initial Support Kit (ISK)

The ISK includes

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

b. 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 the 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.

1.1.3 Non-Developmental Item (NDI)

NDI is defined in the FAR, Part 2.101.

1.1.4 Trainer-Peculiar Equipment ()

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, Part 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 the Government logistic support.

1.1.5 Electromagnetic Environment (EME)

Any electromagnetic disturbance, induced intentionally or unintentionally, that interrupts, obstructs, or otherwise degrades or limits the effective performance of electronics and electrical equipment.

1.1.6 Electromagnetic Compatibility (EMC)

The ability of all equipment and systems to co-exist and operate in their intended operational environments without causing or suffering unintentional performance degradations or harmful reactions as a result of electromagnetic interference.

1.1.7 Electromagnetic Interference (EMI)

Any electrical or electromagnetic phenomenon, either natural or synthetic, either radiated or conducted, which results in unintentional and undesirable responses from, or performance-degradation or malfunction of, electronic equipment.

1.1.8 Electrostatic Discharge (ESD)

Static electricity is an electrical charge caused by an imbalance of electrons on the surface of a material. This imbalance of electrons produces an electric field that can be measured and that can influence other objects at a distance. ESD is the transfer of electric charge between bodies at different electrical-potentials.

1.1.9 Lightning Effects

Lightning is hazardous to systems. Lightning effects can be direct (physical) or indirect (electromagnetic). Direct effects such as burning and eroding, blasting, and structural damage are visible. Indirect effects result from the interaction of the EM-fields with subsystems and equipment within the system.

1.1.10 Electrical Bonding

Electrical bonding is the establishment of a low-impedance path between two conductive surfaces. This path may be between two points on a system ground-plane or between ground-references and a component, circuit or structural element.

1.1.11 Modifications

The term “modification” refers to changes made to update and upgrade training device hardware and software. Although the terms “modification”, “update”, and “upgrade” are sometimes used interchangeably, at other times the latter two are used specifically to differentiate between obsolescence- and performance-driven modifications. The context in which the terms are used conveys the intent.

1.1.12 Optical Surfaces

Optical surfaces are the display device reflective and transmissive surfaces in the optical path, including but not limited to collimating mirrors, chin and side window fold mirrors, back projection screens, front and rear projection screens.

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 a conflict between 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.

2.1 Government Documents

SPECIFICATIONS:

Naval Air Warfare Center Training Systems Division (NAWCTSD)

PRF 200037A - Performance Specification For United States Marine Corps H-1 Training Devices Training Device Modernization

OTHER PUBLICATIONS:

Chief of Naval Operations (OPNAV) Instructions

OPNAVINST 11010.20H - Navy Facilities Projects, CH-1 dated 25 Jun 2015 (Copies of OPNAV issuances are available from https://www.secnav.navy.mil/doni/opnav.aspx)

Code of Federal Regulations (CFR) 22 CFR, Parts 120 - 130 - Foreign Relations, Chapter I - Department of State, Subchapter M - International Traffic in Arms Regulations (The above regulations are available at http://www.ecfr.gov/current/title-22/chapter-I/subchapter-M)

29 CFR 1910 - Occupational Safety and Health Standards

29 CFR 1910.147 - The control of hazardous energy (lockout/tagout) (OSHA standards are downloadable from https://www.osha.gov/law-regs.html)

Defense Federal Acquisition Regulations Supplement (DFARS) DFARS 252.204-7012 - Safeguarding Covered Defense Information and Cyber

Incident Reporting (OCT 2016) DFARS 252.211-7003 - Item Identification and Valuation (Aug 2008) DFARS 252.239.7018 - Supply Chain Risk (Oct 2015) (DFARS Clauses are downloadable from https://www.acquisition.gov/dfars/part-252-solicitation-provisions-and-contract-clauses)

Department of the Army Manuals EM-385-1-1 - US Army Corp of Engineers Safety and Health

Requirements Manual, 30 Nov 2014 (Manual is available at: https://www.usace.army.mil/Missions/Safety-and-Occupational-Health/Safety-and- Health-Requirements-Manual/)

Department of Defense (DoD) Handbooks MIL-HDBK-217F, Notice 2 - Reliability Prediction of Electronic Equipment MIL-HDBK-472, Notice 1 - Maintainability Prediction (Copies of the above handbooks are available at http://quicksearch.dla.mil or from the Standardization Document Order Desk, 700 Robbins Ave., Bldg 4D, Philadelphia, PA 19111-5094.)

DoD, Presidential Department of the Navy (DoN), National Institute of Standards and Technology (NIST) and Committee on National Security Systems (CNSS) Security and Cybersecurity Directives, Instructions, Manuals, National Security Decision Directives (NSSD), and Special Publications (SP)

CNSSD-505 - Supply Chain Risk Management (SCRM), dated 7 Mar

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

DoD 5000.04 - Cost and Software Data Reporting Manual, dated 7 May

DoD 5220.22-M - National Industrial Security Program Operating Manual, dated 18 May 2016

DoD 8570.01-M - Information Assurance Workforce Improvement Program, dated 19 Dec 2005 (w/CH4 of 10 Nov 2015)

DoDI 5200.39 - Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E), dated 28 May 2015

DODI 8500.01 - Cybersecurity, dated 14 March 2014, Incoporating Change 1, Effective 7 October 2019

DODI 8510.01 - Risk Management Framework (RMF) for DoD Information Technology (IT) – Incorporating Change 3, dated 29 December 2020

DoDI 8520.02 - Public Key Infrastructure (PKI) and Public Key (PK) Enabling, dated 24 May 2011

NIST SP 800-53 Revision 5 - Security and Privacy Controls for Federal Information Systems and Organizations, dated September 2020

Federal Acquisition Regulations (FAR) 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/far/part-52)

Marine Corps Orders (MCO) MCO 11000.5 - Facilities Sustainment, Restoration, and Modernization

Program, dated 3 Jun 2016 (Above document is available at: http://www.marines.mil/News/Publications/MCPEL/Electronic-Library- Display/Article/900704/mco-110005/)

Naval Air Systems Command (NAVAIR Instructions) NAVAIRINST 4355.19E - Systems Engineering Technical Reviews, dated 6 Feb

NAVAIRINST 3960.4 - Project Test Plan Policy, dated 9 April 2013

NAVAIR M – 3960.4 - Test Planning Manual Version 2.0, dated 10 December

NAVAIR M - 3905.1 - Test Reporting Manual, dated 22 May 2017

NAVAIRINST 5000.21B - Naval Syscom Risk Management Policy

(NAVAIR Instructions are downloadable from https://directives.navair.navy.mil)

PMA205 Documents PMA205 CM Plan - Configuration Management Plan H-1 Light/Attack

Helicopter Program, Rev C dated May 2014 The above document will be provided as Government-Furnished Information (GFI)

NAWCTSD

TMCR 17-18 - Technical Manual Contract Requirements (TMCR) -

Training Device Modernization (TDM), 10 August

The above documents will be provided as GFI.

NAWCAD

TM-NAWCAD-AB21300-H1-

2021-01-21.0

- NAWCAD AB21300, Flight Vehicle Modeling and Simulation, Manned Flight Simulator UH-1Y Flight Control Mechanical Characteristics, dtd 21 Jan 2021

CDS52866 - Control Loading AH-1Z Aircraft Measurement Report, dtd 1 Aug 2017

The above documents will be provided as GFI.

Tactical Environment (TEn) Documents

NAVAIR 28-TEN6.2-INS-01 - Overview and Installation Guide, 20 March 2018 The above documents will be provided as GFI

United States (U.S.) Code Title 10, Section 2451 - 2456 - Defense Standardization Program (U.S Code is downloadable from http://uscode.house.gov/search/criteria.shtml)

Whole Building Design Guide - DOD Unified Facilities Criteria (UFC) http://wbdg.org/ffc/dod/unified-facilities-criteria-ufc

US Office of Personnel Management (OPM) OPM Memorandum - Final Credentialing Standards for Issuing Personal Identity

Verification Cards under HSPD-12, dated 31 July 2008 (The above document is downloadable from https://www.chcoc.gov/sites/default/files/final-credentialing-standards.pdf)

2.2 Non-Government Documents

INDUSTRY STANDARDS

American National Standards Institute (ANSI)/American Society for Quality (ASQ)

ANSI/ASQ Q9000-2015 - Quality Management Systems - Fundamentals and Vocabulary

ANSI/ASQ Q9001-2015 - Quality Management Systems - Requirements ANSI/ASQ Q9004-2009 - Quality Management Systems - Guidelines for

Performance Improvements (Copies of the above documents are available from www.ansi.org)

ANSI/Institute of Electrical and Electronics Engineers (IEEE)

IEEE Std 29148-2018 - IEEE Guide for Developing System Requirements Specifications

IEEE Std 12207-2017, 2nd Edition

- Systems and Software Engineering – Software Life Cycle Processes

ISO/IEC/IEEE Std 15288-2015, 1st Edition

- Systems and Software Engineering – System Life Cycle Processes

IEEE Std 15939-2017 - Adoption of ISO/IEC 15939:2007 - Systems and Software Engineering - Measurement Process

ISO/IEC/IEEE 24748-1, 1st Edition 2018

- Systems and Software Engineering- Life Cycle Management Part I: Guidelines for Life Cycle Management, (Copies of this document are available from www.ieee.org)

National Fire Protection Association (NFPA) NFPA 70 - National Electrical Code, current version

NFPA-70E

NFPA-75

Standard for Electrical Safety in the Workplace, current edition

Standard for the Fire Protection of Information Technology Equipment

(Copies of this document are available from http://www.nfpa.org/Catalog/)

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

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

3. REQUIREMENTS

3.1 General

3.1.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 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 specification PRF 200037A;

c. measure, monitor, and assess the progress of the work performed and costs incurred under the contract; and

d. develop, maintain, update, and report on a monthly basis the Contractor Integrated Program Management Data Analysis Report (IPMDAR) in accordance with (IAW) the Contract Data Requirements List (CDRL).

3.1.1.1 Program Planning

The contractor shall

a. perform program planning processes IAW section 6.3.1.3 of IEEE Std 12207-2017;

b. develop, document, manage, and apply an Integrated Master Schedule (IMS) that presents the contractor’s and subcontractor’s plans and schedules to meet the requirements of the contract;

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

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

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

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

g. prepare the IMS as part of the IPMDAR IAW the CDRL.

3.1.1.1.1 Life Cycle Model Management

The contractor shall perform life cycle model management at the program level IAW IEEE Std 12207-2017, section 6.2.1.

3.1.1.1.2 Infrastructure Management

The contractor shall perform infrastructure management at the program level IAW the organizational implementation standards in IEEE Std 12207-2017, section 6.2.2.

3.1.1.1.3 Program Assessment and Control

The contractor shall define, document, manage, and apply program assessment and control IAW IEEE Std 12207-2017, section 6.3.2.

3.1.1.1.4 Program Decision Management

The contractor shall define, document, manage, and apply a program decision management process IAW IEEE Std 12207-2017, section 6.3.3.

3.1.1.1.5 Work Planning and Scheduling

The contractor shall

a. develop, implement, control, and maintain an IMS—updated, statused, and reported monthly—which presents the contractor’s plans and schedules to meet the contractual requirements;

b. document the planning and scheduling effort, related Government responsibilities, and the interaction for the efforts required for development and delivery of the training products;

c. develop and document a scheduling system showing program milestones and prerequisite events, conferences, reviews, data submittals, Government trainers down time, Government facility readiness dates, and deliveries;

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

e. construct the IMS to ensure that the program milestones are met and to ensure that all deliveries meet the contractual requirements;

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

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

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

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

3.1.1.2 Subcontractor Management and Reporting

The contractor shall

a. manage all subcontracts, including those for a firm-fixed-price (FFP);

b. ensure the timely award of applicable subcontracts and the integration of subcontractor’s plans into the appropriate schedules with sufficient detail;

c. monitor each subcontractor’s staffing plans, including the execution of those staffing plans at the required levels with the required skills;

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

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

3.1.1.3 Integrated Product Teams (IPTs)

a. define, document, implement, and maintain an IPT structure throughout the entire course of performance;

b. comprise the IPT’s membership of multi-functional stakeholders that meet and work together with a product-oriented focus;

c. defer decisions on all other matters to Government Program Management with recommendations;

d. apply IPTs at various levels, ranging from the overall structure of an organization to informal groups functioning across existing units;

e. define and document the composition, structure, roles, and responsibilities of each IPT with Government input;

f. maintain a list of membership for every IPT established;

g. ensure that each IPT (1) consists of Government, contractor, and any applicable subcontractor personnel and (2) has Government and contractor co-chairs; and

h. empower the IPT, including sub-IPTs, to make minor life cycle decisions regarding each product or process within the given IPT’s purview.

3.1.1.4 Risk Management

The contractor shall perform the following:

a. Conduct risk management reviews to allow program systematic control of the uncertainty in the project’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 as specified in section 6.3.4.3 of

ISO/IEC/IEEE Std 15288-2015, 1st Edition.

d. Participate in the Government Risk Working Group established for the program.

e. Present and discuss the status of risk items during all scheduled conferences and reviews using the 5x5 risk cube described in enclosure (1) of NAVAIRINST 5000.21B.

f. Report risk information, data, and analysis in the IPMDAR cited in paragraph 3.1.1 above.

3.1.1.5 Quality Management

The contractor may use ANSI/ASQ Q9000-2015 and ANSI/ASQ Q9004-2009 for guidance.The contractor shall

a. define, document, manage, and apply a quality management process IAW sections 6.2.5 and 6.3.8 of IEEE Std 12207-2017 and ANSI/ASQ Q9001-2015 (equivalent quality management system);

b. make available to the Government for review, the quality system procedures, planning, and all other documentation and data that comprise the quality system;

c. support any inspections, verifications, and evaluations the Government may perform as necessary to ascertain conformance to requirements and the adequacy of the implementing procedures;

d. require subcontractors to maintain a quality system that achieves control of the quality of the services and supplies provided if the contractor deems it fit; and

e. revise the quality system or portions thereof when the quality system fails to meet the contract requirements, which the Government reserves the right to disapprove.

3.1.1.5.1 Control of Government-Furnished Equipment (GFE)

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

a. Examine GFE upon receipt, consistent with practicality, to detect damage.

b. Provide storage for GFE that precludes deterioration.

c. Examine GFE prior to installation, consistent with practicality, to detect damage.

d. Identify and protect GFE from improper use or disposition.

e. Verify and audit quantity of GFE periodically.

f. Document and inspect for software and configuration.

g. Perform periodic inspection and precautions to assure adequate storage conditions to guard against damage from handling and deterioration during storage.

h. Perform functional testing prior to installation to determine satisfactory operation.

3.1.1.5.2 GFE Tracking and Reporting Requirements

The contractor shall

a. utilize a GFE tracking system to track GFE;

b. update the GFE tracking system when GFE location changes to reflect the new location and the reason for the change in location;

c. complete a DD-1149 prior to moving GFE off-site;

d. provide a copy of the DD-1149 to the Deputy Assistant Program Manager for Logistics

(DAPML); and

e. include in the GFE tracking system, at a minimum for each piece of GFE, the following:

(1) What device the GFE is installed on or, if not installed, its physical location.

(2) Part number.

(3) Serial number.

(4) Hardware configuration.

(5) Software configuration.

(6) Date GFE received.

(7) Date GFE shipped.

(8) Reason for shipment.

3.1.1.5.3 Use of Contractor’s Inspection Equipment

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

b. provide the personnel needed to operate such devices and to verify current calibration, accuracy, and appropriate working condition.

3.1.1.6 Configuration Management (CM)

The contractor shall

a. define, document, manage, and apply a CM process IAW section 6.3.5 of IEEE Std

12207-2017 and SAE/EIA-649-1 2014;

b. place Government-Furnished Software (GFS), NDI, and Commercial Item software, and each item’s associated documentation under CM upon receipt;

c. place Commercial Item software items under CM as “disk image” files of the physical media; and

d. maintain the CM process throughout the test and evaluation (T&E) periods to distinguish between different test load versions under test as well as more formal deliveries.

3.1.1.6.1 Change Management

The contractor shall

a. define, document, manage, and apply a process to accomplish change management;

b. request changes to an approved baseline, to include pertinent design changes made after

Critical Design Review (CDR), by submitting an Engineering Change Proposal (ECP) or a Request for Variance (RFV); and

c. prepare the RFV and ECP IAW their respective CDRLs.

3.1.1.6.2 Configuration Status Accounting

The contractor shall

a. Define, document, manage, and apply a process to accomplish configuration status accounting.

b. Identify and document all items incorporated into or deleted from the training device during development and modification.

c. Ensure documentation includes traceability and concurrence with the Requirements

Verification Traceability Matrix (RTVM) and the ECP CDRL.

d. Prepare the Baseline Description Document (BDD) IAW the CDRL.

3.1.1.6.3 Configuration Audits

a. define, document, manage, and apply a process to accomplish configuration audits; and

b. conduct and participate in the Baseline Configuration Audit (BCA), Functional

Configuration Audtion (FCA) and Physical Configuration Audits (PCA), as specified in 3.2.8.15.1, 3.2.8.15.5.1 and 3.2.8.15.5.2.

3.1.1.7 Information Management

The contractor shall

a. define, document, manage, and apply an information management process IAW section

6.3.6 IEEE Std 12207-2017; and

b. include the status of technical data deliveries in the IPMDAR cited above in paragraph

3.1.1.

3.1.1.7.1 Online Information Exchange

The contractor shall

a. provide the contractually required documents, data, and information IAW the CDRLs via a online site that meets current Federal Government, Navy, and NAWCTSD cybersecurity standards when a given CDRL requires such deliveries,

b. determine the means for delivery of online information via the IPT and obtain final approval from the Government,

c. notify the Government team via email upon each posting of new or changed contractual documents, data, and information,

d. only post unclassified data on the online site.

3.1.1.7.2 Data Management

The contractor may use DoD 5220.22-M as guidance during the preparation of the CDRL items.

The contractor shall

a. develop, manage, and implement a data management process for data deliverables;

b. establish and implement procedures to manage the configuration of contractually required data, including data provided by subcontractors.

c. obtain copies of the Data Item Descriptions (DIDs) cited in the CDRL items from the web site http://quicksearch.dla.mil/qsSearch.aspx; and

d. ensure that all data item deliverables are delivered without read-write restrictions and without password protection.

3.1.1.8 Program Measurement

The contractor shall define, document, manage and apply a process to collect, analyze, track, and report a balanced and diverse set of measures and metrics IAW IEEE Std 12207-2017, section

6.3.7 and IEEE Std 15939-2017, incorporating inputs from Government IPT members as necessary. The contractor shall

a. provide program-related measures and metrics that reflect schedule, cost, quality, staffing, product stability, requirements volatility, and complexity information;

b. incorporate into the overall process software specific measures and metrics related to schedule, quality, staffing, build stability, size, requirements volatility, and resource utilization;

c. track, measure, and analyze metrics data over time to report trends;

d. identify and define bounding criteria associated with each metric;

e. implement corrective action when a metric deviates from the defined bounding criteria;

and

f. report metrics data and analysis in the IPMDAR cited above in paragraph 3.1.1.

3.1.1.9 Cost and Software Data Reporting (CSDR)

The contractor shall use a documented standard Cost and Software Data Reporting (CSDR) process that satisfies the guidelines contained in the DoD 5000.04, CSDR Manual.

3.1.1.9.1 Contractor Cost Data Reporting (CCDR)

The contractor shall

a. Use the Government-approved CDSR Plan, DD Form 2794, and the related Resource

Distribution Table (RDT) as the baseline for reporting.

b. Prepare and deliver to the Government a Cost and Hour Report (FlexFile), IAW the

CDRL, for every indicated data element (Data Group B) within the Government-approved CSDR Plan;

c. Provide a Work Breakdown Structure (WBS) dictionary and remarks as a part of the FlexFile format (Data Group B) for every data element identified within the approved CSDR Plan;

d. Prepare and deliver to the Government a Quantity Data Report, IAW the CDRL, for every indicated data element (Data Group B) within the Government-approved CSDR Plan;

e. Provide the following updates to the Government-approved Contract CSDR Plan and related RDT for Government approval:

(1) align the subcontract reporting entity effort to a single WBS element, and

(2) update the RDT as new subcontracts are awarded.

f. Discuss the contractor’s standard cost and software data reporting process that satisfies the guidelines contained in the DoD 5000.04 (CSDR Manual), the requirements in the Government-approved CSDR Plan, and related RDT during the post award conference. If a formal PAC is not held, then the IPMDAR and EAC requirements can be done ad hoc, as a teleconference after contract award.

g. Ensure all control accounts are identified and added to the CSDR Plan.

3.1.2 Security

The contractor shall

a. abide by the apllied 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.1.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.

Controlled Unclassified Information including Legacy FOUO and Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoD Instruction 5200.48, Controlled Unclassified Information (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 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.1.2.2 Operations Security (OPSEC)

a. develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the contractor and subcontractor during performance of the contract.

b. The contractor shall be responsible for the subcontractor implementation of the OPSEC requirements. This program may include cybersecurity and Communications Security (COMSEC). The OPSEC program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include as outlined in the 2013 OPSEC Annex in the DD254 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;

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

and

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

While performing aboard USG, NAVAIR or NAWC sites, the contractor shall comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts.

Include OPSEC as part of its ongoing security awareness program and take all required Agency training. Be responsive to the Supporting OPSEC Manager on a non-interference basis. 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.

3.1.2.3 Unclassified Contractor-Owned Network Security - Safeguarding of Unclassified Controlled Technical Information

The contractor shall

a. Manage and maintain contractor-owned unclassified Information Technology (IT) network assets used to process U.S. Government controlled unclassified information (sensitive information) IAW DFARS 252.204-7012.

b. Apply the safeguarding of Controlled Unclassified Technical Information applies to prime contractors and their subcontractors (if applicable) for information resident on or transiting through contractor unclassified information systems.

c. provide security to safeguard unclassified controlled technical information on their unclassified information systems from unauthorized access and disclosure.

3.1.2.4 Cyber Incident and Compromise Reporting

The contractor shall

a. report to DoD certain cyber incidents that affect unclassified controlled technical information 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.1.2.5 Access to DoD Installations, Government Information, and IT Systems - Personnel Security Background Checks

The contractor shall abide by the following security requirements:

a. The Common Access Card (CAC) shall be the principal identity credential for supporting interoperable access to DoD installations, facilities, buildings, controlled spaces, and access to U.S. Government information systems IAW FAR 52.204-9. The contractor shall coordinate with the appropriate NAWCTSD Technical Point of Contact (TPOC), Contracting Officer Representative (COR), government sponsor, and NAWCTSD Security Office Trusted Agents for issuance of the CAC via the Trusted Associate Sponsorship System (TASS) Program. More information for obtaining the CAC can be found at http://www.cac.mil/common-access-card/getting-your-cac/for-contractors;

b. Contractor personnel whom do not have a security clearance, but require a CAC in performance of their sensitive duties (including access to controlled unclassified information, but not access classified information), shall coordinate with the NAWCTSD Security Office to complete a National Agency Check with Local Agency Checks including Credit Check (NACLC/TIER- 3) background investigation, which includes submission of fingerprints and the Standard Form SF-86 (Questionnaire for National Security Positions). The contractor shall submit the Standard Form 86 to the NAWCTSD Security Office for processing. There shall be no additional NACLC/TIER-3 submissions for contractors holding a valid national security clearance. The Government may issue the credential upon favorable return of the Federal Bureau of Investigations (FBI) fingerprint check, pending final favorable completion of the

NACLC/TIER-3;

c. Access to restricted areas, controlled unclassified information or Government Information Technology by contractor personnel shall be…