Attachment_1_LCPM_BASE_SOW_09Feb2017.pdf

PEO-STRI-14-W095

9 February 2017

Version 1.1 i

STATEMENT OF WORK

for the

Life Cycle Product-line Management (LCPM)

Base

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

Jayne McClanahan Roberto Capote

Lead Acquisition Logistician Life Cycle Acquisition Mgr., PM TRADE

Date: ___________ Date: ___________

Program Management

Submitted By: ____________________ Approved By: ____________________

Jeremy T. Lanman, Ph.D. Michael Willoughby

Lead Architect/Engineer, LT2 Product Director Digitized Training

Date: __________ Date: _________ ii

TABLE OF CONTENTS

1.0 Scope

1.1 Introduction

1.2 Goals and Objectives

1.3 Background

1.4 Hardware Product-line Vision

2.0 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 Government Documents, Drawings and Publications

2.6 Order of Precedence

3.0 Requirements

3.1 LCPM Contract Management, Organization and Processes

3.1.1 LT2 Product-line Synchronization

3.1.2 Support within LT2

3.1.3 System Problem Reporting

3.1.4 LT2 Evolution Support

3.1.5 LT2 Synchronization

3.1.6 Computer Hardware, Enterprise Software Solutions (CHESS) Program

3.1.7 Product CTR, Obsolescence, Concurrency, Upgrades and Disposal

3.1.8 Facilities and Labs

3.2 Program Management

3.2.1 Contractor Facility

3.2.2 Integrated Product and Process Development (IPPD)

3.2.2.1 Post Award Conference (PAC)

3.2.3 Integrated Master Plan and Integrated Master Schedule (IMP/IMS)

3.2.4 Earned Value Management System (EVMS)

3.2.4.1 Contractor Integrated Performance Management

3.2.4.2 Integrated Baseline Review (IBRs)

3.2.5 Risk Management

3.2.6 Associate Contractor Agreements (ACAs)

3.2.7 Subcontractor Management

3.2.8 Cost as an Independent Variable (CAIV)

3.2.9 Contracting Invoice and Payment

3.2.10 Contractor Manpower Reporting

3.2.11 Metric Tracking

3.2.12 Data Rights

3.3 Systems Engineering

3.3.1 Hardware Engineering

3.3.2 Hardware Test Engineering

3.3.3 System Integration

3.3.5 System Safety Program

3.3.6 Supportability Engineering

3.3.7 Quality Engineering

iii

3.3.8 Reliability and Maintainability (R&M) Engineering Program

3.3.9 Producibility Engineering Program

3.3.10 Manpower and Personnel Integration (MANPRINT)

3.4 Program and Design Reviews

3.5 Cybersecurity (Information Assurance)

3.6 Value Engineering

3.7 Packing, Storage, and Transportability

3.8 Logistics

3.8.1 Supportability Analysis and Logistics Product Data

3.8.2 Initial Spares

3.8.3 Technical Publications

3.8.3.1 Publications In Process Reviews (IPRs)

3.8.3.2 Technical Publication Validation

3.8.3.3 Technical Publication Verification

3.8.4 New Equipment Training (NET)

3.8.4.1 NET Verification

3.8.5 Interim Contractor Support (ICS)

3.8.5.1 ICS Engineering Services

3.8.5.2 ICS Transition Planning

3.8.6 Transition to Life Cycle Contractor Support

3.8.7 Item Unique Identification (IUID)

3.9 Operations Security (OPSEC)/Anti-Terrorism Requirements

3.9.1 AT Level 1 Training

3.9.2 AT awareness training for IS based contractor personnel traveling overseas

3.9.3 Access and General Protection Policy and Procedures

3.9.4 Access to Government Information Systems

3.9.5 Information Assurance/Information Technology Training

3.10 Contract Data Requirements List (CDRL)

3.11 Disclosure of Information

iv

REVISION LOG

Date Version Revision

Description

10/28/2016 1.0 Initial Document for Draft RFP

2/09/2017 1.1 Minor Changes

STATEMENT OF WORK

Life Cycle Product-line Management Base SOW

1.0 Scope

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

Manager Training Devices (PM TRADE) Life Cycle Product-line Management (LCPM) contract. The single award LCPM Indefinite Delivery/ Indefinite Quantity (ID/IQ) contract will enable PM TRADE and other organizations that utilize the Live Training Transformation (LT2)

Product-line (P/L) to perform life cycle management: obsolescence management, Continuous

Technology Refresh (CTR), technology insertion, concurrency, upgrade and disposal of live training systems. The LCPM contract will be responsible for the development and management of the LT2 Hardware P/L (HPL) in support of the tasks described above. Participation in the

LT2 P/L is required and defined as utilizing LT2 P/L core assets, governance, standards, processes, tools, and environments for the development, testing, and life cycle support of systems and subsystems. In order to support these life cycle efforts, the contractor will be required to perform tasks such as trade studies, analysis and forecasting, data collection, design, development, impact assessment, information assurance, materiel procurement, integration, installation, testing, system training, documentation, logistics support, and disposal.

This effort will be inclusive of the programs within the LT2 Product-Line Domain. This domain is defined as programs who are already established within the LT2 P/L or whom are utilizing this effort to adopt the LT2 methodology. The LT2 Domain includes (but is not limited to) the LT2

Family of Training Systems (LT2 FTS) which supports the full range of live training requirements, Force-on-Force and Force-on-Target, from individual training to collective training at unit home stations, Combat Training Centers (CTCs), CTC Military Operations on

Urban Terrain (MOUT), Live Fire and Digital Ranges, and other training ranges throughout the world. These programs include but are not limited to: Digital Range Training Systems (DRTS), Integrated MOUT Training Systems (I-MTS), Target Modernization, Homestation

Instrumentation Training System (HITS), Joint Pacific Multinational Readiness Capability–

Instrumentation System (JPMRC-IS), and Combat Training Center-Instrumentation System

(CTC-IS) at the National Training Center (NTC), Joint Readiness Training Center (JRTC) and the Joint Multinational Readiness Center (JMRC).

To accomplish the requirements and goals listed in this SOW, the Government and contractor will work together to:

a. Establish the LT2 HPL through an analysis of the existing Live Training systems and the existing or emerging technologies to support it.

b. Analyze and leverage the current LT2 Construct (tools, processes and governance) to support the HPL.

c. Develop and maintain the tools and resources necessary as required for delivery orders to utilize the HPL and keep it current.

d. Establish relationships with the current LT2 Consolidated Product-line Management

(CPM), Warfighter Focus (WFF), and Army TADSS Maintenance Program (ATMP) contractors and develop technical interfaces between the tools to allow exchange of data and information needed to perform total life cycle efforts.

e. Perform all of the tasks required to migrate the existing fielded sites to the HPL.

1.1 Introduction

The LCPM contract facilitates evolution of the LT2 P/L programs and life cycle management for

Product Managers operating within the training domains from stove piped approaches to a product line implementation. The LCPM contract will ensure system relevancy via a consolidated, streamlined approach that protects, leverages and matures the Army’s live training investment and continues to evolve the core assets. LCPM will provide efficient, effective, and agile processes to accomplish CTR, obsolescence management, concurrency, upgrades, technology insertion, and disposal of live training systems. The contractor shall ensure the following:

a. Utilization and synchronization of the LT2 P/L products and proactively facilitate future LT2 FTS and Training-Instrumentation System (T-IS) migration.

b. Acquisition, Technology and Logistics Life Cycle System Management of systems/products within the LT2 FTS.

c. End-to-end alignment, synchronization, and integration with the LT2 methodology.

d. Synchronization with operations and maintenance efforts with PEO STRI Life Cycle

Contractor Support (LCCS) activities such as WFF and the future Army TADSS

Maintenance Program ATMP.

1.2 Goals and Objectives

The LCPM contract objective is to establish a consolidated approach to Life Cycle Management

(LCM), proactively address all life cycle phases, obsolescence planning, maintain or improve system performance and operational readiness, ensure relevancy, and improve system maintenance while reducing total ownership costs and logistics footprint.

It is the objective of the LCPM contract to develop a hardware P/L by ensuring standardization, commonality, synchronization, maximum reuse, core asset reuse, and interoperability within the

PM TRADE’s live training systems to include the LT2 P/L.

The LCPM contract should support the business goals of PM TRADE to include:

a. Reducing Operational Cost & Complexity

b. Aligning & Supporting Product Development (common standards, interfaces)

c. Enhancing Soldier Training Effectiveness

d. Reducing Sustainment & Development Costs

e. Increasing Technology Agility

f. Leveraging Other Army Systems

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

1.3 Background

Project Manager Training Devices (PM TRADE) is the Army's solution provider for live instrumented training systems. PM TRADE's mission is to develop, acquire, field and sustain a family of interoperable live training solutions for use at Home Station, CTCs, institutions, and deployed sites to improve Warfighter readiness. By managing the acquisition of training systems to meet the user's requirements, the goal is to deliver the systems on schedule and within cost and to provide life cycle management to ensure the best value products for the Army and external customers. The LCPM contract will provide for hardware centric LCM of PM TRADE training systems, development, and LT2 integration support to the PMs for system acquisitions.

This SOW defines the general tasks to be performed under the LCPM contract in support of live training life cycle management requirements. Individual program efforts will define the detailed requirements on the Delivery Order level. PM TRADE envisions that LCPM will provide proactive life cycle management and will support the evolution of live training systems by leveraging the following initiatives and technical concepts:

a. LT2 methodology

b. Architectural initiatives

1. Common Training Instrumentation Architecture (CTIA)

2. Future Army System of Integrated Targets (FASIT)

3. Live Training Engagement Composition (LTEC)

4. Future LT2 Architectures

c. Government Furnished Information (GFI) software via the LT2 Portal and other means as necessary

d. Product sustainment (synchronization with PEO STRI Life Cycle Contractor Support

(LCCS))

e. Product Line tools & methodologies management

f. Engineering & management dashboards and metrics

g. Reliability, Availability and Maintainability (RAM) assessment for spare listing and support management

h. Component production/obsolescence life-cycle longevity assessment

1.4 Hardware Product-line Vision

LT2 is the focused effort of PM TRADE to carry out the mission of managing the LT2 P/L configuration baseline throughout the total life cycle to ensure that the integrity of the affected systems remains aligned with the development and advancements within on-going acquisition contracts. To ensure consistent performance across systems and products within the P/L over time, it is imperative that life cycle functions align with the overarching P/L management approach. The LCPM contract and strategy will be synchronized with the LT2 strategy that is managed under the LT2 construct.

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 and Instructions

DODD 8570.1 Information Assurance Training, Certification and Workforce

Management

DOD 8570.01-M Information Assurance Workforce Improvement Program

DODI 8500.1 Cybersecurity

DODI 8510.01 Risk Management Framework (RMF) for DoD Information

Technology (IT)

DODI 8582.01 Security of Unclassified DoD Information on Non-DoD

Information Systems

2.2 Availability of Department of Defense Directives

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

2.3 Other Government Documents, Drawings and Publications

DoD Manual 5200.1 Acquisition Systems Protection Program

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

ANSI/EIA-748-C Earned Value Management Systems

AR 25-2 Information Assurance

AR 380-5 Department of the Army Information Security Program

PEOSTRI Basic Accreditation Manual (BAM)

CTIA Common Training Instrumentation Architecture

(www.lt2portal.org)

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

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

Procedures Guide

MIL-STD-882 Standard Practice for System Safety

MIL-DTL-31000C Technical Data Packages

MIL-STD-1472F DoD Design Criteria Standard - Human Engineering

MIL-STD-810G DoD Test Method Standard for Environmental Engineering http://www.dtic.mil/whs/directives/ http://www.lt2portal.org/

Considerations and Laboratory Tests

MIL-HDBK-240 DoD Handbook for Hazards of Electromagnetic Radiation to Ordnance (HERO) Test Guidance

MIL- STD- 40051 Page Based Technical Manuals

MIL-STD-3046 Configuration Management

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

2.4 Non-Government Standards

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 EIA-748C, March 1, 2013 Copies of the document may be purchased from

2.5 Availability of Government Documents, Drawings and Publications

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

2.6 Order of Precedence

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

3.0 Requirements

The requirements defined herein shall form the basis for all work that shall be performed as part of the delivery orders the Government will issue under the LCPM contract for the product line analysis, design, development, integration, prototype production, production, testing, fielding, documentation, sustainment, disposal and consolidated total system life cycle P/L management of live training systems and programs in support of the HPL.

3.1 LCPM Contract Management, Organization and Processes

The contractor shall establish innovative, total system/subsystem life cycle management processes that will maintain or improve system’s performance, operational readiness, ensure http://www.sae.org/ http://www.sae.org/ http://www.sae.org/ http://assist.daps.dla.mil/quicksearch/ relevancy, increase realism, and improve system maintenance while reducing total ownership costs and logistics footprint. LCPM will allow for technology insertion, upgrades, obsolescence management, and evolution/improvement of currently fielded systems for Product Managers operating within the LT2 life cycle support framework. LCPM shall utilize the LT2 construct core processes to ensure end-to-end systematic reuse, governance, integration, alignment, synchronization, and configuration management with the LT2 P/L and consolidated P/L management strategy.

In support of the LCPM contract, the contractor shall perform the programmatic activities, which provide for an optimized P/L organizational structure. The contractor’s approach shall ensure efficient P/L processes for the management and oversight of the P/L technical activities including resources utilized across all LCPM delivery orders. The contractor shall utilize the

LT2 Portal for product-line asset management including but not limited to data, documentation, models, specifications, schemas, etc. The following table provides a representative list of tasks and activities that could be required by specific delivery orders with respect to P/L Management, Organization and Processes.

Technical Planning Hardware Interface Management

Requirements Management Hardware Configuration Management

Risk Management CTR Strategy and Management

Technical Data Management Hardware Obsolescence Management

Decision Analysis Continuous LT2 Integration and

Synchronization

Technology Forecasting Metrics, Measurement and Tracking

Resource Planning and Management Facilities Management

Integrated Product Team Management Technical Reviews

Business Strategy Hardware Concurrency and Upgrades

Strategy and Management

Reuse Analysis Disposal Management

LCPM Transition Planning Training Development

3.1.1 LT2 Product-line Synchronization

The contractor shall develop and manage a hardware P/L for all of the programs utilizing the

LCPM contract and for the LT2 P/L Domain. The contractor shall work with the Government and the LT2 Governance Body (comprised of LT2 program teams and other industry partners) to update the LT2 governance policies and documentation to account for the development of the hardware P/L.

The contractor shall follow LT2 Configuration Management (CM) processes in accordance with the LT2 Product Line Configuration Management Operational Procedures Guide and the LT2

Operations Guide and LT2 Interface Control Documents (ICD). The contractor shall synchronize, populate, and maintain description data and other pertinent information for the LT2 systems and common components within the construct of the LT2 tools and processes. The contractor shall identify, describe, and track all of the work products, components, and systems’ baselines produced under this contract. The contractor shall develop draft Hardware Component

Agreements (HCA) for LT2 process approval, maintain published HCAs and other related component agreements, and actively monitor CM policies as part of the overarching LT2 efforts.

The contractor shall synchronize with the overarching architectures as the versions mature and additional architectures and frameworks are implemented.

3.1.2 Support within LT2

The contractor shall actively support, as required, the development and refinement of the systems and components fielded. The contractor shall support the system/product-line by implementing appropriate processes to support the LT2 P/L. The contractor shall monitor direct components within the scope of LCPM systems and secondary (affiliated) components as well as maintain their component agreements. This support shall range between collection and adjudication of problems and issues, and providing assistance in verifying and/or installing hardware or software changes as issued via the LT2 repository.

3.1.3 System Problem Reporting

The contractor shall report any suspected design and/or capability inadequacies, as well as any performance anomalies that might indicate a systemic flaw/fault or require HPL or software P/L re-baselining. The contractor shall include the nature of the suspected flaw, the time and conditions surrounding the occurrence, and affected systems/locations. These reports shall be implemented within the framework and processes utilized to support the LT2 P/L.

3.1.4 LT2 Evolution Support

The contractor shall support, as defined within the delivery orders, efforts associated with the evolution and maturation of the LT2 P/L, to include development of prototypes and proof of principles, Decision Analysis and Resolution (DAR) studies, and Standards development and synchronization. These efforts shall support specific requirement sets furnished by the

Government and may include hardware development in conjunction with software development.

3.1.5 LT2 Synchronization

The contractor shall implement and sustain inherent processes and oversight to coordinate and synchronize the activities described in this SOW with the overarching LT2 construct and implementation (as described in the LT2 Operations Guide) in order to minimize duplication of efforts and ensure common components integrity is maintained. The contractor shall monitor

LT2 requirements and framework as they mature. The contractor shall participate in the Core

Asset Working Group (CAWG) meetings and support affiliated studies, tasks, and analyses. The contractor shall work with the Government and the CPM Next contractor to ensure that the hardware P/L is addressed within the CAWG processes.

Following the processes detailed in the LT2 Ops Guide the contracter shall, at a minimum, create and track Problem Trouble Reports (PTR) for bugs/fixes, submit Core Asset Change Proposals

(CACP) for new and revised compnents, actively participate in the CAWG process; including reviewing and providing impact assessments to CACPs, participate in product IPTs,

3.1.6 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. CHESS contracts provide 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.7 Product CTR, Obsolescence, Concurrency, Upgrades and Disposal

As specified by individual delivery orders, the contractor shall perform the necessary tasks and activities for product/system fielding, CTR, hardware obsolescence, concurrency, upgrades, disposal, prototype production, technology insertion, testing, delivery and sustainment. The following table provides a representative list of tasks and activities that could be required by specific delivery orders:

Concept Development Functional Analysis

Requirements Analysis System Engineering

Continuous LT2 Integration and

Synchronization

System Design

Prototyping Software Integration

System Integration Testing & Test Engineering

Fielding Training

Verification Testing Validation Testing

System Demonstration Risk Management Framework (RMF)

Testing and Certification

Hardware Configuration Management Security Engineering

Trade Studies Quality Engineering

Architecture and Infrastructure Upgrades Documentation

RAM Analysis

3.1.8 Facilities and Labs

As specified by individual delivery orders, the contractor shall utilize the Government’s P/L facilities and labs, as much as possible, for tasks such as, hardware obsolescence, concurrency, upgrades, disposal, prototype production, technology insertion, testing, fielding and sustainment.

In addition to the utilization of the Governments existing lab investments the contractor shall also maintain a scalable lab environment to support integration, scaling, and testing tasks for more significant efforts (i.e. a completed CTR) or in the event the Government lab is not available for use. The contractor shall establish or integrate with the existing labs to facilitate an efficient and unified P/L environment, which addresses the LCPM functions and activities. The following table provides a representative list of tasks and activities that could be required by specific delivery orders:

Trade Studies Training

Subject Matter Expertise LCPM Transition

Integrated Development Environment Hardware Engineering Environment

Tool Support Publishing

Technical Library P/L CTR, Obsolescence, Concurrency, Upgrades and Disposal

Continuous LT2 Integration and

Synchronization

Prototyping

Integration Testing and Test Harness Development and

Integration

Quality Assurance SoS Management

3.2 Program Management

The contractor shall establish and maintain an integrated program management system, which shall plan, direct, integrate and control the administrative, management, technical, logistical, financial, production and support functions of each specific order. The contractor shall maintain procedures to respond to Request for Proposals (RFPs), Delivery Orders (DO), and contract modifications. The contractor shall manage work efforts to optimize total product performance, ensure interoperability and common solutions, and minimize total ownership cost.

3.2.1 Contractor Facility

The contractor’s management team, primary HPL engineering team, and lab environment shall be located within ten (10) miles of PEO STRI.

3.2.2 Integrated Product and Process Development (IPPD)

As specified by individual delivery orders, the contractor shall establish and maintain a process for IPPD and participate in joint Government/contractor Integrated Product Teams (IPT) in a

Performance-Based Business Environment to manage and integrate all tasks, activities and data.

The contractor shall facilitate Government insight into contract activities and establish working relationships with Government personnel that will enable continuing insight into all contract activities. The contractor shall provide real-time, reliable and user-friendly electronic remote access to all data produced under the contract to enable review of contract status and demonstrate readiness to complete significant events as needed per DO. The contractor shall make available to the Government all technical, cost and schedule data for each specific delivery order. The contractor shall maintain processes that facilitate completion of delivery order.

3.2.2.1 Post Award Conference (PAC)

The Contractor shall conduct a post award meeting within 30 days after initial contract award.

The PAC shall establish the framework of the contractor and Government interaction during the performance period of the contract. The conference shall introduce key participants with emphasis on top level management of the program, identify points of contact, discuss the

Contractor’s understanding of the scope of work, agree on metrics that will be used as management indicators, identify the partnering approach, and other contract issues.

3.2.3 Integrated Master Plan and Integrated Master Schedule (IMP/IMS)

As specified by individual delivery orders, the contractor shall develop an IMP and an IMS. The contractor shall manage to and maintain the IMP and IMS it has developed for each specific order, including appropriate program milestones with corresponding entrance and exit criteria.

The IMP and IMS shall include a detailed account of all tasks necessary to accomplish the goals and objectives of each specific delivery order.

The contractor shall develop and maintain an IMS by logically networking detailed program activities including synchronization of all active delivery orders. The schedule shall contain the planned events and milestones, accomplishments, exit criteria, and activities from contract award to the completion of the contract. The contractor shall quantify risk in hours, days, or weeks of delay and provide the most likely duration for each IMS activity and event.

3.2.4 Earned Value Management System (EVMS)

As specified by individual delivery orders, the contractor shall use EVMS.

3.2.4.1 Contractor Integrated Performance Management

As specified by individual delivery orders, the contractor shall establish, maintain, and use in the performance of each delivery order, an integrated performance management system. Central to this integrated system shall be a validated EVMS in accordance with the basic contract clauses and the EVMS guidelines contained in ANSI/EIA-748. To establish the integrated performance management system, the EVMS shall be linked to and supported by the contractor’s management processes and systems to include the IMS, contract work breakdown structure, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement.

3.2.4.2 Integrated Baseline Review (IBRs)

As specified by individual delivery orders, the contractor shall engage jointly with the

Government team in IBRs to evaluate the risks inherent in the contract’s planned performance measurement baseline. Initially, this shall occur as soon as feasible but not later than six months after each individual delivery order award, and subsequently following all major changes to any delivery order. Each IBR shall verify that the contractor is using a reliable performance measurement baseline, which includes the entire contract scope of work, is consistent with contract schedule requirements, and has adequate resources assigned. Each IBR shall also record any indications that effective EVM is not being used. IBRs shall also be conducted on subcontracts that meet or exceed the EVM application threshold. The prime contractor shall lead the subcontractor IBRs, with active participation by the Government.

3.2.5 Risk Management

As specified by individual delivery orders, 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 conduct that part of risk management that directly impacts the technical effort 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 more than one delivery order is awarded. 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. Early identification of risk, proactive measures to mitigate it, and communication with the Government shall be provided. 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.

3.2.6 Associate Contractor Agreements (ACAs)

In order to consolidate and maintain product line efficiency within the LT2 portfolio of live training systems, the contractor shall synchronize and integrate with the LT2 P/L and consolidated P/L management strategy. The contractor shall synchronize efforts with the LT2 prime contractor (CPM Next) to leverage the LT2 construct to include governance processes.

The CPM Next contractor maintains the Government’s LT2 processes, policies, standards, architectures, and other P/L core assets. The contractor shall synchronize efforts with the WFF and the future ATMP prime contractors to leverage the system maintenance and repair data and other system support efforts being provided by those contracts. The contractor shall establish

ACAs with the LT2 CPM Next, WFF and ATMP contractors.

As specified by individual delivery orders, the contractor shall implement ACAs for exchanging data, accessing and using third party software and equipment, receiving technical support, working interface issues, transitioning to LCCS, and agreeing on equipment use and time. ACAs shall be maintained to achieve interoperability and common component goals, as applicable.

3.2.7 Subcontractor Management

The contractor shall maintain the capability to manage subcontractors in accordance with the

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. The contractor shall ensure the requirements of this contract and subsequent delivery orders are applied to all subcontracts and associate contracts.

3.2.8 Cost as an Independent Variable (CAIV)

As specified by individual delivery orders, the contractor shall participate on joint Government-contractor Cost Performance IPTs to discuss tradeoff options for implementing CAIV concepts and guidance.

3.2.9 Contracting Invoice and Payment

The contractor shall document and track the status of all funds associated with the contract 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 elements of subcontracted work.

3.2.10 Contractor Manpower Reporting

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services under this contract for the LCPM 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/.

3.2.11 Metric Tracking

As specified by individual delivery orders, the contractor shall develop, track, document and provide to the Government those metrics necessary to establish the Return on Investment (ROI) for the development, implementation and upkeep of the HPL pre and post fielding.

3.2.12 Data Rights

The contractor shall provide data rights for technical data and documentation applicable to both software and hardware, so that the Government can maintain and modify the system(s) using

Government personnel and third party contractors. The contractor shall make a willful attempt to analyze feasible non-proprietary solutions and incorporate them when applicable to the effort.

This includes, but is not limited to, software rights, data, source codes, drawings, warranties, and integration efforts. The contractor shall provide data to allow the Government to:

1. Use, maintain, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction.

2. Release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, maintain, modify, reproduce, release, perform, display, or disclose that data for United States Government purposes.

3. Maintain, repair, modify, and upgrade the HPLF or HPL using Government personnel and other Government contractors.

4. Compete future requirements, maintenance, repair, modification, and upgrades.

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

Product-Line Methodology as described on the LT2 Portal when applicable. The contractor shall develop the content for the data through the LT2 tools and processes utilized on the LT2 Portal.

3.3 Systems Engineering

The contractor shall provide the requisite technical and programmatic support to complete the required tasks of the individual delivery orders associated with the LCPM engineering and management. These tasks shall encompass the efforts associated with the development, dissemination, engineering, management, maintenance, CTR, technology insertion, obsolescence, concurrency, upgrades and disposal of the P/L hardware components, and http://www.ecmra.mil/ http://www.ecmra.mil/ documentation. These tasks shall also include the work efforts associated with the engineering, management, and tracking of P/L fielded products, P/L services and core assets.

3.3.1 Hardware Engineering

After the HPL has been established and as each new Delivery Order is issued, the contractor shall perform an analysis of the HPL to ensure it is relevant, contains equipment that is supportable into the future, and is leading towards the goal of providing Training as a Service

(TAAS) (as detailed on the LT2 Portal). The contractor shall update the HPL to keep it current based on these new analyses. Throughout the life of the HPL evolution, the contractor shall disclose if any of its manufactured equipment (or a direct subcontractor) is recommended for inclusion into the HPL.

As specified by individual order, the contractor shall design, develop, integrate, assemble and test the system hardware and associated firmware that satisfies the performance and

Cybersecurity requirements stated in the delivery order. The contractor shall conduct market surveillance and market investigations in order to maximize the use of commercial and non-developmental items. The contractor shall apply the systems engineering process during each level of system development (system, subsystem, and component) to add value (additional detail) to the products defined in the prior application of the process. Through each of the design stages, information generated shall be documented in an integrated database.

3.3.2 Hardware Test Engineering

As specified by individual order, the contractor shall develop, implement, and maintain a system test process satisfying all test requirements, which is traceable throughout the design process, is integrated with other system engineering requirements, and is disseminated to design personnel and subcontractors. The contractor shall establish controls for ensuring that each subcontractor’s test practices are consistent with overall system requirements. The contractor shall define the means for verifying and validating that the diagnostic capability meets specified requirements, using maintainability demonstrations, test program verification, and other demonstration methods. The contractor shall ensure that as test and evaluation of the system progresses, problems presented by new failure modes, test voids, ambiguities, and test tolerance difficulties are recognized and defined, solutions are traceable to diagnostic hardware and software, and technical publication procedures are updated. The contractor shall define an approach for the analysis of acceptance test and evaluation results to determine how built in test hardware and software, automatic test equipment hardware and firmware, and maintenance documentation performed as a means for satisfying production testing, and meeting test requirements. The contractor shall establish a test program that accomplishes the following:

a) Establishment of sufficient, achievable and affordable diagnostic concept and state-of-the-art testability built-in and off-line test performance requirements.

b) Integration of testability into equipment and systems during the design process in coordination with the maintainability design process.

c) Evaluation of the extent to which the design meets testability requirements.

d) Inclusion of testability in the program review process.

e) End-to-end alignment, synchronization, and integration with LT2 test strategy.

3.3.3 System Integration

The contractor shall perform all activities to integrate and assemble the hardware and software to achieve a fully functional system that performs and operates in accordance with the system specification. The contractor shall verify the complete integration of the hardware and software of each hardware and software subsystem and the overall system through the utilization of formalized test procedures. A system level production approval review shall be completed to demonstrate that the total system has been verified to satisfy specification and baseline requirements for each system level, and to confirm readiness for production, distribution, operations, support, training, continuing improvement, and disposal.

3.3.4 Software Engineering

The contractor shall follow the LT2 processes for all software reuse, development and testing.

The contractor shall utilize the LT2 core assets for software to the maximum extent possible and shall use the CAWG when new software is to be developed or utilized.

As specified by individual order, the contractor shall design, implement, integrate, test and field system minor or unique software and firmware, and shall follow the contractor’s organizational software development practices. The contractor shall provide sufficient evidence that the producing software development organizations have software management and development processes documented. The design process shall incorporate features that promote assessment of open source software products, ease of operation, cybersecurity, ease of software maintenance, ease of future updates and modifications, data void work around, and any smart designs that can justify a reduction in the amount of documentation. The contractor shall conduct market surveillance and market investigations, in order to maximize the use of open source software, commercial software and non-developmental software. The contractor shall employ well-defined security policy models, structured, disciplined, and rigorous hardware and software development techniques, and sound system/security engineering principles. The contractor shall follow formal industry-accepted software development practices that are consistent with at least Level 3 of the Capability Maturity Model Integration for Development

(CMMI-DEV).

3.3.5 System Safety Program

As specified by individual delivery orders, the contractor shall maintain a safety process to identify, evaluate, and eliminate or control hazards throughout the LCPM contract. The contractor shall ensure all LCPM hardware, products and software services are designed to minimize safety and health risks to operators and maintainers in accordance with MIL-STD-882.

3.3.6 Supportability Engineering

As specified by individual delivery orders, the contractor shall conduct engineering analyses to establish quantitative and qualitative supportability guidelines. The contractor shall establish system supportability configurations consistent with system readiness and availability and life cycle cost goals specified in each specific delivery order. The contractor shall coordinate with existing LCCS using ACA, develop initial fielding plans for the system and verify that the maintenance actions and support structure are aligned with the maintenance concept.

3.3.7 Quality Engineering

As specified by individual delivery orders, the contractor shall establish measurement points that will provide maximum visibility into new and prior processes to assure contractual requirements are being met. The contractor shall select the proper methods to analyze these processes to continuously improve the system. Metrics shall be developed to assist management visibility into an adequate process control system. The contractor shall establish and maintain a computerized discrepancy tracking system with the ability to produce complete permanent records of all discrepancy or database listing. The contractor shall establish a suspense system to ensure timeliness of analysis and corrective action for discrepancies and risk reduction items.

All discrepancy correction shall be documented and entered in an integrated database.

3.3.8 Reliability and Maintainability (R&M) Engineering Program

As specified by individual delivery orders, the contractor shall establish and maintain active and effective R&M programs that meet program objectives. The R&M programs shall ensure that

Commercial Items and Non-developmental Items to be delivered to the Government as a result of the required TADSS modifications, meet the R&M requirements specified in the individual

DO Specification and the corresponding SOW. The contractor shall include the R&M programs as topics of discussion during scheduled program reviews.

3.3.9 Producibility Engineering Program

As specified by individual delivery orders, the contractor shall perform production planning to ensure a smooth, timely, and cost effective initiation of production. Planning tasks shall include those actions required to ensure that the product has stabilized, the manufacturing processes have been proven, and rate production facilities, equipment, capability, and capacity are in place to support the required delivery schedule.

3.3.10 Manpower and Personnel Integration (MANPRINT)

As specified by individual delivery orders, the contractor shall integrate human factors into the

TADSS modification design. Objectives shall include balance of system performance and cost of ownership by ensuring that the system design is compatible with the capabilities and limitations of the personnel who will operate and maintain the item as each specific DO requires.

3.4 Program and Design Reviews

As specified by individual delivery orders, the contractor shall conduct periodic program reviews at a mutually agreed upon location i.e. at the contractor facility, subcontractor, vendor facility, or

Government facilities. The contractor shall provide visibility on the progress, performance, and status of major subcontractors. The program management review shall provide a program overview and a detailed discussion of pre-selected topics. Status and information at the review shall reflect currency since the previous review. The contractor shall conduct program and design reviews and applicable Technical Interchange Meetings (TIM) for the Government and

IPT members.

3.5 Cybersecurity (Information Assurance)

As specified by individual delivery orders, the contractor shall integrate cybersecurity into their programmatic processes, document decisions, specify and track cybersecuirty requirements, document certification efforts, identify possible solutions, and maintain operational systems security in accordance with (IAW) DoDI 8500.01, DoDI 8510.01, CNSSI 1253, NIST SP 800-

53, DoDI 8582.01, AR 25-2, and the PEO STRI BAM. The contractor shall leverage LT2 software, LCPM hardware and cybersecurity processes to maximum extent possible for ease of transition to sustainment. As specified by the individual delivery orders the contractor shall address Information Assurance such as Cybersecurity Implementation, Cybersecurity

Verification, and Cybersecurity Certification and Accreditation. The contractor shall support migration from existing DoD Information Assurance Certification and Accreditation Process

(DIACAP) accreditations to performing accreditations under the RMF IAW 8500.01 and DoDI

8510.01. The RMF is the “common information security framework” for the federal government and its contractors. The contractor shall ensure all components are implemented in accordance with DISA Security Technical Implementation Guide (STIG) compliance. If a delivery order requires the use of classified data it must be addressed in accordance with AR 380-5. All personnel performing cybersecurity functions shall be trained and certified in accordance with

DoDD 8570.01 at the start of work. The contractor shall secure all unclassified DoD information on Non-DoD information systems in accordance with DoDI 8582.01.

The contractor shall maintain and update existing cybersecurity accreditation documentation

(Architecture drawings, Hardware/Software lists, Information Security Plan (ISP), Continuity of

Operation Plan (COOP), and Contingency Plan (CP)) required to maintain certification and accreditation during system upgrades. In the event a system is being accredited for the first time, the contractor shall create all cybersecurity documentation necessary to support obtaining an cybersecurity accreditation. The contractor shall use products that have been evaluated or validated through either the International Common Criteria (CC) for Information Security

Technology Evaluation Mutual Recognition Arrangement, the NIAP Evaluation and Validation

Program, or the FIPS validation program for any system design work, where available. The contractor shall use DOD-authorized assessment tools to perform cybersecurity testing.

3.6 Value Engineering

As specified by individual delivery orders, the contractor shall implement and use a value engineering program employing the value methodology. The contractor shall conduct multi-disciplined joint Government value engineering methodology workshops in order to identify and implement areas for program/process improvement.

3.7 Packing, Storage, and Transportability

As specified by individual delivery orders, the contractor shall establish a packing, storage, and transportability process which identifies the most economical practices for preservation, packing, storage and transportation and which will result in the most effective means of satisfying these requirements. The contractor shall consider areas such as environmental conditions, physical limitations (dimensions, weight, and major assemblies) which potentially may affect packing, storage, or transportability of the system.

3.8 Logistics

As specified by individual delivery orders and CDRLs, the contractor shall utilize the latest version of GEIA STD 0007,GEIA Handbook 0007 and TA-HB-0007-1. The contractor shall conduct engineering analysis to establish quantitative and qualitative supportability design guidelines.