Attachment_1_IMILES_VTESS_Basic_SOW.pdf

PEO-STRI-15-W47

04 January 2016

DISTRIBUTION LIST STATEMENT A:

Approved for public release; distribution is unlimited.

Statement of Work

For

INSTRUMENTABLE MULTIPLE INTEGRATED LASER ENGAGEMENT SYSTEM

VEHICLE TACTICAL ENGAGEMENT SIMULATION SYSTEM

(IMILES VTESS)

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

12350 Research Pkwy.

Orlando, FL 32826-3276

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 Base 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

3.0 REQUIREMENTS

3.1 MANAGEMENT, ORGANIZATION AND PROCESSES

3.1.1 LT2 Core Asset Evolution

3.1.2 Product Integration, Fielding and Sustainment

3.2 PROGRAM MANAGEMENT

3.2.1 Integrated Product and Process Development (IPPD)

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

3.2.3 Earned Value Management (EVM) System

3.2.4 Configuration Management

3.2.5 Risk Management

3.2.6 Associate Contractor Agreements (ACAs)

3.2.7 Meetings and Program Reviews

3.2.8 Subcontractor Management

3.2.9 Cost as an Independent Variable (CAIV)

3.2.10 Computer Hardware, Enterprise Software Solutions (CHESS) Program

3.2.11 Contracting Invoicing and Payment

3.3 SYSTEMS ENGINEERING

3.3.2 Hardware Engineering

3.3.3 Test Engineering

3.3.4 Hardware and Software Integration

3.3.5 Technology Insertion

3.3.6 System Safety Program

3.4 SPECIALTY ENGINEERING

3.4.1 Reliability Engineering

3.4.2 Maintainability Engineering

3.4.3 Safety Engineering

3.4.4 Producibility Engineering

3.4.5 Quality Engineering

3.4.6 Supportability Engineering

3.4.7 Human-Systems Integration (HSI)

3.4.8 Value Engineering

3.5 CYBERSECURITY

3.5.1 Anti-Terrorism Level 1 Training

3.5.2 iWATCH Training iv

3.5.3 Protection Policy & Procedures

3.5.4 Access to Government Information Systems

3.5.5 OPSEC Plan

3.5.6 OPSEC Training

3.5.7 Information Assurance / Information Technology Training

3.5.8 Spectrum Management

3.6 LOGISTICS

3.6.1 Contractor Support

3.6.2 Disclosure of Information

3.7 WEAPON AND AMMUNITION STORAGE AND TRANSPORTATION

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) Indefinite Delivery/ Indefinite Quantity (ID/IQ) contract. 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. The IMILES VTESS IDIQ contract will be utilized by Department of Defense organizations that desire to procure IMILES VTESS devices.

This SOW defines the general tasks that Project Manager Training Devices (PM TRADE) desires to have performed under the IMILES VTESS IDIQ contract in support of a componentized training system. Individual delivery orders will delineate the detailed requirements in each respective Delivery Order (DO) SOW. PM TRADE envisions the evolution of IMILES VTESS in the following ways:

Architecture Evolution.

Software Integration.

Hardware Integration.

Instrumentation System Integration.

Live Training Engagement Composition (LTEC) Evolution.

Production.

Testing / Automated Testing.

Fielding.

New Equipment Training.

Interim Contractor Support (ICS).

1.1 Background

The U.S. Army Program Executive Office for Simulation, Training and Instrumentation (PEO STRI), 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-STD-882E System Safety

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

DoDM 5200.1 Information Security Program

DoDD 8570.01 Information Assurance (IA) Training, Certification, and Workforce Management

DoD 8570.01-M Information Assurance Workforce Improvement program

DoD 5100.76-M Physical Security of Sensitive Conventional Arms, Ammunition, and Explosives (AA&E)

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

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 5-12 Army Use of the Electromagnetic Spectrum, 15 February

AR 25-2 Information Assurance http://www.assistdocs.com/search/ http://www.assistdocs.com/search/ http://www.dtic.mil/whs/directives/ http://www.dtic.mil/whs/directives/

AR 525-13 Antiterrorism

AR 530-1 Operations Security

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

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

ANSI/EIA-748 Earned Value Management

2.12 Availability of Non-Government Standards and Other Publications

Copies are available on the WWW at URL: http://www.eia.org

3.0 Requirements

The requirements defined herein shall form the basis for all work that shall be performed as part of DOs the Government will issue under the IMILES VTESS IDIQ contract for the integration, prototype production ,testing, fielding, sustainment and product line management of the IMILES VTESS system and it’s Live Training Transformation (LT2) Core Assets and Products.

3.1 Management, Organization and Processes

In support of the IMILES VTESS, the contractor shall perform the programmatic activities, which provide for an optimized Product Line (P/L) organizational structure.

The contractor’s approach shall ensure efficient processes for the management and oversight of the IMILES VTESS technical activities including resources utilized across all IMILES VTESS delivery orders. The following table provides a representative list of tasks and activities that could be required by specific delivery orders.

Associate Contractor Agreements Interface Management

Business Strategy Life Cycle Support

Concept of Operations Meetings & Program Reviews

Conferences Metrics, Measurement and Tracking

Configuration Change Management Organizational Planning

Configuration Identification Post Award Conference

Configuration Management Program Management

Configuration Management Planning and Management

Program Management Review

Configuration Status Accounting Requirements Management

Configuration Verification and Audit Resource Planning and Management

Customer Interface Management Reuse Analysis http://www.apd.army.mil/ http://www.eia.org/

Data Repository Risk Management

Decision Analysis Technical Assessment

Design Review Technical Data Management

Earned Value Management Technical Interchange Meetings

Engineering Change Proposal Technical Planning

Facilities Management Technical Reviews

Financial Management Technology Forecasting

Hardware Audit Test Readiness Review

Integrated Baseline Review Training

Integrated Master Schedules / Plans Variance / Variance Management

Integrated Product Team Management Visitor Support

3.1.1 LT2 Core Asset Evolution

The contractor shall perform the necessary tasks and activities to continue the development, evolution, and sustainment of the IMILES VTESS LT2 Core Assets. The Government will address the specific requirements in each delivery order. The following table provides a representative list of tasks and activities that could be required by specific delivery orders with respect to IMILES VTESS Core Asset Development & Evolution:

Architecture development P/L Developer Training

Architecture evaluation Performance Verification & Validation

Architecture validation Quality Assurance

Configuration Management Requirement Engineering

Decision Analysis Re-Use Analysis

Domain Analysis Service/Component Development

LT2 Configuration Management Standards Development and Sustainment

LT2 Configuration Change Control Technology Insertion

LT2 Configuration Identification Test & Verification

LT2 Configuration Management Planning Variation Management

LT2 Configuration Status Accounting Version Control

Obsolescence Management and Planning

3.1.2 Product Integration, Fielding and Sustainment

The contractor shall perform the necessary tasks and activities for product development integration, prototype production, testing, fielding and sustainment. The Government will address the specific requirements in each delivery order. The following table provides a representative list of tasks and activities that could be required by specific delivery orders with respect to Integration, Fielding and Sustainment:

Assembly Production

Code and Unit Test Production Planning

Cold Start Test Production Readiness Review

Component Testing Prototyping

Concept Development Quality Assurance

Configuration Management Quality Engineering

Cyber Security Reliability Engineering

Electromagnetic Environmental Effects Test & Analysis

Requirements Analysis, Management & Traceability

Fabrication Risk Management Framework Testing and Certification

Factory Inspection Safety Assessment

Fielding Safety Engineering

First Article Test Security Engineering

Full Rate Production Software Engineering

Functional Analysis Software Integration

Government Acceptance Test Spectrum Management

Hardware / Software Integration System Demonstration

Hardware Engineering System Design

Hardware Integration System Engineering

Hazards Tracking & Risk Resolution System Integration

Health Hazard Assessments System Modification

Information Assurance Vulnerability Management

Systems Verification Test

Integrated Testing & Test Planning Test and Inspection Report

Low Rate Initial Production (LRIP) Test Discrepancy Management

Maintainability Engineering Test Support

Manpower and Personnel Integration

(MANPRINT)

Testing & Test Engineering

Operations Security Trade Studies

Post-Deployment Software Support

(PDSS)

Training

Post-Production Software Support

(PPSS)

Training Product Verification & Validation

Producibility Engineering Validation Testing

Product Definition Data (PDD) Verification Testing

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 requirements of Request for Proposals (RFPs) and delivery order 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 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. The contractor shall make available to the Government all technical, cost and schedule data for each specific order of the order IPT. The contractor shall maintain processes that facilitate completion of delivery order.

3.2.2 Integrated Master Plan (IMP) and Integrated Master Schedule (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 Integrated Master Schedule (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.3 Earned Value Management (EVM) System

The contractor shall use EVM System as each specific delivery order defines.

3.2.3.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 Earned Value Management System (EVMS) in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.234-7001, DFARS 252.234-7002, 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.3.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.2.4 Configuration Management

As specified by individual delivery orders, 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.2.4.1 Engineering Change Proposals (ECP)

As specified by individual delivery orders, 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.

3.2.4.2 Variances

As specified by individual delivery orders, 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.

3.2.5 Risk Management

As specified by individual delivery orders, the contractor shall implement an integrated risk management system with risk planning, identification, assessment, mitigation and monitoring functions to improve technical, cost and schedule performance for each specific delivery order.

3.2.6 Associate Contractor Agreements (ACAs)

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

3.2.7 Meetings and Program Reviews

As specified by individual delivery orders, 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.2.8 Subcontractor Management

As specified by individual delivery orders, the contractor shall maintain the capability to manage subcontractors in accordance with the delivery orders’ 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, EVM system, etc. The contractor shall ensure the requirements of this contract and subsequent delivery orders are applied to all subcontracts and associate contracts.

3.2.9 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.10 Computer Hardware, Enterprise Software Solutions (CHESS) Program

The Army's Computer Hardware, Enterprise Software Solutions (CHESS) program, under Program Executive Office Enterprise Information Systems (PEO EIS), is the mandatory source for commercial Information Technology (IT) purchases for IMILES VTESS. 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 IT 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.2.11 Contracting Invoicing 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 Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor shall report all contractor manpower (including subcontractor manpower) required for performance of this contract. The contractor shall be required to completely fill in all the information in the format using the following web address https://cmra.army.mil. The required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer’s Technical representative; (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor name, address, phone number, e-mail address, identity of contractor employee entering data; (5) Estimated direct labor hours paid this reporting period (including sub-contracts); (6) Estimated direct dollars paid this reporting period (including sub-contractors); (7) Total payments (including sub-contractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different); (9) Estimated data collection cost; (10) Organizational title associated with the Unit Identification Code (UIC) for the Army requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information); (11) Locations where contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website); (12) Presence of deployment or contingency contract language; and (13) Number of contractor and sub-contractor employees deployed in theater this reporting period (by country).

As part of its submission, the contractor shall also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year. The contractor shall use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractor’s systems to the secure web site without the need for separate data entries for each required data element at the web site. The Specific formats for the XML direct transfer may be downloaded from the web site as specified.

3.3 Systems Engineering

The contractor shall provide the requisite technical and programmatic support to https://chess.army.mil/ https://cmra.army.mil/ complete the required tasks of the individual delivery orders associated with the IMILES VTESS engineering and management. These tasks shall encompass the efforts associated with the development, dissemination, engineering, management, and maintenance of the IMILES VTESS architecture, components, and documentation.

These tasks shall also include the works efforts associated with the engineering, management, and tracking of IMILES VTESS fielded Products and core assets.

3.3.1.1 Software Engineering

As specified by each delivery order, the contractor shall provide the requisite technical and programmatic support to complete the required tasks of the individual delivery orders associated with the IMILES VTESS engineering and management. These tasks shall encompass the efforts associated with the development, dissemination, engineering, management, and maintenance of the IMILES VTESS architecture, components, and documentation. These tasks shall also include the works efforts associated with the engineering, management, and tracking of IMILES VTESS fielded Products and core assets.

3.3.2 Hardware Engineering

As specified by each delivery order, the contractor shall integrate and assemble the system hardware that satisfies the performance and Risk Management Framework 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 following design stages, information generated shall be documented in an integrated database.

3.3.3 Test Engineering

As specified by each delivery order, the contractor shall develop, implement, and maintain a system testability process satisfying all testability 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 testability 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 software, and maintenance documentation performed as a means for satisfying production testing, and meeting testability requirements. The contractor shall establish a testability 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.

3.3.4 Hardware and Software Integration.

As specified by each delivery order, the Contractor shall perform all activities to integrate and assemble the hardware and software to achieve a fully functional and accreditable 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.3.5 Technology Insertion

As specified by each delivery order, IMILES VTESS shall provide a path-ahead for migration to and incorporation of future FOF/FOT technological advancements. This includes the establishment of a IMILES VTESS baseline configuration that is adaptable and can be extended to incorporate future technologies. The result is better, more realistic FOF/FOT training capability; reduced life-cycle (LC) support costs; and more realistic simulation for Army tactical vehicles that do not have an embedded fire control system. The contractor shall work with the Government to investigate new technology insertion plans through system analysis and trade studies. The cost of production implementation is over and above the firm fixed price of the contract. Possible candidate new technologies to be considered in the future include the following:

a. Improving laser transmission through environments obscurants.

b. Improving supportability, increase mean time between essential function failures.

c. Reducing the size and weight of the devices.

d. Lighter weight sensor and detector with improved detection fidelity.

e. Reducing number and complexity of physical connections (cables and connectors).

f. Improving the ability to quickly and easily introduce system upgrades.

g. Minimizing test measurement and diagnostics equipment.

h. System component modularity.

i. Pan Position System.

j. MANET System.

k. GPS Position Logger.

l. Direction and Position encoding on Laser Link.

m. Incorporation of Fast Code.

n. 1.55 µm Laser/Detector.

o. Optical Communications Link.

p. Passive helmet.

q. Geometric pairing link.

r. Seamless video/I-MILES play.

s. New laser diode.

t. Future Army fire control systems, vehicle types, weapon systems.

u. Weapon effect’s on vehicle crew within and outside the vehicle.

v. Incorporation of total rounds fired data field, updated with every shot.

w. Other technologies agreed upon via the I-MILES Integrated Project Team

(IPT).

x. VICTORY bus integration.

y. Encoding Azimuth, Deflection and Shooter Position into the MCC while maintaining backwards compatibility.

z. LT2 PAN Crew Kill Modules

aa. Future and Modernization of Current Army and Marine Vehicles (e.g., AMPV, JLTV, LAV25, AAV, ACV).

bb. Multifunction Vehicle Port (MFVP).

cc. LT2 Data Driven Technical Data Package Management.

dd. Common Operating Environment (COE).

3.3.6 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 IMILES VTESS IDIQ contract. The contractor shall ensure all CPM software services and products are designed to minimize safety risks to operators and maintainers in accordance with MIL-

STD-882.

3.4 Specialty Engineering

3.4.1 Reliability Engineering

As specified by individual delivery orders, the contractor shall perform reliability engineering to meet the availability and specific Reliability requirements of each specific delivery order.

3.4.2 Maintainability Engineering

As specified by individual delivery orders, the contractor shall perform a maintainability engineering to meet the availability and specific Maintainability requirements of each specific delivery order.

3.4.3 Safety Engineering

As specified by individual delivery orders, the contractor shall perform Safety Engineering to meet the availability and specific safety requirements of each specific delivery order.

3.4.4 Producibility Engineering

As specified by individual delivery orders, the contractor shall perform Producibility engineering to meet the requirements of each specific delivery order.

3.4.5 Quality Engineering

As specified by individual delivery orders, the contractor shall perform quality engineering to meet the requirements of each specific delivery order.

3.4.6 Supportability Engineering

As specified by individual delivery orders, the contractor shall perform supportability tradeoffs during the systems engineering process by considering the effect design decisions have on life-cycle cost, reliability, maintainability, and availability rates as specified by each specific delivery order.

3.4.7 Human-Systems Integration (HSI)

The contractor shall establish and maintain a formal Human-Systems Integration (HSI) engineering program as each specific delivery order requires.

3.4.8 Value Engineering

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. Each delivery order will address specific requirements.

3.5 Cybersecurity

The Contractor shall develop and maintain a 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 a 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.5.1 Anti-Terrorism Level 1 Training

All contractor employees, to include subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 60 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 30 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://atlevel1.dtic.mil/at.”

All US based contractor employees and associated sub-contractor employees shall receive Government provided area of responsibility (AOR) specific AT awareness training as directed by AR 525-13.

3.5.2 iWATCH Training

The contractor and all associated sub-contractors shall brief all employees of the types of behavior to watch (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. Training shall be completed within 60 calendar days of contract award and with 60 calendar days for new employees commencing performance with the results reported to the COR NLT 120 calendar days after contract award.

3.5.3 Protection Policy & Procedures

The contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DOD, HQDA https://atlevel1.dtic.mil/at and/or local policy. In addition to the changes otherwise authorized by the changed clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in the contractor security matters or processes.

3.5.4 Access to Government Information Systems

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

3.5.5 OPSEC Plan

3.5.6 OPSEC Training

Per AR 530-1, Operations Security, All contractor employees must complete annual Level I OPSEC awareness training. New contractor employees must complete Level I OPSEC training within 30 calendar days of their reporting for duty.

3.5.7 Information Assurance / Information Technology Training

All contractor employees and associated sub-contractor employees must complete the DOD Information Assurance Awareness Training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DOD and Army training requirements in DODD 8570.01, DOD 8570.01-M and AR 25-2 within 6 months of employment.

3.5.8 Spectrum Management

As specified by each delivery order, the Contractor shall ensure compliance with the policies and procedures for the Army Frequency Allocation to Equipment (Army J/F-12) Program as described in AR 5-12, Chapter 4 for any system that operates in an electromagnetic spectrum.

3.6 Logistics

The Contractor shall conduct engineering analyses to establish quantitative and qualitative supportability design guidelines. The Contractor shall conduct trade studies, evaluate design and support alternatives, and establish system supportability preliminary design configurations consistent with system readiness and availability and life cycle cost goals. The contractor shall perform the necessary tasks and activities for logistics, fielding and sustainment. The Government will address the specific requirements in each delivery order. The following table provides a representative list of tasks and activities that could be required by specific delivery orders with respect to Logistics, Support Resources, Publications, Training, Fielding and Sustainment:

Requirements Analysis Publication In Process Reviews

Accounting Requirements Codes Reliability Analyses

Authentication Repair Level Analyses

Baseline Drawing Revisions Repair Procedures

Commercial Off The Shelf Publications SCORM Compliance

Common and Bulk Items Serial Numbers

Course Conduct Information Site Support

Diagnostic Procedures Software Support Environment

Engineering Services Source, Maintenance, and Recovery Codes

Facility Analyses and Summary Spares and Support and Test Equipment

Fielding plans Supply Support

Initial Spares and Repair Parts Lists Support Analyses

Instructional Media Design Support Concepts

Instructional Media Package Supportability Analysis

Instructional Media Requirements Sustainment Transition

Instructional Performance Requirements Technical Publications

Interim Contractor Support Test and Evaluation

Inventory Support Tools and Test Equipment

IUID Marking and Reporting Training and Support

Life Cycle Software Engineering Environment

Training Assessments

Logistics Database Management Training Conducts Support

Logistics Demonstration Training Facility and Equipment

Maintenance Actions Training Products

Maintenance Planning Training Reviews

Manpower, Personnel and Training Training Situation Document

Materiel Component List Training System Support

Parts Management Transition Planning

Pocket Guides Validation

Post Production Support Verification

Provisioning Parts List Warranty Data

3.6.1 Contractor Support

The contractor shall perform the tasks necessary to operate, maintain and support the core assets, products, and fielded systems as each specific order defines. The contractor shall provide all supplies, services and system/configuration management necessary to perform Interim contractor Support (ICS).

3.6.2 Disclosure of Information

The contractor shall comply with the protection standards and guidance described in DoDM 5200.1 to prevent foreign intelligence collection and/or the unauthorized disclosure of information.

3.7 Weapon and Ammunition Storage and Transportation

The contractor shall comply with the requirements of DoD 5100.76-M when handling conventional arms, ammunition and explosives.

4.0 Appendix A - Acronym List

AAR After Action Review

ACA Associate Contractor Agreement

AIS Automated Information System

ATP Acceptance Test Procedure

BAE British Aerospace Engineering

BER Beyond Economical Repair

BPR Beyond Physical Repair

C&A Certification and Accreditation

CAB Corrective Action Board

CAGE Commercial and Government Entity

CAIV Cost as an Independent Variable

CBT Computer Based Training

CDE Controlled Development

CDRL Contract Data Requirement List

CI Configuration Item

CL Confidentiality Level

CLS Contractor Logistics Support

CM Configuration Management

CMMI Capability Maturity Model Integration

CMMI – DEV Capability Maturity Model Integration - Development

CMP Configuration Management Plan

CONUS Continental United States

COTS Commercial-off-the-Shelf

CSCI Computer Software Configuration Item

CVS Combat Vehicle System

DCMA Defense Contracts Management Agency

DOD Department of Defense

DODD Department of Defense Directive

DODI Department of Defense Implementation

DS Depot Support

E3 Electromagnetic Environmental Effects

ECP Engineering Change Proposal

FAI First Article Inspection

FAT First Article Test

FBL Functional Baseline

FOF Force on Force

GAT Government Acceptance Test

GFE Government-Furnished Equipment

IA Information Assurance

IAVA IA Vulnerability Alert

IAW In Accordance With

ICD Interface Control Document

ICS Interim Contractor Support

ICWG Interface Control Working Group

IDD Interface Design Description

IMP Integrated Master Plan

IMS Integrated Master Schedule

IPR In Process Review

IPT Integrated Product Team

IS Instrumentation Systems

LCC Life Cycle Cost

LCCS Life Cycle Contractor Support

LPAN Live Player Area Network

LTEC Live Training Engagement Composition

LMI Logistic Management Information

LRIP Low Rate Initial Production

LRU Lowest Replaceable Unit

LT2 Live Training Transformation

MAC Mission Assurance Category

MANPRINT Manpower and Personnel Integration Program

MCC MILES Communication Code

MCTC Maneuver Combat Training Center

MILES Multiple Integrated Laser Engagement System

MOS Military Occupational Specialty

MRB Material Review Boards

NSN National Stock Number

OCONUS Outside Continental United States

OEM Original Equipment Manufacturer

OUM Operators User Manual

O&M Operation & Maintenance

PDD Product Definition Data

PEO STRI

Program Executive Office for Simulation, Training and Instrumentation

PMR Program Management Review

QA Quality Assurance

QE Quality Engineer

RCS Range Communication System

RDMS Range Data Measurement Subsystem

RMF Risk Management Framework

RTM Requirements Traceability Matrix

SAIV schedule as an independent variable

SAR Safety Assessment Report

SAP Security Authorization Package

SAWE Simulated Area Weapons Effects

SCORM Sharable Content Object Reference Model

SIP System Identification Profile

SIT Systems Integration Test

SOW Statement of Work

SPS Software Product Specification

STE Special Test Equipment

ST&TE Special Tools & Test Equipment

STIG Security Technical Implementation Guide

SVD Software Version Descriptions

SVT Systems Verification Test

TASC Training Area Support Center

T&E Test and Evaluation

TD Test Discrepancies

TESS Tactical Engagement Simulation Systems

TIM Technical Interchange Meetings

TIR Test Incident Reports

TRL Technology Readiness Level

TRR Test Readiness Review

TSV Thru Sight Video

UID Unique Identification

VTESS Vehicle Tactical Engagement Simulation System

WAWF Wide Area Workflow

WFF War Fighter Focus