Attachment_7.1_LCPM_DO_0002_SOW_02Nov_16.pdf

PEO-STRI-15-W094

31 October 2016

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: ____________________

Michael Craven II James Griffith

Lead 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: _________ 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 Availability of Government Documents, Drawings and Publications

2.5 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 Start of Work Meeting

3.1.5.5 Preliminary Design Review (PDR)

3.1.5.6 Critical Design Review (CDR)

3.1.5.7 Test Readiness Review (TRR)

3.1.6 Contract Invoicing and Payment

3.1.7 Contract Manpower Reporting

3.1.8 Subcontractor Management

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 Antiterrorism (AT) / Operations Security (OPSEC)

3.1.16.1 Antiterrorism Threat (AT) Awareness Level 1 Training iii

3.1.16.2 Access and General Protection Policy and Procedures for Contractor Requiring

Common Access Card (CAC)

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

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 Access to Government Information Systems

3.1.18 Information Assurance/Information Technology Training

3.1.19 Cybersecurity (Information Assurance)

3.1.20 Cybersecurity Certification Test and Evaluation (CT&E)

3.2 System Engineering

3.2.1 Hardware Engineering

3.2.1.1 Electronic and System Protection

3.2.1.1.1 Surge Protection

3.2.1.1.2 Grounding

3.2.1.1.3 Lightning Protection

3.2.1.1.4 Electromagnetic Environmental Effects (E3)

3.2.2 Hardware Test Engineering

3.2.3 System Integration

3.2.4 Common Training Instrumentation Architecture Program Interface

3.2.5 LT2 Product Line Interface and Support

3.2.6 Software Engineering

3.2.7 Testing

3.2.7.1 In-Plant Testing/ Demonstration

3.2.7.2 Legacy Test

3.2.7.3 Government Acceptance Test

3.2.7.3.1 Functional Testing

3.2.7.3.2 Physical Configuration Audit

3.2.7.4 Acceptance by the Government

3.2.8 Supportability Engineering

3.2.9 Reliability and Maintainability Engineering Program

3.2.10 Manpower and Personnel Integration (MANPRINT)

3.2.11 Quality Assurance (QA)

3.3 Synchronization Initiatives

3.3.1 Synchronization with LT2

3.3.2 Synchronization with the LCCs (WFF and ATMP)

3.3.3 Data Rights

3.4 Logistics

3.4.1 Product Definition Data (PDD)

3.4.2 Supportability Analysis and Logistics Product Data

iv

3.4.3 Inventory Support

3.4.4 Initial Spares

3.4.5 Technical Publications

3.4.5.1 Publications in Process Reviews (IPRs)

3.4.5.2 Technical Publication Validation

3.4.5.3 Technical Publication Verification

3.4.5.4 New Equipment Training (NET)

3.4.5.5 NET Verification

3.4.6 Interim Contractor Support (ICS)

3.4.7 Transition to Life Cycle Contractor Support

3.4.8 Item Unique Identification (IUID)

3.5 Government Furnished Information (GFI)

3.6 Existing Government Facility

3.7 Removal of Legacy Equipment

3.8 Packing, Storage, and Transportability

3.9 Disposal

v

REVISION LOG

Date Version Revision

Description

10/31/2016 1 Initial Document for Draft RFP

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. 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 for the following locations:

Combined Arms Collective Training Facilities (CACTF)

Ft. Stewart, GA

Ft Indiantown Gap, PA

Ft Drum, NY

Ft Polk, LA

Automated Shoothouse (ASH)

Ft Stewart, GA

Gowen Field, ID

FT Bragg, NC

Cp Shelby, MS

Cp Bullis, TX

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. The CACTF is a complex of 20-26 buildings providing combined arms collective training for platoon and company Situational Exercises

(STX) and battalion/brigade Task Force (TF) Field Training Exercises (FTX). The SH is a single building used for live fire training.

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) efforts. 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/ 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

Controls for Federal Information Systems and

Organizations

AR 25-2 Information Assurance

AR 380-5 Department of the Army Information Security Program

PEO STRI Basic Accreditation Manual (BAM)

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

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

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

MIL-STD-40001 Preparation of Final Inspection Record

2.4 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.5 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 provide all necessary labor and expense to design, procure, fabricate, ship, install, integrate, test, verify, certify, document, and provide training and support to meet the performance requirements of the I-MTS technology refreshment. In addition to this SOW, the

CTR solution shall provide the ability to fulfill the requirements outlined in the I-MTS

Performance Specification. The Range Operations Center and training building instrumentation encompasses but is not limited to; targets, battlefield effects, data networking, audio video (A/V) monitoring and recording, exercise control, AAR presentation and THP creation.

http://www.lt2portal.org/ http://www.lt2portal.mil/ http://www.lt2portal.mil/ http://assist.daps.dla.mil/quicksearch/ http://www.lt2portal.org/

The contractor shall perform all the tasks necessary to prepare and install I-MTS instrumentation.

These tasks may include trenching, cabling, power connections, target pit preparations or any other tasks required to repair damaged or inoperable infrastructure components. The contractor shall possess all necessary licenses and permits to conduct grading, excavation, trenching (for power and electrical cables) and construction of supporting infrastructure repairs and in accordance with local environmental policies.

As part of the CTR efforts, the contractor shall use the provided Government Furnished

Information (GFI) to determine their proposed approach to meet the I-MTS requirements defined in this SOW and the Performance Specification. The contractor shall utilize this data for determining the magnitude of the de-installation effort as well as the complete I-MTS system replacement of each location. Exceptions for components that are required for reuse and/or infrastructure issues will be identified in the Government provided Site Survey Report.

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.

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.

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 be in attendance 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 periodic program reviews quarterly. 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

Since the Government is providing the site survey data in advance a typical contractor site survey is not required. However, the contractor shall perform a survey (in conjunction with the legacy test) at the beginning of each installation to validate the implementation of their design at the site. If the contractor identifies additional deficiencies or damage issues observed that will impact the integration of the I-MTS instrumentation the contractor shall notify the Government within five days. The contractor shall work with the Government to determine a contractual resolution for the previously un-known issues identified during the survey. As directed, the contractor shall repair these issues to facilitate complete system integration (i.e. damaged

Ethernet cabling, corroded conduit, or broken fiber connector).

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

3.1.5.5 Preliminary Design Review (PDR)

The contractor shall host a PDR that provides a list and review of the hardware and software configuration items for the CTR. The review shall ensure that a system is ready to proceed into detailed design and can meet the performance requirements. It shall also assess the systems preliminary design as defined in performance documents depicting each configuration item in the system, and ensure that each function in the baseline has been allocated to one or more system configuration items. The contractor shall describe the plan to interact with and manage the HPL.

The contractor shall provide the results of the contractor’s 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

COTS products, including capacity issues, latency, scaling and/or bandwidth concerns. At that time, the Government may consider changes needed to the architecture to minimize technical and schedule risks for delivery of the system. The design shall only proceed after PDR when the

Government has approved the high level design. The Government and contractor shall agree to entrance and exit criteria for the PDR.

3.1.5.6 Critical Design Review (CDR)

Following the PDR the contractor shall host a CDR. This technical review shall include a requirements traceability matrix to ensure that the system is ready to proceed into fabrication, demonstration and test and the contractor has demonstrated the system can meet all performance requirements within acceptable limits of cost, schedule, and performance risk as well as other system constraints. As part of this review, the contactor shall address the systems final design and ensure that each configuration item in the product baseline has been captured in the detailed design documentation. The CDR shall be conducted to include each configuration item as part of a system level design which shall ensure there are adequate interfaces between all of the hardware and software configuration items. The contractor shall discuss how the hardware and software specifications can meet functional and performance requirements. At the conclusion of

CDR, with the Governments approval, the design shall be considered final. Any post CDR changes to the design shall be formally submitted for Government review via an Engineering

Change Proposal (ECP). At a minimum the exit criteria for the CDR 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 complete and consistent

Key product characteristics having the most impact on system performance, assembly, cost, reliability, and sustainment or Environmental, Safety and Occupational Health

(ESOH) have been identified to support CTR decisions

The established system initial product baseline and documentation is sufficiently complete and correct to enable hardware fabrication and software coding to proceed with proper configuration management

Assessment of the technical effort and design indicates potential for operational success

Acceptable risks with mitigation plans approved and documented in the IMS

Updated program development schedule including fabrication, test and evaluation, software coding, and critical path drivers

Corrective action plans for issues identified in the CDR

Adequate processes and metrics are in place for the program to succeed

The program is properly staffed

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

Materials are available to meet the schedule

Additional CDR criteria may be added by the Government up to thirty days prior to CDR.

3.1.5.7 Test Readiness Review (TRR)

The contractor is expected to successfully complete contractor test (CT) using the Government approved test procedure prior to the TRR. Upon successful on-site CT completion, the contractor shall facilitate a separate TRR for each individual site to assess the site’s readiness to commence Government testing and verification of all items associated with Government

Acceptance Testing (GAT). Items discussed 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 Government travel and the contractor shall provide, in writing, a go/no-go recommendation for GAT.

DI-NDTI-80809B: Test/Inspection 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.

3.1.7 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 for this SOW 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 30 September. 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/.

DI-MGMT-81651: Contract Invoice and Payment Report

3.1.8 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. Additionally, subcontractors shall be included in program management and tracking systems such as management information systems, EVMS, etc.

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.

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

3.1.10 Facilities and Labs

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

(PDSS) lab, whenever possible, for software integration and testing in the Integrated

Development Environment (IDE).

3.1.11 Data Development

For all data development and submission, the contractor shall follow the LT2 Data Driven

Product-Line Methodology as described on the LT2 Portal. The contractor shall develop the content for the data through the LT2 tools and processes utilized on the LT2 Portal in accordance with the LT2 Operations Guide. The contractor shall utilize the Lifecycle Data Service ICD.

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.

https://chess.army.mil/

3.1.15 Access and General Protection Policy and Procedures

All contractor employees and all associated sub-contractor employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative). The contractor shall also 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’s workforce shall comply with all personal identity verification requirements as directed by DOD, HQDA, and/or local policy.

3.1.16 Antiterrorism (AT) / Operations Security (OPSEC)

3.1.16.1 Antiterrorism Threat (AT) Awareness Level 1 Training

All contractor employees, to include subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete AT Level I awareness training in accordance with AR381-12 within thirty (30) calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable.

The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the Contracting Officer’s Representative (COR) or to the contracting officer, if a COR is not assigned, within thirty (30) calendar days after completion of training by all employees and Subcontractor personnel. AT level I awareness training is available at the following website: http://jko.jten.mil.

3.1.16.2 Access and General Protection Policy and Procedures for Contractor Requiring

Common Access Card (CAC)

Contractor and all associated subcontractor 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.

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

Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated

National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DOD facility and access, via logon, to DOD networks on-site or remotely; (2) Remote access, via logon, to a DOD network using DOD -approved remote access procedures; or (3) 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. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the Federal Bureau of Investigation

(FBI) fingerprint check and a successfully scheduled NACI at the Office of Personnel

Management.

http://jko.jten.mil/

3.1.16.3 AT Awareness Training for US Based Contractor Personnel Traveling Overseas

All US based contractor employees and associated subcontractor employees shall take

Government provided Area of Responsibility specific AT awareness training as directed by AR

525-13. Specific Area of Responsibility training content is directed by the combatant commander with the unit AT Office being the local point of contact.

3.1.16.4 iWATCH Training

The contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity AT Office). This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within thirty (30) calendar days of new employees commencing performance with the results reported to the COR no later than sixty (60) calendar days after contract award.

3.1.16.5 Army Training Certification Tracking System (ATCTS) Registration for

Contractor Employees Who Require Access to Government Information Systems

All contractor employees with access to a Government information system shall be registered in the ATCTS at commencement of services, and shall successfully complete the DOD Information

Assurance Awareness prior to access to the Information System (IS) and then annually thereafter.

3.1.16.6 OPSEC Program

The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the responsible Government

OPSEC officer. This plan shall include a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The contractor shall implement OPSEC measures as ordered by the commander. In addition, the contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.

3.1.16.7 Requirements for OPSEC Training

Per AR 530-1, Operations Security, new contractor employees shall complete Level I OPSEC training within thirty (30) calendar days of their reporting for duty. All contractor employees shall complete annual OPSEC awareness training. The contractor shall ensure all applicable employees have completed OPSCE initial training and annual refresher training and shall certify that their work force has completed the training through the submission of completion certificates(s) to the COR within 30 days of arrival on the installation. OSPEC training can be accomplished at the Defense Security Services website at:

http://cdsetrain.dtic.mil/opsec/idex.htm.

3.1.16.8 Cybersecurity / Information Technology (IT) Training

All contractor employees and associated subcontractor employees shall complete the DOD

Cybersecurity awareness training before issuance of network access and annually thereafter. All contractor employees working Cybersecurity/IT functions shall comply with DOD and Army training requirements in DODD 8570.01, DOD 8570.01-M and AR 25-2 within six (6) months of employment. Cybersecurity/Information Technology (IT) training can be accomplished at https://ia.signal.army.mil/dodiaa/default.asp.

http://cdsetrain.dtic.mil/opsec/idex.htm https://ia.signal.army.mil/dodiaa/default.asp

3.1.16.9 Cybersecurity / IT Certification

Per DOD 8570.01-M , Defense Federal Acquisition Regulation Supplement (DFARS)

252.239.7001 and AR 25-2, the contractor employees supporting Cybersecurity/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in

DOD 8570.01-M shall be completed upon contract award.

3.1.16.10 Threat Awareness Reporting Program (TARP)

For all contractors with security clearances, per AR 381-12 Threat Awareness and Reporting

Program (TARP), contractor employees shall receive annual TARP training by a counterintelligence agent or other trainer as specified in 2-4b.

3.1.17 Access to Government Information Systems

All contractor employees with access to a Government information system shall be registered in the Army Training Certification Tracking System (ATCTS) at commencement of services, and must successfully complete the DOD Information Assurance (IA) awareness training prior to access to the information system and then annually thereafter.

3.1.18 Information Assurance/Information Technology Training

All contractor employees and associated sub-contractor employees shall complete the DOD

Information Assurance Awareness Training before issuance of network access and annually thereafter. All contractor employees working Cybersecurity/IT functions shall comply with

DOD and Army training requirements in DODD 8570.01, DOD 8570.01-M and AR 25-2 within

6 months of employment.

3.1.19 Cybersecurity (Information Assurance)

The contractor shall integrate Cybersecurity into their management processes, document decisions, specify and track Cybersecurity requirements, document certification efforts, identify possible solutions,…