Attachment 1-JTC_TRS_PWS_PWS.pdf

DRAFT

Performance Work Statement (PWS) for

JTC TRS Follow On 2021 Contract No.: FA8621-20-R-0003

Prepared by:

Air Force Life Cycle Management Center (AFLCMC) Agile Combat Support (ACS) Directorate

Simulators Division (WNS) 2300 D Street, Bldg. 32

Wright-Patterson Air Force Base (AFB), OH 45433-7249

13 January 2020

Performance Work Statement Change Matrix

Revision Date Description Paragraphs Contract Modification

1.0 PROGRAM OVERVIEW / SCOPE

1.1 Overview

1.2 Scope

2.0 APPLICABLE DOCUMENTS

2.1 Government Documents…………………………………………………………………….7

3.0 REQUIREMENTS

3.1 Program Management

Integrated Product Team (IPT) Reviews and Meetings Database Working Group (DWG) Contractor Labor Hour Reporting Subcontractor Management Associate Contractor Agreements (ACAs) Integrated Master Schedule (IMS) Integrated Master Plan (IMP) 50/50 Requirement Report

3.2 Systems Engineering (SE):

Modular Open Architecture Requirements Database Design Description (DBDD) Drawings

3.3 Configuration Management (CM)

Government Approval and Oversight Configuration Management Plan (CMP) Engineering Change Proposal (ECP)/Contract Change Proposal (CCP) CM Tracking and Repository Commercial Software Sustainment

3.3.6 Government Software Sustainment………………………………………………….15

Multiple CM Baselines Change Incorporation Item Unique Identification (IUID)

3.4 Test and Evaluation

Qualification Test and Evaluation (QT&E) Acceptance Testing Modification Testing Operational Utility Evaluation (OUE) Operational Assessment Support Integrated Test Team (ITT) Test Database

3.5 System Safety

Voluntary Protection Program (VPP)

3.6 Quality

3.7 Security and Access

Security Control Program Protection Plan (PPP) Technology Control Industrial Security Acquisition Systems Protection

3.8 Cybersecurity (CS)

CS Design for Assessment and Authorization (A&A) Error! Bookmark not defined.

System Security .......................................................... Error! Bookmark not defined.

Architecture Analysis ................................................. Error! Bookmark not defined.

3.9 Data Management and Distribution

Data Accession List (DAL) Electronic Data Management System (EDMS)

3.9.3 Multi-user ECP Automated Review System (MEARS)……………………………. 21

3.10 System Requirements

System Network Requirements System/Subsystem Specification (SSS) Design Data Software Development System Integration Distributed Mission Operations (DMO) Joint Deficiency Reporting System (JDRS) Functional Configuration Audit (FCA) Physical Configuration Audit (PCA) Prototype System Integration Laboratory (SIL) Designation

3.11 Production

Factory Acceptance Tests (FATs) Trainer Facilities Report Site Surveys/Facility Interface Delivery (Production) Site Acceptance Tests (SATs) Cybersecurity Tests

3.12 JTC TRS Device Transition…………………………………………………………... 27

3.12.1 Design Acceptance Tests (DATs)………………………………………………... 27

3.12.2 JTAGSS Device Transition ……………………………………………………… 27

3.13 Sustainment

System Supportability Contractor Logistic Support (CLS) Training System Support Center (TSSC) Simulator Configuration Working Group (SCWG) GFE/Government Furnished Property (GFP)

3.14 Deficiency Reporting

JDRS Requirements

3.14.2 Deficiency Report Initiation……………………………………………………… 39

3.14.3 Deficiency Tracking………………………………………………………………. 39

3.14.4 Deficiency Analyzing……………………………………………………………... 39

3.15 Contract Transition

Transition Planning

4.0 CONTRACTOR-PROVIDED TRAINING

4.1 Initial System Operations Training

4.2 Tier One Maintenance Training

4.3 Follow-On Operations & Maintenance Training

5.0 SERVICES SUMMARY (SS)

5.1 SS Requirement

5.2 Surveillance Methods

6.0 PRICED UPGRADE REQUIREMENT………………………………………………42

6.1 Digitally Aided Close Air Support (DACAS) Option………………………………….42

6.1.1 DACAS Overview…………………………………………………………………42

6.1.2 DACAS Design Requirements…………………………………………………….43

6.1.3 DACAS General Requirements……………………………………………………43

Appendix A: Acronyms Appendix B: Database Development Requirements Appendix C: Simulator Common Architecture Requirements and Standards (SCARS)..….. 53

1.0 PROGRAM OVERVIEW / SCOPE

1.1 Overview

The Joint Terminal Control Training and Rehearsal System (JTC TRS) Program will continue to acquire and sustain high fidelity training systems designed to provide realistic training for Terminal Attack Control, Close Air Support (CAS), Call for Fire and Air to Ground Command and Control.

The JTC TRS Program consists of two separate simulation systems: a Joint Terminal Attack Controller (JTAC) simulator, known as JTC TRS, which includes fixed dome, desktop, and portable systems, and an Air Support Operations Center (ASOC) simulator known as Joint Theater Air Ground Simulation System (JTAGSS). The JTC TRS Program will continue to provide robust, interactive multimedia, High Level Architecture (HLA) and/or Distributed Interactive Simulation (DIS) compliant systems. The systems will provide constructive entity control, realistic flight profiles, accurate ordnance delivery and effects, and support actual, simulated or emulated equipment used in combat operations including weapons, radio equipment, target marking equipment and global positioning systems. The systems are and must be capable of participating in distributed operations over Distributed Mission Operations (DMO) networks. Both simulator systems are critical to the training and mission readiness of the TACP Weapons System and Combat Control JTAC qualifications, and therefore there can be no interruption of training capability during any transition or over the course of the system sustainment.

1.2 Scope

The JTC TRS Program will continue to procure, field and support upgradeable mission simulation systems (JTC TRS and JTAGSS) that have joint applicability for training personnel in all services.

JTC TRS and JTAGSS devices will be procured as production-ready systems or transitioned into the program to support JTAC training needs. For day-to-day training operations at the JTC TRS training sites, government and military personnel will conduct all training, perform minor maintenance, and offer limited upgrade support. Contractor instructors or technicians for JTC TRS training sites will not be required on-site except during initial system installation or if unscheduled or scheduled maintenance is required. Contractor field support for JTC TRS will be conducted on an as needed and/or as scheduled basis. For day-to-day operations at the JTAGSS training sites, contractor personnel will operate the system for training events, perform maintenance, and install government approved configuration changes. The contractor will provide spare parts, system repair support, and maintain system concurrency via a logistics support process and through operation of a Training System Support Center (TSSC) to meet the trainer repair time requirement (as defined in the H001 Clause), the Performance Specification (P-Spec) and the contract.

2.0 APPLICABLE DOCUMENTS

The following documents form a part of this Performance Work Statement (PWS) to the extent specified herein. These documents are provided as reference material for the purpose of interpreting the tasks of the PWS, unless otherwise specified. The latest revision or date in effect at the time of contract award shall apply. In the event of conflict between the documents (other than those implementing Public Law) referenced herein and the contents of this PWS, the contents of this PWS shall be considered as superseding requirements.

Applicable Documents Number Document Name Date

2.1 Government Documents

AFCD Standard, Version 2 Air Force Common Dataset (AFCD), Version 2 01 Dec 11

AFI 13-112, Vol 1 Joint Terminal Attack Controller Training (JTAC) Program

29 Sep17

AFI 13-114V1 Air Support Operations Center (ASOC)Training Program 30 Apr 12

AFI 13-114V3 Air Support Operations Center (ASOC) Operations Procedures 1 Jun 09

AFI 21-113 AF Metrology and Calibration (AFMETCAL) Management

03 Jun 16

AFI 16-1406 Industrial Security Program Management 25 Aug 15

AFI 17-101

Risk Management Framework (RMF) for Air Force Information Technology (IT)

23 Feb 17

AFI 36-2251 Management of Air Force Training Systems 05 Jun 09

AFI 63-101/

20-101

Integrated Life Cycle Management, Chapter 5 09 May 17

AFI 91-203

Air Force Occupational Safety, Fire, and Health Standards

11 Dec 18

AFI 99-103 Capabilities-Based Test and Evaluation 06 Apr 17

AFMAN 17-1301 Computer Security (COMPUSEC) 10 Feb 17

AFMAN 17-1302-o Communication Security (COMSEC) Operations 03 Feb 17

AFTTP 3-3

JTAC

Combat Fundamentals Joint Terminal Attack Controller 24 Oct 12

ASD-TR-90-

5000 Simulator Test 2000 (ASD Study) 12 Dec 90

CNSS

Instruction No.

Security Categorization and Control Selection For National Security Systems 27 Mar 14

DFARS Department of Defense FAR Supplement Part 252.245-7004 20 Aug 19

DoD 5200.1-M Acquisition Systems Protection Program, Chapter 5 15 Mar 94

DoD 5220.22-M National Industrial Security Program Operating Manual (NISPOM)

18 May 16

DoD 8570.01-M Information Assurance Workforce Improvement Program

19 Dec 05 (Chg 4, 11

Oct 15)

DoD Guide to

IPPD

DoD Guide to Integrated Product and Process Development August 1998

DoD Guide to

IMP/IMS

Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide (Version 0.9)

21 Oct 05

DoDD 5000.01 The Defense Acquisition System 12 May 03 (Chg 2, 31

Aug 18)

DoDD 5230.25 Withholding of Unclassified Technical Data From Public Disclosure

6 Nov 84 (Chg 2, 15

Oct 18) DoD FMR7000.14- R

Department of Defense Financial Management Regulation (DoD FMR) Jun 17

DoDI 5000.64 Accountability and Management of DoD Equipment and Other Accountable Property 27 Apr 17

DoDI 5000.76 Accountability and Management of Internal use Software (IUS) 2 Mar 17

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

28 May 15 (Chg 2, 15

Oct 18)

DoDI 5230.24 Distribution Statements on Technical Documents 23 Aug 12 (Chg 3, 15

Oct 18) DoDI 8500.01 Cybersecurity 14 Mar 14

DoDI 8510.01 Risk Management Framework for DoD Information Technology (IT)

12 Mar 14 Chg 2, 28 Jul

17)

DoDI 5000.02 Operation of the Defense Acquisition System 7 Jan 15 (Chg 4, 31 Aug 18)

DoDM 4140.01 Vol 1-11 DoD Supply Chain Materiel Management Procedures 3 Jun 19

FAR Federal Acquisition Regulation, Part 52.219-14 Nov 11 FIAR Guidance Financial Improvement Audit Readiness (FIAR) Guidance Apr 17

FIPS PUB 199 Standards for Security Categorization of Federal Information and Information Systems Feb 04

JP3-09.3 Joint Tactics, Techniques, and Procedures for Close Air Support 25 Nov 14

MIL-HDBK-61

A Configuration Management Guidance 07 Feb 01

MIL-STD-

130N(1)

Department of Defense Standard Practice, Identification Marking of U.S. Military Property 16 Nov 12

MIL-STD-882E

DoD Standard Practice for System Safety 11 May 2012

NIST Special Publications (SP) 800-53, Rev 4

Security and Privacy Controls for Federal Information Systems and Organizations Apr 13

NIST Special Publications (SP)

Assessing Security and Privacy Controls in Federal Information Systems and Organizations Dec 14

800-53A, Rev 4 Public Law 91-

Occupational Safety and Health Act (OSHA), as amended by Public Laws

29 Dec70 (Amd thru 1

Jan 04) Technical Order 00-20-14

Air Force Metrology and Calibration Program 30 Sep 17

Technical Order 00-35D-54

USAF Deficiency Reporting, Investigation, and Resolution 1 Sep 15

USC Title 10, Section 2466

Title 10, U.S. Code, Limitations on the Performance of Depot-Level Maintenance of Material

Number Document Name Date

2.2 Commercial Documents

ANSI/GEIASTD-

Reliability Program Standard for Systems Design, Development, and Manufacturing 20 Aug 09

ASTM-D3951-18 Standard Practice for Commercial Packaging 01 May 18

SAE AS5553C Fraudulent/Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition

26 Mar 19

SAE EIA-649C

Configuration Management Standards 07 Feb 19

3.0 REQUIREMENTS

3.1 Program Management

The contractor shall be responsible for integrating all work relating to the performance of this contract. The contractor shall designate a Program Manager (PM) who will oversee the JTC TRS effort and be the focal point for all program management issues. The PM shall manage the JTC TRS Program In Accordance With (IAW) the requirements outlined in the P-Spec and this document.

3.1.1 Integrated Product Team (IPT)

The contractor shall provide a structured IPT approach to requirements management IAW the “DoD Guide to Integrated Product and Process Development (Version 1.0) February 5, 1996”. The IPT shall include the contractor, users and JTC TRS Program Office participation to improve coordination within the IPT and ensure inputs from all program stakeholders and functional disciplines.

3.1.2 Reviews and Meetings

The contractor shall schedule and conduct meetings for the government. Unless otherwise specified, these meetings and reviews shall be held at the contractor’s facility, an alternate location or via teleconference with government coordination.

Contractor personnel and their subcontractors must identify themselves as contractors or subcontractors during meetings, telephone conversations, and in all electronic messages or correspondence related to this contract.

3.1.2.1 Post Award Conference (PAC)

The contractor shall conduct a PAC within 15 days after contract award. The purpose of the PAC is to discuss all parties’ understanding of the scope of work.

[A001: DI-ADMN-81249B, Conference Agenda; A002: DI-ADMN-81250B, Conference Minutes; A042: DI-ADMN-81373, Presentation Material]

3.1.2.2 System Requirements Review (SRR)

The contractor shall conduct SRRs in conjunction with the PAC to confirm to the government that the contractor understands JTC TRS and JTAGSS system/operational requirements and ensure that each requirement is traceable.

[A002: DI-ADMN-81250B, Conference Minutes]

3.1.2.3 Guidance Conference

Also in conjunction with the PAC, the contractor shall present a briefing on their interpretation of the technical manual program requirements as reflected in the basic contract, PWS, CDRLs, DIDs, and the Technical Manual Contract Requirements (TMCR) as well as the planned preparation and delivery of the Technical Manuals (TMs) and related data.

[A041: TM 86-01P/T, Technical Manual Contract Requirements]

3.1.2.4 IPT Meetings

The contractor shall co-chair, with the government, bi-weekly IPT teleconferences for contractor tracking of action items, schedule progress, and providing status updates. The entries for each action item shall include the originator, a detailed description of the problem or issue, responsibility, suspense date, status, actions required, actions taken and date closed, with closure agreement by the government. Access to action items shall be available to the government.

3.1.2.5 Program Management Reviews (PMRs)

PMRs shall be conducted as requested by the government but not more often than quarterly. The PMRs shall provide details of program schedule, technical and financial status (to include compliance with Federal Acquisition Regulation (FAR) 52.219-14), action items, risk management, and other topics as needed. The PMRs will be held at a location directed by the government.

[A001: DI-ADMN-81249B, Conference Agenda; A002: DI-ADMN-81250B, Conference Minutes; A042: DI-ADMN-81373, Presentation Material]

3.1.2.6 Technical Interchange Meetings (TIMs)

The contractor shall support TIMs as required through the life of the contract. A TIM may be called to address specific topics or issues, the status of development or test activities between PMRs, the functions of an established working group, or to coordinate and provide guidance for engineering data or technical manuals. TIMs may be combined with other meetings or held as a stand-alone meeting. Their estimated frequency will be twice per year.

[A001: DI-ADMN-81249B, Conference Agenda; A002: DI-ADMN-81250B, Conference Minutes; A042: DI-ADMN-81373, Presentation Material]

3.1.2.7 Engineering Review Board (ERB)

The contractor shall co-chair, with the government, monthly IPT teleconferences for contractor tracking of test discrepancies (TDs)/deficiencies, Help Desk tickets, as well as concurrency and obsolescence issues. The contractor shall identify and brief new TDs, system deficiencies, and help desk tickets, and provide recommendation of priorities for government review. The contractor shall report on existing discrepancies and provide schedule, status, approach, engineering status, and TDP revisions needed to resolve the discrepancies. The contractor shall identify and brief concurrency candidates and potential obsolescence issues with recommended solutions.

[A002: DI-ADMN-81250B, Conference Minutes]

3.1.3 Database Working Group (DWG)

The contractor shall form a DWG in conjunction with the JTC TRS Program Office. The contractor shall support DWGs as required through the life of the contract to discuss database and model requirements, work, progress and testing.

Responsibilities of the DWG include:

- Define and control modeling issues for each database

- Review and recommend approval of scenario data to be included in the scenario databases

- Acceptance of the Database Design Description (DBDD)

- Define the baseline for each database

The contractor shall use a product life cycle approach for the management of the database development process. The contractor shall discuss database requirements, schedule, status, approach, engineering status, and TDP revisions. The contractor shall note any potential impacts to training and identify possible impacts related to COTS software. The contractor shall provide reports for formal and informal database testing.

[A001: DI-ADMN-81249B, Conference Agenda; A002: DI-ADMN-81250B, Conference Minutes; A042: DI-ADMN-81373, Presentation Material; A009: DI-IPSC-81437A, Database Design Description (DBDD); A032: DI-NDTI-80809B, Test/Inspection Report]

3.1.4 Contractor Labor Hour Reporting

The contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Air Force via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each government Fiscal Year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the Contractor Manpower Reporting Application (CMRA) help desk at cmra@pentagon.af.mil.

3.1.5 Subcontractor Management

The contractor shall integrate subcontractor efforts into program management and tracking systems.

The contractor shall ensure all requirements of this contract and subsequent modifications are consistently applied to all subcontracts and teaming arrangements.

3.1.5.1 Subcontractor Compatibility and Performance

The contractor shall institute procedures to ensure subcontractors and vendors have incorporated necessary program elements to assure compatibility of supplied equipment or services. The contractor shall effectively manage and monitor subcontractor and supplier performance to ensure the quality of all acquired products and services. The contractor shall manage subcontractor compliance with all cybersecurity and Supply Chain Risk Management (SCRM) requirements.

http://www.ecmra.mil/ mailto:cmra@pentagon.af.mil

3.1.6 Associate Contractor Agreements (ACAs)

The contractor shall obtain ACAs or Letters of Intent to obtain data necessary to meet program requirements. In addition, the contractor shall enter into ACAs as required to exchange data and participate with manufacturers/data sources for the system. The government will sponsor ACA relationships as needed. The contractor shall make these agreements available to the government via the Data Accession List (DAL).

[A018: DI-MGMT-81453B/T, Data Accession List/Internal Data (DAL)]

3.1.7 Integrated Master Schedule (IMS)

The contractor shall prepare an IMS IAW the “DoD Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide (Version 0.9, October 21, 2005)”. The IMS shall result in a fully detailed networked schedule capable of critical path analysis. The IMS must be consistent with other contract documents and plans, reflect a clear understanding of program requirements, and durations must be realistic and compatible with the contract scope of work.

[A024: DI-MGMT-81861A/T, Integrated Program Management Report (IPMR)]

3.1.8 Integrated Master Plan (IMP)

For modifications and Engineering Change Proposals (ECPs), the contractor shall prepare and deliver an IMP with their proposal based on a comprehensive product-oriented Work Breakdown Structure (WBS) to meet and maintain program management cost, schedule, and performance requirements IAW the DoD “Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide (Version 0.9, October 21, 2005)”. The contractor shall document all significant cybersecurity events, technical reviews and entrance/exit criteria in their IMP. The contractor shall include detailed descriptions of key milestones and supporting criteria in the IMP. The IMP shall include a clear and complete allocation of events necessary to successfully execute the modification or ECP. The IMP shall include event entrance and exit criteria with process integration. The contractor shall use a risk assessment management tool to monitor cost, schedule, and performance status.

[A018: DI-MGMT-81453B/T, Data Accession List/Internal Data (DAL)]

3.1.9 50/50 Requirement Report The contractor shall provide depot data IAW Title 10 United States Code Section 2466 known as the “50/50” law, as amended by the National Defense Authorization Acts of FY98.

[A020: DI-MGMT-81749B/T, The 50/50 Requirements Report]

3.1.10 Budgetary Estimates

The Contractor shall provide budgetary estimates as requested by the Government PMO. Budgetary estimates shall include estimated cost (labor, material, travel, courseware, etc.), schedule, and assumptions.

[A028:DI-MISC-80748/T, Engineering Services Memorandum (ESM)]

3.2 Systems Engineering (SE):

The contractor shall develop, establish, deliver and maintain a SE process that is documented in their Systems Engineering Management Plan (SEMP). The SE process shall be a requirements driven, iterative design process that determines alternative design solutions, and conducts trade studies and analyses, to select the most cost-effective solution. The SE process shall include total system performance including quality, safety, security, human engineering, cybersecurity, reliability (using the system engineering practices of American National Standards Institute (ANSI)/Government Electronics and Information Technology Association (GEIA)-Standard

(STD)-0009), maintainability, and availability. The contractor shall include features that support technology insertions and system evolution throughout the training system life cycle (reference Air Force Instruction (AFI) 63-101/20-101, Chapter 5).

[A040: DI-SESS-81785A, System Engineering Master Plan (SEMP)]

3.2.1 Modular Open Architecture Requirements

The contractor should maintain a modular, open architecture design using Commercial Off-the- Shelf (COTS) products to the maximum extent possible and follow the Simulator Common Architecture Requirements and Standards (SCARS) Affiliate design approach. The SCARS Affiliate design approach, delineated in Appendix C, shall produce a system that consists of hierarchical collections of software and hardware configuration items (components). These components shall be of a size that supports competitive acquisition as well as reuse. The SCARS Affiliate design approach shall emphasize the selection of components that are available commercially or within the DoD, to avoid the need to redevelop products that already exist and that can be reused. The SCARS Affiliate rationale shall explicitly address any tradeoffs performed, particularly those that compromise the modular and open nature of the system.

The SCARS Affiliate architectural approach shall enable the rapid and affordable insertion and refreshment of technology through modular design, the use of open standards and open interfaces.

The SCARS Affiliate shall define the functional partitioning and the physical modularity of the system to facilitate future replacement of specific subsystems and components without impacting other parts of the system. The SCARS Affiliate shall design to minimize inter-component dependencies to enable future rapid development, replacement, or upgrade of simulator components.

The SCARS Affiliate shall use Commercial-off-the-Shelf (COTS) and Open Source software whenever possible.

The SCARS Affiliate shall use interface standards that are well defined, mature, widely used, and readily available. SCARS Affiliate shall provide documentation that clearly defines and describes all interfaces between the proprietary or vendor-unique components and any interdependent components within the simulator. For additional SCARS data, refer to Appendix C of this document.

SCARS capability shall will be integrated into and managed within the JTC TRS devices as delineated in Appendix C.

3.2.2 Database Design Description (DBDD)

The contractor shall generate, submit, and maintain a DBDD. The DBDD shall contain the specific details of delivered databases, models, and entity behaviors.

[A009: DI-IPSC-81437A/T, Database Design Description (DBDD)]

3.2.3 Drawings

The contractor shall develop and deliver engineering drawings defining the system baseline and all associated training system assets covered by this contract, including system drawings and schematics, mechanical assembly drawings, and instrument drawings. Drawings shall include all data necessary to modify and sustain the system and components.

[A038: DI-SESS-81000F/T Product Drawings/Models and Associated Lists]

3.2.3.1 Drawing Updates

The contractor shall update the engineering baselines for all modifications performed under this contract. The contractor shall maintain the currency of each engineering drawing and document.

Whenever a contract tasking affects the content of existing drawings, the contractor shall revise, and shall ensure all subcontractors revise, the existing engineering data in accordance with their approved Configuration Management Plan (CMP).

[A037: DI-SESS-80858C Supplier’s Configuration Management Plan]

3.3 Configuration Management (CM)

The contractor shall establish and institute an effective CM process. The contractor shall use Military (MIL)-Handbook (HDBK)-61A and Society of Automotive Engineers (SAE) Electronic Industries Alliance (EIA)-649B as a guide to all CM procedures.

3.3.1 Government Approval and Oversight

The contractor shall submit Class I configuration changes to be approved by the government through the ECP process. The contractor will make all Class II changes available to the government for review. The contractor shall perform CM and maintain CM documentation for software, hardware, engineering data, drawings, technical orders/manuals and databases. The contractor is subject to government oversight and inspections and shall provide CM documentation as required.

[A035: DI-SESS-80639D, Engineering Change Proposal (ECP)]

3.3.1.1 Class I Changes

Class I changes, as defined in MIL-HDBK-61A, Table 6-2 and paragraph 6.1.1.2, shall be incorporated into engineering data and associated lists within 30 days after approval of the applicable change authorization documents.

3.3.1.2 Class II Changes

Class II changes, as defined in MIL-HDBK-61A, Table 6-2 and paragraph 6.1.1.2, shall be incorporated into engineering data and associated lists upon accumulation of five approved changes, or upon incorporation of subsequent Class I changes, whichever occurs first.

3.3.2 Configuration Management Plan (CMP)

The contractor shall submit a CMP which addresses the management of concurrency, obsolescence, technology refresh management, and process improvements.

[A037: DI-SESS-80858C, Supplier’s Configuration Management Plan]

3.3.3 Engineering Change Proposal (ECP)/Contract Change Proposal (CCP) The contractor shall prepare and execute all ECPs/CCPs upon direction of the Procuring Contracting Officer (PCO). This effort may include, but is not limited to, systems modifications, reference documents collection, project communication plans, impact analyses, and feasibility studies. ECPs shall be accompanied by a Notice of Revision (NOR) when changes to the baselines are necessary. Potential configuration baseline waivers shall be presented to the PCO.

[A004: DI-ADMN-81401C, Contract Change Proposals; A035: DI-SESS-80639D, Engineering Change Proposal (ECP); A036: DI-SESS-80642D, Notice of Revision (NOR)]

3.3.4 CM Tracking and Repository

The contractor shall track and store all system baselines for hardware, software, firmware, supporting engineering and technical documentation. The computer software product end item baseline documentation shall be made available to the government (via electronic means to the maximum extent possible) for all system baselines.

[A012: DI-MCCR-80700A/T, Computer Software Product End Items]

3.3.5 Commercial Software Sustainment

The contractor shall document and sustain all procedural and operational changes made to commercial software, to include integration software to meld Commercial Off the Shelf (COTS) software/systems. The contractor shall deliver, maintain, and track all commercial vendor software and licenses used on all JTAGSS and JTC TRS versions through the life of the program.

The contractor shall identify and keep COTS software maintenance licenses current for all that require periodic renewal to add system functionality.

[A005: DI-IPSC-81431A/T, System/Subsystem Specification (SSS); A010: DI-IPSC-81441A/T, Software Product Specification (SPS); A011: DI-IPSC-81442A/T, Software Version Description (SVD)]

3.3.6 Government Software Sustainment

The contractor shall manage and maintain all procedural and operational software code changes made to the government JTAGSS Execution Tool (JET) software application.

[A005: DI-IPSC-81431A/T, System/Subsystem Specification (SSS); A010: DI-IPSC-81441A/T, Software Product Specification (SPS); A011: DI-IPSC-81442A/T, Software Version Description (SVD)]

3.3.7 Multiple CM Baselines

The contractor shall manage the configuration of multiple fielded system baselines. Baseline information shall be provided to the government as requested.

3.3.8 Change Incorporation

When a Physical Configuration Audit (PCA) is performed, all outstanding changes, (including those resulting from ECPs) shall be incorporated into engineering drawings and associated lists within 30 days after the PCA and prior to completion of this contract. Original Commercial and Government Entity (CAGE) codes shall not be deleted.

[A038: DI-SESS-81000F/T, Product Drawings/Models and Associated Lists]

3.3.9 Item Unique Identification (IUID)

The contractor shall follow the applicable IUID requirements in Section I, DFARS Clauses 252.211-7003, 252.211-7007, 252.211-7008 and MIL-STD-130N(1). The contractor shall manage and maintain an IUID program throughout the life of the contract. The contractor shall apply IUID to the training system only; spares and the imbedded components will not be marked.

The contractor shall propose and implement IUID on any items not previously marked, e.g., new or transitioned JTC TRS or JTAGGS devices, if the item meets the IUID requirement(s).

[A021: DI-MGMT- 81803/T, IUID Marking Plan; A022: DI-MGMT-81804A/T, IUID Marking Activity, Validation and Verification Report]

3.4 Test and Evaluation

The contractor shall develop and deliver a comprehensive life cycle System Test Plan (STP) for JTC TRS and JTAGSS.

The contractor shall prepare, submit, and update the STPs as required to reflect changes, additions and/or ECPs. The JTC TRS and JTAGSS STPs will document the overall test approach, schedule, entry/exit criteria and define roles and responsibilities for production and follow-on testing as necessary for program success. The STPs shall identify test events, test methods and analysis approaches as required, as well as resources required. The JTC TRS STP status will be reviewed during Integrated Test Team (ITT) meetings and approved by the government prior to conducting final site acceptance testing.

[A030: DI-NDTI-80566A/T, Test Plan]

3.4.1 Qualification Test and Evaluation (QT&E)

The contractor shall support QT&E as requested by the Government. The contractor shall create Design Acceptance Test (DAT) procedures to verify compliance with the P-Spec. The contractor shall conduct a Test Readiness Review (TRR) prior to this testing to ensure system, contractor, and government test team support readiness to conduct the test. The contractor shall support the testing as requested by the government.

[A031: DI-NDTI-80603A/T, Test Procedures]

3.4.2 Acceptance Testing

The contractor shall develop an Acceptance Test Procedure (ATP) for government approval.

The ATP shall evolve to ensure each system, modification, or upgrade meets the P-Spec and current product baseline to include current database, model counts and model articulations. The ATP will support Design Acceptance Tests (DAT), Factory Acceptance Tests (FAT) and Site Acceptance Tests (SAT). The government reserves the right to observe all acceptance testing.

[A031: DI-NDTI-80603A/T, Test Procedures]

3.4.2.1 Cybersecurity and Distributed Mission Operations (DMO) Acceptance Requirements The contractor’s Cybersecurity assessment, to include a mitigation plan for non-compliant controls (per para 3.8), shall be received and approved by the Live, Virtual, Constructive (LVC) Authorizing Official (AO) prior to the Program Office accepting JTAGSS and JTC TRS device modifications or new JTC TRS configurations. JTC TRS devices may be accepted prior to DMO certification; however, contractor is responsible to comply with specifications in paragraph 3.10.6 for all devices, even if previously accepted by the government.

[A026: DI-MGMT-82001/T, DOD Risk Management Framework (RMF) Package Deliverables]

3.4.2.2 ATP Updates

The contractor shall update the ATP documentation as necessary to reflect the latest product baseline.

[A031: DI-NDTI-80603A/T, Test Procedures]

3.4.3 Modification Testing

The contractor shall provide a fielded system modification and upgrade test plan using AFI 99-103, AFI 36-2251 and Aeronautical Systems Division (ASD)-TR-90-5000 (Simulator Test 2000) as guidelines. Software and database modifications shall be tested and accepted by the government at the TSSC or designated site prior to installation. Prior to fielding any major software changes, the contractor must ensure the system changes pass a new Operational Utility Evaluation, gain JFS ESC Sim Accreditation, have a complete LVC AO approved ATO, and have completed CAF DMO Federation Testing to be certified for operation on the CAF Distributed Mission Operations Network to ensure no period exists where training cannot be accomplished in the simulators.

System changes must also be capable of using current created training and mission rehearsal scenarios at each simulator location. The contractor shall provide the required media, package, shipping, and installation (or instruction for on-site tier-1 install) of the software programs and data at the required sites. Documentation such as the Software Version Description (SVD) and user guide shall be delivered with the software (as applicable). All upgrades shall be subjected to acceptance testing at the fielded site.

[A011: DI-IPSC-81442A/T, Software Version Description; A030: DI-NDTI-80566A/T, Test Plan; A031: DI-NDTI-80603A/T, Test Procedures; A032: DI-NDTI-80809B, Test/Inspection Report]

3.4.4 Operational Utility Evaluation (OUE)

The contractor shall support independent government OUE testing as requested. The contractor shall support a government-run TRR before OUE to ensure the system, contractor, government test team and support required by using organization is prepared prior to the OUE.

3.4.4.1 OUE Training

The contractor shall provide hands-on system operation and familiarization training for the government evaluators. Familiarization training will not exceed two business days.

3.4.5 Operational Assessment Support

The contractor shall provide support for the conduct of OUE, government certifications (e.g., SIMCERT), validations (e.g., SIMVAL) and other operational assessment activities by the government in order to verify the training devices provide accurate and effective training. The contractor shall provide technical consultation and support, including subcontractor personnel as required. Technical support may include but not be limited to:

- Test setup and establish initial conditions

- Operate instructor stations

- Record test results

- Maintain configuration control and management

- Report, process, and track test discrepancies

- Monitor maintenance of test articles

- Perform daily readiness checkout and otherwise jointly participate in the conduct of tests

3.4.6 Integrated Test Team (ITT)

The contractor shall participate in an ITT comprised of government and contractor representatives to lead the JTC TRS test program. The ITT will be responsible for tasks including developing and reviewing test plans, reports, and related program test documentation and organizing and scheduling test events. The contractor shall designate a Test Director to act as the Point of Contact (POC) for all test-related matters and the Test Director or his representative shall participate in the JTC TRS and JTAGSS ITT activities. ITT meetings shall be jointly led. ITT meetings shall be held as required.

[A030: DI-NDTI-80566A/T, Test Plan; A031: DI-NDTI-80603A/T, Test Procedures]

3.4.7 Test Database

The contractor shall develop a test database to capture, store, and retrieve all test results to include contractor and government-run tests. The contractor shall provide a status report of all open test results at the Engineering Review Board (ERB) or Database Working Group (DWG).

[A018: DI-MGMT-81453B/T, Data Accession List/Internal Data (DAL)]

3.5 System Safety

The contractor shall deliver and maintain a safe, environmentally compliant system. The contractor shall evaluate the potential environmental safety and occupational health risks, propose hazard controls and mitigations, and design the system to reduce or eliminate risks IAW MIL-STD-882E, AFI 91-203, and Occupational Safety and Health Administration (OSHA) Public Law 91-596. The contractor shall clearly delineate all risks, their likelihood of occurring, mitigation plans, and recovery plans in case risk(s) are realized. The contractor shall conduct a safety review of the JTC TRS and JTAGSS.

[A034: DI-SAFT-80102C/T, Safety Assessment Report; A019: DI-SAFT-80626/T, System Safety Program Plan]

3.5.1 Voluntary Protection Program (VPP)

The contractor shall establish a safety and health plan and corresponding site safety checklist resulting in the promotion, investigation, correction and tracking of safety and health violations and/or uncontrolled hazards in contractor work areas. Installation-specific references and policies may be included (or attached) to the plan.

3.5.1.1 VPP Lifecycle Compliance

The contractor shall comply with the health and safety rules of each government installation. The contractor shall take reasonable steps and precautions to prevent accidents and preserve the health and safety of contractor and government personnel in performance of any tasks related to this contract. The contractor shall take additional immediate precautions identified by the contracting officer for health and safety purposes.

3.6 Quality

The contractor shall establish, implement and maintain a quality assurance program in support of the JTC TRS Program and TSSC operations. The contractor shall allow access to all program data, documentation, and records of inspection throughout the contract performance period, so that performance can be evaluated by the government. The contractor shall correct noted deficiencies and provide a mitigation strategy to correct deficiencies within an agreed-to timeframe coordinated with the government Program Office. The contractor shall develop a Quality Assurance Program Plan (QAPP). At a minimum, the plan shall address compliance and implementation of the following items:

- A process to ensure the required trainer repair times are achieved on all training devices.

- A periodic audit process to ensure service delivery objectives as indicated in the Services

Summary (SS) Table in Section 5.1 are met.

[A019: DI-QCIC-81794A, Quality Assurance Program Plan]

3.7 Security and Access

The contractor shall provide a level of security (physical and information) that is commensurate with the security level of the information handled by JTC TRS and JTAGSS, and conform to DD- Form 254 security requirements, (reference Committee on National Security Systems Instruction (CNSSI) No. 1253). In the event of a conflict between requirements in the DD-254 and this PWS, the DD-254 shall take precedence. JTC TRS and JTAGSS data and equipment will be categorized up to the SECRET level of security classification.

3.7.1 Security Control

The contractor shall designate a Field Security Officer and establish a Joint Personnel Adjudication System account with the Defense Security Service.

3.7.2 Program Protection Plan (PPP)

The contractor shall participate with the government in the development of a PPP. The contractor shall participate with the government in recommending protection strategies/ countermeasures needed to safeguard the acquisition process at all fielded locations.

3.7.2.1 Program Protection Implementation Plan (PPIP)

The contractor shall develop a PPIP to include all requirements outlined in the government provided PPP.

[A003: DI-ADMN-81306/T, Program Protection Implementation Plan]

3.7.3 Technology Control

The contractor shall implement protection standards and guidance described in DoD 5200.1-M, Chapter 5, to prevent foreign intelligence collection and/or the unauthorized disclosure of information governed by the International Traffic in Arms Regulation (ITAR) and/or the Export Administration Regulation during JTC TRS Program execution. All such documents shall be properly marked in accordance with DoD Instruction (DoDI) 5230.24. Technical documents prohibited from distribution are defined in DoD Directive (DoDD) 5230.25.

3.7.4 Industrial Security

The contractor shall enter into a Visitor Group Security Agreement (VGSA) for service performed on a military installation. The contractor shall comply with the requirements of DoD 5220.22-M (National Industrial Security Program Operating Manual (NISPOM) and AFI 31-601 in management of the contract. The contractor shall appoint an Industrial Security Manager/Specialist who shall oversee security operations IAW applicable DoD and Air Force instructions listed above.

3.7.5 Acquisition Systems Protection

The contractor shall ensure security program requirements are integrated into all areas of the JTC TRS Program as required by DoDD 5000.01, DoDI 5200.39, and DoDI 5000.02. The contractor shall establish, implement and maintain the requirements IAW the provisions of DoD 5200.1-M.

The contractor shall protect the system against compromising security requirements in accordance with Assessment and Authorization (A&A), Information Security, Emulation Security, Communication Security, Operational Security, Computer Security, Physical Security, and Procedural Security, as outlined in National Institute of Standards and Technologies (NIST) Special Publication (SP) 800-53Ar4, Air Force Manual (AFMAN) 33-282, and AFMAN 33-283.

3.8 Cybersecurity (CS)

The contractor shall assist creating, documenting, and implementing a Cybersecurity Program to ensure compliance with DoDI 8500.01: Cybersecurity, DoDI 8510.01: Risk Management Framework (RMF) for DoD Information Technology (IT), and AFI17-130 Air Force Cybersecurity Program Management. The contractor shall incorporate Cybersecurity requirements into all JTC TRS and JTAGSS simulator configuration components.

The contractor shall identify system vulnerabilities and mitigations and/or risk reduction strategies for those vulnerabilities to include Security Technical Implementation Guides (STIGs) in accordance with Defense Information System Agency (DISA).

The contractor shall accomplish the Cybersecurity Program relative to the current classification of the system beginning at program inception and support planned changes throughout the life of the program. JTC TRS program includes: (1) Dome, (2) desktop and (3) portable and (4) JTAGSS enclaves.

The contractor shall plan, design, develop/build, test, deploy and sustain all system products and conduct activities in accordance with Federal, Committee on National Security Systems (CNSS), Department of Defense (DoD), and Air Force (AF) Cybersecurity policy, guidance, and standards.

The system shall comply with the most recent versions as of the contract date. Federal-level cybersecurity policy is contained within:

• National Institute of Standards and Technology (NIST) 800-series Special Publications (SP), http://csrc.nist.gov/publications/PubsSPs.html.

• CNSSI 1253, https://www.cnss.gov/CNSS/issuances/Instructions.cfm, provides system categorization and security control selection guidance mandated by DoD policy for all DoD systems.

• DoD Cybersecurity policy and guidance is contained within 8500-series publications, http://www.dtic.mil/whs/directives/.

• The DoD Information Assurance Technology Analysis Center (IATAC) IA Policy Chart, available at http://iac.dtic.mil/iatac/ia_policychart.html, also provides a useful resource.

• AF Cybersecurity policy and guidance is contained within 33-series publications, available at http://www.e-publishing.af.mil/.

The contractor shall provide system artifacts to support Assess and Authorization (A&A) of the system.

The contractor shall comply with Authorizing Official (AO) specific instructions as directed by the Government. AO specific instructions include device vulnerability scanning, device compliancy scanning, device virus scanning, and registration of system controls into an automated information system for A&A. The specific scanning tool is Assured Compliance Assessment Solution (ACAS) (fully accredited), and the current automated certification and accreditation database for the documentation of security controls is the AF Enterprise Mission Assurance Support Service (eMASS) (IAW AFI 17-130). Changes to AO specific instructions shall be directed by the Government.

[A026, DI-MGMT-82001/T, DoD Risk Management Framework (RMF) Package Deliverables]

3.8.1 Cybersecurity Staffing

The contractor shall manage personnel IAW DoD 8570.01M and AFM 17-1303 and comply with DFARS 252.239.7001 and all cybersecurity requirements stipulated in the contact. Individuals shall possess a DoD-approved cybersecurity baseline certification commensurate to category and level of the assigned position. DoD-approved listing can be found at this link:

https://public.cyber.mil/cw/cwmp/dod-approved-8570-baseline-certifications/

The contractor shall obtain and maintain security clearances within 90 days of contract award for personnel assigned to perform these tasks (for example ISSO). DD Form 254, Contract Security Classification Specification, is applicable. The contractor shall be responsible for determining the number of SECRET billets required and all personnel requiring a SECRET clearance. This information shall be made available to the Government upon request.

3.8.1.1 Information Systems Security Engineer (ISSE)

The contractor shall assign an ISSE as the lead cybersecurity analyst for this contract. The ISSE shall be responsible for tracing security controls to the actual systems security requirements as documented and derived from security controls. The ISSE shall capture and refine information security requirements and ensure the requirements are effectively integrated into all JTC TRS and JTAGSS training device configurations through security architecting, design, development and configuration. The ISSE shall reference the RMF, DoDI 5000.02 and NIST SP 800-160 for systems engineering information and processes in relation to cybersecurity. The ISSE shall complete training and maintain certification IAW AFI 17-303 and be qualified IAW DoD 8570.01-M.

[A026, DI-MGMT-82001/T, DoD Risk Management Framework (RMF) Package Deliverables]

3.8.1.2 Information System Security Officer (ISSO)

The contractor shall assign an Information Systems Security Officers (ISSO) responsible for all aspects of Cybersecurity (CS)/security management for the systems. The ISSO shall obtain and maintain a SECRET level clearance at the start of the contract.

a. The ISSO shall meet the minimum requirements, certifications, and job duties of IAM- Level I as defined in DoDD 8570.01. Contractor personnel must be certified upon “Day-1” assignment of CS duties. Those who fail to maintain their certified status will not be permitted to carry out the responsibilities of the position. The contractor shall maintain copies of Cybersecurity personnel certifications at their facility, and make copies of the Cybersecurity personnel certifications available for upload to the system accreditation package IAW AFMAN 17-1303, CYBERSECURITY WORKFORCE IMPROVEMENT PROGRAM. Any lapses in certification requirements shall be reported to the Government.

b. The ISSO shall develop, implement, update and maintain CS System Security Plans (SSP) in conjunction with the Government and Program Management Office (PMO) Information Systems Security Manager (ISSM) to include: systems operating processes and procedures documents (e.g., password management plan); information system Architectural Analysis; and CS Accreditations.

The ISSO shall identify and document the NIST SP 800-53A controls applicable to each system, and work with the ISSM to develop security processes for each JTC TRS and JTAGSS training device configuration.

[A041, TM-86-01P /T, Technical Manual Contract Requirements]

c. The contractor shall assist the PMO ISSM in annual…