Attachment 1 DRTS Fort Knox DAGIR SOW_10May2022.pdf

SOW-2021-002

Version: 1.3 2 May 2022

DIGITAL RANGE TRAINING SYSTEMS

STATEMENT OF WORK

FOR

FT KNOX DIGITAL AIR/GROUND INTEGRATION RANGE (DAGIR)

US Army Program Executive Office for Simulation, Training and Instrumentation (PEO STRI)

12211 Science Drive Orlando, FL 32826-3276

Prepared By: ____________________ Concurrence: _______________ Nicole Steib James Todd Systems Engineer, PdM LTS Chief Engineer, PdM LTS

Prepared By: ____________________ Concurrence: ______________ Gary Stevenson Matt Brothers Lead Acquisition Logistician Product Support Manager

Submitted By: ____________________ Approved By: _______________ Carol Spicer Michael Willoughby Assistant Program Manager, PdM LTS Product Manager

Live Training Systems (LTS)

Distribution Statement A:

Approved for Public Release, Distribution is Unlimited

2 May 2022 i

Revision History

Date Version Author Section Revision Description 8 Dec 21 1.0 DRTS

Team All DRTS SOW for Ft Knox DAGIR

24 Feb 22 1.1 DRTS Team

3.1.2.1, 3.1.2.2, 3.1.5, 3.2.4, 3.3.3, 3.3.11

Removed references to TII and Site Survey.

28 Mar 22 1.2 DRTS Team

5 Added ITAS Data section and associated CDRL

2 May 2022 1.3 DRTS Team

3.1.4.4 Added field camera integration

requirements ii

Table of 1 Scope

1.1 Introduction

1.2 Background

1.3 DAGIR Description:

1.4 Ft Knox DAGIR Milestone Planning Dates

2 Applicable Documents

2.1 Government Directives, Manuals, and Instructions

2.2 Military Specifications, Standards, and Handbooks

2.3 Other Government Documents

2.4 Non-Government Standards and Publications

2.5 Order of Precedence

3 Requirements

3.1 Requirements Overview

DAGIR Effort

3.1.1.1 Operations Control Facility Preparation

3.1.1.2 Range Preparation and Definition

Site Preparation Government Furnished Property (GFP) Range Equipment System Requirements Software Requirements

3.2 Program Management (PM)

Management Review Integrated Product Teams (IPTs) Program Schedule

RESERVED

Computer Hardware, Enterprise SW Solutions (CHESS):

RESERVED

Risk Management Deviations and Waivers

3.3 Engineering

Systems Engineering Product-Line Engineering System Design and Definition SW Engineering Product Definition Data (PDD) System Integration iii

Configuration Management (CM) Quality Assurance (QA) and Quality Control (QC) Engineering Change Proposal (ECP)

Safety Engineering Technical Design Review (TDR)

3.4 Test and Verification

Test Readiness Review (TRR) In-Plant Testing Contractor Test System Technical Test (STT) System Operational Test (SOT)

3.5 Government Acceptance

3.6 Cybersecurity (CS)

CS Artifacts

3.7 Security

Handling or Access to Classified Information Access and General Protection Credentialing Security Training Army Training Certification Tracking System (ATCTS) Registration for

Contractor Employees Who Require Access to Government Information Systems

4 Logistics

4.1 Supportability Analysis and Logistics Product Data

4.2 Inventory Support

4.3 Synchronization with the LCCS

4.4 Initial Spares

4.5 Technical Publications

Publication In-Process Reviews (IPRs) Technical Publication Validation Technical Publication Verification Physical Configuration Audit (PCA)

4.6 New Equipment Training (NET)

4.7 Interim Contractor Support (ICS)

4.8 Transition to LCCS

4.9 NET Verification

4.10 Item Unique Identification (IUID)

5 Information Technology Approval System (ITAS) Data iv

: Abbreviations and Acronyms

: Range Variables for the Ft Knox DAGIR

: DRTS Work Breakdown Structure

1 Scope This Statement of Work (SOW) defines the work required to provide technical and management support for the design, procurement, installation, integration, testing, fielding, training, and documentation for the new fielding of the Ft Knox Digital Air/Ground Integration Range (DAGIR).

1.1 Introduction

The Digital Range Training System (DRTS) DAGIR complex is used to train aviation crews, teams, platoons, and companies/troops on skills necessary to detect, identify, and effectively engage stationary and moving infantry and/or armor targets in a tactical array. It provides armor, infantry vehicle, and helicopter crews with collective gunnery training and qualification In Accordance With (IAW) Army doctrine. This complex supports dismounted infantry platoon tactical live fire operations either independently or simultaneously with supporting vehicles. The main types of armor vehicles trained are the M1 Abram series, M2 Bradley series, and Stryker Infantry Crew Vehicle, and the Commander’s Vehicle. DRTS supports aviation training and qualification for the AH- 64D/E, door gunnery for the UH60, and CH47 utility/cargo helicopters. The DAGIR will also include the permanent Aerial Weapons Scoring System (AWSS), which is an objective scoring system designed to support Aviation Gunnery Training. AWSS consists of five subsystems that promotes and defends readiness. The Computer Control Subsystem provides the operator interface to all of the scoring subsystems and is used to generate all scoring reports.

The DAGIR will also support aviation training for Unmanned Aerial Systems (UAS) to provide a capability to train and qualify UAS crew. UAS implementation consists of integrating the UAS video payload, crew audio, and air vehicle data (i.e. Speed, Altitude, etc.) capability into the DRTS system.

DRTS supports the Combined Arms Training Strategy collective task training and exercise events. DRTS provides objective data collection and analysis of unit performance for Force-On-Target, Live Fire Exercises, and associated command post exercises. DRTS utilizes the Dismounted Tracker (DMT) to provide situational awareness during section, platoon, and company training to track movement of troops on ground on the entire range complex. DRTS also interfaces with the tactical vehicles through an Integrated Player Unit Recorder (IPUR) or Smart Onboard Data Interface Module (SMODIM) to provide both real-time feedback to leaders and rapid development of complete After Action Reviews (AARs) and Take Home Packages (THPs). Targets will receive and transmit digital data from the Control Tower (CT). The captured data is then compiled and available to the unit during the After Action Review (AAR). DRTS also supports live fire training for individual and crew served weapon skill qualification and sustainment.

1.2 Background

The DRTS program provides a complete hardware (HW)/software (SW) instrumentation package with training to the Ft Knox DAGIR. This effort includes the design, delivery, installation, integration and testing of targetry, workstations (WSs), servers, switches, projectors, displays, communications systems, keyboards, and mice. The instrumentation also includes Field Cameras (FCs), Player Units (PUs), PU infrastructure, Dismounted Tracker (DMT), AWSS, and Battle Effects Simulator II

(BES).

1.3 DAGIR Description:

A DAGIR supports all Aviation gunnery tables to include diving fire and door gunnery, as well as individual and crew qualification training. It also supports platoon level collective training for all gunnery tables for Abrams, Bradley, Stryker, dismounted infantry (via DMT), and aviation, which the vehicle variations are referenced in the DRTS Integrated Player Unit Recorder (IPUR) Performance Specification PRF-PT-765.

A DAGIR uses thermal targets, night illumination devices, hostile-fire, target-kill, and visual flash. The Fort Knox DAGIR footprint threshold is 4Km x 6Km and primary features detailed list is included in Appendix B.

1.4 Ft Knox DAGIR Milestone Planning Dates

a. Beneficial Occupancy Date (BOD): Scheduled for November 2022.

b. Contractor installation date: Immediately following BOD.

c. System Operational Test (SOT): 9 months after BOD.

d. Range Acceptance: 12 Months after BOD.

2 Applicable Documents In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of this SOW shall be the governing requirement.

2.1 Government Directives, Manuals, and Instructions

Document Number Document Title Department of Defense Manual

(DODM) 5200.1

DOD Information Security Program: Overview, Classification, and Declassification

DODM 5220.22 National Industrial Security Program Operating Manual

DOD 8570.01-M Information Assurance Workforce Improvement Program

DODD 8570.01 Information Assurance (IA) Training, Certification, and Workforce Management

DODI 8500.01 Cybersecurity DODI 8510.01 Risk Management Framework for DOD

Information Technology

DODI 8582.01 Security of Non-DOD Information Systems Processing Unclassified Nonpublic DOD Information

DODD 8140.01 Cyberspace Workforce Management

DoDI 5200.48 Controlled Unclassified Information (CUI)

Table 1: Government Documents

2.2 Military Specifications, Standards, and Handbooks

The following specifications, standards, instructions, regulations, and handbooks form a part of this document to the extent specified herein.

Document Number Document Title AR 530-1 Operations Security (OPSEC) MIL-STD-31000B Technical Data Packages (TDP) MIL-STD-882E Standard Practice for System Safety MIL-HDBK-240 DOD Handbook for Hazard of Electromagnetic

Radiation to Ordnance (HERO) Test Guide Committee on National Security Systems Instruction (CNSSI) No.

Security Categorization and Control Selection for National Security Systems

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

AR 25-2 Cybersecurity AR 190-13 Army Physical Security Program AR 381-12 Threat Awareness and Reporting Program MIL-STD-40051-2C Preparation of Digital Technical Information for

Page-Based Technical Manuals MIL-STD-130N Identification Marking of US Military Property TC 25-8 Training Ranges TC 3-04.3 Aviation Gunnery TC 3-20.31 Training and Qualification, Crew

Table 2: Military Specifications, Standards, and Handbooks

2.3 Other Government Documents

The following other Government documents, drawings, and publications form a part of this specification to the extent specified herein.

Document Number Document Title

PRF-PT-765 DRTS Integrated Player Unit Recorder (IPUR) Performance Specification

DRTS ATO DRTS Authority to Operate LT2-TRADE-TD-000499 Lifecycle Data Service Interface Control

Document DRTS-SSP DRTS System Security Plan (SSP) Army Directive 2014-05 Policy and Implementation Procedures for

Common Access Card Credentialling and Installation Access for Uncleared Contractors.

MIL-PRF-32216A Performance Specification Evaluation of Commercial-Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data

DFARS 252.239.7001 Defense Federal Acquisition Regulation Supplement

PRF-PT-768 DRTS Performance Specification PRF-PT-767 DRTS Dismounted Tracker (DMT) Performance

Specification PRF-PT-769 DRTS Video System Suite (VSS) Performance

Specification PRF-PT-00468 Future Army System of Integrated Targets

(FASIT) Performance Specification RMF Implementation Plan DRTS RMF Implementation Plan

Table 3: Other Government Documents

2.4 Non-Government Standards and Publications

The following documents form a part of this document to the extent specified herein.

Standard Number Standard Title ANSI/NFPA 70 National Electrical Code ANSI/NFPA 780-1997 Installation of Lightning Protection Systems GEIA-STD-0007C Logistics Product Data GEIA-HB-0007B Handbook and Guide for Logistics Product Data TA-HB-0007-1 Logistics Product Data Reports Handbook 29CFR1910.1200 Occupational Health and Safety Standards

Table 4: Non-Government Standards and Publications

Copies of specifications, standards, drawings, may be obtained as directed by the Procuring Contracting Officer (PCO). Copies of the Department of Defense (DOD) Information documents are available at URL: https://www.dtic.mil/whs/directives/.

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

2.5 Order of Precedence

In the event of a conflict between the text of this SOW and the references cited herein, the text of this SOW takes precedence. The contractor shall notify the Government of any conflict so the Government may address the discrepancy. However, nothing in this SOW supersedes applicable laws and regulations.

3 Requirements

Figure 1: DRTS System Diagram

3.1 Requirements Overview

DAGIR Effort

The contractor shall procure and acquire materials, install, integrate, test, verify performance, and document the DRTS DAGIR functional baseline training instrumentation system. The contractor shall comply with the existing DRTS Cybersecurity baseline as specified in the latest approved Authority to Operate (ATO), SSP, and relevant Risk Management Framework (RMF) documentation. Down range target devices (Range Devices, Presentation Devices, and Range Effects Devices) will be compliant with the Future Army System of Integrated Targets (FASIT) Performance Specification (PRF-PT-00468) and implement the FASIT Interface Control Documents (ICDs) as applicable to the device type IAW TC 25-8. The contractor shall define and maintain a HW and SW system baseline for the DAGIR system in accordance with the DRTS performance specification (PRF-PT-768), IPUR performance specification (PRF-

PT-765), DMT performance specification (PRF-PT-767), and VSS performance specification (PRF-PT-769) IAW TC 3-20.31. The contractor shall utilize Government developed and owned control system/SW, which will be provided by the Government DRTS Integrated Development Environment (IDE) Lab.

3.1.1.1 Operations Control Facility Preparation

The contractor shall integrate the DRTS control suite and AAR system to the CT infrastructure, prepare the CT for installation of the DRTS control suite and AAR systems with any infrastructure or extra instrumentation system components (i.e.

enterprise Uninterruptible Power Source (UPS)). Any DRTS design requiring a change to the DAGIR shall be presented at the Technical Design Review (TDR) for Government concurrence/ approval. All connections between DRTS and the DAGIR’s utility and grounding points shall be provided IAW applicable codes and regulations.

3.1.1.2 Range Preparation and Definition

The contractor shall coordinate with and provide technical support to the Government construction contractor tasked with range preparation. The contractor shall define and provide to the Government all required modifications and additions to the site in preparation for the installation of the DRTS.

Site Preparation

3.1.2.1 On-Site Responsibilities

The contractor shall report to the on-site Government representative/PCO as soon as possible, but not later than the next business day, after any damage or accidents.

Government Furnished Property (GFP)

3.1.3.1 Government Furnished Information (GFI)

The following GFI will be provided as part of this effort:

a. US Army CoE Ft Knox DAGIR Data Package will include Contractor Built Prints (Delivery at Contract Award), and As Built Drawings (Delivery 30 – calendar days after BOD). These drawings are delivered as is. PEO STRI is not responsible for any discrepancies found within the drawings.

b. Live Training Transformation (LT2) Sight SW will be available for the contractor to obtain 30-calendar days prior to the In-Plant Testing/Demonstration date.

c. DRTS SW (LT2 Version) can be obtained by the contractor 30–calendar days prior to the contractor lab scheduled test date).

Range Equipment The following Range Equipment (RE) will be available to the contractor at the range.

The contractor shall install and integrate the RE a-c below, but integrate the RE d-f below into the DRTS:

a. SINCGARS radios (Delivery 90-calendar days after contract award).

b. BFT 2 (Delivery 120-calendar days after contract award).

c. BES II

d. AWSS

e. Field Cameras

f. FASIT Compliant Targetry (Capable of lifting frontal and flank silhouettes).

3.1.4.1 BES II Installation and Procurement

The contactor shall procure and install BES II shelves, one each per BES II device (to include the MATs). The BES II shelf should support a BES II unit, which is 17.91” wide, 26.63” long, 8.84” high, and weighs 72lbs. The contractor shall install and integrate the BES II into the targets and DRTS, to include connecting to power and data. The contractor shall procure any additional cables and/or connectors needed.

3.1.4.2 AWSS Communication Network Installation and Procurement The contractor shall procure, install, and verify the communication network between the AWSS and DRTS CT. The contractor shall install Amphenol connectors for all SATs and MATs, but not responsible for installing AWSS equipment (i.e. brackets, radar, acoustic).

3.1.4.3 BFT 2 Installation and Integration

The contractor shall install and integrate the BFT 2 into the DRTS to include any equipment required to capture the BFT 2 screen data and make it available for the AAR.

3.1.4.4 Field Camera Integration Requirements

The contractor shall complete integration and test of the field cameras into the DRTS system. The field camera integration activities shall include:

a. Verify video display.

b. Verify Pan, Tilt, Zoom (PTZ).

c. Create and verify presets.

d. Verify video recording.

e. Verify audio recording.

f. Verify operation in a scenario.

3.1.4.5 UAS Integration Efforts

The contractor shall integrate the DRTS UAS solution IAW the approved UAS Core Asset Change Proposal (CACP) (C2P0864) and the UAS/LT2 Interface Control Document (ICD) to ensure proper communication is established between the DRTS CT and the UAS Universal Ground Control Station (UGCS). The UGCS will be unclassified and not require a cross-domain solution. The contractor shall submit a request to the Government for use of the UGCS within 120 days of any on-site testing event.

System Requirements The following requirements provide additional clarification for the implementation of the Ft Knox DAGIR. The contractor shall:

a. Integrate and verify the required computing and networking components to support the deployment of a permanent AWSS solution.

b. Install, integrate, and verify BES II devices. One BES II is required per each MAT and SAT.

c. Provide necessary spares, consumables, special tools and test equipment.

The spares equipment package determination shall utilize Reliability, Availability, and Maintainability metrics in conjunction with the Mean Time to Repair, and Mean Time Between Failure requirements.

d. Provide the capability to install or relocate SITs at all the façade locations.

e. Provide a commercially available DVD player capability at each of the two

Presentation Workstation (PWS) computers. The DVD player shall be physically available at the podium and fully controlled by the PWS computer.

f. Provide any non-LT2 SW assets to include installation, configuration, and verification support to the IDE DRTS Lab located on Research Parkway, Orlando, FL.

g. Perform a thorough analysis, testing, and risk assessment where wireless Local Area Networks are to be implemented, to determine the risk of information interception/monitoring and network intrusion prior to installation of these devices.

Software Requirements

The DRTS baseline SW (LT2 Version) will be provided by the Government as GFI. The contractor shall test, to the maximum extent possible, the software baseline during In- Plant Testing prior to installing the software at the range on the DAGIR IT system. The contractor shall fully test the software baseline at the range regardless of the In-Plant testing results.

3.2 Program Management (PM)

The contractor shall provide overall program management and administrative support to ensure the requirements of this SOW are accomplished. The contractor shall implement proactive partnering processes with the Government concerning all aspects of the design, development, production, integration, installation, training, and testing.

The contractor shall monitor and track key cost, schedule, performance, risks, and supportability metrics on a monthly basis and notify the Government of any issues or concerns that arise. The contractor shall track metrics showing how the requirements of this SOW influenced and was integrated into the Hardware Product Line (HPL) as a whole. The contractor shall track and maintain resources to ensure overall programmatic performance.

A001: DI-MGMT-81928 - Contractor’s Progress and Status Report

Management Review The contractor shall:

a. Conduct quarterly Program Management Reviews to provide the Government the current status and outstanding issues. These reviews shall:

1) Include the entirety of the DRTS activities being completed, and status reviews for cost, schedule, and performance of all affiliated DRTS activities.

2) Provide updates to the risk management planning, obsolescence planning/execution, and cost status.

b. Provide visibility on the progress, performance, and status of major subcontractors.

c. Provide meeting minutes, document action items, coordinate resolutions, and track action items until closure.

3.2.1.1 Post Award Conference

The contractor shall host a Post Award Conference at the contractor’s facility within 10-calendar days after contract award. The conference shall introduce the key Integrated Product Team (IPT) participants, identify POCs and discuss both parties understanding of the scope of work and other contract issues.

3.2.1.2 Technical Interchange Meetings (TIMs)

The contractor shall support TIMs after contract award. The contractor shall propose the required TIMs and frequency for each TIM. TIMs shall be held at the contractor’s facility unless a location change is mutually agreed to in advance by both the Government and the contractor. The contractor shall prepare and lead the TIMs.

Integrated Product Teams (IPTs) The contractor shall materially participate, provide membership, and assume various roles to include leadership/management roles, as coordinated with the Government, for bi-weekly (every other week) IPT meetings. IPT meetings shall address program status, issues, installation/integration/testing status. IPT membership shall consist of multi-functional stakeholders working together with a product-oriented focus and be empowered to make critical life cycle decisions regarding each product or process within their purview. IPTs shall be applied at various levels ranging from the overall structure of an organization to informal groups functioning across existing units.

Program Schedule The contractor shall develop and maintain a schedule that shows planned efforts to achieve each significant accomplishment. The contractor shall generate and maintain an Integrated Master Schedule (IMS) to include schedules of the activities required to execute the tasks of this SOW. The contractor shall ensure that the IMS remains current. The contractor shall also generate and make available a monthly one page high level milestone schedule that provides key dates i.e., in-plant testing, site installation, integration, System Technical Test (STT), SOT, New Equipment Training (NET), ICS, Cybersecurity (CS) events, and other identified milestones. The contractor shall update the IMS after any major Baseline Change Request.

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

RESERVED

A003: RESERVED

Computer Hardware, Enterprise SW Solutions (CHESS):

The contractor shall comply with the Army’s CHESS program. Under PEO Enterprise Information Systems, CHESS is the mandatory source for commercial IT purchases.

The CHESS contract provides IT products and services that comply with Network Enterprise Technology Command and Army/DOD policy and standards. Purchasers of commercial HW and SW must satisfy their IT requirements by utilizing CHESS contracts and DOD Enterprise SW Initiative agreements first, regardless of dollar value.

Any purchase made outside of CHESS contracts requires an approved waiver. A complete list of CHESS contracts and the on-line waiver process can be found at https://chess.army.mil.

RESERVED

Risk Management The contractor shall conduct risk management assessments to systematically control the uncertainty in the project’s ability to meet cost, schedule, and performance objectives. The contractor shall ensure that the program interdependencies are highlighted and the risks are monitored on a continuous basis. Risk management shall be covered at all program and technical reviews, and at any time the contractor identifies a potential impact to cost, schedule, or performance. The contractor shall use their internal risk management tools to perform risk management.

Deviations and Waivers The contractor shall document the rationale and obtain approval from the PCO before deviating from any Government-controlled baseline.

https://chess.army.mil/ https://chess.army.mil/

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

3.3 Engineering

Systems Engineering The contractor shall utilize existing System Engineering techniques to ensure a complete baseline description for the Fort Knox DAGIR solution. The systems engineering processes shall consider hardware, firmware, and software in the baseline, and ensure all performance requirements are fulfilled.

The contractor shall decompose the system requirements into a requirements traceability verification matrix. The requirements shall be delineated as hardware or software systems. The matrix shall identify all components as existing, new, and replacements within the baseline. The matrix shall support the design process, and shall be utilized to identify required trade-off determinations. The matrix shall show dependencies between the HW and SW requirements, and the cascade effects of new components. These requirements shall be the basis for the generation of a test/demonstration plan.

A005: DI-MGMT-81024 - System Engineering Management Plan A006: DI-MGMT-82133 - Requirements Traceability Verification Matrix (RTVM)

Product-Line Engineering The contractor shall utilize to the maximum extent possible the Live Training Transformation Product-Line Governance and standards for both hardware and software components.

3.3.2.1 HPL Analysis

The contractor shall utilize the existing LT2 HPL components for any new hardware added to or modified within the existing DRTS baseline. The contractor shall assess the HPL components against the requirements to fulfill the requirements of the performance specifications. The contractor shall follow the LT2 Governance and submit any new hardware components to the HPL.

The contractor shall adhere to the LT2 Governance and processes for any software modifications required to ensure a fully operational system.

System Design and Definition

The contractor shall utilize the existing system and subsystem specifications and design documents to establish a system design and definition baseline. This baseline shall be reviewed in depth at the TDR. The contractor shall maximize the use of COTS and HPL solutions in the design and shall ensure/provide multiple sources for each new component added to the existing baseline. The contractor shall associate the design elements to the RTVM. The contractor shall:

a. Utilize the reference documents listed in paragraph 2.3 as the basis for development of all lower level specifications.

b. Perform trade-off studies and then finalize the system design. Commercial-off-the-Shelf (COTS) items shall be used when possible.

c. Provide multiple sourcing options when selecting these items. Selected designs and specifications shall be based on performance, CS, TOC, Life Cycle Product-line Management, and HPL goals, and upgrade potential.

d. Establish the definition of the system with a focus on system products required to satisfy operational capabilities.

e. Complete the system, subsystems, interface requirements, and verification definition.

A007: DI-IPSC-81432A - System/Subsystem Design Description (SSDD)

SW Engineering The contractor shall utilize agile software development techniques for any new software components developed, or for any software component modifications in conjunction with their established CMMI Level 3 software practices. The contractor shall not utilize any proprietary software or software requiring reoccurring license expenses. All SW requirements required for PU shall be accomplished through the latest Sight SW baseline available in the LT2 portal. The contractor shall install, integrate, and configure the SW to test the system as a whole. The contractor shall use latest approved Operating Systems within the LT2 Portal.

The contractor shall utilize their own facilities for all SW integration and contractor testing. The contractor shall coordinate with the Government team and submit the SW baseline to the DRTS IDE lab for certification. This certification testing shall be completed prior to the deployment of the SW to the range. This certification process is only required if SW modifications are incorporated into the baseline.

The contractor shall deliver the final software and documentation IAW LT2 requirements. Provide the Government a complete image (or images) of the system, including but not limited to, the SVD, SW, firmware, configurations, and site specific data, capturing all SW and configurations to be used for off-site storage in support of disaster recovery upon completion of SOT (to be left at the site). Provide a second copy of all imaging for the PEO STRI IDE Lab.

A008: DI-IPSC-81442A - Software Version Description (SVD) A009: DI-MCCR-80700 - Computer Software Product End Items

Product Definition Data (PDD) The contractor shall develop, produce, and maintain PDD IAW MIL-STD-31000B and shall accurately depict the final product of the fielded system. The PDD is the technical description of items adequate for supporting an acquisition strategy, integration, engineering and logistics support.

B001: DI-SESS-81000E - Product Drawings/Models and Associated Lists (PDAL) (Refer to Annex to Exhibit B for specifically tailored drawing requirements)

System Integration The contractor shall perform all activities involved with integrating and assembling the HW and SW to achieve a system that fulfills the performance requirements and specifications. The contractor shall conduct a system level requirements review utilizing the RVTM during TDR and in-plant testing to determine that the total system has been considered.

3.3.6.1 Comprehensive Range Radio Frequency (RF) Analysis

The contractor shall ensure the appropriate types, number, and location of RF devices are incorporated into the design and implementation. The comprehensive range RF analysis shall be applicable to all system components that use RF for their functionality.

A010: DI-MISC-80711A - Scientific and Technical Report - RF Coverage

3.3.6.2 Spectrum Management

The contractor shall ensure compliance with the policies and procedures for the Army Frequency Allocation to Equipment (Army J/F-12) Program as described in AR 5-12, Chapter 4 for any system that operates in an electromagnetic spectrum. The Contractor shall assist in obtaining an approved DD Form 1494 (Application for Equipment Frequency Allocation) and ensure that the equipment can operate in spectrum bands per the national and international tables of spectrum allocation. The contractor shall integrate existing Army approved spectrum/Electromagnetic Compatibility (EMC) HW and SW tools into system procurements. All coordination with the Army Spectrum Management Office will be conducted through PEO STRI’s CIO and DRTS lead engineer.

Configuration Management (CM) The contractor shall perform CM IAW the LT2 Operations Guide and LT2 Product Line CM Guide.

Quality Assurance (QA) and Quality Control (QC) The contractor shall implement and synchronize an overarching QA program to ensure that the requirements being tracked in the RTVM are met. The QA program shall focus on the entire quality system including suppliers and consumers. It shall include all activities designed to produce products and services of appropriate quality. The contractor shall include all activities designed to produce products and services to meet requirement. The contractor shall implement a QC Plan for the activities used during production and integration efforts of a product, which shall be designed to verify that the product meets the requirements.

The contractor shall develop metrics and host on LT2 portal to assist management visibility into an adequate process control system. The contractor shall utilize the existing Jira SW discrepancy tracking system identified in the LT2 Operations Guide.

The contractor shall establish a suspense system to ensure timeliness of analysis and corrective actions for discrepancies and risk reduction. The contractor shall document and integrate all discrepancy corrections in the systems’ database.

A011: DI-QCIC-81794 - Quality Assurance Program Plan

Engineering Change Proposal (ECP) The contractor shall identify and document all proposed changes to the established baselines for review by the IPT. The contractor shall ensure all changes are approved by the Government PCO prior to implementation.

In coordination with the Government, the contractor shall hold a requirements review on all proposed changes prior to the submittal of the ECP 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, or a formal meeting. All appropriate parties shall attend in order to conduct a thorough and effective review. Minutes from each meeting shall be taken by all parties and compared to allay any miscommunications. The contractor shall compile all meeting minutes and provide to the Government.

A012: DI-SESS-80639D - Engineering Change Proposal (ECP)

Safety Engineering The system design shall incorporate the guidelines established in MIL-STD-882E. The contractor shall conduct safety analyses, hazard identification/classification, and hazards tracking integral to the system effort. The contractor shall present all safety considerations and mitigations at the TDR.

The contractor shall ensure that safety of the design is achieved and that all system specific safety requirements are met. This shall include verifying any changes due to redesign. Once complete, the contractor shall verify the safe design of the system and to determine the safety risk assumed prior to test or operation.

The contractor shall implement a method to track hazards to ensure that all hazards are assessed, that proper program managers and IPT personnel are notified, and that each hazard is tracked until final resolution.

A013: DI-SAFT-80102C - Safety Assessment Report A014: DI-SAFT-80106C - Health Hazard Assessment Report (HHAR)

Technical Design Review (TDR) The contractor shall host a Technical Design Review for the purpose of assessing technical progress. The contractor shall document the results of the review, including any resulting action items. The review shall accomplish the following:

a. Assess the system requirements and allocations.

b. Present the risks associated with the development effort.

c. Data to support a determination to proceed.

The TDR is a multi-disciplined product and process assessment to ensure that the system can proceed into system fabrication, demonstration, and test, and can meet the stated performance requirements within cost (program budget), schedule (program schedule), risk, and other system constraints. Entry into the TDR shall be mutually agreed to by the Government and contractor teams.

The contractor shall conduct the TDR within 30-calendar days after contract award.

This TDR shall be considered complete when the System/Subsystem Design Description has been approved.

A015: DI-MISC-80711A - Scientific and Technical Report - Technical Design Review

3.4 Test and Verification

The contractor shall ensure the RTVM supports the development of a comprehensive test and evaluation strategy by mapping each requirement to one or more verification events. The contractor shall document and record any and all problems/failures that arise during the verification events. The contractor, along with the Government, shall document these problems/failures in Test Incident Reports (TIR), and the contractor shall utilize a TIR tracking tool to capture the information for classification and chargeability, trend analysis, and closure. The contractor shall support daily Scoring Conferences for each verification event. The contractor shall ensure that lessons learned, test voids, ambiguities, and test tolerance discrepancies are incorporated into diagnostic HW, SW, Operator User Manuals (OUMs), and System Maintenance Manuals (SMMs). The contractor shall define, within the maintenance manual, an approach to determine how Built-In Test (BIT) results are evaluated for both HW and

SW.

The contractor shall include a comprehensive test and evaluation plan for the IPUR if a previously validated solution is not pursued as part of the technical approach, to include all environmental, EMI, and performance verifications from the IPUR specification. The contractor shall implement these tests across the in-plant, technical and operational testing events as appropriate.

A016: DI-NDTI-80566A - Test Plan

Test Readiness Review (TRR) The contractor shall conduct a TRR 3 calendar days prior to the start of any Government witnessed test event. The TRR shall assesses test objectives, test methods and procedures, scope of tests, and determines if required test resources have been properly identified and coordinated to support planned tests. The TRR shall also verify the traceability of planned tests to program requirements. The TRR shall address/ensure the following Entrance Criteria are met:

a. System configuration has been baselined, documented, and accepted into Configuration Management.

b. Defect Tracking Method has been established.

c. Approved test plans, cases, and procedures are available.

d. Critical and Major TIRs have been closed. If there are critical or major TIRs outstanding, a waiver from the Government will be required for testing to proceed.

e. All known system discrepancies have been identified.

f. All required test resources have been identified.

g. DD 1494 (J/F 12) Application for Equipment Frequency Allocation approved

(as required).

h. Interim Authority to Test (IATT) approved (as required).

The TRR shall address/ensure the following Exit Criteria are met:

a. Test event is completed

b. Problems found during testing are documented via TIRs.

c. All Critical and Major TIRs found in test event have been closed. If there are critical or major TIRs outstanding, a waiver from the Government will be required to exit testing event.

In-Plant Testing

The contractor shall conduct in-plant verification tests to demonstrate complete functional capabilities of the system (i.e. HW/SW testing utilizing audio, video, player unit, and targets simulators). The in-plant testing event is a formal government witnessed testing event, and is aimed at assessing the adequacy of the system to fulfill the requirements.

The contractor shall identify and request any additional Government equipment required to support the in-plant testing at least 60 working days prior to the start of testing.

Contractor Test The Contractor Test (CT) is an on-site test where the contractor tests the system. The CT is a Government witnessed test event. During the CT the initial and comprehensive requirements are tested using the test procedure in preparation for the System Technical Test (STT). The contractor shall conduct CT after the installation and integration of all system components, to include all RE.

System Technical Test (STT) The System Technical Test is an on-site test where the contractor and the Government representatives test the system. During the STT the initial and comprehensive requirements are tested using the test procedure. The STT is conducted before SOT to ensure the system is ready to be tested by the Government.

The contractor shall conduct STT after the completion of the CT and the STT TRR. The STT shall include system cold start, start-up and shut-down, and software recovery.

The STT shall include a system functional and performance testing on the entire integrated system. The contractor shall test all the Performance specs requirements within the STT.

The STT shall include the following testing to ensure full coverage of the requirements:

a. Auto-Start and Shutdown System Test, including all server room device status.

b. Clear-Com and SINCGARS radio check testing.

c. Dismounted Tracker coverage testing to ensure full range coverage.

d. Handheld Target Controller (HTC) testing.

e. Computer System and Network test (SYSCOM).

f. SYSCON functionality testing to include target manipulation and fault clearing and BES II Testing.

g. IPUR coverage testing to include all course roads and battle position.

h. Complete VSS Testing to include all video functionalities as well as Field Camera presets.

i. IPUR radio network nodes Saturation Testing to ensure that each node can withstand heavy loads without crashing the system.

j. System Saturation and Endurance Testing for Ground Vehicles (Stress Test).

k. System Saturation and Endurance Testing for AWSS to include manned and unmanned aircrafts. These stress tests can be perform with the help of testing devices (i.e. audio-video injectors into IPUR, AWSS simulators, UAS simulators).

l. Test functionality of all targets.

The contractor shall identify and request any additional Government equipment, resources (i.e. vehicles, ammunition, etc.), required to support the SST at least 120 working days prior to the start of testing.

A017: DI-NDTI-80603A - Test Procedure A018: DI-NDTI-80809B - Test/Inspection Report

System Operational Test (SOT) The System Operational Test is the final acceptance of the system prior to fielding. The focus of the SOT is to perform an end-to-end testing; everything from scenario development, creating and executing training events/runs through qualification and collective AARs to include IPUR video in-gestation and THPs. The Government will conduct the SOT, on-site, using tactical vehicles under a live-fire environment to emulate an abbreviated training cycle. The SOT activities will be conducted in the same manner as they would be during operational use. The contractor shall provide a minimum of 3 printed paper copies of all the documents and certification credentials (e.g., TIR, Test Plan). The contractor shall provide appropriate personnel support required for SOT.

A017: DI-NDTI-80603A - Test Procedure A018: DI-NDTI-80809B - Test/Inspection Report

3.5 Government Acceptance

Government acceptance shall be based upon successful completion of the System Operational Test, correction of all TIRs, delivery of complete and accurate inventory, delivery of verified and validated system OUM and SMMs, RMF documentation, delivery/acceptance of system drawings, and delivery of the final SW/ documentation.

Once the above items are complete, the Government team will provide a recommendation to accept the system.

3.6 Cybersecurity (CS)

a. Integrate CS into their management processes, document any issues that arise during installation, identify possible solutions, and seek waiver with PCO approval before implementing changes.

b. Ensure all components are delivered in a certifiable configuration for a Closed Restricted Network Type IV and all required security controls are effectively implemented IAW DODI 8500.01, DODI 8510.01, CNSSI No.

1253, NIST SP 800-53, DODI 8582.01, AR 25-2, DRTS ATO, and System RMF Implementation Plan.

c. Leverage the National Information Assurance Partnership and the Common Criteria Evaluation and Validation Scheme to ensure Defense Information Systems Agency (DISA) approved SW and HW are utilized.

d. Deliver upgrades to the system in a configuration that will pass an RMF authorization and not negatively impact the existing ATO authorization.

e. Ensure the efforts performed under this contract apply the appropriate CS considerations in the decision making process.

f. Ensure the system remains compliant with the DRTS RMF Implementation Plan, SSP, and RMF baseline documentation. The Government will provide CS documentation of the existing accreditations for inclusion of the data into the new RMF package. The contractor shall develop or update documentation as required.

g. Leverage LT2 CS processes and procedures to the maximum extent possible to ensure a common approach across PM ST.

h. Scan the system as part of this compliance using the latest DOD approved scanning tools. Each revision shall include a CS compliance scan as part of the IOC.

i. Provide CS compliance scan results of the hardened system no later than 5-calendar days after the completion of in-plant testing.

j. Work with LT2 CS personnel to coordinate a transition to Government IDE Lab for CS and Post Deployment Software Support and CS sustainment.

k. Submit any updates to the RMF Authorization documentation as required due to system configuration changes.

A019: DI-MISC-80711A - Scientific and Technical Report: DOD Risk Management Framework (RMF) Package Deliverables

CS Artifacts

a. Comply with the CS process IAW DOD 8510.01 RMF for DOD IT, CNSSI No. 1253, NIST SP 800-53, AR 25-2, and PEO STRI guidance.

b. Produce all components of the RMF package specific to the Ft. Knox site implementation including HW/SW lists and CS compliance scans.

c. Ensure that the CS requirements and procedures are met IAW all required DOD and Army regulations per the Confidentiality, Integrity, and Availability levels specified for the system. All CS artifacts shall be stored on LT2.

3.7 Security

The contractor shall be in compliance with the security regulations and security requirements specified in Contracts Security Classification Specifications, DD Form 254 and addendums sheets. The contractor will be required to have a SECRET facility clearance with no storage requirements.

Handling or Access to Classified Information The contractor shall comply with FAR 52.204-2 Security Requirements. This clause involves access to information classified Confidential, Secret, or Top Secret. The contractor shall comply with Security Agreement (DOD Form 441), including the National Industrial Security Program Operating Manual (DOD 5220.22-M) and any revisions to DOD 5220.22-M.

Access and General Protection 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 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.

Credentialing The Common Access Card (CAC) shall be the principal identity credential only for those contractor employees supporting and requiring access to DOD installations, Government leased facilities, buildings and Government information systems per FAR 52.204-9.

The prime and subcontractor shall coordinate with their Government sponsor and complete DD Form 1172-2 in order to obtain a CAC. The prime and subcontractor employee will be issued a CAC only if duties involve one of the following:

a. Require both physical access to a 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 6 months or more.

The prime and subcontractor employees shall, at a minimum, have a favorably adjudicated Tier 1 or an equivalent or higher investigation in accordance with Army Directive 2014-05. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled T1 at the Office of Personnel Management.

The contractor shall ensure that all employees clearly display the prescribed identification at all times while they are working within Government facilities and performing official duties in execution of contract requirements.

The contractor shall account for all forms of Government-provided identification credentials issued to contractor (or their employees including subcontractor employees in connection with performance) under the contract. The contractor shall return such identification credentials to the issuing agency at the earliest of any of the circumstances listed below, unless otherwise determined by the Government. The contracting officer may delay final payment if the contractor or subcontractor fails to comply with these requirements. The contractor shall return all identification credentials when:

a. No longer needed for contract performance.

b. Completion of contractor employee’s employment.

c. Contract completion or termination.

The contractors and all associated subcontractor employees that do not require CAC, but require access to a DOD facility or installation, shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index and Terrorist Screening Database (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).

Contractor personnel shall possess the required security level clearance (prior to assignment to a specific task and work site in order to effectively perform assigned work. In order to obtain a security clearance, the following website is provided to assist you (Defense Security Service Website (https://www.dcsa.mil/) National Industrial Security Program Operating Manual (DODM 5220.22)).

Security Training The contractor shall read and execute the below listed security training for contractor employees who have security clearances and who are working on DOD contracts.

3.7.4.1 Threat Awareness Reporting Program (TARP)

All contractors and subcontractors with security…