2. UO DRAFT SOW 30 January 09.doc

PEO-STRI-09-XXXX

W900KK-09-R-0002

30 January 2009

PEO-STRI-09-XXXX

W900KK-09-R-0002

30 January 2009

DRAFT

STATEMENT OF WORK

FOR

URBAN OPERATIONS TRAINING SYSTEMS

(UOTS)

Prepared by

Program Executive Office Simulation, Training and Instrumentation (PEO STRI)

12350 Research Parkway

Orlando, FL 32826-3276

REVISION LOG

TABLE OF CONTENTS

11. SCOPE

11.1 Overview

11.2 Background

22. APPLICABLE DOCUMENTS

22.1. Department of Department of Defense Directives

22.2 Availability of Department of Defense Directives

22.3. Other Government Documents, Drawings, and Publications

Error! Bookmark not defined.2.4 Availability of Other Government Documents, Drawings, and Publications

22.5. Non-Government Standards and Other Publications

33. REQUIREMENTS

33.1 MOUT Training Systems

33.1.1. Operations Control Facility Preparation

Error! Bookmark not defined.3.1.2. Range Preparation and Definition

133.1.3 Corps of Engineers (CoE) Coordination

Error! Bookmark not defined.3.2 MOUT Training Systems Program Oversight

Error! Bookmark not defined.3.2.1. Program Management

Error! Bookmark not defined.3.2.2. Integrated Product Teams (IPTs)

133.2.3. Program Reviews

133.2.3.1 Preliminary Design Review (PDR)

133.2.3.2 Test Readiness Review (TRR)

143.2.3.3 Technical Interchange Meetings (TIMs)

Error! Bookmark not defined.3.2.4. Program Schedule

Error! Bookmark not defined.3.2.5 Visitor Support

Error! Bookmark not defined.3.2.6 Exhibition Support

Error! Bookmark not defined.3.2.5 Contract Invoicing and Payment

Error! Bookmark not defined.3.3. Systems Engineering

Error! Bookmark not defined.3.3.1. System Baseline

Error! Bookmark not defined.3.3.1.1 Requirements Traceability

Error! Bookmark not defined.3.3.1.2 Hardware and Software Integration

Error! Bookmark not defined.3.3.2 Live Training Transformation (LT2)

Error! Bookmark not defined.3.3.2.1. CTIA Program Interface

Error! Bookmark not defined.3.3.2.2 Live Training Transformation (LT2) Product Line Interface and Support

Error! Bookmark not defined.3.3.2.3 Other Live Training Transformation Programs Interface

Error! Bookmark not defined.3.3.2.4 Software Blocking

Error! Bookmark not defined.3.3.3 Allocated Baseline Maturation

Error! Bookmark not defined.3.3.4. Safety Assessment and Health Hazard Analysis

Error! Bookmark not defined.3.3.4.1 Health Hazard Assessment

Error! Bookmark not defined.3.3.5. Automated Information System (AIS) Security

Error! Bookmark not defined.3.3.5.1 Information Assurance Vulnerability Alert (IAVA)

Error! Bookmark not defined.3.3.5.2 DoD Information Technology Security Certification and Accreditation Process (DITSCAP) Support

293.3.6. Electronic and System Protection

293.3.6.1. Surge Protection

293.3.6.2. Grounding

293.3.6.3. Lightning Protection

293.3.6.4 Electromagnetic Environmental Effects (E3)

Error! Bookmark not defined.3.3.7 Site Preparation

Error! Bookmark not defined.3.3.7.1 On-Site

Error! Bookmark not defined.3.3.7.2 On-Site Range Effort

Error! Bookmark not defined.3.3.8 Engineering Change Proposal (ECP)

Error! Bookmark not defined.3.4. System Verification

Error! Bookmark not defined.3.4.1. Early System Integration Platform and Demonstration

Error! Bookmark not defined.3.4.2. Test and Verification

Error! Bookmark not defined.3.4.3. On-Site Acceptance

293.4.4. Electromagnetic Interference/Compatibility Test and Verification

303.4.5. Electromagnetic Interference/Compatibility Acceptance

303.4.6. Environmental Test and Verification

303.4.7. Environmental Acceptance

Error! Bookmark not defined.3.4.8. Information Assurance Verification

Error! Bookmark not defined.3.5. Software Engineering

Error! Bookmark not defined.3.5.1 Software Design

Error! Bookmark not defined.3.5.1.1 Software Requirements and Architecture Development and Review

Error! Bookmark not defined.3.5.1.2 Software Design and Implementation

Error! Bookmark not defined.3.5.1.3 Software Development Test

Error! Bookmark not defined.3.5.2. Interface Control

Error! Bookmark not defined.3.5.3. Virus Software

Error! Bookmark not defined.3.6 Technical Publications

Error! Bookmark not defined.3.6.1 Publications In-Process Reviews (IPR)

Error! Bookmark not defined.3.6.2 Validation

Error! Bookmark not defined.3.6.3 Verification

Error! Bookmark not defined.3.7. Training

Error! Bookmark not defined.3.7.1. New Equipment Training (NET)

Error! Bookmark not defined.3.7.2 Instructor and Operator Training

Error! Bookmark not defined.3.7.3 Maintenance Training

Error! Bookmark not defined.3.7.4 Class Size

Error! Bookmark not defined.3.7.5 Course Completion Criteria

Error! Bookmark not defined.3.8. Configuration Management

Error! Bookmark not defined.3.8.1. Product Definition Data (PDD)

Error! Bookmark not defined.3.8.2 Physical Configuration Audit (PCA)

Error! Bookmark not defined.3.8.2 Unique Identification (UID) of Tangible Items

Error! Bookmark not defined.3.9. Logistics Analysis

Error! Bookmark not defined.3.9.1 Spares Acquisition Integrated with Procurement/Production

Error! Bookmark not defined.3.10 Deleted

Error! Bookmark not defined.3.11. Technical Studies

Error! Bookmark not defined.3.12. Telecommunication System Engineering Plan (TSEP)

Error! Bookmark not defined.3.13. Initial Logistics Support

DRAFT Statement of Work for

Urban Operations Training Systems

1 SCOPE TC "1. SCOPE" \f C \l "1" .

This Statement of Work (SOW) defines the work efforts for the design, fabrication, installation, integration, verification and fielding of the UOTS. UOTS for this effort includes the following sites and types of efforts.

· Army, Army Reserve and National Guard

· DOD Sites

· Integrated MOUT Training Systems (IMTS)

· Mobile MOUT

· Modular Live-Fire Shoot Houses (MLFSH)

· Combat Training Center MOUT-Instrumentation Systems (CTC MOUT-IS)

· UOTS Site Upgrades and Technology Refresh

· MOUT Training (FMS and sales to other countries)

· Corps of Engineers Reviews (Charrettes, Design, Inspections)

· Integration/Interoperability with other DOD Systems (LVC, Tactical Systems, C4I, etc.)

· UOTS Information Assurance

· UOTS Engineering

· UOTS Logistics

1.1 Overview TC "1.1 Overview" \f C \l "1" .

For the purpose of this Statement of Work, the Allocated Baseline is defined as the entirety of the proposed solution (hardware, software, firmware, and data) in fulfillment of the Performance Specification. All efforts addressed in this Statement of Work are in reference to the maturation of the Allocated Baseline over time or modification of the Allocated Baseline for the fulfillment of a particular range instantiation.

1.2 Background TC "1.2 Background" \f C \l "1" .

The intent of the UOTS is to provide dynamic, modular and scalable solutions to fulfill various aspects of individual, collective, and combined arms training. The UOTS may encompass more than traditional going-to-war training; it also addresses other-than-war operations (such as peacekeeping missions), and homeland defense and anti-terrorism scenarios. UOTS includes MOUT efforts associated with the Global War On Terror (GWOT).

The UOTS supports both fixed permanent and non-permanent structure facilities, allows for the addition or expansion to existing facilities, allows for the integration across sites and mission domains (Live, Virtual, and Constructive), and supports the continuation of instrumentation and data processing growth commensurate with tactical systems.

UOTS will completely immerse the training participants into the realism of the event, and will become indistinguishable from “real life” environments. The UOTS environment must allow and support flexibility and changing of scenarios to prevent learned responses vice learning benefit. Finally, UOTS must include unexpected, unplanned and uncontrolled events.

2. APPLICABLE DOCUMENTS TC "2. APPLICABLE DOCUMENTS" \f C \l "1" .

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 the SOW shall be the governing requirement.

2.1 Department of Defense Directives TC "2.1. Department of Department of Defense Directives" \f C \l "1"

DODD 8500.01

Information Assurance

DODI 8500.2

Information Assurance (IA) Implementation

DODI 8510.01

Department of Defense Information Assurance Certification and Accreditation Process (DIACAP)

DODI 8320.04

Item Unique Identification (IUID) Standards for Tangible Personal Property

2.2 Availability of Department of Defense Directives/Guidance TC "2.2 Availability of Department of Defense Directives" \f C \l "1" .

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

(IUID) http://www.acq.osd.mil/dpap/pdi/uid/index.html

2.3 Other Government Documents, Drawings, and Publications. TC "2.3. Other Government Documents, Drawings, and Publications" \f C \l "1"

MIL-DTL-31000

Technical Data Packages

MIL-STD-40051-2

Preparation of Digital Technical Information for Page-Based Technical Manuals

MIL-STD-130

DoD Standard Practice Identification Marking of US

Military Property

PEO-STRI-XXXX

UOTS Specifications

MIL-PRF-49506

Logistics Management Information (LMI)

2.4 Non-Government Standards and Other Publications TC "2.5. Non-Government Standards and Other Publications" \f C \l "1" .

ANSI/NFPA 70

National Electric Code

NFPA 780

Installation of Lightning Protection Systems

3. REQUIREMENTS TC "3. REQUIREMENTS" \f C \l "1" .

3.1 UOTS TC "3.1 The Urban Operations and Live Training Ranges Systems" \f C \l "1" .

You shall procure and acquire materials, install, integrate, test and verify performance, and document the allocated baseline training systems in fulfillment of the requirements defined in Performance Specification (XXXX). You shall define and maintain a system baseline for the fielded and tested system; this baseline shall be established prior to the start of testing and maintained through system acceptance. This includes targets, battlefield effects, sounds, video, monitoring & recording cameras, After Action Review (AAR), Observer Controller interface, Position Location Tracking (PLT), Range Operations Center instrumentation and Mobile MOUT and Modular Live-Fire Shoot Houses.

3.1.1 Instrumentation TC "3.1.1. Operations Control Facility Preparation" \f C \l "1" .

You shall ensure that the Range Operations Center (ROC) and AAR are instrumented and integrated with UOTS. You shall perform the following:

a. Report any design changes as a result of on-site preparations for installation to include trade-off impacts.

b. Report any damage or accidents to on-site government representative as soon as possible, but not later than the next business day.

c. Perform all the tasks necessary to prepare and to install UOTS instrumentation. These tasks shall include trenching, cabling, power connections, target pit preparations, and any other tasks required.

d. The prime contractor or sub-contractors shall possess all necessary licenses and permits to conduct grading, excavation, trenching (for power and electrical cables) and construction of supporting infrastructure and local environmental effects.

3.1.2 Mobile Systems

a. The prime contractor or sub-contractors shall possess all necessary licenses and permits to conduct grading, excavation, trenching (for power and electrical cables) and construction of supporting infrastructure and local environmental effects.

b. If special anchoring for wind resistance is required, the vendor shall include sufficient analysis for the Government to verify the resistance of the containers and structures to wind.

c. The Mobile MOUT assets shall be capable of installation/erection on graded level soil (compacted if necessary), gravel or cement site. The Mobile MOUT training sets shall be operational as soon as possible after site preparation is completed. Configuration and complexity determine actual time to complete.

3.1.3 Hardware and Software Integration TC "3.3.1.2 Hardware and Software Integration" \f C \l "1" .

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

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

b. Test procedures for components, assemblies, and products are complete and accurate.

c. The system and products were tested in accordance with established procedures.

d. An audit trail shall be established that logs all changes made to meet specification requirements.

e. Risk Management (reference Risk Management section)

f. Present a fielding plan which covers the required procedures and resources to field the system. Planning is complete and procedures, resources, and other requisite people, products, and processes are available (or programmed to be available) to initiate production, distribution, operations, support, training, disposal, and evolutionary development (if any).

3.1.4 Production Planning.

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

3.1.5 Product Definition Data (PDD) TC "3.8.1. Product Definition Data (PDD)" \f C \l "1" .

3.2 Integrated Product and Process Management

3.2.1 Integrated Product and Process Development (IPPD)

3.2.1.1 Systems Engineering Design

You shall provide a systems engineering approach and activities necessary to maintain the allocated baseline and to deploy a complete and functional system. System engineering includes all planning, organizing, and control to ensure that the operational needs and requirements are delineated as functional requirements. You shall include into the Systems Engineering process considerations for supportability, maintenance concepts, obsolescence, and total ownership cost management (reduction). The systems engineering approach shall be one of an incremental build. Each build shall add functionality to the previous build, so that the final build shall be one that is tested and verified at acceptance testing. Systems integration includes the integration of technical components, organizational components, and verification (acceptance testing). The area of system integration may make use of technical laboratories, prototype systems, and pilot systems. The development of these systems shall include all necessary safety, reliability/maintainability engineering, Manpower and Personnel Integration (MANPRINT), pollution prevention, and human factor considerations. You shall employ a quality engineering program to measure and track key processes and establish metrics and process control systems.

3.2.1.1.1 System Baseline TC "3.3.1. System Baseline" \f C \l "1" .

You shall define, maintain, and integrate the allocated baseline to meet the requirements of PRF-PT-00XXX . You shall track the requirements in an automated management tool from requirements development through final acceptance.

3.2.1.1.2 Requirements Traceability TC "3.3.1.1 Requirements Traceability" \f C \l "1" .

You shall track and account for all requirements (including derived requirements) through the use of a requirement traceability matrix implemented using a commercially available database tool. The requirements traceability database shall provide traceability from the requirement design criteria source data to the system test procedure. You shall maintain and update the requirements traceability database throughout the contract.

3.2.1.1.3 Technical Studies TC "3.3.1.1 Requirements Traceability" \f C \l "1" .

You shall perform additional technical studies, when requested. The technical studies programmatic scope and desired outputs and outcomes shall be defined at the time of the study initiation. You shall extend the IPT approach to envelop the results of the studies in a seamless and homogenous manner.

3.2.1.2 Software Engineering

You shall use systematic, documented methods for all software development activities and establish and apply standards and practices for representing requirements, design, code, test cases, test procedures, and test results. Traceability shall be maintained between levels of requirements, between requirements and design, between design and the software that implements it, between requirements and qualification test information, and between computer hardware resource utilization requirements and measured computer hardware resource utilization. You shall ensure that interoperability and security are built-in, and that information made available is trusted and interoperable. You shall identify and evaluate reusable software products that meet specified requirements and are cost-effective over the life of the system. You shall analyze requirements concerning computer hardware resource utilization and allocate computer hardware resources among the software items, continuously monitor the utilization and reallocate or identify the need for additional resources. You shall record rationale that will be useful to the maintenance organization for key decisions made in specifying, designing, implementing, and testing the software. The rationale shall include trade-offs considered, analysis methods, and criteria used to make the decisions. The rationale shall be recorded in documents, code comments, or other media that will transition to the maintenance organization. You shall maximize the usage of commercial software packages, open source and LT2 software components.

3.2.1.2.1 Software Design TC "3.5.1 Software Design" \f C \l "1" . You shall develop the system software and firmware in accordance with recognized industry standards and internal documented process. The design shall incorporate features that promote ease of operation, ease of software maintenance, ease of future updates and modifications. The test configuration shall match the final baseline. You shall document the procedures and demonstrate that the software baseline tested can be regenerated following established procedures. (DI-IPSC-81441A, DI-IPSC-81442A)

3.2.1.2.2 Software Requirements and Architecture Development and Review TC "3.5.1.1 Software Requirements and Architecture Development and Review" \f C \l "1" . You shall develop software requirements and architecture in accordance with your software development process plan. You shall define and record the operational concept, the architectural design (identifying the components and their interfaces) and the traceability between the system components and system requirements.

3.2.1.2.3 Software Design and Implementation TC "3.5.1.2 Software Design and Implementation" \f C \l "1" . You shall design software, develop executable code, perform unit testing, and integrate software components (with each other and with hardware components) to meet system requirements. Software design includes not only design to requirements, but selection of existing software products to meet system requirements.

3.2.1.2.4 Software Development Test TC "3.5.1.3 Software Development Test" \f C \l "1" . You shall establish test cases (in terms of inputs, expected results, and evaluation criteria) and establish traceability between the test case and the system requirements, detailed procedures for conducting the test, and test data for testing the software corresponding to each software item. You shall test the software corresponding to each software item. The testing shall be in accordance with the unit test cases and procedures. You shall analyze the results of item testing and shall record the test and analysis results. Prior to the start of final test, you shall upgrade the Commercial Off The Shelf (COTS) products to the latest versions, as applicable to support and maintain system without performance implications.

3.2.1.2.5 Interface Control TC "3.5.2. Interface Control" \f C \l "1" . You shall describe the interface boundaries between all hardware and software configuration items, and any interfaces available to outside systems. These descriptions shall include references to commercial standards, messages protocols, and security issues and precautions.

(DI-CMAN-81248A)

3.2.1.3 Engineering Supportability

You shall conduct engineering analyses to establish quantitative and qualitative supportability design guidelines. You 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. You shall coordinate with existing life cycle support contractors (LCCS) using associate contractor agreements, develop initial fielding plans for the system and verify that the maintenance actions and support structure are aligned with the maintenance concept. You shall evaluate reliability, availability, and maintainability factors in your design process. Design for supportability shall include the use of common components and parts, common commercial standards, and proven technology. Your design shall minimize life-cycle costs and maximize life-cycle supportability by avoiding the use of proprietary items; components with limited sources for spare parts, support, or maintenance; recurring usage or service fees; and the need for special tools or test equipment

3.2.1.3.1 Logistics Analysis TC "3.9. Logistics Analysis" \f C \l "1" .

You shall conduct an analysis after final design and prior to system baseline and installation. This will identify the spares, expendables, and manpower necessary for the normal operation and maintenance of the system performance. You shall determine the most efficient and effective means, tools, and processes of documenting and conducting your analysis. You shall document all assumptions made during the analysis and include all boundaries and other constraints placed on the final technical recommendation. The analysis shall provide all information in clear and understandable terms. This report shall be formatted and utilized to support future sustainment recommendations. You shall identify support resources and infrastructure necessary for test and evaluation activities. You shall analyze existing LCCS support structures and develop and define an optimized support infrastructure for production and deployment. The recommended support resources shall be sufficient to allow another contractor with comparable skills to assume operation, maintenance, and support of the system and sustain the system availability requirement. You shall only use the form, fit, function, and interface requirements in the performance specifications for provisioning, training and maintenance planning. You shall document the analysis in the support summaries. (DI-ALSS-81530)

3.2.1.3.2 Supportability Analysis and Logistics Management Information.

You shall identify support requirements for the system. This shall include any Associated Support Items of Equipment (ASIOE), projected support costs, and risk items. You shall conduct repair level analyses, develop diagnostic, preventative maintenance and repair procedures, conduct facilities analyses, refine hardware and software maintenance and support concepts, and identify support resource requirements including required spares and support equipment. You shall develop a listing of which items should be repaired and which should be discarded and the level of maintenance at which the repair should be performed with the associated cost. You shall document the following in the integrated database (e.g. contractor’s preferred database or IMTS Sharepoint site):

a. All input data and their corresponding value and source of the data.

b. Operational scenario modeled, assumptions made, constraints assumed, and non-economic factors imposed.

c. Maintenance alternatives considered.

d. Analytical method and models used to perform the economic evaluations.

e. The sensitivity of the evaluation performed including the results obtained.

(DI-ALSS-81529) Logistics Management Information (LMI) Data Product(s)

(DI-ALSS-81530) Logistics Management Information (LMI) Summaries

3.2.1.3.4 Unique Identification (UID) of Tangible Items TC "3.8.2 Unique Identification (UID) of Tangible Items" \f C \l "1" .

You shall be knowledgeable of all DoD requirements for uniquely identifying government property and implement a Unique Identification program in accordance with DODI 8320.04 and MIL-STD-130. Unique item identifier means a set of data marked on items that is globally unique, unambiguous, and robust enough to ensure data information quality throughout life and to support multi-faceted business applications and users. These requirements apply to developed and commercial items. You shall coordinate among the IPT members and identify IUID type, the IUID to be used, and items requiring unique identification including embedded subassemblies, components and parts. You shall provide unique item identification, or a DoD recognized unique identification equivalent, for all identified items delivered. IUID marking of items shall be both machine readable and human readable and located for easy viewing for inventory/accountability purposes. You shall load all required IUID data into the UID Central Registry and provide to the Government a listing of all items marked with a IUID label and entered into the registry. (DI-MGMT-80177A.

3.2.1.4 Specialty Engineering

3.2.1.4.1 Reliability Engineering

You shall develop, implement and manage a system reliability process satisfying all reliability objectives and be completely integrated within the systems engineering process. The reliability process shall support economical achievement of overall program objectives and ensure sustained product integrity, personal safety, and logistics support information is derived from early reliability engineering analysis such that reliability engineering can be applied to influence the design effort. The process shall:

a. Improve operational readiness and mission success of the system.

b. Reduce system demand for maintenance manpower and logistic support.

c. Provide essential management information.

d. Hold down the reliability programs own impact on overall program cost and schedule.

Specific reliability design and verification criteria shall be established. All reliability data and information used for logistics support analysis and engineering activities shall be based upon, and traceable to, the outputs of the reliability process. Reliability status shall be included as part of each program review. You shall conduct trade off studies to ensure quantitative issues such as stress levels, selection of parts, parts simplicity and redundancy are properly considered in the design trade off. You shall verify that reliability requirements are attained through analyses and test.

3.2.1.4.2 Maintainability Engineering

You shall develop, implement and maintain a system maintainability process satisfying all maintainability and related objectives and be completely integrated within the systems engineering process. The maintainability process shall form the basis of concurrent and subsequent life cycle planning. The maintainability effort shall measure complexity, accessibility, and testability to enhance servicing, preventive maintenance, corrective maintenance, and diagnostic capabilities. Specific design and verification criteria shall be established through performance specifications, of qualitative and quantitative factors to be expressed as measures of maintainability achievement, for system, segment, subsystem, and equipment levels.

3.2.1.4.3 Testability Engineering

You 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. You shall establish controls for ensuring that each subcontractor’s testability practices are consistent with overall system requirements. You shall define the means for demonstrating and validating that the diagnostic capability meets specified requirements, using maintainability demonstrations, test program verification, and other demonstration methods. You 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, and solutions are traceable to diagnostic hardware and software, and technical publication procedures are updated. You 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. You 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.2.1.4.4 Safety Engineering

You shall develop and implement tasks and activities to identify, evaluate, and eliminate or control hazards throughout the systems life cycle. You shall ensure the safety of the system's design, operation, transportation, maintenance, support, and disposal. You shall conduct safety analyses, hazard identification and classification and hazards tracking integral to the system design effort. A hazard risk index including hazard severity and hazard probability levels shall be developed for all hazards.

3.2.1.4.4.1 Safety Assessment and Health Hazard Analysis TC "3.3.4. Safety Assessment and Health Hazard Analysis" \f C \l "1" .

You shall analyze the final design and conduct a safety assessment and health hazard analysis of the UO/LTR. The entire system shall be considered for these analyses. The analysis shall include a description of all identified risks, hazards, and environmental concerns, and the means to reduce these risks to acceptable levels. (DI-SAFT-80102B)

3.2.1.4.4.2 Health Hazard Assessment TC "3.3.4.1 Health Hazard Assessment" \f C \l "1" .

You shall identify all potential health hazards and recommend engineering controls, equipment and protective procedures to reduce the associated risk to an acceptable level. You shall assess system, facility, and personnel protective equipment design requirements to allow safe operation and maintenance. When feasible engineering designs are not available to reduce hazards to acceptable levels, you shall develop alternative protective measures. You shall address the hazardous materials listed in the Environmental Protection Agency's (EPA) toxics release inventory and the list of Class I and Class II stratospheric ozone depleting substances (ODSs), as listed 29 Code of Federal Regulations (CFR) 1910.1200. (DI-SAFT-80106B)

3.2.1.4.4.3 Health Hazard Assessment Report (HHAR).

You shall collaborate with the U.S. Army’s Center for Health Promotion and Preventive Medicine (CHPPM) agency to obtain a HHAR for the system as a whole and all its related subsystems, if needed.

3.2.1.5 Interoperability.

3.2.1.5.1 Live Training Transformation (LT2) TC "3.3.2 Live Training Transformation (LT2)" \f C \l "1" .

The LT2 Product Line Management Concept of Operations is intended to ensure an integrated and compatible line of Live Training products that maximize use of common components. The Common Training Instrumentation Architecture (CTIA) determines the core compatibility standard for LT2.

(DI-MISC-80711A)

3.2.1.5.2 Common Training Instrumentation Architecture (CTIA) Program Interface TC "3.3.2.1. CTIA Program Interface" \f C \l "1" .

You shall work with the CTIA program and representatives and support the PM TRADE Live Training Transformation (LT2) strategy. You shall monitor their system development and identify and leverage components for re-use vice new development. You shall ensure any software development efforts are compatible with the latest baseline configuration release from the CTIA program. You shall adhere to the CTIA compliance definitions for new major systems and subsystems utilized within your system. You shall conduct and support the CTIA compliance verification processes for developed, integrated, or procured components. You shall utilize the CTIA Product Line Architecture Specification (PLAS) and Product Line Architecture Framework (PLAF) documentation to maximize software re-use from the LT2 components repository. You shall provide an evaluation of the applicability of existing and programmed LT2 Components and delineate anticipated modifications.

3.2.1.5.3 LT2 Product Line Interface and Support TC "3.3.2.2 Live Training Transformation (LT2) Product Line Interface and Support" \f C \l "1" .

You shall work with the LT2 program. You shall utilize the LT2 CONOPS and support the initiatives for the development of common components with the baseline architectures utilized within the range facilities. You shall establish, maintain, and coordinate component contracts, transaction definitions, and relationships within the LT2 Domain Architecture, and establish appropriate interface and control specifications. You shall support the development Department of Defense Architecture Framework (DODAF) model in support of the LT2; you shall ensure the incorporation of domain specific component and participate in the development of the entire framework model.

3.2.1.6 Packing, Handling and Storage (PHS)

You shall conduct and analyses for PHS of the system; subsystems and system components. This will identify any unique requirements, management responsibilities, and procedures use to ensure that PHS unique requirements are identified. You shall identify the following PHS requirements:

a. Describe storage modes and constraints, environmental storage and climates requirements including humidity, and static control and grounding.

b. Identify special care required during the removal of sensitive components, calibration, and special PHS requirements during repair and movement.

c. Identify requirements for shipping equipment worldwide.

3.2.1.7 Quality Engineering

You shall establish measurement points that will provide maximum visibility into new and prior processes to assure contractual requirements are being met. You shall select the proper methods to analyze these processes to continuously improve the system. Metrics shall be developed to assist management visibility into an adequate process control system. You shall establish and maintain a computerized discrepancy tracking system within the IMTS Integrated Digital Environment (IDE) (e.g. IMTS SharePoint site) with the ability to produce complete permanent records of all discrepancy or database listing. You shall establish a suspense system to ensure timeliness of analysis and corrective action for discrepancies and risk reduction items. All discrepancy correction shall be documented and entered in the integrated database.

3.2.1.8 Information Assurance

You shall develop and maintain an Information Assurance (IA) process to guide management and design actions, document decisions, specify and track IA requirements, document certification efforts, identify possible solutions, and maintain operational systems security. You shall establish or adopt standards for managing IA requirements and capabilities and an information system security engineering approach that emphasizes purposeful design or configuration of security solutions.

3.2.1.8.1 Assessment.

You shall conduct an assessment of the current system environment and the supporting infrastructure for security vulnerabilities and weaknesses. You shall quarterly support evaluation of the security of the system, both physical and logical, identifying exposures and providing protective options for reducing security risk for the period of performance of this contract. You shall identify assets to be protected, identify system vulnerabilities, provide software patches and a set of recommendations on how to eliminate or mitigate the threats.

3.2.1.8.2 Implementation.

You shall implement protective measures to address identified system vulnerabilities. You shall integrate protective mechanisms into the system and applications to provide enhanced identification and authentication, access control, accountability, availability, confidentiality, privacy, data integrity, and non-repudiation. You shall provide all architectures, plans, policies and security controls in accordance with the DIACAP, DoD 8500.1, DoD 8500.2, DoD 8510.bb and AR 25.2 for integrating robust security practices. You shall maintain IAVA & STIG compliances throughout the System Development Lifecycle.

3.2.1.8.3 Verification.

You shall verify that protective measures appropriately address each specific security requirement. Contractor shall test the security controls appliances using Army approved IA tools, located at the U.S. Army Computer Emergency Response Team (ACERT) website: https://www.acert.1stiocmd.army.mil, to ensure they meet appropriate levels of acceptability to the Certification Authority.

3.2.1.8.4 Certification & Accreditation

You shall support the Government in the Certification and Accreditation (C&A) of the system in accordance with the DIACAP and PEO STRI’s Basic Accreditation Manual (BAM). Contractor shall deliver all documentation required by the Contract in accordance with the PEO Contract policies. You shall support the Army IMTS Designated Approval Authority (DAA). Contractor shall provide the IA security requirements for a system that has Mission Assurance Category (MAC) Level III, a Confidentiality Level (CL) of Sensitive and a Robustness Level of Basic. You shall support efforts to secure an IMTS Authority to Operate (ATO). You shall capture all these efforts in a delivered Comprehensive DIACAP Package Review (CPR) document that will be generated to support securing an ATO for IMTS. For the period of performance of this contract, the contractor shall support the government in maintaining the IMTS ATO through:

a. Annual Security Review

b. Annual Contingency Test

c. Annual Security Control Test

d. Information Assurance Vulnerability Alerts and STIG compliances

3.2.1.8.5 Information Assurance Vulnerability Alert (IAVA)

You shall implement processes and ensure compliance to the IAVA requirements throughout the development, integration, fielding, and verification of the system. Contractor shall ensure and record the implementation of the IAVA requirements. You shall acknowledge IAVAs within five days of an alert and comply with IAVAs within thirty days of an alert.

3.2.1.8.6 DoD Information Assurance Certification and Accreditation Process (DIACAP) Support You shall provide assistance in the development of the documentation required to achieve accreditation and certification. You shall assist the government during the definition, verification, and validation phases of the certification and accreditation processes.

3.2.1.9 Technical Reviews

3.2.1.9.1 Corps of Engineers (CoE) Coordination TC "3.1.3 Corps of Engineers (CoE) Coordination" \f C \l "1" .

You shall attend and participate in the Target Interface Inspection (TII) with the Corps of Engineers (CoE) for each of the sites, as appropriate. You shall review the instrumentation infrastructure requirements, to include network connectivity, fiber optics, conduits, cable trays, power, grounding, air conditioning loading, etc., and the impacts unto the designs and site building plans,

3.2.1.9.2 Program Reviews TC "3.2.3. Program Reviews" \f C \l "1" .

You shall attend and conduct the program reviews. The reviews shall provide a forum for IPT members to clarify integration, installation, and management issues. You shall document action items, coordinate resolutions, and track action items until closure.

3.2.1.9.3 Technical Design Review (TDR) TC "3.2.3.1 Preliminary Design Review (PDR)" \f C \l "1" .

You shall conduct a Technical Design Review (TDR) to demonstrate the technology of the UOTS. A TDR shall be conducted for each baseline to be fielded. The TDR shall be a formal technical review of the basic design approach, the allocated baseline, and changes made to the allocated baseline. The TDR shall cover the progress and technical adequacy of the selected design approach. The TDR shall include a subsystem block and functional diagram, design standards and logistical considerations (including training and manuals), and interference analysis.

3.2.1.9.4 Test Readiness Review (TRR) TC "3.2.3.2 Test Readiness Review (TRR)" \f C \l "1" .

Prior to the start of system acceptance testing at each site, you shall present evidence that documentation is complete, test facilities are ready, prior test(s) were successful or open issues have been addressed. There shall be reasonable confidence that the system to be tested can satisfactorily pass the test and enter the next test phase. This review shall determine what actions are required to ensure resources, training, and test hardware will be in place to support the successful conduct of the test, and to ensure that test and evaluation planning, documentation, design maturity and configuration, and data systems has been adequately addressed.

You shall address the following key issues at the system engineering TRR prior to the start of formal testing to ensure that the system and all test resources are ready to begin testing:

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

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

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

· Operator and Maintenance Manuals are validated

· System Drawings are validated

· Validated Inventory Lists of system components The following documentation shall be reviewed during the TRR:

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

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

· Requirements changes pending.

· Design changes since the last design review.

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

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

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

· Problem areas and their resolution.

3.2.1.9.5 Technical Interchange Meetings (TIMs) TC "3.2.3.3 Technical Interchange Meetings (TIMs)" \f C \l "1" .

You shall support TIMs as required. A TIM shall address specific topics or issues, address status of development or test activities between management reviews, address the functions of an established working group, or coordinate and provide guidance for engineering data or technical publications.

3.2.2 Program Management.

You shall provide the overall management and administrative effort necessary to ensure that the requirements of this contract are accomplished. You shall track program progress utilizing metrics. You shall plan, implement, and maintain a life cycle cost (LCC) management process to minimize the system cost and use LCC to conduct trade studies, evaluate design and support alternatives, and select the resource support requirements. You shall define and monitor metrics and technical performance measures (TPMs) to evaluate the performance of each critical technical and management process and conformance of the evolving products with contract requirements and objectives including cost requirements and objectives. You shall provide ROMs, site proposals and site execution schedules that shows planned efforts to satisfy site contractual requirements.

(DI-MGMT-81453) Data Accession List (DAL)

3.2.2.1 Integrated Master Plan (IMP).

You shall implement, manage to, update, and maintain the contract IMP. You shall develop the system in accordance with the IMP. The IMP shall be used throughout the contract as a management tool to assess progress and determine success in achieving program requirements. You shall report on work in progress in accordance with the IMP at each program review, at selected technical reviews and at government discretion. The IMP shall depict the contract work breakdown structure. The contents of the IMP shall be determined through the Integrated Product and Process Management process.

3.2.2.2 Integrated Master Schedule (IMS).

You shall develop, implement, manage to, update, and maintain the contract IMS. All contract schedule information delivered or presented at program reviews shall originate from the IMS, shall be traceable to the IMP, and shall contain all critical events and exit criteria, accomplishments, predecessors and successors events, and their dependencies. The IMS shall address total program activities including activities performed by major subcontractors. You shall develop an IMS that accurately portrays the sequence and relationship of activities defining the total development and production program. These activities shall be keyed to the Contract Work Breakdown Structure (CWBS). The IMS shall be implemented on a computer based management control system which utilizes critical path method network analysis, accepts parametric data input, and can provide an estimate of the program schedules and cost for reporting project progress. The time and cost data shall be updated to reflect accomplished activities and any changes in activity time and cost estimates. You shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

(DI-MISC-81650) Integrated Master Schedule (IMS) [NOTE: For the IMS, the CDRL must define “significant and critical” elements.]

(DI-MGMT-81334B) Contract Work Breakdown Structure

3.2.2.3 Financial Management.

You shall plan, budget, schedule, and control the resources and costs allocated to meet the requirements of the contract. You shall document and track the status of all funds associated with the contract to include payments, cancellations and invoices against each contract line item and sub-line item. You shall extend the government-provided CWBS to lower levels which represent how you plan to accomplish the entire contract work scope and which are consistent with internal organizations and processes. The extended CWBS shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status. You shall identify major elements of subcontracted work in the extended CWBS and may propose changes to the CWBS to enhance its effectiveness in satisfying program objectives. You shall continually update the integrated database during contract performance with pertinent records and data that underlie and support the cost and schedule data reported.

(DI-MGMT-81468) Contract Funds Status Report (CFSR)

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

(DI-MGMT-81334B) Contract Work Breakdown Structure

3.2.2.3.2 Integrated Baseline Review.

You shall participate with the government in the assessment of program risk and the degree to which the following have been established:

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

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

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

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

· Rationales underlying the review are reasonable.

· Management processes support successful execution of the project.

3.2.2.4 Risk Management.

You shall prepare, implement, and maintain a cost, technical and schedule risk management process which includes risk detection and identification, assignment of risk categories, corrective actions, tracking of compliance, reporting of status and planning for risk abatement. You shall cover Risk Management at all Program Reviews. You shall:

· Identify and document moderate and high-risk items for each risk assessment area.

· Identify and implement risk handling approaches and track over time each moderate and high-risk item.

· Document risk issues that have been successfully resolved and schedule each open item into the program IMS.

· Allocate life cycle cost and schedule goals to each development item in a manner balancing Cost, Schedule, Performance (CSP) and risk using Cost As Independent Variable (CAIV), its schedule equivalent, and associated CSP risk analysis.

· Develop mitigation plans to identify the recommended critical path for contract completion and the appropriate risk handling approach to lower the level of uncertainty identified.

· Recommend decision points in terms of CSP objectives to facilitate management and technical control.

3.2.2.5 Management Reviews.

You shall conduct periodic program reviews as coordinated with the government.