Attachment_6.1_LCPM_DO_0001_HPL_SOW_14Mar2017.pdf

PEO-STRI-15-W096

14 March 2017

Version 1.1 i

STATEMENT OF WORK

FOR THE

LIFE CYCLE PRODUCT-LINE MANAGEMENT

LIVE TRAINING TRANSFORMATION HARDWARE PRODUCT-LINE

Delivery Order 0001

U.S. Army Program Executive Office for

Simulation, Training and Instrumentation (PEO STRI)

12350 Research Parkway

Orlando, FL 32826-3276

Engineering

Prepared By: ____________________ Concurrence: ____________________

Chris Windler James Griffith

Systems Engineer, PD DT Deputy Product Director Digitized Training

Date: _________ Date: __________

Acquisition Logistics

Prepared By: ____________________ Concurrence: __________________

Jayne McClanahan Roberto Capote

Lead Acquisition Logistician, PD DT Life Cycle Acquisition Mgr., PM TRADE

Date: ___________ Date: ___________

Program Management

Submitted By: ____________________ Approved By: ____________________

Jeremy T. Lanman, Ph.D. Mr. Mike Willoughby

Lead Architect/Engineer, LT2 Product Director Digitized Training

Date: __________ Date: _________ ii

TABLE OF CONTENTS

1. Scope

1.1. Introduction

1.2. Long Term Vision

1.3. Goals and Objectives:

1.3.1. LT2 Synchronization

1.3.2. Data Analytics

1.3.3. Commodity Hardware

2. Applicable Documents

2.1. Department of Defense Directives and Instructions

2.2. Availability of Department of Defense Directives

2.3. Other Government Documents, Drawings, and Publications

2.4. Non-Government Standards

2.5. Availability of Other Government Documents, Drawings and Publications

2.6. Order of Precedence

3. Requirements

3.1. Program Management

3.1.1. Management Activity

3.1.2. Program Schedule

3.1.3. Metrics Tracking

3.1.4. Integrated Product Team (IPT)

3.1.5. Program Reviews

Program Management Reviews

Technical Interchange Meetings (TIM)

Management Reviews

3.1.6. Exhibition Support

3.1.7. Contract Invoicing and Payment

3.1.8. Associate Contractor Agreements (ACA)

3.1.9. Risk Management

3.1.10. Access and General Protection Policy and Procedures

AT Level 1 Training

Access to Government Information Systems

Cybersecurity /Information Technology Training

3.2. Hardware Product Line Capabilities

3.2.1. HPL Analysis and Development

3.2.2. HPL Evolution

3.2.3. HPL Management

3.2.4. Synchronization with LT2

3.2.5. HPL Optimization

3.2.6. HPL Processes

3.2.7. HPL Sustainment

Information Technology Sustainment

3.2.8. Fielded HPL Support

Configuration Management

Integration & Development Labs

Lab Environment Information Technology Support iii

HPL Help Desk

3.3. Hardware Product Line Activities

3.3.1. Hardware Product Development Support Activity

3.3.2. Obsolescence Management

3.3.3. Reusability

3.3.4. Extensibility

3.3.5. Governance

3.3.6. LCPM Prime and Subcontractor Equipment Manufacturing

3.3.7. Technology Insertion/Refreshment Activity

3.4. System Engineering

3.4.1. LT2 Model-Based Systems Engineering (MBSE)

3.4.2. System Baseline

3.4.3. Hardware and Software Integration

3.4.4. Product Definition Data (PDD)

3.4.5. Quality Assurance (QA)

3.4.6. Test and Verification

Testability Engineering

System Verification

3.4.7. Software Engineering

3.4.8. Data Rights

3.4.9. Cybersecurity

Certifications and Accreditation Support

Information Assurance Vulnerability Alert (IAVA)

Cybersecurity Training

3.5. Logistics

3.5.1. Reliability and Maintainability (R&M) Engineering

3.5.2. Failure Tracking and Analysis

3.5.3. Technical Publications

3.5.4. Item Unique Identification (IUID) of Tangible Items

iv

REVISION LOG

Date Version Revision

Description

10/31/2016 1.0 Initial document for Draft RFP

3/14/2017 1.1 Updated Table of Contents

STATEMENT OF WORK

FOR THE

HARDWARE PRODUCT-LINE

1. Scope

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

Training Devices (PM TRADE) within the Life Cycle Product-Line Management (LCPM) contract. This SOW defines the work efforts for the analysis, development, implementation, management and evolution of the Hardware Product Line (HPL). This SOW shall be the continuous execution of the HPL governance and management by leveraging the Government’s investment in the Live Training Transformation (LT2) Construct (i.e., tools, processes and procedures) for all subsequent Delivery Orders (DOs) throughout the life of the LCPM contract.

This shall include, but not limited to, forecasting, analysis, data collection (i.e., site installation data collection), data analytics (e.g., business intelligence metrics, return-on-investment data, data mashups, data correlations and patterns, etc.), hardware feasibility analyses, use case analyses, courses of action and recommendations. The support of obsolescence, concurrency, technology insertion, continuous technology refreshment (CTR), system disposal, and logistics of fielded training systems within the LT2 Family of Training System (FTS) or those migrating to the LT2 Product Line (P/L). Furthermore, this SOW describes the effort required to stand up the HPL that will define an initial set of standards, preliminary baseline, and an implementation approach for a commodity set of hardware components in relation to the PM TRADE business vision and goals, Training as a Service (TaaS) strategy, and LT2 Product Line.

Finally, this SOW defines the work efforts for the implementation, maturation, technology refreshment, and life cycle controls associated with the HPL strategy including the utilizion of the analyses generated from other DOs as part of the continued HPL evolution. An integration lab will be established to allow synchronization and testing of fielded and newly fielded systems to validate their capabilities against the requirements, as well as general support of the HPL evolution.

1.1. Introduction

Currently, PM TRADE’s training systems implementation comprises multiple, disparate sets of sub-systems located in exercise control centers, after action review buildings, range operation centers, edge devices (e.g., cameras, effects simulators, player units, etc.) in the field and on participants, and other co-located facilities in support of training exercises at numerous installations. Within any given installation, multiple training systems coexist with duplicated hardware in support of multiple training systems:

1. Combat Training Center – Instrumentation System (CTC-IS)/ Range Communication

System (RCS): Exercise Control (ExCon), After Action Review (AAR) and equipment

(i.e., building 990), edge devices;

2. Joint Pacific Multi-National Range Complex (JPMRC-IS): ExCon, AAR and equipment, edge devices;

3. Homestation Instrumentation System (HITS): ExCon, AAR and equipment, edge devices;

4. Digital Range Training System (DRTS): AAR, Range Operations Center (ROC) and/or tower equipment, edge devices;

5. Integrated MOUT Training System (I-MTS)/CTC MOUT: AAR, ROC and/or maintenance rooms, edge devices;

6. CTC MOUT: AAR, ROC and/or maintenance rooms, edge devices;

7. Target Modernization: Small arms and other Training Circular 25-8 Ranges.

8. Combat Training Centers Live Fire System: ExCon, AAR and equipment, edge devices;

9. Crew Module Unit with Recorder (CMUR): Edge devices.

The system implementation uses equipment primarily to host common software and typically perform same or similar tasks. However, the equipment is duplicated across several sites at any given installation.

PM TRADE is pursuing a HPL architectural analysis and implementation with the objective of identifying commonality, and determining the feasibility of a solution consisting of both centralized and distributed elements capable of simultaneously supporting the Concept of

Operations (CONOPS), operational availability, training throughput, Cybersecurity accreditation requirements of multiple systems, safety and maintenance requirements of fielded system identified above. The ascendant objective is a common set of commercial system components defined by a P/L that will facilitate centralized installation, operations and logistic support while reducing Operations and Maintenance (O&M) requirements and Total Ownership Cost (TOC).

1.2. Long Term Vision

The long-term vision for the HPL is the definition and implementation of a common architectural framework that supports the enterprise Training as a Service (TaaS) concept in accordance with

PM TRADE’s LT2 vision and the future Training-Instrumentation System (T-IS) requirement document. The HPL shall be based on the following concepts:

1. Modular and open architectures

2. Non-proprietary, no/minimal licenses

3. P/L approach

4. Software agnostic

5. High operational availability/low maintenance

6. Reduction in Cybersecurity accreditation costs

1.3. Goals and Objectives:

The primary objectives of this effort include:

1. Analyzing current systems in relation to future objectives

2. Analyzing the current system implementation

3. Developing the definition of a commodity HPL that will satisfy PM TRADE’s performance requirements

4. Establishing a solution consisting of both centralized and distributed elements capable of simultaneously (within an installation or potentially off-site supporting multiple installations) accommodating multiple fielded systems and to lower the Information

Technology (IT) footprint required to operate the systems

5. Synchronizing with established LT2 processes and standards as detailed on the LT2

Portal (www.lt2portal.mil)

6. Supporting the development of the HPL by leveraging as well as further developing the established LT2 processes, standards, and tools as detailed in the LT2 Operations Guide

(www.lt2portal.mil).

7. Providing a technical methodology to be used across future DOs as a guide to making

HPL decisions

8. Obsolescence and failure rate analysis, prediction and planning

9. Establishing an integration/test lab environment

10. Increasing training realism, relevancy, and usability for the Warfighter

This effort should support the business goals of PM TRADE to include reducing TOC. Once the

HPL 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 ensures that subsequent DOs utilize the

HPL to meet their program’s needs. The contractor 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.

The initial creation of the HPL will establish a baseline of the HPL using the majority of the requirements of the LT2 Product Line domain as nothing exists today for hardware. This establishment of the HPL will be done through an analysis of a subset of training systems’ requirements and fielded sites. The analysis of the broader spectrum of live training systems is to normalize the HPL selection process using requirements other than simply the first to use LCPM

(I-MTS/DO2). The Government expects the results of the initial HPL will not be all inclusive but will evolve overtime through additions or modifications, which shall be subject to the LT2 governance process

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.

1.3.1. LT2 Synchronization

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 environment 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 http://www.lt2portal.mil/ 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)).

1.3.2. Data Analytics

Data analytics refers to the process of collecting, organizing and analyzing large sets of data

(potentially big data) to discover patterns and other useful information. Data analytics can help organizations to better understand the information contained within the data and will also help identify the data that is most important to the business and future business decisions.

To analyze large volumes of data, data analytics can be performed using specialized software tools and applications for predictive analytics, data mining, text mining, forecasting, and data optimization. Collectively these processes are separate but highly integrated functions of high-performance analytics. Using data tools and software enables an organization to process large volumes of data that an organization has collected to determine which data is relevant and can be analyzed to drive better business decisions in the future.

The HPL may consider a 6C system:

1. Connection (sensor and networks)

2. Cloud (computing and data on demand)

3. Cyber (model and memory)

4. Content/Context (meaning and correlation)

5. Community (sharing and collaboration)

6. Customization (personalization and value)

In order to provide useful insight to the HPL management and gain correct content, data has to be processed with advanced tools (analytics and algorithms) to generate meaningful information.

Considering the presence of visible and invisible issues in a HPL, the information generation solution has to be capable of detecting and addressing unforeseen issues such as hardware degradation, component wear, system health management, etc. in the product line.

1.3.3. Commodity Hardware

Commodity hardware is readily available and affordable. A device that uses commodity hardware has components that were previously available or designed and not necessarily unique to that device. Enterprises often use commodity hardware with file servers, or cluster it to provide large-scale computing power, or to maximize savings in information technology design.

Based on ongoing research efforts and the continuing advancements of computing and networking technology, it is believed that use of commodity hardware is vital in creating a cost-effective and easily scalable solution. In addition, this is poised to have a major impact on PM

TRADE’s data-centric HPL endeavors.

2. Applicable Documents

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

Department of Defense Index of Specifications and Standards (DoDISS) and supplement thereto.

2.1. Department of Defense Directives and Instructions

DODD 8570.1 Information Assurance Training, Certification and

Workforce Management

DOD 8570.01-M Information Assurance Workforce Improvement

Program

DODI 8500.01 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 Controls for Federal Information

Systems and Organizations

PEOSTRI Basic Accreditation Manual (BAM)

AR25-2 Information Assurance

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

AR 380-5 Department of the Army Information Security

Program

MIL-STD-31000A Technical Data Packages

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

LT2-TRADE-TD-000499 Lifecycle Data Service Interface Control Document

(ICD)

Xxx LT2 Issue Tracker ICD

2.4. Non-Government Standards

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

SAE GEIA-STD-0007B, 1 May, 2013 Copies of the document may be purchased from

SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, www.sae.org

SAE GEIA-HB-0007B, 10 Feb, 2014 Copies of the document may be purchased from

SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, www.sae.org

2.5. Availability of Other Government Documents, Drawings and Publications

Copies of the documents are available from PEO STRI, SFAE-STRI-KOL, 12211 Science Dr, Orlando, FL 32826, or may be available at: http://assist.daps.dla.mil/quicksearch/ or http://www.lt2portal.mil

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

The tasks described in this SOW are intended to address the core functionalities of the HPL and its management within the LCPM contract. Individual program/product efforts may implement some or all of these functionalities for the fulfillment of the individual programmatic requirements, however, it is envisioned that all succeeding DOs must correspond with the framework established in this SOW to maintain the ongoing effort to grow the HPL. During the implementation of the requirements, the contractor shall continually strive towards the evolution and development of an approach to achieve the goals listed above.

The requirements defined herein shall form the basis for all work that shall be performed as part of this effort in the establishment of the HPL. The contractor shall execute the HPL systems/site analysis, prototyping, development, installation and testing within the emerging framework being established to manage the HPL as described in the LT2 Operations Guide. The contractor shall:

1. Perform a minimum of one site survey for each of the following types of fielded systems and subsystems (i.e. system - I-MTS; subsystems - CACTF, Shoot House, and UAC):

DRTS, HITS, Target Modernization, I-MTS and a CTC to gain an understanding of the implementation of each program’s requirements and to collect data applicable to the

HPL. The location for the initial site to be surveyed is Fort Benning, GA. Additional sites will be provided by the Government as required (no OCONUS site survey locations as part of the initial HPL establishment).

2. Provide an audit of as fielded hardware and software configurations, with migration and proposed change updates.

3. Analyze existing COTS, GOTS, and other hardware to recommend a set of hardware components that can meet the LT2 programs’ system requirements in order to stand up an initial HPL.

4. Provide a synchronization plan of HPL Configuration Management data for systems http://www.sae.org/ http://www.sae.org/ http://assist.daps.dla.mil/quicksearch/ http://www.lt2portal.mil/ being developed and already fielded. Establish objectives to maintain a single baseline between fielded systems and new fieldings.

5. Provide mitigation efforts to minimize the number of product baselines, disparate hardware assets and device versions released.

6. Use the data provided from the Life Cycle Contractor Support (LCCS) contractors (WFF and ATMP) within the LT2 repository to develop an obsolescence audit to identify when hardware products, services and components are no longer being supported within fielded systems.

7. Continue the evolution and development of an implementation approach to achieve the

PM TRADE business goals.

8. Consider CTR opportunities for the HPL which utilize cost, schedule, and performance risk mitigation approaches to integrate new capabilities to ensure P/L integrity and usability efficiencies that reduce TOC.

9. Establish a strategy for the HPL development and sustainment of logistics products (such as training, operator, support manuals and documents, to include TDP artifacts such as drawings, interface control documents, etc.) to realize cost avoidance, increased performance, enhanced usability, and higher quality products.

10. Develop and manage a near-term and long-term plan, and roadmap to facilitate and support program management decisions based on CTR objectives, system performance metrics and data, and on-site system/product configurations.

11. Analyze, establish, execute and manage plans to reduce TOC and logistics footprint for

LT2 systems and products (for example: migration plan to cloud computing-based configuration).

12. Analyze, establish, execute and manage plans to reduce the number of fielded hardware configurations to sites.

13. Analyze, establish, execute and manage a research and development plan and roadmap to facilitate and support CTR and technology insertion.

14. Establish a methodology that defines the data to include analytics, metrics (performance, status, return on investment, etc.), interfaces, standards and implementation approach for the HPL in accordance with PM TRADE’s business goals, LT2 strategies, and the DoD’s

Better Buying Power initiatives.

15. Use the above analyses and plans to develop an initial set of HPL recommendations for hardware components to be used by subsequent DOs to implement common hardware baselines.

16. Be required to disclose if they, or a direct subcontractor, is the Original Equipment

Manufacturer (OEM) for any equipment to be recommended for inclusion into the HPL.

DI-MISC-81381 Site Survey Report

DI-MISC-80711A Scientific and Technical Report – HPL Final 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 HPL design, implementation, and sustainment.

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 for 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 HPL efforts and ensure consistency and synchronization across all DOs.

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

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

3. The contractor shall consider the long range goals of TaaS and T-IS when performing analyzing or developing the components for the HPL.

4. The management processes shall include the visibility and authority across all DOs to enforce strategic integration and synchronization.

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 HPL. The contractor shall ensure that the IMP/IMS is current and includes integration between specific DO IMSs and other LT2 dependencies.

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

3.1.3. Metrics Tracking

In support of the Government’s Better Buying Power (BBP) 3.0 (and future BBP versions) initiatives, the contractor shall develop, track, document and provide to the Government the metrics necessary to determine the Government’s Return on Investment (ROI) for the development, implementation, synchronization, and maintenance of the HPL. In addition to ROI, the contractor shall collect, analyze, synthesize and interpret LCPM data to report on metrics that describe and quantify the overall benefit the HPL has provided to the Government. The contractor shall provide these metrics through dashboards on the LT2 repository.

3.1.4. Integrated Product Team (IPT)

The contractor shall materially participate, provide membership, and assume various roles, as coordinated with the Government, throughout the various IPTs required for the HPL 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.5. Program Reviews

The contractor shall attend and conduct periodic program reviews. The reviews shall provide a forum for IPT members to discuss various issues in the support of the HPL. The contractor shall provide meeting minutes, document action items, coordinate resolutions, and track action items until closure.

Program Management Reviews

The contractor shall conduct semi-annual program management reviews to provide the

Government a “state of the HPL” status and update.

1. The contractor shall provide reviews to include the entirety of the LCPM activities, assessment as to the effectiveness of the utilization of the HPL, and status reviews for cost, schedule, and performance of affiliated LCPM activities.

2. The contractor shall provide updates to the risk management planning, obsolescence and failure rate analysis, planning, and execution, and cost accounting.

3. The contractor shall provide visibility on the progress, performance, and status of major subcontractors.

Technical Interchange Meetings (TIM)

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

1. The contractor shall 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.

2. The contractor shall utilize TIMs to support business case analyses with respect to programs decision making on leveraging an existing component, pursuing COTS, GOTS, or custom development based on the data from the HPL and configuration management

(CM) activity.

Management Reviews

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

HPL.

1. The contractor shall ensure proper oversight and management of subcontractors in the execution of their assigned responsibilities and functions.

2. The contractor shall ensure that the HPL team functions as a comprehensive whole.

3.1.6. Exhibition Support

The contractor shall support and attend various exhibitions and conferences as directed by the

Government (AUSA, Capitol Hill, I/ITSEC as examples).

1. The contractor shall provide program management and technical support to these conferences.

2. The contractor shall provide, as required, technical solutions and representations that demonstrate the value and capabilities of the HPL.

3. The contractor may be required to provide exhibition support in conjunction with other

LT2 industry partners to demonstrate the LT2 P/L as a whole.

3.1.7. Contract Invoicing and Payment

The contractor shall document and track the status of all appropriated funds associated with this

SOW to include payments, cancellations and invoices 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 elements of subcontracted work.

DI-MGMT-81651: Contract Invoicing and Payment Report

3.1.8. 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 CPM Next contractor, the Director of Field Ops Life Cycle contractor (WFF and the future ATMP contractor).

3.1.9. Risk Management

The contractor shall conduct risk management 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 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, including but not limited to scheduling of manpower requirements in the event that multiple DOs are awarded with overlapping schedules. 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 tools, assessment, mitigation, and control techniques. The contractor shall document risk management as part of the CPSMR.

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

All contractor employees and all associated subcontractor 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.

AT Level 1 Training

All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 60 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 COR or to the contracting officer (if a COR is not assigned) within 60 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://atlevel1.dtic.mil/at.

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 Cybersecurity awareness training prior to access to the information system and then annually thereafter.

Cybersecurity /Information Technology 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 6 months of employment.

3.2. Hardware Product Line Capabilities

The contractor shall establish innovative, total system/subsystem life cycle management processes that will maintain or improve systems performance, operational readiness, ensure relevancy, and improve system maintenance while reducing total ownership costs and logistics footprint. The HPL shall reuse the LT2 investments to support technology insertion, tech refreshment, obsolescence and failure rate management for the evolution/improvement of the

LT2 FTS The contractor shall provide the necessary engineering technical support to integrate new hardware products and components into the HPL baselines (validation and certification of hardware component agreements). Figure 2 illustrates the interactions and data exchanges between the LCPM contractor and the other PEO STRI elements.

https://atlevel1.dtic.mil/at

Figure 1: PM TRADE LT2 Product Line Synchronization Relationship Framework

3.2.1. HPL Analysis and Development

As part of the instantiation, the contractor shall perform life cycle baseline analysis for the creation of the HPL to include the following:

a. The analysis and initial implementation (instantiation) of the HPL;

b. Hardware and equipment selection analysis;

c. Use case analysis to determine technology insertion, CTR, obsolescence, disposal, etc. of hardware products (e.g., servers, switches, routers, desktops, mobile devices, cameras, target lifters, player units, edge devices, etc.);

d. Analysis and recommendations for achieving an enterprise TaaS environment;

e. Analysis for maintaining concurrency of existing HPL components/technology with state-of-the-art technologies and processes, PM TRADE Enterprise Architecture;

(business vision, goals, etc.), LT2 model-based systems engineering approach, LT2

Construct and LT2 Portal;

f. Development of the appropriate Hardware Component Agreements (HCA) for the technologies chosen in the HPL consistent with current LT2 component agreements.

3.2.2. HPL Evolution

The contractor shall establish, execute, manage and continue the advancement, evolution, integration and verification of the HPL to fulfill the capabilities and requirements. The contractor shall facilitate a structured process/method to ensure early discovery of stakeholders driving requirements and/or quality attributes for the HPL functions, and utilize this data for HPL life cycle management, CTR, technology insertion, obsolescence management, concurrency, upgrade, disposal, and hardware focus and improvement efforts (i.e., optimize HPL evolution).

The contractor shall accomplish this by leveraging the Army’s LT2 P/L investment, while evolving hardware core assets and the HPL with LT2 Construct tools and processes to ensure synchronization, concurrency, and technology relevance across the PM TRADE P/L and LT2

FTS. The contractor shall maintain awareness of the development and evolution of the live training products/systems, core assets, plans/roadmaps, and the HPL, while continuing to provide

PM TRADE an efficient, effective, and agile method to accomplish:

1. Development, integration, testing, management, maintenance, and evolution of the HPL

(products, systems, SoS capabilities, processes, standards, and hardware core assets).

2. Total life cycle systems management and HPL support.

3. HPL support of products, systems, and SoS capabilities that leverage HPL and LT2 software P/L assets.

4. Support of architectural and system development, and core asset evolution in support of external interoperability initiatives such as Live, Virtual, Constructive Integrated

Training Environment (LVC-ITE) Common Operating Environment, Joint services initiatives, and Foreign Military Sales as required within the LT2 P/L.

5. A holistic change control process and procedure, building on the existing LT2 processes and procedures, to maintain baseline control of the common hardware products, services and components.

6. An audit of configurations, with migration and change updates for the HPL.

7. An obsolescence audit to identify when hardware products, services and components are approaching end of life or are no longer available to be utilized within fielded systems.

8. Track and analyze failure rates of HPL components through data provided on the LT2 repository. Provide a mitigation plan with courses of action to the Government to minimize future equipment failures.

9. Develop a synchronization plan of the HPL CM data for systems being integrated into the

LT2 Family of Training Systems and already fielded LT2 programs. Establish objectives to maintain a single baseline between fielded systems and new products.

10. Maintain a technology refreshment plan for the HPL and utilize cost, schedule, and performance risk mitigation approaches to integrate new capabilities to ensure P/L integrity while maximizing usability efficiencies that reduce total ownership costs.

11. Leverage the LT2 strategy (published in the LT2 Operations Guide) for the HPL development and sustainment of logistics products (such as training, operator, and support manuals, to include TDP artifacts such as drawings, interface control documents, etc.) to result in cost avoidance, increased performance, enhanced usability, increase realism and relevancy achieving higher quality products.

12. Provide recommendations and modifications of the LT2 governance processes that ensures full integration of HPL activities across LT2 P/L participants (Field Ops sustainment contractors (WFF and ATMP), LT2 (CPM Next), other PM TRADE production contracts). Focus shall include SoS management and configuration management processes across the LT2 portfolio of systems and products across the life cycle, ensuring consistency with the SoS model-based systems engineering approach.

The contractor shall utilize, follow and modify current LT2 governance processes to include HPL logistics management strategy.

13. Leverage the LT2 documentation initiative to establish an integrated and open approach for HPL TDP to be seamlessly incorporated into sustainment activities repositories.

14. Optimize testing methodologies and environments across the life cycle within a HPL environment to result in cost avoidance, increased performance, and higher quality products.

15. Develop and manage a technology roadmap with near-term and long-term plans, to facilitate and support program management decisions based on objectives, goals, system performance metrics and data, on-site system/product configurations as well as a migration plan to support future technology and requirements such as TaaS and T-IS.

16. Analyze, establish, execute and manage plans to reduce costs and logistics footprints for current and future on-site live training systems and products.

17. Analyze, establish, execute and manage plans to reduce the number of fielded hardware configurations to sites (i.e. migration plan to distributed computing type configuration).

18. Analyze, establish, execute and manage a research and development plan and roadmap to facilitate and support technology refreshment and technology insertion.

19. As illustrated in Figure 2 directly support synchronization efforts with PM TRADE’s

LT2 industry partners and between contracts with the current LT2 prime contractor (CPM

Next) and Field Ops Life Cycle contractors (WFF and ATMP) to ensure system/product concurrency and mitigate impacts to current system/product life cycle efforts and schedule.

3.2.3. HPL Management

The contractor shall manage the development, evolution and migration of the HPL functions for all LT2 FTS hardware products, components, systems, documents, standards and other affiliated

P/L artifacts. The contractor shall manage the evolution, document, and instantiate the processes to support the HPL capabilities and activities, both for current assets (e.g., hardware components, standards, products) and artifacts contained within the HPL, and for the development and insertion of new hardware assets and artifacts.

3.2.4. Synchronization with LT2

The contractor shall synchronize all efforts of the HPL with LT2 in order to achieve a holistic system-of-systems approach for the total life cycle systems management of the HPL and LT2 software P/L.

1. The contractor shall obtain and utilize all performance data (e.g., reliability, availability and maintenance data, obsolescence data, failure data, etc.) from LT2 to conduct analyses that will facilitate real-time planning and execution of the obsolescence management, CTR, concurrency, failure rate data analysis, and upgrade and disposal of live training systems to include the LT2 P/L.

2. The contractor shall support the analysis conducted by each subsequent DO to ensure synchronization and integration with the HPL and overarching LT2 processes.

3. The contractor shall ensure all HPL data is synchronized to LT2 core asset data for software systems and PDSS activities.

4. The contractor shall participate in LT2 trade studies, analyses and tool selection meetings, and proactively participate in the evolution of LT2 tools to include new and/or modified LCPM data.

5. The contractor shall collect, analyze, synthesize and interpret LCPM data, and establish, monitor and report on metrics that describe the overall health and status of the HPL. The contractor shall provide return-on-investment data and reports based on LCPM metrics in support of program management Better Buying Power 3.0 initiatives.

3.2.5. HPL Optimization

The contractor shall conduct a formal and continuous process (at least yearly) to assess the effectiveness of the HPL implementation and instantiate corrective action changes. The contractor shall identify, maintain, and track key metrics regarding the implementation and key measure points for the LCPM contract. This process shall consider the HPL life cycle management and LT2 synchronization processes, and real-time plans and roadmaps in support of

CTR, technology insertion, upgrades, obsolescence management, concurrency, upgrade, and disposal.

The contractor shall work directly with the LT2 prime contractor (CPM Next) and PD Field Ops

LCCS contractors to implement and synchronize appropriate metrics to gather real world data for the HPL. The contractor shall work directly with the LT2 sustainment contractors to establish and synchronize the processes to effectively use the measurement results to facilitate decision making and improvement within the HPL.

3.2.6. HPL Processes

The contractor shall conduct an analysis of the current business practices with LT2 with respect to the HPL and conduct a gap analysis between current and end state processes for the HPL. The contractor shall conduct iterative assessments of the processes to ensure they remain relevant and up-to-date (consistent with technology and usage of LCPM contract). The contractor shall evolve the processes (if required) as the HPL evolves.

1. The contractor shall identify and document any proposed changes to the current operating processes to define roles, responsibilities, and mechanisms inherent to the implementation of the HPL.

2. The contractor shall analyze the processes for management of change requests and problem reports for both legacy and new hardware components and products. The analysis shall focus on Configuration Change Board (CCB) and overarching CM process synchronization with the LT2 Core Asset Working Group (CAWG), component agreements, service level agreements, and standards.

3. The contractor shall consider proactive obsolescence execution as part of the analysis;

both as a forcing function to move existing baselines to latest configuration components, and as a mechanism to identify where obsolescence will impact/hinder the HPL.

4. The contractor shall focus the analysis on the delineation of integrated processes for the entirety of the HPL management.

3.2.7. HPL Sustainment

The contractor shall support hardware component and asset development, management, evolution, and maturation, to include synchronization with the LT2 processes and P/L core assets utilizing the LT2 Construct.

1. The contractor shall support, refine, and develop existing HPL assets (inclusive of documentation) to allow for technology refreshment and insertion into the HPL and LT2.

2. The contractor shall ensure synchronization of the HPL with the work efforts/products from the LT2 software sustainment efforts (CPM Next) and Field Ops sustainment efforts (WFF and ATMP) in the operations and maintenance of the various products, documentation, product lines, product line artifacts, architectures, and system configurations.

3. The contractor shall utilize the currently defined LT2 processes (Core Asset Working

Group (CAWG), etc.) where appropriate. The contractor shall also analyze, identify gaps, and recommend modifications to the LT2 processes to facilitate the activities within the HPL.

Information Technology Sustainment

The contractor shall sustain the Information Technology (IT) hardware components and infrastructure that support the management of the HPL. The contractor shall synchronize these efforts (as applicable) with the appropriate Cybersecurity requirements and constraints of the

Government’s IT components.

1. The contractor shall include the sustainment, modernization, and disposal of all IT elements required to maintain and evolve the HPL.

2. The contractor shall synchronize efforts with LT2 in the utilization of the LT2

Portal/repository and other Government LT2 resources to align to the operation needs and requirements of the HPL and allow users access to HPL specifications, documentation, drawings, configuration information, or other data/metadata required.

3.2.8. Fielded HPL Support

Through the use of the contractor’s integration lab and/or existing Government PDSS lab environments and the processes established in the HPL, the contractor shall provide technical, CM, documentation, and management support for fielded assets as well as new components for the HPL.

1. The contractor shall include integration support, interoperability support, site acceptance support, testing support, and demonstration/experimentation support.

2. The contractor shall conduct engineering assessments and provide implementation and transition plans to support the release of new hardware components, products, and configurations.

3. The contractor shall conduct analyses of HPL components, products, and configurations and provide assessments as to change/maturation impacts of the components, products, and configurations. These assessments shall include the cost tradeoff between maintaining multiple versions/configurations of hardware components and product baseline vice cost of maturing older systems/products to the latest fielded configuration baseline.

Configuration Management

The contractor shall be a stakeholder and proactively participate in the evolution of the LT2 CM methodology to establish and maintain the accuracy of the hardware components, products and assets throughout the HPL life cycle. The contractor shall synchronize with all CM activities for products and product support within the LT2 and Field Ops programs (WFF and ATMP) and provide an overarching CM method for all P/L assets, artifacts, and processes.

In coordination with the Government, the contractor shall hold a requirements review on all proposed changes prior to the formal submittal 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 formal meeting at PEO STRI, or a formal meeting at the contractor’s facility. Minutes shall be a historical record to eliminate any miscommunications. The contractor shall document and submit to the CAWG for review all changes to the HPL.

1. The contractor shall implement CM throughout the entire period of execution for all hardware components and assets of the HPL.

2. The contractor shall have CM be a proactive activity within the HPL.

3. The contractor shall identify, track, and document configuration items, manage the configuration items and changes to them, and record and report status, and change activities to the configuration items pertaining to the HPL.

4. The contractor shall have CM function as a multidimensional version of a typical CM process (multi-phased, multi-program, multi-tiered, multi-instantiated, and multi-baseline), binding the HPL products and activities.

5. The contractor shall support parallel LT2 development, distribution, and build releases…