Attch 01 GTS SOW.pdf

Statement of Work for the

Gunnery Training Systems (GTS) – Base Tech Refresh, Concurrency, and Production

Version 1.0

Prepared by

U.S. Army Program Executive Office for Simulation, Training, and Instrumentation

(PEO STRI)

and Program Manager Training Systems (PM TRASYS)

12211 Science Drive

Orlando, FL 32826-3276

Engineering Prepared By: ____________________ Concurrence: ____________________ Trudy Ryan Jeff Meister Lead Systems Engineer Chief Engineer, PdM VTS

Date: _________ Date: __________

Acquisition Logistics Prepared By: ____________________ Concurrence: ____________________ Miguel Carrion Matthew Brothers Logistics Management Specialist Product Support Manager

PM ST

Date: __________ Date: __________

Program Management Submitted By: ___________________ Approved By: ____________________ Scott Turner LTC Edgar Santana Assistant Product Manager Product Manager Gunnery Training Systems Virtual Training Systems

Date: __________ Date: _________

SOW-2019-0020

W900KK-21-R-0055

26 January 2021

Revision Number Date Log of Changes Made and

Description of Reason Changes Approved By

1.0 26 January 2021 Initial Release

26 January 2021

TABLE OF CONTENTS

1 SCOPE

1.1 Introduction

1.2 Goals and Objectives

1.3 Background

2 APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 Non-Government Documents

3 REQUIREMENTS

3.1 Program Management

3.1.1 Integrated Master Plan (IMP)

3.1.2 Integrated Master Schedule (IMS)

3.1.3 Financial Management

3.1.3.1 Earned Value Management

3.1.3.2 Integrated Baseline Review

3.1.4 Product Line Management and Processes

3.1.5 Configuration Management

3.1.5.1 Configuration Management Planning and Management

3.1.5.2 Configuration Identification

3.1.5.3 Configuration Change Management

3.1.5.4 Configuration Status Accounting

3.1.5.5 Configuration Verification and Audit

3.1.5.6 Contractor Internal Hardware Build-Up Audit

3.1.5.7 Government Sample Audit to Verify Product Baseline

3.1.5.8 Physical Configuration Audit (PCA)

3.1.5.9 Software Configuration Management

3.1.5.10 Software Configuration Control Board

3.1.5.11 Software Item Database

3.1.5.12 Systems Engineering Interface

3.1.5.13 Engineering Change Proposals (ECP)

3.1.5.14 Engineering Change Proposal Review

3.1.5.15 Variances

26 January 2021

3.1.6 Technical Performance Measures (TPM)

3.1.7 Risk Management

3.1.8 Management Reviews and Subcontractor Management

3.1.8.1 Post Award Conference (PAC) / Start of Work Meeting

3.1.8.1.1 PAC Entrance Criteria

3.1.8.1.2 PAC Exit Criteria

3.1.8.2 Program Management Reviews (PMR)

3.1.8.3 Integrated Product Team (IPT) Meetings

3.1.8.4 Technical Interchange Meetings (TIMs)

3.1.9 Visitor Support

3.1.10 Subcontractor Management

3.1.11 Obsolescence Management

3.1.12 Data Rights

3.1.13 Government Furnished Information (GFI)

3.1.14 Government Furnished Equipment (GFE)

3.1.15 Security

3.1.15.1 Controlled Unclassified Information (CUI)

3.1.15.2 Security Training

3.1.15.2.1 Threat Awareness Reporting Program (TARP)

3.1.15.2.2 Operations Security (OPSEC) Awareness Training

3.1.15.2.3 Insider Threat Training

3.1.15.2.4 DOD Annual Security Awareness Refresher Training

3.1.15.2.5 CUI Training

3.1.15.2.6 Unauthorized Disclosure of Classified Information for DOD & Industry 31

3.1.15.2.7 Anti-Terrorism (AT) Awareness Training for Contractor Personnel Traveling Overseas

3.1.15.2.8 AT Level I Awareness Training

3.1.15.2.9 iWATCH Training

3.1.15.2.10 Cybersecurity (CS) Information Technology (IT) Training and Certification

3.1.15.3 Access and General Protection Policy and Procedures for Contractor Requiring Common Access Card (CAC)

3.2 Systems Engineering

26 January 2021

3.2.1 System Design

3.2.1.1 System Definition Phase

3.2.1.2 Preliminary Design Phase

3.2.1.3 Detailed Design Phase

3.2.1.4 Fabrication, Assembly, Integration and Test Phase

3.2.2 Hardware Engineering

3.2.2.1 Hardware Requirements and Review

3.2.3 Software Engineering

3.2.3.1 Software Requirements and Architecture Development and Review

3.2.3.2 Software Design and Implementation

3.2.3.3 Software Development Test

3.2.3.4 Software Integrity Certification

3.2.4 Hardware and Software Integration

3.2.5 Cybersecurity (CS)

3.2.5.1 Cybersecurity Artifacts

3.2.5.2 CS Control Review/RMF Package

3.2.5.3 Security Control Assessment (SCA) Readiness Review

3.2.5.4 SCA Event

3.2.5.5 Information Assurance Vulnerability Management Program (IAVMP) .. 43

3.2.5.6 Information Assurance Contractor Training and Certification

3.2.6 Specialty Engineering

3.2.6.1 Security Engineering

3.2.6.2 Reliability, Availability and Maintainability (RAM) Engineering

3.2.6.3 Safety Engineering

3.2.6.4 Health Hazard Assessment

3.2.6.5 Producibility Engineering

3.2.6.6 Quality Engineering

3.2.6.6.1 Test Discrepancies

3.2.6.6.2 Test Discrepancy Processing

3.2.6.6.3 Test Discrepancy Severity

3.2.6.6.4 Quality Control

3.2.6.7 Human Factors Engineering

26 January 2021

3.2.6.8 Electromagnetic Environmental Effects (E3)

3.2.6.9 Contaminate and Corrosion Control

3.2.6.10 Standardization

3.2.6.11 Integration of Third Party Products

3.2.7 Design Reviews

3.2.7.1 System Requirements Review (SRR)

3.2.7.1.1 SRR Entrance Criteria

3.2.7.1.2 SRR Completion/Exit Criteria

3.2.7.1.3 SRR Products

3.2.7.2 Preliminary Design Review (PDR)

3.2.7.2.1 PDR Entrance Criteria

3.2.7.2.2 PDR Completion/Exit Criteria

3.2.7.2.3 PDR Products

3.2.7.3 Critical Design Review (CDR)

3.2.7.3.1 CDR Entrance Criteria

3.2.7.3.2 CDR Completion/Exit Criteria

3.2.7.3.3 CDR Products

3.2.8 Product Definition Data (PDD)

3.2.8.1 Maintenance Services

3.3 Logistics

3.3.1 Logistics Product Data (LPD)

3.3.1.1 Initial Spares

3.3.2 Technical Manuals

3.3.2.1 Operator Manual

3.3.2.2 System Maintenance Manual (SMM)

3.3.2.3 Commercial Off-The-Shelf (COTS) Manuals

3.3.2.4 Technical and COTS Manual Validation

3.3.2.5 Technical Manual Verification

3.3.3 Item Unique Identification (IUID)

3.3.4 Software Support Environment

3.3.5 Training

3.3.5.1 New Equipment Training (NET)

26 January 2021

3.3.5.2 Senior Instructor/Operator Training

3.3.5.3 Instructor/Operator Training

3.3.5.4 Maintenance Training

3.4 Interim Contractor Support (ICS)

3.5 Integrated Testing

3.5.1 Test Readiness Review (TRR)

3.5.1.1 TRR Entrance Criteria

3.5.1.2 TRR Exit Criteria

3.5.2 In-Plant Acceptance Test (IPAT)

3.5.3 Cybersecurity Compliance

3.5.4 Operational Test Support

3.5.5 Production Qualification Test (PQT)

3.5.6 Baseline System Test

3.5.7 On-Site Acceptance Test (OSAT)

3.6 Site Activation

3.6.1 Site Survey

3.6.2 Site Preparation

3.6.3 Installation Tools and Test Equipment

3.6.4 Installation Spares

3.6.5 Removal of Equipment

3.7 System Technical Support

3.8 Outside the Continental United States (OCONUS)

Travel

3.9 Specific Requirements

26 January 2021

1 SCOPE

The U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI), Project Manager Soldier Training (PM ST) and Product Manager Virtual Training Systems (PdM VTS) intend to retrofit, procure, develop, integrate, produce, test, refresh hardware/software, support Risk Management Framework (RMF) certification/ recertification, and upgrade capabilities for the Gunnery Training Systems (GTS) in support of Marine Corps Systems Command (MARCORSYSCOM), Program Manager Training Systems (PM TRASYS), Forces Command (FORSCOM), Training and Doctrine Command (TRADOC), and United States Marine Corps (USMC) Training and Education Command (TECOM). The initial list of efficiencies expected include hardware/software reuse and commonality, common architectures and standards, reduction of development and sustainment costs, acquisition streamlining and reduction of development time, and inherent agility to react to platform changes.

1.1 Introduction

The single award contract for GTS will incorporate an Indefinite Delivery/Indefinite Quantity (ID/IQ) delivery order approach in support of the tasks described above. This SOW defines the general tasks that PdM VTS desires to have performed under the GTS ID/IQ contract. PdM VTS envisions management, development, and evolution of the GTS assets under the GTS ID/IQ contract. Individual delivery orders (DOs) will define the detailed requirements in each respective DO SOW.

The GTS contract facilitates the development, evolution, and maturity of the GTS program’s products and capabilities across the Army’s/Marine Corps’ virtual gunnery training systems total life cycle. The GTS contract will ensure program relevancy via a consolidated, streamlined approach that protects, leverages, and matures the GTS investment while supporting Army/Marine Corps modernization efforts. The GTS contract will provide efficient, effective, and agile processes to accomplish production, tech refresh, fielding, obsolescence management, concurrency, upgrades, and disposal of legacy and obsolete hardware as needed. The Contractor shall ensure the following:

a. Elimination of duplication across development and sustainment efforts

b. Maximum reuse of existing training system subsystems to include:

• Visual training environment (terrain databases, moving models, special effects and animations)

• Aural training environment (aural cues and inter/intra-vehicle communication)

• Exercises

• Scoring

• Training management system

• Trainer usage data

• Instructional subsystem

• Graphical User Interface (GUI)

26 January 2021

• Input/Output subsystem (I/O)

• Common Software Libraries (CSL)

• Computer Generated Forces (CGF)

• Linking subsystem

c. Utilize the latest version of the existing Scalable Advanced Graphics Engine

(SAGE) Real Time Software (RTS) interface in order to avoid cost related to modifications of the existing training environment and exercises

d. Update to appropriate blue force tracking systems

e. Achieve a high degree of hardware commonality and reuse when possible

f. Use of a consistent set of tools and processes across the GTS DOs

g. Increase of technology agility

h. Update operating systems (OS) to latest approved versions

i. Support RMF certification

1.2 Goals and Objectives

The objective of the GTS ID/IQ is to integrate new technologies across existing legacy systems’ computational components as well as optimize development, production, obsolescence planning, performance, and operational readiness, while reducing total ownership costs of existing systems. It is the objective of the contract to develop a hardware and software solution for GTS that maximizes standardization, commonality, and core asset reuse of current products and system components across platforms.

This effort will include dynamic mechanisms for multi-phase configuration management, development, support, and growth of all GTS.

The GTS contract should support the business goals of PdM VTS as follows:

a. Configuration management

b. Product tools & methodologies management

c. Engineering & management metrics

d. Reduce development cost & complexity

e. Integrate innovative technologies to reduce systems footprint

f. Maximize common standards and interfaces

g. Reduce life cycle support costs

26 January 2021

1.3 Background

PdM VTS and PM TRASYS have a requirement for tech refresh, concurrency upgrades, development, and production of current gunnery training simulation systems to support FORSCOM, TRADOC, and USMC TECOM requirements with training devices that support gunnery units with platform familiarization and Tactics, Techniques and Procedures (TTP), as well as sustainment of gunnery skills. This effort includes tech refresh for existing gunnery systems and the production of GTS systems. Each system shall meet or exceed its particular set of requirements as described in its respective SOW, System Specification, and all applicable documentation.

The GTS devices shall provide training for the following:

• Abrams Advanced Gunnery Training Systems (AGTS) (Tech Refresh/Upgrade/Production) M1A2 System Enhancement Package (SEP) v2 AGTS M1A2 SEP v2 AGTS Pre-Brief/After-Action Review (PAAR) M1A2 SEP v4 AGTS (as a concurrency upgrade to the M1A2 SEP v2

AGTS)

M1A1 Situational Awareness (SA) C-AGTS

M1A1 SA C-AGTS PAAR

• Bradley Conduct of Fire Trainer (COFT) (Tech Refresh/Upgrade)

• Stryker Mobile Gun System (MGS) AGTS (Tech Refresh/Upgrade/Production)

Stryker Mobile Gun System AGTS Pre-Brief/After Action Review (PAAR)

• USMC Light Armored Vehicle-25 (LAV-25) AGTS (Tech

Refresh/Upgrade/Production)

USMC LAV-25 PAAR

The GTS are virtual gunnery training simulators that shall provide initial familiarization training, skills progression, and sustainment training that fulfill Gunnery training requirements for wheeled and tracked vehicles. The GTS shall provide capabilities that allow students to become familiar with the actual platform instrumentation including sensors, switches, and various terrain, environmental, and visibility conditions.

Through the selection of scenarios, GTS shall train soldiers’ physical and mental skills critical for successfully winning battles under any condition. The GTS shall permit the Instructor/Operator to monitor soldier gunnery performance and soldier reactions to complex progression scenarios, to include randomly induced malfunctions through gunnery skill progression.

The GTS devices shall allow for training gunnery tasks including individual, crew, and collective tasks up to platoon level or higher as required in the applicable DO SOW.

Systems that require PAAR support shall allow the PAAR Instructor/Operator to monitor exercises via a 2D Plan View Display (PVD) and 3D displays to view any vehicle in the exercise, communicate, and attach the 3D display eye point to a selected vehicle in accordance with the applicable DO SOW. The PAAR shall support free eye point

26 January 2021 movement/teleportation to any location in the visual databases. CGF shall be provided to support section and platoon free play exercises. PAAR capabilities shall be implemented as required by the applicable DO SOW and system requirements documentation.

2 APPLICABLE DOCUMENTS

The following documents are applicable to this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of the SOW will be the governing requirement.

2.1 Government Documents

29 CFR 1910 Occupational Safety and Health Administration (OSHA) Regulations OSHA 1910, Subpart S Electrical (Copies of the above regulations are available from (http://www.osha.gov))

29 CFR 1910.119 Code of Federal Regulations (CFR), 29 CFR 1910

Occupational Safety and Health Standards (OSHA standards are downloadable from (http://www.osha.gov))

29 CFR 1910.1200 Occupational Safety and Health Standards Toxic and hazardous Substances

Army Directive 2014-05 Policy and Implementation Procedures for CAC

Credentialing and Installation Access for Uncleared Contractors

AR 25-2 Army Cybersecurity

AR 190-13 The Army Physical Security Program

AR 380-5 Army Information Security Program

AR 380-10 Foreign Disclosure and Contacts with Foreign

Representatives

AR 380-49 Industrial Security Program

AR 381-12 Threat Awareness and Reporting Program

AR 530-1 Operations Security

26 January 2021

AR 525-13 Antiterrorism

AR 525-28 Personnel Recovery, dated 5 March 2010

DFARS 252.225.7040 Contractor Personnel Supporting U.S. Armed Forces

Deployed Outside the United States

DFARS 252.225.7043 Antiterrorism/Force Protection for Defense Contractors outside the US

DFARS 252.239-7001 Information Assurance Contractor Training and

Certification

DOD 4500.54G DOD Foreign Clearance Guide

DODM 5200.01, Vol. 3 DOD Information Security Program: Protection of

Classified Information

DODI 5200.48 Controlled Unclassified Information (CUI)

DOD 5220.22-M National Industrial Security Program Operating Manual

DODM 5220.22, Vol. 2 National Industrial Security Program: Industrial Security

Procedures for Government Activities

DODD 8140.01 Cyberspace Workforce Management

DODI 8500.01 Cybersecurity (CS)

DODI 8510.01 Risk Management Framework for DOD Information

Technology

DOD 8570.01-M

Information Assurance Workforce Improvement Program

DODI 8582.01 Security of Unclassified DOD Information on Non-DOD

Info Systems

EM 385-1-1 Department of Army Manuals, US Army Corp of

Engineers Safety and Health Requirements Manual 2014 (Manual is downloadable from (www.usace.army.mil/CESO/Pages/EM385-1-1.aspx)).

FAR clause 52.204-9 Personal Identity Verification of Contractor Personnel

FIPS 140-2 Federal Information Processing Standards (FIPS)

Publication 140-2 Security Requirements for Cryptographic Modules

LT2-TRADE_PLAN-2013-

00009

Live Training Transformation (LT2) Product Line Configuration

LT2-TRADE-PLN-000384 Live Training Transformation (LT2) Operations Guide

(Version H)

MIL-DTL-24784C Manuals, Technical: General Acquisition and

Development Requirements, General Specification For - Revision C

MIL-HDBK-1222 Guide to the General Style and Format of U.S. Army

Work Package Technical Manuals

MIL-PRF-29612B Training Data Products Performance Specification

MIL-PRF-32216A Evaluation of Commercial Off-the-Shelf (COTS)

Manuals and Preparation of Supplemental Data Performance Specification

MIL-STD-130N Identification Marking of U.S. Military Property

MIL-STD-1472 Department of Defense (DOD) Design Criteria Human Engineering

MIL-STD-40051-2C Preparation of Digital Technical Information for Page-

Based Technical Manuals

MIL-STD-31000B Technical Data Packages

SEP-2019-011 Systems Engineering Plan (SEP) for Gunnery Training

Systems (GTS), Version 1.0

TRADOC Regulation 350-70 Training, Army Learning Policy and Systems

2.2 Non-Government Documents

26 January 2021

Program unique documentation as specified in each DO’s SOW

ANSI/EIA-748 Earned Value Management

CNSSI 1253F Committee on National Security Systems Instruction (CNSSI)

GEIA-HB-0007-B Logistics Product Data Handbook

GEIA-STD-0007-B Logistics Product Data

IEEE STD 12207-2017 IEEE Standard Systems and software engineering -- Software life cycle processes

NFPA 70 National Fire Protection Association (NFPA 70 National

Electrical Code, 2017 Edition (Copies of this document are available from (http://www.nfpa.org/Catalog/) or National Fire Protection Association, 11 Tracy Drive, Avon, MA 02322)

NIST SP 800-53 National Institute of Standards and Technology (NIST) Special

Publication (SP) 800-53: Security and Privacy Controls for Federal Information Systems and Organizations

NIST SP 800-171 Protecting Controlled Unclassified Information in Nonfederal

Systems and Organizations

TA-HB-0007-1 Tech America Logistics Product Data Reports Handbook

3 REQUIREMENTS

The GTS Contractor shall provide efficient, effective, and agile processes to accomplish development of GTS devices and their variants, production, fielding, tech refresh, obsolescence management, concurrency upgrades, support embedded training, and disposal of legacy, obsolete hardware as needed. The requirements defined herein shall form the basis for all work performed as part of the DOs the Government will issue under the GTS ID/IQ contract. Each DO will specify the tasks performed as derived from the GTS ID/IQ contract base SOW.

Tech Refresh:

The Contractor shall procure, design, develop, fabricate, integrate, test, validate, deliver, and install tech refreshes on existing GTS units. Tech refresh shall conform to all CS requirements. Tech Refresh shall utilize the latest version of legacy system

26 January 2021 software (e.g. Common Software Libraries, Host software, visual environment, training management, exercises, etc.). HW designs shall meet or exceed all requirements identified in the individual DO GTS Specifications.

Production:

The Contractor shall procure, design, develop, fabricate, integrate, test, validate, deliver, and install current GTS simulators to be concurrent with the tactical vehicle capabilities as defined in individual DO SOWs and requirements documentation. The simulators shall meet or exceed all requirements identified in the individual GTS Specifications and System Requirements Documents (SRD) as applicable.

Concurrency Upgrades:

The Contractor shall procure, design, develop, fabricate, integrate, test, validate, deliver, and install concurrency upgrades to the existing GTS simulators to be concurrent with the tactical vehicle capabilities, as defined in individual DO SOWs and requirements documentation. The concurrency upgrades shall meet or exceed all requirements identified in the individual GTS Specifications and SRDs as applicable.

RMF Recertification:

As specified in each applicable DO, the Contractor shall assist and support Government RMF CS activities to recertify the system for the Authority to Operate (ATO). RMF recertification will be on a three (3) year cycle after the respective RMF certification.

As specified in each DO, the Government will identify the tech refresh, concurrency upgrades, legacy system production, and/or RMF recertification requirements.

3.1 Program Management

The Contractor shall provide the overall management and administrative effort necessary to ensure the requirements of this contract are accomplished. The Contractor shall track program progress utilizing metrics. The Contractor shall consider life cycle costs while conducting trade studies and evaluating design alternatives. The Contractor shall define and monitor metrics and Technical Performance Measures (TPMs) to evaluate each critical technical and management process and the conformance of evolving products with contract, cost requirements, and objectives. The Contractor shall identify progress, issues, and status of the program. The Contractor shall identify problem areas and corrective actions required to eliminate or reduce schedule impacts. The Contractor shall, at a minimum, report the following:

a. Problems and solutions

26 January 2021

b. Time-lines and schedules

c. Plan of next month activities

d. Development and fabrication progress

e. Expenditures to date and cost projections

(DI-MGMT-80227) Contractor's Progress, Status, and Management Report

3.1.1 Integrated Master Plan (IMP)

The Contractor shall implement, manage to, update, and maintain the contract IMP.

The Contractor shall develop the system in accordance with the IMP. The IMP shall be used throughout the contract as a management tool to assess progress and determine success in achieving program requirements. The Contractor shall report on work in progress in accordance with the IMP at each program review, at selected technical reviews, and at government discretion. The IMP shall depict the contract work breakdown structure.

3.1.2 Integrated Master Schedule (IMS)

The Contractor shall develop, implement, manage to, update, and maintain the contract IMS. All contract schedule information delivered or presented at program reviews shall originate from the IMS, shall be traceable to the IMP, and shall contain all critical events and exit criteria, accomplishments, predecessors and successors events, and their dependencies. The IMS shall address total program activities including activities performed by major subcontractors. The Contractor shall develop the logic resource loaded network that accurately portrays the sequence and relationship of activities defining the total program. These network activities shall be keyed to the Contract Work Breakdown Structure (CWBS). The network shall be implemented on a computer based program management control system which utilizes critical path method network analysis, accepts parametric data input, and can be utilized to determine a probabilistic estimate of the program schedules and cost for reporting project progress. The network activities time and cost data shall be updated to reflect accomplished activities and any changes in activity time and cost estimates. The Contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

(DI-MGMT-81861A) Integrated Program Management Report (IPMR) Integrated Master Schedule (IMS) Format 6

3.1.3 Financial Management

The Contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The Contractor shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations and invoices against each contract line item and subline item. The Contractor shall extend the government-provided Program Work Breakdown Structure

26 January 2021

(PWBS) to lower levels in the Contractor’s CWBS. It defines the lower level components of what is to be procured and includes all the product elements (hardware, software, data, or services), which are defined by the Contractor and the Contractor’s responsibility. The extended CWBS shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status. The Contractor shall identify major elements of subcontracted work in the extended CWBS. The Contractor may propose changes to the CWBS to enhance its effectiveness in satisfying program objectives. The Contractor shall continually update an integrated database during contract performance with pertinent records and data that underlie and support the cost and schedule data reported.

(DI-MGMT-81468) Contract Funds Status Report (CFSR) (DI-MGMT-81651) Contract Invoicing and Payment Report

3.1.3.1 Earned Value Management

The Contractor shall integrate cost, schedule, and performance management information. The Contractor shall develop, implement, maintain, and use an EVM system that complies with Industry Guidelines ANSI/EIA-748 and meets contractual requirements. The Contractor shall document the integrated cost and schedule status of work progress on the contract and relate technical performance with cost and schedule accomplishment using procedures for planning work, controlling costs, and measuring performance based on ANSI/EIA-748.

(DI-MGMT-81861A) Integrated Program Management Report (IPMR) Format

3.1.3.2 Integrated Baseline Review

The Contractor shall participate with the government in the assessment of program risk and the degree to which the following have been established:

a. Technical scope of work is fully included and is consistent with authorizing documents

b. Project schedule key milestones are identified and supporting schedules reflect a logical flow to accomplish the work

c. Resources (budget, facilities, personnel, skills, etc.) are available and are adequate for the assigned tasks

d. Tasks are planned and can be measured objectively relative to the technical progress

e. Rationales underlying the review are reasonable

f. Management processes support successful execution of the project

26 January 2021

3.1.4 Product Line Management and Processes

The Contractor shall implement a GTS product line that will allow for development, production, fielding, concurrency upgrades, obsolescence management, and evolution/improvement of currently fielded systems for platforms operating within the GTS product line life cycle support framework. The initial list of efficiencies expected from the new GTS product line implementation include hardware/software reuse and commonality, common architectures and standards, reduction of development and sustainment costs, acquisition streamlining and reduction of development time, and inherent agility to react to platform changes. The ultimate end goal of this effort is to develop a single common hardware/software/documentation baseline for all GTS devices.

All GTS software, digital information, and documentation will reside on the Live Training Transformation (LT2) portal. The LT2 portal is an Army repository for data and standards for the training community created under the CPMNext contract. Information uploaded by the Contractor onto the LT2 portal may be available to other Contractors on a need to know basis to perform work for the Army. The Contractor shall provide a plan that documents a path to conformance with the LT2 Product Line Operations and CM Guide. The LT2 portal and guides are located at (https://www.lt2portal.mil/). A Common Access Card (CAC) is required to access the LT2 CM repositories.

3.1.5 Configuration Management

The Contractor shall use an automated internal configuration management process to monitor, update, and control all configuration documentation, physical media, and physical parts representing or comprising the system configuration items (CIs). The Contractor shall plan and implement an automated configuration management function to perform configuration control, configuration identification, audits, and status accounting in a system engineering environment. The Contractor shall develop, maintain, and update configuration management procedures and processes for control of all hardware and software baselines. The process shall allow simultaneous access to the common product data model coupled with the ability to coordinate and update immediate changes to the product definition data. The configuration management process must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant events. The Government will maintain control of the functional baseline (FBL) defined by the system performance specification, interface control documents, and software requirement specifications.

(DI-SESS-80858C) Supplier’s Configuration Management Plan

3.1.5.1 Configuration Management Planning and Management

The Contractor shall establish processes and tools to establish and maintain consistency between system requirements, system configuration information, and all relevant information about the system. The configuration management process shall http://www.lt2portal.mil/

26 January 2021 include changes made to the Cybersecurity (CS) configuration and associated documentation. The Contractor shall:

a. Plan implementation of the CM functions for the context and environment in which they are to be performed and manage in accordance with the planning

b. Determine the specific CM value-adding functions and levels of emphasis

c. Document how your organization will implement CM functions to provide the consistency between the system’s attributes, system definition information and the system’s configuration information, throughout the applicable phases of the life cycle

d. Identify resources required to implement the CM functions and ensure they are applied throughout the system’s life cycle

e. Assess the effectiveness of CM plan implementation and performance of the configuration management functions with performance measurements

f. Flow down responsibility for CM performance to subcontractors

g. Plan and identify information status levels for managing system configuration information and ensure that transmitted data products are usable

3.1.5.2 Configuration Identification

The Contractor shall identify unique identifiers for selected system attributes, system information and components to be used as the basis for configuration management.

The Contractor shall:

a. Define the functional, performance, interface and physical attributes of the system and components

b. Determine the systems composition using its product definition information

c. Assign unique identifiers to configuration items so that they can be distinguished from other items, one configuration of the system can be distinguished from another, the source of a component can be determined, and the correct system definition information can be retrieved

d. Assign unique unit identifiers to individual components of the system

e. Update component identifiers when a system is modified reflecting the new configuration without altering the system identifier and model identifier

f. Uniquely identify information so that it can be correctly associated with the applicable configuration of the system

g. Apply information identification rules to maintain representation and version relationships

h. Maintain relationships between information, information requirements, and the related system configuration to ensure accurate information retrieval

i. Establish complete, valid, and suitable for use agreed-to descriptions of the attributes of the system and components at a point in time and provide a known configuration to which changes can be addressed

26 January 2021

j. Identify interfaces and establish mutually agreed-to control of common attributes for system or component boundaries that interface to the system or within the system

3.1.5.3 Configuration Change Management

The Contractor shall establish a systematic and measurable configuration change management process for managing product configuration changes and variances.

Once the system requirements have been approved by an authorized management activity, the Contractor shall effect changes to the baseline requirements only after the proposed change has been approved using the change process. The Contractor shall:

a. Document and uniquely identify each change

b. Classify requested changes to aid in determining the levels of review and approval

c. Clearly and completely document request for change

d. Consider the technical, support, schedule, and cost impacts of a requested change before making a judgment to approve the change for implementation and incorporation in the system and its documentation

e. Determine potential effects of a change and coordinate impacts with the impacted areas of responsibility

f. Determine the effectivity for each change and identify which units of the system are to be changed, the point of production break-in, and which units will be included in a retrofit

g. Verify implementation of a change to ensure consistency between the system, its documentation, and its support elements

h. Document variances, when authorized by the appropriate level of authority

3.1.5.4 Configuration Status Accounting

The Contractor shall provide access to accurate, timely information about the system and its documentation through the integrated database. The Contractor shall correlate, store, maintain, and provide readily available views and information of system configuration information including pending, current and historical data. The Contractor shall:

a. Systematically record, safeguard, validate, and disseminate system information

b. Establish methods, processes and procedures to provide controlled access to system information

c. Capture configuration information as it evolves

26 January 2021

3.1.5.5 Configuration Verification and Audit

The Contractor shall verify and audit the system configuration information to ensure that requirement attributes are met and accurately documented. The Contractor shall:

a. Verify the system attributes through a systematic comparison with the associated results of system tests, analyses, inspections, demonstrations or simulation models

b. Maintain surveillance over the configuration management process to ensure it is being followed and remains in compliance with requirements

3.1.5.6 Contractor Internal Hardware Build-Up Audit

Concurrent with manufacture of piece parts and incoming inspection of procured parts, a 100% audit shall be conducted by personnel approved by the QA Manager to verify the as-built configuration matches the design documentation prior to use of each part in production. During this process each product definition document will also be examined for proper format (compliance with American National Standards Institute (ANSI) Y14 series standards), completeness, currency of material references, accuracy of piece part identification, and adequacy of manufacturing instructions and any other information critical to acquire a like part. A record of each product attribute verified shall be maintained and available through the LT2 documentation repository.

3.1.5.7 Government Sample Audit to Verify Product Baseline

After completion of acceptance testing and any required design modifications, but prior to formal acceptance, the final product baseline shall be verified by the government by reviewing a representative number of drawings, associated technical manuals, logistics management information and manufacturing instructions to determine their accuracy in accordance with the final product configuration design.

3.1.5.8 Physical Configuration Audit (PCA)

The Contractor shall support the Government in conducting the PCA by providing the necessary space, tools, equipment, personnel, and documentation required for the activity. The PCA is the formal technical examination of the system “as-built” configuration against its technical documentation to establish or verify the configuration item’s product baseline. It is used to examine the actual configuration of each item (down to the lowest level of repair) in order to verify that the related design documentation matches the physical configuration. The PCA addresses accuracy of the documentation to include inspection of inventory/equipment lists, logistics product data, documentation, drawings, spares and all manuals. The documentation and equipment shall be examined to verify that all applicable safety labels along with incorporating applicable warnings are incorporated.

26 January 2021

In addition to the PCA, the Contractor shall provide the necessary space, tools, equipment, personnel, and documentation required for the Government to perform the inspection of the complete system inventory. Each item shall be inspected to ensure Government property sticker is affixed in a prominent location.

a. Verification of Serial number and Item Unique Identification (IUID). All items requiring an IUID marking, per contractual guidance, shall be marked with an IUID label that is constructed of a material designed to last the life of the item/system in its intended environment and operation. The IUID data shall be entered into the central registry for accountability/visibility

b. Equipment Inventory Records (EIR) for Government property accountability, Government specified format and data elements are accurate. Equipment record shall contain the following data: Complete Item Description, Original Part Number, National Stock Number (NSN), Serial Number, Quantity, Vendor Name, Vendor Point of Contact (POC), and Warranty Period

c. Cable naming, source, destination, and numbering details are on both ends of the wiring

The Contractor shall correct all discrepancies found by the Government during verification of the “as-built” drawings. The drawings shall include complete system level drawings of all equipment, wiring, network topology, and system architecture. Drawings shall either be new or revised with changes incorporated.

(DI-SESS-81022D) Configuration Audit Summary Report (Physical) (DI-SESS-81646B) Configuration Audit Plan (Physical)

3.1.5.9 Software Configuration Management

The Contractor shall establish and document a software configuration management process. The Contractor’s software configuration management plan may be incorporated into the software development process plans or may be a separate configuration management plan.

3.1.5.10 Software Configuration Control Board

The Contractor shall establish and maintain a software configuration control board or equivalent responsible for configuration control of its software configuration items and related software products. The software configuration control board will be responsible for COTS (including open source) management including product and version identification. The Contractor shall obtain approval of the system engineering IPT prior to committing to use any version of any COTS product. The Contractor shall ensure that all COTS products included in the system deliverable configuration are commercially supported.

26 January 2021

3.1.5.11 Software Item Database

The Contractor shall capture software design data in an integrated database. The Contractor shall develop software item data to populate the software database. The software item database shall have the capability to establish, modify, make available, and maintain the integrity of the database. The Contractor shall maintain the system software item database until transition to the Government.

A schema shall be developed for identification of software items and their versions. The Contractor shall perform the following: identification and recording of change request, analysis and evaluation of the changes; approval or disapproval of the request, and implementation, verification, and release of the modified software item. The database shall contain an audit trail whereby each modification, the reason for the modification, and authorization of the modification can be traced.

3.1.5.12 Systems Engineering Interface

The process shall allow simultaneous access to the common product data model coupled with the ability to coordinate and update immediate changes to the product definition data. The configuration management system must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant events. The information architecture must permit capture of change information and notify affected team members.

3.1.5.13 Engineering Change Proposals (ECP)

The Contractor shall document and the IPT shall review all changes to established baselines and all changes to the requirements (other than the functional baseline), including changes to the statement of work, contract data requirements list (CDRL), the contract schedule, and the general provisions of the contract.

(DI-SESS-80639D) Engineering Change Proposal (ECP) (DI-SESS-80642D) Notice of Revision (NOR) (DI-SESS-80643D) Specification Change Notice (SCN) (DI-SAFT-80103C) Engineering Change Proposal System Safety Report

3.1.5.14 Engineering Change Proposal Review

In coordination with the government, the Contractor shall hold a requirements review on all proposed changes prior to the submittal of the engineering change proposal in order to clarify requirements, format, and content. Depending upon the criticality of the proposed changes, this review may take the form of a teleconference, a video-teleconference, a formal meeting at PEO STRI, or a formal meeting at the Contractor’s facility. All appropriate parties shall be in attendance in order to conduct a thorough, effective review. The Contractor shall also be responsible for generating minutes of the review and provide them to the Government for approval.

26 January 2021

(DI-ADMN-81505) Report, Record of Meeting/Minutes

3.1.5.15 Variances

The Contractor shall document the rationale and the potential impact to any DO training system and its respective variances. The Contractor shall obtain approval before varying from any government-controlled baseline.

(DI-SESS-80640D) Request for Variance (RFV)

3.1.6 Technical Performance Measures (TPM)

The Contractor shall select technical performance parameters that reflect key indicators of program success. TPM parameter inter-relationships shall be depicted through construction of tiered dependency trees similar to the specification tree. Each parameter shall be correlated with a specific CWBS element. Parameters to be reported at each management review shall be selected from the total parameters tracked and shall be identified in the integrated master plan. As the design and development activity progresses, the achievement to data shall be tracked continually for each of the selected technical performance parameters. If the data falls outside the tolerance band a new profile or current estimate shall be developed immediately. The current estimate shall be determined from the “achievement to date” and the remaining time and budget. An analysis shall be accomplished on the variation to determine the causes and to assess the impact on higher level parameters, on interface requirements, and on system cost effectiveness. For performance in excess of requirements, opportunities for reallocation of requirements and resources shall be assessed.

3.1.7 Risk Management

The Contractor shall establish and maintain a risk management program to identify risks related to the project. The Contractor shall identify and track all risks and corrective actions required to mitigate the risks. The Contractor shall define and implement a risk assessment methodology that includes not only an understanding of cost, schedule, and performance impacts on risk areas, but also provides a periodic reassessment of these impacts on risk areas. The Contractor shall update, maintain, and execute program metrics to monitor issues and to determine the likelihood of risks occurring.

The Contractor shall ensure that the risk management process is utilized to manage risks across all facets of the contract, including subcontractor activities.

(DI-MGMT-81808) Contractor Risk Management Plan (DI-MGMT-81809) Risk Management Status Report

26 January 2021

3.1.8 Management Reviews and Subcontractor Management

The Contractor shall conduct Management Reviews at the request of the Government with a minimum of one every quarter. The Government and Contractor shall mutually agree upon the review location. The Management Reviews shall provide an accurate program overview and a detailed discussion of pre-selected topics. The Contractor shall manage subcontractors and shall be responsible for the performance of subcontractors.

The Contractor shall establish an IPT structure to address major areas (e.g., systems engineering, hardware configuration, software solutions, integrated logistics support, testing). The Contractor shall establish IPT charters and host regularly scheduled IPT meetings or teleconferences. Management reviews shall use IPT meetings/teleconferences to address systems production, status of activities, questions, and issues in a timely manner. The Contractor shall prepare the meeting agendas, document action items, document due dates, coordinate resolution, and track action items until closure. Action item closure shall require Contractor and Government approval. At a minimum, the Contractor shall conduct the following meetings and reviews:

(DI-ADMN-81505) Report, Record of Meeting/Minutes (DI-MGMT-81605) Briefing Material

3.1.8.1 Post Award Conference (PAC) / Start of Work Meeting

As specified for each DO, the Contractor shall conduct a combined PAC/Start of Work Meeting held at the Contractor’s facility, at a mutually agreed upon date with the Government, within 20 working days after contract award. The purpose of the conference shall be to establish the framework of the Contractor and Government interaction during the performance period of the contract. The Contractor shall place emphasis on the operating procedures, methodologies, and processes used in the execution of the contract. The meeting shall include the Contractor’s key team members identified in the proposal with emphasis on top level management of the program, agreement on metrics used as management indicators during the program and partnering approach to implement. The Contractor shall present the program IMS, Integrated Product Team (IPT) structure, management concept, organizational structure, and the interfaces with the Government that are employed to perform the GTS mission. The Contractor shall document action items, due dates and coordinate resolution and track action items until closure.

3.1.8.1.1 PAC Entrance Criteria

The PAC entry criteria shall consist of: Government acceptance of the PAC agenda, presentation materials, and the IMS.

The PAC Agenda shall include the following:

• Introduction and Overview

• Discussion and clarification of requirements

• Program Management Plan including subcontractors

• Risk Management Process and Report

• Quality Control Program

• IMS identifying critical path, milestones, and deliverables

• CWBS

• Configuration Management Plan

• Integrated Logistic Support Overview o Revision of existing technical documentation (COTS & Technical manuals) o Parts provisioning and selection o Obsolescence management o Long lead item identification and status o Spares o Tools and test equipment (if applicable) o Warranty o Inventory (Hardware/Software) Control o Item Unique Identification (IUID) Marking Plan o Disposal of removed GTS components

• Overview of current Management Information System (MIS)

• Contract Management Plan (i.e. invoicing, billing)

3.1.8.1.2 PAC Exit Criteria

The PAC exit criteria shall consist of the following:

• Government concurrence that all required PAC agenda items have been satisfactorily presented

• Government acceptance of the PAC CDRLs

• Submittal and Government acceptance of the PAC minutes

3.1.8.2 Program Management Reviews (PMR)

The Contractor shall conduct program management reviews on a quarterly basis in accordance with the IMS. The first PMR shall be no more than 90 working days after the combined PAC/Start of Work Meeting. The Procuring Contracting Officer (PCO) and the Contractor shall mutually agree upon the location of the PMRs. The Contractor shall coordinate and provide all facilities and infrastructure for Government-Contractor meetings and separate breakout rooms for Government only meetings during the PMR.

The PMR shall provide a program overview and shall include as a minimum:

a. Hardware and software design status

b. Risk and problem identification

c. Subcontract management/progress

26 January 2021

d. Data collection and modeling

e. GTS Government Furnished Equipment (GFE) planning and status

f. Logistics planning

g. Test planning

h. Provisioning for training and technical publications status

i. Schedule status

j. Pre-selected topics of interest

k. CS status and progress (copies of all CS documents in draft format)

l. Human Factors Engineering

Status and information at the review shall reflect currency since the previous review.

When possible, other program reviews such as technical reviews, technical manual reviews, etc. shall combine into the PMR. The Contractor shall also be responsible for generating minutes of the meetings and provide them to the Government for approval.

The Contractor shall document action items, due dates, coordinate resolution, and tracking of action items until closure.

3.1.8.3 Integrated Product Team (IPT) Meetings

The Contractor shall host and participate in bi-weekly IPT meetings with Government representatives which address the full spectrum of the program concerns including system engineering, schedule, financial, integrated logistics support, CS, and testing.

The Contractor shall document and timely submit the minutes to the Government team members.

3.1.8.4 Technical Interchange Meetings (TIMs)

The…