STATEMENT OF WORK PEO STRI OMNIBUS CONTRACT II

Transcription

1 STATEMENT OF WORK for the PEO STRI OMNIBUS CONTRACT II PEO-STRI-08-W001 U.S. Army Program Executive Office for Simulation, Training and Instrumentation Research Parkway Orlando, FL i

2 TABLE OF CONTENTS PEO-STRI-08-W SCOPE INTRODUCTION GOALS AND OBJECTIVES BACKGROUND APPLICABLE DOCUMENTS REQUIREMENTS: ENGINEERING: Product Line Engineering: Knowledge Engineering: Systems Engineering: Manufacturing: Hardware and Software Integration: Courseware Development: Quality Assurance: Reliability Engineering Program: Maintainability Engineering Program: Producibility Engineering Program: Hazardous Materials/Environmental Safety Program: Hazardous Material Management: Chemical/Hazardous Materials Usage: Manpower and Personnel Integration (MANPRINT): Technology Insertion: Program and Design Reviews: Logistics Support Development: Instructional Systems Development: Value Engineering: TEST: PROGRAM MANAGEMENT: Integrated Product and Process Development (IPPD): Integrated Master Plan/Integrated Master Schedule (IMP/IMS): Contract Management: Earned Value Management (EVM) System: Risk Management: Associate Contractor Agreements (ACAs): Subcontractor Management: Cost as an Independent Variable (CAIV): SYSTEM SECURITY: Specific Order Security: Disclosure of Information: Interim Contractor Support: Configuration Update Working Group: Surge Support: Re-competition Support Package: Scheduling and Evaluation: Support Centers: MISSION READINESS SUPPORT: TRANSITION TO LIFE CYCLE CONTRACTOR SUPPORT (LCCS): DEPLOYMENT: HORIZONTAL INTEGRATION: INFORMATION ASSURANCE (IA) APPENDIX A1 PRODUCT AREA DOCUMENT ii

3 1.0 Scope: This Statement of Work (SOW) defines the scope of the PEO STRI Omnibus Contract (STOC) II Indefinite Delivery/ Indefinite Quantity Contract (ID/IQC). STOC II will provide PEO STRI with the ability to procure a broad range of Modeling & Simulation (M&S) and Instrumentation solutions in support of Customer training and testing requirements. These solutions will include procurement and/or services support of training and testing simulators, simulations, systems/devices, instrumentation systems, telecommunications systems, experimentation, targets, gaming, advanced simulation concepts, and open architecture, and common part and component solutions. 1.1 Introduction: This SOW defines the general tasks the PEO desires to have performed under the STOC II contracts. The delivery/task orders will define the detailed requirements in the respective Statements of Work or Statements of Objectives (SOO) for each specific order. The PEO envisions the following types of product and/or service support delivery/task orders occurring under the procurement: Equipping actual warfighting equipment, systems and munitions with the capability to execute individual, crew and collective training, testing, experimentation and rehearsal in a specific environment. It includes training/testing/experimentation executed using computer-generated battlefields in simulators with the approximate physical layout of tactical weapons systems and vehicles. Procuring and/or supporting war games, gaming and automated simulations which represent actions of people and systems in a simulation. The PEO identifies these solutions with large-scaled, complex, computer-driven models most often associated with exercises dealing with Battalions, Brigades, Divisions, Corps, Echelons Above Corps and/or their Other Service (e.g., USAF) or Joint Force equivalent. This also includes entity level force simulations and models. Representing military operations using live forces and instrumented weapon systems interacting on training, test and exercise ranges which simulate experiences during actual operational conditions. It includes training/testing or experimentation executed in field conditions using tactical equipment, enhanced by training aids, devices, simulators and simulations (TADSS), test systems, and Tactical Engagement Simulation (TES) to simulate combat conditions. Procuring and/or supporting the systems, subsystems, components or devices, targets or threat simulators which includes, but is not limited to, the sensors which individually/collectively test materiel, non-weapon systems or weapon systems in a developmental/operational testing environment or training exercise. This includes the sensors, telecommunications equipment and other materials that provide the capability to detect, measure, record, transmit and process/analyze information generated during a test or training exercise. 1

4 Developing, integrating, or procuring common components to reduce Total Ownership Cost (TOC) or enhance interoperability. This includes developing interoperability solutions across Modeling and Simulation domains as well as stand-alone or embedded capabilities to interface with or stimulate command and control or battle command systems. 1.2 Goals and Objectives: The STOC II contract goals and objectives are to acquire the capability to perform product and service support related Front-End Analysis (FEA), Design, Development, Fielding and Sustainment functions in support of military training/testing instrumentation, systems, simulations and simulators. The PEO STRI intent is to award contracts to a cadre of best qualified contractors possessing the business practices and technical capabilities which meet (or exceed) requirements in increasing responsiveness and flexibility relative to customer needs. This will include capabilities which are interoperable across training/testing instrumentation systems, simulations and simulators. A PEO STRI goal is to migrate to training and testing composable environments that are created from common components and interoperable systems. 1.3 Background: The PEO STRI mission is to acquire training and testing simulations, simulators, systems and instrumentation products and services to support various military and civilian agencies. Integral to the success of this mission is the ability to compete requirements amongst qualified contractor providers in the most efficient and timely manner possible. Acquisition Reform initiatives have made available avenues intended to increase the efficiency and economy of the acquisition process. One of the central Acquisition Reform initiatives is the creation of Multiple Award Indefinite Delivery Indefinite Quantity contracts that allow for competition of individual delivery/task orders. PEO STRI s objective is to establish a long-term, competitively awarded, contract vehicle which reflects a pre-qualified cadre of contractors at the ID/IQC level. PEO STRI s intent is to then provide each selected Offeror a fair opportunity to be considered for all subsequent delivery/task order level requirements within the scope described above, supporting the breadth and depth of the applicable Warfighter training and testing requirements. This also includes a commitment to develop interoperable and common component solutions which can be applied across a system of systems training/testing environment. 2.0 Applicable Documents: DISR OMB Circular A-130 DoDD DoDR R DoD Manual DoD Information Technology Standards & Profile Registry Management of Federal Information Resources Defense Acquisition Mandatory Procedures for Major Defense Acquisition Programs (MDAPS) and Major Automated Information System (MAIS) Acquisition Programs Acquisition Systems Protection Program 2

5 DoDD DoDD DODD DoD M DoDD DoDD DoDD DODI NAS411 MIL-STD-882 AR 25-2 DoD Information Security Program Security Requirements for Automated Information Systems Security, Intelligence, and Counterintelligence Support to Acquisition Program Protection National Industrial Security Program Operating Manual International Transfer of Technology, Goods, Services, and Munitions Distribution Statements on Technical Documents Withholding Unclassified Technical Data from Public Disclosure Development, Management and Delivery of Distributed Learning Hazardous Materials Management Program Military Standard, System Safety Program Requirements Information Assurance 3.0 Requirements: The requirements defined herein form the basis for all work contractors will perform as part of the delivery/task orders the Government will issue under this procurement. The overarching functional areas required in this SOW include the needs Customers have to conduct front-end analysis, design, development, fielding and sustainment in support of training and testing: systems, instrumentation, targets, threat systems, devices, gaming systems, simulators and simulations and all of the support systems required to operate, maintain and train them. The requirements are applicable for the Product Areas described within Appendix A1. All efforts this SOW describes are applicable to all U.S. Government entities (federal, state and local), selected non-government entities and appropriate/approved foreign entities. In support of Section 803 of Public Law , concerning homeland defense projects, equipment and/or services described within the Statement of Work may be procured in support of both federal, non-federal government, and state or local authorities to procure anti-terrorism services, systems, subsystems and items, provided that a federal account is used to fund the effort. PEO STRI defines the overarching functional areas as follows: Front-End Analysis (FEA): The formal, standardized processes and procedures by which a contractor analyzes a requirement to determine the best conceptual course of action (COA) to satisfy that requirement. It generally consists of a concise problem/requirement statement, gathering of data and making assumptions relevant to the requirement, identification of potential COAs, development and application of evaluation criteria and, ultimately, selection of the most viable COA for the requirement. It may consist of the integration of several supporting analyses, such as cost-benefit or task analyses. Providers may require outside expertise to conduct a competent analysis and, as such, FEA may include the incorporation of teaming partners/subcontractors into the analysis process. 3

6 Design: The formal, standardized processes and procedures by which a contractor transitions a chosen COA into an implementation plan. Design incorporates DoD/Commercial common standards, common architectures and common parts into a comprehensive product and/or service implementation plan. Design integrates and synchronizes products and/or services with existing product and/or service solutions. Design includes integration and synchronization of the resource input from a teaming partner(s) or subcontractor(s) into the final product and/or service implementation plan, as applicable. Design also includes the incorporation of concepts relative to ease of sustainment and cost savings in the final product and/or service and addresses the life cycle requirements of the selected COA. Develop: The formal, standardized processes and procedures by which a contractor transitions a COA product and/or service Design into a deliverable product and/or service. Develop includes the procurement of materials and personnel, building and/or assembling of hardware, software and personnel as well as other resources applicable to the product or service Design. Develop provides for changing a design solution, e.g., in response to evolving Government requirements, a design failure, integration issues or newly emerging technology. Develop integrates products and/or services provided by a teaming partner/subcontractor, if applicable. Develop also includes testing of the product or service, to include teaming partner/subcontractor provided products and/or services, in meeting a given requirement. Field: The formal, standardized processes and procedures by which a contractor delivers a product and/or provides a service solution in terms of quantity, schedule, location, and/or personnel, and integrates the solution into the existing environment(s). Field may include products and/or services provided by a teaming partner/subcontractor. Field includes the enabling of end-users to acquire the skills and knowledge necessary to effectively use the product and/or service. Sustain: The formal, standardized processes and procedures by which a contractor maintains and/or resources a Fielded product and/or service over a specified period of time. Sustain may include products and/or services provided by a teaming partner/subcontractor. Sustain identifies and resolves problems/issues, maintains proper documentation and information, replaces personnel, retains qualified personnel, tracks warranties and spares, and supports on-going training requirements. In the context of these five over-arching functional areas, the following paragraphs delineate the types of specific processes and procedures the Government expects contractors to employ in the execution of delivery/task orders relative to the broad scope of work outlined above. The Government will specify applicable processes and procedures for incorporation at the delivery/task order level. 4

7 3.1 Engineering: The Contractor shall perform the necessary tasks to accomplish a structured engineering approach to the requirements stated in the specific order. The Contractor shall apply the engineering disciplines listed below or any other collaborative engineering discipline as each order requires Product Line Engineering: The Contractor shall perform the necessary tasks to support development or use of established product lines, to include definition, analysis, development of models, development of architectures, and implementation of assets. The Government will address specific requirements for product line development or reuse in each specific delivery order/task order Knowledge Engineering: The Contractor shall perform knowledge acquisition (KA) and knowledge engineering (KE) activities to better scope and define high level requirements. Through performance of KA/KE activities, the Contractor shall document and transform knowledge collected from authoritative sources, to include subject matter experts, into computationally useful products (data and/or algorithms) that support system designers and software engineers. The Government will address specific requirements for knowledge acquisition/ engineering in each specific delivery/task order Systems Engineering: The Contractor shall perform the necessary tasks to evolve the requirements of each specific delivery order/task order into a finished product. The Government will address specific requirements for Government standards and the use of non-government standards in each specific delivery order/task order Front End Analysis: The Contractor shall perform the tasks necessary to identify candidate technical approaches, conduct cost/benefit analysis and determine best technical solutions Requirements Analysis and Traceability: The Contractor shall perform the tasks necessary to define key components, interrelationships and requirements of any item a delivery/task order requires. The Contractor shall establish an automated means to track and account for evolution of requirements throughout the product development. Automated refers to a continuing process or procedure that provides a means for tracking requirements, such as an information management system which provides visibility into the development of a product or service System Design: The Contractor shall perform the tasks necessary to synthesize system designs in response to requirements each specific delivery/task order defines. Where applicable, the Contractor shall direct system design at optimizing total system performance and minimizing the cost of ownership by addressing both the equipment (hardware and software) and the human part of the total system equation. The Contractor shall also design to interoperability standards and protocols as prescribed in each delivery/task order. 5

8 Software Development: The Contractor shall perform software engineering tasks in accordance with approved software development plans and procedures as each specific delivery order/task order requires Hardware Development: The Contractor shall generate and document hardware designs and performance-based product definition data in accordance with the requirements of each specific delivery order/task order Configuration Management: The Contractor shall implement a configuration management program in accordance with the requirements of each specific delivery order/task order System Safety Program: The Contractor shall develop and implement a system safety program to identify and control the hazards of the system. In order to eliminate hazards or reduce the associated risk to a level acceptable to the managing activity (MA), the Contractor shall impose design requirements and management controls aimed at preventing mishaps. To ensure consistent hazard tracking, the Contractor shall use Appendix A of MIL-STD Supportability Engineering: The Contractor shall perform supportability tradeoffs during the systems engineering process by considering the effect design decisions have on life-cycle cost, reliability, maintainability, and availability rates as specified by each specific delivery order/task order Manufacturing: The Contractor shall perform the tasks necessary to fabricate and assemble the components and systems required in each specific delivery order/task order Hardware and Software Integration: The Contractor shall perform the engineering tasks necessary to integrate system hardware and software to meet requirements each specific delivery order/task order defines Courseware Development: The Contractor shall perform courseware development tasks as each specific delivery order/task order requires Quality Assurance: The Contractor shall implement a quality program that meets the requirements of each specific delivery order/task order Reliability Engineering Program: The Contractor shall institute a system reliability program to meet the availability and specific Mean-Time-Between-Failures requirements of each specific delivery order/task order. 6

9 3.1.9 Maintainability Engineering Program: The Contractor shall institute a maintainability program to meet the availability and specific Mean-Time-To-Repair requirements of each specific delivery order/task order Producibility Engineering Program: The Contractor shall institute a producibility engineering program to meet the requirements of each specific delivery order/task order Hazardous Materials/Environmental Safety Program: The Contractor shall institute an environmental occupational health and personnel safety program Hazardous Material Management: The Contractor shall specify the design approach for a clean environment, when appropriate. The Contractor s Hazardous Material Management shall be NAS 411 compliant. To the maximum extent possible, the Contractor shall incorporate Pollution Free Processes into the task s Systems Engineering Approach. The Contractors Hazardous Material Management Program shall reduce or eliminate the use of hazardous material for systems, system component, and associated support items throughout all phases of the system life cycle Chemical/Hazardous Materials Usage: For operations conducted on Government property, the Contractor shall identify chemical and hazardous material usage and status and relay the information to the appropriate Government agency or office with local responsibility for the disposition of hazardous materials and/or to the appropriate Government agency or office with local responsibility for Toxic Release Inventory reporting responsibility. This information shall include the amount of chemical a Contractor has used {by Chemical Abstract Society (CAS) number and common name} and the process in which it used the material Manpower and Personnel Integration (MANPRINT): The Contractor shall establish and maintain a formal Manpower and Personnel Integration (MANPRINT) management program in Key Performance Parameters as each specific delivery order/task order requires Technology Insertion: The Contractor shall perform the necessary tasks to assess and implement timely technology insertions to improve product capabilities, mitigate program risk and reduce total ownership costs. This includes but is not limited to modular reuse, horizontal technical insertion of existing Commercial-Off-The-Shelf (COTS)/ Government-Off- The-Shelf (GOTS) products, and/or other innovative approaches Program and Design Reviews: The Contractor shall conduct program and design reviews and applicable Technical Interchange Meetings (TIM) for the Government and Integrated Product Team (IPT) members as defined in each specific order. 7

10 Logistics Support Development: The Contractor shall perform a supportability analysis to determine the support structure necessary to maintain the system at the availability rate the specific order defines. The Contractor shall determine spares quantity, support equipment, technical documentation and number of maintenance technicians. The Contractor shall develop the support structure and a re-competition support package that meets the current system configuration and includes all the spares, support equipment and technical documentation to maintain the system at the availability rate identified in each specific delivery order Instructional Systems Development: The Contractor shall develop training programs and curricula in accordance with approved training system development plans as each specific delivery order/task order requires Value Engineering: The Contractor shall implement and use a value engineering program employing the value methodology. The Contractor shall conduct multi-disciplined Joint Government value engineering methodology workshops in order to identify and implement areas for program/process improvement. Each delivery order/task order will address specific requirements. 3.2 Test: The Contractor shall establish a test program verifying it has met the requirements the specific order has defined. The Contractor shall document all facets of the test program in a Test Evaluation Master Plan (TEMP), which shall govern the test planning process and the actual conduct of testing. The test program shall include milestones integrated throughout the development process and define entry and exit criteria in the Integrated Master Plan (IMP) and as each specific delivery order/task order specifies. 3.3 Program Management: The Contractor shall establish and maintain an integrated program management system, which will plan, direct, integrate and control the administrative, management, technical, logistical, financial, production and support functions of each specific order. The Contractor shall maintain procedures to respond to requirements of Request for Proposals (RFPs) and delivery/task order modifications. The Contractor shall manage work efforts to optimize total system performance; promote interoperability and common solutions; and minimize total ownership cost. The Contractor shall adopt a total systems and system of systems approach to product support and structure system design, testing, support planning, resourcing, post-fielding evaluation and operational support to give full consideration to all aspects of system support. The subparagraphs below identify the required characteristics of an integrated program management system Integrated Product and Process Development (IPPD): The Contractor shall establish and maintain a process for IPPD and participate in joint Government/Contractor Integrated Product Teams (IPT) in a Performance-Based Business Environment to manage and integrate all tasks, activities and data each specific 8

11 order requires. The Contractor shall facilitate Government insight into contract activities and establish working relationships with Government personnel that will enable continuing insight into all appropriate contract activities. The Contractor shall provide real-time, reliable and user-friendly electronic remote access to all appropriate data produced under the contract to enable periodically review of contract status and demonstrate readiness to complete significant events. The Contractor shall make available to Government members all technical, cost and schedule data for each specific order of the order IPT. The Contractor shall maintain processes that facilitate completion of delivery order/task orders Integrated Master Plan/Integrated Master Schedule (IMP/IMS): The Contractor shall develop an IMP and an IMS if the specific order so requires. The Contractor shall manage to and maintain the Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) it has developed for each specific order, including appropriate program milestones with corresponding entrance and exit criteria. The IMP and IMS shall include a detailed account of all tasks necessary to accomplish the goals and objectives of each specific delivery order/task order Contract Management: The Contractor shall maintain all contract data passed between Government and industry in a conformed copy format. PEO STRI will develop and maintain a master database of the conformed contract which shall include all contract modifications and subsequent Orders and Order modifications Earned Value Management (EVM) System: The Contractor shall use an Earned Value Management System as each specific order defines Risk Management: The Contractor shall implement an integrated risk management system with risk planning, identification, assessment, mitigation and monitoring functions to improve technical, cost and schedule performance for each specific delivery order/task order Associate Contractor Agreements (ACAs): The Contractor shall maintain the capability to enter into Associate Contractor Agreements (ACAs) for exchanging data, accessing and using third party software and equipment, receiving technical support, working interface issues, transitioning to Life Cycle Contractor Support (LCCS) and/or agreeing on equipment use and time, as each specific delivery order/task order requires. ACAs shall be maintained to achieve interoperability and common component goals, as applicable Subcontractor Management: The Contractor shall maintain the capability to manage subcontractors in accordance with the Subcontractor Management Plan. The Contractor shall integrate subcontractors into program Integrated Product Teams and program management and tracking systems such as management information systems, EVM system, etc. The Contractor shall ensure the 9

12 requirements of this contract and subsequent orders are consistently applied to all subcontracts and associate contracts Cost as an Independent Variable (CAIV): The Contractor shall participate on joint Government-Contractor Cost Performance IPTs as each specific order defines to discuss tradeoff options for implementing CAIV concepts and guidance. 3.4 System Security: The Contractor shall ensure integration of security program requirements into all program areas of this contract as DoD Directive requires Specific Order Security: The Contractor shall comply with all security requirements as Government identifies in the Department of Defense Contract Security Classification Specification (DD Form 254) which you shall execute in accordance with DoD M, and DoD Directive Each specific delivery order/task order will identify any additional program security requirements Disclosure of Information: The Contractor shall comply with the protection standards and guidance described in DoD Manual , Chapter 5, to prevent foreign intelligence collection and/or the unauthorized disclosure of information governed by the International Traffic in Arms Regulation (ITAR) and/or the Export Administration Regulation (EAR) during the acquisition process. 3.5 Interim Contractor Support: The Contractor shall perform the tasks necessary to operate, maintain and support the fielded systems as each specific task order defines. The Contractor shall provide all supplies, services and system/configuration management necessary to perform Interim Contractor Support (ICS) and Total Contractor Training (TCT) Configuration Update Working Group: The Contractor shall support the configuration update working group as each specific delivery order/task order defines Surge Support: The Contractor logistics support shall include Surge in ICS Over and Above Repair of Government Furnished Property, logistics support package maintenance, system or device relocation, tear down, packaging, shipment, storage and/or disposal Re-competition Support Package: The Contractor shall manage and maintain the Re-competition Support Package (RSP) at the current configuration level. The RSP includes all the spares, support equipment and 10

13 technical documentation necessary to maintain the system at the availability rate the individual order specifies. ICS tasks include spares replenishment and the update of technical documentation to reflect changes to the system Scheduling and Evaluation: The Contractor shall schedule equipment use and students, accomplish student tracking/management and evaluate training system effectiveness as each specific delivery order/task order defines Support Centers: The Contractor shall develop, manage and/or operate the support centers as each specific order defines. Tasks may include but are not limited to configuration management and directed modifications to the training systems hardware, software, courseware, and databases. 3.6 Mission Readiness Support: The Contractor shall provide services, tools, and capabilities needed to sustain mission readiness and support mission training, test, demonstration and execution as required by each specific delivery/task order. 3.7 Transition to Life Cycle Contractor Support (LCCS): The Contractor shall provide the re-competition support package and transitional training to the Life Cycle Contractor Support (LCCS) contractor. The Contractor shall conduct a transition period during which support will transition to the LCCS contract. 3.8 Deployment: The Contractor shall support the worldwide deployment of systems in the quantities and configurations each specific order defines. 3.9 Horizontal Integration: The Contractor shall seek, recommend, develop and synchronize horizontal integration solutions with focus toward interoperability and adoption of standards and product lines. These efforts will include technical solutions and information sharing to leverage Contractor initiatives across all delivery/task orders issued under this contract. This includes assessing partnership opportunities for similar product requirements, the integration of technology development and the pursuit of acquisition solutions. Each delivery/task order will address specific requirements Information Assurance (IA) The Contractor shall develop and maintain an information assurance process to guide management and design actions, document decisions, specify and track Information Assurance (IA) requirements, document certification efforts, identify possible solutions, and maintain operational systems security. The Contractor shall establish or adopt standards for managing IA requirements and capabilities and an information system 11

14 security engineering approach that emphasizes purposeful design or configuration of security solutions. 12

15 Appendix A1 Product Area Description Document 1) Individual, Crew, Combined Arms Trainers; Individual, Crew, Combined Arms Simulators; Test Systems. Any training or testing simulator/device used to train or test: an individual, crew or multiple crews to operate or employ an operational system or a number of dissimilar operational systems. 2) Maintenance and Part Task Trainers; Maintenance and Part Task Simulators Any device or simulator used to train personnel in the performance of subsystem operation or maintenance on a particular system, subsystem or type of equipment. 3) Advanced Distributed Learning (ADL) Interactive and adaptive training and job aiding that leverages the full power of computer, information, and communication technologies through the use of common standards. 4) Ranges and Installation Instrumentation Systems Any system, including, but not limited to the telecommunications sub-system, used to transmit, receive, and collect any data at any facility or area for the purposes of: training, testing, or operation of a weapon or system; live firing of a weapon/weapons; maneuvering of operational equipment/units; or force on force operational training or testing. 5) Simulations and Simulation Systems Simulations include the stimulation and simulation of command and battle staff processes in both analog and digital systems in a synthetic environment, and engineering and scientific simulations. The simulations operate in real time to non-real time (faster and slower) depending on the specific applications, and represent systems at the aggregate, entity and sub-entity level and all levels of command. The simulations may range from low to high fidelity and can be used to support network simulators by providing simulated friendly and opposing forces. These simulations may include the requirements of the ACR, RDA, and TEMO as well as the requirements of other services and Joint simulations in the synthetic environment. 6) Tactical Engagement Simulator Systems Any system of people-safe transmitters, receivers, sensors and support equipment used to allow force-on-force training or testing of individuals, equipment or units of individuals and equipment. 13

16 7) Embedded Training; Embedded Testing PEO-STRI-08-W001 Hardware/ Software and software simulations hosted in an operational system or piece of equipment that allow training or testing on that equipment with or without the actual operation of the equipment or system. 8) Advanced Concepts Any innovative application of existing or emerging technology, state-of-the-art tool or advanced concept system. Advanced Concepts include the planning and implementation of simulation based demonstrations, experiments, and exercises, and other advanced concepts, analysis, and applications as they emerge. 9) Threat Representations Any live, virtual or constructive representation utilized to simulate or represent the multi-spectral and functional effects of an actual foreign or hostile platform and/or capability intended to engage and/or cause harm to friendly forces and/or weapons systems. Includes the validation/accreditation of these representations, as defined under AR ) Threat Computer Network Operations An adversaries use of Computer Network Attack (CNA), Computer Network Exploitation (CNE), and Computer Network Defense (CND) tools and techniques to stress Friendly system(s) performance during testing, as part of a simulated real-world environment. Includes pre-event and active reconnaissance, enumeration, and exploitation of vulnerabilities to create a desired end result/effect. 11) Threat Materiel Any foreign system or component thereof, procured in support of Foreign Materiel Sales, Test and Evaluation, or training. Includes both Ground and Aviation Systems. 12) Security Systems Any system or device used to encrypt or to implement multiple levels of security in a simulation system used by the Department of Defense for testing military systems or training US Armed Forces. 13) Game Applications and Technology Game applications and technology leverage solutions from both industry and government to support current and future Soldier, leader, collective, and mission rehearsal training. The application may be a game that provides training or practice for a particular skill or specific technology which could include game hardware, infrastructure, licenses, engines, game assets, or other technologies to support a particular game application. May include development and maintenance of training support packages, web portal services and post deployment game engine and software applications. 14

17 14) Persistent Interoperable Simulation Capabilities Any set of interoperable simulators or simulations integrated and configuration managed to provide a persistent training capability as a linked set of systems. 15) Common Components Reuse of existing capability at the component level or development/production of a capability that is intended to support the current application plus future use in other systems where a similar capability is needed. 15