Training Support Management Tool (TSMT) PerformancE work

DISTRIBUTION A: APPROVED FOR PUBLIC RELEASE // DISTRIBUTION IS UNLIMITED

Performance Work Statement (PWS)

For

Synthetic Training Environment – Information System

(STE-IS)

TRAINING SIMULATION SOFTWARE / TRAINING

MANAGEMENT TOOL (TSS / TMT)

11 December 2020

Version 1.2

Prepared by

U.S. Army PEO for Simulation, Training and Instrumentation

(PEO STRI)

12211 Science Drive

Orlando, FL 32826-3276



i


This page intentionally left blank.


ii


Revision Level

Document Date Summary of Change Pages Affected

1.0 16 October 2020 Initial release of document

All

1.1 13 November 2020 1. Updated distribution Astatement

2. Reformatted document3. Include MBSE

Statement4. Revised text5. Updated Table 3-2 for

Environmental Testing6. Updated Industrial

Security7. Revised text8. Added IMS Template to

Appendix E9. Updated IMS

Deliverable10. Added Appendix H

Composite PDF FileInstructions

11. Updated ProductSupport Deliverables

12. Updated ProductSupport PerformanceRequirements UpdatedAppendix D File.

13. Removed CostDeliverables Section

14. Removed Appendix FCost Deliverables

15. Updated Engineeringand ManagementDeliverables Sections

16. Removed Appendix EIMS Template

17. Revised text

1. All2. All3. Pg. 9, Sec 3.54. Pg. 33 Sec

3.9.9.9; pg. 44,3.11.1

5. Pg. 23, Table3-2

6. Pg. 51, Sec3.13.1

7. Pgs. 3, 9,308. Pgs. E-19. Pg. 1210. Pgs. H-1/211. Section 3.8.312. Section 3.12

Pg. D-113. Section 3.8.514. Cost

DeliverablesAppendix FCostDeliverables

15. Sections 3.8.1and 3.8.2

16. Appendix E17. Pgs. ii, 1, 2,

10, 14, 15, 16,17, 20, 34, 39,40, 41, 44, 45

1.2 11 December 2020 1. UpdatedProduct/RequirementManager to FunctionalManager and Product

1. All2. All3. Pg. 344. Pg. 385. Pg. 8


iii


Owner to Functional Owner

2. Changed ACM to TPO 3. Updated Platform One

requirements 4. Updated requirement

3.12.2.1 5. Updated Table 3-1 6. Updated Table 3-3 7. Added Understanding

OE Variables Appendix 8. Updated DEEP

requirements 9. Updated Integration

requirements

6. Pg. 18 7. Pg. G-1 8. Pg. 23 9. Pgs. 10 – 11


iv


Table of Contents

Overview .................................................................................................................. 1

1.1 Problem Statement ............................................................................................ 1

1.2 Synthetic Training Environment Overview ......................................................... 1

1.3 Training Simulation Software / Training Management Tool Overview................ 3

1.3.1 TSS/TMT Scope ........................................................................................... 3

1.3.2 Capability Overview ...................................................................................... 4

1.3.2.1 TSS/TMT ............................................................................................... 4

1.3.2.1 TMT ....................................................................................................... 4

Planning Phase ................................................................................ 4

Prepare Phase ................................................................................. 4

Execute Phase ................................................................................. 5

Assess Phase ................................................................................... 5

1.3.2.2 TSS ........................................................................................................ 5

Acquisition Pathway and Objectives .................................................................... 5

2.1 Software Acquisition Pathway ............................................................................ 5

2.2 Objective ............................................................................................................ 6

Requirements .......................................................................................................... 7

3.1 Program Management ....................................................................................... 7

3.2 Associate Vendor Agreements .......................................................................... 7

3.3 Communication .................................................................................................. 7

3.4 Reviews ............................................................................................................. 8

3.5 System Engineering ........................................................................................... 8

3.6 Configuration Management ................................................................................ 9

3.6.1 Configuration Identification ........................................................................... 9

3.6.2 Configuration Control .................................................................................. 10

3.6.3 Configuration Status Accounting ................................................................ 10

3.7 Integration ........................................................................................................ 10

3.8 Deliverables ..................................................................................................... 11

3.8.1 Management Deliverables .......................................................................... 11

3.8.2 Engineering Deliverables ............................................................................ 12

3.8.3 Product Support Deliverables ..................................................................... 15

3.8.4 TSS/TMT Hardware Deliverables ............................................................... 18


v


3.9 System Requirements ...................................................................................... 19

3.9.1 General ....................................................................................................... 22

3.9.2 Architecture ................................................................................................ 22

3.9.3 Point of Need .............................................................................................. 24

3.9.3.1 Point of Need Conditions ..................................................................... 24

3.9.3.2 Network ............................................................................................... 25

3.9.3.3 Cloud ................................................................................................... 26

3.9.3.4 Multi-level Security ............................................................................... 26

3.9.4 TSS/TMT Hardware .................................................................................... 26

3.10 Agile Process ................................................................................................... 27

3.10.1 General ....................................................................................................... 27

3.10.2 Agile Ceremonies ....................................................................................... 28

3.10.3 Agile Metrics ............................................................................................... 29

3.10.4 Roadmap .................................................................................................... 31

3.10.5 DevSecOps ................................................................................................ 32

3.11 Testing ............................................................................................................. 35

3.11.1 Incremental Government Testing ............................................................... 35

3.11.2 Integration Environment .............................................................................. 36

3.11.3 Development Testing .................................................................................. 37

3.11.4 Cybersecurity Tests and Events ................................................................. 37

3.12 Product Support ............................................................................................... 38

3.12.1 General ....................................................................................................... 38

3.12.2 Interim Contractor Support ......................................................................... 39

3.12.3 Maintenance Planning/Concept .................................................................. 39

3.12.4 Warranty ..................................................................................................... 39

3.12.5 Technical Support Documentation .............................................................. 39

3.12.6 Training ....................................................................................................... 40

3.12.7 Item Unique Identification ........................................................................... 40

3.12.8 System Delivery .......................................................................................... 40

3.13 Security ............................................................................................................ 41

3.13.1 Industrial Security ....................................................................................... 41

3.13.2 Cybersecurity .............................................................................................. 42

3.13.2.1 Cyber Survivability ............................................................................... 42

3.13.2.2 Risk Management Framework ............................................................. 42


vi


3.13.2.3 Cross Domain Solution Authorization (CDSA) ..................................... 45

3.13.2.4 Cybersecurity Incident Reporting ......................................................... 45

3.13.2.5 Cybersecurity Training ......................................................................... 45

3.14 Safety and Health ............................................................................................ 46

3.14.1 Safety ......................................................................................................... 46

3.14.2 Health ......................................................................................................... 46

References ............................................................................................................ 47

Appendix A Capability Descriptions ....................................................................... A-1

A.1 One World Terrain ..........................................................................................A-1

A.2 Reconfigurable Virtual Collective Trainer ........................................................A-1

A.3 Live Virtual Constructive Integrating Architecture ...........................................A-2

A.4 Mission Command Information Systems .........................................................A-2

A.5 Avionics Software Emulation ..........................................................................A-3

A.6 Common Software Library ..............................................................................A-3

A.7 Army Training Information System ..................................................................A-3

A.8 Soldier Virtual Trainer .....................................................................................A-4

A.9 Integrated Visual Augmentation System / Squad Immersive Virtual Trainer ............................................................................................................A-4

A.10 STE Live Training System ..............................................................................A-4

Appendix B Objective Values .................................................................................. B-1

Appendix C Capability Roadmap ............................................................................ C-1

Appendix D Notional MVP/MVCR/Release Plan ..................................................... D-1

Appendix E Cybersecurity ....................................................................................... E-1

E.1 DoD CDS Connection Process Diagram .........................................................E-1

Appendix F Composite PDF File Instructions ........................................................ F-1

Appendix G Understanding Operational Environment Variables ......................... G-1

Appendix H Acronyms and Glossary ...................................................................... H-1

H.1 Acronyms ....................................................................................................... H-1

H.2 Glossary ......................................................................................................... H-6


vii


List of Figures

Figure 1-1. STE OV-1. ..................................................................................................... 1

Figure 1-2. Synthetic Training Environment. ................................................................... 3

Figure 1-3. TMT Interaction. ............................................................................................ 4

Figure E-1. DoD CDS Connection Process Diagram. ..................................................E-1

Figure F-1. Displaying Attachment Pane. ..................................................................... F-1

Figure F-2. Attachment Pane Displayed. ...................................................................... F-1

Figure F-3. Save Embedded Attachment. .................................................................... F-2

List of Tables

Table 3-1. Recurring Government Meetings. .................................................................. 8

Table 3-2. Development / User Feedback Locations. ................................................... 18

Table 3-3. Fielding Locations. ....................................................................................... 18

Table B-1. Objective Values. ........................................................................................B-1

Table G-1. Acronyms. ................................................................................................. H-1

Table G-2. Glossary. ................................................................................................... H-6


1


Overview

1.1 Problem Statement

The Army currently employs a collection of outdated, cyber-vulnerable, and inefficient live, virtual, constructive, gaming (LVCG) collective training systems that form the Integrated Training Environment (ITE) which is not available at the Point of Need (PoN). These systems do not replicate the complex challenges of the current and future Operational Environment (OE) nor are they Agile enough to allow Warfighters to train multiple iterations prior to mastering training in the live training environment. As we set the foundation for a Multi-Domain Operations (MDO) capable force in 2028, these critical capability gaps degrade Warfighter training readiness and performance placing our Nation’s defense at risk.

1.2 Synthetic Training Environment Overview

The Army’s future training capability is the Synthetic Training Environment (STE). The STE will be a single, interconnected training system that provides a training environment, in which units from Soldier/Squad through Army Service Component Command (ASCC) conduct collective training, see Figure 1-1 below.

Figure 1-1. STE OV-1.

The STE is envisioned to converge the LVCG environments as one complete training capability. This training capability will enable Army units and leaders to conduct realistic multi-echelon / multi-domain combined arms maneuver and mission command training, increasing proficiency through repetition. This allows units to enter collective level


2


training in the live environment at a much higher level of proficiency. The STE will deliver collective training, accessible at the PoN in the operational, self-development and institutional training domains. The STE is an essential component for the Army to fully realize the Standard of Training Proficiency (STP) required and levels of proficiency.

The STE must have the ability to change with technology, allowing for the replication/representation of current and future force structure, weapons effects, warfighting functions, Joint, Interagency, and Multinational (JIM) capabilities, human interaction, dense urban environment and near-peer threat capabilities. The STE will be capable of training units across the full range of Unified Land Operations (ULO) in multiple domains (Air, Land, Maritime, Cyber, and Space).

The STE provides a synthetic environment to represent and enable rapid generation of the OE. Scalable immersive collective trainers provide the commander with multiple training capability options to train operational tasks at the PoN with around-the-clock accessibility. The STE operates in connected and disconnected modes (for training under limited or degraded network conditions) and is embedded within the Common Operating Environment (COE). The STE leverages the Army Network (enterprise and tactical) to either host or deliver capabilities and provides intuitive, composable applications and services that enable embedded training with mission command workstations and select platforms. Future Live training systems will interface with the STE to incorporate instrumentation, ranges, targets, and ammunition into the synthetic environment. Next Generation Constructive will expand training of large-scale Brigade Combat Team (BCT) through ASCC. The integrated STE system consists of three foundational capabilities that are each a separate other transaction authority (OTA) effort:

• Training Simulation Software / Training Management Tool (TSS/TMT) that consists of the Training Simulation Software (TSS), Training Management Tool (TMT), and hardware.

• Reconfigurable Virtual Collective Trainer(s) (RVCT(s)).

• One World Terrain (OWT).

The STE delivers software, application(s) and services that will enable the RVCT and other training capabilities. The STE will enable multi-level security through a cross domain solution (CDS). The STE architecture and design enables and supports interoperability with existing training systems (Live, Virtual, Constructive - Integrating Architecture [LVC-IA], Joint Land Component Constructive Training Capability [JLCCTC], Homestation Instrumentation Training System [HITS]); and future training systems Soldier Virtual Trainer (SVT), the embedded Integrated Visual Augmentation System (IVAS) with Squad Immersive Virtual Trainer (SiVT), future Next Generation Constructive (NGC), Synthetic Training Environment - Live Training System (STE-LTS) and operational capabilities.

TSS/TMT is planning to utilize the Department of Defense (DoD) Software Acquisition Pathway (SAP) as defined by DoDI 5000.87 Operation of the Software Acquisition Pathway. In accordance with this pathway, the delivery of TSS/TMT capability is defined in terms of Minimum Viable Products (MVP), an initial Minimum Viable Capability Release (MVCR), and annual software releases after initial MVCR.


3


1.3 Training Simulation Software / Training Management Tool Overview

1.3.1 TSS/TMT Scope

This Performance Work Statement (PWS) defines the scope for providing the integrated TSS/TMT solution identified in Figure 1-2 by the red outlined box. The scope is a Brigade and Below collective training capability. This capability includes Soldier/Squad to BCT virtual and a Brigade and below constructive staff training capability. The vendor shall design and build the TSS and TMT software, and provide TSS/TMT Hardware.

Figure 1-2. Synthetic Training Environment.

The TSS/TMT solution will use OWT products and integrate with RVCT as a cohesive STE system. The vendor will need to monitor, collaborate, and integrate with OWT, RVCT, SVT, IVAS-SiVT, and interfaces to Mission Command Information Systems (MCIS) (see full list of MCIS in the Technical Data Package [TDP] Appendix F Systems Requirements Document [SRD]), Avionics Software Emulation [AvSE], Common Software Library [CSL], authoritative data sources (see TDP Appendix A and B, Authoritative Data Sources [Threshold and Objective] for additional information), and LVC-IA. This PWS will refer to the set of vendors in the preceding sentence as the STE system capability and interface vendors. Descriptions of these capabilities (e.g., OWT, RVCT) are in Appendix A Capability Descriptions.

The Brigade and Above capability is outside the scope of this OTA however, it and other objective values are identified in Appendix B Objective Values to provide a holistic STE vision. The MVP, MVCR, and subsequent software releases must not preclude achieving the Objective Values and scalability up to ASCC in the future.

The TSS/TMT system bi-directionally communicates with MCIS. The TSS/TMT system interfaces with LVC-IA to incorporate HITS, JLCCTC and Intelligence Electronic Warfare Tactical Proficiency Trainer (IEWTPT) into an exercise.


4


1.3.2 Capability Overview

1.3.2.1 TSS/TMT

The TSS/TMT is the “core” simulation software and hardware that provides a common

synthetic environment, the exercise design and control tool, and data manager for STE

collective training.

Figure 1-3. TMT Interaction.

1.3.2.1 TMT

TMT is the single Army user interface for exercise design, and execution control used at all echelons to plan, prepare, execute, and assess multi-echelon collective training. Figure 1-3 depicts TMT, the data manager for TSS/TMT.

Planning Phase

TMT enables Commanders and Leaders at all echelons to design exercises and scenarios to meet training objectives. TMT uses authoritative sources to ensure realism by representing force structure and the OE as closely possible.

Prepare Phase

TMT performs the orchestration, provisioning, scheduling, and deployment of infrastructure, training, and simulation resources identified in the plan phase. TMT provides OWT terrain, parametric data, force structure and equipment, 3D moving models, behaviors, OE information, and other data required for simulator/simulation initialization.


5


Execute Phase

TMT exercise control (EXCON) monitors, collects, facilitates runtime assessments and interventions, and stores all simulation data while providing Commanders and Training Managers near real-time information. The TMT EXCON enables in progress scenario changes to achieve training objectives and to tailor the experience to the training audience level of proficiency.

Assess Phase

TMT automates nomination of significant activities (SIGACTs) and development of multi-media After-Action Review (AAR) as an initial baseline for training managers and commanders review so they can provide feedback to the training units. TMT supports Force Readiness measures and reporting across the collective training spectrum within the Sustainable Readiness Model and Standards for Training Proficiency goals.

1.3.2.2 TSS

The TSS is the STE ‘core’ simulation engine that provides a synthetic environment to enable collective training from Soldier/Squad through BCT across the Fires, Movement and Maneuver, and Mission Command Warfighting Functions (WfF) and supporting the Sustainment, Protection, and Intelligence WfFs. TSS ensures fair fight adjudication for interactions in the STE system. The TSS synthetic environment is delivered over the network to RVCT, MCIS, and other interfaces.

The TSS provides computer generated forces (CGF) of BLUEFOR, OPFOR, civilians, ground vehicles, and air platforms. The TSS provides a functional virtual representation of RVCT platforms and provides the simulation software core for RVCT platforms. For example, the TSS renders the inside view of an Apache helicopter, visually displaying the interior of the cockpit with all the functional displays and switches/interfaces needed for collective training. TSS also renders the out-the-window views that the pilot and copilot see when flying through the synthetic environment as well as models or represents all RVCT platform performance, weapons, sensors, targeting, communications, and mission command subsystems.

Acquisition Pathway and Objectives

2.1 Software Acquisition Pathway

The TSS/TMT will use the SAP. This pathway facilitates rapid and iterative delivery of software capability to the user. The SAP employs modern, Agile, Development Security Operations (DevSecOps) software development practices. This allows delivery of secured working software rapidly and iteratively to meet the highest priority user needs. SAP uses automated tools for development, integration, testing, deployment/delivery, and certification to iteratively update software capabilities.

Appendix C Capability Roadmap contains the Government’s initial product roadmap. Appendix D Notional MVP/MVCR/Release Plan provides a notional MVP/MVCR/Release plan. The Government’s expectation is that the vendor will utilize the initial capability roadmap, the notional release plan and the vendor’s technical approach to develop a revised capability roadmap, and an MVP/MVCR/Release plan


6


that meets or exceeds the requirements of the initial backlog as defined by the SRD. The Government’s expectation for initial MVCR is defined as:

• Delivery of the highest echelon trainable capability, across the broadest number of training uses, focused on identified Combine Arms Training Strategy (CATS) tasks, the vendor can deliver in accordance with MVP1 (3 months after OT award) and subsequent required system test and VV&A timelines.

• Enables the training audience to plan, prepare, execute, and assess (PPEA) collective training.

• MVCR verification, validation, and accreditation process complete.

• Meets Cybersecurity requirements.

• Fielding to Fort Hood is complete.

• New Equipment Training (NET) at Fort Hood is complete.

• All contractor requirements for TSS/TMT operations and support are in place and ready to support unit training at Fort Hood.

2.2 Objective

The TSS/TMT objective is to provide a Soldier/Squad through Brigade collective training capability with increased capability for Commanders / Soldiers to train and closes the ITE limitations without creating new gaps. (i.e., Close Combat Tactical Trainer [CCTT]; Aviation Combined Arms Tactical Trainer [AVCATT]; and Games for Training [GFT] and a Brigade and below constructive staff and Commander training capability). The STE system enables the Unit/Staff to train offense, defense, and stability support operations realized through the CATS to set the foundation for an MDO capable force. Some of the collective training task sets are provided in the TDP Appendix C Collective Training Task Sets and training tasks in the TDP Appendix D Collective Training Tasks for additional collective task information.

TSS/TMT is integrated with the OWT and RVCT to achieve a holistic STE capability. The intent of the integrated STE system is to provide value to the end user with each MVP and MVCR that enables units to conduct their doctrinal collective training. Subsequent STE system releases continue to improve the collective training capability (higher echelon, new functionality, etc.). Program Increments, MVP/MVCR/subsequent software releases continue to build on the capabilities in the previous gate.

A successful TSS/TMT system provides the features identified in the TSS/TMT product roadmap. The product roadmap is a series of incremental capability deliveries that provide a working / functional training capability for the user to provide feedback. In addition, Solider Touchpoints will be conducted on an integrated solution (RVCT with TSS/TMT and OWT software). Soldier Touchpoints will be conducted with an operational unit (Forces Command [FORSCOM], Army National Guard [ARNG], and Office of the Chief Army Reserve [OCAR] coupled with the Training and Doctrine Command (TRADOC) Proponent Office [TPO], Cross Functional Team [CFT] and Center of Excellence [CoE] Subject Matter Experts [SMEs]). A successful TSS/TMT system provides an entity level simulation that provides virtual, gaming, and constructive collective training, training to soldiers, squads, platoons, companies, battalions, and brigades. It is also interoperable with LVC-IA to enable interoperability with HITS, JLCCTC and IEWTPT (IEWTPT interoperability is through JLCCTC and


7


LVC-IA); and bi-directionally communicates with RVCT, SVT, IVAS-SiVT, and operational capabilities (e.g., MCIS, AvSE, CSL, air, and ground platforms) enabling Commanders and units to achieve their collective training objectives at the PoN.

The Government will evaluate the technical feasibility and military utility of the TSS/TMT solution as the foundation for the STE. The end-state of the TSS/TMT system is the creation and successful implementation of a modular open system approach that delivers the foundational capabilities in support of the holistic STE vision.

Requirements

The requirements defined herein form the basis for all work that the vendor shall perform as part of the agreement the Government will issue under the TSS/TMT OTA award for the design, development, integration, testing, delivery, and product support of TSS/TMT.

3.1 Program Management

The vendor shall accomplish all planning, execution, risk management, reporting and related program management activities to ensure that the technical, schedule, and financial requirements of this PWS are accomplished in accordance with (IAW) the Government approved product roadmap. Program Management documentation shall include an integrated master plan and monthly program management metrics, technical, financial, and schedule status.

3.1.1 The vendor shall provide a set of program management metrics for the Government to approve.

3.1.2 The vendor shall provide and brief monthly program management metrics to the Government and when requested by the Government.

3.2 Associate Vendor Agreements

Associate Vendor Agreements (AVA) are the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of TSS/TMT. AVAs ensure the greatest degree of cooperation for the development of the program to meet the terms of the efforts.

3.2.1 The vendor shall establish associate vendor agreements and collaborate with STE vendors.

3.2.2 The vendor AVA shall identify potential conflicts between relevant Government contracts, agreements, and the AVA; the agreement shall also include agreements on protection of proprietary data and restrictions on employees.

3.2.3 The vendor shall notify the Government of another vendor’s inability to agree to terms that impact the TSS/TMT vendor’s ability to meet requirements.

3.2.4 The vendor shall collaborate with STE vendors to develop the data model.

3.2.5 The vendor shall collaborate with STE vendors to develop Application. Programming Interfaces (APIs) and Interface Control Documents (ICDs).

3.3 Communication


8


The STE requires the coordination of multiple OTA vendors. The core effort of STE is the TSS/TMT OTA. The TSS/TMT OTA vendor is in the best position to understand the interdependencies between the supporting OWT and RVCT OTAs.

3.3.1 The vendor shall establish and maintain regular communication with the Government team (both formal and informal) so that the Government can identify, assess, and resolve deviations in a timely manner.

3.3.2 The vendor shall provide technical and programmatic project status to the Government during status meetings.

3.3.3 The vendor shall participate in recurring meetings as directed by the Government (see Table 3-1).

Table 3-1. Recurring Government Meetings.

Meeting Location Host Frequency

Architecture Synchronization TBD Government Weekly

Functional Manager Synchronization TBD Government Daily

Scrum of Scrums TBD Government Weekly

Pre-Program Increment Planning Session TBD Government TBD

Cybersecurity/CDS System Team Synchronization TBD Government Weekly

Data Management System Team TBD Government TBD

DevSecOps System Team Synchronization TBD Government Weekly

Integration System Team Synchronization TBD Government Weekly

Logistics/Product Support System Team Synchronization TBD Government Weekly

Network/Cloud System Team Synchronization TBD Government Weekly

OWT Integration System Team Synchronization TBD Government Weekly

RVCT Integration System Team Synchronization TBD Government Weekly

Science and Technology Integration System Team TBD Government Monthly

SiVT Integration System Team Synchronization TBD Government Monthly

Testing System Team Synchronization TBD Government Weekly

Others as directed by the Government TBD Government TBD

3.4 Reviews

3.4.1 The vendor shall host and conduct technical interchange meetings (TIM) and test and assessment reviews to inform Government approval of the product design at least once prior to each program increment, MVP, the MVCR, and subsequent software releases and as requested by the Government.

3.4.2 The vendor shall summarize the TIM and test and assessment reviews discussions, action items, risks, dependencies, and issues and submit to the Government not later than (NLT) 5 calendar days after the event and manage the action items list until all items are accepted by the Government in accordance with the deliverables (3.8.1.1).

3.5 System Engineering

The vendor uses an Agile system engineering process that is consistent with the SAP as well as the Digital Engineering, Model Based Systems Engineering (MBSE), and


9


DevSecOps environments to plan, design, develop, incorporate, test, and deliver STE system of systems capabilities.

3.5.1 The vendor shall identify risks, issues, and mitigating actions.

3.5.2 The vendor shall deliver a requirements traceability/verification matrix that traces requirements from the STE Information System Abbreviated – Capability Development Document (A-CDD) through the PWS, System Requirements Document (SRD), System/Sub System Specification (SSS), Software Requirements Specification (SRS) and test cases to the delivered products.

3.5.3 The vendor shall support Government coordination across efforts performing the managerial and technical systems engineering processes.

3.5.4 The vendor shall utilize the Government provided Digital Engineering environment/tools. These include but are not limited to: MagicDraw for MBSE, Dynamic Object-Oriented Requirements System (DOORS) for requirements management, and Jira for sprint and backlog management.

3.6 Configuration Management

This section references the traditional functional, allocated and product baselines. These terms equate to the following Agile elements:

• Functional Baseline: The entire set of all the prioritized features in all the program increments, MVPs, MVCR, and Subsequent Software releases. This is documented in the Product Roadmap and Product Backlog.

• Allocated Baseline: The planned set of prioritized features to be developed in a specific program increment, MVP, MVCR, and subsequent software releases. This is specific segment in the Product Roadmap and Product Backlog.

• Product Baseline: The features delivered in the working software for the specific program increment, MVP, MVCR, and subsequent software releases.

3.6.1 Configuration Identification

3.6.1.1 The vendor shall ensure configuration identification, control, and status accounting of all TSS/TMT system hardware, software, and documentation including Government-furnished information and vendor-supplied items for the period of performance of this effort.

3.6.1.2 The vendor shall identify the TSS/TMT hardware and software configuration in the Functional, Allocated and Product Baselines.

The vendor shall document the Functional Baseline as defined by the SRD and incremental Contractor Data Requirements List (CDRL) deliveries.

The vendor shall document Allocated Baseline as defined by the incremental CDRL deliveries, approved requirements, MVP, MVCR and subsequent software releases.

The vendor shall document the Product Baseline as defined by CDRL deliveries, MVCR, and subsequent software releases.


10


The vendor shall, in consonance with the Government, select the Configuration Items (CIs) to be identified and assign hierarchical identifiers to each CI, select the configuration documentation to be used to identify each CI, define and document interfaces between CIs, and establish a release system for the control of configuration documentation and computer software source code.

3.6.1.3 The vendor shall seek approval for the initial system configuration and for subsequent system configuration changes during the Government hosted Functional Manager Synchronization meeting.

3.6.1.4 The vendor shall document the Functional Manager Synchronization meeting process in a Configuration Management Plan (CMP), to be delivered via Enterprise Mission Assurance Support Service (eMASS).

3.6.1.5 The vendor shall provide Functional Manager Synchronization meeting minutes and all applicable artifacts for review to the Government via eMASS in accordance with deliverable 3.8.1.2.

3.6.1.6 The vendor shall deliver an updated hardware and software list and functional architecture diagram artifact prior to each test and functional validation event via eMASS in accordance with deliverable 3.8.1.2.

3.6.2 Configuration Control

3.6.2.1 The vendor shall control CI for all baselines by form, fit, function, interchangeability, and interoperability.

The vendor shall control and change all baselines using contractor change and engineering release process.

The vendor shall request Government approval for all proposed changes that affect the form, fit, function, interchangeability, or interoperability of the current system configuration.

The vendor shall ensure that all changes to the baselines result in a common configuration for Government operational use and maintenance activities that provides interchangeability and interoperability.

The vendor shall ensure that proposed engineering changes to CIs are fully coordinated and documented.

3.6.3 Configuration Status Accounting

3.6.3.1 The TSS/TMT vendor shall identify and document all items incorporated into or deleted from the TSS/TMT during development.

3.7 Integration

The vendor is responsible for the full range of integration activities associated with planning, coordination, documentation, and execution of TSS/TMT integration with the larger STE system capability to include integration of hardware, software, networks, data, and interfaces. These duties include the following integration responsibilities to assist Government oversight and decision making.


11


3.7.1 The vendor shall work with the STE system capability developers, authoritative data providers (including OWT), and the Government to formulate, identify and document integration plans, schedules, dependencies, risks/issues and blockers associated with the full range of integration work required to ensure that TSS/TMT software is delivered in a fully integrated state to provide the full range of STE training capabilities.

3.7.2 The vendor shall document and maintain a comprehensive STE integration plan to include dependencies, milestones, action items and integration of software baseline handovers, APIs, and data elements.

3.7.3 The vendor shall plan and coordinate external STE system capability and interface vendor participation in routine vendor integration events and touchpoints in the Technology Integration Facility (TIF) located in Partnership IV.

3.7.4 The vendor shall evaluate Government provided Science and Technology (S&T) handovers to assess reuse potential to meet TSS/TMT requirements and develop plans for integration of handover capability with the TSS/TMT software baseline and external STE enablers. If a handover is not suitable for reuse, the vendor shall provide supporting rational.

3.7.5 The vendor shall document expected capabilities and limitations associated with each demonstration, test event, or release to include both TSS/TMT standalone capabilities and integrated capabilities across the full STE system capability.

3.8 Deliverables

The vendor provides the following list of deliverables to the Government throughout the performance of this effort. These deliverables serve to provide the performance data and product support data to the Government to allow for the appropriate planning and oversight for the TSS/TMT.

3.8.1 Management Deliverables

Vendor format is acceptable and shall be delivered electronically in MS Office compatible formats unless otherwise noted. The Government provides the Data Item Descriptions (DID) for vendor consideration.

3.8.1.1 Name: Contractor's Progress, Status and Management Report (CPSMR)

Purpose: Documents and tracks program performance, Agile metrics, DevSecOps metrics, tasks, agreements and existing or potential problem areas.

Initial Submission Due: 30 days after Contract Award

Recurring Submissions Due: Monthly

DID: DI-MGMT-81928 (§10.3 A-F; H; and J only) The Government reserves the right to modify the CPMSR management deliverable content during execution.

3.8.1.2 Name: DoD Risk Management Framework (RMF) Package Deliverables

Purpose: Contains the artifacts necessary to successfully achieve the Initial Authorization to Test (IATT) and Authority to Operate (ATO).

Initial Submission Due: Initial submission required 60 days after award to support Government IATT development.


12


Recurring Submissions Due: Subsequent submissions required 60 days before MVCR and follow-on releases to support Government ATO development.

DID: DI-MGMT-82001

Format: As specified in the DID.

3.8.1.3 Name: Product Roadmap

Purpose: Aligns prioritized functional and architecture features to a high-level calendar for each program increment, MVPs, MVCR, and subsequent software releases. Includes the sequence and timing of development, integration, test, and delivery. The product roadmap is a series of incremental capability deliveries that provide a working / functional training capability for the user to provide feedback.

Initial Submission Due: NLT 5 calendar days after the initial program increment planning session.

Recurring Submissions Due: NLT 5 calendar days after the increment, MVP, MVCR, and subsequent software releases program increment planning sessions.

3.8.2 Engineering Deliverables

Vendor format is acceptable, except as noted and shall be delivered electronically in MS Office compatible formats unless otherwise noted.

3.8.2.1 Name: Computer Software Product End Items

Purpose: Contains the format, content (including source code and any supporting information, data or scripts required to build), and intended use information of the software deliverable

Initial Submission Due: Initial submission with first MVP

Recurring Submissions Due: Recurring submissions with all MVP, MVCR, and releases

DID: DI-AVCS-80700A

3.8.2.2 Name: Interface Design Description (IDD)

Purpose: Describes the interface characteristics of one or more systems, subsystems, hardware configuration items, computer software configuration items, manuals, or other system components.

MBSE Approach Addendum: The Government will provide several architectural and design products of the desired system in Department of Defense Architecture Framework (DoDAF) views and Systems Modeling Language (SysML) diagrams to the vendor at contract award in the MagicDraw tool. The vendor shall use and build on these products to further define system and component interface specifications in the digital models created in and shared through the MagicDraw tool. The vendor shall use appropriate DoDAF views and/or SysML diagrams to capture the interface descriptions.

Agile Approach Addendum: The vendor shall continuously reference and evolve interface description models during development sprints. The vendor shall add new interfaces and interface descriptions as necessary and agreed-upon with the Government.


13


Initial Submission Due: The vendor shall provide initial updates to models in the MagicDraw tool at the completion of the first sprint demonstration.

Recurring Submissions Due: The vendor shall continuously update and evolve models throughout the life of the project. The vendor shall conduct reviews during sprint planning, program increment planning, and MVP/MVCR/subsequent software release completion. The vendor shall conduct additional, issue specific reviews when directed by the Government. Report snapshots may be drawn from the MagicDraw tool by any person who has access to the tool(s) at any time.

Sample Data Item Description: DoDAF 2.02; SysML 1.6

3.8.2.3 Name: Software Version Description (SVD)

Purpose: Identifies and describes a software version consisting of one or more Computer Software Configuration Items (CSCIs). It is used to release, track, and control software versions.

Initial Submission Due: Initial submission with the first MVP.

Recurring Submissions Due: Recurring submissions with all MVP, MVCR, and subsequent software releases.

DID: DI-IPSC-81442

3.8.2.4 Name: System/Subsystem Design Description (SSDD) or Software Product Specification (SPS)

Purpose: Describes the system or subsystem-wide design and the architectural design of the system and/or subsystem.

MBSE Approach Addendum: The Government will provide several architectural and design products of the desired system in DoDAF views and SysML diagrams to the vendor at contract award in the MagicDraw tool. The vendor shall use and build on these products to further define system and component design specifications in digital models created in and shared through the MagicDraw tool. The vendor shall use appropriate DoDAF views and/or SysML diagrams to capture the design descriptions. The vendor shall create/use SysML diagrams and DoDAF views to the extent that they are relevant to producing or managing the overall system as agreed to with the Government.

Agile Approach Addendum: The vendor shall continuously reference and evolve design models as required during development sprints. The vendor shall add new design models and their descriptions as necessary and agreed-upon with the Government.

Initial Submission Due: The vendor shall provide initial updates to models in the MagicDraw tool at the completion of the first sprint demonstration.

Recurring Submissions Due: The vendor shall continuously update and evolve models throughout the life of the project. The vendor shall conduct reviews during sprint planning, program increment planning, and MVP/MVCR/subsequent software release completion. The vendor shall conduct additional, issue specific reviews when directed by the Government. Report snapshots may be drawn from the MagicDraw tool by any person who has access to the tool(s) at any time.



14


3.8.2.5 Name: System/Subsystem Specification

Purpose: Specifies the requirements for a system or subsystem and the methods to be used to ensure that each requirement has been met.

Digital Engineering Approach Addendum: The Government will provide the vendor access to an initial Dynamic Object-Oriented Requirements System (DOORS) requirements repository at agreement award. The Government will also provide Cameo Data Hub to link the requirements in DOORS and the MagicDraw tool so requirements information can be efficiently included in the MBSE model diagrams/views. The vendor shall use the Government provided system requirements in the DOORS tool and shall update/annotate the requirements repository to indicate system model parts that satisfy requirements.

MBSE Approach Addendum: The vendor shall annotate and/or trace relations to system requirements in the digital models created in and shared through the MagicDraw tool. Tracing the relation to the requirements (e.g., Requirements Traceability Matrix [RTM]/Verification Matrix) depends on which DoDAF views and/or SysML diagrams the model uses and not all SysML diagrams or DoDAF views require tracing back to requirements. The vendor shall use requirement ID numbers consistently throughout the system model diagrams/views.

Agile Approach Addendum: The vendor shall use the requirements repository to form the Program, Iteration, and Sprint Backlogs. The vendor shall develop user stories that encapsulate the requirements into manageable sets. The vendor shall use requirement ID numbers consistently throughout the Agile development process.

Initial Submission Due: The vendor shall begin Agile planning with requirements and include requirements tracing to/from system model diagrams/views starting with the first development sprint.

Recurring Submissions Due: The vendor shall continuously update and evolve the requirements repository and the system model(s) throughout the life of the project. The vendor shall conduct reviews during sprint planning, program increment planning, and MVP/MVCR/subsequent software release completion. Report snapshots may be drawn from the requirements and MBSE tool(s) by any person who has access to the tools at any time.


3.8.2.6 Name: Test Plan

Purpose: Provides an overview of the DevSecOps, Incremental Government, and Cybersecurity Tests and Events test strategies to include scope and objectives.

Initial Submission Due: 30 days after contract award.

Recurring Submissions Due: N/A.

DID: DI-SESS-80688

3.8.2.7 Name: Test Procedure


15


Purpose: Identifies the step-by-step testing operations to be performed on items undergoing developmental, qualification, or acceptance testing. Includes objectives and definitions of success.

Initial Submission Due: Provide the initial draft procedure 45 days prior to the Technical Assessment (TA) and the final procedure 10 days prior to the TA.

Recurring Submissions Due: Every TA.

DID: DI-NDTI-80603A

3.8.3 Product Support Deliverables

Deliverables shall conform to the format identified in the Data Item Description and shall be delivered electronically in MS Office compatible formats unless otherwise noted.

3.8.3.1 Name: Commercial Off-The-Shelf (COTS) Manuals & Associated Supplemental Data

Purpose: Documentation provided with COTS products that may be used “as is” or with supplemental data, if required.

Initial Submission Due: Draft 30 days prior to MVCR

Recurring Submissions Due: Final with MVCR. Draft 30 days prior to each subsequent software release. The final with each subsequent software release (as required by the Government).

DID: DI-TMSS-80527C

3.8.3.2 Name: Preparation of Digital Technical Information for Electronic Technical Manuals (TMs) – System User Manual

Purpose: Establishes the technical content, style, and format requirements for all TMs, including operator and maintenance TMs and can be used to develop TMs as paper, page-based manuals, or electronic technical manuals.

Initial Submission Due: Draft 30 days prior to MVP


DID: MIL-STD-40051-1C

3.8.3.3 Name: Preparation of Digital Technical Information for Electronic Technical Manuals (TMs) – Quick Reference Card(s)

Purpose: Contains the requirements for development of Quick Reference Guides (QRGs).

Initial Submission Due: Draft 30 days prior to MVP


DID: MIL-PRF-32614


16


3.8.3.4 Name: Training Aids, Devices, Simulators, and Simulations (TADSS) Materiel Component List (MCL)

Purpose: The MCL is listing of all system and non-system TADSS component parts and the data required to create a Component of the End Item List, Basic Issue Item (BII) List, and Additional Authorization List (AAL). The MCL contains the TADSS end item, discrete subassemblies, and nonexpendable components in an indentured format for TADSS end item. The MCL defines the property record of TADSS items and allows gaining commands to account for an end item's components. The Government provided format outlines the required structure of the data that gives the Government the ability to import the MCL into DoD databases or property accountability and property transfers.

Initial Submission Due: 30 days prior to MVP


DID: DI-PSSS-82310

3.8.3.5 Name: Training Materials

Purpose: Provides the materials required to support training on the end item equipment (e.g. video applications, applets, instructor guides, student guides, presentations, etc.).


Recurring Submissions Due: Recurring submissions with all MVPs, MVCR, and each subsequent software release

DID: DI-ILSS-80872

3.8.3.6 Name: Item Unique Identification (IUID) Marking and Verification Report

Purpose: A tabular list that provides physical asset marking, registration, verification, inventory audits, quality audits, and other asset lifecycle activities.

Initial Submission Due: 30 days prior to MVP


DID: DI-MGMT-81858

3.8.3.7 Name: Training System Support Document

Purpose: Provides complete procedures for using all software utility programs, support software file generation, and system performance characteristics verification for life cycle maintenance. This document also contains information to assist users in operating and fully using the training system during the presentation of course(s) of instruction, training exercise(s), or missions.


Recurring Submissions Due: Recurring submissions with each MVP, MVCR, and each subsequent software release

DID: DI-PSSS-81527C


17


3.8.3.8 Name: Trainer Facilities Report (TFR)

Purpose: The report defines and identifies criteria and requirements necessary to design and construct/modify a facility in which the trainer and associated equipment will be installed, operated, and maintained. The report identifies contractor and Government responsibilities and the time frame in which the responsibilities will be completed.

Initial Submission Due: 30 days prior to first MVP

Recurring Submissions Due: As required for each delivery site

DID: DI-FACR-80966F

3.8.3.9 Name: Training Device Inventory Checklist/Record (TD ICL/R)

Purpose: Provides a checklist and record of expendable and nonexpendable equipment and support items, including tools, test equipment, Government Furnished Equipment (GFE), technical documentation, software and spare and repairable parts that are delivered as part of or with the device or system. This report will be utilized during device acceptance, inventory and transfer of the training device or system.

Initial Submission Due: 30 days prior to first MVP


DID: DI-MISC-81191B

3.8.3.10 Name: Instructional Media Package – Training Video

Purpose: Contains visual, textual, and audio information to be used in the development and presentation of training. It also includes the fully integrated instructional media presentation package.

Initial Submission Due: 30 days prior to the first MVP


DID: DI-SESS-81526C

3.8.3.11 Name: Warranty

Purpose: Provide information on items under warranty; contractor repair, replacement, and reimbursement; and equipment failure data associated with Reliability Improvement Warranties (RIWs). Data is used to track and assess the effectiveness and implementation of the contract warranty provisions; to apprise the Government of the type, severity, and frequency of failures; to verify warranty coverage for each item delivered; and to document warranty periods and delivery schedules.

Initial Submission Due: 30 days prior to the first MVP



18


DID: DI-SESS-81639A

3.8.4 TSS/TMT Hardware Deliverables

The Government based the quantity of hardware identified in the tables below on existing training systems. The vendor shall recommend a hardware set that enables Brigade and below collective training that minimizes the quantity, size, and logistics footprint for the Government to evaluate and approve. The training capability for RVCT Ground, RVCT Soldier, RVCT Air, and SVT shall be able to operate independently. For example, if a location has all training capabilities, that location shall be able to operate each training capability simultaneously and independent of each other. For additional hardware and PoN concepts see the TDP Appendix E TSS/TMT Hardware Concept.

Table 3-2 identifies hardware quantities. The vendor shall provide all hardware, except the central node, in rugged, modular, weatherproof, and lockable storage/transit cases.

Table 3-2. Development / User Feedback Locations.

Name Location Central

Node CDS

Edge

Node

Field

Server

EXCON

Laptops

OC Mobile

Device

Vendor Development Lab TBD As proposed by vendor

Government Orlando

Labs FL 2 1 2 1 9 3

Operational Test

Command (OTC) TX 0 0 0 1 4 2

Army Test & Evaluation

Command (ATEC) MD 1 1 1 1 1 1

PEO AVN / CCDC AvMC AL 0 0 0 1 4 2

Fort Leavenworth KS 0 0 0 1 4 1

Total 3 2 3 5 22 9

Table 3-3 identifies the hardware quantities the vendor shall provide to the identified fielding sites. The Government based the hardware quantiles identified in the tables below on existing training systems.

Table 3-3. Fielding Locations.

Name Deliveries Central

Node CDS

Edge

Node

Field

Server

EXCON

Laptops

OC

Mobile

Device

Fort Hood, TX

MVP / Operational Test

/ MVCR / Annual

Releases

2 1 2 6 42 28

Total 2 1 2 6 42 28

3.8.4.1 The vendor shall specify the hardware concept, quantities, and draft specifications no later than 75 days after contract award for the Government to approve.


19


3.8.4.2 The TSS/TMT vendor shall provide a minimum hardware resource requirement or specification to the Government and RVCT vendor not later than 60 days after OTA award to accommodate TSS/TMT platform mission software (OFP, CSL, etc.) and certain TSS functions much as mobility modeling, e.g. flight dynamics model, that will be hosted on RVCT provided computer kit hardware.

3.8.4.3 The vendor shall choose hardware items that provide a reduction of total ownership costs and logistics footprint to include supply chain support.

The vendor shall, when possible, avoid using any individual item whose unit purchase cost or spare price is greater than $25,000.

The TSS/TMT system shall avoid using any individual item that has a projected removal/replacement rate greater than once per year.

The vendor shall, when possible, avoid using any item that has a projected annual maintenance cost of greater than $10,000 per training device.

The TSS/TMT system shall avoid using any item that requires special or extraordinary handling, disposal, usage rate, or maintenance procedures.

The TSS/TMT system shall avoid using any item that will be unsupportable and out of production by the Original Equipment Manufacturer (OEM) within 36 months after MVCR or each subsequent annual software release.

3.8.4.4 The vendor shall preload the RVCT, Central Node, Edge Node, Field Server, EXCON Laptop, and Observer Controller (OC) Mobile Devices with the current TSS/TMT software release and the OWT data and models as appropriate prior to each delivery.

3.8.4.5 The vendor shall deliver all hardware in accordance with commercial best practices and applicable packaging, handling, storage, and transportation (PHS&T) standards.

3.8.4.6 The vendor shall deliver production representative hardware to development and user feedback sites no later than 30 days after the Government approves the vendor’s hardware concept, hardware quantities, and draft specifications IAW Table 3-2.

3.8.4.7 The vendor shall provide a cost option to replace production representative hardware at the development and user feedback sites with production hardware (final specification) after MVCR, release 1, and release 2.

3.8.4.8 The vendor shall update the software loads on the previously delivered hardware to the latest software baseline with each software release.

3.8.4.9 The vendor shall deliver production hardware (final specification) to fielding and operational testing sites to be available on the first day of fielding or the first day of the test event preparation window as appropriate.

3.8.4.10 The vendor shall provide cross domain solutions (software or hardware) for the development and fielding locations IAW Table 3-2 and Table 3-3.

3.9 System Requirements

The vendor ensures that the STE simulation represents and models units, organizations, lifeforms, and other like objects as individual entities at all times. Although aggregation is required to be applied for purposes of viewing, decluttering, or controlling large units or formations, internal simulation/game engine entity level modeling and entity level representation within network packets is always required. The


20


STE definition of an entity is as follows: An entity is any independent object within a simulation that possesses complex behaviors and attributes. For example, personnel, vehicles, complex munitions, key communications devices might all be represented as independent entities within a simulation.

The vendor utilizes the system requirements as described in the TSS/TMT TDP Appendix F SRD to form the initial backlog for TSS/TMT capability. The TDP contains materials with distribution limitations. The Government can release the TDP to vendors that successfully navigate the PEO STRI vetting process.

The first two levels of the SRD requirements schema are shown below.

0 Introduction and Scope: This Synthetic Training Environment (STE) Training Simulation Management Tool (TSS/TMT) (the combined name for the Training Simulation Software (TSS) and Training Management Tool (TMT)) System Requirements Document (SRD) Outline document provides an outline of the master SRD (in Excel format) and summary of its major sections. This Outline document does NOT contain the actual system requirements which are contained in the TSS/TMT SRD spreadsheet (in Microsoft Excel format). Recommend that reader have both this document and the TSS/TMT SRD spreadsheet open. The headings are hyperlinks which will take the reader to the corresponding sections in the TSS/TMT SRD Excel file.

1 Common TSS/TMT Requirements: This section contains system requirements that are at a higher-level and may be applicable to both TSS and/or TMT. The specific TSS or TMT sections may contain detailed requirements specific to that system that are decomposed from the general requirements in this section.

1.1 Played Items: This section specifies requirements for the entity types that shall be modeled by the TSS/TMT. The Entity List appendix to this SRD contains the complete list of entity types required.

1.2 PMESII-PT: This section specifies the requirements for the modeling of the Operational Environment (OE), specifically in the areas of PMESII-PT (Military, Information, Infrastructure, Physical Environment, and Time) variables.

1.3 METT-TC: This section specifies the requirements to model the dynamic mission analysis factors METT-TC (Mission, Enemy, Terrain, Troops Available, Time, and Civilian Considerations).

1.4 Rendering: This section specifies the requirements for the 3D rendering of the complete synthetic training environment (including static and dynamic elements).

1.5 Architecture: This section specifies the various architecture-level requirements that include but are not limited to the following areas: Scalability, modular and open standards, cybersecurity, data model, and authoritative data sources.

1.6 Technology: This section specifies requirements for technology expectations especially in the areas of Intelligent Tutor System (ITS), Artificial Intelligent / Machine Learning (AI/ML), and Big Data.

1.7 Interoperability/Integration: This section specifies requirements for the external systems that the TSS/TMT shall interface/interoperate with,


21


specifically with Live and Constructive (LVC) systems through LVC-IA, as well as with the Mission Command Information Systems (MCIS).

1.8 Deployment: This section specifies requirements related to deployment that include computing and networking/cloud equipment at the PoN.

1.9 Non-Architecture Attributes/Guidance: This section specifies requirements for other non-architecture areas such as support for the CATS tasks and unit collective training, Data Right, Safety and Health.

1.10 One World Terrain: This section specifies requirements for the One World Terrain (OWT) products integration with TSS/TMT.

1.11 RVCT Integration: This section specifies requirements to provide software for the Reconfigurable Virtual Collective Trainer (RVCT) and the integration to the required RVCT Air/Ground/Soldier platforms.

1.12 Product Support: This section specifies requirements to enable TSS/TMT product support including RAM, Packaging and Handling, Helpdesk support, hardware design considerations.

1.13 Multi-Domain Operations (MDO): This section specifies requirements to support MDO.

2. Training Simulation Software (TSS): This section specifies requirements specifically applicable to the TSS. There may be other implied TMT requirements to support the TSS/TMT integration that may not be explicitly documented in Section 3.x (TMT).

2.1 TSS/RVCT: This section specifies requirements for the TSS software to run on all required RVCT Ground/Air/Soldier platforms/systems/subsystems.

2.2 TSS General: This section specifies requirements for the TSS to provide the complete synthetic training environment that includes the physical environment modeling and effects, Computer Generated Forces for entity- and aggregate-level models and behaviors, communications, game engine, semi-immersive, and TMT integration.

2.3 SVT: This section specifies requirements for the TSS to support the integration with the Soldier Virtual Training (SVT).

2.4 SiVT: This section specifies requirements for the TSS to support the integration with the Squad Immersive Virtual Training (SiVT).

3. Training Management Tool (TMT): This section specifies requirements specifically applicable to the TMT. There may be other implied TSS requirements to support the TMT-TSS integration that may not be explicitly documented in Section 2.x (TSS). The requirements are arranged in the Plan, Prepare, Execute, and Assess (PPEA) phases and those are common to more than one of the PPEA phases.

3.1 Assess: This section specifies the TMT requirements for the Assess phase of the training event life cycle.

3.2 Execute: This section specifies the TMT requirements for the Execute phase of the training event life cycle.

3.3 Plan: This section specifies the TMT requirements for the Planning phase of the training event life cycle.

3.4 Prepare: This section specifies the TMT requirements for the Prepare phase of the training event life cycle.


22


3.5 Common: This section specifies the TMT requirements that are common or applicable to more than one phase of the PPEA phase.

3.9.1 General

3.9.1.1 The vendor shall provide 50 copies of any commercial software used in the TMT or TSS solution for independent Government capability verification, benchmarking, and experimentation.

3.9.1.2 The vendor shall consume products provided by OWT. Refer to the TDP Appendix F SRD for additional OWT requirements.

The TSS/TMT vendor shall supplement the moving model library obtained from the OWT vendor with vehicle models that already exist in their library. These models shall be used as is without further modification and without new model development. These models shall be disclosed to the Government and limitations in functionality published so that the Government can determine their suitability for use in the simulation.

The vendor shall provide a methodology that allows a third party to produce models in the open OWT format and then convert the model to the open TSS/TMT run-time format specifications in accordance with the deliverables (3.8.2.1).

The TSS/TMT vendor shall work with the OWT vendor to ensure that the Well Formed Format (WFF) provides all of the information required by the TSS/TMT software while keeping the WFF an open specification and be able to be used by third party software (see TDP Appendix G for the OWT Specification).

The TSS/TMT vendor shall provide the human and animal models and kinematics for those models as listed in the model list.

The TSS/TMT vendor shall work with the OWT vendor and the Government to ensure that the Filmbox (FBX) and glTF implementations contain all the information required by the TSS/TMT software to render the model. The TSS/TMT vendor shall provide a methodology for third party content creators to create models that can be rendered by the TSS/TMT software.

3.9.1.3 The vendor shall ensure the TSS solution is optimized for cross platform use and must function on mobile devices, laptops, desktops, and untethered cross reality (XR) devices.

3.9.1.4 The vendor shall work with the RVCT vendor to perform analysis, trade studies and experimentation to determine the feasibility of achieving significant reduction in power consumption of the RVCT Compute Kit(s) and TSS/TMT compute/rendering/storage capability located at the PoN. The vendor shall identify and explore novel approaches such as application of low power mobile computing technology and/or transmission of streaming video in support of significant PoN power reduction.

3.9.1.5 The vendor’s new development work shall not break current capabilities.

3.9.2 Architecture


23


The separation in contract vehicles drives the need for the development to synchronize architecture and establish platform abstraction layers, integration services interfaces, and interface agreements between vendors. The STE architecture defines the conceptual structure and logical organization of the STE capabilities. The architecture supports real-time situational awareness across all modules / components, scalability, cybersecurity, accessibility, interoperability, and extensibility. The STE provides a secure system that meets the cybersecurity requirements outlined in Section 3.13.2 Cybersecurity.

The vendor has the option to use the Government provided and managed Development and Engineering Experience Platform (DEEP), a vendor provided and managed digital engineering environment, or a hybrid that uses both the DEEP and a vendor provided and managed digital engineering environment. The DEEP is a Government collaboration space for U.S. persons that hosts the authoritative architecture model and requirements repository. The DEEP includes NoMagic MagicDraw that uses Unified Profile for DoDAF/MODAF (UPDM) and SysML plug ins. The DEEP also includes the Dynamic Object-Oriented Requirements System (DOORS). The DEEP architecture model is the central system, software, and DoDAF architectural model, and the DEEP requirements repository is the central requirements repository.

3.9.2.1 If the vendor provides their own digital engineering environment and tool set or a hybrid approach, then the vendor shall provide automated exports in the MDzip standard and integrate with the DEEP central architectural model and central requirements repository with no data loss in the transfer process. The submitted architecture must adhere to the Government style guides.

3.9.2.2 The vendor tool set data / object structure export shall align with MagicDraw and DOORS tools and satisfy all the data elements, object structure, and linkages in the central architecture model and central requirements repository.

3.9.2.3 If the vendor creates new architectural elements that need to be incorporated into the central architectural model, then the vendor export / import process must generate these new elements in the central architectural model.

3.9.2.4 If the vendor provides their own digital engineering environment or uses a hybrid approach, then the vendor shall update the central model at least once a week or as directed by the Government.

3.9.2.5 If the vendor creates new requirements that need to be incorporated into the central architectural model, then the vendor export / import process must generate these new requirements and mappings in the central requirements repository.

3.9.2.6 If the vendor provides their own digital engineering environment or uses a hybrid approach, then vendor shall update the central requirements repository at least once a week or as directed by the Government.

3.9.2.7 The vendor shall implement a Modular Open Systems Approach (MOSA) that complies with MOSA Implementation Guide Version 1.0 and the MOSA Reference Frameworks in Defense Acquisition Programs.


24


3.9.2.8 The TSS/TMT shall be modular, with an open architecture, such that the system interfaces share common, widely accepted standards that support interoperability across OWT, RVCT and IVAS-SiVT if available, at the Brigade and Below software release.

3.9.2.9 The vendor shall enforce modular architectures.

3.9.2.10 The vendor shall certify conformance to modularity and openness using the Program Assessment and Review Tool (PART) in accordance with the deliverables (3.8.2.1).

3.9.2.11 The vendor shall comply with the Army Data Modernization Strategy.

3.9.2.12 The vendor shall designate key interfaces.

3.9.2.13 The vendor, in collaboration with the Government, shall define and manage all ICDs in accordance with the deliverable (3.8.2.2).

3.9.2.14 The vendor shall propose standards for Government approval in accordance with the deliverable (3.8.2.2).

3.9.2.15 The vendor shall develop and deliver the SSS and SRS in accordance with the deliverables (3.8.2.4 and 3.8.2.5).

3.9.2.16 The vendor shall document major interfaces and components of the vendor solution in a briefing that identifies points of modularity and evaluates all major components and interfaces for their degree of modularity and openness in accordance with the deliverable (3.8.2.2).

3.9.2.17 The vendor shall provide frequent architecture updates that focus on interface definition to support rapid integration.

The vendor shall provide the first briefing not later than 60 days after OTA award.

The vendor shall provide architecture updates at each MVPs, MVCR, and releases.

3.9.2.18 The vendor architecture shall be compliant with the Government’s high-level STE architecture.

3.9.2.19 The vendor shall provide the architecture for the TSS/TMT cloud.

3.9.2.20 The vendor can request changes to the Government’s high-level STE architecture through the Government’s Architecture Synchronization Agile ceremony as appropriate and the Government will evaluate and determine applicability in accordance with the deliverables.

3.9.2.21 The vendor shall develop documentation that integrates the STE system capability and interfaces to include software architecture, systems architecture, training manuals, technical and troubleshooting manuals, and test plans and procedures in accordance with the deliverables (3.8.2.1, 3.8.2.2, 3.8.3.2, and 3.8.2.6).

3.9.3 Point of Need

The TSS/TMT delivers training content to the PoN at Home Stations, deployed locations, and training and educational institutions. See Table 3-3 for MVCR and Operational Test locations. See the TDP Appendix E TSS/TMT Hardware Concept for more information on the PoN.

3.9.3.1 Point of Need Conditions


25


The STE collective training system will be used at existing facilities at the PoN. The STE collective training system uses existing facilities’ shelter, power, and environmental control that maintains the temperature and humidity range (see AR 70-38, Research, Development, Test, and Evaluation of Materiel for Extreme Climatic Conditions).

When the STE collective training system is transported to a PoN that does not have a facility, the unit will provide tents, generators, and environmental control units to shelter and power the training capabilities and maintain the temperature and humidity in the range needed to operate the training capabilities. This will enable the operation of the STE collective training system in austere and semi-austere environments.

3.9.3.2 Network

The STE operates in connected and disconnected modes (for training under limited or degraded network conditions). STE leverages the Army Network (enterprise and tactical) to deliver training to the PoN. STE traffic traverses the Integrated Enterprise Network (IEN), Integrated Tactical Network (ITN), and commercial networks. The IEN is the backbone wide area network that connects installations together. The Installation Campus Area Network (ICAN) connects buildings on the installation. The ITN connects the MCIS and COE. STE traffic will also traverse organizational networks (Army National Guard and United States Army Reserve) to provide a total Army training capability.

The vendor solution shall use DoD networks (e.g., ITN, IEN, ICAN), and commercial networks for transport.

The vendor shall provide network access from the Cloud provider to the DoDIN access point.

At a minimum, the vendor shall use identity management, domain name service, and active directory enterprise services.

The vendor shall design the TMT software to be securely accessible to the user from a public network.

The vendor shall support network communication exercises (COMEX) prior to each network risk reduction event (NRRE).

The vendor shall support TIF NRREs using the Joint Mission Environment (JME) and the DoDIN utilizing Non-classified Internet Protocol (IP) Router (NIPR).

The vendor shall support Operational Site NRREs using the Department of Defense Information Network (DoDIN) to inform/determine the network bandwidth and latency thresholds.

The vendor shall support Government wireless pilot experiments in the Government lab infrastructure and at Operational Sites over the DoDIN to inform/determine the network bandwidth and latency thresholds.

The vendor shall support Government cellular pilot experiments in the Government lab infrastructure and at Operational Sites over the DoDIN to inform/determine the network bandwidth and latency thresholds.

The vendor solution shall be able to use installation wireless capabilities.


26


3.9.3.3 Cloud

The TSS/TMT uses elastic and scalable shared computing resources to scale the capability without excessive, idle overhead capacity. The TSS/TMT hybrid cloud agnostic design enables the capability to transition between cloud service providers. The vendor shall use Defense Information Systems Agency (DISA) approved Cloud services and shall adhere to the Enterprise Cloud Management Office (ECMO) guidelines and standards. See enterprise-cloud-management-office-ecmo for additional information. The vendor follows the DoD Digital Modernization Strategy and DoD Cloud Strategy and operates up to Impact Level 6 and MCIS classification of secret.

The vendor shall collaborate with the Government and use the Army approved cloud provider.

The vendor shall use a zero-trust cloud.

The vendor shall use Cloud enabled Multi-cluster and cross-data center deployments including disaster recovery, aggregation for analytics, cloud migration, mission-critical stretched deployments, and global distribution to provide the framework for storing, reading, and analyzing streaming data.

3.9.3.4 Multi-level Security

The vendor shall employ a bi-directional CDS that can host multiple security classifications (i.e., Unclassified, Secret, and Secret Releasable) in a single exercise.

The vendor shall work with the Government to determine the number and type of releasable categories the CDS will support. The TDP Appendix E TSS/TMT Hardware Concept includes conceptual CDS courses of action.

3.9.4 TSS/TMT Hardware

TSS/TMT employs an innovative and minimalistic hardware solution that leverages breakthroughs in content delivery. TSS/TMT hardware may include central nodes, edge nodes, field servers, EXCON laptops and OC Mobile Devices. The central node and edge node hardware provides compute, store, and local area network capabilities that reduce risk for the Army network in connected or disconnected operations at the PoN. The central nodes, unclassified and classified, reside in the Network Enterprise Center (NEC) or other suitable location that provides the physical security, network connections, power, cooling, and administration as determined by installation and Army Regulation. Edge nodes will be collocated with the RVCT-Air and RVCT-Ground training capabilities and expanded to provide compute at PoN for future SVT and live capabilities. The field server hardware provides a compute and store capability that enables training at the PoN. TSS, TMT and OWT software and data reside on the edge nodes and the field servers. EXCON laptops allow EXCON / HighCon / LowCon / White cell and OPFOR to monitor and control the training event. OC Mobile Devices enable observer controller trainers to monitor and interact with the training event while observing the training audience. For additional hardware and PoN concepts see the TDP Appendix E TSS/TMT Hardware Concept.

https://login.milsuite.mil/?goto=https%3A%2F%2Fwww.milsuite.mil%3A443%2Fbook%2Fgroups%2Fenterprise-cloud-management-office-ecmo


27


3.9.4.1 The vendor shall recommend a hardware set that enables Brigade and Below collective training that has a minimal size, weight, and power footprint for Government evaluation and approval.

3.9.4.2 The vendor TSS/TMT hardware configuration shall provide compute, store, and network capabilities.

3.9.4.3 The vendor shall consider trade space between network, cloud, storage, and end-device (e.g., zero/thin client, thick client, RVCT, SVT) capabilities and location.

3.9.4.4 The vendor shall identify the hardware configuration that satisfies the STE requirements (TSS/TMT & OWT services) at the PoN.

3.9.4.5 The vendor shall use the National Information Assurance Partnership (NIAP) validated or Approved Products List (APL) components in the performance of this contract.

3.10 Agile Process

The Government requires that the TSS/TMT solution be built using Agile practices that are consistent with the SAP and that enable frequent user feedback. The vendor identifies how they will produce deliverables within an incremental, fast-paced software development schedule to reduce the risk of failure.

The vendor identifies an Agile approach that addresses meetings and Agile ceremonies such as: daily scrum meetings, scrum of scrums, sprint planning, sprint demonstrations, sprint retrospectives, program increment planning sessions, integration points between teams, system demonstrations, and other components of the Agile methodology. The vendor Agile approach ensures continuous user engagement and feedback mechanisms. The vendor identifies sprint and program increment length. The vendor identifies a specific technique to facilitate distributed meetings with the Government, vendors, and sub-vendors using a mechanism approved for official use only (FOUO). Using the Agile development process, the vendor works with the Government to identify the capabilities the vendor develops during each program increment and sprint.

The TDP Appendix F SRD provides additional requirements guidance necessary for the Government and vendor to collectively construct the initial and incremental backlog of features and / or user stories. The specifics of each backlog item shall include, but not be limited to:

• A Government approved prioritized increment feature list and product roadmap.

• Functional owner approved, prioritized increment/sprint user stories (including the anticipated outcome).

• Business value of each user story toward overall objectives.

• Progress reporting, risk identification and dependency identification.

The Government’s preferred Agile approach embraces changing requirements over time based on constant user feedback. The approach provides a common cadence for the Agile teams where they plan, develop, demonstrate, and learn together as an integrated system.

3.10.1 General


28


3.10.1.1 The vendor Agile process shall include time for technology investigation, innovation, refactoring, and bug fixes.

3.10.1.2 The vendor shall support the Government leadership team in addressing expectations, and identifying risks, issues, opportunities, and dependencies across the development.

3.10.1.3 The vendor shall deliver the initial working software that meets the vendor’s proposed and Government approved MVCR in accordance with the deliverable (3.8.2.1).

3.10.1.4 The vendor shall elevate all cost, schedule, and performance decisions to the Government.

3.10.1.5 The vendor shall participate in the weekly Government-led scrum of scrum meetings.

3.10.1.6 The vendor shall participate in the weekly Government-led functional manager / functional owner synchronization meetings.

3.10.1.7 The vendor shall participate in the weekly Government-led architecture synchronization meetings.

3.10.1.8 The vendor shall provide the Government an Architecture Roadmap review at least two increments prior to a program increment, MVP, MVCR, and subsequent software release as per the mutually agreed to schedule.

3.10.1.9 The vendor in collaboration with the Government shall incrementally update and maintain the roadmap and product backlog after each program increment, MVP, MVCR, and subsequent software release in accordance with the deliverables (3.8.1.3).

3.10.1.10 The vendor shall participate in the Government-led pre-program increment planning session.

3.10.2 Agile Ceremonies

3.10.2.1 The vendor shall conduct a program increment planning session with the Government prior to each increment and shall use the Government provided prioritized features to conduct the planning.

The vendor shall meet the following program increment planning session entry criteria:

• Government provided prioritized functional features and architecture enablers.

The vendor shall provide the Government the following program increment planning session exit criteria NLT 5 calendar days after the planning session in accordance with the deliverables (3.8.1.3, and 3.8.2.7):

• Program increment objectives.

• Sprint plan for each team.

• Team risks.

• Program Increment dependency board.

• Updated product roadmap.

• Updated architectural runway.

• Updated product backlog.

• T&E Plan.


29


• RTM.

3.10.2.2 The vendor shall conduct team sprint planning sessions on the first day of the sprint.

The vendor shall meet the following team sprint planning session entry criteria:

• Program increment planning session exit criteria artifacts.

The vendor shall provide the Government the following team sprint planning session exit criteria NLT 1 calendar day after the sprint planning session:

• Refined team sprint plan.

• Team sprint goals.

3.10.2.3 The vendor shall conduct a sprint review with the Government at the end of the sprint cycle.

The vendor shall meet the following sprint review entry criteria:

• Refined team sprint plan.

• Sprint test results.

The vendor shall provide the Government the following sprint review exit criteria NLT 2 calendar days after the sprint demonstration:

• Sprint retrospective.

• Sprint release notes.

• Sprint backlog refinement.

3.10.2.4 The vendor shall conduct a program increment demonstration with the Government at the end of the program increment cycle.

The vendor shall meet the following program increment demonstration entry criteria in accordance with the deliverables (3.8.2.6, 3.8.2.7, and 3.8.2.1):

• Program increment software/hardware.

• Program increment test results.

The vendor shall provide the Government the following program increment demonstration exit criteria NLT 2 calendar days after the demonstration:

• Program increment release notes.

• Program increment retrospective.

• Software release.

• Product backlog refinement.

• Next program increment planning session.

3.10.3 Agile Metrics

3.10.3.1 The vendor shall provide an automated Agile metric reporting mechanism for Government approval.


30


3.10.3.2 The vendor shall develop and track the following Agile metrics for each sprint and program increment, MVP, MVCR, and subsequent software releases to the Government NLT 2 calendar days after the cycle in accordance with the deliverables (3.8.1.1). See the DoD Agile Metrics Guide, Strategy Considerations and Sample Metrics for Agile Development Solutions Version 1.1 dated 23 September 2019 for additional information and formulas for the metrics identified below.

Agile Process Metrics. Agile process metrics measure process performance, or how well planning, execution, and delivery activities are performing. Agile process metrics shall include:

• Feature Points: Used for sizing features. It measures the complexity of a feature. Typically, features points utilize the Fibonacci sequence (1,2,3,5,8 etc.).

• Story Points. Story points measure the complexity of a story. The developer assigned to a story is responsible for identifying how much effort is required to complete the work in each sprint. If a story is larger than 8, the team must go back and split the story.

• Velocity. Velocity measures the amount of work (usually in story points, although other measurement units can be used as well, such as hours) that the team completes in each sprint.

• Velocity Variance. Velocity variance is the standard deviation from average velocity – or the difference from the mean velocity.

• Velocity Predictability. Velocity predictability is measured as the difference between planned and completed velocity, which is the difference between the total planned and completed story points for a given sprint.

• Story Completion Rate. Story completion rate describes the number of stories Across Board completed in each sprint or release.

• Sprint Burndown. Teams implementing sprints use a sprint burndown chart to estimate their pace of work accomplished daily. The pace is usually measured in hours of work.

• Release Burnup. The release burnup metric is a planning tool that allows the Agile team to estimate whether the team is on track to complete the items in the release.

Agile Quality Metrics. Agile quality metrics measure the quality of work being delivered. Agile quality metrics include:

• Recidivism. Recidivism describes stories that are returned to the team for various reasons. If stories are not completed as the users expect, the team will need to understand the reasons, especially if recidivism rates are relatively high or increasing.

• Defect Count. Defect count measures the number of defects per sprint or release.

• Number of Blockers. Number of blockers describes the number of events that prohibit the completion of an activity or work item. These blockers cannot be resolved by the individual assigned to complete the activity and the team needs assistance to remove the blocker.


31


Agile Product Metrics. Agile product metrics should measure the value that the product delivers in terms of user acceptance and alignment to desired outcomes (measured by value). Agile product metrics include:

• Delivered Value Points. This metric represents the count of value points delivered to users for a given release. Value points are usually defined by the users (or user representatives) to indicate a business value assigned to a given feature, capability, epic or story.

• Level of User Satisfaction. This metric represents the measure of user satisfaction based on the value delivered by the product or solution.

3.10.4 Roadmap

3.10.4.1 The vendor shall collaborate with the Government to develop and maintain an executable product roadmap that includes prioritized features aligned to a high level calendar and success metrics approved by the Government for each program increment, MVPs, MVCR, and subsequent software releases in accordance with the deliverables (3.8.1.3).

3.10.4.2 The vendor shall propose their version of the product roadmap in response to this PWS that considers the desires of the Government’s draft product roadmap and balances that with the practical sequence and timing of development, integration, test and delivery that it can support.

The vendor roadmap shall include test dates.

The vendor roadmap shall include test lead time cutoff points.

The vendor roadmap shall include TMT capability progression broken out by the plan, prepare, execute, and assess elements; artificial intelligence, machine learning, and intelligent tutoring system integration; and interfaces with authoritative data sources.

The vendor roadmap shall include TSS computer generated forces capability progression.

The vendor roadmap shall include TSS entity level constructive training.

The vendor roadmap shall include the cross-domain solution accreditation progression.

The vendor roadmap shall include the cybersecurity accreditation progression.

The vendor roadmap shall include fires training capabilities by echelon capability progression.

The vendor roadmap shall include mission command training capabilities by echelon capability progression.

The vendor roadmap shall include movement and maneuver training capabilities by echelon capability progression.

The vendor roadmap shall include RVCT-Soldier software capability progression e.g., Soldier/Squad to BCT.


32


The vendor roadmap shall include platform level Mission Command representation and interoperability capability progression (includes Platform command and control [C2] capability required by certain RVCT Solider and/or EXCON roles such as Squad leader and Platoon leader and Fires handheld C2 device representation [simulation, emulation or “wrapping” of tactical software] for use by a simulation role player).

The vendor roadmap shall include Command Post Mission Command interoperability, mapped to all systems specified in SRD capability progression.

The vendor roadmap shall include scalability capability progression.

The vendor roadmap shall include voice communications system capability progression.

The vendor roadmap shall include RVCT Air Software platform software capability progression.

The vendor shall provide a breakout of when each major air subsystem is integrated and delivered (e.g., Apache basic flight, AvSE integration, fire control radar, 30 mm, Rockets, Hellfire, voice comms, digital comms Link 16, Air Force Applications Program Development (AFAPD) and Joint Variable Message Format (JVMF), TMT management, Aviation Mission Planning Software (AMPS) initialization, etc.).

The vendor roadmap shall include RVCT Ground Software platform software capability progression.

The vendor shall provide a breakout of when each major ground subsystem is integrated and delivered

The vendor roadmap shall include Political, Military, Economic, Social, Infrastructure, Information - Physical Environment, & Time (PMESII-PT) capability aligned to Military, Information, Infrastructure, Physical Environment and Time variables capability progression.

The vendor roadmap shall include interoperability (e.g., LVC-IA, JLCCTC, IEWTPT) capability progression.

The vendor roadmap shall include RVCT Air and Ground platform integration capability progression.

The vendor roadmap shall include OWT capability progression (e.g., model integration, base globe, Graphics Library Transmission Format (glTF)/3D tiles import, download and stitch hi resolution areas onto base globe, terrain editing, submission of edits to OWT repository for potential integration into master OWT repository).

The vendor roadmap shall include Government Furnished Information (GFI) / GFE / S&T integration.

The vendor roadmap shall include CATS task progression.

3.10.5 DevSecOps

DevSecOps is an organizational software engineering culture and practice that aims at unifying software development (Dev), security (Sec) and operations (Ops). The main characteristic of DevSecOps is to improve outcomes and mission value by automating, monitoring, and applying security at all phases of the software lifecycle. A full


33


DevSecOps pipeline includes Continuous Integration, Continuous Delivery, Continuous Deployment, Continuous Operation, and Continuous Monitoring. The goal for the DevSecOps environment is to facilitate planning, coordination, execution, and delivery of an integrated system in one managed place through Agile software development processes. DevSecOps, in the context of TSS/TMT, are users and developers working together to enable rapid and frequent delivery of capabilities to the Warfighter to receive feedback that informs the requirement.

3.10.5.1 The vendor shall conduct DevSecOps discussions with current and future OTA vendors and the Government.

3.10.5.2 The vendor shall document their DevSecOps plan and provide to the Government NLT 30 days after contract award.

3.10.5.3 The vendor shall employ a transparent DevSecOps / Agile process involving the Government to plan, develop, build, test, secure, deploy, operate, and scale TSS/TMT.

3.10.5.4 The vendor shall coordinate and synchronize all phases and activities of STE system capability and interface vendors through the software factory.

3.10.5.5 The vendor shall design their DevSecOps process to employ a delivery pipeline that enables the systems to develop on cadence, release on demand, and conduct continuous integration and continuous delivery (CI/CD) with STE system capability and interface vendors to ensure an integrated STE system of systems.

3.10.5.6 The vendor shall release a fully integrated STE system that provides collective training value.

3.10.5.7 The vendor shall design their DevSecOps process to maximize automation for activities in develop, build, test, release, and deliver/field phases.

3.10.5.8 The vendor shall establish pass criteria, perform, and pass automated unit tests, regression tests, and automated interface tests as entry criteria for assessment events.

3.10.5.9 The vendor shall co-develop and/or review the automated test procedures with the Government to ensure they are accurate and complete.

3.10.5.10 The vendor shall present all automated test tools to the Testing System Team.

3.10.5.11 The vendor shall use automated security tools to ensure compliance with the continuous ATO process.

3.10.5.12 The vendor shall provide the Government source code, build scripts, and any other dependency necessary to independently build the application developed under the OTA at each MVP, MVCR, and each subsequent delivery to the Government in accordance with the deliverables (3.8.2.1).

3.10.5.13 The vendor shall deploy approved system configurations to the locations identified in Table 3-2 and Table 3-3.

3.10.5.14 The vendor shall provide the Government remote access to the system to install and access diagnostic, instrumentation, and test software to collect and view test data for each sprint, program increment, MVP, MVCR, and subsequent software releases.

3.10.5.15 The vendor shall recommend changes and improvements that increase the effectiveness of the STE DevSecOps processes and procedures.


34


DevSecOps metrics relate to measurements that provide insight into the organization’s delivery pipeline. They also include metrics that provide a high-level assessment of the organization’s ability to integrate, deliver, monitor, and restore products.

3.10.5.16 The vendor shall develop and track the following DevSecOps metrics and provide monthly updates to the Government in accordance with the deliverables (3.8.1.1):

• Mean Time to Restore (MTTR). MTTR measures how quickly a system or solution can be restored to functional use after a critical failure.

• Deployment Frequency. Deployment frequency provides information on the cadence of deployments in terms of time elapsed between deployments.

• Lead Time. This flow metric represents how long it takes to deliver a required solution.

• Change Fail Rate. Tracks defect count measures and returned stories per sprint or release.

3.10.5.17 Platform One

Platform One is the official DoD DevSecOps Enterprise service. Platform One facilitates efficient and effective coordination between development scrums and the Government. The vendor accesses Platform One using the internet. The Government will purchase services to have the STE DevSecOps pipeline hosted in Platform One. The CI/CD pipeline will use Platform One provided tools and products. Platform One may have the flexibility to support additional tools required for the STE DevSecOps process. Platform One hosted pipelines currently have access to:

• Plan & Develop: Jira, Gitlab, Github, Git.

• Build: Ant, Cmake, Maven, MSBuild, Gradle, Jenkins.

• Test: Selenium, Cucumber, Junit.

• Secure: Sonarqube, Nessus, Twislock, Fortify, Aqua, Qualys, Nexus, Archiva, Jfrog.

• Deploy & Operate: Ansible, Chef, Puppet, Helm, Salt, Operator SDK.

• Monitor: Nagios, Splunk, Sunsu, Kubernetes, Docker, and ELK Stack.

• Scale: Azure, AWS Gov Cloud, milCloud, and Google cloud.

The vendor can use the Government provided and managed Platform One DevSecOps environment, provide their own DevSecOps environment or implement a hybrid approach that employs both the Government provided Platform One environment and the vendor environment.

If the vendor implements the Government provided Platform One DevSecOps environment or a hybrid approach, the vendor shall identify and propose additional or


35


substitute tools (with rationale) required above and beyond Platform One that the vendor will procure and operate.

The vendor shall provide an option for 50 Government personnel access licenses for any vendor requirements, architecture or DevSecOps tools needed.

If the vendor implements their own DevSecOps environment, then the vendor shall provide the Government access to the plan and development, build, test, secure, deploy and operate, monitor, and scale tools.

If the vendor implements their own DevSecOps environment or a hybrid environment, then the vendor shall provide a process to transition codes, scripts, and executables and documentation of the vendor’s CI/CD pipeline operations and at the direction of the Government shall transition codes, scripts, executables, and automated testing to the Government environment.

3.11 Testing

Incremental Government testing occurs outside of the Agile process and will typically be associated with delivery of a program increment, MVP, MVCR, and subsequent software releases. Incremental Government testing includes:

• TA/Functional Verifications (FV).

• Soldier Touch Point (STP) / User Assessments (UA).

• Operational Testing (OT).

• Verification, Validation, and Accreditation (VV&A).

• Logistics Demonstration/Maintenance Evaluations (LD/ME).

3.11.1 Incremental Government Testing

3.11.1.1 The vendor shall enable, participate in, and support incremental Government testing that supplements Agile process and DevSecOps testing.

3.11.1.2 The vendor shall provide software and hardware to support incremental Government testing.

3.11.1.3 The vendor shall provide manuals and training support package for UA, OT, and VV&A in accordance with the deliverables (3.8.3.2 and 3.8.3.3).

3.11.1.4 The vendor shall develop test and evaluation plans which shall include an incremental test strategy in accordance with the deliverables (3.8.2.6 and 3.8.2.7).

3.11.1.5 The vendor shall allow the Government to review vendor test plans and metrics and to provide input on vendor testing methods to ensure the usability of vendor test data for Government purposes.

3.11.1.6 The vendor shall provide the Government access to the vendor’s test plans, testing, and test results to reduce the Government test burden in accordance with deliverables (3.8.2.6, and 3.8.2.7).

3.11.1.7 The vendor shall support Government training effectiveness assessments during the User Assessments to inform vendor design and performance trades.


36


3.11.1.8 The vendor shall document test/assessment objectives and known limitations for the full range of STE system capabilities and interfaces under test, irrespective of contributing vendor, in accordance with the deliverables (3.8.2.6, and 3.8.2.7).

3.11.1.9 The vendor shall meet the following program incremental test and assessment entry criteria:

The vendor shall pass automated unit tests as entry criteria for incremental test events.

Configuration of system under test has been defined and agreed to. All interfaces have been placed under configuration management or have been defined in accordance with an agreed to plan and a Software Version Description Document has been made available 10 days prior to completion of the software release.

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

All test and assessment reviews specific materials such as Government approved test plans, cases, and procedures have been available to all participants prior to conducting the review.

All known system discrepancies have been identified in accordance with an agreed to plan.

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

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

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

All applicable Cyber security requirements have been met (e.g., Interim Authority to Test approved).

3.11.1.10 The vendor shall meet the following incremental test and assessment entry criteria:

All Action Items to document situations and possible action where the technical approach does not appear to meet the specification requirement have been addressed, assessed, and agreed upon.

All required independent evaluators were involved and concur with the planned tests and expected results.

Adequate test plans completed and approved for the system under test.

Previous component, subsystem, system test results form a satisfactory basis for proceeding into planned tests.

Risk level identified and accepted by Program leadership as required.

3.11.2 Integration Environment

3.11.2.1 The vendor shall provide a development lab to facilitate vendor led testing and potentially portions of Government incremental testing as required.


37


3.11.2.2 The vendor shall use the Government Technology Integration Facility (TIF) for integration, demonstrations, assessments, and test and evaluations that replicates conditions of the operational environment.

3.11.2.3 The vendor shall use the Government integration environment at the Joint Development and Integration Facility (JDIF) for classified (up to SECRET, SECRET REL, SECRET NATO) integration, demonstrations, assessments, and test and evaluations.

3.11.3 Development Testing

3.11.3.1 The vendor shall develop a sprint and increment level test and evaluation plan NLT 30 days after contract award for the Government to approve in accordance with the deliverables (3.8.2.6, and 3.8.2.7).

The vendor shall update the test and evaluation plan NLT 30 days into each program increment, MVP, MVCR and subsequent software releases in accordance with the deliverables (3.8.2.6, and 3.8.2.7).

The test and evaluation plan shall address development testing, component testing, integration testing, sprint demonstrations, program increment demonstrations, MVP, MVCR, subsequent software release demonstrations of the integrated STE solution.

The vendor test and evaluation plan shall establish an integration and testing roadmap/plan with events/touchpoints and coordinate STE system capability and interface vendors’ dependencies through the Government.

The vendor test and evaluation plan shall include the Government in sprint cycles that include other vendors.

The vendor shall develop a RTM that traces all system requirements and features allocated to a given sprint, program increment, MVP, MVCR or subsequent software release; vendor provided, and Government approved test procedures; and vendor provided and Government approved measures of success.

The vendor shall support Environmental testing by providing hardware test assets and possible onsite support as required at an approved DoD/Army test agency facility.

3.11.4 Cybersecurity Tests and Events

3.11.4.1 The vendor shall support development of a multi-phased, test timeline and cyber test and evaluation plan in accordance with the deliverables (3.8.2.6, and 3.8.2.7).

3.11.4.2 The vendor shall adhere to the Director, Operational Test & Evaluation (DOT&E) Procedures for Operational T&E of Cybersecurity in Acquisition Programs Memorandum.

3.11.4.3 The vendor shall participate in and support Cybersecurity DT Events.

The vendor shall support Combat Capabilities Development Command Data and Analysis Center (CCDC-DAC) in coordination with (ICW) PM (Blue Team) and AEC Cooperative Vulnerability Identification (CVI) testing and provide the test data to the Government NLT 5 calendar days after the events in accordance with the deliverable (3.8.1.2).


38


The vendor shall support the Threat System Management Office (TSMO) ICW PM (Red Team) and AEC Adversarial Cyber Developmental Tests (ACDT) and provide the test data to the Government NLT 5 calendar days after the events in accordance with the deliverables (3.8.1.2).

The vendor shall provide Verification of Fixes (VoF’s) event(s) NLT 10 calendar days after the test is completed in accordance with the deliverables (3.8.1.2).

3.11.4.4 The TSS/TMT shall undergo Cybersecurity Operational Test events.

The vendor shall support Cooperative Vulnerability Penetration Assessments (CVPA) and provide CVPA test data to the Government NLT 10 calendar days after the test is completed in accordance with the deliverables (3.8.1.2).

The vendor shall support Adversarial Assessments (AA) and provide AA data to the Government NLT 10 calendar days after the assessment is completed in accordance with the deliverables (3.8.1.2).

The vendor shall support ATEC/AEC evaluations IAW the DOT&E Procedures for Operational T&E of Cybersecurity in the Acquisition Programs Memorandum.

3.12 Product Support

While each STE system will have their independent sustainment strategy, the STE system capability vendor’s sustainment concept shall provide interfaces to allow integration of operation and sustainment as a system of systems.

3.12.1 General

3.12.1.1 The vendor shall safeguard, securely store, and track Government furnished property (GFP) (i.e., GFI and GFE). Contractor Acquired Property (CAP) shall be considered as GFP and will be added to the GFP list after presentation of the DD250. The vendor can request additional GFI/GFE and the Government will evaluate and determine applicability.

3.12.1.2 The vendor shall perform the following to ensure positive control and safety of Government furnished items:

a. Examine upon receipt, consistent with practicality, to detect damage.

b. Provide storage that precludes deterioration.

c. Examine prior to installation, consistent with practicality, to detect damage.

d. Identify and protect from improper use or disposition.

e. Verify and audit quantities every quarter with 100% inventory annually.

3.12.1.3 The vendor shall provide a data library of source documentation and data used to create the TSS/TMT system and document it.

3.12.1.4 The vendor shall participate in the Government-led incremental logistics demonstrations/maintenance evaluations.

3.12.1.5 The vendor shall design the Product Support to support a third-party maintainer.

The system vendor shall provide transition of product support to another provider at the end of the contract period of performance.


39


3.12.1.6 The system vendor shall provide sustainment projections for the lifecycle management and affordability of the TSS/TMT solution.

3.12.2 Interim Contractor Support

3.12.2.1 The vendor shall provide Interim Contractor Support (ICS) starting with first hardware delivery to the Government and continue for at least 24 months after the final release of capability in accordance with contract options.

3.12.2.2 During the ICS period, the vendor shall repair/replace, as directed by the Government, defective TSS/TMT hardware, this includes performing warranty actions as needed.

3.12.2.3 During the ICS Period, the vendor shall process bug reports, conduct preventative and corrective maintenance, patch, and update delivered software as required.

3.12.2.4 The vendor shall document TSS/TMT system ICS.

3.12.2.5 During the ICS period, the vendor shall provide Helpdesk support.

3.12.3 Maintenance Planning/Concept

3.12.3.1 The vendor shall provide a prognostic health monitoring system that provides for continuous prognostic and preventative maintenance.

3.12.3.2 The vendor shall provide remote diagnostic capability to allow Helpdesk troubleshooting and corrective actions.

3.12.3.3 The vendor shall provide an automated built-in-test (BIT) functionality that runs at system startup and as selected by the maintainer/Helpdesk.

3.12.3.4 The vendor shall develop and document a 2-level maintenance concept that considers current field maintenance capabilities, and training audience level.

3.12.3.5 The vendor shall maintain and document software using the DevSecOps process.

3.12.4 Warranty

3.12.4.1 The vendor shall track and document warranties in accordance with the deliverable (3.8.3.11).

3.12.4.2 The vendor shall provide no cost warranty transfer to the Government or third-party maintainer.

3.12.4.3 The vendor shall purchase, as applicable, transferable extended warranties to coincide with the duration of the ICS period.

3.12.5 Technical Support Documentation

3.12.5.1 The vendor shall integrate the technical documentation (e.g. System/Software User Manuals, Operator Manuals, COTS manuals, Maintenance Manuals, engineering data, programmatic data, etc.) from OWT, SVT, SiVT and RVCT into the TSS/TMT system technical documentation providing a single source of integrated technical documentation.

3.12.5.2 The vendor shall host and participate in Government-led in-process reviews at 40% and 80% of document completion in accordance with the entry and exit criteria.

3.12.5.3 The vendor shall conduct a validation of the Technical Documentation, participate in a Government run verification of the Technical Documentation.


40


3.12.5.4 The vendor shall provide the Technical Documentation in interactive electronic format in accordance with the deliverables (3.8.3.1, 3.8.3.2, and 3.8.3.3).

3.12.5.5 The vendor shall document all COTS items and modified COTS items in accordance with deliverable (3.8.3.1).

3.12.5.6 The vendor shall document and provide a process to reboot the TSS/TMT hardware in accordance with the deliverables (3.8.3.2, and 3.8.3.3).

3.12.5.7 The vendor shall document common and special tools and test equipment, if applicable, in the Technical Documentation in accordance with the deliverables (3.8.3.2).

3.12.5.8 The vendor shall include integrated supporting documentation for the maintenance and operation training tools in the Technical Documentation in accordance with the deliverable (3.8.3.5).

3.12.6 Training

3.12.6.1 The vendor shall integrate TSS/TMT training products with training products from other STE system vendors and document the training in accordance with the deliverables (3.8.3.5, 3.8.3.7, and 3.8.3.10).

3.12.6.2 The vendor shall provide sufficient perpetual licenses for any commercial products to enable the continued TSS/TMT training development, modification, and operation.

3.12.6.3 The vendor shall provide a STE system “train the trainer” course for instructors/trainers and maintainers.

The vendor shall provide the STE training courses at five locations as identified in the fielding locations table.

The vendor shall accommodate a maximum of ten students for each STE training course including student course materials.

3.12.6.4 The vendor shall develop and document specific task videos covering critical and infrequent tasks for use as refresher and just in time training in accordance with the deliverables (3.8.3.5 and 3.8.3.10).

3.12.6.5 The vendor shall develop, document, and embed in the TSS/TMT system applications for use by the intelligent tutoring system to provide just in time and refresher training in accordance with the deliverables (3.8.3.5).

3.12.7 Item Unique Identification

3.12.7.1 The vendor shall apply and register Government approved Item Unique Identification labels to all material that will be delivered to the Government in accordance with MIL-STD-130 and the deliverable (3.8.3.6).

3.12.8 System Delivery

3.12.8.1 The vendor shall assist the Government with coordination of system delivery.

3.12.8.2 The vendor shall assist with the preparation of system delivery documentation.

3.12.8.3 The vendor shall prepare briefing slides documenting the system delivery process for each site.


41


3.12.8.4 The vendor shall conduct site surveys with the Government to determine suitability of the TSS/TMT system delivery location and any adjustments to the TSS/TMT system configuration that will be required prior to delivery.

3.12.8.5 The vendor shall participate in telephone Site Readiness Review meetings as determined by the Government to coordinate with the TSS/TMT system receiving site in the months prior to delivery.

3.12.8.6 The vendor shall conduct site installation.

3.12.8.7 The vendor shall conduct site testing.

3.12.8.8 The vendor shall conduct site training.

3.12.8.9 The vendor shall conduct site daily reporting.

3.12.8.10 The vendor shall conduct site daily briefs.

3.12.8.11 The vendor shall cleanup and remove debris left over from the installation activities prior to departing the installation site.

3.12.8.12 The vendor shall be responsible for repair of any damage caused by their personnel or equipment during the installation activities.

3.12.8.13 The vendor shall incrementally demonstrate the product support processes with the resources needed to operate and sustain the system during TAs, UAs, and Operational Tests.

The vendor shall incrementally demonstrate the documented TSS/TMT setup procedures during the TAs, UAs, and Operational Tests.

The vendor shall incrementally demonstrate the documented procedures for execution of a mission during the TAs, UAs, and Operational Tests.

The vendor shall incrementally demonstrate representative field and depot maintenance (using the technical documentation) that returns the TSS/TMT from failure to full operating status during the TAs, UAs, and Operational Tests.

The vendor shall incrementally demonstrate preparing the TSS/TMT system for transportation during the TAs, UAs, and Operational Tests.

The vendor shall incrementally demonstrate the storage process during the TAs, UAs, and Operational Tests.

The vendor shall incrementally demonstrate the shipping processes during the TAs, UAs, and Operational Tests.

3.13 Security

3.13.1 Industrial Security

Any contractor (prime or sub) that is a Foreign Owned, Controlled, or Influenced (FOCI) company that does not have their FOCI mitigated by the Defense Counterintelligence and Security Agency (DCSA) and who does not possess a Facility Clearance Level (FCL) by submission of their Demonstration Plan, cannot prime this contract.

3.13.1.1 The vendor shall meet security requirements as instructed in form DD254.

3.13.1.2 The vendor shall develop a TSS/TMT system that complies with the RMF, the cybersecurity plan, and local security policies.


42


3.13.1.3 The highest level of classification required for this effort is: SECRET / SECRET REL. The multiple nodes exist in a variety of security enclaves, including unclassified, SECRET, and SECRET REL.

3.13.1.4 The vendor shall meet all applicable security requirements for protecting controlled unclassified information and secret information.

3.13.2 Cybersecurity

The vendor ensures that the TSS/TMT complies with applicable DoD Cyber Survivability Endorsement, Volumes I-III, Cyber Survivability Endorsement Implementation Guide and establishes safeguards IAW all cybersecurity related policies, regulations, and the DoD’s best business practices to include:

• DoDI 8500.01Cybersecurity.

• DoDI 5200.44 Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN).

• AR 25-2.

• DoDD 8140.01 Cyberspace Workforce Management.

• DoD 8570.01-M Information Assurance Workforce Improvement Program.

• DA PAM 25-2-6 Cybersecurity Training and Certification.

• DA PAM 25-2-7, Army Information System Privileged Access.

• NIST 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.

See Appendix E Cybersecurity for the CDS phases flowchart.

3.13.2.1 Cyber Survivability

The vendor shall comply with DoD Cyber Survivability Endorsement, Volumes I-III, Cyber Survivability Endorsement.

The vendor shall respond to cybersecurity tasking orders, as directed by the Government, provided by organizations such as NETCOM's 7th Signal Command, DOD CIO G6 and US Cyber Command.

The vendor shall manage vulnerabilities to maintain cyber survivability capabilities (e.g., automated patch management, mitigation of known threats, and effects of obsolescence).

3.13.2.2 Risk Management Framework

The vendor shall comply with all required DoD and Army regulations (e.g., DoDI 8510.01 RMF for DoD IT, Committee on National Security Systems Instruction (CNSSI) 1253, the National Institute of Standards and Technology (NIST) SP 800-53, and Army Regulation AR 25-2) to implement and document the cybersecurity requirements, processes, and procedures to meet the Confidentiality, Integrity, and Availability impact levels of Moderate-Moderate-Low.

The vendor shall mitigate or fix all category 1 (CAT1) noncompliance items as directed by the Government within 30 days of submission to the Package Approval Chain.


43


The vendor shall be Army Endpoint Security System (AESS) compliant.

The vendor shall develop and maintain the functional architecture/topology diagram, authorization boundary diagram, and data flow diagram, using the NETCOM template format.

The vendor shall review and support the system categorization.

The vendor shall plan, resource, and document the RMF Assessment and Authorization (A&A) for the test and development enclaves and fielding sites IAW Table 3-2 and Table 3-3.

The vendor shall produce all components of the required RMF packages (i.e. IATT, ATO) necessary to test, develop, deliver, and operate an authorized system in accordance with the deliverables (3.8.1.2).

The vendor shall evaluate and document all system, interfaces and network changes that impact security in accordance with the deliverables (3.8.1.2).

The vendor shall develop and maintain the system cybersecurity artifacts required by RMF, DoD, DoDI, and NIST regulations, guidelines, and controls (e.g., Security Plan (SP), Continuity of Operations Plan (COOP), Contingency Plan (CP), Incident Response Plan (IRP), CMP, Standard Operating Procedures (SOP), eMASS Control Self-Assessment test results input, Ports, PPSM document) in eMASS in accordance with the deliverables (3.8.1.2).

The vendor shall create and maintain the System RMF authorization documentation, processes, and assessments in eMASS to achieve the fielding and DT&I sites RMF Authorizations (i.e. IATT, ATO) in accordance with the deliverables (3.8.1.2). Note: Secure Internet Protocol Routing (SIPR) eMASS instance is required for classified systems.

The vendor shall complete the eMASS RMF Implementation Plan in accordance with the deliverables (3.8.1.2).

The vendor shall develop a Continuous Monitoring Plan and update the System-level Continuous Monitoring (SLCM) Strategy in eMASS in accordance with the deliverables (3.8.1.2).

The vendor shall input RMF data into eMASS; ports, protocols, and services management (PPSM) registry, Army Portfolio Management Solution (APMS) and other database repositories as required by DoD directives and instructions in accordance with the deliverables (3.8.1.2).

The vendor shall develop and maintain hardware and software lists in eMASS that include version(s), vendor(s), vendor addresses, vendor phone numbers, release dates, license(s), certifications dates, termination or authorization dates, and authorization expiration dates in accordance with the deliverables (3.8.1.2).


44


The vendor software development and integration shall comply with RMF practices and guidelines for the Enclave Test and Development (T&D) Security Technical Implementation Guide (STIG) to achieve Development, Test, and Integration (DT&I) environment RMF authorizations (i.e., IATT and ATO) for the management and storage of TSS/TMT related data. Note: DT&I environment RMF authorization is required to host or interoperate with GFE/GFI products such as MCIS, software applications such as LVC-IA, and authoritative data sources such as ATIS. DT&I environment RMF authorization is required to establish external connections with the Federal, State, and University Network (FEDSUN) that provides access to the Defense Research Engineering Network (DREN) and NIPRNET.

The vendor shall coordinate with the Government to obtain the TSS/TMT system authorization from the AO 30 days prior to deploying to test and development enclaves and fielding sites IAW Table 3-2 and Table 3-3.

The vendor shall employ current Army Best Practice scanning and remediation monthly.

The vendor shall ensure log files and audits are collected, maintained, and reviewed for all systems.

The vendor shall audit authentication policies (e.g., password) policies for compliance.

The vendor shall review Audit Logs for alarms.

The vendor shall ensure the Information Assurance Vulnerability Alert (IAVA) and STIGs can be applied individually when needed without the need to re-image the system.

The vendor shall develop an automated patch management plan that includes IAVA implementation by due date.

The vendor shall implement all hardware, network, and software STIGs.

The vendor shall develop an automated patch management plan that implements new DISA STIGs NLT 30 days after the STIG release. Note: DISA releases updates and new STIGS on a 90-day cycle.

The vendor shall document the system's Cybersecurity Deviation Report for Government approval for all updates that cannot be applied within 30 days in accordance with the deliverable (3.8.1.2).

The vendor shall report all IAVA, STIGs, and Bulletins in a system Plan of Action and Milestone (POA&M) that includes a list those implemented, those not implemented, justification for items not implemented, and mitigation for those not implemented at least monthly, or more frequent if directed by the local AO.

The vendor shall document all IAVA, STIGs, Bulletins, and security control implemented, not implemented, justification for items not implemented, impacts, and mitigations in the POA&M in eMASS at least monthly, or more frequent as directed by the local AO.

The vendor shall ensure cybersecurity posture and accreditation boundaries are not impacted during support and maintenance.


45


The vendor shall ensure that security changes do not invalidate any authorized accreditation.

3.13.2.3 Cross Domain Solution Authorization (CDSA)

The vendor shall design, use, and support the authorization of the selected CDS in a secure, enterprise environment IAW DoDI 8540.01 and Chairman Joint Chiefs of Staff Instruction (CJCSI) 6211.02D.

The vendor shall define data flowing through the CDS within 60 days of OTA award to support ACDMO questionnaires for Phase 1.

The vendor shall support the CDSA waiver artifact development, testing, and authorization processes for each required security.

3.13.2.4 Cybersecurity Incident Reporting

The vendor shall develop a program IRP in compliance with PEO STRI and Army IRP procedures NLT 30 TBD days after contract.

The vendor shall comply with the IRP when responding to a cybersecurity related incident.

3.13.2.5 Cybersecurity Training

The vendor shall deny access to DoD information systems when contractor personnel do not have proper and current certifications.

The vendor shall provide evidence of DOD cybersecurity awareness requirements compliance, in accordance with 8570.01-M and DoDD 8140.01 Cyberspace Workforce Management for the category and level functions in which they are performing within 10 days of contract award.

The vendor shall verify employees have at least 3 years' cybersecurity or related experience (e.g., operating systems, network devices, database) for the system being managed at the moment of hiring.

The vendor shall have up to six months to obtain the remaining employee certification or training qualifications for their position IAW DoD 8570.01-M.

The vendor cybersecurity personnel shall establish an Army Training and Certification Tracking System (ATCTS) account, in accordance with AR 25-2. The Government ISSM will manage the vendor training and certification requirements on the ATCTS website (https://atc.us.army.mil). ATCTS will be used to ensure that users' profiles are current and correct with all applicable documentation, to include completed DD Form 2875 (System Authorization Access Request (SAAR)), annually signed user agreement, applicable training certificates, and, as applicable, DA Form 7789 (Privileged Access Agreement and Acknowledgement of Responsibilities), appointment memoranda, and records of professional certifications.

The vendor shall provide the Government verification that Cybersecurity/IT personnel meet the baseline certification requirements established in the DoD 8570.01-M and DoDD 8140.01 Cyberspace Workforce Management for the category and level functions in which they are performing by contract award and update monthly after contract. Approved baseline certifications and a list of cybersecurity workforce certification providers is available at: https://public.cyber.mil/cw/cwmp/dod-approved-8570-baseline-certifications/.


46


The vendor shall document information assurance certification status for TSS/TMT personnel performing information assurance functions and provide to the Government NLT 10 days after contract award and update monthly.

3.14 Safety and Health

The vendor complies with Federal, State, and local environmental laws and regulations, Executive Orders, treaties, and agreements required to maintain a safe and non-hazardous occupational environment. The TSS/TMT design complies with all applicable safety and health requirements and prevent any safety and health hazards to the operator or maintenance personnel throughout its life cycle. The TSS/TMT design and operational characteristics minimize the possibilities for accidents caused by human error or system failure.

3.14.1 Safety

3.14.1.1 The vendor design shall comply with the following standards and publications to optimize system performance and to prevent safety, health, environmental, ergonomic, and software/firmware (to include modifications updates and new system interfaces) hazards.

• MIL-STD-1472, Human Engineering Design Criteria, Principles, and Practices.

• MIL-STD-882E, DoD Standard Practice, System Safety.

• DA PAM 385-30, Safety Risk Management Technical Bulletin (TB) 43-0134 (Battery Disposition and Disposal).

• AR 385-10 The Army Safety Program and Army Pamphlet (DA Pam) 385-16 System Safety Management Guide.

3.14.1.2 The vendor shall document all known software and hardware hazards using the US Army Risk Management process in a Hazard Tracking Log and provide to the Government.

3.14.1.3 The vendor shall provide data required for event safety releases not later than 20 calendar days prior to Soldier involved assessment events.

3.14.1.4 The vendor shall provide a Safety Assessment Report that quantifies all known hazards IAW MIL-STD 882E.

3.14.1.5 The vendor shall provide a safety lead to participate in the program System Safety Working Group.

3.14.2 Health

3.14.2.1 The vendor shall provide a Health Hazard Assessment (HHA) to the Program Office 45 days prior to each program increment, MVP, MVCR, and subsequent software releases to identify, assess, and provide mitigation of potential health hazards as required by AR 40-10, Health Hazard Assessment Program in Support of the Army Acquisition Process.

3.14.2.2 The vendor HHA shall identify and assess health hazards associated with the life cycle management of materiel systems and provide recommendations to the Program Office to eliminate or control system hazards.


47


References

# Reference Title Web Location

1 29 CFR 1910.147 “The Control of Hazardous Energy (Lockout/Tagout)” June 2011

https://www.energy.gov/sites/prod/files/2013/06/f1/29cfr-1910-147_ssm.pdf

2 ADP 5-0 “The Operations Process” 17 May 2012

https://armypubs.army.mil/ProductMaps/PubForm/ADP.aspx

3 ADRP 5-0 “The Operations Process” 17 May 2012

https://armypubs.army.mil/ProductMaps/PubForm/ADRP.aspx

4 AR 25-2 "Army Cybersecurity" 4 April 2019 https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN17503_AR25_2_Admin_FINAL.pdf

5 AR 40-10 "Health Hazard Assessment Program in Support of the Army Acquisition Process" 27 July 2007

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/AR%2040-10.pdf

6 AR 70-38 “Research, Development, Test and Evaluation of Materiel for Extreme Climatic Conditions” 26 June 2020

https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN30017-AR_70-38-000-WEB-1.pdf

7 AR 385-10 "The Army Safety Program" 24 February 2017

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN16777_ARN16343_AR385_10_FINAL.pdf

8

Army Training and Certification Tracking System (ATCTS)

Army Training and Certification Tracking System (ATCTS)

https://atc.us.army.mil

9 CADE Cost Assessment Data Element (CADE) website

http://cade.osd.mil

10 Certifications Cybersecurity Workforce Certifications

https://public.cyber.mil/cw/cwmp/dod-approved-8570-baseline-certifications/

11

Chairman Joint Chiefs of Staff Instruction (CJCSI) 6211.02D

“Defense Information Systems Network (DISN) Responsibilities” 24 January 2012 current 4 August 2015

https://www.jcs.mil/Portals/36/Documents/Library/Instructions/6211_02a.pdf?ver=2016-02-05-175050-653

12

Committee on National Security Systems Instruction (CNSSI) 1253

"Security Categorization and Control Selection for National Security Systems" 27 March 2014

https://www.dcsa.mil/portals/91/documents/ctp/nao/CNSSI_No1253.pdf

13

Cyber Survivability Endorsement Implementation Guide

Cyber Survivability Endorsement Implementation Guide

14 DA PAM 25-2-6 "Cybersecurity Training and Certification" 8 April 2019

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN16685_DAPam25_2_6_FINAL.pdf





48



15 DA PAM 25-2-7 Army Information System Privileged Access" 8 April 2019

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN17343_P25_2_7_Admin_FINAL.pdf

16 DA PAM 385-16 "System Safety Management Guide" 13 August 2013

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/p385_16.pdf

17 DA PAM 385-30 "Safety Risk Management" https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/p385_30.pdf

18 DoD 8570.01-M

"Information Assurance Workforce Improvement Program" 19 December 2005with change 4 10 November 2015

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/857001m.pdf

19 DoD Agile Metrics Guide

"DoD Agile Metrics Guide, Strategy Considerations and Sample Metrics for Agile Development Solutions Version 1.1" dated 23 September 2019

https://www.dau.edu/cop/it/DAU%20Sponsored%20Documents/Agile%20Metrics%20v1.1%2020191122.pdf

20 DoD DevSecOps Reference Guide

“DoD Enterprise DevSecOps Reference Design Version 1.0” 12 August 2019

https://dodcio.defense.gov/Portals/0/Documents/DoD%20Enterprise%20DevSecOps%20Reference%20Design%20v1.0_Public%20Release.pdf?ver=2019-09-26-115824-583

21

DoD Cyber Survivability Endorsement, Volumes I-III

DoD Cyber Survivability Endorsement, Volumes I-III

22 DoDD 8140.01 "Cyberspace Workforce Management" 11 August 2015 with change 1 31 July 2017

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/814001p.pdf

23 DoDI 8500.01 "Cybersecurity" 14 March 2014 with change effective 7 October 2019

https://www.esd.whs.mil/portals/54/documents/dd/issuances/dodi/850001_2014.pdf

24 DoDI 8510.01 "Risk Management Framework for DoD Information Technology” 28 Jul 2017

https://www.esd.whs.mil/Directives/issuances/dodi/

25 DoDI 8540.01 "Cross Domain Policy" 8 May 2015 with change 1 28 August 2017.

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/854001p.pdf

26 DoDI 5200.44

"Protection of Mission Critical Functions to Achieve Trusted Systems and Networks" 5 November 2012, with change 3 15 October 2018

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520044p.pdf

27 DOT&E Memorandum

"Procedures for Operational T&E of Cybersecurity in Acquisition Programs" 3 April 2018

https://www.dote.osd.mil/Portals/97/pub/policies/2018/20180403ProcsForOTEofCybersecurityInAcqProgs(17092).pdf

28 Enterprise Cloud Management Office (ECMO)

ECMO Policies and Strategies https://www.milsuite.mil/book/groups/enterprise-cloud-management-office-ecmo/overview

https://www.milsuite.mil/book/groups/enterprise-cloud-management-office-ecmo/overview




49



29 FM 7-0 “Train to Win in a Complex World” 5 October 2016

https://armypubs.army.mil/ProductMaps/PubForm/FM.aspx

30 MIL-STD-882E "DoD Standard Practice, System Safety" 11 May 2012

http://acqnotes.com/acqnote/tasks/mil-std-882e-system-safety

31 MIL-STD-1472G Change 1

“Human Engineering Design Criteria, Principles, and Practices w Change 1 17 January 2019

http://everyspec.com/MIL-STD/MIL-STD-1400-1499/MIL-STD-1472G_CHG-1_56051/

32 MOSA Implementation Guide

"Modular Open Systems Approach (MOSA) Implementation Guide Version 1.0" 10 June 2020

33 MOSA Reference Frameworks

"Modular Open Systems Approach (MOSA) Reference Frameworks in Defense Acquisition Programs" May 2020

https://ac.cto.mil/wp-content/uploads/2020/06/MOSA-Ref-Frame-May2020.pdf

34 NIST SP 800-53

"National Institute of Standards and Technology (NIST) SP 800-53 Rev 5 Security and Privacy Controls for Information Systems and Organizations" September 2020

https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final

35 NIST SP 800-171

"National Institute of Standards and Technology (NIST) SP 800-171 Rev 2 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations" February 2020

https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-171r2.pdf

36 PART Program Assessment Review Tool

http://www.acqnotes.com/Attachments/MOSA%20Program%20Assessment%20and%20Review%20Tool%20(PART).xls

38 TB 43-0134 "Battery Disposition, Handling and Disposal" 30 May 2018

https://liw.logsa.army.mil/etmapp/api/general/search/084893/0/pdf


A-1


Appendix A Capability Descriptions

A.1 One World Terrain

One World Terrain delivers a 3D global terrain capability and associated information services that support virtual replication of the physical Earth and complexities of the operational environment in support of training as provisioned through the Army's Synthetic Training Environment and dynamically rendered at the PoN. Specifically, OWT provides a synthetic/virtual World representation that supports land, air, maritime, and space operations to facilitate multi-domain operations; a well-formed format that is consumable by standard commercial tools and technologies; automatic processing of raw terrain data into the well-formed format; and a terrain configuration management capability that incorporates approved geospatial information updates and local terrain surveys back into the OWT foundational repository.

A.2 Reconfigurable Virtual Collective Trainer

The RVCT hosts the physical platform elements (e.g., cyclic, collective pedals, steering wheels, switches). The RVCT physical controls will interface with the TSS API through the platform abstraction layer. The TSS will contain a functional virtual representation of the RVCT platforms. For example, the TSS will contain the inside of an Apache helicopter visually displaying the interior of the cockpit with all the switches needed for collective training being functional (think game console or PC game). The RVCT vendor will provide 3D interior platform models and supplement the TSS virtualized hardware components and functionality with physical hardware to create the appropriate fidelity for the RVCT end user.

RVCT Initial Operational Capability (IOC) and Full Operational Capability (FOC) Definitions for the current increment

IOC Definition and target date IOC attainment is projected to occur in Fiscal Year (FY) 2022, subject to change based on the rate of progress of development of the material solution. IOC is defined as the first fielding and acceptance of the RVCT capability by an installation. It is further defined as:

• All RVCT components have completed the verification, validation, and accreditation process prior to IOC.

• All RVCT equipment is fielded to the first installation site and accepted.

• All Information Assurance (IA) requirements are complete.

• New Equipment Training (NET) at the first site is complete.

• Network Enterprise capabilities are sufficient to support the STE-IS capabilities to include RVCT.

• All product support requirements for RVCT operations and support are in place and ready to support unit training at the first site.

RVCT FOC Definition and target date


A-2


FOC attainment is projected to occur in FY 2027. FOC is achieved when the Basis of Issue Plan (BOIP) for the RVCT has been fielded to all sites (post, installation, armory, and institution) scheduled for fielding and all sites have accepted their associated RVCT equipment.

FOC is further defined as:

• Meets or exceeds all threshold requirements.

• All equipment associated with the RVCT has been fielded, in accordance with the APO and BOIP.

• All IA requirements are complete.

• Network Enterprise capabilities to support the STE-IS capabilities, including RVCT.

• New Equipment Training (NET) at all sites is complete.

• All product support requirements for RVCT operations and support are in place and ready to support unit training at all sites.

• The RVCT sustainment plan is in place and being executed.

A.3 Live Virtual Constructive Integrating Architecture

LVC-IA is a net-centric linkage that collects, retrieves, and exchanges data among TADSS and Joint and Army Mission Command Systems. LVC-IA defines “how” information is exchanged among TADSS and Mission Command Systems. It enables the live, virtual, constructive training audience to see the common operating picture and to communicate using organizational command and control equipment. LVC-IA provides the common protocols, specifications, standards, and interfaces that help standardize common LVC components and tools required for interoperability of LVC components for simulations/stimulation (SIM/STIM) of unit MCS for training.

A.4 Mission Command Information Systems

The Army employs the Command Post Computing Environment (CPCE) in operations. It must do so also in training to help retain the knowledge and expertise in MCIS employment, contributing to the maintenance of (digital) readiness. Their inclusion in training is also consistent with the Army viewpoint of train as you fight.

The solution software system design shall seamlessly integrate and maintain concurrency with the COE, MCIS, and Operational Platforms. The software system design shall provide flexible, extensible data models and interfaces (i.e. API, Software Development Kits [SDK], Command Line Interfaces [CLI], Web Interfaces, and Graphical User Interfaces) that foster interoperability and integration while maintaining synchronization of data across all components of the STE. The solution software system design shall be loosely coupled to support the upgrade and, when necessary, the replacement of STE modules. The full list of MCIS is located within the TDP Appendix F SRD.


A-3


A.5 Avionics Software Emulation

AvSE is tactical or emulated software that provides the functionality of the Operational Flight Program (OFP) and flight model to simulate flying the aircraft. Each platform has a unique instantiation of the AvSE, and some include sensor models.

A.6 Common Software Library

The CSL is a software component for Army ground vehicle trainers which replicates vehicle functionality using vehicle source code. The process of creating a CSL removes hardware specific code to allow training devices to replicate vehicle functions and simulate vehicle performance using common PC hardware. Use of a CSL for vehicle trainers ensures high functional fidelity for the training audience and helps maintain concurrency with the current fielded platform.

A.7 Army Training Information System

The enterprise ATIS provides a common operational picture of the training environment through integrated, interoperable training development, management, scheduling, and delivery capabilities. These capabilities will enable Commanders, leaders, Soldiers, and civilians to better understand, visualize, describe, direct, lead, and assess training requirements so they can more effectively plan, prepare, execute, and assess training. End result is a system that enables Soldiers to train as they will fight, so they can effectively fight as they have trained. ATIS includes the following five major capabilities:

Army Training Management Capability. Provides individual and collective training managers ability to manage Training & Education information, including military individual and collective training that supports mission tasks; provides users centralized access to unit training management and their individual training records.

Training Enterprise Scheduling Capability. Provides unit leaders, installation leaders, training managers, trainers, and instructors ability to submit and manage schedule requests for Training & Education resources, including transportation, classrooms, ranges, supplies, and mandated legal and social individual and unit training usage. Scheduling enabler for Training & Education.

Training Resource Management Capability. Provides leaders, training managers, training developers, trainers, and instructors ability to manage inventory and sustainability of Training & Education enablers (i.e. ranges, classrooms, simulators). Managerial enabler for tracking availability and utilization for Training & Education.

Army Training Development Capability. Provides training developers and training managers the ability to develop and coordinate Training & Education information, including training packages, training events, courses, and exercises in support of the training development enterprise.

Army Learning Content Management Capability. Provides trainers and instructors a single source to deliver Training & Education information, including educational and professional instruction, to students anytime, anywhere; provides users centralized


A-4


access to Training & Education information necessary to conduct training missions. Provides trainers and instructors a single source to deliver Training & Education information, including educational and professional instruction, to students anytime, anywhere; provides users centralized access to Training & Education information necessary to conduct training missions

A.8 Soldier Virtual Trainer

The SVT will provide individual weapons skill development; enables Joint Fires training; and exercises Use of Force decision making. The SVT is enabled by the STE and is a virtual immersive trainer that combines and integrates several individual Soldier training capabilities, Weapon Skills Development (WSD), Joint Fires Training (JFT), and Use of Force (UoF), into a single capability that can be used simultaneously or individually. The WSD provides immersive capability to meet individual/crew weapons training in support of Army integrated weapon training strategies (IWTS). The JFT provides certification and qualification of Joint Fires Observers (JFO) IAW with TC 3-09.8. This includes the training of Joint Terminal Attack Controllers (JTAC) types I, II, and III close air support IAW TC 3-09.8 and the JFO and JTAC Memorandums of Agreement. Additionally, the SVT provides UoF training that enables Soldiers to exercise cognitive functions including rapid decision making and target acquisition under stress, including the introduction/removal of verbal interactions.

A.9 Integrated Visual Augmentation System / Squad Immersive Virtual Trainer

The IVAS is an operational capability that uses mixed reality goggles, wearable compute, and a network bubble. PEO Soldier is the IVAS materiel developer. SiVT software provides the IVAS display an augmented reality view that enables the overlay of Synthetic objects (e.g., virtual soldiers and platforms) and effects (e.g., virtual cratering) on the real-world terrain. This converges Live and Synthetic training in the local training area (LTA). SiVT software adjudicates all activities in the 200-meter box in the stand-alone mode. When part of a larger training event, SiVT will interoperate with the TSS software on the TSS/TMT Edge Node in the NEC. Details of this interoperability must be investigated.

A.10 STE - Live Training System

The STE-LTS will enable a true representation of real combat to ensure a multi-domain operation ready force. The STE-LTS will integrate Live training with the STE and ensure interoperability with Joint and Coalition partners. The STE-LTS will modernize both force on force and force on target training with the development of the 12 Engagements and 5 Instrumentations. The Engagement Types are: Direct Fire, Counter-Defilade Fire, Indirect Fire, Dropped Objects, Placed Objects, Thrown Objects, Guided and Autonomous Weapons, Direct Energy and Radiant Energy Weapons, Plumes, and Connections (Information Warfare). The "Plus 5" Instrumentation enablers are: Calculations, Network, Sensors, Terrains, and Transmitters. The STE-LTS will provide


A-5


representation of Soldier and weapon capabilities, vulnerabilities, and battlefield effects from the individual Soldier up to the BCT level. This includes an appropriately sized and equipped OPFOR and will include Echelons above Brigade elements, as well as aviation and Special Operations Forces assets. The Twelve engagement types named above will be supported in near-real-time using the five instrumentation capabilities. Physics-based munition trajectory simulations will replace current MILES Probability of Hit (Ph)/Probability of Kill (Pk) tables. The STE-LTS will allow the simulation of all weapon systems in near-real-time; include virtual targets and player avatars in Synthetic Training Environments; and enable post-engagement AARs delivered to training units during training exercises. The STE-LTS will replace the current live training capabilities to include Home Station and maneuver Combat Training Centers (CTC), and deployed training sites of instrumentation systems, engagement capabilities, and range systems. This future system will interface with the STE architecture in native manner; leveraging the Live Training Transformation (LT2) architecture, providing the seamless exchange of content between live and simulated virtual and constructive environments for purpose of integrated EXCON, AAR generation and delivery, Networked Targetry for training on all weaponry from Soldier to BCT echelons with EAB supporting elements and Networked Tactical Engagement Simulation System (TESS) capability collecting real-time Training Performance Data (TPD).


B-1


Appendix B Objective Values

The TSS/TMT PWS objective is to provide a Soldier/Squad through Brigade collective training capability that performs at least as proficient as the existing ITE and collective training capabilities (i.e., CCTT, AVCATT, and GFT) and a Brigade and below constructive staff training capability. The FOC is outside the scope of this Agreement, however, it is identified in this appendix as an “objective value” to provide a holistic STE vision. Objective values scale up to ASCC.

Table B-1. Objective Values.

ID Category Objective

OBJ 1 Interoperability

The TSS/TMT shall support the Intelligence Warfighting Function by interoperating with IEWTPT via APIs and appropriate classified networks (s).

OBJ 2 OWT 3D Objects correctly attributed for simulation training and mission rehearsal needs.

OBJ 3 OWT Integrate and Base globe Complete (World Geodetic System (WGS)-84, greater than 1m) to support full global coverage and mission rehearsal needs.

OBJ 4 OWT Implement OWT Data Model (logical, physical, and conceptual) and External interfaces / API defined that enable integration and information exchanges.

OBJ 5 OWT Import training and other locations glTF 3D tiles terrain set (enhanced base globe, 20cm to 1m).

OBJ 6 OWT Integrate High Resolution insets (Exterior, Interior, 20cm or better). OBJ 7 OWT Integrate and import vegetation biome point features.

OBJ 8 OWT OWT shall produce JLCCTC and Next Generation Constructive Capability terrain within 4 days (96 hours).

OBJ 9 OWT OWT produces terrain for and HITS via LVC-IA.

OBJ 10 OWT

OWT rapid terrain capture shall ingest data from a Squad-equipped UAS (fixed or rotary-wing) with RGB cameras (1in sensor, 3x optical zoom) capable of 90 min flight time, autonomous flight planning and redundant, robust return-to-home features. Range of 15km. FMV-compatible (10 km range). 3-axis gimbal (pitch, roll, yaw).

OBJ 11 OWT OWT rapid terrain capture shall enable PoN photogrammetric processing capabilities - i.e. local compute.

OBJ 12 OWT OWT rapid terrain capture shall enable Classification software to detect and extract features of interest: roads, surfaces, buildings, apertures, threads, change detection, urban clutter, people, vehicles, weapon systems.

OBJ 13 OWT OWT rapid terrain capture shall enable Synchronization of data back to Enterprise Grid on both low and high side.

OBJ 14 OWT OWT rapid terrain capture shall enable Data outputs: gltf/3dtiles, kmz, ortho, dsm.

OBJ 15 TMT

The Training Management Tools are aligned with the DOD's Advanced Distributed Learning Initiative. The ADL created the Total Learning Architecture around common set of data standards, business rules, governance rules, and policies. By aligning the STE TMT to the TLA, CFT takes advantage of the background research and development needed to make a functional distributed training system at PoN.

OBJ 16 TMT

TMT will use an intelligent tutoring system in support of training readiness execution and outcomes. The intelligent tutor may be initiated by a human or may be automated if the number of simultaneous trainees is too large for the available training managers to surveille effectively. The intelligent tutor will be able to assess current knowledge elements.


B-2



OBJ 17 TMT The TMT shall interoperate with real world mission command systems up to the ASCC (Joint/MN).

OBJ 18 TMT The TMT shall interoperate with ATIS and other authoritative data sources to develop the training simulation.

OBJ 19 TMT

The TMT will have the ability to consume data from the other parts of the CSE, namely the RVCT - A/G/S to measure individual and unit performance measures. This data will be described in the TMT object data model (ODM) and stored in a common TMT database.

OBJ 20 TMT

For each event, a common TMT database will be the repository of data produced for that event. The data described in the extended training support package (TSP), such as Task Measures and Steps, will be analyzed to track unit training performance over time. The results from the data collected in the TSS will be stored in the TMT database and later transmitted to the ATIS for individual and collective record management.

OBJ 21 TMT

The TMT ODM will contain at a minimum all the data elements needed to create a TSP. The TMT ODM will also include all the data elements needed to support the calculation of readiness per the Standards of Training Performance in accordance with FM 7-0 and AR 350-1. This new data document will be referred to as an extended TSP.

OBJ 22 TMT

The vendor will document pedagogical guidance for how the TMT is to be used in an instructional setting. Instructional design will include guidance for scenario design, initialization and utilization of the intelligent tutoring system, and utilization of the after-action review software.

OBJ 23 TMT

The TMT shall support two operational modes. The preferred operational mode is cloud delivery know at "platform as a service", where the TMT is comprised of network-based applications that are pre-configured to work with the TSS, RVCT's, OWT, etc. The second mode is a disconnected mode which an offline mode, where the network-based applications are hosted on local server assets but operate in an identical manner as the cloud delivery mode. In this mode of operation, all scenario and training data is housed on locally hosted storage until reconnected to Army networks or until copied manually to authoritative servers.

OBJ 24 TMT The TMT may employ user-assistive technologies to ensure all steps are correctly completed during a phase of the PPEA workflow.

OBJ 25 TMT

TMT provisions all the software services across the PPEA workflow. These software services include those required by TSS prior to the execution of the scenario and not limited to "All static Information" network, MCIS, synthetic, LIVE systems and or STE "systems admin data collection and management".

OBJ 26 TMT TMT collects and manages all data/services during all phases of the PPEA workflow including managing all changes to the OE.

OBJ 27 TMT TMT will provide data/interoperability services and management thereof across the PPEA.

OBJ 28 TMT

The STE shall provide a TMT that represents the Army Operations Process consistent with FM 7-0, FM 6.0, ADP 5-0, and ADRP 5-0 (The Operations Process) at the PoN to plan, prepare, execute, and assess collective training from Squad through ASCC.

OBJ 29 TMT The TMT shall update Soldier records based on completed training.

OBJ 30 TMT TMT manages OWT edits and use of terrain for a particular training event instance depending on the need of the instance scenario. TMT will maintain instance edits and modification for the life of the instance/scenario.


B-3



OBJ 31 TMT The TMT serves as the primary user interface into the STE and must be intuitive and easy to use, requiring zero specialized or formal training to operate.

OBJ 32 TMT

Due to the large amount of information produced and consumed during training, Artificial Intelligence and Machine Learning technologies may be utilized to automate data management and analysis. This real-time and post-event analysis will improve training, readiness and individual / Unit competency. Both humans and automated decision makers will recommend training interventions, assist in collecting objective data for future training assessments, needs and remediation events.

OBJ 33 Training The TSS/TMT shall be able to support distributed exercises to twelve distinct locations.

OBJ 34 Training The TSS/TMT central node with Cross Domain Solution shall be able to support TOP SECRET classification and host multiple classifications in single exercise.

OBJ 35 Training The TSS/TMT shall provide sufficient hardware to conduct ASCC staff training (Exercise control, Higher Headquarters, Lower response cells, opposing forces, Observer/Controller, and MSEL management).

OBJ 36 Training The TSS/TMT shall support constructive exercises Brigade and Above staff training up to ASCC level in disconnected semi-austere environments.

OBJ 37 Training The TSS/TMT shall support constructive exercises at the BCT/BN level and virtual and live at the Company and below level in disconnected semi-austere environments.

OBJ 38 TSS/TMT

The TSS/TMT shall support execution of the threshold critical mission threads identified in the system's integrated architectures and satisfy the technical requirements for Net-Centric military operations. It shall provide a single, common interface with the COE (Mission Command Systems and Networks) and Live TESS systems (platforms and Soldiers).

OBJ 39 TSS/TMT The TSS/TMT shall support the Intelligence Warfighting Function by interoperating with IEWTPT via APIs and appropriate classified networks (s).

OBJ 40 TSS/TMT The TSS/TMT shall interoperate with the Soldier Virtual Trainer (SVT).

OBJ 41 TSS/TMT The TSS/TMT shall interoperate with the Synthetic Training Environment - Live Training System (STE-LTS).

OBJ 42 TSS/TMT The TSS/TMT shall interoperate with the Future Next Generation Constructive (NGC).

OBJ 43 TSS/TMT The TSS/TMT shall interoperate with future training aids, devices, simulators, and simulations (TADSS) and appended TADSS.

OBJ 44 TSS/TMT The TSS/TMT shall interoperate with Joint and Multi-national MCIS.

OBJ 45 TSS/TMT The TSS/TMT shall interoperate with Joint and Multi-national simulation systems.

OBJ 46 TSS/TMT Build a simulation interoperability bridge using common standards.

OBJ 47 TSS/TMT

The TSS/TMT shall support cross domain security training events (unclassified up to TS/SCI) at any and all echelons regardless of scale and training construct (i.e., separate, and distinct events and a training event with varying echelons/levels) at any and all echelons.

OBJ 48 TSS/TMT The TSS/TMT shall represent the air, maritime, space, and cyber domains.

OBJ 49 TSS/TMT TSS/TMT central node shall be capable of hosting 100 simultaneous exercises with 100,000 entities each or 1 exercise with 10 million entities.

OBJ 50 TSS The TSS shall interoperate with JLCCTC and PCTE.

OBJ 51 TSS The TSS/TMT shall interoperate with the Integrated Visual Augmentation System (IVAS) Squad Immersive Virtual Trainer (SiVT).

OBJ 52 TSS The TSS Computer Generated Forces shall aggregate and disaggregate from Soldier to ASCC Level.


B-4



OBJ 53 TSS The TSS shall provide Computer Generated Forces with automated behaviors that represent tactical tasks and maneuver up to the ASCC level (BLUFOR, OPFOR, Civilian and Multinational Forces).

OBJ 54 TSS The TSS shall support training up to TOP SECRET level.

OBJ 55 TSS The vendor shall include design considerations for a field server capable of providing training for a Battalion and Brigade training event.

OBJ 56 TSS The TSS shall provide realistic and dynamic operational environment with all factors of PMESII-PT (Political, Military, Economic, Social, Infrastructure, Information - Physical Environment, & Time).

OBJ 57 TSS The TSS Entity Level, Virtual and Constructive Simulation shall scale to 10 million entities with 5,000 in the field of view; simultaneous virtual and constructive execution.

OBJ 58 TSS The TSS shall provide a personalized avatar capability so the user profile can be loaded on demand to provide an avatar that represents the Soldier's human performance characteristics.

OBJ 59 TSS TSS shall present modular models (life forms, vehicles, and equipment) found in ASCC and below formations including Cyber and EW.

OBJ 60 TSS

The TSS shall provide full replication of the Warfighting Functions in an Operational Environment. The TSS must provide an accurate representation of the Army's six warfighting functions (movement and maneuver, intelligence, fires, sustainment, protection, and mission command) consistent with the simultaneous deployment of unit/force types (i.e., combat arms, combat support, combat service support, as well as Special Operations Forces [SOF]) associated with those functions.


C-1


Appendix C Capability Roadmap

The TSS/TMT Product Overview brief embedded below as an object contains the Government’s initial capability roadmap expressed as echelon-based capability sets (i.e., Squad, Platoon, Company, Battalion and Brigade). The TDP Appendix F SRD identifies the initial product backlog to be utilized in development of the capability roadmap. Please note references to the Common Synthetic Environment Statement of Work (CSE SOW) is old language from a previous effort in the April 2020 timeframe. Also included is the current high-level capability over time slide from August 2020 timeframe. Appendix D Notional MVP/MVCR/Release Plan contains the Government’s notional MVP/MVCR/Release plan. The USG desires the highest echelon (Company, Battalion, Brigade) the vendor can deliver. The USG will consider vendor proposals which deliver less than company level capability.

Appendix C_1 TSS

TMT Product Roadmap Overview 15APR20 1700EST Distribution A.pdf

Appendix C_2

SPARTAN CAPSET Oneslider 12OCT20 Distribution A.pdf


D-1


Appendix D Notional MVP/MVCR/Release Plan

The MS Excel file embedded below as an object contains the Government’s draft Notional MVP/MVCR/Release Plan.

Appendix D 05 NOV

2020 RFS Notional Schedule DRAFT Distribution A.XLSX


E-1


Appendix E Cybersecurity

E.1 DoD CDS Connection Process Diagram

Appendix E CDS

Process Flowchart Distribution A.pdf

Figure E-1. DoD CDS Connection Process Diagram.


F-1


Appendix F Composite PDF File Instructions

1. Open the Training Simulation Software / Training Management Tool (TSS/TMT)

Performance Work Statement (PWS) / Technical Data Package (TDP) composite

Portable Document File (PDF) in Adobe Acrobat by right clicking the file, select open

with, and then select Adobe Acrobat. Embedded files do not appear if you open the

file in a web browser.

2. If the attachment pane does not appear on the left side of the document when the

file is open select View, Show/Hide, Navigation Panes, and select Attachments. The

attachment pane should now appear on the left side of the document.

Figure F-1. Displaying Attachment Pane.

Figure F-2. Attachment Pane Displayed.


F-2


3. To view a file, double click the file and it should open. To view MS Excel, MS Word,

or Visio files the user will need Adobe Acrobat Pro. If you do not have Adobe

Acrobat Pro, save the file, and then open the file in the appropriate application to

view the file.

4. To download an embedded file, right click the file and select save attachment.

Figure F-3. Save Embedded Attachment.


G-1


Appendix G Understanding Operational Environment Variables

Appendix G

Understanding OE Variables Distribution A.pdf


H-1


Appendix H Acronyms and Glossary

H.1 Acronyms

Table H-1. Acronyms.

Acronym Meaning

A&A Assessment and Authorization

AA Adversarial Assessment

AAL Additional Authorization List

AAR After Action Review

A-CDD Abbreviated Capability Development Document

AEDC Adversarial Cyber Developmental Test

AESS Army Endpoint Security System

AFAPD Air Force Applications Program Development

AMPS Aviation Mission Planning Software

AO Authorizing Official

API Application Programming Interface

APL Approved Products List

APMS Army Portfolio Management System

ARNG Army National Guard

ASCC Army Service Component Command

ATEC Army Test and Evaluation Command

ATCTS Army Training and Certification Tracking System

ATIS Army Training Information System

ATO Authority to Operate

AVA Associate Vendor Agreements

AVCATT Aviation Combined Arms Tactical Trainer

AvSE Avionics Software Emulation

BCT Brigade Combat Team

BII Basic Issue Item

BIT Built in Test

C2 Command and Control

CAC Common Access Card

CADE Cost Assessment Data Element

CAP Contractor Acquired Property

CAT1 Category 1

CATS Combined Arms Training Strategies

CCDC AvMC Combat Capabilities Development Command Aviation and Missile Command

CCDC DAC Combat Capabilities Development Command Data and Analysis Center

CCTT Close Combat Tactical Trainer

CDRL Contractor Data Requirements List

CDS Cross Domain Solution


H-2


Acronym Meaning

CDSA Cross Domain Solution Authorization

CFT Cross Functional Team

CGF Computer Generated Forces

CI Configuration Item

CI/CD Continuous Integration / Continuous Delivery

CJCSI Chairman Joint Chiefs of Staff Instruction

CLI Command Line Interfaces

CLIN Contract Line Item Number

CMP Configuration Management Plan

CNSSI Committee on National Security Systems Instruction

COE Common Operating Environment

CoE Center of Excellence

COMEX Communication Exercises

COOP Continuity of Operations Plan

COR Contracting Officer Representative

COTS Commercial Off the Shelf

CP Contingency Plan

CPCE Command Post Computing Environment

CPSMR Contractor's Progress, Status, and Management Report

CPVA Cooperative Vulnerability Penetration Assessments

CSCI Computer Software Configuration Items

CSDR Cost and Software Data Reporting

CSL Common Software Library

CTC Combat Training Centers

CVI Cooperative Vulnerability Identification

DA PAM Department of the Army Pamphlet

DCARC Defense Cost and Resource Center

DCSA Defense Counterintelligence and Security Agency

DDCA Deputy Director Cost Analysis

DEEP Digital Engineering Environment Platform

DEI Data Exchange Item

DevSecOps Development Security Operations

DID Data Item Description

DISA Defense Information Systems Agency

DMSMS Diminishing Manufacturing Sources and Material Shortages

DoD Department of Defense

DoDAF Department of Defense Architecture Framework

DoDIN Department of Defense Information Network

DOORS Dynamic Object-Oriented Requirements System

DOT&E Director, Operational Test & Evaluation

DREN Defense Research Engineering Network


H-3


Acronym Meaning

DT&I Development Test and Integration

ECA External Certification Authorities

ECMO Enterprise Cloud Management Office

eMASS Enterprise Mission Assurance Support Service

EXCON Exercise Control

EXORD Execution Order

FBX Filmbox

FCL Facility Clearance Level

FEDSUN Federal, State and University Network

FFS File Format Specification

FOC Full Operational Capability

FOCI Foreign Ownership, Control, or Influence

FORSCOM Forces Command

FOUO For Official Use Only

FV Functional Verification

GFE Government Furnished Equipment

GFI Government Furnished Information

GFP Government Furnished Property

GFT Games for Training

glTF Graphics Library Transmission Format

HHA Health Hazard Assessment

HITS Homestation Instrumentation System

IATT Interim Authorization to Test

IAVA Information Assurance Vulnerability Alert

IAW In Accordance With

ICAN Installation Campus Area Network

ICD Interface Control Document

ICS Interim Contractor Support

ICW In Coordination With

IDD Interface Design Description

IEN Integrated Enterprise Network

IEWTPT Intelligence Electronic Warfare Tactical Proficiency Trainer

IOC Initial Operational Capability

IRP Incident Response Plan

ISSM Information System Security Manager

ITE Integrated Training Environment

ITN Integrated Tactical Network

IUID Item Unique Identification

IVAS Integrated Visual Augmentation System

IWTS Integrated Weapon Training Strategies

JBLM Joint Base Lewis McChord


H-4


Acronym Meaning

JDIF Joint Development and Integration Facility

JFO Joint Fires Observers

JFT Joint Fires Trainer

JIM Joint Interagency and Multinational

JLCCTC Joint Land Component Constructive Training Capability

JME Joint Mission Environment

JTAC Joint Terminal Attack Controllers

JVMF Joint Variable Message Format

LD/ME Logistics Demonstration/Maintenance Evaluation

LT2 Live Training Transformation

LTA Local Training Area

LVCG Live, Virtual, Constructive, Gaming

LVC-IA Live, Virtual, Constructive - Integrating Architecture

MBSE Model Based Systems Engineering

MCIS Mission Command Information Systems

MCL Materiel Component List

MDO Multi-Domain Operations

MOSA Modular Open Systems Architecture

MTTR Mean Time to Restore

MVCR Minimum Viable Capability Release

MVP Minimum Viable Product

NEC Network Enterprise Center

NET New Equipment Training

NGC Next Generation Constructive

NIAP National Information Assurance Partnership

NIPR Non-classified Internet Protocol (IP) Router

NIST National Institute of Standards and Technology

NLT Not Later Than

NRRE Network Risk Reduction Event

o/a On or About

OC Observer Controller

OCAR Office of the Chief Army Reserve

ODM Object Data Model

OE Operational Environment

OEM Original Equipment Manufacturer

OFP Operational Flight Program

OSD Office of the Secretary of Defense

OT Operational Test

OTA Other Transaction Authority

OTC Operational Test Command

OWT One World Terrain


H-5


Acronym Meaning

PART Program Assessment and Review Tool

PEO AVN Program Executive Office Aviation

PEO STRI Program Executive Office for Simulation, Training and Instrumentation

Ph Probability of Hit

PHS&T Packaging, Handling, Shipping, and Transport

Pk Probability of Kill

PMESII-PT Political, Military, Economic, Social, Infrastructure, Information - Physical Environment, & Time

POA&M Plan of Action and Milestones

PoN Point of Need

PPEA Plan, Prepare, Execute, and Assess

PPSM Ports, Protocols, and Services Management

PWS Performance Work Statement

QRG Quick Reference Guides

RAM Reliability, Availability, Maintainability

RFT Ready for Training

RIW Reliability Improvement Warranties

RMF Risk Management Framework

RTM Requirements Traceability Matrix

RVCT Reconfigurable Virtual Collective Trainer

S&T Science and Technology

SAP Software Acquisition Pathway

SDK Software Development Kit

SDRL Supplier Data Requirements List

SIGACTS Significant Actions

SIPR Secure Internet Protocol Routing

SiVT Squad Immersive Virtual Trainer

SLCM System-Level Continuous Monitoring

SME Subject Matter Expert

SOP Standard Operating Procedures

SP Security Plan

SPS Software Product Specification

SRD System Requirements Document

SRDR Software Resources Data Reports

SRS Software Requirements Specification

SSDD System/Subsystem Design Description

SSS System/Subsystem Specification

STE Synthetic Training Environment

STE-LTS Synthetic Training Environment - Live Training System

STIG Security Technical Implementation Guide

STP Standards of Training Proficiency

SVD Software Version Description


H-6


Acronym Meaning

SVT Soldier Virtual Trainer

SysMIL System Modeling Language

T&D Test and Development

TA Technical Assessments

TAA Technical Assistance Agreement

TADSS Training Aids, Devices, Simulators, and Simulations

TB Technical Bulletin

TD ICL/R Training Device Inventory Checklist/Record

TDP Technical Data Package

TESS Tactical Engagement Simulation System

TFR Training Facilities Report

TIF Technology Integration Facility

TIM Technical Interchange Meeting

TM Technical Manuals

TMDE Test, Measurement, and Diagnostic Equipment

TMT Training Management Tool

TPD Training Performance Data

TPO TRADOC Proponent Office

TRADOC Training and Doctrine Command

TRR Test Readiness Review

TSMO Threat System Management Office

TSN Trusted Systems and Networks

TSP Training Support Package

TSS Training Simulation Software

UA User Assessments

ULO Unified Land Operations

UoF Use of Force

UPDM Unified Profile for DoDAF/MODAF

USAPHC US Army Public Health Command

USG United States Government

VoF Verification of Fixes

VV&A Verification, Validation, and Accreditation

WfF Warfighting Function

WGS World Geodetic System

WSD Weapons Skills Development

WTC ARNG Warfighter Training Center Army National Guard

XR Cross Reality

H.2 Glossary

Table H-2. Glossary.


H-7


Term Definition

Accessibility The quality of being able to be reached, easy to obtain/use, and easily understood/appreciated. The ability for a system to reach the PoN by traversing the appropriate communications network (e.g. DODIN-A).

After Action Review (AAR)

A professional discussion of a training event focused on performance standards, that enable the participating Soldiers to discover for themselves what happened, why it happened, and how to sustain strengths and improve on weaknesses. It is a tool that leaders, trainers, and units can use to get the maximum benefit from every mission or task. Normally prepared by the TAF Analyst and conducted by an OC/T.

Application Programming Interface (API)

A set of application programs or operating system functions that can be utilized by a program.

Architecture Runway The Architectural Runway consists of the existing code, components, and technical infrastructure needed to implement near-term features without excessive redesign and delay.

Architecture Synchronization

Government-led meeting hosted by the Systems Architect with the Tech Leads from each development team.

Army Service Component Command (ASCC)

Command responsible for recommendations to the joint force commander on the allocation and employment of Army forces within a combatant command. Also called ASCC. (JP 3-31).

Artificial Intelligence (AI)

The capacity of a computer to perform operations analogous to learning and decision making in humans, as by an expert system, a program for CAD or CAM, or a program for the perception and recognition of shapes in computer vision systems. The STE will use AI to replicate large unit level routines to increase realism of the operational environment, to support automated adaptive behaviors and free-thinking hybrid threats, to represent culturally aware virtual humans and small units, to mimic unit behaviors when they are not present, to support communication and interfacing techniques with the environment and other entities/agents, and to ease the application for a military user base.

ATO (Authority to Operate)

The official management decision given by a senior organizational official to authorize operation of an information system and to explicitly accept the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation based on the implementation of an agreed-upon set of security controls.

Backlog The product backlog is the holding area for upcoming Features, which are intended to address user needs and deliver business benefits. It also contains the enabler features necessary to build the Architectural Runway.

Baseline The documented configuration that is the basis of the design / development / build of the product.

Cloud

Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.


H-8


Term Definition

Common Operating Environment (COE)

The COE is an approved set of computing technologies and standards applied across six Computing Environments (CE): Command Post, Mounted, Mobile/Handheld, Real Time/Safety Critical/Embedded, Sensor, and Enterprise. As a strategic Army initiative, and as an integral part of the LandWarNet and the Joint Information Environment, the COE is a foundational component of the Army’s modernization strategy. It aligns development and migration of Army programs to a common software baseline and a centralized hardware procurement process across the COE and within the Computing Environments.

COMMEX

A COMMEX is a network and cloud connectivity check that precedes a Network Risk Reduction Event (NRRE). The purpose of the COMEX is to ensure the capability will be network and cloud connected at the Government assessment and NRRE.

Compliance

1. The act of conforming, acquiescing, or yielding. 2. A tendency to yield readily to others, esp. meekly. 3. Conformity; accordance: in compliance with orders. 4. Cooperation or obedience.

Computer Generated Force (CGF)

A generic term used to refer to computer representations of forces in models and simulations that attempts to model human behavior sufficiently so that the forces will take some actions automatically (without requiring man-in-the-loop interaction). Types of CGF include automated forces - computer-generated forces that require little or no human interaction. Semi-automated forces - computer-generated forces in which the individual platform simulation is operated by computer simulation of the platform crew and command hierarchy.

Computing Environment (CE)

A logical grouping of systems with similar characteristics used to organize the COE (deployment /echelon (sic), environmental, transport dependencies, form factors, etc.). A computing environment comprises the necessary hardware, operating system, libraries, and software required to run applications within the COE.

Configuration Audit Compares the as built / as developed product against the system documentation to identify and document any variance in the documented configuration baseline.

Constructive Training Models and simulations that involve simulated people operating simulated systems. Real people stimulate (make inputs) to such simulations but are not involved in determining the outcomes.

Cybersecurity

Protection against intentional subversion or forced failure. A composite of four attributes – confidentiality, integrity, availability, and accountability – plus aspects of a fifth, usability, all of which have the related issue of their assurance. Prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. Defined in National Security Presidential Directive-54/Homeland Security Presidential Directive-23.

Daily Scrum Team members meet daily to report plans for the day, accomplishments from the previous day and identify any blockers.


H-9


Term Definition

Department of Defense Information Network (DoDIN)

The globally interconnected, end-to-end set of information capabilities for collecting, processing, storing, disseminating, and managing information on demand to warfighters, policy makers, and support personnel. The DoDIN includes owned and leased communications and computing systems and services, software (including applications), data, security services, other associated services, and National Security Systems (NSS). Non-DoDIN Information Technology (IT) includes stand-alone, self-contained, or embedded IT that is not, and will not be, connected to the enterprise network.

Diminishing Manufacturing Sources and Material Shortages (DMSMS)

The loss, or impending loss, of manufacturers or suppliers of items, raw materials, or software.

Distributed Exercise An event enabled by distributed simulation where the training participants are at different locations (i.e., different cities, countries, or continents).

Distributed Simulation

A simulation that has multiple modules, which can be run on multiple processors. The processors can be co-located in the same room or located in remote sites. Entity Perspective: The perception of the synthetic environment held by a simulation entity based on its knowledge of itself and its interactions with the other simulation entities. This includes not only its own view of the simulated physical environment, but also its own view of itself, the other entities in the synthetic environment, and of the effects of the other entities on itself and the synthetic environment. Syn: World View. (SISO-REF-020-2007).

Effect A change which is a result or consequence of an action or other cause.

Elastic In cloud computing, elasticity is the measure of how well a system adapts to workload changes by provisioning and de-provisioning systems to match the demand as closely as possible.

Entity

An entity is any independent object within a simulation that possesses complex behaviors and attributes. For example, personnel, vehicles, complex munitions, key communications devices might all be represented as independent entities within a simulation.

Environment

The texture or detail of the natural domain, that is terrain relief, weather, day, night, terrain cultural features (cities or farmland), sea states, etc.; and the external objects, conditions, and processes that influence the behavior of a system.

Experience The process of doing and seeing things and having things happen to you.

Extensibility The quality of being designed to allow the addition of new capabilities or functionality. An extensible system is one which takes future growth into consideration during implementation.

Fair Fight

“Fair fight” is when the performance characteristics of two of more interoperating simulations are seamless, preventing discrepancies in simulation algorithm or environmental representations from effecting the outcome of cross environment simulation exercises (e.g., Unseen opponents, pairing mismatch, effects mismatch, location mismatch, aspect mismatch).


H-10


Term Definition

Fidelity

The degree to which a model or simulation represents the state and behavior of a real-world object or the perception of a real world object, feature, condition, or chosen standard in a measurable or perceivable manner; a measure of the realism of a model or simulation.

Field/Fielding

The process of delivering a product to the end user, this includes providing the support elements (e.g. user manuals, maintenance manuals, operator guides, spare parts, tools, etc.) that will allow the user to successfully operate and maintain the product.

Full Operational Capability (FOC)

In general, attained when all units and/or organizations in the force structure scheduled to receive a system 1) have received it and 2) can employ and maintain it. The specifics for any particular system FOC are defined in that system's Capability Development Document and Capability Production Document. • All equipment associated with the STE has been fielded, IAW the BOIP. • All information assurance requirements are complete. • New operator training for all sites is complete. • All contractor requirements for STE operations and support are in place and ready to support unit training at all sites. • The STE sustainment plan is in place and being executed.

Functional Fidelity

Functional fidelity captures how well the game acts like (not replicates) the operational equipment in responding to tasks performed by the training audience. For example if there is a surrogate communications system that represents the actual operational communications system but uses different means (e.g., Voice over IP (VOIP)) to provide communications, the functional fidelity is high because the training audience can perform its normal communications function even though it does not have its actual communications system or network. Functional fidelity appears to be an important factor in increasing and maintaining interest, realism, and motivation in the training event. It also helps support attention to detail.

Functional Manager Synchronization

Government-led meeting hosted by the Functional Manager with Functional Owners from each development team. Functional Manager is the industry best practice role for the Agile Product Manager. The role was renamed to deconflict the use of the role program manager which is reserved for the O6 PEO STRI Program Manager. Functional Owner is the industry best practice role for the Product Owner. The role was renamed to make it consistent with the Functional Manager.

Gaming Commercial and Government-off-the-shelf computer generated environment for interactive, semi-immersive training and education.

IATT (Interim Authority to Test)

Temporary authorization to test an information system in a specified operational information environment within the timeframe and under the conditions or constraints enumerated in the written authorization.

Immersed Sight, sound, and touch modalities are stimulated. The quality of stimulation approximates what the Soldier experiences in the Live Environment.

Immersion The placing of a human in a synthetic environment through physical and/or emotional means.

Immersive cf., Immersed.


H-11


Term Definition

Initial Operational Capability (IOC)

In general, attained when selected units and/or organizations in the force structure scheduled to receive a new system have received it and can employ and maintain it. The specifics for any system IOC are defined in that system’s Capability Development Document (CDD) and Capability Production Document (CPD). IOC is defined as the first fielding and acceptance of the STE capability by an installation. It is further defined as: • All STE components have completed the verification, validation and accreditation process prior to IOC. • All STE equipment is fielded to the first installation site and accepted. • All information assurance requirements are complete. • New user operator training at the first site is complete. • All contractor requirements for STE operations and support are in place and ready to support unit training at the first site.

Instrumentation The use or application of instruments to measure the effectiveness of training systems.

Integrated Training Environment (ITE)

The Army’s Integrated Training Environment (ITE) is current array of Training Aids, Devices, Simulators and Simulations (TADSS) that enable Army Collective, Non-Systems Training. The ITE is a system of systems that, by design, combines and connects key training enablers in a persistent and consistent manner to accurately train Mission Command (MC) according to the Commander’s training objectives within the appropriate Operational Environment. The ITE Implementation and Management Plan (I2MP) describes how the Army aligns ITE system of systems requirements, funding, and solutions to create incremental ITE capabilities to support Home Station Training with a focus on Brigade and below by 2020. The plan is a living document developed cooperatively by the Deputy Commanding General, Combined Arms Center – Training and the Program Executive Officer, Simulation Training, and Instrumentation. The plan covers the stakeholders; organizations; roles; responsibilities; high-level governance and systems engineering approaches; tasks; and schedules involved in developing incremental ITE capabilities.

Integration The process of combining software or hardware components or both into an overall system.

Intelligent Tutoring cf., Intelligent Tutoring System.

Intelligent Tutoring System

The mechanism or technologies (tools and methods) to provide tailored training and educational experiences; adaptive tutoring systems respond to changing states in the learner and changing conditions in the training environment to optimize learning; adaptive tutoring systems anticipate and recognize teachable moments. The STE will use ITS for Team and Unit Modeling, Automated Enterprise Hot wash and After-Action Review (AAR), Affective/Cognitive Modeling Capabilities, Training Effectiveness/Human Performance Measurement, Authoring Tools to Extend Applicability Across Training Domains, Domain Modeling across a range of dynamic military tasks, and elements of the Human Dimension to drive the cognitive, social, and physical skills of Soldiers over their career (Long-term Learner Modeling). An Intelligent Tutoring system (ITS) is a computer system that aims to provide immediate and customized instruction or feedback to learners, usually without.


H-12


Term Definition

Interface

1. A shared boundary across which information is passed. 2. A hardware or software component that connects two or more components for the purpose of passing information from one to another. 3. To connect two or more components for the purpose of passing information from one to another. 4. To serve as a connecting or connected component as in (2).

Interim Contractor Support Temporary product support provided to the Government by a contractor.

Interoperability

The ability to operate in synergy in the execution of assigned tasks. The ability of a model or simulation to provide services to and accept services from other models and simulations, and to use these exchanged services to operate effectively together.

Interoperable The ability of two or more systems or components to exchange information and to use the information that has been exchanged.

Item Unique Identification Method of providing unique identification for each item in a system to allow documentation, tracking, and analysis of parts usage.

Joint Fires Training The training for the application of Fires delivered during the employment of forces from two or more components in coordinated action to produce desired effects in support of a common objective.

Life Cycle The life of a system from initiation, planning, procurement, development, implementation, operation, maintenance, to disposal of the system.

Live, Virtual, Constructive - Integrating Architecture (LVC-IA)

The Army's program of record that provides the common software, protocols, standards, and interfaces to facilitate interoperability of currently non-linked LVCG TADSS so that they can interoperate, share information, provide common views of the battlefield, and stimulate MC systems. The LVC-IA will be developed and fielded in increments (notionally two years) and is the key technical enabler foundation of the ITE. The Live, Virtual Constructive - Integrating Architecture (LVC-IA) is the Program of Record that establishes initial interoperability and over time, the integration of Live, Virtual, Constructive and Gaming Simulations and Simulators and the stimulation of Mission Command Systems.


H-13


Term Definition

Logistics Demonstration/Maintenance Evaluations (LD/ME)

The LD/ME are used to evaluate the adequacy of the system support package and ensure the user unit has the logistical capability to achieve IOC. A logistics demonstration includes the nondestructive disassembly and reassembly of a production representative system using its related peculiar test, measurement, and diagnostic equipment (TMDE), tools, training devices, technical publications, and support equipment. It also evaluates the adequacy of trouble-shooting procedures, personnel skill requirements; the selection and allocation of spare parts, tools, test equipment, and tasks to appropriate maintenance levels; and the adequacy of maintenance time standards. LD/ME shall use vendor developed test procedures (e.g., threads and vignettes) to test the product support capabilities. The vendor shall support and participate in the LD/ME. The vendor shall provide all required hardware and software for the events. The Government will document issues in PTRs for the vendor to address/correct during the event or as part of the backlog. LD/ME locations are TBD and may include P4 STE TIF, P5 JDIF, Cloud / data center, distributed locations, MTCs, or a combination of these locations. The test environment will approximate the infrastructure (e.g., network, cloud, security) conditions of the anticipated fielding locations. The Government will host a daily hot wash and Government only AAR.

Master Scenario Event List (MSEL)

The MSEL is a chronological list that supplements the event scenario with event synopses; expected participant responses; capabilities, tasks, and objectives to be addressed; and responsible personnel. It includes specific scenario events (or injects) that prompt players to implement the plans, policies, and procedures that require testing during the event, as identified in the capabilities-based planning process. It also records the methods that will be used to provide the injects (i.e., phone call, facsimile, radio call, e-mail).

MCIS MCIS combines data and information from the Warfighting Functions to support common CP activities that contribute to the commander’s ability to understand, visualize, describe, direct, lead, and assess operations.

Mission Command

The event of authority and direction by the commander using mission orders to enable disciplined initiative within the commander's intent to empower Agile and adaptive leaders in the conduct of full-spectrum operations; commander-led and blends the art of command and the science of control to integrate the Warfighting Functions to accomplish the mission. (ADP 6-0).

Model A three-dimensional representation of a person or thing or of a proposed structure, typically on a smaller scale than the original.


H-14


Term Definition

Modular Open Systems Approach (MOSA)

An integrated business and technical strategy. The DoD will use MOSA as a tool to help provide joint combat capabilities. Five (5) MOSA Principles: 1. “Establishes an enabling environment conducive to open system implementation”. 2. “Employs modular design tenets”. 3. “Defines key interfaces where appropriate”. 4. “Applies widely supported, consensus-based (i.e., open) standards that are published and maintained by a recognized industry standards organization”. 5. “Uses certified conformant products”. · Title 40 (Public Law 104-106), Subtitle III/Clinger-Cohen Act (CCA) Compliance Requirements, Modular Contracting Implementation Guidance includes the use of Modular, Open Systems Approach as part of the Systems Engineering of each DoD System. · Federal Acquisition Regulations (FAR), Part 39, Acquisition of Information Technology, paragraph 103, requires the use of Modular Contracting (and the implied use of OSA as part of the Systems Engineering of each system). · DoDI5000.02, Enclosure 2, paragraph 6.a(5) Modular Open System Architecture (MOSA) states, “Program management is responsible for evaluating and implementing a MOSA to the maximum extent feasible and cost effective. … The Acquisition Strategy for the system should identify where, why, and how a MOSA will or will not be used by the program.”

Multi-Domain

Multi-Domain Operations allows US forces to outmaneuver adversaries physically and cognitively, applying combined arms in and across all domains. It provides a flexible means to present multiple dilemmas to an enemy and create temporary windows of localized control to seize, retain and exploit the initiative. Employing Multi-Domain Operations, Army and Marine forces with cross-domain capabilities provide a credible capability to deter adversary aggression, deny enemy freedom of action, overcome enemy anti-access and area denial (A2AD), secure terrain, compel outcomes, and consolidate gains for sustainable outcomes.

MVCR Initial set of features suitable to be fielded to an operational environment that provides value to the user in a rapid timeline.

MVP An early version of the software to deliver or field basic capabilities to users to evaluate and provide feedback on. Insights from MVPs help shape scope, requirements, and design.

Network Risk Reduction Event

A NRRE is network and cloud data collection and performance assessment to assess the capability on the network. The purpose of the NRRE is to ensure the software will operate on the Government’s network and security infrastructure.

Operational Environment (OE)

(DOD) A composite of the conditions, circumstances, and influences that affect the employment of capabilities and bear on the decisions of the commander. Also called OE. See ADRP 3-0 and ADRP 6-0.


H-15


Term Definition

Operational Testing

The Government conducts the OT on production, or production representative articles, to determine whether systems are operationally effective and suitable for intended use by representative users to support the decision to proceed to fielding the software release. The vendor shall support and participate in the OTs. The OT will be a distributed exercise conducted at Home Station(s) and encompass all LVCG domains utilizing STE and legacy components. The OT will validate the user's ability to Plan, Prepare, Exercise, and Assess capabilities of the STE for the various echelons. The vendors shall provide all required hardware and software for the events. OT may consist of a series of distinct test events at various locations based on the functionalities being tested. The Government will host a daily hot wash and Government only AAR.

Other Transactional Authority (OTA)

Other transactions Authority (OTA) is the term commonly used to refer to the 10 U.S.C. 2371 (Prototyping) / 10 U.S.C. 2373 (Research) authority to enter transactions other than contracts, grants, or cooperative agreements.

Performance The action or process of performing a task or function.

Platform as a Service (PaaS)

The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages, libraries, services, and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly configuration settings for the application-hosting environment.

Point of Need (PoN)

The STE PoN concept provides a collective training capability to training audiences of all components at Home Stations (e.g., installations, combat training centers [CTCs], armories, reserve centers, Regional Collective Training Centers [RCTC], etc.), while deployed, and at the institution. The STE PoN functional area has five task groups: Networking and Cloud Technology, Exercise Control / Synch and Scenario Generation / Initialization, User Interface / Contextual Input and Support for Various Platforms, Single Client Install or Web Application Access Gateway to access entire training system / environment (elimination of federated training systems), and Common Risk Management Framework that links to Mission Command. PoN is further defined as the ability to provide a collective training capability during connected, standalone, and *disconnected, intermittent, and low-bandwidth (DIL) network conditions. (*Disconnected: The STE needs the capability to operate on isolated networks, without access to enterprise resources.).

Pre-Program Increment Planning

Key stakeholders identify features from the Product Backlog from the MVP feature set for the teams to plan and develop for the 8-12 release cycle.

Product Roadmap High-level visual summary that maps out the vision and direction of product offerings over time. Describes the goals and features of each software sprint and program increment.

Product Support (see also sustainment)

The processes, documentation, and actions required to field and maintain the readiness and operational capability of a system.

Product Vision The Vision is a description of the future state of the Solution under development. It reflects customer and stakeholder needs, as well as the Feature and Capabilities proposed to meet those needs.


H-16


Term Definition

Program Increment

A Program Increment (PI) is a timeboxed planning interval during which an Agile Release Train plans and delivers incremental value in the form of working, tested software and systems. PIs are typically 8 – 12 weeks long. The most common pattern for a PI is four development Iterations, followed by one Innovation and Planning (IP) Iteration.

Program Increment Demonstration

Teams will demonstrate the work that they have been working on during the Program Increment.

Program Increment Dependency Board

Highlighting the new feature delivery dates, feature dependencies among teams and relevant Milestones.

Program Increment Objectives

Program Increment (PI) Objectives are a summary of the business and technical goals that an Agile Team or train intends to achieve in the upcoming Program Increment (PI) that are created by each team with the business value assigned by the Business Owners.

Program Increment Planning

Key Stakeholders and the development teams create a high-level plan for each sprint for the release. This activity gives the opportunity to identify dependencies and risks among the teams. The Key Stakeholders and the Development team will leave the planning session with a plan and a User Agreement.

Program Increment Retrospective

Teams discuss the results of the Program Increment, review practices, and identify ways to improve.

Realism Fine Arts. Treatment of forms, colors, space, etc., in such a manner as to emphasize their correspondence to actuality or to ordinary visual experience.

Reconfigurable Virtual Collective Trainer (RVCT)

The Air and Ground RVCT are used to train units in collective tasks on a simulated, fully interactive, real time battlefield. RVCT provides a realistic virtual environment in which units train and perform tasks preparing themselves to successfully accomplish their collective missions.

Release Notes Release notes are documents that are distributed with software products and can be delivered when products are still be developed.

Renderer A software or hardware process that generates a visual image from a model.

Representation

Models of the entity or phenomenon associated and its effects. Representations using algorithms and data that have been developed or approved by a source having accurate technical knowledge are often considered authoritative.

Resolution The degree of detail visible in a photographic or television image.

Risk Management

The process of managing risks to organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, or the nation resulting from the operation or use of an information system, and includes: 1) the conduct of a risk assessment; 2) the implementation of a risk mitigation strategy; 3) employment of techniques and procedures for the continuous monitoring of the security state of the information system; and 4) documenting the overall risk management program.

RMF (Risk Management Framework)

A disciplined and structured process that integrates information security and risk management activities into the system development life cycle.


H-17


Term Definition

Scalability cf., Scalable.

Scalable The capacity to be changed in size or scale. The ability of the system to adapt to increased demands.

Scrum of Scrums Scrum of Scrum Sessions that are Government-led hosted by the Release Train Engineer with Scrum Masters from each development. Upcoming features are socialized, and dependencies are discussed at this meeting.

Semi-Immersed Sight, sound, and touch modalities are stimulated. The quality of stimulation is a low-fidelity approximation of what the Soldier experiences in the Live Environment.

Semi-Immersive cf., Semi-Immersed.

Situational Awareness

Knowledge of one’s location; the location of friendly and hostile forces; and of external factors, such as terrain, weather, etc., that may affect one’s capability to perform a mission. Commanders, staffs, units, and soldiers/weapon platforms at all echelons require the means to optimally utilize all mission command information available that affects their area of operations. SA is a state of understanding gained through decisions made from knowledge supplied by a graphical Common Picture of the battlefield consisting as a minimum of the enemy situation (location, resources, status, and possible actions), friendly situation (location, resources, and status), and the logistics situation (location and status).

Software Release Functionality developed during the Program Increment.

Sprint Demonstration Teams demonstrate the work that they have been working on during that 2-week Sprint.

Sprint Goals Teams develop goals for the 2-week sprint during Sprint Planning.

Sprint Plan

Teams engage in mapping out each sprint with features during Program Increment Planning to highlight dependencies among teams and risks which is captured in the sprint plan. During the Sprint Planning Event, the teams revisit the sprint plan and add additional detail during the Sprint Planning Phase of the Sprint Lifecycle.

Sprint Retrospective The Team discuss the results of the sprint, review the team practices, and identify ways to improve.

Sustainment The support required to maintain a system in an operational status throughout its life cycle.

Synthetic Representation or model of the characteristics of the real world. Devised, arranged, or fabricated for special situations to imitate or replace usual reality.


H-18


Term Definition

Synthetic Environment

The integrated set of data elements that define the environment within which a given simulation application operates. The data elements include information about the initial and subsequent states of the terrain including cultural features, and atmospheric and oceanographic environments throughout an event. The data elements include databases of externally observable information about instantiable entities and are adequately correlated for the type of event to be performed. Also known as virtual world. (IEEE Std 1278.1-2012) [10] Virtuality Continuum: “The Virtuality Continuum is a continuous scale ranging between the completely virtual, a virtuality, and the completely real, reality. The reality-virtuality continuum therefore encompasses all possible variations and compositions of real and virtual objects.” [2] Virtual: An entity or data that is derived from a modeled or simulated representation of the actual or anticipated system.

Technical Assessment/Functional Verification

The Government conducts the TA/FVs on the latest developed capabilities to ensure requirements are met per the SRD/SSS. TA/FVs shall use vendor developed test procedures (e.g., threads and vignettes) to test TSS/TMT capabilities. The vendor shall support and participate in the TA/FVs. The vendor shall provide all required hardware and software for the events. TA/FVs shall collect Reliability, Availability, and Maintainability (RAM) data. The Government will document issues in Problem Trouble Tickets (PTRs) for the vendor to address/correct during the event or as part of the backlog. TA/FV locations are TBD and may include P4 STE Technology Integration Facility (TIF), P5 Joint Development and Integration Facility (JDIF), Cloud / data center, distributed locations, MTCs, or a combination of these locations. The test environment will approximate the infrastructure (e.g., network, cloud, security) conditions of the anticipated fielding locations. The Government will host a daily hot wash and Government only AAR.

Training Aids, Devices, Simulators, and Simulations (TADSS)

Training aids, devices, simulators, and simulations (TADSS) replicate OE complexities (training role players, IED simulators, MILES, small arms) to a low-fidelity environment (low fidelity as defined by Army training directives).

Training Effectiveness Evaluation of the impact of training and educational tools and methods on usability, learning, comprehension, performance, retention, reasoning, and transfer of knowledge and acquired skills to the operational environment.

Training Unit The unit which is trained and evaluated during the event.

Use of Force

A series of actions an individual can take to resolve a situation. Use of force allows the Soldier flexibility as the need for force changes as the situation develops. The level of force is not linear or consecutive; one may go up a scale, and back again in a matter of seconds. Use of force includes less lethal force (e.g., officer presence; voice commands; empty hand control; pepper spray, baton, Taser; other less lethal weapons) and deadly force.

User Agreement

Agreement between the operational and acquisition communities to gain ensure active user involvement and decisions. Ensure proper resourcing of user involvement to support development. Commit to active user involvement throughout design and development during planning phase. Signed by sponsor, PMO prior to entry into Execution Phase.


H-19


Term Definition

User Assessment (UA)

The Government conducts the UA to allow the user/Soldier to operate the system and provide feedback to the developers. Users roles include but are not limited to scenario planners, dismounted Soldiers, platform operators and AAR personnel. The vendor shall support and participate in the UAs. The vendor shall assist the Government to identify proper UA Soldier staffing at least 90 days prior to the event. The vendors shall provide all required hardware and software for the events. Locations of the TAs is to be determined and may include P4 STE TIF, P5 JDIF, Cloud / data center, distributed locations, including MTCs, or a combination of these locations. The Government will host a daily hot wash and Government only AAR.

Verification, Validation, and Accreditation (VV&A)

The Government conduct VV&A on all SRD/SSS requirements. The vendor will assist in all VV&A activities as required. The National Simulation Center (NSC) Analysis and Test Branch conducts testing that informs both validation decisions, and subsequent recommendations to accrediting authorities, made by TPO on the use of modeling and simulation solutions for training exercises and military operations. The testing concept for informing the TPO STE involves using applicable data from the OT, and from prior assessments (TAs and UAs), and conducting, by exception, additional activities, and events with priority to validation testing. Additional activities and events include technical and functional thread testing and vignette and operational scenario testing. The validation data informs identification of capabilities and limitations of STE solutions when using those to train Soldiers.

Virtual Semi-Immersive Interfaces

Virtual Semi-Immersive interfaces are common ‘keyboard and mouse’ interfaces into a virtual 3D representation of a training environment.

Virtual Training A simulation involving real people operating simulated systems. Virtual simulations inject human-in-the-loop in a central role by exercising motor control skills, decision skills, or communication skills.

Warfighting Function

A group of tasks and systems (people, organizations, information, and processes) united by a common purpose that commanders use to accomplish missions and training objectives. (ADRP 3-0) A Warfighting Function is a group of tasks united by a common purpose that commanders use to accomplish missions.

Weapon Skill Development The development of fire’s knowledge, skills, marksmanship, and engagement techniques involved in the effective lethal employment of the weapon system.

Zero Client

A zero-client is an I/O redirector device that allows a full cluster of peripheral devices to be deployed at the desired point of service without a dedicated PC or thin client at that same location and without requiring any modifications to existing software applications.

Synthetic Training Environment Cross Functional Team

DISTRIBUTION A: APPROVED FOR PUBLIC RELEASE // DISTRIBUTION IS UNLIMITED 1

COL McCarthy, STE CFT

STE CFT MVP Overview Brief

16 APR 20

15 1700EST APR 20


DISTRIBUTION A: APPROVED FOR PUBLIC RELEASE // DISTRIBUTION IS UNLIMITED 215 1700EST APR 20

Revised CAPSETs Capability Set 1

• TSS: Behaviors, Movement and Maneuver• Mission Command, Force Structure• Fire WFF, PMESSII-PT, METT-TC, Crowd behaviors/Patterns of Life• Platform C2, Sensors, Multi-spectral• 3D Models equipment, Avatar, Interoperability• Scalability• TMT: End state Capability• RVCT: Dismounted Soldier, Apache, Abrams, UH 60, CH47, Shadow• Up Armored M1151• OWT: Partial Base Globe, 1 IOC Sites, Hi Res inset

Capability Set 2• TSS: Behaviors, Movement and Maneuver• Mission Command, Force Structure• Fire WFF, PMESSII-PT, METT-TC, Crowd behaviors/Patterns of Life• Platform C2, Sensors, Multi-spectral• 3D Models equipment, Avatar, Interoperability• Scalability• RVCT: Dismounted Soldier, Apache, Abrams, UH 60, CH47, Shadow• Up Armored M1151, M915 Line Haul Tractor, M1120 Load Handling System, Palletized load system, Joint Light Tactical Vehicle,

M1078 Light Medium Tactical Vehicle (LMTV) • OWT: Partial Base Globe, 1 IOC Sites, Hi Res inset

Capability Set 3• TSS: Behaviors, Movement and Maneuver• Mission Command, Force Structure• Fire WFF, PMESSII-PT, METT-TC, Crowd behaviors/Patterns of Life• Platform C2, Sensors, Multi-spectral• 3D Models equipment, Avatar, Interoperability• Scalability• RVCT: Dismounted Soldier, Apache, Abrams, UH 60, CH47, Shadow, • Up Armored M1151, M915 Line Haul Tractor, M1120 Load Handling System, Palletized load system, Joint Light Tactical Vehicle, M1078 Light Medium Tactical Vehicle (LMTV) • OWT: Base Globe, 1 IOC Sites, Hi Res inset

Capability Set 4• TSS: Behaviors, Movement and Maneuver• Mission Command, Force Structure• Fire WFF, PMESSII-PT, METT-TC, Crowd behaviors/Patterns of Life• Platform C2, Sensors, Multi-spectral• 3D Models equipment, Avatar, Interoperability• Scalability• TMT: End state Capability• RVCT: Dismounted Soldier, Apache, Abrams, UH 60, CH47, Shadow• Up Armored M1151, M915 Line Haul Tractor, M1120 Load Handling System, Palletized load system, Joint Light Tactical Vehicle, M1078 Light Medium Tactical Vehicle (LMTV)• OWT: Base Globe, 3 IOC Sites, Hi Res inset

Capability Set 5• TSS: Behaviors, Movement and Maneuver• Mission Command, Force Structure• Fire WFF, PMESSII-PT, METT-TC, Crowd behaviors/Patterns of Life• Platform C2, Sensors, Multi-spectral• 3D Models equipment, Avatar, Interoperability• Scalability• TMT: End state Capability• RVCT: Dismounted Soldier, Apache, Abrams, UH 60, CH47, Shadow• Up Armored M1151, M915 Line Haul Tractor, M1120 Load Handling System, Palletized load system, Joint Light Tactical Vehicle, M1078 Light Medium Tactical Vehicle (LMTV) • OWT: Base Globe, 5 IOC Sites, Hi Res inset

SquadOperations

PlatoonOperations

CompanyOperations

BNOperations

BCT Operations

Aligned through DEVSECOPS& Sprint cycles to ensure three items:• Soldier Feedback • Maintain awareness of developmental cycle• Early risk/issue identification & mitigation



Revised CAPSET MVP TSS



Revised CAPSET 1-TSS

CS 1 MVP Standard Clearance Gate

TSS

Human and Computer Generated Forces and Modeling

1. Individual Behaviors

(CSE SOW ID 2.4.1)(CSE SOW ID 2.4.1.2)

1a. Provide Human and CGF Behaviors (see Visio [OneSAF & GFT Behaviors])

1a1. Given an operational scenario, human and artificial intelligent role players (e.g., BLUFOR, OPFOR, CIV) will executeoperationally relevant behaviors (e.g., battle drills, civilian reaction to battle).1a2. Entities maneuver while avoiding collisions.1a3. Entities behaviors can be controlled by operational/tactical graphics received from TMT and MCIS (ADP 1-02, MILSTD 2525).1a4. NPCs have adjustable behavior models.1a5. Provides automated route planning and selection, accounting for terrain and trafficiability

2. Squad: Refined Movement & Maneuver WfF(CSE SOW ID 2.1.22)

2a. Replication of Traveling, Traveling Overwatch, and Bounding Overwatch movement techniques by unit type IOT position combat power to establish the conditions for maneuver (ADP-3-90).

Given an operational scenario, IAW appropriate tactical tasks (e.g., under direct & indirect fire in a movement to contact / react to contact scenario), a Unit will have the ability to conduct:2a1. Traveling movement techniques2a2. Traveling overwatch movement techniques2a3. Bounding overwatch movement techniques2a4. AI reasoning over terrain.

2b. Forms of maneuver are distinct tactical combinations of fire and movement with a unique set of doctrinal characteristics that differ primarily in the relationship between the maneuvering force and the enemy. The Army has five forms of maneuver—envelopment, frontal assault, infiltration, penetration, and turning movement (ADP 3-90).

Given an operational scenario, IAW appropriate tactical tasks (e.g., under direct & indirect fire in a movement to contact / react to contact scenario), a Unit will have the ability to conduct:2b1. Envelopment2b2. Frontal assault2b3. Infiltration2b4. Penetration2b5. Turning movement

2c. Command and Control with human controlled and CGF forces.

2c1. Human player can command and control with CGF forces acting IAW doctrine, tactics, techniques and procedures. 2c2. EXCON, OPFOR, WHITECELL, LCOAON, HICON, and BLUEFOR players can control aggregate formations.

3. Platoon Mission Command WfF(CSE SOW ID 2.1.22)

3a. Communicate/C2 in a tactical scenario.Physical/Virtual Replication of Tactical Radio Net

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a1. To record and replay comms3a2. Interoperate and send messages with JBC-P, send/receive identified messages (Visio)3a3. To interoperate and send / receive position & location3a4. Record, replay, and incorporate comms into AAR

4. Company level Blue force structure (BLUFOR), OPFOR, and Civilian (Green), Allied, Neutral, and other colors. (CSE SOW ID 2.4.1.2.1)

4. (ArmyOrg Server, ODIN) Ability to access, download, replicate, edit and display force structure, hierarchy, and native command links doctrinally correct for incorporation into scenario. OPCON, TACON, ADCON. Joint Enablers (e.g., Link16 to support AH64E, Air Defense Warnings, and Artillery Defense systems).

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:4a1. Aggregate, de-aggregate, & C24a2. Through TMT, access, automatically/manually download (Army Org Server, ODIN, DATE), replicate, create, edit, and display force structure, hierarchy, and native command links.Dynamic Organization as mission and fragmentary orders require.4a3. Replicate Joint Enablers (e.g., Link16 to support AH64E, Air Defense Warnings, and Artillery Defense systems).





TSS


5. Refined Fires WfF(CSE SOW ID 2.1.22)

5a. Integration of AFATDS, PFED, & MFED (Fires handheld)

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:5a1. Conduct CFF missions and report BDA.5a2. Bidirectional AFATDS to simulation communications5a3. Replicate the complete sensor to shooter process

5b. Incorporation of Fire ammunition data Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:5b1. Select different Fire ammunition data

5c. Replication of Fires battlefield effects Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:5c1. Replicate Fires battlefield effects

5d. Fully automated replication of BN mortars assigned as direct support to operations.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:5a. Conduct CFF missions and report BDA.5b. Select different Fire ammunition data5c. Replicate Fires battlefield effects5d. Bidirectional AFATDS to simulation communications5e. Replicate the complete sensor to shooter process



Revised CAPSET 1-TSSCS 1 MVP Standard Clearance Gate

TSS


6. PMESII-PT: Military, Infrastructure, Physical Env(CSE SOW ID 2.4.1.2.2)

6a. Defined via Visio Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:6a1. Select and tailor the variables during exercise planning & replicate in a movement to contact tactical scenario6a2. OE variables influence the virtual operational environment.6a3. OE variables are dynamic ( environment is altered, influencing military decisions). 6a4. OE variables effect Unit decision making (OPFOR, BLUFOR, White Cell).6a5. Weather impacts operations (e.g., humidity impacts FLIR).6a6. Representation of a free thinking hybrid synthetic OPFOR/threats and other exercise CGF entities.

7. METT-TC considerations(CSE SOW ID 2.4.1.2.2)

7a. Defined via ADP 3-90, Offense and Defense Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:7a1. Input text for METT-TC considerations comments in unit planning.7a2. Mission variable influences CGF behaviors and impacts the virtual OE.7a3. The AAR automatically correlates SIGACTS to METT-TC mission variables.

8. Refined crowd behaviors / pattern of life(CSE SOW ID 2.4.1.2.2)

8a. Defined via Visio Given an operational scenario, IAW appropriate tactical tasks, civilians will have the ability to:8a1. Exhibit Second/third order effects on/of military operations.8a2. Riot / Demonstrate (peaceful / violent)8a3. Portray Tribal/family relationships8a4. Commute to work / shop / attend religious gatherings / go to school8a5. Conduct Mass migrations / refugee / displaced civilian operations




TSS

RVCT Soldier Software

1. Platform C2-1a. JBCP Mission Command: messages, POS/LOC 1b. Net Warrior Mission CMD: message, POS/LOC1c. CPCE Mission Commands: messages, POS/LOC(CSE SOW ID 2.1)(CSE SOW ID 2.4.2.2.1.2)

1. Send and receive Soldier C2 messages by JBCP, Net Warrior, and CPCE2. Send and receive POS/LOC by JBCP, Net Warrior, and CPCE

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a. Execute Solder C2 messages (JBCP, Net Warrior, and CPCE) and send/receive POS/LOC in a movement to contact/react to contact tactical scenario 1b. Conduct Movement and Maneuver in a Semi-Immersive environment.

2. Sensors-Ground Sensors: proximity, cued set, intelligent nodes and networked fields(CSE SOW ID 2.4.2.2.1.6)

2a. Ability to detect Enemy movement by sensor type (proximity, cued set, intelligent nodes and networked fields)

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Replication of ground sensors by enemy movement in a movement to contact/react to contact tactical scenario.2a2. PLT/CO UAS (e.g., Raven), Ground Moving Target Indicator (GMTI)

3. Multi-spectral (Night Vision, FLIR, Thermal, laser, IR Strobe [flashlight], GLINT) Device(CSE SOW ID 2.4.2.2.1.6)

3a. Ability to display multi-spectral from the 1st person POV.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a1. Identify and engage enemy in night vision mode with proper field of view in a movement to contact mission.3a2. Correctly displays thermal signatures (e.g., AN/PAS-13).3a3. Correctly display multi-spectral modes.

4. 3D Model equipment list(CSE SOW ID 2.4.2.2.1.5)

4a. Replicate the 3D model equipment list 4b. Replicate models with modularity

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:4a. Replicate equipment qualities in the 3D model equipment list 4b. Soldiers can mount a platform (e.g., M119 model) and replace the original equipment (e.g., 50 cal machine gun) with different equipment (e.g., Mk 19 grenade launcher). prior to a movement to contact mission4c. Import 3D models4d. Publish 3D model specification4e. Represent model performance as defined by CCDC DAC parametric and WWEG.4f. Models interact appropriately within environment (e.g. tanks drive through walls)4g. Models must be correctly articulated with damage states. Objective: dynamic physics.




TSS


5. Player Interactions as Avatar(CSE SOW ID 2.5.12.6.2.6)

Ability to:5.A Shoot their assigned weapons or special weapons in an inventory or mounted on a platform5B. Move individually, as part of a formation, or a piece of equipment/vehicle51c. Communicate with simulated tactical communications with a bridge to real world mission command – both to human and CGF forces

Given an operational scenario, human and artificial intelligent role players (e.g., BLUFOR, OPFOR, CIV) will1. execute operationally relevant and realistic behaviors (e.g., battle drills, civilian reaction to battle).2. Give and Receive Orders to CGF Forces, human players, subordinates, enablers, and higher headquarters3. Interact with all objects and maneuver all vehicles4. Contain inventory of doctrinally correct equipment5. Send Receive messages IAW doctrinally Correct equipment6. Conduct all individual movements and maneuvers outlined in Visio7. Restrained by real world physics and equipment limitations




TSS

Interoperability

1. Initial Mission Command Adapter - Basic MCIS/Sim -Integration of TSS and MCA to Ground and Aviation C2 messages, POS/LOC, & Chat.(CSE SOW ID 2.1)(CSE SOW ID 2.1.16)

1a. Send and receive Ground to Air/Air to Ground C2 messages.1b. Send and receive Ground to Air/Air to Ground C2 POS/LOC.1c. Send and receive Ground to Air/Air to Ground C2 Chat.1d. Interoperability defined in with Specific MCIS and messages via Visio

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1. Send and receive Ground to Air/Air to Ground C2 messages, POS/LOC, & Chat in a movement to contact/react to contact tactical scenario.

Scalability

1. Aggregation: Individual to SQD, Squad to Platoon(CSE SOW ID 2.1.34)

1a. Ability to Aggregate and De-aggregate with respect to Force Structure and Task organization (Ind to SQD, SQD to PLT, PLT to CO) in the different modalities (e.g., human in the loop, human controlling CGF, first person view, C2 view) IAW with Visio aggregation/disaggregation.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a1.Execute Aggregate and De-aggregate in a tactical scenario to support Command & Control 1a2. Aggregation/disaggregation is tied to operationally realistic behaviors.

2. Multiple instances of SIM Engine (20-100), each with 1,000 entities.1 exercise with 100,000 entities20 exercises with 5,000 entities each100 exercises with 1,000 entities each

1,000 in the field of view.(CSE SOW ID 2.4.5.1)

2a. Large Groups of people with autonomous non-complex behaviors maneuvering with collision avoidance (walking, driving cars on a route, waiting for bus, large groups standing around)

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Execute 80,000 civilian personnel with non-complex behaviors in an urban pattern of life (walking, driving cars on a route, waiting for bus, large groups standing around)

2b. Large Groups of people with autonomous complex behaviors (Rioting, Running away from danger, Running toward danger [e.g., First Responder], Angry/screaming in place)

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2b1. Execute 40,000 civilian personnel with complex behaviors in an urban pattern of life (Rioting, Running away from danger, Running toward danger [e.g., First Responder], Angry/screaming in place) 2b1. Performance efficient and cost effective solution that maintains at least 60 FPS with advanced graphic options enabled, simulating XXX, YYY, ZZZ fidelity entities, using a dynamic entity load balancing. Cost, entity number, entity fidelity, density per server.

3. Multiple exercises (20 to 100), each with 1,000 entities, can be run on a single STE IS Server. 1 exercise with 100,000 entities20 exercises with 5,000 entities each100 exercises with 1,000 entities each(CSE SOW ID 2.5.14.6)

3a. Ability to control all entities within an exercise. Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a1. EXCON has full control of entities and Units within one exercise.




TSS


1. PLT Behaviors(CSE SOW ID 2.4.1)(CSE SOW ID 2.4.1.2)


1a1. Given an operational scenario, human and artificial intelligent role players (e.g., BLUFOR, OPFOR, CIV) will execute operationally relevant behaviors (e.g., battle drills, civilian reaction to battle).1a2. Unit maneuver while avoiding collisions.1a3. Unit behaviors can be controlled by operational/tactical graphics received from TMT and MCIS (ADP 1-02, MILSTD 2525).1a4. NPCs have adjustable behavior models.1a5. Provides automated route planning and selection, accounting for terrain and trafficiability

2. PLT Refined Movement & Maneuver WfF(CSE SOW ID 2.1.22)

2a. Replication of Movement techniques of Traveling, Traveling Overwatch, & Bounding Overwatch by unit type IOT positioning of combat power to establish the conditions for maneuver (ADP 3-90)

2a1. Unit has ability to conduct traveling movement techniques under direct & indirect fire in a movement to contact / react to contact scenario 2a2. Unit has ability to conduct traveling overwatch movement techniques under direct & indirect fire in a movement to contact / react to contact scenario 2a3. Unit has ability to conduct bounding overwatch movement techniques under direct & indirect fire in a movement to contact / react to contact scenario2a4. AI reasoning over terrain.

2b. Forms of maneuver are distinct tactical combinations of fire and movement with a unique set of doctrinal characteristics that differ primarily in the relationship between the maneuvering force and the enemy. The Army has five forms of maneuver—envelopment, frontal assault, infiltration, penetration, and turning movement (ADP 3-90)

2b1. Unit has ability to conduct envelopment under direct & indirect fire in a movement to contact / react to contact scenario 2b2. Unit has ability to conduct frontal assault under direct & indirect fire in a movement to contact / react to contact scenario 2b3. Unit has ability to infiltration under direct & indirect fire in a movement to contact / react to contact scenario 2b4. Unit has ability to conduct penetration under direct & indirect fire in a movement to contact / react to contact scenario 2b5. Unit has ability to conduct turning movement under direct & indirect fire in a movement to contact / react to contact scenario


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2c1. Human player can command and control with CGF forces acting IAW doctrine, tactics, techniques and procedures. 2c2. EXCON, OPFOR, WHITECELL, LCOAON, HICON, and BLUEFOR players can control aggregate formations.

3. Company Mission Command WfF(CSE SOW ID 2.1.22)

3a. Physical/Virtual Replication of Tactical Radio Net 3b. Ability to record and replay comms3c. Ability to interoperate and send messages with JBCP3d. Ability to interoperate and send / receive position & location3e. CGF aggregates data for reports.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a. Communicate/C2 in a tactical scenario.3b. Incorporate comms into AAR (EXCON, OC-T). 3c. Send/receive identified messages (Visio).3d. Send / receive location & position.3e. Replicate tactical radio net bridged to real world tactical radio. 3f. Send / Receive / C2 using an ATAK device.3g. Simulation reduces duplicate CGF reports.

4. Battalion level Blue force structure (BLUFOR), OPFOR, and Civilian (Green), Allied, Neutral, and other colors. (CSE SOW ID 2.4.1.2.1)

4a. (ArmyOrg Server, ODIN) Ability to access, download, replicate, edit and display force structure, hierarchy, and native command links doctrinally correct for incorporation into scenario. OPCON, TACON, ADCON. Joint Enablers (e.g., Link16 to support AH64E, Air Defense Warnings, and Artillery Defense systems).

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:4a1. Aggregate, de-aggregate, & C24a2. Through TMT access, automatically/manually download (Army Org Server, ODIN, DATE), replicate, create, edit, and display force structure, hierarchy, and native command links. Dynamic Organization as mission and fragmentary orders require.4a3. Replicate Joint Enablers (e.g., Link16 to support AH64E, Air Defense Warnings, and Artillery Defense systems).




TSS



5a. Integration of AFATDS, PFED, & MFED (Fires handheld)5b. Incorporation of Fire ammunition data5c. Replication of Fires battlefield effects5d. Fully automated replication of BN mortars assigned as direct support to operations, direct support artillery BN, GS Artillery Fires.





TSS


1. PLT Behaviors(CSE SOW ID 2.4.1)(CSE SOW ID 2.4.1.2)


1a1. Ability to execute behaviors in an operational scenario, IAW appropriate tactical tasks.

2. PLT Refined Movement & Maneuver WfF(CSE SOW ID 2.1.22)

2a. Replication of Movement techniques of Traveling, Traveling Overwatch, & Bounding Overwatch by unit type IOT positioning of combat power to establish the conditions for maneuver (ADP 3-90)

2a1. Unit has ability to conduct traveling movement techniques under direct & indirect fire in a movement to contact / react to contact scenario 2a2. Unit has ability to conduct traveling overwatch movement techniques under direct & indirect fire in a movement to contact / react to contact scenario 2a3. Unit has ability to conduct bounding overwatch movement techniques under direct & indirect fire in a movement to contact / react to contact scenario2a4. AI reasoning over terrain.


2b1. Unit has ability to conduct envelopment under direct & indirect fire in a movement to contact / react to contact scenario 2b2. Unit has ability to conduct frontal assault under direct & indirect fire in a movement to contact / react to contact scenario 2b3. Unit has ability to infiltration under direct & indirect fire in a movement to contact / react to contact scenario 2b4. Unit has ability to conduct penetration under direct & indirect fire in a movement to contact / react to contact scenario 2b5. Unit has ability to conduct turning movement under direct & indirect fire in a movement to contact / react to contact scenario


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2c1. Human player can command and control with CGF forces acting IAW doctrine, tactics, techniques and procedures. 2c2. EXCON, OPFOR, WHITECELL, LCOAON, HICON, and BLUEFOR players can control aggregate formations.

3. Company Mission Command WfF(CSE SOW ID 2.1.22)

3a. Physical/Virtual Replication of Tactical Radio Net 3b. Ability to record and replay comms3c. Ability to interoperate and send messages with JBCP3d. Ability to interoperate and send / receive position & location3e. CGF aggregates data for reports.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a. Communicate/C2 in a tactical scenario.3b. Incorporate comms into AAR (EXCON, OC-T). 3c. Send/receive identified messages (Visio).3d. Send / receive location & position.3e. Replicate tactical radio net bridged to real world tactical radio. 3f. Send / Receive / C2 using an ATAK device.3g. Simulation reduces duplicate CGF reports.

4. Battalion level Blue force structure (BLUFOR), OPFOR, and Civilian (Green), Allied, Neutral, and other colors. (CSE SOW ID 2.4.1.2.1)

4a. (ArmyOrg Server, ODIN) Ability to access, download, replicate, edit and display force structure, hierarchy, and native command links doctrinally correct for incorporation into scenario. OPCON, TACON, ADCON. Joint Enablers (e.g., Link16 to support AH64E, Air Defense Warnings, and Artillery Defense systems).

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:4a1. Aggregate, de-aggregate, & C24a2. Through TMT access, automatically/manually download (Army Org Server, ODIN, DATE), replicate, create, edit, and display force structure, hierarchy, and native command links. Dynamic Organization as mission and fragmentary orders require.4a3. Replicate Joint Enablers (e.g., Link16 to support AH64E, Air Defense Warnings, and Artillery Defense systems).




TSS



5a. Integration of AFATDS, PFED, & MFED (Fires handheld)5b. Incorporation of Fire ammunition data5c. Replication of Fires battlefield effects5d. Fully automated replication of BN mortars assigned as direct support to operations, direct support artillery BN, GS Artillery Fires.





TSS


6. PMESII-PT: Military, Infrastructure, Physical Env(CSE SOW ID 2.4.1.2.2)

6a. Defined via Visio Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:6a1. Select and tailor the variables during exercise planning & replicate in a movement to contact tactical scenario6a2. OE variables influence the virtual operational environment.6a3. OE variables are dynamic ( environment is altered, influencing military decisions). 6a4. OE variables effect Unit decision making (OPFOR, BLUFOR, White Cell).6a5. Weather impacts operations (e.g., humidity impacts FLIR).


7a. Defined via ADP 3-90, Offense and Defense Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:7a1. Input text for METT-TC considerations comments in unit planning.7a2. Mission variable influences CGF behaviors and impacts the virtual OE.7a3. The AAR automatically correlates SIGACTS to METT-TC mission variables.


8a. Defined via Visio Given an operational scenario, IAW appropriate tactical tasks, civilians will have the ability to:8a1. Exhibit Second/third order effects on/of military operations.8a2. Riot / Demonstrate (peaceful / violent)8a3. Portray Tribal/family relationships8a4. Commute to work / shop / attend religious gatherings / go to school8a5. Conduct Mass migrations / refugee / displaced civilian operations




TSS RVCT Soldier

Software

1. Platform C2-1a. JBCP Mission Command: messages, POS/LOC 1b. Net Warrior Mission CMD: message, POS/LOC1c. CPCE Mission Commands: messages, POS/LOC1d. FM radio1e. Handheld Computing Environment (HH CE)1f. Mounted Computing Environment (Mounted CE)(CSE SOW ID 2.1)(CSE SOW ID 2.4.2.2.1.2)

1. Send and receive Soldier C2 messages by JBCP, Net Warrior, and CPCE2. Send and receive POS/LOC by JBCP, Net Warrior, and CPCE3. Replicate tactical radio net bridged to real world tactical radio.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a. Execute Soldier C2 messages (JBCP, Net Warrior, CPCE, HH CE, Mounted CE) and send/receive data. POS/LOC in a movement to contact/react to contact tactical scenario. 1b. Conduct Movement and Maneuver in a Semi-Immersive environment.

2. Sensors-Ground Sensors: proximity, cued set, intelligent nodes and networked fields.(CSE SOW ID 2.4.2.2.1.6)

2a. Ability to detect Enemy movement by sensor type (proximity, cued set, intelligent nodes and networked fields).

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Replication of ground sensors by enemy movement in a movement to contact/react to contact tactical scenario.2a2. PLT/CO UAS (e.g., Raven), Ground Moving Target Indicator (GMTI).2a3. Communications and sensors impacted by terrain.


3. Ability to display multi-spectral from the 1st

person POV.4. View UAS feeds.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a. Identify and engage enemy in night vision mode with proper field of view in a movement to contact mission.3b. Correctly displays thermal signatures (e.g., AN/PAS-13).3c. Correctly display multi-spectral modes.

4. 3D Model equipment list.(CSE SOW ID 2.4.2.2.1.5)

4a. Replicate the 3D model equipment list. 4b. Replicate models with modularity.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:4a. Replicate equipment qualities in the 3D model equipment list. 4b. Soldiers can mount a platform (e.g., M119 model) and replace the original equipment (e.g., 50 cal machine gun) with different equipment (e.g., Mk 19 grenade launcher). prior to a movement to contact mission.4c. Import 3D models.4d. Publish 3D model specification.4e. Represent model performance as defined by CCDC DAC parametric and WWEG.4f. Models interact appropriately within environment (e.g. tanks drive through walls).4g. Models must be correctly articulated with damage states. Objective: dynamic physics.




TSS RVCT Soldier

Software

Player Interactions as Avatar(CSE SOW ID 2.5.12.6.2.6)

Ability to:1a. Shoot their assigned weapons or special weapons in an inventory or mounted on a platform1b. Move individually, as part of a formation, or a piece of equipment/vehicle1c. Communicate with simulated tactical communications with a bridge to real world mission command – both to human and CGF forces

Given an operational scenario, human and artificial intelligent role players (e.g., BLUFOR, OPFOR, CIV) will1. execute operationally relevant and realistic behaviors (e.g., battle drills, civilian reaction to battle).2. Give and Receive Orders to CGF Forces, human players, subordinates, enablers, and higher headquarters3. Interact with all objects and maneuver all vehicles4. Contain inventory of doctrinally correct equipment5. Send Receive messages IAW doctrinally Correct equipment6. Conduct all individual movements and maneuvers outlined in Visio7. Restrained by real world physics and equipment limitations8. Semi-Immersive players must be able to interact with high-fidelity FFF BLUFOR platform representations, and low-fidelity FFF OPFOR platform.




TSS

Interoperability

2. LVC-IA interoperability (CSE SOW ID 2.4.2.3)

1. TSS Initialized LVC-IA.2. Send and receive traffic with HITS.3. Send and receive traffic with JLCCTC.4. Interoperability defined in with Specific MCIS and messages via Visio.5. Fair fight adjudication between LVC-IA and STE.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1. Unit can situational awareness and tactical information with Live and constructive units. 2. Fully correlated data to ensure fair fight adjudication.3. Fully correlated terrain to ensure fair fight adjudication.4. No duplicate entities in mission command information systems.

Scalability

1. Aggregation: Platoon to Company

(CSE SOW ID 2.1.34)1a. Ability to Aggregate and De-aggregate with respect to Force Structure and Task organization (Ind to SQD, SQD to PLT, PLT to CO) in the different modalities (e.g., human in the loop, human controlling CGF, first person view, C2 view) IAW with Visio aggregation/disaggregation.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a1. Execute Aggregate and De-aggregate in a tactical scenario to support Command & Control 1a2. Aggregation/disaggregation is tied to operationally realistic behaviors.

2. Multiple instances of SIM Engine (20-100), each with 5,000 entities.1 exercise with 500,000 entities20 exercises with 25,000 entities each100 exercises with 5,000 entities each


2a. Large Groups of people with autonomous non-complex behaviors maneuvering with collision avoidance (walking, driving cars on a route, waiting for bus, large groups standing around, patterns of life).

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Execute 500,000 civilian personnel with non-complex behaviors in an urban pattern of life (walking, driving cars on a route, waiting for bus, large groups standing around, patterns of life) .2a2. A Company of BLUEFOR.2a3. A Company of OPFOR.2a4. Maintain 60 frames per second (FPS) with a minimum of 4K resolution.

2b. Large Groups of people with autonomous complex behaviors (Rioting, Running away from danger, Running toward danger [e.g., First Responder], Angry/screaming in place, patterns of life).

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2b1. Execute 250,000 civilian personnel with complex behaviors in an urban pattern of life (Rioting, Running away from danger, Running toward danger [e.g., First Responder], Angry/screaming in place, patterns of life) .2b2. A platoon of BLUEFOR.2b3. A company of OPFOR.2b4. Maintain 60 frames per second (FPS) with a minimum of 4K resolution.

3. Ownership transfer of entities and PLT Units.(CSE SOW ID 2.5.14.6)

3a. Ability to transfer Control Cell and Player control within an exercise.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a1. EXCON has full control of entities and Units within one exercise.3a2. Dynamic transfer of entity control during exercises.




TSS


1. Company Behaviors(CSE SOW ID 2.4.1)(CSE SOW ID 2.4.1.2)


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a. Execute behaviors in simulated mission environment.

2. Company Refined Movement & Maneuver WfF(CSE SOW ID 2.1.22)

2a. Replication of Movement techniques by unit type IOT position combat power to establish the conditions for maneuver (ADP 3-90)

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Unit has ability to conduct traveling movement techniques under direct & indirect.2a2. Unit has ability to conduct traveling overwatch movement techniques under direct & indirect fire.2a3. Unit has ability to conduct bounding overwatch movement techniques under direct & indirect fire.2a4. AI reasoning over terrain..


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to conduct:2b1. An envelopment under direct & indirect fire.2b2. A frontal assault under direct & indirect fire.2b3. An infiltration under direct & indirect fire.2b4. A penetration under direct & indirect fire. 2b5. A turning movement under direct & indirect fire.

3. Battalion Mission Command WfF(CSE SOW ID 2.1.22)

3a. Physical/Virtual Replication of FM and Digital Tactical Radio Net for Blue Force, Red Forces, Green Forces, Black Forces, and Gray Forces.

Blue Forces = Friendly ForcesRed Forces = Hostile ForcesGreen Forces = CiviliansBlack Forces = GovernmentGrey Forces = Non-Governmental Forces (NGO)

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a1. Communicate/C2 in a tactical scenario.3a2. Incorporate comms into AAR (EXCON, OC-T). 3a3. Send/receive identified messages (Visio).3a4. Send / receive location & position.3a5. Replicate tactical radio net bridged to real world tactical radio. 3a6. Send / Receive / C2 using an ATAK device.3a7. Simulation reduces duplicate CGF reports.3a8. Record and replay comms3a9. Interoperate and send messages with JBCP3a10. Interoperate and send / receive position & location3a11. CGF aggregates data for reports.

4. Brigade level Blue force structure (BLUFOR), OPFOR, and Civilian (Green), Allied, Neutral, and other colors(CSE SOW ID 2.4.1.2.1)

4a. Use approved force structure data sources (e.g., ArmyOrg Server, ODIN) to provide doctrinally correct force structures in the scenario.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:4a1. Aggregate, de-aggregate, & C24a2. Through TMT access, automatically/manually download (Army Org Server, ODIN, DATE), replicate, create, edit, and display force structure, hierarchy, and native command links.4a3. Dynamic organization as mission and fragmentary orders require.4a4. Replicate Joint Enablers (e.g., Link16 to support AH64E, Air Defense Warnings, and Artillery Defense systems). 4a5. Enable OPCON, TACON, ADCON.


5a. Automated and manual replication of Fires in the operational environment

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:5a1. Fully automate replication of BN/BCT mortars/artillery assigned as direct support to operations.5a2. Conduct call for fire and counterfire missions and report BDA.5a3. Replicate Fires battlefield effects with appropriate visuals, sounds, and damage.5a4. Replicate the complete sensor to shooter process.5a5. Use AFATDS to perform Fires WfF.5a6. Use PFED, & MFED (Fires handheld) to make a call for fire.5a7. Incorporate Fire ammunition data.5a8. Select different Fire ammunition data.5a9. Bidirectional AFATDS to simulation communications.5a10. Indirect fires impacted by terrain.




TSS


6. PMESII-PT: Military, Infrastructure, Physical Environment(CSE SOW ID 2.4.1.2.2)

6a. Provide dynamic OE variables in the simulated mission environment (Defined via Visio)

Given an operational scenario, IAW appropriate tactical tasks, dynamic OE variables:6a1. Provide visual and auditory cues in the simulated mission environment.6a2. Influence the simulated mission environment.6a3. Alter the environment. 6a4. Effect Unit decision making (OPFOR, BLUFOR, White Cell).6a5. Impact operations (e.g., weather effects on terrain trafficability, humidity impacts FLIR, fog limits line of sight).


7a. Provide dynamic mission variables that impact the simulated mission environment (Defined via ADP 3-90, Offense and Defense)

Given an operational scenario, IAW appropriate tactical tasks, the Unit will have the ability to:7a1. Input METT-TC considerations during unit planning.7a2. Mission variable influences CGF behaviors and impacts the simulated mission environment.7a3. The AAR automatically correlates SIGACTS to METT-TC mission variables.


8a. Provide dynamic crowd behaviors / patterns of life (Defined via Visio)

Given an operational scenario, IAW appropriate tactical tasks, civilians will have the ability to:8a1. Exhibit Second/third order effects on/of military operations.8a2. Riot / Demonstrate (peaceful / violent)8a3. Portray Tribal/family relationships8a4. Commute to work / shop / attend religious gatherings / go to school8a4. Conduct Mass migrations / refugee / displaced civilian operations




TSS


1. Platform C2-1a. JBCP Mission Command: messages, POS/LOC 1b. Net Warrior Mission CMD: message, POS/LOC1c. CPCE Mission Commands: messages, POS/LOC(CSE SOW ID 2.1)(CSE SOW ID 2.4.2.2.1.2)

1. Send and receive Soldier C2 messages by JBCP, Net Warrior, and CPCE2. Send and receive POS/LOC by JBCP, Net Warrior, and CPCE

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a. Execute Solder C2 messages (JBCP, Net Warrior, and CPCE) and send/receive POS/LOC in a movement to contact/react to contact tactical scenario 1b. Conduct Movement and Maneuver in a Semi-Immersive environment.

2. Sensors-Ground Sensors: proximity, cued set, intelligent nodes and networked fields(CSE SOW ID 2.4.2.2.1.6)

2a. Ability to detect Enemy movement by sensor type (proximity, cued set, intelligent nodes and networked fields)

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Replication of ground sensors by enemy movement in a movement to contact/react to contact tactical scenario.2a2. PLT/CO UAS (e.g., Raven), Ground Moving Target Indicator (GMTI)2c. Communications and sensors impacted by terrain.


3. Ability to display multi-spectral from the 1st person POV.4. View UAS feeds.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a1. Identify and engage enemy in night vision mode with proper field of view in a movement to contact mission.3a2. Correctly displays thermal signatures (e.g., AN/PAS-13).3a3. Correctly display multi-spectral modes.

4. 3D Model equipment list(CSE SOW ID 2.4.2.2.1.5)

4a. Replicate the 3D model equipment list 4b. Replicate models with modularity

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:4a. Replicate equipment qualities in the 3D model equipment list 4b. Soldiers have the ability to mount a platform (e.g., M119 model) and replace the original equipment (e.g., 50 cal machine gun) with different equipment (e.g., Mk 19 grenade launcher). prior to a movement to contact mission4c. Import 3D models4d. Publish 3D model specification4e. Represent model performance as defined by CCDC DAC parametric and WWEG.4f. Models interact appropriately within environment (e.g. tanks drive through walls)4g. Models must be correctly articulated with damage states. Objective: dynamic physics.




TSS



5. Ability to:5a. Shoot their assigned weapons or special weapons in an inventory or mounted on a platform5b. Move individually, as part of a formation, or a piece of equipment/vehicle5c. Communicate with simulated tactical communications with a bridge to real world mission command – both to human and CGF forces





TSS

Interoperability

1. LVC-IA interoperability (CSE SOW ID 2.4.2.3)

1a. Interoperate with LVC-IA 1a1. TSS exchanges simulation data with LVC-IA.1a2. Send and receive traffic, situational awareness, and tactical traffic with HITS through LVC-IA.1a3. Send and receive traffic, situational awareness, and tactical traffic with JLCCTC through LVC-IA.1a4. Interoperate with MCIS through LVC-IA (see Visio specific MCIS and messages) (bi-directional).1a5. Fully correlated data.1a6. Fully correlated terrain.1a7. Fair fight adjudication between LVC-IA simulations and simulators and STE.1a8. No duplicate entities in mission command information systems.

Scalability

1. Aggregation: Company to BN(CSE SOW ID 2.1.34)

1a. Ability to Aggregate and De-aggregate with respect to Force Structure and Task organization (Ind to SQD, SQD to PLT, PLT to CO, CO to BN) in the different modalities (e.g., human in the loop, human controlling CGF, first person view, C2 view) IAW with Visio aggregation/disaggregation.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a1. Perform aggregation and De-aggregation in a tactical scenario to support Command & Control. 1a2. Aggregation/disaggregation is tied to operationally realistic behaviors.

2. 1 STE IS servicer should be able to support: 1 exercise with 800,000 entities20 exercises with 40,000 entities each100 exercises with 8,000 entities each

3,000 in the field of view.

(CSE SOW ID 2.4.5.1)


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Execute 600,000 civilian personnel with non-complex behaviors in an urban pattern of life (walking, driving cars on a route, waiting for bus, large groups standing around, patterns of life)2a2. A Battalion of BLUEFOR.2a3. A Battalion of OPFOR.2a4. Maintain 60 frames per second (FPS) with a minimum of 4K resolution.


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2b1. Execute 100,000 civilian personnel with complex behaviors in an urban pattern of life (Rioting, Running away from danger, Running toward danger [e.g., First Responder], Angry/screaming in place, patterns of life) 2b2. A platoon of BLUEFOR.2b3. A company of OPFOR.2b4. Maintain 60 frames per second (FPS) with a minimum of 4K resolution.

3. Ownership transfer of entities and CO Units.(CSE SOW ID 2.5.14.6)






TSS


1. Battalion Behaviors(CSE SOW ID 2.4.1)(CSE SOW ID 2.4.1.2)

1a. Provide Human and CGF Behaviors (see Visio [OneSAF& GFT Behaviors])

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a1. Execute behaviors in simulated mission environment.

2. Battalion Refined Movement & Maneuver WfF(CSE SOW ID 2.1.22)


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Unit has ability to conduct traveling movement techniques under direct & indirect.2a2. Unit has ability to conduct traveling overwatch movement techniques under direct & indirect fire.2a3. Unit has ability to conduct bounding overwatch movement techniques under direct & indirect fire.2a4. AI reasoning over terrain.



3. Brigade Mission Command WfF(CSE SOW ID 2.1.22)



Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a1. Communicate/C2 in a tactical scenario.3a2. Incorporate comms into AAR (EXCON, OC-T). 3a3. Send/receive identified messages (Visio).3a4. Send / receive location & position.3a5. Replicate tactical radio net bridged to real world tactical radio. 3a6. Send / Receive / C2 using an ATAK device.3a7. Simulation reduces duplicate CGF reports.3a8. Record and replay comms3a9. Interoperate and send messages with JBCP3a10. Interoperate and send / receive position & location3a11. CGF aggregates data for reports.3A12. Communicate with all Common Operating Environment (COE) Computing Environment (CE)

4. Division and Joint Enablers level Blue force structure (BLUFOR), OPFOR, and Civilian (Green), Allied, Neutral, and other colors(CSE SOW ID 2.4.1.2.1)






TSS




Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:5a1. Fully automate replication of BN/BCT mortars/artillery assigned as direct support to operations.5a2. Conduct call for fire and counterfire missions and report BDA.5a3. Replicate Fires battlefield effects with appropriate visuals, sounds, and damage.5a4. Replicate the complete sensor to shooter process.5a5. Use AFATDS to perform Fires WfF.5a6. Use PFED, & MFED (Fires handheld) to make a call for fire.5a7. Incorporate Fire ammunition data.5a8. Select different Fire ammunition data.5a9. Bidirectional AFATDS to simulation communications.5a10. Indirect fires impacted by terrain.




TSS


6. PMESII-PT:Military, Infrastructure,Physical Env, Information and Time(CSE SOW ID 2.4.1.2.2)


6a1. Ability to select and tailor variable in exercise planning & replicate in a movement to contact tactical scenarioGiven an operational scenario, IAW appropriate tactical tasks, dynamic OE variables:6a2. Provide visual and auditory cues in the simulated mission environment.6a3. Influence the simulated mission environment.6a4. Alter the environment. 6a5. Effect Unit decision making (OPFOR, BLUFOR, White Cell).6a6. Impact operations (e.g., disrupt deployment operations, time windows, information warfare).6a7. Provide Intelligence, Information Warfare, Information Management, Public Communications Media6a8. Provide Time.






Given an operational scenario, IAW appropriate tactical tasks, civilians will have the ability to:8a. Exhibit Second/third order effects on/of military operations.8b. Riot / Demonstrate (peaceful / violent)8c. Portray Tribal/family relationships8d. Commute to work / shop / attend religious gatherings / go to school8e. Conduct Mass migrations / refugee / displaced civilian operations




TSS


1. Platform C2-1a. JBCP Mission Command: messages, POS/LOC 1b. Net Warrior Mission CMD: message, POS/LOC1c. CPCE Mission Commands: messages, POS/LOC1d. FM radio1e. Handheld Computing Environment (HH CE)1f. Mounted Computing Environment (Mounted CE)1g. DCGS-A(CSE SOW ID 2.1)(CSE SOW ID 2.4.2.2.1.2)

1. Send and receive Soldier C2 messages by JBCP, Net Warrior, and CPCE2. Send and receive POS/LOC by JBCP, Net Warrior, and CPCE3. Replicate tactical radio net bridged to real world tactical radio. Defined in Visio.


2. Sensors-Ground Sensors: proximity, cued set, intelligent nodes and networked fields.(CSE SOW ID 2.4.2.2.1.6)


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Replication of ground sensors by enemy movement in a movement to contact/react to contact tactical scenario.2a2. PLT/CO UAS (e.g., Raven), Ground Moving Target Indicator (GMTI).2c. Communications and sensors impacted by terrain.

3. Multi-spectral (Night Vision, FLIR, Thermal, laser, IR Strobe [flashlight], GLINT) Device.(CSE SOW ID 2.4.2.2.1.6)

3. Ability to display multi-spectral from the 1st person POV.4. View UAS feeds.








TSS








TSS

Interoperability

1. AFATDS and platform C2 full Call for Fire thread integration

(CSE SOW ID 2.4.1.4.3)

1a. Automated and manual replication of fires in the OE using organic MCIS and Soldier equipment.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a1. Fully automate replication of BN/BCT, DIV, And Joint Enablers mortars/artillery assigned as direct support to operations.1a2. Conduct call for fire and counterfire missions and report BDA.1a3. Replicate Fires battlefield effects with appropriate visuals, sounds, and damage.1a4. Replicate the complete sensor to shooter process.1a5. Use AFATDS to perform Fires WfF.1a6. Use PFED, & MFED (Fires handheld) to make a call for fire.1a7. Incorporate Fire ammunition data.1a8. Select different Fire ammunition data.1a9. Bidirectional AFATDS to simulation communications.

Scalability

1. Aggregation: BN to BCT(CSE SOW ID 2.1.34)

1a. Ability to Aggregate and De-aggregate with respect to Force Structure and Task organization (e.g., CO to BN, BN to BDE) in the different modalities (e.g., human in the loop, human controlling CGF, first person view, C2 view) IAW with Visio aggregation/disaggregation.


2. BDE level scenario performance benchmarking with extensive civilian and traffic background 1.2 million.



Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Execute 800,000 civilian personnel with non-complex behaviors in an urban pattern of life (walking, driving cars on a route, waiting for bus, large groups standing around, patterns of life)2a2. A BDE of BLUEFOR.2a3. A DIV of OPFOR.2a4. Maintain 60 frames per second (FPS) with a minimum of 4K resolution.


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2b1. Execute 200,000 civilian personnel with complex behaviors in an urban pattern of life (Rioting, Running away from danger, Running toward danger [e.g., First Responder], Angry/screaming in place, patterns of life) 2b2. A platoon of BLUEFOR.2b3. A company of OPFOR.2b4. Maintain 60 frames per second (FPS) with a minimum of 4K resolution.

3. Ownership transfer of entities and BN Units.(CSE SOW ID 2.5.14.6)






TSS

Human and

Computer Generated

Forces and

Modeling

1. BDE Behaviors(CSE SOW ID 2.4.1)(CSE SOW ID 2.4.1.2)


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a1. Execute behaviors in simulated mission environment.

2. BDE Refined Movement & Maneuver WfF(CSE SOW ID 2.1.22)


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Unit has ability to conduct traveling movement techniques under direct & indirect.2a2. Unit has ability to conduct traveling overwatch movement techniques under direct & indirect fire.2a3. Unit has ability to conduct bounding overwatch movement techniques under direct & indirect fire.2a4. AI reasoning over terrain.



3. DIV Mission Command WfF(CSE SOW ID 2.1.22)



Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:3a1. Communicate/C2 in a tactical scenario.3a2. Incorporate comms into AAR (EXCON, OC-T). 3a3. Send/receive identified messages (Visio).3a4. Send / receive location & position.3a5. Replicate tactical radio net bridged to real world tactical radio. 3a6. Send / Receive / C2 using an ATAK device.3a7. Simulation reduces duplicate CGF reports.3a8. Record and replay comms3a9. Interoperate and send messages with JBCP3a10. Interoperate and send / receive position & location3a11. CGF aggregates data for reports.3A12. Communicate with all Common Operating Environment (COE) Computing Environment (CE)

4. Division and Joint Enablers level Blue force structure (BLUFOR), OPFOR, and Civilian (Green), Allied, Neutral, and other colors(CSE SOW ID 2.4.1.2.1)






TSS

Human and

Computer Generated

Forces and

Modeling



Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:5a1. Fully automate replication of DIV/Joint Enablers mortars/artillery/rockets/naval gunfire/naval flyouts assigned as direct support to operations.5a2. Conduct call for fire and counterfire missions and report BDA.5a3. Replicate Fires battlefield effects with appropriate visuals, sounds, and damage.5a5. Replicate the complete sensor to shooter process.5a5. Use AFATDS to perform Fires WfF.5a6. Use PFED, & MFED (Fires handheld) to make a call for fire.5a7. Incorporate Fire ammunition data.5a8. Select different Fire ammunition data.5a9. Bidirectional AFATDS to simulation communications.5a10. Indirect fires impacted by terrain





TSS

Human and

Computer Generated

Forces and

Modeling

6. PMESII-PT: Military, Infrastructure,Physical Env, Information and Time(CSE SOW ID 2.4.1.2.2)


Given an operational scenario, IAW appropriate tactical tasks, dynamic OE variables:6a1. Provide visual and auditory cues in the simulated mission environment.6a2. Influence the simulated mission environment.6a3. Alter the environment. 6a4. Effect Unit decision making (OPFOR, BLUFOR, White Cell).6a5. Impact operations (e.g., disrupt deployment operations, time windows, information warfare).6a6. Provide Intelligence, Information Warfare, Information Management, Public Communications Media6a7. Provide Time.






Given an operational scenario, IAW appropriate tactical tasks, civilians will have the ability to:8a. Exhibit Second/third order effects on/of military operations.8b. Riot / Demonstrate (peaceful / violent)8c. Portray Tribal/family relationships8d. Commute to work / shop / attend religious gatherings / go to school8e. Conduct Mass migrations / refugee / displaced civilian operations




TSS


1. Platform C2-1a. JBCP Mission Command: messages, POS/LOC 1b. Net Warrior Mission CMD: message, POS/LOC1c. CPCE Mission Commands: messages, POS/LOC1d. FM radio1e. Handheld Computing Environment (HH CE)1f. Mounted Computing Environment (Mounted CE), Sensor CE, ECE, RTSC CE1g. TAIS1h. AMDWS1i. DCGS-A(CSE SOW ID 2.1)(CSE SOW ID 2.4.2.2.1.2)

1. Send and receive Soldier C2 messages by JBCP, Net Warrior, and CPCE2. Send and receive POS/LOC by JBCP, Net Warrior, and CPCE3. Replicate tactical radio net bridged to real world tactical radio.


2. Sensors-Ground Sensors: proximity, cued set, intelligent nodes and networked fields.

**Coordinate with TRADOC G2 for sensor list and CCDC C5ISR (Susan Harkrider)

(CSE SOW ID 2.4.2.2.1.6)


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Replication of ground sensors by enemy movement in a movement to contact/react to contact tactical scenario.2a2. PLT/CO UAS (e.g., Raven), Ground Moving Target Indicator (GMTI).2c. Communications and sensors impacted by terrain.

3. Multi-spectral (Night Vision, FLIR, Thermal, laser, IR Strobe [flashlight], GLINT) Device.(CSE SOW ID 2.4.2.2.1.6)

3. Ability to display multi-spectral from the 1st

person POV.4. View UAS feeds.








TSS








TSS

Interoperability

Full CP CE and GGCS-A Integration.1a. AFATDS and platform C2 full Call for Fire thread integration.1b. JBCP Mission Command: messages, POS/LOC 1c. Net Warrior Mission CMD: message, POS/LOC1d. CPCE Mission Commands: messages, POS/LOC1e. FM radio1f. Handheld Computing Environment (HH CE)1f. Mounted Computing Environment (Mounted CE), Sensor CE, ECE, RTSC CE1h. TAIS1i. AMDWS1j DCGS-A(CSE SOW ID 2.1)(CSE SOW ID 2.4.2.2.1.2)

1. Bidirectional communication with organic MCIS. Defined in Visio.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:5a. Bidirectionally communicate with between the simulation and MCIS.5b. Provide a Common Operational Picture with appropriate tactical information to influence the Commander’s decision-making process.

Scalability

1. Aggregation: BCT to DIV

(CSE SOW ID 2.1.34)1a. Ability to Aggregate and De-aggregate with respect to Force Structure and Task organization (Ind to SQD, SQD to PLT, PLT to CO) in the different modalities (e.g., human in the loop, human controlling CGF, first person view, C2 view) IAW with Visio aggregation/disaggregation.


2. BCT level scenario performance benchmarking with extensive civilian and traffic background 2 million.

5,000 in the field of view.

(CSE SOW ID 2.4.5.1)


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2a1. Execute 1,400,000 civilian personnel with non-complex behaviors in an urban pattern of life (walking, driving cars on a route, waiting for bus, large groups standing around, patterns of life)2a2. A BDE of BLUEFOR; DIV HHQ/Enablers.2a3. A DIV+ of OPFOR.2a4. Maintain 60 frames per second (FPS) with a minimum of 4K resolution.


Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:2b1. Execute 500,000 civilian personnel with complex behaviors in an urban pattern of life (Rioting, Running away from danger, Running toward danger [e.g., First Responder], Angry/screaming in place, patterns of life) 2a2. A BDE of BLUEFOR; DIV HHQ/Enablers.2a3. A DIV+ of OPFOR.2a4. Maintain 60 frames per second (FPS) with a minimum of 4K resolution.

3. Ownership transfer of entities and BDE Units.(CSE SOW ID 2.5.14.6)






TSS

Artificial Intelligence (AI)(CSE SOW 2.1.25)(CSE SOW 2.1.26)(CSE SOW 2.1.27)(CSE SOW 2.1.28)(CSE SOW 2.1.29)

1. automate steps in the Plan, Prepare, Execute, and Assess cycle.



2. adjust difficulty based on the unit’s training proficiency

2. adjust difficulty based on the unit’s training proficiency 2. Unit’s training proficiency influences OPFOR difficulty (Target only, easy, medium, hard, elite) by adjusting equipment, speed of movement, tactics, and accuracy.

3. use Intelligent Tutoring to increase efficiency inexercise development.

3. use Intelligent Tutoring to increase efficiency in exercise development.

3. use Intelligent Tutoring to increase efficiency inexercise development.

4. use Intelligent Tutoring to provide the training audience informal training objective feedback.



5. use Big Data techniques to analyze and search largedata sets (e.g., data collection) to inform training effectiveness, inform AI/machine learning, and to identify themes.






TSS

Packaging, Handling, Shipping, and Transportation (PHS&T)(CSE SOW 2.9.16) (CSE SOW 2.9.16.1)(CSE SOW 2.9.16.2) (CSE SOW 2.9.16.3)(CSE SOW 2.9.16.4) (CSE SOW 2.9.16.5) (CSE SOW 2.9.16.6)(CSE SOW 2.9.16.7)(CSE SOW 2.9.16.8) (CSE SOW 2.9.16.9) (CSE SOW 2.9.16.10)(CSE SOW 2.9.16.11) (CSE SOW 2.9.16.11.1) (CSE SOW 2.9.16.11.2) (CSE SOW 2.9.16.11.3)(CSE SOW 2.9.16.11.4) (CSE SOW 2.9.16.11.5)

TSS shall conform to Packaging, Handling, Shipping, and Transportation (PHS&T) factors below: 1. modular.2. man portable.3. transportable by commercial air, ship, rail & ground4. Transportable by military air, ship, rail & ground.5. Packaged transit cases that are reusable, ruggedized,weatherproof, lockable, and carried by no more than two persons (less than or equal to 88 pounds).

TSS shall conform to Packaging, Handling, Shipping, and Transportation (PHS&T) factors below: 1. modular.2. man portable.3. transportable by commercial air, ship, rail & ground4. Transportable by military air, ship, rail & ground.5. Packaged transit cases that are reusable, ruggedized,weatherproof, lockable, and carried by no more than two persons (less than or equal to 88 pounds).

TSS shall conform to Packaging, Handling, Shipping, and Transportation (PHS&T) factors below: 1. modular.2. man portable.3. transportable by commercial air, ship, rail & ground4. Transportable by military air, ship, rail & ground.5. Packaged transit cases that are reusable,ruggedized, weatherproof, lockable, and carried by no more than two persons (less than or equal to 88 pounds).



Revised CAPSET MVP TMT Endstate



Revised CAPSET 1 to 5-TMT EndstateCS 1-5 MVP Standard Clearance Gate

PLA

N

Training Objectives

1. Define collective tasks with standards of training proficiency.

(CSE SOW 2.1.19)(CSE SOW 2.5.12.2)

1a. Input proposed training objectives as statements that describe the desired outcome of a training activity in the unit that consist of tasks, conditions, and standards for Commander’s approval.1b. CDR approve or modify training objectives.1c. Ability to access Collective tasks for unit training in CATS (e.g., Infantry, Stryker, Armor, Sustainment, Aviation, & Fires BCTs) (& in Visio)

1a. During exercise design, the exercise planner input proposed training objectives as statements that describe the desired outcome of a training activity in the unit that consist of tasks, conditions, and standards.1b. The CDR approves or modifies training objectives.1c. During execution, the unit leader can assess and modify collective tasks per unit's performance in the tactical scenario.

2. Initial digital Training Support Package (TSP).

(CSE SOW 2.1.14)(CSE SOW 2.5.12.5)(CSE SOW 2.1.29)(CSE SOW 2.5.12.5)

2a. IAW TP 350-70-1 capture exercise and scenario parameters, schedule training resources, instantiate training infrastructure, initialize simulation and MCIS, and generate Training Support Package.

2a. Ability to start simulation with exercise and scenario parameters.2b. Ability to schedule training resources.2c. Automatically connect and configure network and cloud infrastructure.2d. Ability to initialize Simulation and MCIS.2e. Ability to publish TSP IAW TP 350-70-1.

Training Preparation

Activities

1. Download and import Soldier and Unit performance/training records from DTMS/ATIS.

(CSE SOW 2.5.12.2)

1a. Records influence Soldier/Unit performance in the simulation.

1a1. Records influence Soldier/Unit performance in the simulation.

2. Utilize Authoritative Data.(CSE SOW 2.5.12.2)

2a. Incorporate authoritative data into the planning process (e.g., Armyorg server for force structure; ERDC for soil mechanics, material attribution, construction database; CCDC DAC for Ph/Pk; Midb, Meped for models; TRADOC G27 ODIN [DATE, PMESII-PT, Road to war, WWEG]). (see Visio)2b. Edit data to support the training event.2c. CAC Authentication with DOD Active Directory.2d. LDIF2e. JMUL

2a-e1. Execute authoritative data form Armyorg, ERDC, CCDC DAC, Midb-mepd, TRADOC G27 ODIN for in exercise and tactical scenario. 2a2. Ability to log in with CAC and assume role defined in TSP.




PLA

N

Training Preparation

Activities

3. User/role-based access control.(CSE SOW 2.10.1.3.2)CSE SOW 2.5.12.4)

3a. Single Sign on using CAC Authentication with DOD Active Directory.

3a1. Ability to log in with CAC and assume role defined in TSP.

4. Use Existing Exercise Data.(CSE SOW 2.5.12.9.4)

4a. Reuse of previous exercise data to create the new exercise (clone, edit).

4a1. Store exercise data.4a2. Search exercise data.4a3. Clone exercise data.4a4. Modify exercise data.

5. Manuals and Guided Training.(CSE SOW 2.5.12.2)

5a. Manuals digitally available for user on demand.

On demand, the Soldier can access:5a1. CATS5a2. User and troubleshooting manuals.5a3. Doctrinal publications

5b. Guided training is intuitive to the user IAW appropriate doctrine for ease of use.

Guided training is in accordance with:5b1. FM 7.05b2. TC 7-101 5b3. AR 350-TBD5b4. Guided training is user configurable to meet the Soldier’s needs.

6. Aviation Mission Planning Capability (e.g., Aviation Mission Planning).(CSE SOW 2.4.2.2.2.3)

6a. Ingest Aviation Mission Planning Capability data into the TMT.

6a1. Aviation Mission Planning Capability data is ingested into TMT through the RVCT Instructor Operator Station (IOS) via a transferable storage media. 6a2. Aviation Mission Planning Capability data is ingested into TMT through a government computer via a transferable storage media.6a3. Aviation Mission Planning Capability data is ingested into TMT directly from a Mobile/Handheld CE tablet (i.e., Net Warrior Air Tablet) via the network.6a4. TMT accurately imports data.




PLA

N Training Preparation

Activities

7. Collaborative Pre-Execution Checklist.(CSE SOW 2.5.13.1)

7a. Provide a collaborative venue to develop the pre-execution checklist.

The collaborative environment allows participants:7a1. To communicate via voice.7a2. To communicate via chat.7a3. To share screens.7a4. To upload/download files.7a5. To simultaneously edit an exercise.7a6. Allows at least 25 simultaneous participants.

8. Automated Training Identification.(CSE SOW 2.5.12.6.1.7)(CSE SOW 2.5.12.9)

8a. Provide user appropriate training at echelon for the unit.

User at the appropriate echelon can see:8a1. Their echelon.8a2. Two echelons below.8a3. One echelon above.8a.4 Tasks the unit has completed in the 12-month AR 350-1 directed training calendar.8a5. Tasks the unit has completed in ATIS.8a6. Tasks the unit has yet to complete.

9. Automated Training.(CSE SOW 2.1.30)

9a. Automat the TC-7-101 training process. 9a1. Identify training resource requirements.9a2. Identifying times to schedule resources (e.g., RVCT, classrooms, ranges, SVT, kit). 9a3. Dashboard provides availability, approval of requested resources, and status of training resources.




PLA

N

Scenario Design

1. Planning roadmap.(CSE SOW 2.5.13)

1a. IAW TC 7-101 Exercise Design, the planning roadmap is incorporated into the exercise prep.

1a1. The exercise planner, IAW TC 7-101 Exercise Design, can input, modify, delete the planning roadmap.

2. Pre-execution Checklist.(CSE SOW 2.5.13.1)

2b. IAW TC 7-101 Exercise Design, the pre-execution checklist is incorporated in the exercise prep.

2b1. The exercise planner, IAW TC 7-101 Exercise Design, can input, modify, delete the pre-execution checklist.

3. Edit Terrain to Meet Training Objectives.(CSE SOW 2.4.3.6)

3a. The user is able to modify terrain during scenario design to meet training objectives.

3a1. Add/edit rivers, wadis, bridges, roadways, trenches, swap out buildings, obstacles (e.g., concertina wire, abatis, tank trap) battlefield clutter, forest density.

3b. IAW FM 7-0 and Troop Leading Procedures, create scheme of maneuver and operational graphics.

3b1. Overlay ADP 1-02 operational graphics onto the terrain.3b2. Overlay FM25-25 MILSTAND D symbols and MILSTAND B and C symbols onto the terrain. 3b3. Operational graphics and symbols guide computer generated forces and behaviors.3b4. Communicate operational graphics and symbols overlays to MCIS.3b5. Receive operational graphics and symbols from MCIS.

4. Planning(CSE SOW 2.5.12.6.1)

4a. Define exercise parameters. 4a1. Criteria = Standards 4a2.Automated Guide to Assist Planner4a3. Automated Recommendation (Based on current STP)4a4. Option for Manual Creation

4b. Determine exercise time-line. 4b1. Criteria = Standards 4b2.Automated Guide to Assist Planner4b3. Automated Recommendation (Based on current STP)4b4. Option for Manual Creation

4c. Determine whether exercise will be live, virtual, constructive, gaming, or a combination.

4c1. Criteria = Standards 4c2.Automated Guide to Assist Planner4c3. Automated Recommendation (Based on current STP)4c4. Option for Manual Creation

4d. Determine operational theme. 4d1. Criteria = Standards 4d2.Automated Guide to Assist Planner4d3. Automated Recommendation (Based on current STP)4d4. Option for Manual Creation




5. Task and CountertaskDevelopment (CSE SOW 2.5.12.6.2)

2a. Determine OPFOR countertasks.*

Criteria = Standards Automated Guide to Assist PlannerAutomated Recommendation (Based on Unit, Training Objectives)*Option for Manual CreationOption to Edit Manually

2b. Develop OPFOR OB and task organization.*

Criteria = Standards Automated Guide to Assist PlannerAutomated Recommendation (Based on Unit, Training Objectives)*Option for Manual CreationOption to Edit Manually

2c. Select OPFOR tier levels. Criteria = Standards Automated Guide to Assist PlannerAutomated Recommendation (Based on Unit, Training Objectives)*Option for Manual CreationOption to Edit Manually

6. PMESII-PT OE Development(CSE SOW 2.5.12.6.3)

6a. Develop the OE. Criteria = Standards Automated Guide to Assist PlannerAutomated Recommendation Option for Manual CreationOption to Edit Manually

6b. Refine supporting METL tasks and associated task organization.

Criteria = Standards Automated Guide to Assist PlannerAutomated Recommendation Option for Manual CreationOption to Edit Manually

6c. Determine common processes for the desired OE.





6. PMESII-PT OE Development(CSE SOW 2.5.12.6.3)

6d. Determine key events to highlight chosen training objectives.


6e. PMESII-PT variable representation require traceability and causality to be effective in training and required for AAR efforts.





PLA

N ScenarioDesign

7. Orders, Plans, and Instruction Development(CSE SOW 2.5.12.6.4)

4a. Prepare and conduct final exercise planning conference. 4b. Prepare and conduct final exercise briefing. 4c. Develop and issue higher unit warning orders, intelligence estimates and documents to the training unit. 4d. Develop and issue higher unit OPLANs and orders to the training unit. 4e. Develop and issue OPFOR orders. 4f. Develop instructions for role-players. 4g. Develop and issue the road to war to the training unit.

Criteria = Standards Automated Guide to Assist PlannerAutomated RecommendationOption for Manual CreationOption to Edit Manually

8. Aviation Mission Planning Capability Import (e.g., Aviation Mission Planning).(CSE SOW 2.5.13.2)(CSE SOW 2.5.13.7)

8a. Edit Aviation Mission Planning Capability data in TMT. 8a1. TMT capabilities refine Aviation Mission Planning Capability data.8a2. TMT instantiates TSS exercise with updated Aviation Mission Planning Capability data as part of the initialization data.

9. Exercise Design with Defaults.(CSE SOW 2.5.2.1)(CSE SOW 2.5.12)

9a. TMT provides a recommended exercise design with default settings.

9a1. Exercise plan is tailored to the user role.9a2. Exercise planners can manually edit the recommended plan.

10. Single Sign On (SSO).(CSE SOW 2.1.8)

10a. Users can sign into the training system using their Common Access Card (CAC).

10a1. Users can successfully log into the training system using their CAC.10a2. Training system recognizes user role and provides appropriate role-based controls.

10b. Identify non-CAC login 10b1. Users can successfully ID’d in the training system using their CAC.

11. Guided ITS exercise design and recommendations.(CSE SOW 2.1.27)

See Plan – Training Preparation Activities #8 ITS (duplicate)

12. Collaborative Scenario Design(CSE SOW 2.5.12.6.1)(CSE SOW 2.1.24

12a. Provide a collaborative venue to develop the scenario. The collaborative environment allows participants:12a1. To communicate via voice.12a2. To communicate via chat.12a3. To share screens.12a4. To upload/download files.12a5. To simultaneously edit an exercise.




PLA

N

Event Assessment Plan1. Event Assessment Plan(CSE SOW 2.5.13)

1a. Provide event assessment plan. 1a1. Assessment plan provides the elements identified in AR 350-70-1.

PR

EPA

RE

Manage Training Resources

1. Initialize TSS.(CSE SOW 2.5.13.6)(CSE SOW 2.5.13.7)

1a. IAW TP 350-70-1 capture exercise and scenario parameters, schedule training resources, instantiate training infrastructure, initialize sim and MCIS.

1a1. Ability to initialize simulation and MCiS

2. Initial TSP export (MS Office Products and MSDL Export for LVC-IA and MCIS Initialization).(CSE SOW 2.5.12.5)

2a. IAW TP 350-70-1 generate Training Support Package.

2a1. Ability to publish TSP IAW TP 350-70-1.

3. Brigade Resource Provisioning.(CSE SOW 2.5.13.4)(CSE SOW 2.5.13.5)

3a. Exercise planner can ensure all resources required for the exercise have been provisioned and can be instantiated.

3a1. Connectivity with resources.3a2. Thread testing with resources.

4. Cloud Based Training Delivery Squad through Brigade.(CSE SOW 2.5.13.4)

4a. Trainees can access training over the network.

4a1. Processing occurs in the cloud.4a2. Processing occurs on the STE IS edge server.

5. MCIS and CPCE Initialization(CSE SOW 2.5.13)(CSE SOW 2.5.14)

5a. Exercise planner can ensure the MCIS thread and CPCE resources have been provisioned and can be instantiated.

5a1. Connectivity with resources.5a2. Thread testing with resources.

6. Scenario Initialization TSS – BN(CSE SOW 2.5.13.6)(CSE SOW 2.5.13.7)

6a. Exercise planner can initialize the training exercise.

6a1. RVCT initialized and operational.6b1. MCIS initialized.6b3. Initialization includes correct location, mission profile, ability to communicate.

7. Load Aviation Mission Planning Capability Data into TSS AFS.(CSE SOW 2.4.4)(CSE SOW 2.5.12.8)

7a. Crews can modify the Aviation Mission Planning Capability data from within the RVCT Air.

7a1. Crew edited data accurately captured in TMT.7a2. TMT updates the exercise initialization data to include the crew edited data.

8. Automated Delivery.(CSE SOW 2.5.12.6.1) (CSE SOW 2.5.12.6.1.1)

8a. All exercise planning efforts are synchronized

8a1. TMT provides dashboard of changes. 8a2.Exercise planner confirms exercise modifications.




Schedule Army Training Resources

1. Cloud architecture support training needs.

(CSE SOW 2.5.13.4 )

1a. Digital TSP instantiates and configures cloud and network infrastructure (as defined by 350-70-1)

1a1. Prior to a tactical scenario, the Digital TSP instantiates and configures cloud and network infrastructure.

2. Initialize Simulation Environment (TSS, OWT, RVCT, LVC-IA)(CSE SOW 2.1,2.1.10)(CSE SOW 2.1.14)CSE SOW 2.1.17)

2a. Common synthetic environment established for the training event.

2a1. TSS has proper array of training resources (e.g., OWT, RVCT, LVC-IA)2a2. Common Synthetic Environment passes thread testing.2a3. User roles and stations assigned for HICON, LOCON, EXCON, OPFOR, White Cell.2a3. Exercise director verifies Common Synthetic Environment is ready for training execution.

3. Schedule Training Resources Using Army Training Management Capability (ATMC). (CSE SOW 2.1,2.5.20,2.5.21,2.5.22,2.5.12.1,2.5.12.2)

3a. Schedule training event resources. 3a1. Event planner confirms training event resources are scheduled on the right day(s) and time(s).

4. Brigade Level Simulation Support.(CSE SOW 2.5.12.6.1)(CSE SOW 2.1.24)(CSE SOW 2.1.25)(CSE SOW 2.1.26)

4a. Support synchronized with execution of exercise.

4a1. Resources synchronized IAW execution checklist and support includes personnel and equipment.




EXEC

UTE Event

Execution Activities

1. Procedural checklist UI and updates. (CSE SOW 2.5.14.5,2.5.14.6)

1a. Pre-execution check IAW TC 7-101 Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1a1. EXCON can receive status updates and modify status on pre-execution checklist.1a2. EXCON can modify status on pre-execution checklist.

2. Observer views with simple event indicators.(CSE SOW 2.5.14.7)

2a. OC-T has access to current and future MSELs 2b. OC-T has access to training objectives2c. OC-T has free text area for daily report2d. Automated OC-T Updates2e. Coordinate between OC-T and EXCON.

OC-T has access and ability to comment on current and future MSELs.4. OC-T has access and ability to comment on training objectives.5. OC-T has access and ability to comment on free text area for daily reports.6. OC-T and EXCON have voice comms, free cell text, and image share.7. OC-T receives automated alerts (e.g., off plan, missed timed activity [e.g., missed LD], MSEL injected, incorrect location).

3. ITS Recommended Adjustments(CSE SOW 2.5.2.4)

3a. ITS provides recommended scenario adjustments to EXCON and OC-T.

3a1. Scenario adjustments tailor training to the competency of the training audience.3a2. EXCON and OC-T can select, edit, and implement recommendations to employ. 3a3. EXCON and OC-T can dynamically edit task organization, MSEL, and execution checklist.

4. Observer Views(CSE SOW 2.5.14.7)

4a. Duplicate of # 2 above 4a1.

4. ITS Driven Indicators and Views(CSE SOW 2.5.2)

4a. ITS notifies EXCON and OC-T of key events.

4a1. ITS provides EXCON and OC-T notifications of events that will occur.4a2. ITS provides EXCON and OC-T notifications of events that should have occurred (e.g., MSEL, missed lD).4a3. ITS provide EXCON and OC-T notification of events and objectives that have been met4a4. ITS provides EXCON and OC-T recommendations to retrain missed events and objectives during execution.




DistributedEXCON

1. Monitoring, control, scenario adjustment, MSEL synchronization, entity control, communications capture, and data replay – single and multiple EXCONs.(CSE SOW 2.5.14.4)

1. EXCON has ability to monitoring the exercise units and key area environments, either local or geographically distributed.2. EXCON has ability to adjust, add, delete, modify or inject (MSEL, Scenario Key events) to the exercise either local or geographically distributed.3. EXCON has ability to take control of individual entities or unit entities in the exercise either local or geographically distributed.4. EXCON has ability to record audio and video of training units, OPFOR, or entities in the exercise either local or geographically distributed.5. EXCON can monitor the health of the simulation and systems.6. One location (potentially one person) can perform EXCON, WHITE CELL, HICON, OPFOR, LOCON functions simultaneously. 7. OC-T has ability to pause, rewind, replay, fast-forward and record for immediate action correction.

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1. EXCON maintains situational awareness of the exercise units, OPFOR, and Civilians on the Battlefield (local and geographically separated). 2. EXCON maintains situational awareness of key areas of the environment (local and geographically separated). 3. EXCON executes adjustments to MSEL/Scenario Key events (local and geographically separated).4. EXCON can monitor network connectivity, RVCT performance, and the health of the simulation before, during, and after a training event. 5. One location with multiple people performs EXCON, WHITE CELL, HICON, OPFOR, LOCON functions simultaneously for a geographically distributed exercise with multiple ocations (based on scale and complexity).




EXEC

UTE

DataCollection

1. Data tagging, storageand analysis.

(CSE SOW: 2.5.14,2.5.14.16,2.5.14.17,2.5.14.18,2.5.14.19,2.5.14.20 ,2.5.14.21)

1. EXCON has ability to data-tag the exercise SIGACTs/key events, either local or geographically distributed.2. EXCON has ability to store the exercise SIGACTs/key events, either local or geographically distributed.3. EXCON has ability to replay, pause, rewind, fast-forward and record the exercise SIGACTs/key events, either local or geographically distributed.5. TMT automatically meta-tags data from STE systems (e.g., TSS, MC, LVC-IA). 6. Collect audio, visual, live, sensors, optics, mission command views, and data.7. Collect data for standard and custom reports.8. System Health Data for Maintenance.9. Data tagging for Unit Competency Modeling. 10. Utilization Data

Given an operational scenario, IAW appropriate tactical tasks, a Unit will have the ability to:1. EXCON, during the exercise, has ability to data-tag, elements such as the exercise SIGACTs/key events, either local or geographically distributed.2. EXCON, after the exercise, has ability to data-tag, elements such as the exercise SIGACTs/key events, either local or geographically distributed.3. EXCON, during the exercise, has ability to store the exercise, elements such as exercise SIGACTs/key events, either local or geographically distributed.4. EXCON, after the exercise, has ability to store the exercise, elements such as exercise SIGACTs/key events, either local or geographically distributed.5. EXCON, during the exercise, has ability to replay, pause, rewind, fast-forward and record the exercise elements such as exercise SIGACTs/key events, either local or geographically distributed.6. EXCON, after the exercise, has ability to replay, pause, rewind, fast-forward and record the exercise elements such as exercise SIGACTs/key events, either local or geographically distributed.7. Generate standard reports (e.g., Enemy Destroyed, Friendly Destroyed, Ammunition Consumption, Fuel Consumption, Fratricide, Kill Victim Report, Digital Comms, SIGAX, cost avoidance for Live training, system damage report).8. Generate custom report based on user defined criteria.9. Generate System Health report.10. Generate Unit Competency outcomes.11. Generate Utilization Reports (current, historical, Soldier, unit, overall system; plan through assess, execute)




EXEC

UTE

DataCollection

2. Capture User Generated Products.(CSE SOW: 2.5.14.20,2.5.14.21 ,2.5.15.17,2.5.15.18)

2a. TMT captures user generated planning products. 2a1. Maps2a2. Graphics2a3. Orders and Fragmentary orders2a4. Voice2a5. Reports (e.g., Ammunition Status, Fuel Status, SPOT Reports)




ASS

ESS

Exercise Feedback

1. Playback and Analysis CO through BDE Echelon.2. Trend Analysis. 3. Data Lake

(CSE SOW:2.4.2.2.3.4.3,2.4.3.3 ,2.5.15.2)

•1Training Audience has ability to data-tag the exercise SIGACTs/key events, either local or geographically distributed.•2Training Audience has ability to store the exercise SIGACTs/key events, either local or geographically distributed.•3Training Audience has ability to replay, pause, rewind, fast-forward and record the exercise SIGACTs/key events, either local or geographically distributed.

•1OC-T has ability to data-tag the exercise SIGACTs/key events, either local or geographically distributed.•2OC-T has ability to store the exercise SIGACTs/key events, either local or geographically distributed.•3OC-T has ability to replay, pause, rewind, fast-forward and recordthe exercise SIGACTs/key events, either local or geographically distributed.

•Trend analysis to forecast training needs with recommended list of tasks to train for commander’s approval.

•Training Audience, during the exercise, has ability to data-tag, elements such as the exercise SIGACTs/key events, either local or geographically distributed in a movement to contact scenario•Training Audience, after the exercise, has ability to data-tag, elements such as the exercise SIGACTs/key events, either local or geographically distributed in a movement to contact scenario•Training Audience, during the exercise, has ability to store the exercise, elements such as exercise SIGACTs/key events, either local or geographically distributed.•Training Audience, after the exercise, has ability to store the exercise, elements such as exercise SIGACTs/key events, either local or geographically distributed.•Training Audience, during the exercise, has ability to replay, pause, rewind, fast-forward and record the exercise elements such as exercise SIGACTs/key events, either local or geographically distributed.•Training Audience, after the exercise, has ability to replay, pause, rewind, fast-forward and record the exercise elements such as exercise SIGACTs/key events, either local or geographically distributed.

•OC-T, during and after the exercise, has ability to data-tag, elements such as the exercise SIGACTs/key events, either local or geographically distributed in a movement to contact scenario•OC-T, during and after the exercise, has ability to data-tag, elements such as the exercise SIGACTs/key events, either local or geographically distributed in a movement to contact scenario•OC-T, during and after the exercise, has ability to store the exercise, elements such as exercise SIGACTs/key events, either local or geographically distributed.•OC-T, during and after the exercise, has ability to store the exercise, elements such as exercise SIGACTs/key events, either local or geographically distributed.•OC-T, during and after the exercise, has ability to replay, pause, rewind, fast-forward and record the exercise elements such as exercise SIGACTs/key events, either local or geographically distributed.•OC-T, during and after the exercise, has ability to replay, pause, rewind, fast-forward and record the exercise elements such as exercise SIGACTs/key events, either local or geographically distributed.




ASS

ESS

Exercise Feedback

1. Playback and Analysis through CO through BDE Echelon.2. Trend Analysis. 3. Data Lake

(CSE SOW:2.4.2.2.3.4.3,2.4.3.3 ,2.5.15.2)

•Data lake for raw data.•Data lake for training objectives, training calendar, feed ATIS as appropriate per echelon.•Data lake in support of AI/ML for competency learning.•Automated data lake management.

•PMESII-PT variable representation require traceability and causality to be effective in training and required for AAR efforts

•Data lake that can store TBD TB/PB.•Automated data management processes to move data from hot storage to cold storage that implements data migration business rules.•Automated data management processes to purge data that implements purge business rules. •Automated data management process to track data utilization.

•Training audience and OC-T, during and after the exercise, can data-ta, store, and replay, pause, rewind, fast-forward and record exercise elements related to PMESII-PT representation.




ASS

ESS

AfterAction Review (AAR)

1. AAR product generation

(CSE SOW: 2.1.7,2.1.30,2.2,2.5.15,2.5.15.1 ,2.5.15.2,2.5.15.4,2.5.15.5 ,2.5.15.6)

OC-T, during and after the exercise, can generate products to support an “in person” and “paper AAR Format” in a local or geographically distributed manner:OC-T, during and after the exercise, can recorded audio and visual unit actions to MSELs, SIGACTs or training events during the exercise. 1. Review what was supposed to happen:1a. Access and display for review the training objectives and tasks to train

Clearance Gate established by MVP Standard

Expectation is most of the AAR is autogenerated.OC-T/EXCON can edit autogenerated AAR.

2. AAR data replay

(CSE SOW: 2.4.2.2.1.1)

2. Access and display for review what happened for a particular event, chronologically and at squad, plt, co, BN, BCT, DIV, through video unit action recordings and / or unit communications recording:2a. Access and display for review the OPFOR mission and purpose2a. Access and display for review actions before first detection2b. Access and display for review report of first detection or contact2c. Access and display for review reaction to detection or contact2d. Access and display for review any key elements of FRAGO developed during the exercise as selected by OC-T team2e. Access and display for review recorded events during engagement



(CSE SOW: 2.5.15.2)

3a. Access and display for review unit leader mission, intent and concept of operations3. Review what went right and wrong:3a. Ability to and display and input subheading comments below training objective centered on extent to which unit met training objectives3b. Ability to display input subheading comments below commander’s intent on extent to which the unit met commander’s intent3c. Ability to display and input comments from training audience centered on Training Audience learning points in three areas.3c1. Identify training deficiencies3c2. Identify unit’s ability to perform task and meet commander’s intent3c3. Identify safety risks and measures employed to mitigate the risks






ASS

ESS After

Action Review (AAR)

4. AAR reports(CSE SOW: 2.5.15.1)

4. Ability to display and input comments from training audience centered on how the exercise or tasks should be done next time in four areas.4a. Identify if retraining should occur4b. Identify the conditions to modify4c. Identify which tasks to retrain to meet the commander’s intent4d. Identify a more effective way to meet the commander’s intent OC-T, during and after the exercise, can display and input additional topics in a free text manner. OC-T, after the exercise, can produce and paper document of the ARR with multimedia accompanied audio and visual key events.

Clearance Gate established by MVP StandardExpectation is most of the AAR is autogenerated.

OC-T/EXCON can edit autogenerated AAR.

5. Formal AAR PLT to BDE:(CSE SOW: 2.5.12.5)

5a. Provide formal AAR with feedback products. 5a1. Capability to conduct AAR by echelon.5a2. Provide AAR products (e.g., Screen Captures, Video Replay, Voice Replay).

6. Task Performance. (CSE SOW: 2.5.2.3)

6a. Assess task performance. 6a1. Provide task performance visualization (bullet to death ratio) against TE&O.

7. Guided Assessment.

(CSE SOW: 2.5.2.1)

7a. TMT assessment tool enables guided assessment through automated processes.

7a1. Automatically imports exercise data.7a2. Automatically imports/bookmarks SIGACTs.7a3. Automatically imports/bookmarks OC-T observations.7a4. Simultaneous workflow for exercise participants (e.g., BLUEFOR, OPFOR).




ASS

ESS After

Action Review (AAR)

8. Support External AAR Products. (CSE SOW: 2.5.15)

8a. TMT Enables Exercise Director and Exercise Staff to Inject Subjective AAR products into the AAR process.


9. User Defined Reports. (CSE SOW: 2.5.14.20)

9a. TMT enables the User to define reports with available data.


10. Intelligent AAR Product Generation. (CSE SOW: 2.5.15.1)

10a. TMT develops operationally relevant AAR products. 10a.1 Operational relevant products identify trends.10a2. Operationally relevant products recommends additional training opportunities based on the assessment.10a3. CATS focused10a4. OPFOR Behaviors at contact.

11. Recommend Unit Assessment.

11a. TMT provides a CATS based unit assessment 11a1. The unit receives assessment results presented in the form of STP.

12. Automated Performance Assessment.

12a. TMT provides a CATS based unit assessment




ASS

ESS

Training Records

1. Sustaining Training Proficiency (STP)Circle Back

(CSE SOW: 2.5.22)

1. Training audience, during and after the exercise, can access recorded audio and visual unit actions to MSELs, SIGACTs or training events during the exercise. 2. Training audience, during and after the exercise, can access Unit METL for input and comment. 3. Training audience, during and after the exercise, can upload CATS task assessment to Digital Training Management System and / or Army Training Information System TMS/ATIS (when online) 4. Training audience, after the exercise, can access Unit AAR. 5. Must adjust to ATIS reporting compliance.6. Initial classification identification and derivative classification


2. Training Record Update.

(CSE SOW:2.5.22)

2a. TMT provides refined data to ATMC to update training records. 2a1. Commander/staff verifies unit training records are updated.2a2. Unit verifies crew training records are updated.2a3. Unit verifies Soldier training records.

3. Publish and Archive Exercise Data.(CSE SOW: 2.5.15.14.6)

3a. TMT enables units to view and replay previous exercises. 3a1. Discoverable3a2. Searchable3a3. Retrievable3a4. View in TMT

4. Classification Identification and Derivative Classification. (CSE SOW: 2.5.15.14)

4a. TMT identifies appropriate classification for the data. 4a1. TMT uses the Exercise Security Guide to classify data. 4a2. Unclassified4a3. Secret Releasable to MPE




ASS

ESS

Intelligent Tutor

1. Informal AAR(CSE SOW: 2.5.12.5)

1. Provides training audience “during exercise feedback” to identity key significant activities to unit leaders assessment for METL Tasks and / or training objectives.


2. Recommended Retraining. (CSE SOW:2.5.15)

2a. TMT recommends retraining based on unit performance of CATS task.

2a1. Retraining is relevant.2a2. Recommendations have operational significance.2a3. Recommendations are IAW Commander’s Training Objectives.

3. Human Dimension Lessons Learned.

3a. Human dimension characteristics are captured in lessons learned. 3a1. Cognitive3a2. Warfighter3a3. Physical3a4. Social

1DISTRIBUTION A: APPROVED FOR PUBLIC RELEASE // DISTRIBUTION IS UNLIMITED

Distribution A: This is approved for public release distribution is unlimited.

Capability by Echelon

❖ TSS: Squad Tactical Missions❖ TMT: Plan, Prepare, Execution & AAR ❖ OWT: Portions of the Globe, 1 site with hi-res inserts❖ RVCT: Soldier & Combat Platforms

+ Platoon Level Behaviors and Operations+ Company Mission Command Integration+ Scalable simulation engine up to 500,000 entities+ OWT displays Hi-Res Drone Capture, SE Core, Bing, and Vricon Data

+ Company Level Behaviors and Operations+ TMT: Plan, Prepare, Execution & AAR at Company Level+ OWT: Full integration and approval of all Fort Hood, TX Data Sets; + Implementation of battle damage effects on Terrain+ TMT integration with authoritative data

+ Full Globe, 3 sites with hi-res inserts+ Geo-Specific Interiors+ TSS: BN Tactical Missions with a focus on Mission Command+ All Biomes attributed and defined+ Defined external interfaces and APIs

+ TSS: BCT Tactical Missions against SAF/CGF OPFOR+ Cross Domain Solution and Single Sign on CAC auth.+ Brigade Mission Command+ Scalable up to 2 Million Entities and 20 simultaneous exercises+ Cloud Computing and Distribution Architecture

SQD echelon

PLT echelon

Company echelon

BN echelon

X 6

X 30

X 168

OWT, BN FiresFHTX, JBLM, FBGA

BCT Fires

BCT echelon


CDS Phases Flowchart

1

Approved for Public Release; Distribution Unlimited

Understanding Operational Environment (OE) Variables

1. Setting Conditions. The OE operational variables, or PMESII-PT, set the conditions for leader development and training. While these conditions may be represented at varying degrees to meet specific planning or training objectives, some will always have a predominant impact during training, such as the military or physical environment operational variables. With the recently instantiated ‘Objective T’ readiness conditions4, there will be a need for representation and consideration (based on training echelon) of all eight operational variable within a given OE scenario5. OE operational variables do not exist in isolation from one another; the interrelationships of these variables cause the complex and often simultaneous dilemmas that a military force will face on the battlefield. In order to provide both relevant and realistic training, training venues must simulate, or represent their individual and synergistic effects, to the maximum degree feasible, on the OE. This document is aimed at providing a general overview – definitions, considerations and example – of the either operation variables.

PMESII-PT Definitions & Variations:

1. On the following pages, PMESII-PT definitions and variations are provided for each operational variable to not only describe the variable itself, but to also provide various examples and variations for planning and training purposes.

2. Variations provide M&S community leadership a variety of options to represent specific operational variables to varying degrees, in varying numbers, and with numerous variations to account for a multitude of worldwide options.

3. For training, where Live collective venues may not be able to represent all variations simultaneously (which is neither expected nor realistic), Constructive, Virtual, and Gaming models and simulations can pick up the slack to augment Live in order to meet the newer Army Objective-T readiness requirements. For operational planning, with the right M&S tools to stimulate Mission Command Information Systems, PMESII-PT operational variables can and should be integrated to meet doctrinal requirements in ADP/ADRP 3.0.

4. The figure below provides a quick snap shot of operational variable consideration and variations.

2


Political Variable • Attitude toward the United States

• Centers of political power

• Type of government

• Government effectiveness and

legitimacy

• Influential political groups

• International relationships

Military Variable • Military forces

• Government paramilitary forces

• Non-state paramilitary forces

• Unarmed combatants

• Nonmilitary armed combatants

• Military functions Command and control

Maneuver

Information warfare

Reconnaissance, intelligence,

surveillance, and target acquisition

Fire Support

Protection

Logistics

Economic Variable • Economic diversity

• Employment status

• Economic activity

• Illegal economic activity

• Banking and finance

Social Variable

• Demographic mix • Social volatility

• Education level

• Ethnic diversity

• Religious diversity

• Population movement

• Common languages

• Criminal activity

• Human rights

• Centers of social power

• Basic cultural norms and values

Information Variable • Public communications media

• Information warfare • Electronic warfare

• Computer warfare

• Information attack

• Deception

• Physical destruction

• Protection and security measures

• Perception management

• Intelligence

• Information management

Infrastructure Variable • Construction pattern

• Urban zones

• Urbanized building density

• Utilities present

• Utility level

Physical Environment Variable

• Terrain Observation and fields of fire

Avenues of approach

Key terrain

Obstacles

Cover and concealment

Landforms

Vegetation

Terrain complexity

Mobility classification

• Natural hazards • Climate

• Weather Precipitation

High temperature—heat index

Low temperature—wind chill index

Wind

Visibility

Cloud cover

Relative humidity

Time Variable • Knowledge of the AO

• Cultural perception of time

• Key event resolution

• Information offset

• Tactical exploitation of time

• Key dates, time periods, or events

3


The Political Variable:

1. Definition: The Political variable encompasses the Governmental orientation and loyalty of other than Blue Forces (BLUFOR) towards BLUFOR, the administrative bureaucracy, type of governmental type, stability, effectiveness, and status. Describes the distribution of responsibility and power at all levels of governance—formally constituted authorities, as well as informal or covert political powers. (Who are the tribal leaders in the village? Which political leaders have popular support?)

4


2. Sub-categories and variations:

a. Loyalties: (Scenario Considerations) Describes government orientation and attitude towards BLUFOR. Once established, this setting manifests itself in the scenario in the form of Role Player instructions or combat instructions to the OPFOR.

(1) Friendly - Describes an overall favorable, positive reception of BLUFOR activities, presence, and initiatives. Limits infiltration and scripted sabotage against BLUFOR actions. High level of tips (4 to 5 per day) and populace cooperation against OPFOR activities

(2) Neutral/Ambivalent - Describes an undecided reception of BLUFOR activities, presence, and initiatives. Increased infiltration and scripted sabotage against BLUFOR actions. Moderate level of tips (2 to 3 per day) and populace cooperation against Opposing Forces (OPFOR) activities.

(3) Hostile - Describes an unfavorable, negative reaction to BLUFOR activities, presence, and initiatives. Heavy infiltration and scripted sabotage against BLUFOR actions. Low level of tips (1 to 2 per day) and populace cooperation against OPFOR activities.

b. Administrative Divisions: (Scenario and Resource Considerations) Determines the number of bureaucratic divisions within a scenario government. Also determines the type of governmental focus, domestic or international. An example would be federal, state, and local, with a primary focus on local matters.

(1) Tribal - Sub-local focus, limited government or government of limited status. Characterized by civilians on the battlefield (COB) Tribal elders, religious figureheads.

operations.

(2) Local - Town and some district focus in the government day to day

(3) Provincial - District and minimal cross-border focus by the local and

provincial government. Some regional (international) elements and story themes present in the scenario. Government COB adopt a national focus at the expense of Local and Tribal needs.

(4) Regional - International and cross border focus based on the existence of multiple regions or national borders in the scenario OE.

c. Type: (Scenario and Resource Considerations) Determines the type of government structure and associated behaviors encountered by BLUFOR.

(1) Dictatorship/Authoritarian - Characterized by increased government bureaucracy, limited freedoms and decree based rule.

5


(2) Theocracy - Defined as the religious control of the state and all state functions. Government personnel are either religious figures themselves or defer their decisions to religious figure influencers (mullahs or equivalent)

(3) Representative Government - Characterized as a representative form of government --either democratic, republic or parliamentary in form--with elected representatives and executives. All the government politics are governed by will of people and government has limited, defined powers.

(4) Anarchy - No functioning government, necessitates a "tribal" and religious leader lead towns

d. Stability: (Scenario Considerations) Defines the initial level of government cohesion and strife within an OE government. Helps establish the levels of Status and Effectiveness and sets the conditions for Infrastructure Services Level and sets the overall Social Strife level in the OE.

(1) Stable - Defined as not more than two major political parties with minimal dissent and issues of contention (not more than two clearly defined issues). Presented and manifested in OE through scripting and role player sub -instructions.

(2) Divisive - Establishes conditions for Moderate Social strife. Requires the establishment of up to three different political groups with at least three competing interests to be written into the scenario sub-events, back-stories, and Role player sub- instructions.

(3) Corrupt - Establishes conditions for Moderate or potentially high Social strife. Requires the establishment of up to three different political groups with at least three competing interests to be written into the scenario sub-events, back-stories, and Role players instructions.

e. Effectiveness: (Scenario and Resource Considerations) Describes the level of services and infrastructure repair. Also determines the amount of criminal tolerance and general law & order in a society.

(1) Competent - Defined as 60-75% of all government services provided throughout the scenario OE, 60-75% of all infrastructure present and functioning. Limited civil unrest.

(2) Semi-competent - Defined as 40-60% of all government services provided throughout the scenario OE, 60-75% of all infrastructure present and functioning.

(3) Incompetent - Defined as 20-40% of all government services provided throughout the scenario OE, 60-75% of all infrastructure present and functioning.

f. Status: (Scenario and Resource Considerations)

(1) Functioning - Full complement of all specified COB government positions required in the provincial, district and town elements.

6


(2) Semi-Functioning - The government is only partially manned and capable of administering its area.

(3) Non-Functioning - The government is partially manned and minimally capable of administering its area.

7


The Military Variable:

1. Definition: The Military variable encompasses the aspects of the type, capability, and equipment of the OPFOR as well as any niche weaponry and unique tactics. Explores the military and/or paramilitary capabilities of all relevant actors (enemy, friendly, and neutral) in a given OE. (What is the force structure of the enemy?) For the latest in representing specific or hybrid OPFORs, refer to the TC 7-100 series.


a. Type (Scenario Consideration): Specifies the types of unit organizations present within a scenario. Determined by referencing FM 100.4.

(1) Regional - Conventional standing military units.

8


(2) Transitional - Border Patrol, Constabulary, and paramilitary forces present. Some Guerrilla forces present.

(3) Adaptive - Paramilitary, Insurgent, Guerrilla, and armed criminal elements present in the OE. Limited conventional unit organizations and tactics present.

b. Tactics (Scenario Considerations): Specifies the primary methods of tactics, techniques and procedures used by OPFOR within the scenario OE. Specific tactics used are found in FM7-100.3.

(1) Regional (conventional) - Conventional OPFOR Operational concepts and tactics present in the OE. Limited SOF play or adaptive operations present.

(2) Transitional (mixed) - Mixed (Conventional and paramilitary) OPFOR Operational concepts and tactics present in the OE. Limited SOF play or adaptive operations present.

(3) Adaptive (asymmetric) - Primarily paramilitary and adaptive OPFOR Operational concepts and tactics present in the OE. High levels of SOF play or paramilitary, adaptive operations present.

c. Capability (Scenario Development): Describes the overall effectiveness of OPFOR units and formations in conducting successful coherent operations. Determines the level of tactical nuance and strategic depth used in OPFOR play against BLUFOR units and tactics.

(1) Low - Capable of no "wildcard” techniques, tactics and procedures (TTPs) or adaptive operations or tactics used in response to specific BLUFOR vulnerabilities.

(2) Moderate - Capable 1 or 2 "wildcard” TTPs or adaptive operations or tactics used in response to specific BLUFOR vulnerabilities.

(3) High - Capable 3 to 4 "wildcard” TTPs or adaptive operations or tactics used in response to specific BLUFOR vulnerabilities.

d. Niche Weaponry (Scenario and Resource Consideration): Defines the ability of scenario OPFOR to possess and employ Niche weaponry or capabilities the negate BLUFOR capabilities.

(1) Present - OPFOR able to employ TIER I equipment and commensurate technique as specified in the Weapons Equipment Guide (WEG).

(2) Not Present - OPFOR limited to TIER II -TIER IV levels of equipment as specified in the WEG.

e. Equipment Level (Scenario and Resource Considerations): Technical level of equipment used against BLUFOR in scenarios as specified by the WEG Tier tables (see also paragraph 4-1-2)..

(1) TIER I - Weapons systems across the different functional areas that a major military force with state-of-the-art technology would generally have, causing the

9


OPFOR to achieve technical equality or overmatch against similar BLUFOR weapon systems.

(2) TIER II - Modern competitive weapons systems fielded in significant numbers for the last 10 to 20 years, with limitations or vulnerabilities being diminished by available upgrades.

(3) TIER III - Equipment systems dating back 30 to 40 years. They have limitations in all three subsystems categories: mobility, survivability, and lethality. However, they can still challenge vulnerabilities of U.S. forces.

(4) TIER IV - Weapon system which are 40 to 50 years old, some of which have been upgraded numerous times. These represent equipment typically found in forces of Third World or smaller developed countries. Use of effective strategy, adaptive tactics, niche technologies, and terrain limitations could enable a Tier 4 OPFOR to challenge the effectiveness of a U.S. force in achieving its goals. This tier includes militia, guerrillas, special police, and other forces. This category also includes the panoply of improvised weapons or equipment.

10


The Economic Variable:

1. Definition: The Economic variable encompasses the type and function of the economic base, status, and structure to include the banking and criminal aspects. Encompasses individual and group behaviors related to producing, distributing, and consuming resources. (What is the unemployment rate?)


a. Economic Industries (Scenario and Resource Considerations): Presents a listing of the most probable industrial bases present in a scenario OE. Each industry theme represents and represents the entire line or theme from the standpoint of actors and props required to represent the initial inputs, refinement, distribution, and, ultimately, their retail sale of the goods created.

11


(1) Mining/Mineral Fuels - Mining: a series of props and activities used to represent a mining or petroleum operation. Scenario writers must create COB transactions to represent the production and movement of goods, intra-province, inter-district, and inter-town.

(2) Manufacturing - A series of props, Role player instructions and pre- scripted activities that represent a complete manufacturing, distribution, wholesale, and retail series of actions to approximate a product life cycle in the OE. Scenario writers must create COB transactions to represent the production and movement of goods, intra- province, inter-district, and inter-town.

(3) Agriculture - A series of props, Role player instructions and pre-scripted activities that represent a complete agricultural infrastructure to include, planting, crop cultivation, distribution, wholesale, and retail actions to approximate an agricultural or product life. Scenario writers must create COB transactions to represent the production and movement of goods, intra-province, inter-district, and inter-town.

b. Economic Base of the OE (Scenario Considerations): Describes the representation of up to three different, complete economic themes per town to describe the scenario economy: mining, manufacturing, or agricultural industries, or livestock ranching/herding.

(1) Multiple economic themes present, single or none predominant - Describes conditions where multiple industries are present in an economy. Any single industry selected as predominant will cause scenario writers to ensure the preponderance of storylines, themes, & COB roles are focused on that industry & all of its associated parts.

(2) Single industry theme present - Describes the condition of a single economically significant industry. The industry theme selected acts as the focal point for all economic storylines, themes, and COB roles focused on that industry and its sustainment.

c. Economic Structure (Scenario and Resource Considerations): Helps describe the type of economic activity present. Manifests itself in the form of specific activities, number of role players required to represent the behavior and scenario design instructions in the form of Role descriptions for different activities.

(1) Command - A centrally controlled and regulated economy lacking many products and service; Black Market operations and smuggling is wide spread (represented by three or more types of illicit goods being traded--one or more necessary to cob population well being).

(2) Socialist - Denotes a partially controlled economy with some black market trade in controlled items. Will require half COB special mission element to represent limited black-market and some organized crime.

(3) Free Market - Limited black-market, robbery, or organized crime activities. Types of crime represented: petty theft and limited drug or single item smuggling, distribution and sales.

12


d. Criminal and Economic Mix (Scenario and Resource Considerations): Describes the predominant type of criminal activities present in the OE, from High (3 types of activities) to Low (1 activity). Each activity represented requires ¼ COB special mission element to represent the activity, in addition to scenario storyline.

(1) Smuggling - Defined as the acquisition, distribution, and sale of a controlled, restricted or forbidden item. Requires the representation of all aspects of the distribution chain, from suppliers to mules, to retail customers.

(2) Theft/Looting - small theft rings to represent the acquisition and distribution of stolen property.

(3) Gang/Organized Crime type Activities - defined as role player instructions and storylines to represent criminal activities such as bribery, coercion, thuggery, protection rackets, and inter gang rivalry

(4) Mixed/Multiple Activities Present - Multiple, above mentioned activities present in the OE. Represented by multiple minor or major sub events occurring during the scenario play.

e. Banking and Finance (Scenario and Resource Consideration): All minor implements and props that more effectively represent the economic environment.

(1) Primitive - Hawala, private money lender type arrangement. Requires at least one COB money lender, with currency per town (7 total).

(2) Developing - Mixture of private moneylenders and Banking infrastructure (Bank building with props).

(3) Advanced - Banking infrastructure (one bank with employees per town). Private money-lending restricted to criminal/gang activity.

f. Status (Scenario Considerations) - Represents the employment status and level of disenfranchisement of the COB populace. Manifests itself in specific role assignments and COB sub instructions for role players’ instructions.

(1) Failing - 2/3 COB unemployment, high criminal tolerance

(2) Emerging - 1/2 COB unemployment with 1/2 disenfranchised.

(3) Thriving - Majority of COB employed with 1/4 disenfranchised.

13


The Social Variable:

1. Definition: The Social variable encompasses various aspects of the demographic mix as social/religious groups to include volatility, transience, literacy, and criminal tolerance. Describes the cultural, religious, and ethnic makeup within an OE and the beliefs, values, customs, and behaviors of society members. (What is the ethnic composition of the OE? What are the behaviors of society members? (Who are the influential people in the village—for example, religious leaders, tribal leaders, warlords, criminal bosses, or prominent families?)

14



a. Demographic Mix or Scenario Diversity (Scenario Considerations): Describes the number of gender and age balance of a COB population.

(1) Balanced - A scenario environment consisting of equal proportions of gender and military age population.

(2) Unbalanced (gender) - A scenario environment consisting of unequal proportion of gender (male, female) in proportion to the overall group. The military age proportion of the population is not affected and remains the same as if it were in a balanced setting.

(3) Unbalanced (age) - A scenario environment consisting of a greater proportion of the military age demographic (male, female) in proportion to the overall COB population. The gender proportion of the population is not affected and remains the same as if it were in a balanced setting.

b. Social Volatility (Scenario Considerations) - Describes the amount of inter-group or religious conflict present in a society and the amount of civil unrest present. Determined by Ethnicity, Religious Diversity, (political) effectiveness, refugee prevalence, and political type and status.

(1) Low Volatility - 1-2 preplanned or spontaneous riots or civil disorders based on religious or ethnic strife present within the scenario.

(2) Moderate Volatility - 3-4 preplanned or spontaneous riots or civil disorders based on religious or ethnic strife present within the scenario.

(3) High Volatility - 5-6 preplanned or spontaneous riots or civil disorders based on religious or ethnic strife present within the scenario.

c. Literacy (Scenario Considerations): Describes the education level, media and technical sophistication of the COB population. Helps determine the scripting requirements and may introduce specific scenario sub-themes into a scenario setting.

(1) Limited - 1/4 COB population literate or educated. Limited education infrastructure and jobs (no more than 5%).

(2) Moderate - 1/2 COB population literate or educated. Moderate amount of education infrastructure and jobs (no more than 10%).

(3) High - 3/4 COB population literate or educated. High amount of education infrastructure and jobs (no more than 15%).

d. Ethnicity (Scenario and Resource Considerations): Describes the number and specifies the interaction of various ethnic groups within a scenario population

(1) Single Group – single Group; non Competitive.

15


(2) Multiple Group, Competitive, Single Predominant - Up to three distinct groups distributed within the COB population with one group as the dominant population.

(3) Multiple Group, Competitive, None Predominant - Up to three distinct groups distributed within the COB population with no group designated as the dominant population.

e. Religious Diversity (Scenario and Resource Consideration): Describes the number and specifies the interaction of various religious groups within a scenario population

(1) Single Group – single Group; non Competitive.

(2) Multiple Group, Competitive, Single Predominant - Up to three distinct groups distributed within the COB population with one group as the dominant population.

(3) Multiple Group, Competitive, None Predominant - Up to three distinct groups distributed within the COB population with no group designated as the dominant population.

f. Societal Transients (Scenario and Resource Considerations): Describes the initial prevalence of refugee or displaced migrant populations within the scenario OE. Once set, the designation does not preclude the possibility of migrant populations as a result of BLUFOR action or inaction.

(1) Settled/Stable - Population is settled, organized, and does not move or displace except when confronted with occasions of extreme duress.

(2) Mixed Populations - Population movement is based on BLUFOR activities or pre-scripted as a scenario sub-event in response to BLUFOR training needs.

(3) Migrant/Displaced - Population frequently moves and displaces as a part of the normal state of affairs. Populace is nomadic and stateless.

g. Criminal Tolerance (Scenario Considerations): Defines the level of criminal activity tolerated by the social groups' mores and norms. It determines the amount and level of criminal economic mix and intensity of activity.

(1) Not Tolerated - Limited criminal activity. 1-2 activities present from the Criminal economic Mix. It is limited to up to 30% of the total urban landscape (1-2 towns).

(2) Ambivalent - Moderate criminal activity present. 1-3 activities present from the Criminal economic Mix. It is limited to 50% of the total urban landscape (3-4 towns). Presence of at least one criminal gang distributed throughout the scenario environment.

(3) High criminal activity present. 3-4 activities present from the Criminal economic Mix, two or more rival criminal gangs or organizations present and active in the scenario (manifested by competition, gang or mob warfare). It is limited to presence in 75% of the total urban landscape (5-6 towns).

16


The Information Variable:

1. Definition: The Information variable encompasses the various potential mediums and conditions of passing or influence information flow, as well as sophistication levels of equipment and use. Describes the nature, scope, characteristics, and effects of individuals, organizations, and systems that collect, process, disseminate, or act on information. (How much access does the local population have to news media or the Internet?)


a. Information Condition (Scenario and Resource Considerations): Describes the complexity of the information environment present in a scenario. Sets the conditions for the types, capabilities, and activities of the information mediums present in the scenario.

(1) Minimally integrated - Single additional information source present and represented within the Scenario OE (typically the newspaper or possibly radio mediums) in addition to the Word of Mouth (WOM), Gossip network.

(2) Moderately Integrated - Two to three information sources present in the OE in addition to WOM, Gossip Network. Typically represented by the inclusion of newspaper and one other medium.

(3) Highly Integrated - Maximum saturation of multiple information sources. Requires three or more information sources present in addition to WOM, Gossip network.

b. Potential Mediums (Scenario and Resource considerations): Describes the type of information or media sources that may be present in a scenario the material requirements that enables their representation.

17


(1) Internet - Interruptible, 4-5 building intranet access per town, capable of representing an 'internet' capable of hosting at least six dynamic pages or sites consisting of the following site types: two web-logs, two internet chat rooms, and two news websites.

(2) Television - A single channel, cable broadcast capability with a connected studio production site (located in play box), associated personnel, and sufficient programming to broadcast 10 hours per day.

(3) An AM or FM radio broadcast station, with associated personnel, and the ability to broadcast programming for 10 hours per day for the duration of an exercise. Broadcast and studio facilities would ideally be located in the training area to enhance training realism.

(4) Newspaper - Media personnel (role players) and associated equipment required to create and locally produce a single page newspaper or flyer. Minimum of one production element present per two towns.

c. Sophistication (Scenario and Resource Considerations): Describes the scenario population's ability to manufacture, create, utilize, or adapt to new ideas and technology. Drives the ability of a society to incorporate or posses a niche or high technology concept or item within the scenario. Also determines level of OPFOR niche technology present and overall level of equipment (Tier 1-Tier 4) present in the OE.

(1) Low - Capable of manifesting and using Tier 2 through Tier 4 level of equipment. Possesses one element of Tier I technology. COB players capable of grasping higher level concepts, though not afraid of adopting them.

(2) Developing - Capable of manifesting and using Tier 2 level of equipment and up to two types of Tier I (niche) technology. COB players capable of grasping higher level concepts and generally receptive to new ideas and innovations.

(3) High - Capable of manifesting and using Tier 1 level of equipment and at least two types of Tier I (niche) technology. COB players capable of grasping higher level concepts and are very receptive to new ideas and innovations.

18


The Infrastructure Variable:

1. Definition: The Infrastructure variable encompasses the urban layout and building types and density, as well as available services and overarching information and transportation architectures. Is composed of the basic facilities, services, and installations needed for the functioning of a community or society. (What are the key modes of transportation?)

19



a. Urban/Town Layout (Resource Considerations): The physical layout of a village, town, or city generally represents a historical composite of the area's urban development as specified by FM 3-06/FM 3-06.11.

(1) Dense/Random - Dense, random construction are buildings located close together along the edges of narrow winding streets.

(2) Closed Orderly Block - Urban areas consisting of residential and commercial type buildings. Buildings often form continuous fronts for as much as a city block, and each block normally contains an inner court. Streets in this area normally average meters in width and are normal.

(3) Dispersed - Dispersed areas consist of row-houses or single dwellings with yards, trees, gardens, and fences. The street pattern is normally rectangular or gently curving. Street widths average 14 meters. However, buildings are normally set back 6-8 meters from the road.

(4) High Rise - Urban area consisting of multistoried buildings, separated by large open areas such as parking lots, recreation areas, parks, and individual one-story buildings. Rarely are there unbroken rows of houses facing the street in this type area.

b. Urbanization (building density) (Resource Consideration) - Describes the average building density within each town of the seven town OE representation model, as implied the COB WG whitepaper.

(1) Low – Up to 30 structures with at 15 permanent buildings or less per town (remaining can be mobile structures) with no two story structures. Single economic industry structures present in each town.

(2) Medium - 30 to 45 structures per town with at least 23 permanent building of which three are multi-story structures, one government center (5 building cluster) and one site of significance (3 building cluster). Two Economic industry structures present per town.

(3) High – 46 or more structures per town with at least 10 Multi-story structures clustered together or separated by a one story building or open area, one government center (12 building cluster), and one site of significance (a 6 building cluster) per district.

c. Utilities (Scenario and Resource Requirements): Describes the range of public and private services present within a typical scenario OE. Defines the material and scenario scripting requirements associated with each represented service.

(1) Power (Electricity) - Power generation and distribution equipment, capable of providing selectively interruptible power to 75% of all structures present in the OE. Conceptually this network would be similar in design to a series of trailer park power

20


points, centrally powered, with an interruptible node at each built up area. The power network can be controlled and one or more nodes can be shut down to give the appearance of a variety of conditions.

(2) Water - Water piping, distribution equipment, or plumbing to provide each built-up area with an interruptible water supply. Similar in design to the power network, the water network can be centrally or locally controlled to provide the appearance of a developed to non-existent water supply within the OE.

(3) Sewage - At least one large sewer or drainage pipe infrastructure of at least 200m length, either buried or above ground, following along the a town main or secondary roads to give the appearance of a simple infrastructure. The pipe infrastructure should branch at least once with an extension of at least 50m. At least one town substitutes this branching drainpipe for a shallow trench, 200m in length running along the town's main road.

(4) Services and Transportations - Up to two complete public services elements and their respective vehicle requirements (per COB whitepaper), up to 150 additional COB-Vs, and at least one represented gas/service station (1-2 structure POL distribution point) per district or every two towns.

d. Services Level (Scenario and Resource Considerations): Describes the approximate percentage of services available to each town. Each utility present in the scenario has its own respective service level, which determines the material and scenario writing requirements for the scenario.

(1) Non-Existent - 25% of all distribution nodes or required infrastructure and COB elements/material are present or operational, with physical distribution and services present to at least 1/4rd of the structures in each “switched on” area.

(2) Degraded - 50% of all distribution nodes or required infrastructure and COB elements/material are present or operational, with physical distribution and services present to at least 1/3rd of the structures in each “switched on” area.

(3) Developed - 75% of all distribution nodes or required infrastructure and COB elements/material are present or operational, with physical distribution and services present to at least half of the structures in each “switched on” area.

e. Transportation Architecture (Scenario and Resource Considerations): Details the existing road and transportation network present in an OE. Describes the type of roads present and the coverage of the road network to any built up areas. Includes airports, ports, rail, and surface road networks.

(1) Simple - Single track or improved two lane hardball road networks, extending to all built up areas. Single line railway, no functioning airports, limited river transportation networks.

21


(2) Moderate - Improved multi- lane hardball road networks, extending to all built up areas with secondary, two lane hardball roads paralleling primary roads. Two to three 2 line railways, connecting at least 50% of the OE infrastructure. One functioning airport and, if present moderate river transportation networks.

(3) Complex - Multi- lane hardball highway networks, extending to all built up areas with secondary, multi-lane hardball roads paralleling primary roads. Three to four 2 line railways, connecting at least 75% of the OE infrastructure. Two to three large sized, functioning airports (jet capable) and, if present extensive river transportation networks.

f. Information Architecture (Scenario and Resource Considerations): Data, telephone landline, and wireless (cellular) communications access for the OE. Defined as an interruptible infrastructure with the capacity to service 4-5 buildings per built-up area. Cellular coverage is defined as Cellular phone service, selectively interruptible, providing enough coverage to service 75% of the scenario play box.

(1) Non-Existent - 25% of all distribution nodes or required infrastructure and COB elements/material are present or operational, with coverage extending to at least 1/4 of the scenario play box.

(2) Degraded - 50% of all distribution nodes or required infrastructure and COB elements/material are present or operational, with coverage extending to at least 1/3rd of the scenario play box.

(3) Developed/Emerging - 75% of all distribution nodes or required infrastructure and COB elements/material are present or operational, with coverage extending to at least 3/4 of the scenario play box.

22


The Physical Environment Variable:

1. Definition: The Physical Environment (training environments) variable encompasses various landforms, drainage considerations, natural hazards, and vegetation; it also includes the climatic conditions. Includes the geography and man-made structures as well as the climate and weather in the area of operations. (What types of terrain or weather conditions in this AO favor enemy operations?)


a. Landforms (Scenario Considerations): Types of terrain predominating the OE (describes more than 60% of the terrain present in the OE). Limitations inherent with specific types of terrain are enforced by Observe/Controller rules (Live), or computer

23


enforced simulation rules. (Definitions derived from http://encyclopedia.thefreedictionary.com/Landform)

(1) Sloped - Sloping landforms consisting of, but not limited to the following types: cliffs, dells, escarpments, glens, gullies, hills, mountains, plains & plateaus, ridges, valleys, and watersheds.

(2) Coastal - Coastal landforms consisting of, but not limited to the following types: bays, beaches, cuspate forelands, capes, coves, delta, fjords, slagoons, sounds, spits or tombolos.

(3) Fluvial - Riverine or water type landforms consisting of, but not limited to the following types: -arroyos, basins, bars, bayous, lakes, levees, marshes, rivers & streams, swamps, waterfalls, watersheds or combinations of those mentioned.

(4) Erosion - Erosion type landforms consisting of, but not limited to the following types: canyons, caves, and desposition or eolian landforms.

(5) Mountain/Glacial - Mountain landforms consisting of, but not limited to the following types: mountain ranges, crevasses, U-shaped valleys, glaciers, hanging valleys, kane deltas, outwash fans, and other types of valley formations.

(6) Mixed Landforms - One or more of the above categories of landforms comprising over 80% of the available terrain in an OE.

b. Drainage (Scenario Considerations): Describes the primary type of surface water drainage pattern present in the OE. Used primarily in designing virtual and constructive scenarios and determines streams, river flows, and flooding patterns present in an OE.

(1) Dendritic - A tree-like pattern composed of branching tributaries to a main stream, characteristic of essentially flat lying and homogeneous rocks. This drainage type is typical of glacial tilt, tidal marshes, and localized areas in sandy coastal plains.

(2) Trellis - Drainage pattern where the mainstream runs parallel, and small streams flow and join at right angles. This pattern is found in areas where sedimentary or metamorphic rocks have been folded.

(3) Radial - A drainage pattern where streams flow outward from a high central area. The pattern is found on domes, volcanic cones, and round hills.

(4) Annular - The annular pattern is a modified form of the radial drainage system, found where sedimentary rocks are upturned by a dome structure. In this pattern, streams circle around a high central area. The granitic dome drainage channels may follow a circular path around the base of the dome when it is surrounded by tilted beds.

(5) Parallel - In the parallel pattern, major streams flow side by side in the direction of the regional slope. Parallel streams are indicative of gently dipping beds or uniformly sloping topography. The greater the slope, the more nearly parallel the drainage and the straighter the flow. Local areas of lava flows often have parallel drainage, even

http://encyclopedia.thefreedictionary.com/Landform)

24


though the regional pattern may be radial. Coastal plains, because of their slope toward the sea, develop parallel drainage overboard regions.

(6) Rectangular - A specific type of angular drainage and is usually a minor pattern associated with a major type such as dendritic. Characterized by abrupt bends in streams and develops where a tree-like drainage pattern prevails over a broad region. Its drainage pattern is extremely angular and has easily recognizable short gullies that are locally parallel.

c. Vegetation (Scenario Consideration) - Describes the predominant vegetation found in an OE. Primarily a virtual or constructive setting. Can be represented live in select instances by applying OC enforced rules to govern behavior in the type of area specified.

(1) Desert/Scrub - A variety of trees that have had their growth stunted soil or climatic conditions. Shrubs comprise the undergrowth in open forests, but in arid and semiarid areas they are the dominant vegetation. Shrubs normally offer no serious obstacle to movement and provide good concealment from ground observation however, they may restrict fields of fire.

(2) Grassland - Grasslands from .5 to 2m in height. Grassland more than 1 meter high is considered tall. Very tall grass may provide concealment for foot troops. Foot movement in savannah grasslands is slow and tiring; vehicular movement is easy; and observation from the air is easy. Improved solid traffic-ability during seasonal wet periods.

(3) Woodlands - Broadleaf , deciduous, or coniferous forests capable of slowing dismounted troops and military vehicles, canalizing movement and causing limited observation and fields of fire. The type of woodland is determined by the dominant tree type (>60% of either deciduous or coniferous types). Forests containing >60% mix of either type are considered mixed.

(4) Mixed (two or more types) - Multiple types of vegetation, creating the preponderance of the OE vegetation present.

d. Climate (Scenario Considerations): Specific environmental climatic zones sharing similar climatic attributes such as temperature, length of the solar day (sunlight), and in particular latitudinal distance from the equator. In represented environments, climate is primarily classified on the basis of temperature and precipitation. Climatic descriptions are used in scenarios to vary climatic conditions to better train BLUFOR units, exposing them to the variety of climatic conditions and their effects on operations. This variable is primarily used in a virtual and constructive environment. Some climatic conditions can be represented in a live setting using scenario based rules and play box restrictions on player and OPFOR movement and actions. Variable conditions are defined in http://encyclopedia.thefreedictionary.com/Climate.

http://encyclopedia.thefreedictionary.com/Climate

25


(1) Tropical - A type of climate characterized by 12 months of mean temperatures above 18 degrees Celsius (64.4F) and almost continuous rainfall throughout the year, usually convectional occurring predominantly in the afternoon.

(2) Arid - Climate encountered in regions too dry to support a forest, but not dry enough to be a desert. The soil is considered too moist to be a desert, but too dry to support normal forest life. Characterized by hot summers and cold winters, with 10-20 inches of rain or snowfall per year.

(3) Mediterranean - A climate that resembles those of the lands bordering the Mediterranean Sea. These climates generally occur on the western coasts of continental landmasses, roughly between the latitudes of 30° and 45° north and south of the equator. Areas with this climate receive almost all of their yearly rainfall during the winter season, and may go anywhere from 2-5 months during the summer without having any significant precipitation.

(4) Oceanic - Oceanic climates are characterized by a narrower annual range of temperatures than are encountered in other places at a comparable latitude, and differ from Mediterranean climates in that significant amounts of precipitation are received in summer.

(5) Continental - Characterized by winter temperatures cold enough to support a fixed period of stable snow cover each year, and relatively low precipitation occurring mostly in summer, although east coast areas (chiefly in North America) may show an even distribution of precipitation. They have either forest or tall-grass prairie as natural ground cover and include some of the most productive farmlands in the world. All such climates have at least three months of temperatures in excess of 10°C (50°F) and winters with at least one month below 0°C (32°F).

(6) Sub-Artic - Regions having a sub-arctic climate (also called boreal climate) are characterized by long, usually very cold winters, and brief, warm summers. It is found on large landmasses, away from the moderating effects of an ocean, generally at latitudes from 50° to 70°N. Due to the absence of any large landmasses at such latitudes, it is not found in the Southern Hemisphere.

e. Natural Hazards (Scenario Considerations): Describes the type of natural disasters or hazards that BLUFOR may be required to contend with when conducting humanitarian relief, civil order, or stability and support operations. Can be represented in live virtual or constructive settings by the adoption of chemical, nuclear attack conditions (virtual or constructive), or the use of OC enforced rules to govern transit and survivability of such events in a live setting.

(1) Volcanic Eruption - Self-explanatory. Characterized by moderate to fast lava flows and possible explosive eruptions of rock and hot ash (similar to the Mt St Helens eruptions and after effects).

26


(2) Earthquakes - Large magnitude, long duration, surface quakes resulting in severe infrastructure damage and urban destruction.

(3) Flooding - Large area flooding of 2 to 3 meters of depth, disrupting all transportation, destroying infrastructure, and subsiding after a prolonged period. Often accompanied by local contagions and waterborne diseases, which are best represented by chemical or biological weapon effects.

(4) Avalanche - Self explanatory. Large scale effect occurring primarily in a mountain or terraced valley.

(5) Other (disease) - Any natural, biological, short term, short duration, large area affect, propagated by either weather or prevailing terrain conditions present in an OE.

(6) Non - Self explanatory.

27


The Time Variable:

1. Definition: The time variable encompasses timeline and scenario setting conditions to provide for exercise event resolution. Describes the timing and duration of activities, events, or conditions within an OE, as well as how the timing and duration are perceived by various actors in the OE. (What is the cultural perception of time in this OE?)


a. Setting (Scenario Consideration): Defines the amount of pre-knowledge that the BLUFOR unit would rightfully possess based on the amount of time the unit has spent in the OE prior to scenario STARTEX. The setting determines the amount of information offset that BLUFOR is entitled to prioritize.

(1) Entry - BLUFOR is initially beginning its tour of duty. The unit is not established and has limited knowledge of the OE.

28


(2) Occupying - BLUFOR is mid-way through its tour of duty. The unit is established and has moderate knowledge of the OE.

(3) Exit - BLUFOR is nearing the end of its tour of duty in the OE. The unit is established and has detailed knowledge of the environment.

b. Scenario Timeline - The number of major sub-events scripted into the scenario OE used to drive BLUFOR training objectives.

(1) Compressed - 10-12 major OE sub-events planned with sufficient planning conducted to diagram and execute effects in response to probable BLUFOR actions. Setting used only for a highly experienced, capable unit.

(2) Normal - 4-5 major OE sub-events planned with sufficient planning conducted to diagram and executes effects in response to probable BLUFOR actions. Setting used for a well trained, moderately experienced unit.

(3) Expanded - 1-3 major OE sub-events planned with sufficient planning conducted to diagram and execute effects in response to probable BLUFOR actions. Setting used for moderately trained, relatively experienced unit to emphasize specific training objectives.

c. Sub-Event Resolution (Scenario Consideration): Defines the planning depth of each major sub-event planned in a scenario. The setting may describe the entire scenario, encompassing all sub-events or may describe specific sub-events within the scenario.

(1) Shallow - Sub-effects depth limited to 2nd order effects.

(2) Moderate - Sub-event effects depth limited to 3rd order effects.

(3) Detailed - Sub-event effects depth expanded to capture 2nd, 3rd, and 4th order effects in response to BLUFOR actions and counter actions.

d. Information Offset (Scenario Consideration): Tips, informants, and serendipitous events or reports that presage OPFOR activities in a meaningful, predictive way. This information is either provided to BLUFOR prior to STARTEX for planning purposes or is scripted into the scenario.

(1) Low - 10% of all OPFOR activities or major sub events are presaged by sufficient tips, hints or indicators to enable successful BLUFOR reaction or interdiction to the events.

(2) Medium - 20% of all OPFOR activities or major sub events are presaged by sufficient tips, hints or indicators to enable successful BLUFOR reaction or interdiction to the events.

(3) High - 30% of all OPFOR activities or major sub events are presaged by sufficient tips, hints or indicators to enable successful BLUFOR reaction or interdiction to the events.