Attachment_5_IMILES_VTESS_DO_0001_SOW.pdf

PEO-STRI-14-W091

04 January 2016

DISTRIBUTION LIST STATEMENT A:

Approved for public release; distribution is unlimited.

Statement of Work

For

INSTRUMENTABLE MULTIPLE INTEGRATED LASER ENGAGEMENT SYSTEM

(IMILES) VEHICLE TACTICAL ENGAGEMENT SIMULATION SYSTEM

(VTESS) Delivery Order (DO)-0001

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

12350 Research Pkwy.

Orlando, FL 32826-3224

Patrick Sincebaugh Systems Engineer, PM LTS

Jesse Campos Chief Engineer, PM LTS

Shanitha Coats Logistician, PM LTS

Roberto Capote Chief Logistics Manager, PM TRADE

Kyle Platt Project Director, PM LTS

LTC Corey Hemmingway Product Manager Live Training Systems http://www.peostri.army.mil/apps/

20160104 – VTESS Statement of Work ii

Revision History

REV DATE BY CHANGE

- 20160104 KP Published.

iii

Table of Contents

1.0 SCOPE

1.1 BACKGROUND

2.0 APPLICABLE DOCUMENTS

2.1 DEPARTMENT OF DEFENSE SPECIFICATIONS

2.2 AVAILABILITY OF DEPARTMENT OF DEFENSE SPECIFICATIONS

2.3 DEPARTMENT OF DEFENSE STANDARDS

2.4 AVAILABILITY OF DEPARTMENT OF DEFENSE STANDARDS

2.5 DEPARTMENT OF DEFENSE DIRECTIVES

2.6 AVAILABILITY OF DEPARTMENT OF DEFENSE DIRECTIVES

2.7 DEPARTMENT OF DEFENSE INSTRUCTIONS

2.8 AVAILABILITY OF DEPARTMENT OF INSTRUCTIONS

2.9 OTHER GOVERNMENT DOCUMENTS, DRAWINGS, AND PUBLICATIONS

2.10 AVAILABILITY OF OTHER GOVERNMENT DOCUMENTS AND PUBLICATIONS

2.11 NON-GOVERNMENT STANDARDS AND OTHER PUBLICATIONS

2.12 AVAILABILITY OF NON-GOVERNMENT STANDARDS AND OTHER PUBLICATIONS

2.13 GOVERNMENT FURNISHED MODELS

2.14 AVAILABILITY OF GOVERNMENT FURNISHED MODELS

3.0 REQUIREMENTS

3.1 PROGRAM AND FINANCIAL MANAGEMENT

3.1.1 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS)

3.1.2 Financial Management

3.1.3 Configuration Management

3.1.4 Risk Management

3.1.5 Meetings and Program Reviews

3.1.6 Production Planning

3.1.7 Government Property Management

3.1.8 Organizational Process Management

3.2 SYSTEMS ENGINEERING

3.2.1 System Design

3.2.2 Hardware Engineering

3.2.3 Software Engineering

3.2.4 Hardware and Software Integration

3.2.5 Cybersecurity

3.2.6 Requirements Traceability

3.2.7 Specialty Engineering

3.2.8 Product Definition Data (PDD)

3.3 INTEGRATED TESTING

3.3.1 First Article Test (FAT)

3.3.2 Electromagnetic Environment Effects (E3) Testing

3.3.3 Hardware/ Software Component Testing

3.3.4 Systems Verification Test (SVT)

3.3.5 Government Acceptance Test (GAT)

3.3.6 Factory Inspection and Factory Acceptance Testing

3.3.7 Test Support

3.3.8 Test Plan

3.3.9 Test and Inspection Report

3.3.10 Test Incidents (TI)

3.3.11 Logistics Demonstration (LD)

3.4 LOGISTICS

iv

3.4.1 Logistics Support Analysis

3.4.2 Supportability Analysis and Logistics Product Data

3.4.3 Parts Management Plan

3.4.4 Technical Publications

3.4.5 Item Unique Identification (IUID)

3.4.6 Development Software Support Environment

3.4.7 Test Measurement and Diagnostic Equipment

3.5 TRAINING PRODUCTS

3.5.1 Training Situation Document

3.5.2 Instructional Performance Requirements Document

3.5.3 Instructional Media Requirements Document

3.5.4 Instructional Media Design Package (IMDP)

3.5.5 Course Conduct Information Package

3.5.6 Training Conduct Support Document

3.5.7 Instructional Media Package

3.5.8 Training System Support Document

3.6 INVENTORY SUPPORT

4.0 APPENDIX A - ACRONYM LIST

Statement of Work For

Instrumentable Multiple Integrated Laser Engagement System Vehicle Tactical Engagement Simulation System

(IMILES VTESS)

1.0 Scope

This Statement of Work (SOW) defines the efforts for the production of the Instrumentable Multiple Integrated Laser Engagement System (IMILES) Vehicle Tactical Engagement Simulation System (VTESS). The requirements for this document are derived from MILES 2000 Operational Requirements Document (ORD) for Replacement of Ground Direct Fire Tactical Engagement Systems (TES) Devices, Cards Number 0291, and revised July 1996.

1.1 Background

The U.S. Army Program Executive Office for Simulation, Training and Instrumentation (PEO STRI), Project Manager Training Devices (PM TRADE), Product Manager Live Training Systems (PM LTS) has an immediate need to evolve and procure the I-MILES product line. IMILES VTESS is a product within the I-MILES product-line and is also one system within in a larger Live Training System of Systems (SoS). The IMILES VTESS acquisition will complete the Basis of Issue (BOI) and potentially replace older legacy systems. The IMILES VTESS will provide a more realistic training capability, reduce life cycle costs, and integrate emerging commercial-off-the-shelf (COTS) or modified COTS technologies.

2.0 Applicable Documents

The following documents form a part of this SOW to the extent specified herein:

2.1 Department of Defense Specifications

2.2 Availability of Department of Defense Specifications

Copies are available on the WWW at URL: http://www.assistdocs.com/search/

2.3 Department of Defense Standards

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

MIL-HDBK1222 Guide to the General Style and Format of U.S. Army Work

Package Technical Manuals MIL-HDBK-1467 Acquisition of Software Environments and Support Software

MIL-PRF-2961B Performance Spec Training Data Products

MIL-STD-31000 Technical Data Packages http://www.assistdocs.com/search/

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

MIL-STD-502 Product Support Analysis

MIL-STD-46855 Human Engineering Requirements for Military Systems, Equipment and facilities

2.4 Availability of Department of Defense Standards

Copies are available on the WWW at URL: http://www.assistdocs.com/search/

2.5 Department of Defense Directives

DoDD 4151.18 Maintenance of Military Materiel

2.6 Availability of Department of Defense Directives

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

2.7 Department of Defense Instructions

DoDI 8500.2 Information Assurance Implementation

DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT)

2.8 Availability of Department of Instructions

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

2.9 Other Government Documents, Drawings, and Publications

AR 25-1 Army Information Technology, 25 June 2013

AR 5-12 Army Use of the Electromagnetic Spectrum, 15 February

AR 700-127 Integrated Product Support, 7 October 2013

AR 700-142 Type Classification, Materiel Release, Fielding and Transfer, 17 January 2013

AR 750-1 Army Materiel Maintenance Policy, 12 September 2013

Copies are available on the WWW at URL: http://www.apd.army.mil

NIST SP 800-53 National Institute of Standards and Technology (NIST) Special Publication: Security and Privacy Controls, Revision

Copies are available on the WWW at URL: http://csrc.nist.gov/publications/pubssps

CNSSI 1253 Security Categorization and Control Selection For National Security Systems, Version 2 http://www.assistdocs.com/search/ http://www.dtic.mil/whs/directives/ http://www.dtic.mil/whs/directives/ http://www.apd.army.mil/ http://csrc.nist.gov/publications/pubssps

Copies are available on the WWW at URL: https:www.cnss.gov

PEO STRI SOP 70-1 Acquisition Program Management and Documentation

99-0008380 Consolidated Product Line Management (CPM) Operations Guide

PRF-PT-00639 Performance Specification for the Instrumentable Multiple Integrated Laser Engagement System Vehicle Tactical Engagement Simulation System (IMILES VTESS), Version 1.1

PRF-PT-00608 Live Training Engagement Composition (LTEC) Interface Control Document (ICD), Version 1.1

PRF-PT-00549 Live Player Area Network (PAN) Interface Standard, Revision C

Title 10 § 2464 Armed Forces

Copies are available on the WWW at URL: https:www.LT2Portal.org

TRADOC Reg 350-70 Army Learning Policy and Systems, 6 December 2011

TRADOC PAM 350-70-5 Systems Approach to Training: Testing, 20 August 2004

TRADOC PAM 350-70-10 Systems Approach to training Course and Courseware Validation, 29 March 2004

TRADOC PAM 350-70-12 The Army Distributed Learning (DL) Guide, 3 May 2013

TRADOC PAM 525-8-2 The U.S Army Learning Concept for 2015, 20 Jan 2011

Copies are available on the WWW at URL: http://www.tradoc.army.mil/tpubs

29 CFR 1910.1200 Occupational Safety and Health Standards / Toxic and Hazardous Substances

Copies are available on the WWW at URL: http://www.osha.gov

2.10 Availability of Other Government Documents and Publications

Copies of the above documents are available at PEO STRI, ATTN: SFAE-STRI- TRADE-LT, 12350 Research Parkway, Orlando, FL 32826-3276

2.11 Non-Government Standards and Other Publications

SAE GEIA-HB-0007 Logistics Product Hand Book

SAE GEIA-STD-0007 Logistics Product Data

2.12 Availability of Non-Government Standards and Other Publications

Copies must be contractor purchased and can be found on the WWW at URL:

http://www.nssn.org/search https://www.cnss.gov/ https://www.lt2portal.org/ http://www.tradoc.army.mil/tpubs http://www.osha.gov/ http://www.nssn.org/search

2.13 Government Furnished Models

Computerized Optimization Model for Predicting and Analyzing Support Structures

(COMPASS)

Computerized Optimization Model for Predicting and Analyzing Support Structures Lite (COMPASS Lite)

2.14 Availability of Government Furnished Models

Copies, references and training materials can be found on the WWW at https://www.logsa.army.mil/lec/compass and https://www.logsa.army.mil/lec/compass-lite/

3.0 Requirements

This SOW defines the effort required for manufacturing, integrating, testing, managing, documenting, delivering, and initially sustaining the IMILES VTESS. The Contractor shall produce an IMILES VTESS Training System that meets the performance requirements as defined in the IMILES VTESS Training System Performance Specification PRF-PT-00639.

3.1 Program and Financial Management

The Contractor shall provide the overall management and administrative effort necessary to ensure that the requirements of this contract are accomplished.

3.1.1 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS)

The Contractor shall implement, manage update, and maintain the contract IMP and an IMS for the IMILES VTESS program. The Contractor shall develop and complete all planned IMS tasks for each milestone. The Contractor shall provide IMS and IMP data to the Government and review the data at Program Management Reviews (PMR). The Contractor shall manage cost, schedule, technical performance, and address Life Cycle Cost (LCC) considerations in program decision making. The Contractor shall report on work in progress in accordance with (IAW) the IMP at each program review, at selected technical reviews and at Government’s discretion. The IMP shall depict the contract work breakdown structure (CWBS). The Contractor shall coordinate and maintain an IMS that shows the work planned to achieve each significant accomplishment and the criteria leading up to each event.

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

3.1.2 Financial Management

The Contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The Contractor shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations and invoices against each contract line item and subline item. The https://www.logsa.army.mil/lec/compass https://www.logsa.army.mil/lec/compass-lite/ https://www.logsa.army.mil/lec/compass-lite/

Contractor shall extend the Government-provided Program Work Breakdown Structure (PWBS) to lower levels in the CWBS. It defines the lower level components of what is to be procured and includes all the product elements (hardware, software, data, or services), which are defined by the Contractor and the Contractor’s responsibility.

The extended CWBS 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 in the extended CWBS. The Contractor may propose changes to the CWBS to enhance its effectiveness in satisfying program objectives. The Contractor shall continually update an integrated database during contract performance with pertinent records and data that underlie and support the cost and schedule data reported.

A001 - (DI-MGMT-81651) Contract Invoicing and Payment Report

3.1.2.1 Earned Value Management

The Contractor shall integrate cost, schedule, and performance management information. The Contractor shall develop, implement, maintain, and use an EVM system that complies with Industry Guidelines ANSI/EIA-748 and meets contractual requirements. The Contractor shall document the integrated cost and schedule status of work progress on the contract and relate technical performance with cost and schedule accomplishment using procedures for planning work, controlling costs, and measuring performance based on ANSI/EIA-748.

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

3.1.2.2 Integrated Baseline Review

The Contractor shall participate with the Government in the assessment of program risk and the degree to which the following have been established:

a. Technical scope of work is fully included and is consistent with authorizing documents.

b. Project schedule key milestones are identified and supporting schedules reflect a logical flow to accomplish the work.

c. Resources (budget, facilities, personnel, skills, etc.) are available and are adequate for the assigned tasks.

d. Tasks are planned and can be measured objectively relative to the technical progress.

e. Rationales underlying the review are reasonable.

f. Management processes support successful execution of the project.

3.1.3 Configuration Management

The Contractor shall use an automated internal configuration management process to monitor, update, and control all configuration documentation, physical media, and physical parts representing or comprising the system configuration items (CIs). The Contractor shall plan and implement an automated configuration management function to perform configuration control, configuration identification, audits, and status accounting in a system engineering environment. The Contractor shall develop, maintain, and update configuration management procedures and processes for control of all hardware and software baselines. The process shall allow Government simultaneous access to the common product data model coupled with the ability to coordinate and update immediate changes to the product definition data. The configuration management process must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant events. The Government will maintain control of the functional baseline (FBL) defined by the system performance specification, interface control documents, and software requirement specifications.

3.1.3.1 Configuration Management Planning and Management

The Contractor shall establish processes and tools to establish and maintain consistency between system requirements, system configuration information, and all relevant information about the system. The configuration management process shall include changes made to the IA configuration and associated documentation. Failure to include IA considerations in the configuration management and engineering change control processes could adversely affect the program’s ability to integrate and maintain IA in the functional design of the system. This will affect the system's ability to obtain IA accreditation. It may also increase the system's susceptibility to computer network attack from information operation activities. The Contractor shall:

a. Plan implementation of the CM functions for the context and environment in which they are to be performed and manage in accordance with the planning.

b. Determine the specific CM value-adding functions and levels of emphasis.

c. Document how your organization will implement CM functions to provide the consistency between the system’s attributes, system definition information and the system’s configuration information, throughout the applicable phases of the life cycle.

d. Identify resources required to implement the CM functions and ensure they are applied throughout the system’s life cycle.

e. Assess the effectiveness of CM plan implementation and performance of the configuration management functions with performance measurements.

f. Flow down responsibility for CM performance to subcontractors.

g. Plan and identify information status levels for managing system configuration information and ensure that transmitted data products are usable.

3.1.3.2 Configuration Identification

The Contractor shall identify unique identifiers for selected system attributes, system information and components to be used as the basis for configuration management.

The Contractor shall:

a. Define the functional, performance, interface and physical attributes of the system and components.

b. Determine the systems composition using its product definition information.

c. Assign unique identifiers to configuration items so that they can be distinguished from other items, one configuration of the system can be distinguished from another, the source of a component can be determined, and the correct system definition information can be retrieved.

d. Assign unique unit identifiers to individual components of the system.

e. Update component identifiers when a system is modified reflecting the new configuration without altering the system identifier and model identifier.

f. Uniquely identify information so that it can be correctly associated with the applicable configuration of the system.

g. Apply information identification rules to maintain representation and version relationships.

h. Maintain relationships between information, information requirements, and the related system configuration to ensure accurate information retrieval.

i. Establish complete, valid, and suitable for use agreed-to descriptions of the attributes of the system and components at a point in time and provide a known configuration to which changes can be addressed.

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

3.1.3.3 Configuration Change Management

The Contractor shall establish a systematic and measurable configuration change management process for managing product configuration changes and variances.

Once the system requirements have been approved by an authorized management activity, the Contractor shall effect changes to the baseline requirements only after the proposed change has been approved using the change process. The Contractor shall:

a. Document and uniquely identify each change.

b. Classify requested changes to aid in determining the levels of review and approval.

c. Clearly and completely document request for change.

d. Consider the technical, support, schedule, and cost impacts of a requested change before making a judgment to approve the change for implementation and incorporation in the system and its documentation.

e. Determine potential effects of a change and coordinate impacts with the impacted areas of responsibility.

f. Determine the effectivity for each change and identify which units of the system are to be changed, the point of production break-in, and which units will be included in a retrofit.

g. Verify implementation of a change to ensure consistency between the system, its documentation, and its support elements.

h. Document variances, when authorized by the appropriate level of authority.

3.1.3.4 Configuration Status Accounting

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

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

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

c. Capture configuration information as it evolves.

3.1.3.5 Configuration Verification and Audit

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

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

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

3.1.3.5.1 Contractor Internal Hardware Build-Up Audit

Concurrent with manufacture of piece parts and incoming inspection of procured parts, a 100% audit shall be conducted by personnel approved by the QA Manager to verify the as-built configuration matches the design documentation prior to use of each part in First Article and Full Rate Production. During this process each product definition document will also be examined for proper format (compliance with ANSI Y14 series standards), completeness, currency of material references, accuracy of piece part identification, and adequacy of manufacturing instructions and any other information critical to acquire a like part. A record of each product attribute verified shall be maintained and available through the integrated development environment.

3.1.3.5.2 Government Sample Audit to verify Product Baseline

After completion of acceptance testing and any required design modifications, but prior to formal acceptance, the final product baseline shall be verified by the Government by reviewing a representative number of drawings, associated technical manuals, logistics management information and manufacturing instructions to determine their accuracy in accordance with the final product configuration design.

3.1.3.6 LT2 Configurations Management (CM)

The Contractor shall implement a configuration management process that establishes and maintains consistency of the IMILES VTESS, the Live Training Engagement Composition (LTEC) Software Product Line, PRF-PT-00608 (LTEC ICD), and PRF- PT-00549 (Live Player Area Network Interface Standard) items with its requirements and configuration information. The IMILES VTESS CM process shall be fully integrated and synchronized with the LT2 CPM Construct processes.

3.1.3.7 LT2 CM Planning

The Contractor shall provide software and hardware CM planning and implication to include projected obsolescence and technical refreshment.

3.1.3.8 LT2 Configuration Identification

The Contractor shall establish a structure to select, define, document, and baseline IMILES VTESS, Live Training Engagement Composition (LTEC) Software Product Line, PRF-PT-00608 (LTEC ICD), and PRF-PT-00549 (Live Player Area Network Interface Standard), components and attributes, and assign unique identifiers for configuration items under configuration control.

3.1.3.9 LT2 Configuration Change Control

The Contractor shall execute all LT2 connected processes IAW Document No. 99- 0008380 Consolidated Product Line Management (CPM) Operations Guide that ensures changes to the IMILES VTESS, Live Training Engagement Composition (LTEC) Software Product Line, PRF-PT-00608 (LTEC ICD), and PRF-PT-00549 (Live Player Area Network Interface Standard) baselines are identified, justified, recorded, coordinated, evaluated, and approved or disapproved by the Core Asset Working Group (CAWG) and the Product Manager Live Training Systems (PM LTS).

3.1.3.10 LT2 Configuration Status Accounting

The Contractor shall manage the configuration status accounting of IMILES VTESS, the

Live Training Engagement Composition (LTEC) Software Product Line, PRF-PT-00608 (LTEC ICD), and PRF-PT-00549 (Live Player Area Network Interface Standard) configuration information necessary to account for each configuration.

3.1.3.11 Engineering Change Proposals (ECP)

The Contractor shall document and the IPT shall review all changes to established baselines and all changes to the requirements (other than the functional baseline), including changes to the statement of work, contract data requirements list (CDRL), the contract schedule, and the general provisions of the contract.

A022 - (DI-SAFT-80103) Engineering Change Proposal System Safety Report

A040 - (DI-SESS-81880) Engineering Change Proposal (ECP)

A041 - (DI-SESS-81881) Notice of Revision (NOR)

A024 - (DI-MISC-80508) CCB Minutes

3.1.3.12 Engineering Change Proposal Review (ECP)

In coordination with the Government, the Contractor shall hold a requirements review on all proposed changes prior to the submittal of the ECP in order to clarify requirements, format, and content. Depending upon the criticality of the proposed changes, this review may take the form of a teleconference, a video-teleconference, a formal meeting at PEO STRI, or a formal meeting at the Contractor’s facility. All appropriate parties shall be in attendance in order to conduct a thorough, effective review. Minutes shall be a historical record to allay any miscommunications.

3.1.3.13 Variances

The Contractor shall document the rationale and the potential impact of any variance.

The Contractor shall obtain approval before varying from any Government-controlled baseline.

A039 - (DI-SESS-81883) Request for Variance (RFV)

3.1.4 Risk Management

The Contractor shall prepare, implement, and maintain a risk and opportunity management process that includes identification, analysis, mitigation planning, mitigation plan implementation, and tracking. The Contractor shall develop and implement IA risk management, which will include security safeguards. These safeguards shall include but are not limited to local policy and guidance, identifies threats, problems and requirements, and adequately plan for the required resources.

The Contractor’s risk management process shall measure future uncertainties in achieving program goals within defined cost, schedule, and performance constraints.

The IA risk shall be addressed across the risk management process and can be addressed in multiple areas.

A016 - (DI-MGMT-81808) Contractor’s Risk Management Plan

3.1.5 Meetings and Program Reviews

The Contractor shall attend and conduct meetings, reviews and working groups. The Contractor shall document action items, coordinate resolutions and track action items until closure.

3.1.5.1 Post Award Conference

A post award conference shall be held at the Contractor’s facility within the CONUS at a mutually agreed to date within 30 days of contract award. The conference shall include:

a. A discussion of the top level management of the program.

b. An agreement on metrics that will be used as management indicators during the program and the partnering approach to implement.

c. An introduction of key IPT participants and structure.

d. Identification of specific points of contact.

e. A discussion on both parties understanding of the scope of work.

f. A review of the requirements traceability matrix.

g. System Requirements.

h. Other contract issues.

3.1.5.2 Program Management Reviews (PMR)

The Contractor shall plan and support PMRs. The Contractor shall present the following topics quarterly:

a. IMS & IMP.

b. Design modifications and details.

c. Identify problems (Risk Management).

d. Program status including testing status.

e. Production status including Parts Management status.

f. CDRL status.

g. Contract status.

h. Wide Area Workflow (WAWF) and Disbursement Reports.

i. Information Assurance Status.

A006 - (DI-MGMT-81605) Briefing Materials (PMR)

A005 - (DI-ADMN-81505) Report, Record of Meeting/Minutes

3.1.5.3 Technical Interchange Meetings (TIMs)

The Contractor shall support TIMs. A TIM shall address specific topics or issues, address status test activities between management reviews, address the functions of an established working group, or coordinate and provide guidance for engineering data or technical publications. The Contractor shall support the Live Training Standards (LTS) Working Groups and the PM TRADE embedded training working group. The Contractor shall host, lead and conduct one Industry Standards Working Group meeting per quarter.

3.1.5.4 Visitor Support

The Contractor shall host visits and arrange for and provide demonstrations of system performance, program progress, and other system characteristics when notified by the procurement contracting officer.

3.1.5.5 Integrated Product Team (IPT) Meetings

The Contractor shall host weekly IPT meetings and address the full spectrum of the program concerns. The Contractor shall document action items, coordinate resolutions, and track action items until closure. Topics to be covered shall include:

a. Risk Status.

b. Work in Progress (WIP) Status.

c. Critical program items (e.g. CDRLs, Financials, Schedule, Engineering, and Logistics).

A005 - (DI-ADMN-81505) Report, Record of Meeting/Minutes

3.1.5.6 Associate Contractor Agreements (ACA) and Industry Standards Working Groups (ISWG)

The Contractor shall maintain an ACA with the Life Cycle Contractor Support (LCCS) Contractor and the CPM/CPM Next Contractor. The Contractor shall also enter into a Non-Disclosure Agreement (NDA) with Government Contractors vehicle Original Equipment Manufacturer (OEMs) to which the IMILES VTESS shall interface. The contractor shall be required to host ISWG, once per quarter, to discuss the progress and enable a collaborative exchange of technical information between the various contractors in the Live Training community.

3.1.5.7 Program and Design Reviews

The contractor shall conduct program and design reviews and applicable Technical Interchange Meetings for the Government and IPT members as required to execute and technically manage the IMILES VTESS efforts.

3.1.5.7.1 System Design Review

The contractor shall conduct a System Design Review which is a multi-disciplined product and process assessment that ensures the system can proceed into system fabrication, demonstration, test and sustainment, while meeting the stated performance requirements within cost (program budget), schedule (program schedule), risk, and other system constraints. This review shall assesses the system final design as captured in product technical documentation (to include Hardware Component Agreements (HCAs)) for each configuration item in the system (product baseline), and ensures that each product in the product baseline has been captured in the detailed design documentation.

The subsystem detailed designs shall be evaluated to determine whether they correctly and completely implement all system requirements allocated to the subsystem, human-systems integration and whether the traceability of final subsystem requirements to final system detail design is maintained. At this review the IPT will also review the results of peer reviews on requirements and final detail design documentation, and ensure that latest estimates of cost (development, production, and support) are consistent with the detail design. The contractor shall brief Level of Repair Analysis (LORA) inputs and data used in the Computerized Optimization Model for Predicting and Analyzing Support Structures (COMPASS) model, the Army standard LORA model per AR 750-1 Materiel Maintenance Policy and as described in AR 700-127 Integrated Product Support. In addition, the contractor shall brief the proposed determination of repair level to assist the Government in determining the optimum maintenance levels for repair actions and recovery of the end item and Components. A successful review is predicated on the IPT’s determination that the subsystem requirements, subsystem detail design, results of peer reviews, and plans for testing form a satisfactory basis for proceeding into system fabrication, demonstration and test.

The Contractor shall develop all derived technical requirements and architecture in accordance with the LT2 TESS Architecture. The Contractor shall derive all system requirements into detailed technical requirements by component. The derived technical requirements shall be the results from a logical analysis decision or physical design solution decision. A derived technical requirement is a 'design-to' requirement for the Design. All analysis and results shall be documented in an integrated database and a RTM. As part of this activity, the Contractor shall work within the LT2 IPTs to iterate the system and System-of-System (SoS) software requirements and architecture. The Contractor is encouraged to suggest revisions to Government requirements where such revisions would result in cost or schedule reduction or performance improvements. The Contractor shall record the operational concept for the system, and define and record the architectural design of the system (identifying the components of the system, their interfaces, and a concept of execution among them) and the traceability between the system components and system requirements. Based upon analysis of system requirements, system design, and other considerations, the Contractor shall define and record the software requirements to be met by each software item, the methods to be used to ensure that each requirement has been met, and the traceability between the software item requirements and system requirements. The Contractor shall evaluate the

IA requirements to assess any impacts on developed software and provide potential solutions, if applicable. The Contractor shall use modeling and simulation as appropriate for architecture validation. In addition, the Contractor shall determine if LTEC or existing open source software products are capable of meeting any operational capabilities, perform a detailed software reuse evaluation, and document the results of the analysis. The Contractor shall conduct architecture evaluations, including stakeholders external to the Contractor’s organization, for each software build.

A020 - (DI-SESS-81771) Reuse Management Report

A015 - (DI-ADMN-80925) Revisions to Existing Government Documents (HCAs)

A010 - (DI-ADMN-80925) Revisions to Existing Government Documents (SCA)

3.1.5.8 Test Readiness Review (TRR)

The Contractor shall address the following key issues at the TRR prior to the start of each Government witnessed test event to ensure that documentation is complete, test facilities are ready and prior test(s) were successful or open issues have been addressed: to include.

a. Test procedures comply with plans and descriptions, are adequate to accomplish test requirements and satisfy requirements for verification.

b. Pre-test predictions and informal tests indicate testing will confirm performance.

c. New or modified test equipment, facilities and procedure manuals required to accomplish planned test and evaluation, are available and satisfy the test requirements.

d. Identify the perceived risk level for the test and provide path for mitigation.

e. All required test resources (e.g. Manpower, Personnel and Training).

3.1.5.8.1 Documentation to be reviewed during the TRR

a. Evidence that the test management system as required under the contract is ready to accept the qualification tests and their results.

b. Evidence that the requirements in the performance specification have been traced to test procedure requirements traceability matrix.

c. A list of outstanding problem reports, both external and internal cross-referenced to the contracted deliverable end items or development hardware and software products.

d. Test requirements.

e. Pending changes to requirements.

f. Design changes since the last design review.

g. Test constraints based on previous testing or test hardware limitations.

h. Test configuration (test article and instrumentation and support equipment).

i. Detailed test procedures including Government resources required to conduct the test.

j. Plans for collection, reduction and analysis of the test data.

k. Test equipment calibration plan and status.

3.1.5.9 Production Readiness Review

The Contractor shall conduct a PRR following the First Article Test to demonstrate that the total system has been verified to satisfy specification and baseline requirements for each system level, and to confirm readiness for full-rate production, distribution, operations, support, training, continuing improvement, and disposal. The review shall ensure that:

a. Issues for the component, assemblies, subsystem, products and life cycle process and services are resolved.

b. Test procedures for components, assemblies, and products were completed and were accurate.

c. The system and products were confirmed ready for test.

d. Tests were conducted in accordance with established procedures.

e. An audit trail from design reviews, held after detailed design, is established with changes substantiated, and all component, subsystem, and system products meet specification requirements.

f. Risk-handling procedures are satisfactory for production.

g. Evolutionary development requirements and plans have been refined.

h. Planning is complete and procedures, resources, and other requisite people, products, and processes are available (or programmed to be available) to initiate production, distribution, operations, support, training, disposal, and evolutionary development (if any).

i. All production/build documentation shall be made available during all reviews and shall not contain any build information not contained in the Product Definition Date (PDD).

j. Manufacturing processes are in place.

3.1.6 Production Planning

The contractor shall perform production planning to insure a smooth, timely, and cost effective initiation of production. Planning tasks shall include those actions required to ensure that the IMILES VTESS has stabilized, the manufacturing processes have been proven, and that adequate production facilities, equipment, capability, and capacity are in place to support the required delivery rate schedule. The contractor shall maintain the functional architecture, the allocated baselines, and any elements of the product baseline so that they balance system performance, cost, schedule, and risk. The contractor shall inform the government of changes that could affect performance, cost, schedule, or risk before they are implemented. Contractor shall maintain the change history of the product baseline (date, rationale, and authority for each change and all previous baselines), as required.

3.1.6.1 Low Rate Initial Production (LRIP)

The contractor shall deliver Prime Item Units with Provisioned Items Order (PIO) spares and Special Tools and Test Equipment (ST&TE) to support LRIP First Article Test (FAT) testing to include functional, range, radiated emissions [electromagnetic radiation (EMR)], radiated susceptibility [electromagnetic environment (EME)], electromagnetic interference (EMI), electrostatic discharge (ESD) effects and environmental testing. At the end of LRIP FAT, the contractor shall make necessary repairs and deliver to government the repaired I-MILES TVS FAT units to like new condition. Prior to start of LRIP, all IMILES VTESS Production Drawings shall fully capture all Quality Assurance Provisions (QAPs) associated with execution of each step of the production process.

3.1.6.2 Full Rate Production (FRP)

The contractor shall deliver IMILES VTESS devices with Provisioned Items Order (PIO) spares and ST&TE which are inclusive of all necessary repairs and modifications resultant from Independent Government Test (IGT) and Independent Government Component Validation. The contractor shall ensure all IMILES VTESS Production Drawings fully capture all modifications and changes to the production baseline as well as Quality Assurance Provisions (QAPs) associated with execution of each step of the production process.

3.1.7 Government Property Management

The contractor shall be responsible for all costs related to making Government Furnished Property (GFP) available for use, such as payment of transportation, installation and rehabilitation costs.

3.1.8 Organizational Process Management

The contractor shall use organizational processes equivalent to Capability Maturity Model Integration (CMMI) level 3 or higher. The contractor shall provide process reports to include but not be limited to Project Planning; Requirements Management;

Requirements Development; and Technology Solutions.

3.2 Systems Engineering

The Contractor shall implement a system engineering process that will transform all system and IA requirements into a set of lower level performance requirements that define the system. The process shall accomplish planning, identify and allocate functional requirements, identify participation in trade studies, provide inputs to documentation, and include design reviews. The system engineering effort shall integrate all elements of a multifunctional engineering effort to meet system requirements. The Contractor shall insure the timely integration of engineering specialties such as reliability, maintainability, security engineering, logistics engineering, human factors engineering, safety, value engineering, standardization, and transportability into design and development. The Contractor shall as part of the systems engineering effort develop and maintain the Systems Engineering Management Plan (SEMP) as a living document. The Contractor shall use the SEMP to identify and assure control of the overall technical management process.

B008 - (DI-SESS-81785A) Revisions to Existing Government Documents (HCA)

3.2.1 System Design

The Contractor shall use the Performance Specification IMILES VTESS PRF-PT-00639 as the basis for development of all lower level specifications. The Contractor shall perform trade off studies and then finalize the system design. The design concept shall include incorporate an open systems approach which shall be based on an engineering and business strategy to choose specifications and standards adopted by industry standards bodies or de facto standards (set by the market place) for selected system interfaces, products, practices and tools. Selected designs and specifications shall be based on performance, cost, IA, industry acceptance, long term availability and supportability, and upgrade potential. The System Design shall include any and all considerations necessary to support an Organic Maintenance concept. This includes an identification of any proprietary components down to the piece part level and any design data that does not completely disclose the design down to the piece part level, with the exception of COTS items.

3.2.1.1 System Modification

The Contractor shall execute all LT2 processes IAW Document No. 99-0008380 Consolidated Product Line Management (CPM) Operations Guide to identify updates to the Live Training Engagement Composition (LTEC) Software Product Line, PRF-PT- 00608 (LTEC ICD) and PRF-PT-00549 (Live Player Area Network Interface Standard).

The Contractor shall integrate the LT2 connected processes defined in 99-0008380 Consolidated Product Line Management (CPM) Operations Guide into their program management, systems, development and test engineering functions. The Contractor shall assist the CPM/CPM Next Contractor to determine overall IMILES VTESS system impacts to the LTEC baseline. The Contractor shall identify, propose, and upon Government approval make necessary LTEC software changes fully utilizing the LT2 construct environment and LT2 processes. The resulting baseline changes and technical data will be provided to the CPM/CPM Next contractor for incorporation into the LTEC baseline. The contractor shall integrate LTEC software baseline updates approved by the Government into the IMILES VTESS baseline. If new or modified LTEC software components are needed in order to meet a IMILES VTESS requirement, the Contractor shall, execute the LT2 connected process in accordance with 99-

0008380 Consolidated Product Line Management (CPM) Operations Guide. The Contractor shall perform trade off studies and then finalize the system configuration.

The delivered solution shall be modular, scalable, and flexible. The effort shall necessitate the Contractor to analyze, configure, install and verify operation of the solution.

The Contractor shall develop a set of HCA for the components necessary to meet the requirements of the contract. The Contractor shall develop a System Composition Agreement (SCA) for IMILES VTESS as a complete and cohesive system. The Government will provide draft HCAs and SCA as GFI. The Contractor shall make revisions to these existing Government documents, as required to meet the requirements of the contract.

A015 - (DI-ADMN-80925) Revisions to Existing Government Documents (HCA)

A010 - (DI-ADMN-80925) Revisions to Existing Government Documents (SCA)

3.2.1.2 Fabrication, Assembly, Integration and Test Stage

The Contractor shall resolve product deficiencies when specifications for the system, product, subsystem, assembly, or component are not met, as determined by inspection, analysis, demonstration, or test. The Contractor shall verify that the products designed satisfy specifications. The Contractor shall integrate security engineering processes into the design to achieve an integrated secure solution.

3.2.1.2.1 Functional and Physical Configuration Audits

Functional configuration audits (FCAs) shall be completed to verify that products have achieved requirements; that they satisfy the characteristics as specified in specifications, interface specifications, and other baseline documentation; and that test plans and procedures were complied with. The results of the audit shall be documented. The Contractor shall support a physical configuration audit (PCA) on the as built configuration after Systems Verification Test (SVT) to verify and validate the PDD. All PDD documents shall be included in the review. Review shall be completed to the piece part level. The Contractor shall hold a Government witnessed FCA and PCA as mutually agreed to by both parties.

3.2.2 Hardware Engineering

The Contractor shall integrate and assemble the system hardware that satisfies the performance and IA requirements stated in the developed specifications. 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 following design stages, information generated shall be documented in an integrated database.

3.2.3 Software Engineering

The design shall incorporate features that promote ease of operation, IA, ease of software maintenance, ease of future updates and modifications, data void work around, and also any smart designs that can justify a reduction in the amount of documentation. Computer programs and computer data system shall be fully integrated in accordance with the system specification. The Contractor shall conduct market surveillance and market investigations, in order to maximize the procurement of commercial and non-developmental software. The Contractor shall maintain a software Controlled Development Environment that complies with the NIST SP 800-53 Revision

3. 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 develop and maintain a Software Development Plan (SDP) to ensure visibility into software development processes and practices.

B003 - (DI-IPSC-81441A) Software Product Specification (SPS)

B004 - (DI-IPSC-81442A) Software Version Description (SVD)

B007 - (DI-IPSC-81427A) Software Development Plan (SDP)

3.2.4 Hardware and Software Integration.

The Contractor shall perform all activities to integrate and assemble the hardware and software to achieve a fully functional and accredit-able system, with all support systems, that performs and operates in accordance with the system specification and Contractor generated specifications. 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.

3.2.5 Cybersecurity

The Contractor shall develop and maintain an Cybersecurity process to guide management and modification actions, document decisions, specify and track Cybersecurity requirements, document certification efforts, identify possible solutions, and maintain operational systems security. The Contractor shall establish or adopt standards for managing Cybersecurity requirements and capabilities and an Cybersecurity engineering approach that emphasizes purposeful modification or configuration of security solutions. Contractor shall configure, integrate, and implement all architectures, plans, policies and security controls IAW the Department of Defense Risk Management Framework process.

3.2.5.1 Security Authorization Package Information Assurance Artifacts

The Contractor shall support the Government Cybersecurity process in accordance with DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT), Committee on National Security Systems Instruction (CNSSI) 1253, and the

National Institute of Standards and Technology (NIST) SP 800-53. The Contractor shall produce all components of the RMF package necessary to deliver and operate a fully accredited system. The Contractor shall ensure that the security requirements and procedures are met in accordance with all required DoD and Army regulations for a Confidentiality level of Low, an Integrity level of Low and Availability level of low.

A011 - (DI-MISC-80711A) Scientific and Technical Reports (RMF Package)

3.2.5.2 Information Assurance Vulnerability Management Program

As part of the Information Assurance Vulnerability Management Program (IAVMP), the Contractor shall document the incorporated and unincorporated Information Assurance Vulnerability Alerts (IAVAs), Information Assurance Vulnerability Bulletins (IAVBs), and Information Assurance Vulnerability…