J.1_M6785413R7802_SITE_LIVE_Core_System_Upgrades_SOW_15_Jan_2013.pdf

Page ii of 50

UNCLASSIFIED/FOR OFFICIAL USE ONLY

M67854-13-R-7802 Attachment J.1

15 Jan 2013

STATEMENT OF WORK

FOR

SQUAD IMMERSIVE TRAINING ENVIRONMENT (SITE)

LIVE-CORE SYSTEM UPGRADES

PROGRAM MANAGEMENT OFFICE, TRAINING SYSTEMS

(PMTRASYS)

12350 RESEARCH PARKWAY

ORLANDO, FL 32826-3275

WARNING--This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or Executive Order 12470. Violation of these export laws is subject to severe criminal penalties.

Table of Contents

Section Title Page 1 Scope

1.1 Background

2 Applicable Documents

2.1 Government Documents

2.1.1 Department of Defense Standard Practices & Handbooks

2.1.2 Other Government Documents

2.1.3 Non-Government Documents

2.2 Order of precedence

3 Requirements

3.1 General

3.2 Technical Requirements

3.2.1 SITE Enhancements Systems Development

3.2.2 Environmental Requirements

3.2.3 ITESS II Baseline Architecture

3.2.4 Assault Squads (Optional Task)

3.2.5 Anti-Armor (Option)

3.2.5.1 M41 TOW with Improved Target Acquisition System (ITAS)

3.2.5.2 Javelin (Option)

3.2.6 MK 19 (Optional Task)

3.2.7 Sniper Marksmanship (Optional Task)

3.2.7.1 M107

3.2.8 Employ Munitions (Optional Task)

3.2.8.1 M18A1 Claymore Directional Anti-Personnel Mine

3.3 Detailed Tasks

3.3.1 Integrated Program Management

3.3.2 Integrated Product Team (IPT)

3.3.3 Contract Management

3.3.3.1 Subcontractor Management

3.4 Conferences and Reviews

3.4.1 Post Award Conference (PAC)

3.4.1.1 PAC Entry Criteria

3.4.1.2 PAC Exit Criteria

3.4.2 System Requirements Review (SRR)_

3.4.2.1 SRR Entry Criteria

3.4.2.2 SRR Exit Criteria

3.4.3 In Progress Review (IPR)

3.4.4 Preliminary Design Review (PDR)

3.4.4.1 PDR Entry Criteria

3.4.4.2 PDR Exit Criteria

15 Jan 2013

3.4.5 Critical Design Review (CDR)

3.4.5.1 CDR Entry Criteria

3.4.5.2 CDR Exit Criteria

3.4.6 Test Readiness Review (TRR) Conference

3.4.6.1 TRR entry criteria

3.4.6.2 TRR Exit Criteria

3.5 Interoperability

3.5.1 System Interface Definition

3.5.2 System/Equipment Interoperability Standardization

3.6 System Testing & Logistics Support

3.7 Operational Utilization

3.8 SITE Hardware and Software Integration

3.9 Spectrum Allocation and Approval

3.9.1 Radio Frequency (RF) Management

3.10 Materials

3.11 Reliability and Maintainability (R&M) Tasks

3.11.1 RAM Predictions

3.12 Environment, Safety, and Occupational Health

3.12.1 System Safety

3.12.2 Safety Assessment

3.12.3 Material Safety Data Sheets

3.12.4 Environment, Safety, and Occupational Health Compliance

Assessment

3.12.5 Hazardous Materials Management Program and Pollution

Prevention

3.12.6 Accidents

3.12.7 Transit Cases

3.12.8 Man-Portable

3.12.9 RF Exposure

3.12.10 Lithium Batteries

3.12.10.1 Lithium Battery Safety Qualification

3.12.10.2 Lithium Battery Safety Assessment

3.12.10.3 Battery Charger Adaptor

3.12.11 Lasers

3.12.11.1 Laser Support

3.12.12 Electrostatic Discharge (ESD) control

3.12.12.1 Electrostatic Discharge (ESD) assemblies

3.12.12.2 Electrostatic Discharge (ESD) equipment

3.12.13 Fluid and Gaseous Lines

3.12.14 Cable and Wire Markings

3.12.15 Safety Markings

3.13 Quality Management System Requirements

3.14 Test and Evaluation (T&E)

15 Jan 2013

3.14.1 Responsibility for Tests

3.14.2 Test Authority

3.14.3 Government Acceptance Test (GAT)

3.14.3.1 GAT Entry Criteria

3.14.3.2 GAT Exit Criteria

3.14.4 GAT Plan

3.14.5 Test Resources and Facilities

3.14.6 Test Methods

3.14.7 Test Criteria

3.14.8 Tolerance Data

3.14.9 Alignment and Calibration

3.14.10 Test Log

3.14.11 Changes During Testing

3.14.12 Changes After Testing

3.14.13 Test Deficiency Reporting System

3.14.14 Form & Fit Testing

3.14.14.1 Training scenarios

3.14.14.2 Stress tests

3.14.14.3 Free play tests

3.14.14.4 Product assurance tests

3.14.14.5 ESD tests

3.14.14.6 Human factors engineering compliance tests

3.14.14.7 Nonfunctional examinations

3.14.15 Training Effectiveness Evaluation Event

3.15 Warranty

3.16 Integrated Logistics Support (ILS) Program

3.17 Deliverables

3.17.1 Integrated Master Schedule

3.17.2 Status Reporting

3.17.3 Conference Presentation Materials and Minutes

3.17.4 Test Plan

3.17.5 Test Procedures

3.17.6 Test Report

3.17.7 Requirements Traceability Matrix (RTM)

3.17.8 System Product Specification

3.17.9 Safety Assessment Report

3.17.10 Battery Safety Data Package

3.17.11 Operations and Maintenance Manuals

3.17.12 Commercial Manuals

3.17.13 Copyright Release

3.17.14 Training Products and Services

3.17.15 Training Conduct Support Document

3.17.16 Change Pages/Modification Instructions

15 Jan 2013

3.17.17 Branding

3.17.18 Technical Data Package

3.17.19 Licensing/Ownership Rights

3.18 Packaging, Handling, Storage, and Transportation (PHS&T)

3.19 Item Unique Identification (IUID) Assignment

3.20 Integrated Product and Process Management (IPPM)

3.21 Risk Management

3.22 Configuration Management (CM)

3.22.1 Configuration Verification and Audit

3.22.2 Configuration Management Planning and Management

3.23 Government Furnished Equipment/Information

Appendix A: Acronym List

15 Jan 2013

1 Scope

This Statement of Work (SOW) defines the contractor’s effort required to support the design, development, integration, ruggedized prototype, testing and effectiveness evaluation of Squad Immersive Training Environment (SITE) specific capability enhancements to the Instrumented - Tactical Engagement Simulation System, Increment II, (I-TESS II) training system. These enhancements were identified as part of the SITE Analysis of Alternatives (AoA) exploratory analysis. These enhancements address current training proficiency and readiness gaps at the squad-level and will be used to support both direct Force-on-Force (FoF) and Force-on-Target (FoT) tactical engagement training.

The SITE-specific capabilities enhancements are as follows:

1. Assault-Squads - Integrated MK153 shoulder launched multipurpose assault weapon (SMAW) simulator capability, paring sensors, day/night sighting, and back blast mechanism (non-pyrotechnic).

2. Anti-Armor – Integrated M41 TOW and M98A1 Javelin simulator capabilities and paring sensors.

3. Machine Guns - Integrated MK 19 Instrumented Weapon System (IWS) simulator, Small Arms Transmitter (SAT) and paring sensors.

4. Sniper Marksmanship – Evaluation of the effectiveness of an Integrated M107 long range sniper rifle (LRSR) paring sensors and the FoF use of existing Fire Control Devices while minimizing laser safety issues.

5. Employ Munitions – Integrated M18A1 Claymore mine with integrated battlefield effects capabilities.

1.1 Background

CTIA is the foundational architecture for the Live Training Transformation Family of Training Systems (LT2-FTS) strategy. CTIA consists of standard architecture services, components and protocols, and it facilitates commonality across the various training instrumentation systems and interoperability across Live, Virtual and Constructive (LVC) and joint training environments.

I-TESS II man-worn detection system (MDS) and range equipment is used to instrument the individual Marines during direct force-on-force and force on target engagements.

The I-TESS II system will be used in military operations on urban terrain (MOUT) facilities and Non-Live Fire Maneuver Ranges located at various Marine Corp bases and installations. These facilities and ranges provide the setting for the USMC Pre-deployment Training Program (PTP) and other individual and unit-level training support. The Marine Corps has expressed a need to acquire and deliver training systems that provide real-time situation awareness, exercise control capabilities, and adjudicate indirect fire engagements so as to help facilitate the training exercise objectives. There is a need to collect the training actions/interactions of the Marines during the

15 Jan 2013 training exercise with the ability to provide immediate access of collected data for after action report (AAR) purposes.

2 Applicable Documents

The following documents form a part of this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of this SOW take first precedence. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

2.1 Government Documents

ITESS II Performance Specification M67854-10-R-

- 13Feb12

PMT 90-S002K MILES

Communications Code Standard, 01 Aug 2007

- Multiple Integrated Laser Engagement System (MILES) Communication Code (MCC)

STANDARD

MCO 5104.1C - Navy Laser Hazards Control Program

NAVSEAINST 9310.1B - Navy Lithium Battery Safety Program

LT2-2006-0001 - Common Training Instrumentation Architecture (CTIA) Compliance Definition Document

LT2, 25 March 2009 - Live Training Transformation (LT2) Component Agreement Template

V1.02.0, Version 3.0, 04 Jan 10 - PU Gateway Developers Guide For Interfacing with LT2 Common PU Controller

ANSI Z136.1-2007 - American National Standard for the Safe Use of Lasers

2.1.1 Department of Defense Standard Practices & Handbooks

MIL-STD-1472F

MIL-STD-882

Department of Defense Design Criteria, Human Engineering

System Safety Program Requirements/Standard Practice for System Safety

MIL-PRF-29612 - Training Data Products

MIL-PRF-32216 - Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data

15 Jan 2013

MIL-PRF-49506 - Logistics Management Information

MIL-STD-129 - Military Marking for Shipment and Storage

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

MIL-STD-2073-1 - DoD Standard Practice for Military Packaging

MIL-HDBK-217F - Reliability Prediction of Electronic Equipment

MIL-HDBK-472 - Maintainability Prediction

MIL-HDBK-61 - Configuration Management Guidance

MIL-HDBK-29612-2A - Instructional Systems Development/Systems

DI-HFAC-81743

MIL-STD-3100

MIL-STD-810

Human Systems Integration Program Plan

Technical Data Packages

Environmental Engineering Considerations and Laboratory Tests

2.1.2 Other Government Documents

FED-STD-313 - Material Safety Data, Transportation Data and Disposal Data for Hazardous Materials Furnished to Government Activities

FIPS PUB 140-2, 25 May 11 - Security Requirements for Cryptographic Modules

DODI 8500.2, 6 Feb 2003 - Information Assurance (IA) Implementation

DODI 8510.01. 28 Nov 2007 - DoD Information Assurance Certification and Accreditation Process (DIACAP) Implementation

2.1.3 Non-Government Documents

ANSI/ASQC-Q9000: 2000 - Quality Management Systems - Fundamentals and Vocabulary

ANSI/ASQC-Q9001: 2000 - Quality Management Systems - Requirements

ANSI/ASQC-Q9004: 2000 - Quality Management Systems - Guidelines for Performance Improvements

ASTM D3951 - Standard Practice for Commercial Packaging

EIA-649 - National Consensus Standard for Configuration Management

15 Jan 2013

Note: If document version listed is not the most current, then substitute with the latest version available at time of contract award.

NOTE: Copies of the above DoD specifications and handbooks can be obtained online from the DoD Single Stock Point or from the Acquisition Streamlining and Standardization Information System (ASSIST) Web Site. Electronic copies can be downloaded from the ASSIST Web Site located at: http://assist.daps.dla.mil/quicksearch/Training System Support Documentation.

2.2 Order of precedence

In the event of a conflict between the text of this SOW and the references cited herein, the text of this SOW takes precedence. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

3 Requirements

3.1 General

The contractor shall provide all Program Management, Engineering, Testing, Logistics tasks as designated in this SOW. The contract shall conform to the system upgrades to the Instrumented- Multiple Integrated Laser Engagement System (I-MILES) specification and ensure compliance with the Common Training Instrumentation Architecture (CTIA). SITE sets the conditions in which squad leaders and members act based on standardized tactics, techniques and procedures and adapt correctly to changes in their mission. SITE shall maximize the use of Non- Developmental Item products and Commercial Off -the-Shelf (COTS) (See DoD 5000.2R and FAR 2.101 for detailed definitions of "commercial" and NDI items), computer equipment, while utilizing open architecture to the maximum extent possible.

3.2 Technical Requirements

3.2.1 SITE Enhancements Systems Development

The contractor shall support the technical development, integration, maintenance, training, and logistics for the SITE-specific enhancements listed within this document. All electronic components shall have a built-in (pass/fail) testing mechanism that can be operated manually, remotely and at the beginning of each power-on cycle.

3.2.2 Environmental Requirements

The contractor shall conduct the following environmental tests on the system components:

All SITE components shall:

a. Operate in all temperatures from -20 to 120 degrees Fahrenheit,

b. Store in all temperatures from -20 to 160 degrees Fahrenheit, and

15 Jan 2013

c. Operate and store in relative humidity from 10 to 98 percent, non-condensing, without degradation in performance.

3.2.3 ITESS II Baseline Architecture

All components and equipment developed as part of this contract shall interface and work as defined in the standards for communication to the CTIA common player gateway.

3.2.4 Assault Squads (Optional Task)

The contractor shall provide a SMAW simulator. The capability shall include physical components consisting of a SMAW launcher and firing tube, day sights, night sights, surrogate rounds to replicate High Explosive dual purpose round, anti tank round, and novel explosive rounds, and SATs representing the forward firing and back blast of the equipment. The SMAW shall communicate to the RISCON.

The integrated SMAW capability shall incorporate the following characteristics:

The SMAW back blast shall replicate a 30m lethality back-blast with a 60 degree cone.

The SMAW shall model the form factor and capabilities of the actual device.

The SMAW shall display non-pyrotechnic visual cues when fired.

The SMAW shall emit audio cues when fired.

The SMAW shall include a launcher tube with control electronics. The Control Electronics shall integrate round detection sensors. The control electronics shall integrate GEO-paring sensors.

The SMAW shall simulate lethal back-blast effects of the weapon on personnel. The back blast shall have a 60 degree cone 30 meter lethality area.

The SMAW shall include the weapons tactical “iron” sights.

The SMAW simulator shall provide physical interface for an operational tactical night vision sight. The user shall be able to utilize operational tactical night vision sight on the equipment.

The SMAW simulator shall provide physical interface for an optical day sight. The user shall be able to utilize operational optical day sight on the equipment.

The SMAW shall simulate a High explosive dual purpose round

The SMAW shall simulate anti tank round.

The SMAW shall simulate a novel explosive round.

The SMAW shall include an internal power source (i.e not facility power).

The SMAW shall include a MIL-STD-1472F compliant transit case.

15 Jan 2013

3.2.5 Anti-Armor (Option)

3.2.5.1 M41 TOW with Improved Target Acquisition System (ITAS)

The contractor shall provide a M41 TOW with Improved Target Acquisition System simulator.

The capability shall include physical components at least consisting of a M41 TOW launcher and firing tube, day sights, night sights, surrogate rounds to replicate High Explosive dual purpose round, anti tank round, and novel explosive rounds, and SATs representing the forward firing and back blast of the equipment. The M41 TOW shall communicate to the RISCON.

The M41 TOW/ITAS shall model the form factor and capabilities of the actual device.

The M41 TOW/ITAS shall display non-pyrotechnic visual cues when fired.

The M41 TOW/ITAS shall emit audio cues when fired.

The M41 TOW/ITAS shall include a launcher tube with control electronics. The Control Electronics shall integrate round detection sensors. The control electronics shall integrate GEO-paring sensors. The control electronics shall include semi automated command line of sight guidance.

The M41 TOW/ITAS shall simulate lethal back-blast effects of the weapon on personnel. The back-blast shall have a 90 degree cone 50 meter lethality area.

The M41 TOW/ITAS shall simulate a BGM 71H

The M41 TOW/ITAS shall simulate BGM 71F

The M41 TOW/ITAS shall include an internal power source (i.e not facility power).

The M41 TOW/ITAS shall include a MIL-STD-1472F compliant transit case.

3.2.5.2 Javelin (Option)

The contractor shall provide a Javelin System simulator. The capability shall include physical components consisting of a Javelin Command launch unit and launch tube assembly, day sights, night sights, surrogate rounds, and SATs representing the forward firing and back blast of the equipment.

The Javelin shall model the form factor and capabilities of the actual device to include top attach mode and direct attack mode.

The Javelin shall display non-pyrotechnic visual cues when fired.

The Javelin shall emit audio cues when fired.

The Javelin shall include a launcher tube with control electronics. The Control Electronics shall integrate round detection sensors. The control electronics shall integrate GEO-paring sensors.

The Javelin shall simulate the thermal imagining viewer.

The Javelin shall simulate lethal back-blast effects of the weapon on personnel. The back blast shall have a 60 degree cone 25 meter lethality area.

15 Jan 2013

The Javelin shall include an internal power source (i.e not facility power).

The Javelin shall include a MIL-STD-1472F compliant transit case.

3.2.6 MK 19 (Optional Task)

The contractor shall provide a MK 19 40mm grenade launcher weapon system. The capability shall include physical components to replicate the look and capability of a MK 19 weapon. The MK19 shall communicate to the RISCON.

The SITE MK19 Simulator shall model the form factor and capabilities of the actual device.

The SITE MK19 Simulator shall include an internal power source (i.e., not facility power or external battery unit).

The SITE MK19 Simulator shall simulate firing.

The SITE MK19 Simulator shall emit audio cues when fired.

The SITE MK19 Simulator shall recoil when fired.

The SITE MK19 Simulator laser transmitter shall align to the weapon's sights.

The SITE MK19 Simulator shall include a tripod for ground mounting of the system.

The MK19 shall include Amphibious Assault Vehicle (AAV) mounting bracket and associated hardware.

The SITE MK19 Simulator shall include a MIL-STD-1472F compliant Transit Case.

The MK19 shall include ammunition characteristics of a 40mm Grenade.

The MK19 shall include a visual cueing device to identify impact and to support adjust fires.

3.2.7 Sniper Marksmanship (Optional Task)

3.2.7.1 M107

The Government will provide a M107 SAT to mount on a M107 sniper rifle. The contractor shall provide a mounting bracket that does not interfere with normal weapons operation or add on equipment. The bracket shall not excessively increase the weight of the weapon overall.

15 Jan 2013

3.2.8 Employ Munitions (Optional Task)

3.2.8.1 M18A1 Claymore Directional Anti-Personnel Mine

The contractor shall provide a M18A1 claymore directional anti-personnel mine. The capability shall include physical components at least consisting of a representative claymore device and associated radio hardware. The claymore shall communicate to the RISCON using appropriate MILES codes. The claymore shall provide local adjudication of kill effects.

The SITE Claymore Mine Simulator shall model the form factor and capability of the actual device.

The SITE Claymore Mine Simulator shall model the mine's effective blast area.

The SITE Claymore Mine Simulator shall emit audio cues when detonated.

The SITE Claymore Mine Simulator shall display non-pyrotechnic visual cues when detonated.

The SITE Claymore Mine Simulator shall include a MIL-STD-1472F compliant Transit Case.

The SITE Claymore Mine Simulator shall include an internal power source (i.e., not facility power or external battery unit).

3.3 Detailed Tasks

3.3.1 Integrated Program Management

The contractor shall organize, coordinate, and control all program activities to ensure compliance with the contract requirements and the delivery schedule of required products and services. The contractor shall monitor the progress of all the work performed and costs incurred under the contract.

The contractor shall provide program management, systems engineering, design engineering, materials, services, equipment, facilities, testing, technical, logistics, manufacturing, and clerical support for the efforts described within this SOW IAW CDRLs.

The contractor shall capture these SITE enhancements’ system, product and subsystem interface requirements to establish a system baseline. The contractor shall generate documentation in direct support of this effort and shall coordinated with the SITE working integrated product team (WIPT) during system definition, development and integration and shall be used to guide subsystem development and data/information flow.

15 Jan 2013

3.3.2 Integrated Product Team (IPT)

The contractor shall participate as an Integrated Product Team member for all contract efforts.

The contractor shall participate in joint IPT meetings.

3.3.3 Contract Management

The contractor shall perform all tasks necessary to ensure the requirements of this SOW and subsequent modifications meet cost, schedule and performance requirements.

3.3.3.1 Subcontractor Management

The contractor shall integrate subcontractor efforts into program management and tracking systems such as the Integrated Master Schedule (IMS)/ Integrated Master Plan (IMP). The contractor shall ensure the requirements of this SOW and subsequent modifications are consistently applied to all subcontracts and associated contracts. The contractor shall institute procedures to ensure that subcontractors and vendors have incorporated necessary program elements to ensure compatibility of supplied equipment or services.

3.4 Conferences and Reviews

The contractor shall conduct, attend, and participate in conferences and reviews to be held at both the contractor and Government facilities. The specific locations dates and duration of the conferences shall be as specified in the contract schedule or as mutually agreed upon.

Conferences and reviews will be co-chaired by a Government and contractor representative.

The contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The contractor shall prepare documentation as required, to aid in the presentations. The contractor shall have key personnel and support available to carry out the conference. The contractor shall make available facilities for Government only meetings during all conferences and reviews at the contractor’s facility. Subcontractors shall attend conferences and reviews when required to address key elements.

The contractor shall prepare the Conference Agenda, Conference Minutes, and Presentation Material for all conferences and reviews. Except where noted herein, conferences and reviews shall be considered fulfilled when all of the following items are completed:

• A formal meeting has been conducted and the conference and reviews are presented to the Government

• All topics required for discussion and presentation have been covered

• All action items requiring contractor response have been resolved

• The Government has accepted the conference minutes

15 Jan 2013

3.4.1 Post Award Conference (PAC)

The first conference shall be the PAC and shall occur within 30 days after contract award. The purpose of the conference shall be to establish the framework of the contractor and Government interaction during the performance period of the contract. This meeting shall include the presentation and discussion of information and data relating to:

• Introductions and Contract Overview

• Action item reporting

• Updated team contact list (names, phone numbers, and email address)

• Discussion and clarification of Specification and SOW requirements

• Identification of all critical paths within the IMS

• CDRL delivery schedule

• Integrated Logistic Support

• Training Program Overview

• Technical Manual Overview

• Systems Engineering (SE) Overview

• Program Specific Configuration Management (CM) Overview (to include Data Management)

• Program Specific Risk Management (RM)

• Long lead time item identification and status

• Metrics collection process, analysis, and reporting

3.4.1.1 PAC Entry Criteria

Entry criteria for the PAC shall consist of:

• Contract award has occurred

• Government concurrence that the contractor-submitted PAC agenda is complete and acceptable.

3.4.1.2 PAC Exit Criteria

Exit criteria for the PAC shall consist of:

• Government concurrence that all required PAC topics have been satisfactorily presented, discussed, and documented

• Government concurrence that the IMS and detailed schedule are complete, accurate, and realistic

• Submittal and acceptance of the PAC minutes and presentation materials

15 Jan 2013

• All action items have been assigned with suspense date for closure

3.4.2 System Requirements Review (SRR)_

The contractor shall conduct a SRR as a part of the PAC. The purpose of the SRR shall be to ensure that the SITE requirements have been completely and properly identified and that there is a mutual understanding between the Government and contractor. The contractor shall identify and rank all program risks. The contractor shall present solutions and methods for risk reduction and control for all identified program risks. The SRR shall address at a minimum:

• Completed Requirements Traceability Matrix

• Updated IMS

• Identification of all critical paths within the IMS

• Definition of requirements derived from SOW requirements

• Complete system requirements (including derived requirements) and their functional allocation

• Complete allocation of all system requirements to their functional allocation (e.g.

hardware, software, documentation, process, security, quality, and so forth)

• System and sub-system external (hardware and software) interface requirements

• Software functional requirements

• Software external interface requirements

• System test requirements and strategy

• Human systems/ergonomics considerations

• Draft test and integration plans/process

• Requirements traceability

• DoD Item Unique Identification (IUID) requirements

• Data management and CDRL status

• Metrics collection and reporting analysis

• Logistics support status

• Hazard considerations

• Software Support Environment

3.4.2.1 SRR Entry Criteria

Entry criteria for the SRR shall consist of:

• Delivery and acceptance (as applicable) of all the CDRL items scheduled to be delivered prior to SRR.

15 Jan 2013

• Government concurrence that the contractor submitted SRR agenda is complete and acceptable.

• SRR presentation material has been submitted to the Government in advance of the SRR.

Government preliminary review indicates the presentation material is sufficient to support the SRR.

• SRR technical products listed below for both hardware and software system elements have been made available to the cognizant SRR participants prior to the review:

a. System software functionality description

b. Preferred system solution definition

c. Risk assessment

d. ICD

e. Updated Human Systems Integration related documentation

f. System architecture (hardware, software, human, material as necessary)

a. All applicable CDRLs are accepted

3.4.2.2 SRR Exit Criteria

Exit criteria for the SRR shall consist of:

• Government concurrence that all required SRR topics have been satisfactorily presented, discussed, and documented

• Government concurrence that the system requirements baseline is well supported by thorough analysis, test, and other technical data

• Government concurrence that the IMS and detailed schedule are complete, accurate, and realistic

• Government concurrence that all program risks are known and manageable for production and testing

• Submittal and acceptance of the SRR minutes and presentation materials

• All action items have been assigned with suspense date for closure

• Concurrence that the system requirements sufficiently detailed and understood to enable system functional definition and functional decomposition

3.4.3 In Progress Review (IPR)

The contractor shall conduct an IPR on at least a quarterly basis if no technical review has been completed during this time period. The purpose of the IPR shall be to measure contractor progress and to determine that task requirements have been properly completed or progress goals have been achieved. The Contractor shall present task progress for the previous quarter. The Contractor shall update the IMS. The contractor and the Government will mutually determine the

15 Jan 2013 expected task progress for the following quarter. Initial task progress goals will be set at the

PAC.

3.4.4 Preliminary Design Review (PDR)

The contractor shall conduct a PDR to ensure that the SITE upgrades can proceed into detailed design. The PDR shall be conducted after SRR and prior to the CDR. The contractor shall conduct additional PDR’s as options are exercised. The PDR shall address at a minimum:

a. Outstanding issues from SRR

b. Review IMS and progress to date

c. Draft documents for CDR

d. Open action item status

e. Data management and CDRL status

3.4.4.1 PDR Entry Criteria

Entry criteria for the PDR shall consist of

• Government concurrence that all SRR exit criteria have been satisfied and all SRR

Critical RFAs have been closed

• Government concurrence that the contractor submitted PDR agenda has been coordinated 15 days prior to the PDR

• Delivery and acceptance of all the CDRL items scheduled to be delivered prior to

PDR.

• PDR technical products (hardware and software elements of the product baseline to be reviewed and approved at the PDR) delivered.

• PDR programmatic products have been updated and have been made available prior to the review or will be reviewed at the PDR.

• Program risk assessment

• Systems Engineering Plan changes

• Updated program schedule

• All applicable CDRLs are accepted

3.4.4.2 PDR Exit Criteria

Exit criteria for the PDR shall consist of

a. Government concurrence that all required PDR topics have been satisfactorily presented, discussed, and documented.

b. Government concurrence that the IMS and detailed schedule are complete, accurate, and realistic.

c. Submittal and acceptance of the PDR minutes and presentation materials.

d. All action items have been assigned with suspense date for closure.

e. Government concurrence that the preliminary design, as disclosed, satisfies all of the performance specification requirements.

f. Critical safety items and critical application items identified.

g. Government concurrence that adequate processes and metrics are in place for the program to succeed.

15 Jan 2013

h. Government concurrence that the program is properly staffed.

i. Government concurrence that risks are known and manageable.

j. Key product characteristics having the most impact on system performance, assembly, cost, reliability, or safety been identified

3.4.5 Critical Design Review (CDR)

The contractor shall conduct a CDR to ensure that the SITE systems can proceed into system fabrication, demonstration, and test. The contractor shall conduct additional CDR’s as options are exercised. The CDR shall be conducted after PDR and prior to the TRR. The CDR shall address at a minimum:

• Outstanding issues from PDR

• Review IMS and progress to date

• Draft documents for Test Readiness Review (TRR)

• Open action item status

• SITE components final design as captured in contractor performance specification

• Logistics status

• Demonstrate SITE capabilities that meet the performance requirements

• Identify all of the program risks (technical & cost) and associated impacts to the program schedule.

3.4.5.1 CDR Entry Criteria

Entry criteria for the CDR shall consist of

• Government concurrence that all PDR exit criteria have been satisfied and all PDR Critical Request for Action (RFAs) have been closed

• Delivery and acceptance of all the Contract Data Requirements List (CDRL) items scheduled to be delivered prior to CDR.

• CDR technical products (hardware and software elements of the product baseline to be reviewed and approved at the CDR) have been made available to the cognizant CDR participants prior to the review:

a. Product specifications for each hardware and software configuration item, along with supporting trade-off analyses and data

b. System Design Description complete and ready to be placed under configuration management

c. Preliminary test procedures for software integration and systems testing

d. Human Systems Integration related documentation has been updated

15 Jan 2013

e. Interface Control Document(s) (ICD) are complete and ready to be placed under configuration management

CDR programmatic products have been updated and have been made available prior to the review or will be reviewed at the CDR.

a. Program risk assessment

b. Systems Engineering Plan changes

c. Updated logistics documentation

d. Updated program schedule

e. All applicable CDRLs are accepted

f. Approved Integrated Logistics Support (ILS) Plan

3.4.5.2 CDR Exit Criteria

Exit criteria for the CDR shall consist of:

• Government concurrence that all required CDR topics have been satisfactorily presented, discussed, and documented

• Government concurrence that the IMS and detailed schedule are complete, accurate, and realistic

• Submittal and acceptance of the CDR minutes and presentation materials

• All action items have been assigned with suspense date for closure

• Government concurrence that the detailed design, as disclosed, satisfy all of the SITE performance specification requirements

• Critical safety items and critical application items identified

• Government concurrence that adequate processes and metrics in place for the SITE program to succeed

• Government concurrence that the SITE program is properly staffed

• Government concurrence that the SITE program can be executed with acceptable technical & cost risk.

• Government concurrence that the SITE risks are known and manageable for Developmental Testing (DT)

3.4.6 Test Readiness Review (TRR) Conference

The purpose of the TRR is to determine the SITE readiness for Government testing. The TRR shall be conducted prior to the Government Acceptance Test (GAT). The contractor shall provide the resources, including facilities, equipment, and personnel to support the TRR. The TRR shall include a review of the Test and Evaluation (T&E) program. The TRR shall cover the type of tests to be performed, including internal testing performed by the contractor to ensure the

15 Jan 2013 operation performance of the SITE components. The contractor shall present a requirement traceability matrix, in contractor’s format, to verify that all requirements have been tested. The TRR shall be repeated as necessary until the SITE has been determined by the Government to be acceptable for commencement of the GAT. During the TRR, the following shall be reviewed and discussed:

• Test plan

• Test procedures

• Updated RTM

• Contractor test log, deficiency reporting system

• Test discrepancy reporting process and applicable test discrepancy report form to be used during GAT.

• Identification of software test tools to be used

• Summary of software problems status

• Safety Assessment Report

• Status update of New Equipment Training

• Software Support Environment

3.4.6.1 TRR entry criteria

Entry criteria for the TRR shall consist of:

• Government concurrence that the CDR exit criteria have been met

• Delivery and acceptance (as applicable) of all the CDRL items scheduled to be delivered prior to TRR

• Government concurrence that the contractor submitted TRR agenda is complete and acceptable

• All action items requiring contractor response have been disposition to the satisfaction of the Government

• TRR presentation material has been submitted to the Government in advance of the TRR.

Government preliminary review indicates the presentation material is sufficient to support the TRR

• Configuration of system under test, including software, has been defined and agreed to.

All interfaces have been placed under configuration management or have been defined in accordance with an agreed to plan and a Software Version Description Document has been made available to TRR participants (minimum of 7 working days prior to review)

• All applicable functional, unit level, subsystem, system, and qualification testing has been conducted successfully

15 Jan 2013

• All TRR specific materials such as test plans, test cases, and procedures have been available to all participants prior to conducting the review

• All known system discrepancies have been identified and disposition in accordance with an agreed to plan

• All previous design review exit criteria and key issues have been satisfied in accordance with an agreed to plan

• Test requirements have been documented and are fully traceable to system, engineering, operational or program requirements

• All required test resources (people, facilities, test articles, test instrumentation) have been identified and are available to support required tests

• Roles and responsibilities of all test participants are defined and agreed to

• All applicable CDRLs are accepted

3.4.6.2 TRR Exit Criteria

Exit criteria for the TRR shall consist of

• Government concurrence that all required TRR topics have been satisfactorily presented, discussed, and documented

• Government concurrence that all program risks are known and manageable for testing.

Risk level identified and accepted by Program/Competency leadership as required

• Submittal and acceptance of the TRR minutes and presentation materials

• All action items have been assigned with suspense date for closure

• The identified program and technical risks are accepted by the Government

• Test requirements are traceable, documented and approved. Adequate test plans based on these traceable requirements are completed and approved for the system under test

• Software and hardware test descriptions and procedures are defined, verified and baselined

• Planned testing is consistent with defined incremental approach including regression testing

• All test facilities and resources (including testers, (lab test stations, hardware, and software) are ready and available to support software and hardware testing within the defined schedule

• The software and hardware being tested and the entire test environment is configuration controlled as applicable

• All lower level software and hardware testing has been successfully completed and documented

• Software and hardware metrics show readiness for testing

15 Jan 2013

• Software and hardware problem report system is defined and implemented

• Software and hardware test baseline is established and controlled

• Software and hardware development estimates are updated

• Requirements that cannot be adequately tested at the CSCI and HWCI level (and thus require testing at the subsystem or system levels) are identified

• Testers have a high degree of confidence that the system under test will pass the testing successfully and agree that the anomalies, limitations, and vulnerabilities will not impact this

• The developers are aware of the testers’ plans and have a high degree of confidence that the system under test will pass the testing successfully

3.5 Interoperability

3.5.1 System Interface Definition

The contractor shall document and deliver all software and hardware interfaces in an Interface Control Document (ICD) IAW CDRL A001 (DI-CMAN-81248A). The ICD shall define all interfaces internal and external to the SITE upgrades. The contractor shall define every interface, by medium and by function, including input and output control codes, data format, polarity, range, units, bit weighing, frequency, legal and illegal values, accuracy, resolution, and significance, and testing required validating the interface design. The ICD shall include messages to support association of already developed and fielded MILES & I-TESS Increment II systems. ICD validation shall be included within verification & validation test procedures.

3.5.2 System/Equipment Interoperability Standardization

The contractor shall minimize equipment and parts proliferation through a standardization effort.

This standardization effort shall include coordination with the SITE WIPT to maximize use of parts already in the inventory or to determine that the existing logistics support resources can support life-cycle maintenance of these enhancements. The contractor shall influence the system design for these SITE-specific enhancements to achieve maximum interoperability with the I- TESS II training system including all related subsystems, components and infrastructure, and full compliance with the CTIA framework.

3.6 System Testing & Logistics Support

At the conclusion of system functional testing and in coordination with the SITE WIPT, the contractor shall support the deployment and user testing of these SITE-specific enhancements by capturing all necessary procedures for supporting system integration testing. The contractor shall outline the schedule, scope, processes, interface requirements, test data and resources necessary to complete a limited production, in-field user test of each SITE enhancement.

The contractor shall establish and maintain a Parts Management Program in accordance with (IAW) C001 (MIL-STD-3018), that will ensure the use of parts that meet the contractual

15 Jan 2013 requirements in the performance specification, reduce proliferation of parts through standardization and enhance equipment reliability and supportability, and manage the loss or impending loss of manufacturers or suppliers for the spare and repairable items covered under the SITE. The contractor’s obsolescence management shall prevent impact to contract performance metrics and shall prevent additional costs being incurred by the Government due to obsolescence.

3.7 Operational Utilization

The contractor shall ensure that these SITE-specific enhancements employ only non-lethal, non-pyrotechnic charging or ignition capabilities (i.e. electronic fuses). These SITE-specific enhancements shall operate in all of forms of open terrain currently found within USMC training environments including urban, desert, mountain, and riverine.

3.8 SITE Hardware and Software Integration

The contractor shall perform all activities to develop, assemble, integrate, and test these limited production SITE enhancements (hardware and software) to achieve a fully functional system, with all support systems performing and operating in accordance with this SOW, DoD Certification & Accreditation (C&A) directives or regulations, and all applicable contractor generated specifications. The contractor shall verify the complete integration of the hardware and software upgrades and the overall system through the utilization of formalized test procedures. The contractor shall ensure compliance with the SITE Test & Evaluation Strategy document and that they address conceptual, functional, component and system-level test requirements.

3.9 Spectrum Allocation and Approval

The contractor shall submit a completed DD 1494 and Equipment Location Certification Identification Database (EL-CID) for J/F 12 spectrum allocation documentation to PMTRASYS for further submission to the MARCORSYSCOM Spectrum Office for all Radio Frequencies (RF), and associated equipment operating within Continental United States (CONUS) and Outside Continental United States (OCONUS) Marine Corps bases.

If the proposed COTS/NDI I-TESS II RF Communication System is not approved by individual base Spectrum Management, then the contractor shall reconfigure the RF Communication System to operate on approved frequencies provided by PMTRASYS for that facility.

3.9.1 Radio Frequency (RF) Management

These SITE-specific enhancements shall operate within frequency bands approved by the USMC Base Spectrum Management, Land Mobile Service as defined and allocated by the National Telecommunications and Information Administration (NTIA) for DOD training systems as follows:

• 138.0-144.0 MHz

• 162.0125-173.2 MHz

15 Jan 2013

• 173.4-174.0 MHz

• 225.0-235.0 MHz

• 235.0-243.855 MHz

• 269.95-292.85 MHz

• 317.325-322.0 MHz

• 335.4-380.0 MHz

• Local PAN network currently operates on 2.4-2.4835 GHz

3.10 Materials

All SITE Materials shall be noncombustible or fire retardant in the most hazardous conditions of atmosphere, pressure, and temperature to be expected in their application. Non-permanent fire retardant additives shall not be used to achieve fire retardant.

All SITE equipment shall be fabricated using fungus-inert materials. Non-permanent fungus preventative shall not be used to achieve fungus-inert capability.

All SITE equipment shall not expose personnel or the environment to excessive levels of toxic, carcinogenic, teratogenic, and otherwise hazardous materials as defined by OSHA, 49 CFR Section 100-185 Hazardous Material Regulations (HMR) & Toxic Substance Control Act (TSCA) of 1976 monitored the Environmental Protection Agency (EPA). If hazardous materials must be used in order to meet the performance requirements of this specification, then the hazardous items shall be suitably marked, and all due precautions shall be taken to prevent whatever harm the hazardous material may cause.

Metals shall be corrosion-resistant.

Exposure to environmental conditions shall not cause deterioration of metal parts.

Radioactive materials shall not be utilized.

3.11 Reliability and Maintainability (R&M) Tasks

The contractor shall establish and maintain proactive and effective R&M programs that meet program objectives. The R&M programs shall ensure that the training system equipment, including Commercial Items and Non-Developmental Items meet the R&M requirements.

The Mean-Time-Between-Failures (MTBF) for all SITE equipment shall be 911 hours (threshold) and 1871 hours (objective).

15 Jan 2013

All SITE equipment shall have a Mean-Time-To-Repair (MTTR) of 120 minutes (threshold) and 30 minutes (objective)

The contractor shall include the R&M programs as topics of discussion during the scheduled program reviews.

3.11.1 RAM Predictions

The contractor shall develop a reliability test report that contain the results of each test or other action taken to demonstrate R&M predictions for the SITE equipment and examine the probability, early in the program, that the RAM requirements will be met within the proposed design parameters. MIL-HDBK-217F may be used as guidance for reliability prediction methods and MIL-HDBK-472 may be used as guidance for the maintainability prediction methods. Manufacturer’s data, documented engineering analysis, verifiable field data, MIL- HDBK-217F, and MIL-HDBK-472 may be used as sources of failure rate, Mean-Time-Between- Failures (MTBF), and Mean-Time-To-Repair (MTTR) data. The contractor shall update the RAM predictions throughout the duration of the contract and shall present the prediction results at the scheduled program design reviews IAW CDRL C002 (DI-TMSS-81586A).

3.12 Environment, Safety, and Occupational Health.

3.12.1 System Safety.

The contractor shall identify and evaluate environmental, safety, and health hazards, define risk levels, and establish a program that manages the probability and severity of all hazards associated with development, use, and disposal of the system in accordance with MIL-STD-882E Tasks 205, 206, 207, 210. Residual risks will be evaluated by the Government in accordance with MIL-STD-882E and accepted as appropriate prior to exposing people, equipment, or the environment to known system related Environment, Safety, and Occupational Health (ESOH) risks. The contractor must identify all explosive safety risks as such in the system safety documentation.

3.12.2 Safety Assessment.

The contractor shall document Safety Assessments of MIL-STD-882E Tasks 205, 206, 207, and 210 in a Safety Assessment Report (SAR) according to MIL-STD-882E Task 301. The SAR shall identify all safety features of the hardware, software, and system design and to identify procedural, hardware and software related hazards that may be present in the system including specific procedural controls and precautions that should be followed. Safety assessment shall include Demilitarization and Disposal considerations. In addition, the contractor shall make recommendations applicable to hazards at the interface of the SITE system with other systems.

The SAR shall include a signed statement that all identified hazards have been eliminated or their associated risks controlled to acceptable levels and that the range training systems are ready to field.

DI-SAFT-80102B, Safety Assessment Report (SAR), CDRL A002

15 Jan 2013

3.12.3 Material Safety Data Sheets.

The contractor shall make available Material Safety Data Sheets (MSDS) to the Government for review. MSDS’s shall be included in Safety Assessment Report.

3.12.4 Environment, Safety, and Occupational Health Compliance Assessment.

The contractor shall provide the Government with an assessment of applicable Environment, Safety and Occupational Health (ESOH) laws and regulations, identifying any potential compliance issues. ESOH compliance issues shall be identified in Safety Assessment Report.

3.12.5 Hazardous Materials Management Program and Pollution Prevention.

The contractor shall implement a Hazardous Materials Management Program (HMMP) and Pollution Prevention (P2) in accordance with NAS 411. The contractor shall avoid the use of toxic chemicals, hazardous materials, and ozone depleting substances (ODS) in the design, operational support and disposal of the BT where possible. The HMMP shall establish a process to manage all requirements for asbestos, radioactive materials, cadmium, hexavalent chromium, and extremely toxic or hazardous materials in design, production, operation, and support. In some case, the only acceptable management process may be total elimination of the requirement.

The use of Class I or Class II Ozone Depleting Chemicals (ODCs) is prohibited in the design or operational support of the system without specific written…