Attachment_1_Stryker_MTS_Phase_V_SOW_2017_09_01_Rev_2.1.1

PEO-STRI-17-W016

W900KK-17-R-0016

05 09 017 Rev. 2.1 ii

Revision Number Date Log of Changes Made and Description of

Reason Changes Approved By

1.0 24 OCT 2016 DRAFT for Industry Day submittal

1.1 07 NOV 2016 DRAFT for Industry resubmittal

1.2 16 NOV 2016 DRAFT for Industry resubmittal

1.3 06 FEB 2017 DRAFT for Technical Peer Review

1.4 16 MAR 2017 Update DRAFT for Technical Peer Review

1.5 06 APR 2017 Update with Tech Peer Review comments

1.6 15 JUN 2017 Clarify SOW requirements based on industry findings

1.7 30 JUN 2017 Update to incorporate industry comments

1.8 27 JUL 2017 Update to incorporate Tech review comments

2.0 22 AUG 2017 Update to incorporate internal and Industry comments

2.1 05 SEP 2017 Update to PEO STRI Review

05 09 017 Rev. 2.1 iii

TABLE OF CONTENTS

1 SCOPE

1.1 Background

2 APPLICABLE DOCUMENTS

2.1 Department of Defense Specifications

2.2 Availability of Department of Defense (DOD) Specifications

2.3 Department of Defense Standards

2.4 Availability of Department of Defense (DOD) Standards

2.5 Department of Defense Directives

2.6 Availability of Department of Defense Directives

2.7 Department of Defense Instructions

2.8 Availability of Department of Instructions

2.9 Other Government Documents, Drawings and Publications

2.10 Availability of Non-Government Standards and Other Publications

3 REQUIREMENTS

3.1 Program Management

3.1.1 Subcontractor Management

3.1.2 Integrated Master Plan (IMP)

3.1.3 Integrated Master Schedule (IMS)

3.1.4 Financial Management

3.1.5 Configuration Management (CM)

3.1.6 Technical Performance Measures (TPM)

3.1.7 Risk Management

3.1.8 Management Reviews

3.1.9 Visitor Support

3.1.10 Integrated Digital Environment (IDE)

3.1.11 Antiterrorism (AT) Level 1 Training

3.1.12 Access and General Protection Policy and Procedures for Common Access Card

(CAC)

3.1.13 iWATCH Training

3.1.14 Operation Security (OPSEC) Program

3.1.15 Requirement for OPSEC Training

3.1.16 Cybersecurity (CS) analysis, mitigation planning, mitigation plan implementation, and tracking/Information Technology (IT) training

3.1.17 Cybersecurity (CS)/Information Technology (IT) certification

3.1.18 Security Clearance Requirements

3.1.19 Threat Awareness and Reporting Program

3.2 Systems Engineering

3.2.1 System Design

3.2.2 Hardware Engineering

3.2.3 Software Engineering

3.2.4 Hardware and Software Integration

05 09 017 Rev. 2.1 iv

3.2.5 Cybersecurity (CS)

3.2.6 Specialty Engineering

3.2.7 Design Reviews

3.2.8 Product Definition Data (PDD)

3.3 Logistics

3.3.1 Initial Spares

3.3.2 Technical Publications

3.3.3 Item Unique Identification (IUID)

3.3.4 Software Support Environment (SSE)

3.3.5 Test Measurement and Diagnostic Equipment

3.3.6 Training and Training Products

3.3.7 Transition Planning

3.3.8 Technology Refresh

3.4 On-Call Maintenance Support

3.5 Integrated Testing

3.5.1 Test Readiness Review (TRR)

3.5.2 Contractor Developmental Test

3.5.3 Government Testing

3.5.4 Cybersecurity Compliance

3.6 Site Activation

3.6.1 Site Survey

3.6.2 Installation Program

3.6.3 Installation Tools and Test Equipment

3.6.4 Installation Spares

APPENDIX-A Technical Review Entry and Exit Criteria

A-1 Systems Requirements Review (SRR) Entry Criteria ................................................... A-1 A-2 SRR Exit Criteria ........................................................................................................... A-1 A-3 Preliminary Design Review (PDR) Entry Criteria ........................................................ A-2 A-4 PDR Exit Criteria .......................................................................................................... A-2 A-5 Critical Design Review (CDR) Entry Criteria .............................................................. A-3 A-6 CDR Exit Criteria .......................................................................................................... A-4 A-7 Test Readiness Review (TRR) Entrance Criteria .......................................................... A-5 A-8 TRR Exit Criteria .......................................................................................................... A-5 A-9 Physical Configuration Audit (PCA) Entry Criteria ..................................................... A-6 A-10 PCA Exit Criteria .......................................................................................................... A-6

APPENDIX-B Acronym List .................................................................................................. B-1

05 09 017 Rev. 2.1

1 SCOPE

This Statement of Work (SOW) defines the effort required for designing, developing, integrating, testing, managing, documenting, and delivering the Stryker Phase V Training System. The Phase V is intended to provide the following at the Fort Lee, VA facility:

a. Five (5) high fidelity, fully instrumented, Hands On Trainers (HOTs) for the Stryker Main Gun System (MGS) with associated individual training tasks.

b. Five (5) high fidelity, fully instrumented, HOTs for the Anti-Tank Guided Missile (ATGM) with associated individual training tasks.

c. Five (5) high HOTs for the Mortar Carrier (MC) with associated individual training tasks.

d. One (1) Caterpillar C7 Power Pack Assembly Part Task Trainer (PTT) with associated individual training tasks.

e. Two one-year On-call Support efforts will be included as options for the new devices fielded to the Fort Lee, VA site.

Tactical hardware will be provided to the winning offeror GFE to be used to build the trainer.

The following list indicates the GFE Hardware that will be available:

4 (each) MGS tactical Vehicles and 1 (each) MGS tactical Turret for MGS HOTs

5 (each) ATGM tactical Vehicles for ATGM HOTs

5 (each) MC tactical Vehicles for MC HOTs

1 (each) Complete tactical C7 Power Pack Assembly for PTT

1 (each) Software Support Environment (SSE)

1 (each) Technical Data Package (TDP) to include: three DVDs

a. DVD #1: Interactive Electronic Technical Manual (IETM) viewer for EMS NG

2.1.10 – September 2015

b. DCD #2: IETM (14 December 2015) and executable to load IETM

c. DVD #3: IETM - Stryker ICV CAD files: MGS and MC vehicles, Stryker vehicle drawings (W900KK-17-R-0016; CDRL: B004 – Product

05 09 017 Rev. 2.1

Drawings/Models and Associated Lists), and Phase IV delivered software (W900KK-09-D-0562-0002iv; CDRL: B002 – Software Product Specification.

The Government will provide four (4) complete MGS vehicles and one (1) MGS Turret for developing the MGS HOTs. The appropriate GFE will be made available as options are exercised. Based on the final design, additional crew compartment tactical equipment required but not currently available with the GFE standalone turret will be provided as GFE for the development of MGS HOT number five (5).

The Government provided the TDP to responding Industry partners from a Request For Interest and whom signed a Distribution Agreement (Posted on www.FedBizOpps.Gov on 08 DEC 2016). The TDP can be provide to other interested Industry partners by contact the POCs at ACC-Orlando.

For the new Stryker MTS Phase V deliverables, the contract shall use the performance specification PRF-PT-684. Source code and Technical Manuals (TM) from the existing Stryker MTS family of maintenance trainers will be provided as Government Furnished Information (GFI). Commercial Off -The-Shelf (COTS) software will not be provided by the Government.

The delivered Stryker MTS Phase V systems shall be capable of maintaining concurrency with the provided Interactive Electronic Technical Manual (IETM).

The existing Software Support Environment (SSE) will be provided as Government Furnished Equipment (GFE) after contract award. The SSE currently provides the hardware, software, and documentation resources for performing Post Deployment Software Support (PDSS) activities including identifying, documenting, and correcting system software faults, implementing system upgrades, generating application programs, managing databases, and providing configuration management of the training system(s) software baseline. The existing Stryker MTS documentation must be updated as part of this effort and at the end of the contract must provide the resources (i.e., source code, executable code, maintenance software, data base, and scenario generation tools, documentation, installation hardware, software installation disk, etc.) for the purpose of maintaining computational systems in a fully operational condition.

When the Stryker MTS Phase V devices are fielded, the instructor must have the capability to select the lessons from any Training Task List (TTL), with the same type of graphical user interface that is used currently in the fielded Stryker MTS devices. The existing Instructor and Operator user interface shall be maintained. The remote Instructor/Operator capabilities previously migrated to a “Tablet” hardware solution must be maintained. The software code provided to the Contractor is not warranted and is only provided for information purposes. The existing system architecture, software design, functionality, user interface, and instructor capabilities shall be maintained.

05 09 017 Rev. 2.1

The Stryker MTS systems shall comply with the latest Cybersecurity requirements. The operating system(s) for the trainer shall be an approved Secure Host Baseline-Army (SHB-A).

The threshold accreditation boundary for Cybersecurity will be systems interfaced to the DTT classroom Training Management System (TMS), including the DTTs and the Phase V ATGM and MGS HOTs. The objective requirement is to interface existing HOT and PTT devices to the DTT classroom TMS, harden those systems to meet Cybersecurity requirements, and include those systems within the MTS accreditation boundary.

Deliveries will be to Fort Lee, VA (Building 18030).

1.1 Background

The Stryker Maintenance Training System (Stryker MTS) mission statement is ‘The Institutional Maintenance Training System (MTS) will support the Stryker Additional Skill Identifier (ASI) R4 and 91S Skill Based Training courses.’ This capability is in support for the Ordnance Schools located at Fort Lee, VA with the capability to train the Army’s Military Occupational Specialty (MOS) 91S and provide skill level development training for maintenance personnel covering system operation, symptom verification, troubleshooting, fault isolation, adjustment, servicing, and remove/replace of Line Replaceable Units (LRUs).

The Stryker MTS program comprises the following fielded specialized training devices:

a. Diagnostic Troubleshooting Trainers (DTTs): A beginning stage of training to allow trainees to utilize a desktop trainer system to troubleshoot, go through maintenance lessons following the fielded Interactive Electronic Technical Manual (IETM) in a 3-Dimensional (3-D) virtual world. The instructor can monitor and track each student’s performance in the independent virtual environment.

b. Part Task Trainers (PTTs): A next step in training, utilizing a high fidelity replica of the actual vehicle sub-systems with normal and faulted behavior. Again following through a lesson plan, the student uses an IETM and now applies the DTT skills on to actual replicated hardware monitoring the steps the trainees take.

c. Hands On Trainer (HOT): A parallel next step in training utilizing a high fidelity replica of the actual vehicle with normal and faulted behavior. Again following through a lesson plan, the student uses an IETM and now applies the appropriate DTT and PTT skills on actual replicated vehicle hardware monitoring the steps the trainees take.

The Stryker MTS at Fort Lee, VA currently consist of two (2) twenty (20) student classrooms, which utilize DTT’s, a Training Management System (TMS), and a series of HOTs and PTTs.

05 09 017 Rev. 2.1

The training system provides maintenance training capability for the Army’s 91S Military Occupational Specialty (MOS). This capability supports familiarization, institutional and unit training. The MTS provides training for maintenance personnel in system operation, symptom verification, troubleshooting, fault isolation, adjustment, servicing, and removal/replacement of LRUs. The training system provides an automatic capability to record, score, and store the performance of students on all tasks, as well as, evaluates the student’s knowledge of the appropriate vehicle system’s functioning theory. The training system provides real-time feedback and scoring capability, which displays and records all the information necessary to evaluate the student’s performance and understanding of the training task. The general areas of scoring include as a minimum the management of switches and controls, response to malfunctions, and actions required by the tasks identified in the Training Task List (TTL). The training system also provides real time display of errors generated by student(s) as they occur during real-time scenario execution.

Training is separated into two distinct categories: The Stryker automotive components and the Stryker weapon components. The DTTs include weapons modules, which support the Remote Weapon System (RWS), the Anti-Tank Guided Missile (ATGM), Main Gun System (MGS), and Mortar Carrier (MC) variants. Training on the automotive system utilizes a Hull HOT, existing Brake and C7 Power Pack Assembly PTTs.

The trainer operates in or supports various modes. The modes include 'Lesson Selection', 'Lecture', 'Demonstration', 'Training', and 'Diagnostics'. The 'Lesson Selection' and 'Diagnostics' modes are operator selectable. The 'Lecture', 'Demonstration', and 'Training' modes are a common mode of execution but differ in how the instructor makes use of each mode.

A TMS maintains a library of lessons that can be selected for training. From the Instructor Operator Station (IOS), the instructor can select an appropriate lesson from that library to use for training. The TMS also provides the capability for the instructor to record, score, store, and retrieve the performance of students on all tasks.

2 APPLICABLE DOCUMENTS

The following document is applicable to this SOW to the extent specified herein.

PRF-PT-684 System Requirements Document for the Stryker Phase V Training System

2.1 Department of Defense Specifications

Not Applicable (N/A)

05 09 017 Rev. 2.1

2.2 Availability of Department of Defense (DOD) Specifications Copies are available on the WWW at URL: http://quicksearch.dla.mil

2.3 Department of Defense Standards

DOD 5520.22M National Industrial Security Program Operating Manual

(NISPOM)

DFAR 252.227 Rights in Technical Data – Noncommercial items FAR 52.204-9 Personal Identity Verification of Contractor Personnel

Clause MIL-STD-130 Identification Marking of U.S. Military Property MIL-STD-31000A Technical Data Packages MIL-PRF-32216A Evaluation of Commercial Off The Shelf (COTS) Manuals MIL-PRF-29612B Training Data Products MIL-HDBK-1467 Acquisition of Software Environments and Support

Software MIL-STD-40051-2C Preparation of Digital Technical Information for Multi-output Presentation of Technical Manuals SAE-GEIA-HB-0007 Logistics Product Data Handbook SAE-GEIA-STD-0007 Logistics Product Data

2.4 Availability of Department of Defense (DOD) Standards

Copies are available on the WWW at URL: http://quicksearch.dla.mil/qsSearch.aspx

2.5 Department of Defense Directives

N/A

2.6 Availability of Department of Defense Directives

Copies are available on the WWW at URL: http://www.dtic.mil/whs/directives/

2.7 Department of Defense Instructions

DODI 5200.46 DoD Investigative and Adjudicative Guidance for Issuing the Common Access Card (CAC)

DODI 8510.01 Risk Management Framework (RMF) for DOD Information Technology (IT)

DODI 8582.01 Security of Unclassified DOD Information on Non-DOD Information Systems

NIST SP 800-53 Cybersecurity http://quicksearch.dla.mil/ http://quicksearch.dla.mil/qsSearch.aspx http://www.dtic.mil/whs/directives/

05 09 017 Rev. 2.1

2.8 Availability of Department of Instructions

Copies are available on the WWW at URL: http://www.dtic.mil/whs/directives/

2.9 Other Government Documents, Drawings and Publications

Army Directive 2015-05 Policy and Implementation Procedures for Common Access Card Credentials and Installation Access for Uncleared Contractors

Army J/F-12 Army Frequency Allocation to Equipment Program

AR 5-12 Army Management of the Electromagnetic Spectrum

AR 25-2 Information Assurance Copies are available on the WWW at URL:

https://ia.signal.army.mil/docs/AR25-2.pdf

AR 380-5 Department of the Army Information Security Program

AR 381-12 Threat Awareness and Reporting Program

AR 530-1 Operations Security

CNSSI 1253 Security Categorization and Control Selection for National Security Systems

DODD 8570.01 Information Assurance Workforce Improvement Program

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

Federal Information Processing Standard (FIPS) Publication 140-2 Security Requirements for Cryptographic Modules.

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

http://www.dtic.mil/whs/directives/

05 09 017 Rev. 2.1

Program-Unique Specification Document (PUSD) (RCPN-964-5381-001) for the Stryker Maintenance Training System (MTS) 63B Hands On Trainer (63B HOT) Dated 29 JUL 2010.

Copies of the above documents are available at Program Executive Office of Simulation, Training and Instrumentation (PEO STRI), ATTN: PM TRADE, 12350 Research Parkway, Orlando, FL 32826-3276.

29CFR1910.1200 Environmental Protection Agency's (EPA) toxics release inventory Class I and Class II stratospheric Ozone Depleting Substances (ODSs) available at http://www.epa.gov/tri/chemical/index.htm.

2.10 Availability of Non-Government Standards and Other Publications

National Institute of Standards and Technology SP 800-53 Revision 4

Security and Privacy Controls for Federal Information Systems and Organizations available at http://csrc.nist.gov/publications/drafts/800-53-rev4/sp800_53_r4_draft_fpd.pdf.

3 REQUIREMENTS

3.1 Program Management

The contractor shall provide the overall management and administrative effort necessary to ensure that the requirements of this contract are accomplished. The contractor shall track program progress utilizing, at a minimum, the metrics set forth on this document. The contractor shall plan, implement, and maintain a Life Cycle Cost (LCC) management process to minimize the system cost and use LCC to conduct trade studies, evaluate design, and support alternatives, and select the resource support requirements. The contractor shall define and monitor metrics and Technical Performance Measures (TPMs) to evaluate the performance of each critical technical and management process and conformance of the evolving products with contract requirements and objectives.

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

3.1.1 Subcontractor Management

The Contractor shall manage and have agreements with subcontractors and partners as required.

Contractor shall integrate subcontractors and partners into program Integrated Product Teams (IPT). The Contractor shall ensure the requirements of this contract are applied to all subcontracts and associate contracts.

http://www.epa.gov/opptinr/3350/33finb1.htm

05 09 017 Rev. 2.1

3.1.2 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 (IAW) 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 IAW the IMP at each program review, at selected technical reviews and at the Government discretion. The IMP shall depict the contract work breakdown structure.

3.1.3 Integrated Master Schedule (IMS)

The contractor shall develop, implement, manage to, update, and maintain the contract Integrated Master Schedule (IMS). The IMS shall present a finalized tiered scheduling system showing all critical milestones and prerequisite events. The lower tiered schedules shall display increasing levels of detail down to the work package level. All contract schedule information delivered and presented at program reviews shall originate from the IMS and shall contain all critical events, accomplishments, predecessors, successors’ events, and their dependencies. The IMS shall address all program activities including activities performed by subcontractors and key supplier activities. The contractor shall develop the logic resource loaded network that accurately portrays the sequence and relationship of activities defining the development and production program. 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 duration data shall be updated to reflect accomplished activities and any changes in activity duration 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. The contractor shall include and integrate into the IMS system network outside dependencies/events pertaining to the total program. These dependencies/events will be provided by the Government or gathered by the contractor during participation in other Integrated Project Team (IPT) meetings.

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

3.1.4 Financial Management

The contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The contractor shall document and track the status of all appropriated funds associated with the contract 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 (PWBS) to lower levels in the contractor’s Contractor Work Breakdown Structure (CWBS). It defines the lower level components of what

05 09 017 Rev. 2.1 is to be procured and includes all the product elements (hardware, software, data, or services), which are defined by the contractor and are the contractor’s responsibility. The extended CWBS shall serve as the framework for contract planning, budgeting, 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 schedule data reported.

(DI-MGMT-81651) Contract Invoicing and Payment Report

3.1.4.1 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.

3.1.4.2 Contractor Manpower Reporting Application (CMRA)

The contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. Reporting inputs will be for labor executed during the period of performance during each Government Fiscal Year (FY), which runs 1 OCT through 30 SEP.

While inputs may be reported any time during the FY, all data shall be reported no later than 31 OCT of each calendar year. Contractors can find User Guides, Frequently Asked Questions and may direct questions to the help desk at http://www.ecmra.mil/.

http://www.ecmra.mil/ http://www.ecmra.mil/

05 09 017 Rev. 2.1

3.1.5 Configuration Management (CM)

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.

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 include changes made to the Information Assurance (IA) Cybersecurity (CS) configuration and associated documentation. Failure to include Cybersecurity considerations in the configuration management and engineering change control processes could adversely affect the program’s ability to integrate and maintain CS in the functional design of the system. This will affect the system's ability to obtain CS accreditation.

It may also increase the system's susceptibility to computer network attack from information operation activities. The contractor shall:

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

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

c. Document how the contractor’s 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.

05 09 017 Rev. 2.1

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.

05 09 017 Rev. 2.1

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.

05 09 017 Rev. 2.1

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

c. Capture configuration information as it evolves.

3.1.5.5 Physical Configuration Audit (PCA)

The Physical Configuration Audit (PCA) will consist of non-functional examinations performed to demonstrate the trainer as-built design that satisfies PRF-PT-684 requirements, and that the deliverable hardware and software documentation accurately reflect the configuration items. The contractor shall validate hardware components with each representative drawing(s) and documents as the first trainer is assembled. Results of the contractor conducted “build-up” PCA shall be available for review for each piece part, component, and assembly. Non-deliverable documents may be in contractor format and will be examined only to determine contractor compliance with configuration management requirements.

A hardware and software PCA will be conducted in-plant during In-Plant Acceptance Test (IPAT) by a Government team on the as-built trainer with power off. The contractor shall provide the personnel and facilities necessary to support the Government-conducted audits. The contractor shall be responsible for the disassembly of trainer equipment to the Lowest Repairable Unit (no disassembly would be requested which would violate warranty claims) and for providing access to areas of the trainer not normally accessible. The Government reserves the right to perform other audits deemed necessary to determine compliance with PRF-PT-684 and design documentation requirements.

The Government will conduct a final hardware and software PCA prior to On-Site Acceptance Test (OSAT) to verify the product baseline. The hardware PCA will consist of audits of the as-built training device against its design documentation to include facility modifications. The software PCA will consist of audits of the as-built version of the Computer System Configuration Items (CSCI) against the software technical documentation.

The PCA shall include a detailed audit of engineering drawings, specifications, technical data and tests utilized in production of Hardware Configuration Items (HWCIs) and a detailed audit of design documentation, listings, and manuals for CSCIs. The review shall include an audit of the released engineering documentation and quality control records to verify the as-built or as-coded configuration is reflected by this documentation. For software, the Software Product Specification and Software Version Description shall be a part of the PCA review. Deficiencies recorded by the Government shall be corrected by the contractor prior to the signing of the DD- 250.

05 09 017 Rev. 2.1

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.

(DI-SESS-81022D) Configuration Audit Summary Report and Certification

3.1.5.6 Software Configuration Management Database

The contractor shall establish and maintain a software configuration management database IAW the software development process plan. 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.7 System 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.8 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)

3.1.5.9 Variances

If it is necessary to temporarily depart from specified baseline requirements, a request for variance should be identified, classified, documented, coordinated, evaluated and dispositioned.

05 09 017 Rev. 2.1

The contractor shall document the rationale and the potential impact of any deviation. The contractor shall obtain approval before deviating from any Government controlled baseline.

(DI-SESS-80640D) Request for Variance

3.1.5.10 Engineering and Contract 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 Program Executive Office of Simulation, Training, and Instrumentation (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. Minutes shall be a historical record to allay any miscommunications.

3.1.6 Technical Performance Measures (TPM)

The contractor shall select technical performance parameters that reflect key indicators of program success. Technical Performance Measures (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 budgeted. An analysis shall be accomplished on the variation to determine the causes and to assess the impact on higher-level parameters and on interface requirements.

3.1.7 Risk Management

The contractor shall prepare, implement, and maintain a risk management process that includes identification, analysis, mitigation planning, mitigation plan implementation, and tracking. The contractor’s risk management process shall measure future uncertainties in achieving program goals within defined cost, schedule, and performance constraints. The contractor shall:

a. Identify and document moderate and high-risk items for each risk assessment area.

b. Identify and implement risk handling approaches, and track over time each moderate and high-risk item.

05 09 017 Rev. 2.1

c. Develop mitigation plans to identify the recommended critical path for contract completion and the appropriate risk handling approach to lower the level of uncertainty.

d. Include Government representatives in all risk identification, analysis, mitigation planning and implementation, and tracking through IPTs and Program events.

All of the items being tracked by the contractor’s risk management processes shall be immediately informed, addressed, and updated to the Government through PMRs, Design Reviews, and IPTs.

3.1.8 Management Reviews

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

A start of work meeting shall be held at the contractor’s facility within thirty (30) days after contract award. The start to work meeting shall be limited to the contractor’s key team members identified in the proposal, and will be a two-day session to discuss the System Requirements Review (SRR), top level management of the program, agreement on metrics that will be used as management indicators to implement during the program and partnering approach.

A Post Award Conference (PAC) shall be held at the contractor’s facility at a mutually agree to date after the start of work meeting. The conference shall introduce the key IPT participants, identify points of contact, and discuss both parties understanding of the scope of work and other contract issues.

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

3.1.8.2 Program Management Reviews (PMR)

The contractor shall conduct one formal Program Management Reviews (PMR) every four months IAW the integrated master plan following the start of work meeting. The location of the reviews shall be mutually agreed upon. The PMRs shall provide a program overview and a detailed discussion of pre-selected topics. Status and information at the review shall reflect currency since the previous review.

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

05 09 017 Rev. 2.1

3.1.8.3 Integrated Product Team (IPTs)

The contractor shall establish an Integrated Product Team (IPT) structure to address major areas of system development (e.g., program management, risk management, systems engineering (hardware design, software design, etc.), logistics support, testing, Cybersecurity, etc.). The contractor shall establish IPT charters and host regularly schedule IPT meetings or teleconferences. The IPT meetings/teleconferences shall be used to address systems development status of activities, technical data and status, questions and issues in a timely manner between management and technical reviews. The contractor shall prepare meeting minutes and distribute to attendees before the next IPT meeting.

3.1.8.4 CS Control Review/RMF Implementation Plan Review (RIPR)

The contractor shall support a CS Control Review/RMF Implementation Plan Review (RIPR) held as part of the Preliminary Design Review (PDR). The CS Control Review/RIPR shall address at a minimum:

a. Update on RMF Implementation Plan (RIP)

b. Update Preliminary Data Flow and Accreditation Boundary Diagram

c. Update on the hardware/software lists and procurement action

d. Update on contractor CS training as applicable and the use of CS scanning tools

e. Update on design and system integration schedule

3.1.8.5 Technical Interchange Meetings (TIMs)

The contractor shall conduct and participate in technical interchange meetings to be held at both contractor and Government facilities. The meetings shall be co-chaired by a Government and contractor representative. The contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The contractor shall prepare drawings and other data, as required, to aid in the presentations. The contractor shall have all the required personnel and resources present. The contractor shall make available facilities for Government only meetings. These Government meeting facilities shall include direct internet access for Government personnel laptops. The contractor shall prepare the meeting agendas and document the meeting results. The contractor shall prepare meeting minutes and distribute to attendees within two weeks after the TIM.

05 09 017 Rev. 2.1

3.1.9 Visitor Support

The contractor shall host Very Important Person (VIP) visits, arrange for, and provide demonstrations of system performance, program progress, and other system characteristics when notified by the Procurement Contracting Officer (PCO).

3.1.10 Integrated Digital Environment (IDE)

The Contractor shall provide an Internet based IDE to facilitate the electronic data interchange of all program data. All management, technical, cost, and schedule data (including all internal documents produced to design, develop, test and manage the program) shall be made available to all Government and contractor team members in an integrated, electronic, and query capable database, accessible via the Internet. The Contractor shall provide the capabilities for on-line review, comment, acceptance, and approval of all deliverable data. The Contractor shall establish a disaster recovery process to ensure that appropriate information systems and data are available when needed after a natural or human disaster.

3.1.10.1 The IDE Development and Installation

The contractor shall provide an IDE with the following capabilities:

a. Ability to capture information as it is created.

b. Ability to manage product and program management structures.

c. Real-time information sharing and work flow implementation.

d. Team access to the most current information.

e. Ability to assign rules regarding information access.

f. Common information architecture that is distributed geographically.

g. Electronic notification of changes to program and product information.

h. Ability to present a single interface to the entirety of the contractor’s and the contractor’s subcontractors' data creation activities.

i. Ability to recover from unexpected loss of program data due to environmental disasters, operator error, equipment failure, and hostile intruders.

05 09 017 Rev. 2.1

3.1.10.2 IDE Administration

The contractor shall provide a World Wide Web based electronic data management system to facilitate the electronic data interchange of non-classified data. Except where noted specifically on the DD Form 1423, the contractor shall provide this service for items on the data accession list, management data, and technical data generated and maintained in digital format. The contractor shall provide the Government and contractor team members with the capabilities for on-line review, and comment of deliverable data. The contractor shall include these comments, approvals, and acceptances in the database as well as mechanisms to establish appropriate audit trails to identify the sources of these additions and to maintain configuration control. The contractor shall develop and implement procedures for establishing and administering user accounts for the IDE.

3.1.10.3 IDE Data Management

The Contractor shall establish, implement, and maintain a data management capability within the IDE for the integration, storage, access, management, delivery, and exchange of data furnished by the government or generated by any contract work effort including subcontractors and vendors. The system shall be capable of maintaining a record and reporting the status of data accession and data deliveries for each unit delivered. The Contractor shall generate and maintain a master listing of all documents maintained in the training site libraries. The listing shall include all operations and maintenance publications, engineering drawings and specifications, software source code, software databases, training materials, and baseline description documents.

3.1.11 Antiterrorism (AT) Level 1 Training

All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level 1 awareness training in accordance with AR 381-12 within thirty (30) calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the Contracting Officer Representative (COR) or to the contracting officer, if a COR is not assigned, within thirty (30) calendar days after completion of training by all employees and subcontractor personnel. AT level 1 awareness training is available at the following website: http://jko.jten.mil.

3.1.12 Access and General Protection Policy and Procedures for Common Access Card (CAC)

The contractor and all associated subcontractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services, or Security Office. The

05 09 017 Rev. 2.1 contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following:

a. Both physical access to a Department of Defense (DOD) facility and access, via logon, to DOD networks on-site or remotely;

b. Remote access, via logon, to a DOD network using DOD-approved remote access procedures; or c . Physical access to multiple DOD facilities or multiple non-DOD federally controlled facilities on behalf of the DOD on a recurring basis for a period of six (6) months or more.

At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the Federal Bureau of Investigation (FBI) fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

For contractors that do not require CAC, but require access to a DOD facility or installation.

Contractor and all associated subcontractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

3.1.13 iWATCH Training

The contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity AT Office). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the Contract…