Attachment_7.1_LCPM_DO_0002_IMTS_SOW.pdf

SOW-2017-032

19 April 2017

Version 1.0 i

STATEMENT OF WORK

FOR THE

Continuous Technology Refreshment for the

Integrated - Military Operations on Urbanized Terrain Training Systems

Delivery Order 0002

U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI)

12350 Research Parkway Orlando, FL 32826-3276

Engineering Prepared By: ____________________ Concurrence: ____________________ Christopher Windler James Griffith Systems Engineer, PD DT Deputy Product Director Digitized Training Date: _________ Date: __________

Acquisition Logistics Prepared By: ____________________ Concurrence: __________________ Mac Baker Roberto Capote Lead Acquisition Logistician, PD DT Life Cycle Acquisition Mgr., PM TRADE Date: ___________ Date: ___________

Program Management Submitted By: ____________________ Approved By: ____________________ Dave Stewart Mike Willoughby Assistant Product Manager Product Director Digitized Training Date: __________ Date: _________

GRIFFITH.JAMES.R

GROSSE.12290423

Digitally signed by GRIFFITH.JAMES.R

GROSSE.1229042340

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USA, cn=GRIFFITH.JAMES.R

GROSSE.1229042340

Date: 2017.04.19 13:34:03 -04'00'

WINDLER.CHRI

STOPHER.JOH

N.1081242700

Digitally signed by

WINDLER.CHRISTOPHER.JOHN.1081242700

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USA, cn=WINDLER.CHRISTOPHER.JOHN.1081242700 Date: 2017.04.24 09:04:19 -04'00'

BAKER.MCARTH

UR.1056380686

Digitally signed by BAKER.MCARTHUR.1056380686 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USA, cn=BAKER.MCARTHUR.1056380686 Date: 2017.04.24 14:40:54 -04'00'

STEWART.DAVI

D.L.1230433824

Digitally signed by

STEWART.DAVID.L.1230433824

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USA, cn=STEWART.DAVID.L.1230433824 Date: 2017.04.24 15:01:28 -04'00'

WILLOUGHBY.MICH

AEL.B.1229903779

Digitally signed by

WILLOUGHBY.MICHAEL.B.1229903779

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USA, cn=WILLOUGHBY.MICHAEL.B.1229903779 Date: 2017.04.24 16:08:25 -04'00'

CAPOTE.ROBER

TO.1031558618

Digitally signed by

CAPOTE.ROBERTO.1031558618

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USA, cn=CAPOTE.ROBERTO.1031558618 Date: 2017.05.09 10:34:28 -04'00'

Version 1.0 ii

1.0 Scope

1.1 Introduction

1.2 Goals

1.3 Background

1.4 Objective

1.5 Definitions

2.0 Applicable Documents

2.1 Department of Defense Directives

2.2 Availability of Department of Defense Directives

2.3 Other Government Documents, Drawings and Publications

2.4 Industry Standards

2.5 Availability of Government Documents, Drawings and Publications

2.6 Order of Precedence

3.0 Requirements

3.1 Program Management

3.1.1 Management Activity

3.1.2 Program Schedule

3.1.3 Integrated Product Team (IPT)

3.1.4 Configuration Management (CM)

3.1.4.1 Configuration Identification (CI)

3.1.4.2 Configuration Change Management

3.1.4.3 Configuration Status Accounting

3.1.4.4 Configuration Verification and Audit

3.1.4.5 Software Configuration Control Board

3.1.4.6 Engineering Change Proposal (ECP) and Contract Change Proposal (CCP)

3.1.4.7 Engineering and Contract Change Proposal Review

3.1.5 Program Reviews

3.1.5.1 Technical Interchange Meetings (TIM)

3.1.5.2 Management Reviews

3.1.5.3 Site Survey

3.1.5.4 Legacy Test

3.1.5.5 Start of Work Meeting

3.1.5.6 Technical Design Review (TDR)

3.1.5.7 Test Readiness Review (TRR)

3.1.6 Contract Invoicing and Payment

3.1.7 Subcontractor Management

3.1.8 Contract Manpower Reporting

3.1.9 Metric Tracking

3.1.10 Facilities and Labs

3.1.11 Data Development

3.1.12 Computer Hardware, Enterprise Software Solutions (CHESS) Program

3.1.13 Associate Contractor Agreements (ACA)

3.1.14 Risk Management

3.1.15 Access and General Protection Policy and Procedures

3.1.16 Operations Security (OPSEC) Program

iii

3.1.16.1 Antiterrorism Threat (AT) Awareness Level 1 Training

3.1.16.2 Credentialing

3.1.16.3 AT Awareness Training for US Based Contractor Personnel Traveling Overseas ... 18

3.1.16.4 iWATCH Training

3.1.16.5 Army Training Certification Tracking System (ATCTS) Registration for Contractor

Employees Who Require Access to Government Information Systems

3.1.16.6 OPSEC Program

3.1.16.7 Requirements for OPSEC Training

3.1.16.8 Cybersecurity / Information Technology (IT) Training

3.1.16.9 Cybersecurity / IT Certification

3.1.16.10 Threat Awareness Reporting Program (TARP)

3.1.17 Cybersecurity (Information Assurance)

3.1.18 Security Control Assessment (SCA)

3.1.19 Government Furnished Information (GFI)

3.2 System Engineering

3.2.1 Hardware Engineering

3.2.2 Product Definition Data (PDD)

3.2.3 Test Engineering

3.2.4 System Integration

3.2.5 Common Training Instrumentation Architecture Program Interface

3.2.6 LT2 Product Line Interface and Support

3.2.7 Software Engineering

3.2.8 Safety

3.2.9 Testing

3.2.9.1 In-Plant Testing/ Demonstration

3.2.9.2 Contractor Test

3.2.9.3 Government Acceptance Test

3.2.9.3.1 Functional Testing

3.2.9.3.2 Physical Configuration Audit

3.2.9.4 Acceptance by the Government

3.2.10 Supportability Engineering

3.2.11 Reliability and Maintainability (R&M) Engineering Program

3.2.12 Manpower and Personnel Integration (MANPRINT)

3.2.13 Quality Assurance (QA) and Quality Control (QC)

3.3 Synchronization Initiatives

3.3.1 Synchronization with LT2

3.3.2 Synchronization with PDSS

3.3.3 Synchronization with the LCCS (WFF and ATMP)

3.3.4 Data Rights

3.4 Logistics

3.4.1 Supportability Analysis and Logistics Product Data

3.4.2 Inventory Support

3.4.3 Initial Spares

3.4.4 Technical Publications

3.4.4.1 Publications in Process Reviews (IPRs)

3.4.4.2 Technical Publication Validation

iv

3.4.4.3 Technical Publication Verification

3.4.4.4 New Equipment Training (NET)

3.4.4.5 NET Verification

3.4.5 Interim Contractor Support (ICS)

3.4.6 Transition to Life Cycle Contractor Support

3.4.7 Item Unique Identification (IUID)

3.5 Existing Government Facility

3.6 Removal of Legacy Equipment

3.7 Packing, Storage, and Transportability

3.8 Disposal

v

REVISION LOG

Date Version Revision

Description

10/31/2016 1 Initial Version for Draft RFP

04/19/2017 1.0 Updated version to reflect comment and changed document number.

Final RFP SOW

STATEMENT OF WORK

Continuous Technology Refreshment (CTR) for the Integrated - Military Operations on

Urbanized Terrain (MOUT) Training Systems (I-MTS)

1.0 Scope

This Statement of Work (SOW) defines the work required to be performed for the Project

Manager Training Devices (PM TRADE) within the Life Cycle Product-line Management

(LCPM) contract. This effort shall utilize the Live Training Transformation (LT2) Product Line

(P/L) which consists of the Software P/L and the Hardware Product Line (HPL), once it is populated, in support of the tasks described in this SOW to perform a CTR for the I-MTS program. CTR is defined as the systematic evaluation and evolution of hardware components within the defined configuration, which supports form, fit, and function while achieving improved performance, enhanced capabilities, alignment to future standards, and/or lower total ownership costs. The CTR includes but is not limited to the design, fabrication, production, integration, installation, verification, testing, training and documentation for the I-MTS program's requirements of the Combined Arms Collective Training Facilities (CACTF) and the

Automated Shoot House (ASH).

The contractor will develop, procure components and integrate with existing legacy equipment.

The main overarching functional areas involved will be the design, fielding, and sustainment of

MOUT training sites.

The effort will use Government-owned software and existing documentation to satisfy the I-MTS capabilities/requirements, extend the operational life of I-MTS systems, and support training.

The effort will include various types of processes and procedures in the execution of this effort including Engineering, Manufacturing, Hardware and Software Integration, Quality Assurance, Quality Control, Technology Insertion, Logistics Analysis, Logistics Support, Test, Program

Management, Integrated Master Schedule, Contract Management, Interim Contractor Support, Deployment, Horizontal Integration, and Information Assurance.

As part of this effort the contractor will develop, integrate, and procure components to reduce

Total Costs (TC), increase software reuse, increase technical data reuse, promote component commonality, and enhance interoperability through the CTR process at the following locations:

For CACTF sites:

1- Ft. Stewart, GA

2- Ft Indiantown Gap, PA

3- Ft Drum, NY *

4- Ft Polk, LA

*Fort Drum has multiple unique characteristics that are detailed in the site survey report

For ASH sites:

1- Ft Stewart, GA

2- Gowen Field, ID

3- FT Bragg, NC

4- Cp Shelby, MS

5- Cp Bullis, TX

The Government will provide copies of available facility construction drawings, engineering drawings of the current instrumentation system, Operator and Maintenance manuals, and fielded

Equipment Inventory Records for the current configuration. Any additional system capability that was provided by the site that is not an I-MTS requirement defined in this document or the performance specification shall not be proposed. These capabilities will be discussed after

Contract Award and, if authorized by the Government, shall be proposed as Engineering Change

Proposals.

1.1 Introduction

The intent of I-MTS is to provide urban training solutions, which fulfill specified aspects of individual, collective, and combined arms training requirements. I-MTS also addresses other-than-war operations (such as peacekeeping missions), homeland defense and anti-terrorism scenarios. I-MTS supports both fixed permanent and non-permanent structure facilities and allows for the addition or expansion to existing facilities and the integration across sites and mission domains (Live, Virtual, and Constructive). I-MTS will immerse the training participants into the realism of the event. I-MTS environment must allow and support flexibility and changing scenarios to prevent learned responses vice learning benefit. I-MTS must include unexpected events for the training audience.

Cameras, microphones, speakers, targets, battlefield effects and network recording systems are combined in an urban operation setting to provide unit commanders with:

a. Real-time audio and video monitoring

b. Scenario generation

c. Exercise recording, reviewing and editing

d. After-Action Review (AAR) capability for the playback of training events

e. Multi-media Take Home Package (THP) to allow the training to be individually viewed later

The instrumentation systems permit units to train and perfect tactics, techniques, and procedures for urban warfare and other related operations.

Combined Arms Collective Training Facility (CACTF) - The CACTF replicates an urban environment. The facility consists of 2.25 square kilometers of urban sprawl with 20 to

26 buildings, roads, alleys, parking areas, underground sewers, parks, athletic fields, and command and control building. The CACTF provides combined arms collective training for platoon and company Situational Training Exercises (STX) and battalion/brigade

Task Force (TF) Field Training Exercises (FTX). The actual size and configuration of the

CACTF depends on the local installation site requirements. The CACTF is designed to support heavy and light Infantry, Armor, artillery, and aviation positioning and maneuver. In addition to the training buildings, the CACTF consists of a Range

Operations Control (ROC) and After Action Review (AAR) facility.

Automated Shoot House (ASH) - The ASH is a modern variant of the Shoot House where the unit can operate the system without a dedicated operator. The ASH provides a facility to train and evaluate a unit during a live fire exercise. Units are trained and evaluated on their ability to conduct tactical movement, engage targets, conduct breaches, room clearing, and practice target discrimination in an urban environment. This facility has two parts, the live fire facility (a single training building) and the ROC/AAR building.

1.2 Goals

This SOW continues to follow the LCPM contract goals to maintain a consolidated approach to

Life Cycle Management (LCM), that proactively addresses all life cycle phases; obsolescence planning, maintaining or improving system performance and operational readiness, ensuring relevancy, and improving system maintenance while reducing total ownership costs and logistics footprint. It supports the intent of the HPL by ensuring standardization, commonality, synchronization, maximum reuse, and interoperability within the PM TRADE’s live training systems. The primary objectives of this effort include:

a. Analyzing current systems design, configuration and implementation.

b. Analyzing existing COTS, Government-Off-the-Shelf (GOTS), and other hardware to determine a set of hardware components that can meet the I-MTS program’s requirements and align with other LT2 programs’ system requirements in order to support the initial establishment of the HPL.

c. Considering an approach that establishes a centralized/distributed (within an installation or potentially off-site supporting multiple installations) capability to accommodate multiple fielded systems and to lower the amount of Information

Technology (IT) required to operate the systems.

d. Synchronizing with established LT2 processes and standards as detailed on the LT2 portal (www.lt2portal.mil)

1.3 Background

To rectify the Army’s shortage of urban training systems for MOUT exercises the I-MTS program has fielded over 120 systems for small unit training up to Brigade level providing numerous locations and scenarios for training. This covers Army, Army Reserve, National

Guard, and DOD sites located both within the continental United States (CONUS) and Outside

CONUS. This also includes Foreign Military Sales (FMS), sales to other countries and to qualified federal, state and municipal agencies. Many of these systems or their subsystems have reached end of life and the program has entered into the CTR phase to keep the systems operational and relevant. PM TRADE will modernize and reduce the IT footprint of these systems through the CTR initiative.

1.4 Objective

This effort will support the business goals of PM TRADE to include:

a. Reducing operational cost & complexity

b. Aligning & supporting product development (common standards, interfaces, etc.)

c. Enhancing soldier training

d. Reducing sustainment & development costs

e. Increasing technology agility http://www.lt2portal.mil/

f. Leveraging other Army systems and Commercial Off the Shelf (COTS) technologies, and aligning to Army Common Operating Environment (COE), mobile computing, and distributed computing strategies

1.5 Definitions

The LT2 product line is defined as the overarching set of tools, processes, governance, architectures, software/hardware components, documentation, standards/interfaces, etc. that are utilized across live training programs to gain cost, schedule and performance efficiencies. Figure

1 shows the relationship between these items.

Figure 1: PM TRADE LT2 Product Line Relationships

The HPL will be compromised of components (i.e. servers, racks, switches, cameras, computers, etc.) and hardware component agreements (HCAs) made up of mainly COTS and GOTS equipment. Once the initial HPL baseline is established, it will be maintained with evolutionary input from the subsequent DOs.

The management of the HPL will be part of the LT2 governance process via the usage and modification of the LT2 Operations Guide. This work will run over the life of the contract and ensure that subsequent DOs utilize the HPL to meet their program’s needs. The HPL will utilize/provide the tools necessary for the sharing of technical and logistics data with the

Consolidated Product-line Management (CPM) Next, Warfighter Focus (WFF) and Army

TADSS Maintenance Program (ATMP) contracts. The HPL also involves the obsolescence, Diminishing Manufacturing Sources/Material Shortages (DMS/MS), and failure rate analysis of the fielded systems to make certain that PM TRADE is aware of any potential issues and can proactively plan for CTR across its programs.

During the initialization of the HPL DO1 will establish an initial HPL as nothing exists today for hardware. During the initialization, DO1 will only look at a subset of training systems’ requirements and fielded sites in order to establish a baseline set of hardware components that will make up the HPL.

The HCAs include the requirements being met by the component, the component’s dependencies, the documentation to operate and sustain the component, and other information associated with the component.

LT2 Synchronization is defined as life cycle management of LT2 products following the LT2 governance processes in accordance with the LT2 Operations Guide and LT2 Product Line

Configuration Management Operational Procedures Guide. In essence, all stakeholders coordinate, design, develop, integrate, test, and maintain all core assets for the LT2 Product Line

(e.g., architectures, common components, services, standards, processes, tools, and data) and deployed/fielded capabilities within the construct of the LT2 tools and processes.

Synchronization includes the identification, description, and tracking of all of the work products, components, and systems as produced under this SOW. Furthermore, synchronization assumes maintenance of component and service level agreements, active monitoring of LT2 configuration management policies, and proactive evolution with the overarching LT2 architectures as they mature and additional architectures and frameworks as required by LT2. Lastly, synchronization includes the implementation and sustainment of inherent processes and oversight to coordinate the activities described in this SOW with the overarching LT2 construct and implementation in order to minimize duplication of efforts and ensure core asset integrity is maintained. This requires the monitoring of LT2 requirements and framework as they mature, and participation in the LT2 working groups [i.e., Core Asset Working Group (CAWG)].

2.0 Applicable Documents

The following documents form a part of this SOW to the extent specified herein. Unless otherwise specified, the documents listed are the latest.

2.1 Department of Defense Directives

DODD 8570.1 Information Assurance Training, Certification and Workforce

Management

DOD 8570.01-M Information Assurance Workforce Improvement Program

DODI 8500.1 Cybersecurity

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

2.2 Availability of Department of Defense Directives

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

2.3 Other Government Documents, Drawings and Publications

CNSSI 1253 Committee on National Security Systems Instruction

(CNSSI) 1253

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

Special Publication (SP) 800-53: Security and Privacy http://www.dtic.mil/whs/directives/

Controls for Federal Information Systems and

Organizations

Army Directive 2014-05 Policy and Procedure for CAC Credentialing and

Installation Access for Uncleared Contractors

AR 25-2 Information Assurance

AR 380-5 Department of the Army Information Security Program

AR 530-1 Operations and Signal Security

CTIA Common Training Instrumentation Architecture

(www.lt2portal.mil)

LT2-TRADE-PLN-000384 LT2 Operations Guide (www.lt2portal.mil)

LT2-TRADE-PLAN-2013-00009 LT2 Configuration Management Operational

Procedures Guide (www.lt2portal.mil)

MIL-STD-882 Standard Practice for System Safety

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

LT2-TRADE-TD-000499 Lifecycle Data Service Interface Control Document (ICD)

MIL-STD-31000 Technical Data Packages

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

Based Technical Manuals

PEO STRI Basic Accreditation Manual (BAM)

PRF-PT-668 I-MTS and CTC MOUT-IS Performance Specification

PRF-PT-00468 Future Army System of Integrated Targets (FASIT) performance specification

MIL-STD-1472 Human Engineering

TR 525-13 Training and Doctrine Command Force Protection Program

2.4 Industry Standards

GEIA STD-0007-B Logistics Products Data

GEIA HB-0007-B Handbook and Guide for Logistics Product Data

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

2.5 Availability of Government Documents, Drawings and Publications

Copies of the documents are available from PEOSTRI, SFAE-STRI-KOL, 12211 Research

Parkway, Orlando, FL 32826, or may be available at: http://assist.daps.dla.mil/quicksearch/ or http://www.lt2portal.org

2.6 Order of Precedence

In the event of a conflict between the text of this SOW and the reference cited herein, the text of the SOW shall take precedence. The contractor shall notify the Government of any conflict so they may address the discrepancy. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

3.0 Requirements

The contractor shall perform all the tasks necessary to complete a comprehensive CTR. The contractor shall design, procure, ship, install, test, certify, document, and provide system operations and maintenance training and support to fulfill the performance requirements of the I-

MTS/CTC MOUT-IS Performance Specification, PRF-PT-668. There are no Non-Standard http://www.lt2portal.org/ http://www.lt2portal.mil/ http://www.lt2portal.mil/ http://assist.daps.dla.mil/quicksearch/ http://www.lt2portal.org/

(N/S) or objective requirements identified in this SOW. The contractor shall develop, procure components, design/integrate with existing legacy equipment with a goal to minimize TC and enhance interoperability for the identified CACTFs, and SHs

The Range Operations Center (ROC) and training building instrumentation encompasses but is not limited to; targets, battlefield effects, data networking, audio video (A/V) monitoring and recording, exercise control, and AAR presentation and Take Home Package (THP) creation. The contractor shall perform all the tasks necessary to update the instrumentation system.

These tasks may include trenching, cabling, power connections, target pit preparations or any other tasks required to repair damaged or inoperable infrastructure components. These tasks shall be identified by the contractor at the site survey prior to installation and shall be implemented only when directed by the Contracting Officer. The prime contractor and/or sub-contractors shall possess all necessary licenses and permits required to perform the infrastructure tasks in accordance with all environmental policies and laws (i.e. National Environmental Protection Act

(NEPA) compliance).

The contractor shall reuse the equipment listed in the following table. After award, the contractor shall evaluate the reusability of the items at each of the sites in performing the CTR. If the contractor discovers issues or deviations from the reuse items, the contractor shall submit a notification to the Government, which will then be handled via the Engineering Change Proposal

(ECP) process.

ITEMS IDENTIFIED FOR REUSE

CACTF SH

GPS Time Server GPS Time Server

GPS Antenna GPS Antenna

Exterior Camera NEMA Box

Exterior Speaker NEMA Box

Camera Assembly Components Camera Assembly Components

- Illuminator - Illuminator

- Power Supply - Power Supply

- Camera Box - Camera Box

- Camera Box Mount - Camera Box Mount

Speaker Assembly (Interior and

Exterior) Components

Speaker Assembly (Interior)

Components

- Barix Audio Decoder - Barix Audio Decoder

- Amplifier - Amplifier

- Power Supply - Power Supply

- Speaker Box - Speaker Box

- Speaker Box Mount - Speaker Box Mount

Stand-Alone Equipment Racks

(ROC/AAR & Training

Buildings)

Stand-Alone Equipment Racks

(ROC/AAR & Training

Buildings)

Lighting Control Lighting Control

Panic Buttons Panic Buttons

Data and power infrastructure Data and power infrastructure

8-Port KVM Switch

AAR Microphones AAR Microphones

AAR Speakers AAR Speakers

AAR Projector Screen(s) AAR Projector Screen

Workstation Desk, Chair, Podium Workstation Desk and Chair

Laptop Wall Interface

Desktop Speakers Desktop Speakers

Table 1. Hardware Available for Reuse by Site Type

All reused legacy targets are Future Army System of Integrated Targets (FASIT) performance specification PRF-PT-00468 compliant. The contractor shall provide new targets that are FASIT compliant to interface with the system. The contractor shall deliver the quantities of equipment as defined in Table 2 for each site.

HARDWARE QUANTITIES

CACTF ASH

Human Type Target - 10 Human Type Target - 5

Stationary Infantry Target - 10 Stationary Infantry Target - 0

Smoke Generator - 4 Smoke Generator - 0

Smell Generator - 4 Smell Generator - 0

Table 2. Quantities

3.1 Program Management

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, testing and sustainment of the I-MTS CTR.

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

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

3.1.1 Management Activity

The contractor shall implement proactive management processes and resources at both the technical and organizational levels to support the CTR effort and in conjunction with the initial

HPL effort.

a. The contractor shall identify production constraints, funding models, tracking of HPL evolution, and communication between activities, and provide risk management.

b. The management processes shall include mechanisms and support for the multi-program adjudication of priorities and configuration impacts as related to the CTR and HPL.

c. The contractor shall consider the long range goals of Common Training Instrumentation

Architecture (CTIA) and Training as a Service (TaaS) when performing analyses or selecting the components for the CTR and the HPL.

3.1.2 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

Plan (IMP)/Integrated Master Schedule (IMS) to include schedules of the activities required to execute the CTR and integration with the initial HPL. The contractor shall ensure that the IMS remains current. The contractor shall update the IMS after any major Baseline Change Request

(BCR).

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

3.1.3 Integrated Product Team (IPT)

The contractor shall actively participate in a meaningful capacity and assume various roles, as coordinated with the Government, throughout the various IPTs required for the CTR execution.

The purpose of an IPT is to bring together the functions that have a stake in the performance of a product or process and concurrently make integrated decisions affecting that product or process.

IPT membership shall consist of multi-functional stakeholders working together with a product-oriented focus. Each IPT shall 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.

3.1.4 Configuration Management (CM)

The contractor shall utilize the LT2 CM system for identification, control, configuration status accounting, and auditing of all configuration documentation, hardware and software representing or comprising the product in accordance with the LT2 Operations Guide and LT2 Configuration

Management Guide. As part of the compliance with the Operations Guide for the HPL, this effort shall align with the concurrent efforts of DO1 to ensure the evolution is dynamic. The contractor shall plan and implement an automated configuration management system to perform configuration control, configuration identification, audits, and status accounting in a system-engineering environment. The contractor shall follow LT2 CM procedures and processes for control of all data, hardware and software baselines. The process shall allow simultaneous access to the common product data model, and provide the ability to coordinate and update immediate changes to the Product Definition Data (PDD). The CM process must handle all levels of product and process integration to build and support the product and manage the sequence of events. The Government will maintain control of the functional baseline defined by the system performance specification, Interface Control Documents (ICD) and software requirement specifications.

CM shall be a proactive activity within the LT2 Construct. The contractor shall participate in

LT2 Configuration Control Boards (CCB), Core Asset Working Group (CAWG), Problem

Tracking Report (PTR) Review Boards (PRB), exercises, and mini exercises, as required. The contractor shall implement, integrate, and test software and hardware enhancements, upgrades and modifications. The contractor shall update associated documentation. The contractor shall utilize and synchronize the CM activities with overarching LT2 efforts.

The CTR updated hardware and software product baseline for both the CACTF and SH shall be established at the conclusion of the Technical Design Review (TDR) and maintained throughout the life of this effort. The contractor shall use the updated product baseline in addition to any site specific legacy baseline equipment for each installation. Any change to the updated baseline shall follow the normal CM process to include ECPs as well as compliance with the LT2 process.

3.1.4.1 Configuration Identification (CI)

The contractor shall establish unique identifiers for selected system attributes, system information and components to be used as the basis for CM. 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 CIs 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 upon descriptions of the attributes of the system and components and provide a known configuration to which changes can be addressed.

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

3.1.4.2 Configuration Change Management

The contractor shall utilize the LT2 CM system to perform a systematic and measurable configuration change management process for managing product configuration changes and variances in accordance with the LT2 Operations Guide and LT2 Configuration Management

Guide. The CM system shall factor in the ongoing LT2 evolution from the inclusion of the HPL in DO1. Once the system requirements have been approved by an authorized management activity, the contractor shall make 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 as to whether the change should be approved 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 effective start 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.4.3 Configuration Status Accounting

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

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

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

c. Capture configuration information as it evolves.

3.1.4.4 Configuration Verification and Audit

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

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

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

3.1.4.5 Software Configuration Control Board

The contractor shall utilize and leverage the software configuration processes and governance established under the LT2 Operations Guide.

3.1.4.6 Engineering Change Proposal (ECP) and Contract Change Proposal (CCP)

The contractor shall document and the IPT shall review all proposed changes to established baselines and the requirements, including proposed changes to the SOW, Contract Data

Requirements List (CDRL), the contract schedule, and general provisions of the contract. The

IPT review will be conducted prior to the submittal of the engineering or contract change proposal in order to clarify requirements, format and content. All proposed changes shall require approval of the Government Contracting Officer and Project Director prior to implementation.

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

3.1.4.7 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 ECP or CCP in order to clarify requirements, format and content. Depending upon the criticality of the proposed changes, this review may take the form of a teleconference, a video-teleconference, a formal meeting at PEO STRI, or a formal meeting at the contractor’s facility. All appropriate parties shall attend in order to conduct a thorough, effective review. Minutes shall be a historical record to allay any miscommunications.

3.1.5 Program Reviews

The contractor shall attend and conduct quarterly program reviews. The reviews shall provide a forum for IPT members to discuss various issues in the support of the CTR. The contractor shall generate meeting minutes, document action items, coordinate resolutions, and track action items until closure. Status and information at the review shall reflect currency since the previous review.

3.1.5.1 Technical Interchange Meetings (TIM)

The contractor shall support TIMs as required during the execution of this SOW. A TIM shall address specific technical or programmatic topics or issues during the development, implementation, and management of the CTR. TIMs shall:

a. Include (but not limited to) topics such as developmental issues and solutions, functions and processes of working groups, or coordination of technical or training publications.

b. Be utilized to support business case analyses with respect to program’s decision making on leveraging an existing component, pursuing COTS, GOTS, or custom development based on the data from the HPL and CM activity.

3.1.5.2 Management Reviews

The contractor shall conduct periodic program reviews of its program management, subcontractor management, and vendors to ensure adequate coverage and responses to the requirements of the CTR. The contractor shall ensure:

a. Proper oversight and management of subcontractors in the execution of their assigned responsibilities and functions.

b. The CTR team functions as a comprehensive whole.

3.1.5.3 Site Survey

The contractor shall perform a site survey at each location to clarify site details, identify potential situations that require additional efforts and perform the analysis of the reuse equipment detailed above. Prior to the survey, the Government and contractor shall have a meeting to discuss the site survey schedule as well as identify data requests. The Government will be responsible for coordinating the site survey with the site. The contractor shall provide a written trip report after any site survey. The site survey report shall not act as the formal approval to deviate from the design. If a change is required, the contractor shall coordinate with the Government on how to proceed.

DI-FACR-80966: Trainer Facilities Report (TFR)

3.1.5.4 Legacy Test

In conjunction with the site survey, the contractor shall perform a test of all the legacy infrastructure and equipment that will be used for the I-MTS instrumentation as well components that have been specifically identified by the Government to be reused in the CTR. The legacy equipment test shall address Government Furnished Equipment (GFE) issues prior to the introduction and integration of the new instrumentation equipment and minimize the risk of failures. The results of the legacy test and site survey shall be used as a basis for determining which infrastructure and/or equipment is operational prior to the existing system being taken off-line. The Government will confirm recorded failures at the conclusion of the test. At GAT, the contractor shall be responsible for all functionality of the system, which includes equipment reported as operational at the time of the legacy test. The contractor shall notify the Government in writing within five days after the legacy test at each location of any items discovered that have an impact to cost, schedule or performance.

DI-NDTI-80809B: Test/Inspection Report

3.1.5.5 Start of Work Meeting

A start of work meeting shall be held with the Government within 15 days after the award of this effort. The start to work meeting shall be limited to the contractor’s key team members, with emphasis on management of the program and schedule. The objective of the start of work meeting is to establish both Government and contractor roles as well as discuss the near term schedule. This meeting shall include a high level Requirements Traceability Matrix (RTM) to ensure that each requirement has been specifically identified.

3.1.5.6 Technical Design Review (TDR)

The contractor shall host a TDR that provides a list and review of the hardware and software configuration items for the system. The review shall ensure that a system is ready to proceed into integration, demonstration, test and the contractor has demonstrated the system can meet all performance requirements. As part of this review, the contactor shall address the system’s design and ensure that each configuration item in the product baseline has been captured in the system documentation. It shall also assess the systems design as defined in performance documents depicting each configuration item (including reused components) in the system, which shall ensure all requirements in the performance specification are allocated to one or more configuration items. The contractor shall describe the plan to interact with and manage the HPL.

The contractor shall provide the results of their micro and macro analysis of the proposed technology refreshment configuration. The review shall include such items as assessment of technical risk, inter-operability issues, and compatibility issues between various Commercial off the Shelf (COTS) products, including capacity issues, synchronization, latency, scaling and/or bandwidth concerns.

The contractor shall develop a RTM to provide visibility into the requirements management and to communicate where each requirement has been specifically identified. The RTM shall be a combination of the requirements in this SOW and the Performance Specification. The RTM shall be delivered to the Government in a format that has the ability to be ingested into Dynamic

Object Oriented Requirements System (DOORS). The RTM shall be included in the TDR presentation. The contractor shall update the IMS, detailing the technical implementation of their design in conjunction with the fielding plan. The IMS shall also cover schedule including in plant integration, installation, on site integration, test and evaluation, software coding, critical path drivers, and risks with mitigation plans.

The contractor shall not proceed into the implementation phase until the Government has approved the results of the TDR. Thirty days prior to the TDR, the Government and contractor shall agree to entrance and exit criteria for the TDR. However, at a minimum, the TDR shall meet the following:

Detailed design (hardware and software), including interface descriptions are complete and satisfy all requirements in the system functional baseline.

Requirements trace among functional, allocated, and initial product baselines are established.

Key product characteristics (determined by the Government) having significant impacts on system performance, assembly, cost, reliability, and sustainment or Environmental, Safety and Occupational Health (ESOH) have been identified to support implementation decisions.

The established system initial product baseline and documentation is sufficiently complete and correct to enable hardware and software integration to proceed into implementation and fielding.

Corrective action plans are in place for issues identified in the TDR.

The program is properly staffed with qualified personnel to support the required tasks.

Logistics (sustainment) and training systems planning and documentation are sufficiently complete to support the review.

Long-lead procurement plans are in place; supply chain assessments are complete.

At the conclusion of TDR, with the Government’s approval, the system product configurations shall be considered final. Any post TDR changes to the product configurations shall be formally submitted for Government review via an ECP.

3.1.5.7 Test Readiness Review (TRR)

The contractor shall complete CT using the Government approved test procedure at each site prior to conducting a TRR for that site. The contractor shall facilitate a separate TRR for each individual site to assess the site’s readiness to commence Government Acceptance Testing

(GAT). TRR discussion items shall include the results of CT, outstanding issues/concerns/risks, test objectives, procedures, resources and testing coordination. The TRR shall be conducted a minimum of five calendar days prior to GAT and the contractor shall provide, in writing, a go/no-go recommendation for GAT. The entrance criteria includes, at a minimum, the successful completion of CT and submission of any known discrepancies. The exit criteria shall include the identification and mitigation plan of known discrepancies.

DI-NDTI-80809B: Test/Inspection Report – Contractor Test Report

3.1.6 Contract Invoicing and Payment

The contractor shall document and track the status of all funds associated with the DO to include obligations, payments, cancellations, invoices and disbursements against each contract line item and sub-line item. The contractor shall document and track to levels which represent how they plan to accomplish the entire contract work scope and which are consistent with internal organizations and processes. These documents shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status. The contractor shall identify major subcontractor work elements.

DI-MGMT-81651: Contract Invoice and Payment Report

3.1.7 Subcontractor Management

The contractor shall maintain the capability to manage subcontractors in accordance with the contractor’s Subcontractor Management Plan. The contractor shall integrate subcontractors into program IPTs as required to fulfill the intent of the meeting.

3.1.8 Contract Manpower Reporting

If services are utilized, 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 October

1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 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/.

3.1.9 Metric Tracking

The contractor shall identify, track, document and provide to the Government the metrics and measurements necessary to establish the Return on Investment (ROI) for the development, implementation and maintenance of the I-MTS in pre-fielding and post-fielding. The contractor shall provide metrics and measurements in support of real-time data analytics to show how the

CTR efforts are integrated into the overall HPL.

3.1.10 Facilities and Labs

The contractor shall utilize the Government’s CPM I-MTS Post Production Software Support

(PPSS) lab, whenever possible, for software integration and testing in an Integrated Development

Environment (IDE).

3.1.11 Data Development

For all new data development and submissions (i.e. all CDRLs that are not revisions to existing

Government documents), the contractor shall follow the LT2 Data Driven Product-Line http://www.ecmra.mil/ http://www.ecmra.mil/

Methodology as described on the LT2 Portal and the LT2 Operations Guide. The contractor shall develop the content for the new data through the LT2 tools and processes utilized on the LT2

Portal in accordance with the LT2 Operations Guide. This documents shall use the LT2 TDP development framework (“Lighthouse Initiative”) tools and processes, however, they do not supersede the requirements of the DID/CDRLs. Technical drawings shall be the source data for all technical documentation. The contractor shall utilize the Lifecycle Data Service ICD (LT2-

TRADE-TD-000499)

3.1.12 Computer Hardware, Enterprise Software Solutions (CHESS) Program

The contractor shall comply with the Army’s CHESS program. Under PEO Enterprise

Information Systems (EIS), CHESS is the mandatory source for commercial Information

Technology (IT) purchases. The CHESS contract provides IT products and services that comply with Network Enterprise Technology Command (NETCOM), Army and DoD policy and standards. Purchasers of commercial hardware and software must satisfy their IT requirements by utilizing CHESS contracts and DoD Enterprise Software Initiative agreements first, regardless of dollar value. Any purchase made outside of CHESS contracts requires a waiver. A complete list of CHESS contracts and the on-line waiver process can be found at https://chess.army.mil.

3.1.13 Associate Contractor Agreements (ACA)

The contractor shall initiate and implement ACAs as needed to facilitate collaboration efforts and to maintain the HPL with emerging requirements/systems. At a minimum the contractor shall establish ACAs with the LT2 CPM Next contractor, War Fighter Focus (WFF) contractor, and the future Army TADSS Maintenance Program (ATMP) contractor.

3.1.14 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. The contractor shall conduct that part of risk management that directly impacts the critical efforts and involves risk-management preparation, risk identification, risk assessment, risk-handling option assessment, risk analysis, risk mitigation and risk control.

Risk management to product requirement objectives 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 provide early identification of risk, proactive measures to mitigate it, and communication with the Government of the risks and mitigations. The contractor shall use their internal risk management tools to perform risk management. The contractor shall provide Government insight into the contractor’s assessment, mitigation, and control techniques.

The contractor shall prepare, implement, and maintain a cost, technical and schedule risk management process, which includes risk detection and identification, assignment of risk categories, corrective action, tracking of compliance, reporting of status, and planning for risk abatement.

3.1.15 Access and General Protection Policy and Procedures

All contractor employees and all associated…