3. UO SOW

194 KB Posted

Attached to
Urban Operations Training Systems (UOTS)
Solicitation number
W900KK09R0002
Issued by

About this file

3. UO SOW (Draft rev 1)

Text of this file

DRAFT

STATEMENT OF WORK

FOR

URBAN OPERATIONS TRAINING SYSTEMS

(UOTS)

Prepared by Program Executive Office Simulation, Training and Instrumentation (PEO STRI) 12350 Research Parkway

PEO-STRI-09-W034

Sol. # 900KK-09-R-0002 03 February 2009

PEO-STRI-09-W034

Sol. # 900KK-09-R-0002 18 June 2009

Orlando, FL 32826-3276

REVISION LOG

Date
Version
Author
Section
Revision Description

TABLE OF CONTENTS

1.0 SCOPE.1
1.1Overview.1
1.2Background.1
2.0 APPLICABLE DOCUMENTS.2
2.1Department of Defense Directives.2
2.2Availability of Department of Defense Directives/Guidance.2
2.3Other Government Documents, Drawings, and Publications.2
2.4Non-Government Standards and Other Publications.3
3.0 REQUIREMENTS.3
3.1UOTS.3
3.1.1Instrumentation.3
3.1.2Mobile Systems.3
3.1.3Hardware and Software Integration.4
3.1.4Production Planning.4
3.1.5Recurring Manufacturing Support.4
3.1.6Product Definition Data (PDD).5
3.1.7Electronic and System Protection.6
3.1.7.1Surge Protection.6
3.1.7.2Grounding.6
3.1.7.3Lightning Protection.6
3.1.7.4Electromagnetic Environmental Effects (E3).6
3.1.8Electromagnetic Interference and Compatibility Test and Verification.6
3.1.9Electromagnetic Interference and Compatibility Acceptance.6
3.1.10Environmental Test and Verification.6
3.1.11Environmental Acceptance.6
3.2Integrated Product and Process Management.6
3.2.1Integrated Product and Process Development (IPPD).6
3.2.1.1Systems Engineering Design.6
3.2.1.2Software Engineering.7
3.2.1.3Engineering Supportability.9
3.2.1.4Specialty Engineering.10
3.2.1.5Interoperability.12
3.2.1.6Quality Engineering.13
3.2.1.7Information Assurance.13
3.2.1.8Technical Reviews.14
3.2.2Program Management.16
3.2.2.1Integrated Master Plan (IMP).16
3.2.2.2Integrated Master Schedule (IMS).16
3.2.2.3Financial Management.17
3.2.2.4Risk Management.17
3.2.2.5Management Reviews.17
3.2.2.6Configuration Management.18
3.2.2.7Visitor Support.22
3.2.2.8Contract Invoicing and Payment.22
3.3Testing.22
3.3.1Developmental Test.22
3.3.2Operational Test Support.22
3.3.3Logistics Demonstration.22
3.3.4Production Qualification Test.23
3.3.5Government Acceptance Test (GAT).23
3.3.6Physical Configuration Audit (PCA).23
3.4New Equipment Training.23
3.4.1Operator Training.24
3.4.2Maintenance Training.24
3.4.3Language.24
3.4.4Class Size.24
3.4.5Location of Training.24
3.4.6Training Facility and Equipment.24
3.4.7Recommended Timing of Training Delivery.24
3.4.8Course Completion Criteria.24
3.4.9Course Completion Notification.25
3.5Test Measurement and Diagnostic Equipment.25
3.6System Install Preparation.25
3.6.1Contractor Site Survey.25
3.6.2Installation Program.25
3.6.3Installation Tools and Test Equipment.25
3.6.4Initial Spares. And Repair Parts.26
3.7Interim Life Cycle Contractor Support (LCCS).26
3.7.1Software Support.26
3.7.2Site Support.26
3.7.3Engineering Services.26
3.7.4Transition for Sustainment.26
3.8Integrated Digital Environment.27
3.8.1Data Management.27
3.8.2Database Maintenance.27
3.9Technical Publications.27
3.9.1Publications In-Process Reviews (IPR).28
3.9.2Validation.28
3.9.3Verification.28
3.10Packaging, Handling, Storage, and Transportation (PHS&T).28

Statement of Work for Urban Operations Training Systems (UOTS)

SCOPE.

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.

· Integrated Military Operations on Urbanized Terrain (MOUT) Training Systems (IMTS)

· Combined Arms Collective Training Facility (CACTF)

· Shoot House (SH)

· Urban Assault Course (UAC)

· Mobile MOUT

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

· UOTS Site Upgrades and Technology Refresh

· Integration with other Department of Defense (DOD) Systems (Live, Virtual, Constructive (LVC); Tactical Systems; Command, Control, Communications, Computers, & Intelligence (C4I))

· Other MOUT, UOTS, enhancements, updates, upgrades and changes required for Urban Operations (UO) Training

This covers all Army, Army Reserve, National Guard, and DOD sites located both Continental United States (CONUS) and Outside the Continental United States (OCONUS). This includes all Foreign Military Sales (FMS) and sales to other countries. This provides the support necessary for Corps of Engineers (CoE) Reviews (Charrettes, Design, Inspections), UOTS Information Assurance (IA), UOTS Engineering, and UOTS Logistics.

Overview.

For the purpose of this SOW, 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 SOW 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.

Background.

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 Overseas Contingency Operations (OCO).

The Army’s MOUT live training systems support building and room clearing, search, location and seizure of contraband and high value human targets, cordon and search (or knock) as well as full combined arms maneuver in the UO area. The UO for the Army includes a three-dimensional asymmetric battle space with underground tunnels or sewers and bunkers, hidden caches or voids and multi-storied urban valleys. These MOUT training systems will completely support training operations aimed at countering state sponsored or non-government hostile belligerents. Mobile MOUT training sets are specific live training aids supporting UO training exercises.

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 (LVC), 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.

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

Department of Defense Directives.

DODD 8500.01Information Assurance
DODI 8500.2Information Assurance Implementation
DODI 8510.01Department of Defense Information Assurance Certification and Accreditation Process (DIACAP)
DODI 8320.04Item Unique Identification (IUID) Standards for Tangible Personal Property

Availability of Department of Defense Directives/Guidance.

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

MIL-DTL-31000Technical Data Packages
MIL-STD-40051-2Preparation of Digital Technical Information for Page-Based Technical Manuals
MIL-STD-130DoD Standard Practice Identification Marking of US Military Property
PRF-PT-00519UOTS Specifications
MIL-PRF-49506Logistics Management Information (LMI)

Non-Government Standards and Other Publications.

ANSI/NFPA 70National Electric Code
NFPA 780Installation of Lightning Protection Systems

REQUIREMENTS.

UOTS.

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 PRF-PT-00519. 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 (ROC) instrumentation and Mobile MOUT.

Instrumentation.

You shall ensure that the ROC and AAR are instrumented and integrated with UOTS. You shall perform the following:

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

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

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.

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.

Mobile Systems.

1. 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.

1. 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.

1. 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.

Hardware and Software Integration.

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:

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

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

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

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

1. Risk Management (reference Risk Management section)

1. 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).

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.

Recurring Manufacturing Support.

You shall provide sustaining engineering support to resolve manufacturing problems. As changes become necessary, you shall recommend changes to the Functional Baseline (FBL) and update any elements of the product baseline. You shall maintain the functional architecture, the allocated baselines, and any elements of the product baseline so that they balance system performance, cost, schedule, and risk. You shall inform the IPT of changes that could affect performance, cost, schedule, or risk before they are implemented. You shall maintain the change history (date, rationale, and authority for each change and all previous baselines). As changes become necessary, you shall update the verification, manufacturing, support, deployment, training, operating, and disposal plans, procedures, and data and balance system performance, cost, schedule, and risk. You shall maintain the integrated database and include the following:

1. Both the original and all changes to the FBL, the functional architecture, the physical hierarchy, and the allocated, design, and product baselines.

Both the original and all changes to the system supportability data including logistics support plan, technical manuals, common (government-inventory) support equipment requirements, spares requirements, personnel skill levels, and manpower levels applicable to both operational Test and Evaluation (T&E) and system operations.

The approval authority and rationale for any changes to the data.

Provisions for the efficient traceability through the architectures, baselines, and the physical hierarchy from any element up to the sources of the FBL or down to the lowest elements of the product baseline; from any element to the corresponding requirement reference (such as a trade-off or other rationale); from any requirement to the corresponding verification method and verification plans, procedures, and data; from any component in the physical hierarchy to its design-to and build-to requirements, product description, and supportability data; and from any element to its change history.

Any other decision support data linked to its basis in the rest of the database.

Product Definition Data (PDD).

During the systems engineering and design, and in accordance with MIL-DTL-31000, you shall develop, produce, and maintain PDD that accurately depicts the final product. The PDD is the technical description of items adequate for supporting an acquisition strategy, production, engineering and logistics support. The PDD shall disclose complete design, logistics, manufacturing requirements, and the means of measuring compliance with the requirements. Piece part information (drawings, computer aided design files and meta data.) and associated lists shall provide the necessary design, engineering, manufacturing, and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product, without additional design engineering effort or recourse to the original design activity. You shall produce and maintain documentation for all electrical assemblies and subassemblies in such a manner to ensure their functional integration without recourse to special test equipment or installation of the assemblies or subassemblies into a next higher assembly. Utilizing the established logistic repair procedures, you shall identify the higher level components and assemblies to be repetitively procured as spare components and assemblies or which may be procured independently. For each higher level component or assembly, you shall determine and document the functional requirements for the item, the environment in which it must operate, interface and interchangeability characteristics, and criteria for verifying compliance. You shall obtain document numbers from the government for the PDD elements. You shall not add prefixes or suffixes to the numbers. All unused numbers shall be returned upon completion of PDD preparation. (DI-EGDS-80918, DI-SESS-81003B, DI-SESS-81000B, DI-IPSC-81431A, DI-SDMP-81493) Electronic and System Protection.

Surge Protection.

You shall integrate and install appropriate surge protection devices into the UOTS baselines. The surge protection shall be sized and appropriate for all of the equipment utilized.

Grounding.

You shall evaluate the existing grounding systems employed at the UOTS training facility location. You shall design, integrate, and install appropriate grounding system for each system and subsystem of the UOTS.

Lightning Protection.

You shall ensure all installed equipment is protected against lightning damage. (IAW NFPA 780) Electromagnetic Environmental Effects (E3).

You shall determine the criteria and verification method to ensure that the system electronic or electrical hardware configuration of the UOTS is not a source of Electromagnetic Interference (EMI) or a victim of E3 in the intended operational environment in which it is installed or at its operational locations. You shall establish and maintain a process to verify and assure that the system operations functionality is not affected by E3.

Electromagnetic Interference and Compatibility Test and Verification.

You shall test and evaluate the UOTS to ensure they meet the EMI/EMC requirements of PRF-PT-00519. The test efforts shall consist of a logical sequence and appropriate tests for each hardware subsystem within the system design. The EMI/EMC tests shall be conducted with an approved software baseline loaded onto the test units. (DI-EMCS-80201B) Electromagnetic Interference and Compatibility Acceptance.

You shall ensure that all subsystems of the UOTS meet and fulfill the applicable and appropriate portions of the EMI/EMC requirements of PRF-PT-00519 without degradation of performance. (DI-EMCS-80200B) Environmental Test and Verification.

You shall test and evaluate the UOTS to ensure it meets the Environmental requirements of PRF-PT-00519. The test efforts shall consist of a logical sequence and appropriate tests for each hardware subsystem within the system design. (DI-NDTI-80603) Environmental Acceptance.

You shall ensure that all subsystems of the UOTS meet and fulfill the applicable and appropriate portions of the environmental requirements of PRF-PT-00519 without degradation of performance. (DI-NDTI-80809B) Integrated Product and Process Management.

Integrated Product and Process Development (IPPD).

Systems Engineering Design.

You shall use 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.

System Baseline.

You shall define, maintain, and integrate the allocated baseline to meet the requirements of PRF-PT-00519. You shall track the requirements in an automated management tool from requirements development through final acceptance through the last site. (DI-IPSC-81442A) Requirements Traceability.

You shall track and account for all requirements (including derived requirements) through the use of a requirement traceability matrix implemented using an available non-proprietary 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.

Technical Studies.

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.

Technology Insertion.

You shall integrate the latest technological COTS products to enhance the capabilities and reduce the Total Ownership Costs of the UOTS systems. Changes will be submitted and approved IAW Configuration Management (CM) processes.

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 including LT2 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.

Software Design.

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) Software Requirements and Architecture Development and Review.

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 (identify the components and their interfaces) and the traceability between the system components and system requirements.

Software Design and Implementation.

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.

Software Development Test.

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.

Interface Control.

You shall describe the interface boundaries between all hardware and software Configuration Items (CI), 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) 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 (LCC) goals. 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 LCCs 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.

Logistics Analysis.

You shall conduct an analysis after final design and prior to system baseline and installation. This will identify the spares, expendables and consumables, necessary for normal operations and maintenance of system and subsystems. 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 T&E activities. You shall analyze, 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 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-81520) Supportability Analysis.

You shall identify support requirements for the system. This shall include any Associated Support Items of Equipment (ASIOE), projected support costs, risk items and manpower necessary for the normal operation and maintenance of the system performance. . 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):

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

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

1. Maintenance alternatives considered.

1. Analytical method and models used to perform the cost evaluations.

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

(DI-ALSS-81530)

Unique Identification (UID) of Tangible Items.

You shall be knowledgeable of all DoD requirements for uniquely identifying government property and implement a UID 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 UID including embedded subassemblies, components and parts. You shall provide unique item identification, or a DoD recognized UID 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) Specialty Engineering.

Reliability Engineering.

You shall develop, implement and manage a system reliability process satisfying all reliability objectives; and integrate into 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:

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

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

1. Provide essential management information.

1. Evaluate the reliability program’s 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.

Maintainability Engineering.

You shall develop, implement and maintain a process satisfying all maintainability and related objectives; and integrate into 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.

Testability Engineering.

You shall develop, implement and maintain a system process satisfying all testability requirements which is traceable throughout the design process; and integrate into the systems engineering process. 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 the diagnostic capability meets specified requirements using maintainability demonstrations, test program verification, and other demonstration methods. You shall ensure, as T&E of the system progresses, problems presented by new failure modes, test voids, ambiguities, and test tolerance difficulties are recognized and defined. Solutions shall be traceable using diagnostic hardware and software, and technical publication procedures updated. You shall define an approach for the analysis of acceptance T&E results to determine how Built-In Test (BIT) 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:

1. Establishment of sufficient, achievable and auditable diagnostic capability and state-of-the-art testability. This capability shall be built-in and provide off-line test analysis.

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

1. Evaluation of the extent to which the design meets testability requirements.

1. Inclusion of testability in the program review process.

Safety Engineering.

You shall develop and implement tasks and activities to identify, evaluate, and eliminate or control hazards throughout the system life cycle. You shall ensure the safety of the system 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 probability levels, shall be developed for all hazards.

1.1.1.1.1.1 Safety Assessment and Health Hazard Analysis.

You shall analyze the final design and conduct a safety assessment and health hazard analysis. 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) Health Hazard Assessment.

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 (ODS), as listed 29 Code of Federal Regulations (CFR) 1910.1200. The technical data will be provided in a form of a Safety Assessment Report. (DI-SAFT-80106B) Health Hazard Assessment Report (HHAR) Support.

You shall collaborate with the Safety Office of PEO STRI, the UOTS Integrated Project Team and U.S. Army’s Center for Health Promotion and Preventive Medicine (CHPPM) agency to enable PEO STRI to obtain an acceptable HHAR for the system as a whole and all its related subsystems, if needed.

Interoperability.

Live Training Transformation (LT2).

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) Common Training Instrumentation Architecture Program Interface.

You shall work with the CTIA program and representatives and support the Project Manager Training Devices (PM TRADE) 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.

LT2 Product Line Interface and Support.

You shall work with the LT2 program. You shall utilize the LT2 Concept of Opoerations (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.

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 Development 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.

Information Assurance.

You shall develop and maintain an 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.

Assessment.

You shall conduct an assessment of the current system environment and the supporting infrastructure to include network security for security vulnerabilities and weaknesses. You shall support a physical and logical evaluation of the security of the system on a quarterly basis for closed systems, and on a monthly basis for open systems, 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, and provide software patches and a set of recommendations on how to eliminate or mitigate the threats.

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.01 and AR 25-2 for integrating robust security practices. You shall maintain IAVA & STIG compliances throughout the System Development Lifecycle. You shall design the system using NIAP/CCEVS/AAPL products where available.

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.

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 UOTS 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 UOTS 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 UOTS. For the period of performance of this contract, the contractor shall support the government in maintaining the UOTS ATO through:

1. Annual Security Review Annual Contingency Test Annual Security Control Test Information Assurance Vulnerability Alerts and STIG compliances.

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.

DoD Information Assurance Certification and Accreditation Process Support.

You shall provide assistance in the development of the documentation (System Identification Profile (SIP), DIACAP Implementation Plan (DIP), architecture drawings, Information Security Plan (ISP), Continuity of Operation Plan (COOP), and Contingency Plan (CP)) required to achieve accreditation and certification. You shall assist the government during the definition, verification, and validation phases of the C&A processes.

Technical Reviews.

Corps of Engineers Coordination.

You shall attend and participate in the Target Interface Inspection (TII) with the CoE for each of the sites, as appropriate. You shall review and compare the instrumentation infrastructure requirements with the facility infrastructure provided by the CoE. You shall notify the UOTS IPT of findings and deficiencies.

Program Reviews.

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. These documents shall be maintained in the UOTS IDE (paragraph 3.8).

Technical Design Review (TDR).

You shall conduct a 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.

Test Readiness Review (TRR).

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 T&E 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:

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

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

1. New or modified test equipment and facilities and procedure manuals required to accomplish planned T&E, are available and satisfy the test requirements.

1. Operator and Maintenance Manuals are validated

1. System Drawings are validated

1. Validated Inventory Lists of system components

The following documentation shall be reviewed during the TRR:

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

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

1. Requirements changes pending.

1. Design changes since the last design review.

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

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

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

1. Problem areas and their resolution.

At the TRR, you shall provide an acceptance test plan, which consists of a marked-up test procedures checklist, identifying that all devices in the field and the equipment installed at the ROC has been thoroughly tested. In addition, you shall provide a copy of the verification of the system drawings and inventory. (DI-QCIC-80553) Technical Interchange Meetings (TIMs).

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.

DIACAP Implementation Plan Review (DIPR) You shall support a DIPR prior to the DRR for each UOTS system. A DIPR shall address all IA controls defined in AR 25-2 required to field the system IAW the PEO STRI BAM version 5.0. During this meeting, the SIP, DIP, a draft ISP, and updated architecture drawings will be reviewed.

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 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 (TPM) to evaluate the performance of critical technical and management processes and conformance of the evolving products with contract requirements. You shall provide ROMs, site proposals and site execution schedules that reflect planned efforts to satisfy site contractual requirements. (DI-MGMT-81453, DI-MGMT-81650) Integrated Master Plan (IMP).

You shall implement, manage, 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 (CWBS). The contents of the IMP shall be determined through the Integrated Product and Process Management process.

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 contractor provided 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. The individual site schedules provided as part of each site proposal shall be incorporated into the IMS. (DI-MISC-81650, DI-MGMT-81334B).

Finan…

This is the start of the file's text. The full file is on GovTribe.

Other files

File Type Posted
7. UOTS DRAFT Perf Spec.doc.docx DOCX document
8. UOTS DRAFT PWS.doc.docx DOCX document
5. Industry Day Brf 29 June09.pptx.ppt PPT presentation
6. UOTS Industry Day Atendees 29 June.doc.docm DOCM document
4. UOTS Perf Spec —

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

File details come from the government source that posted it. Updated .