JTC_TRS-DT_P-Spec_1.2_-_11_June_19.pdf

PERFORMANCE SPECIFICATION

JOINT TERMINAL CONTROL TRAINING AND REHEARSAL SYSTEM

DESKTOP TRAINER/U

This specification is approved for use by all Departments and Agencies of the Department of

Defense.

Version 1.2 11 June 2019

Prepared by

AFLCMC/WNS

2300 D Street

Wright Patterson, OH 45433

DISTRIBUTION STATEMENT D.

Distribution authorized to the Department of Defense and U.S. DoD contractors only (Critical Technology) (12 December 2017). Other requests shall be referred to AFLCMC/WNS.

FA8621-20-R-0003

JTC TRS DT Performance Specification

CHANGES & REVISIONS

Document History BASIS ECP / NOR DATE REVISION Paragraph

Initial (1.0) n/a n/a n/a

Ver 1.1

9 Apr 18

1.1 Deleted paragraphs 3.4.2.2,

3.5.2.3 and 3.5.2.4 as they are not applicable to the Legacy Sys.

Ver 1.2

11 June 19

1.2 1. Modified the title from Legacy System Compatibility to

JTC TRS DT

2. Updated 1. Scope to reflect JTC TRS DT and the Legacy ECP award

3. Updated 2.1 Government Document references, subtasks, and their table references

4. Added mandatory models to Appendix E (5 rockets, 2 jammers)

5. Added DACAS requirements to section 3.3.2.14

6. Updated Appendix C to include the HHL-16/PRC-161 radio

Table of Contents

1 SCOPE

1.1 Scope

1.2 System Overview

2 APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 Non-Government Documents

2.3 Order of Precedence

3 REQUIREMENTS

3.1 Specific Performance Requirements

3.2 General Requirements

3.3 Mission Requirements

3.4 Simulated Battlefield Environment Requirements

3.5 Trainee Interactive Requirements

3.6 Voice Communication Requirements

3.7 Instructor/Operator Station (IOS) Requirements

3.8 Human-In-The-Loop (HITL) Requirements

3.9 Integrated Simulations System Requirements

3.10 Design and Construction

3.10.2 Software

3.11 Unclassified/Classified Operations

3.12 Human System Integration (HSI)

3.13 Safety and Health Hazards

4 VERIFICATION AND VALIDATION

4.1 Verification Methods

5 PACKAGING

6 RESERVED FOR FUTURE USE – BLANK

APPENDIX A – ACRONYMS

APPENDIX B – DEFINITIONS

APPENDIX C – EQUIPMENT REQUIREMENTS

APPENDIX C1 – EQUIPMENT

APPENDIX D – RADIO FREQUENCIES

APPENDIX E – MODELS/ENTITIES

APPENDIX F – ORDNANCE/ENTITIES

APPENDIX G – VISUAL REQUIREMENTS

G VISUAL REQUIREMENTS

G.1 Image Generator (IG) Subsystem G.1.1 IG to Host Interface G.1.2 Special Effects G.1.3 Environmental Effects G.1.4 Time of Day G.1.5 Image Quality G.1.6 IG Maintenance G.1.7 Image Perspective & Geometry Accuracy G.1.8 Relocatable Vantage Points G.1.9 Update Rate G.1.10 N/A G.1.11 Transport Delay G.1.12 Range of Vision G.1.13 Scene Load Management & Overload Management G.1.14 Scene Resolution G.1.15 Colors G.1.16 Illumination & Shading G.1.17 Occulting G.1.18 Channel Pixel Fill Rate G.1.19 Polygon Capacity G.1.20 Light Points G.1.21 Anti-Aliasing G.1.22 Stealthview G.1.23 Texture

G.1.24 Mapping G.1.25 Magnified Views (Binoculars and Scopes) G.1.26 Sensor Scenes G.1.27 N/A G.1.28 Reticles and Symbology G.2 Models G.2.1 Simultaneous Model Management G.2.2 Model States G.2.3 Model Controls G.2.4 Model Placement Accuracy G.2.5 Dismounted Personnel (DP) Models G.2.6 Trees and Woods G.3 Visual Database G.3.1 Terrain Features Generation System Requirements G.4 Visual Display Subsystem G.4.1 Display System Requirements

1 SCOPE

1.1 Scope

This specification covers the the Joint Terminal Control Training and Rehearsal System Desktop Trainer (JTC TRS DT). This document establishes the Government’s requirements for system performance.

1.2 System Overview

JTC TRS DT is a mission simulation system that has applicability for training personnel in all services (Army, Navy, Marines, and Air Force). The JTC TRS DT system software is designed to provide realistic Terminal Attack Control (TAC), Close Air Support (CAS), and Call for Fire (CFF) coordination, training, and mission rehearsal. JTC TRS DT provides a robust, interactive multimedia, Distributed Interactive Simulation (DIS) compliant system.

The system provides constructive entity control, representative flight mission profiles, representative ordnance and effects, and supports or includes emulated or simulated military equipment. The JTC TRS DT supplements JTC TRS and field training to provide realistic introductory training, upgrade training, proficiency training, continuation training and mission rehearsal in a synthetic battlespace. The JTC TRS DT can support multiple modes of operation from an individual controller executing Terminal Control Operations (TCO), up to a small team conducting long-haul, networked, Distributed Mission Operations (DMO) missions using multiple scenarios. It is capable of processing and displaying a limited, accurate two dimensional air/ground scene representing virtual and constructive forces generated locally or in the DMO environment. The JTC TRS DT can utilize a Ranger 47 to provide emulated/simulated binocular, laser range finder and laser designator equipment to support JTAC training capabilities. System configuration and performance capabilities are interoperable, modular, and scalable to allow selectable configuration options. JTC TRS DT will be compatible and concurrent with JTC TRS and meet this performance specification.

2 APPLICABLE DOCUMENTS

2.1 Government Documents

The following specifications, standards, and handbooks form a part of this document. If a specific version is not identified explicitly herein, the version of each document current at the time of contract award shall be used.

ID/Number Title Rev/Date AFCD Standard, Version 2

Air Force Common Dataset (AFCD), Version 2 1 DEC 11

AFI 13-112,

Volume 1

Joint Terminal Attack Controller (JTAC) Training Program

29 SEP 17

AFMAN 13-112,

Volume 2

Joint Terminal Attack Controller (JTAC) Standardization/Evaluation Program

6 JUN 18

AFI 91-203

(AFGM3)

Air Force Consolidated Occupation Safety Instruction (Air Force Guidance Memorandum 3, 19 August 2014)

15 JUN 12

(AFGM 3, 19 AUG 14)

AFTTP 3-3 JTAC Combat Fundamentals Joint Terminal Attack Controller 8 Dec 16

CJCSI 3170.01I Joint Capabilities Integration and Development System 31 AUG 18

CJCSI 6212.01E Interoperability and Supportability of Information Technology and National Security Systems

21 MAR 12

ATP 3-09.30 Observed Fire 28 SEP 17

JFIRE

(ATP 3-09.32)

Multi-Service Tactics, Techniques, and Procedures for the Joint Application of Firepower (Allied Tactical Publication 3-09.32)

JAN 16

JP3-09.3 Joint Tactics, Techniques and Procedures for Close Air Support

25 NOV 14

JTAC JMETL Joint Terminal Attack Controller (JTAC) Joint Mission Essential Task List (JMETL)

1 Dec 2017

MIL-STD-882 DoD Standard Practice for System Safety 11 MAY 12

NAVMC 3500.7 Artillery Training and Readiness Manual 18 JUN 15

DACAS JT TTP Digitally Aided Close Air Support (DACAS) Joint Test (JT) Tactics, Techniques, and Procedures (TTP)

MAY 18

2.1.1 Additional Publications/Documents

Combat Air Force (CAF) DMO System Standards (Current version posted on DMO Network (DMON) 2.0 website [https://secure.dmon2.com] at time of contract award)

• Common Models

• Conformance Testing

• Data Sharing

• Event Control

• Network

• Reference Federation Object Model

• Security

• Synthetic Natural Environment

• Tailored DIS

• Technical Performance

• Threat Representation and Computer Generated Forces

• Visualization

2.2 Non-Government Documents

The following documents form a part of this document to the extent specified herein.

ID/Number Title Rev/Date

ANSI/NEMA

Z535.3-2011

Criteria for Safety Symbols 15 SEP 11

ANSI/NEMA

Z535.4-2011

Product Safety Signs and Labels 15 SEP 11

CIGI Version 3.3

ICD

per http://cigi.sourceforge.net/index.php 3 NOV 08

IEEE 1278.1-2012 Standard for Distributed Interactive Simulation – Application Protocols

19 DEC 12

NFPA 70 National Electric Code 2014 Edition

2.3 Order of Precedence

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

3 REQUIREMENTS

3.1 Specific Performance Requirements

The performance requirements defined herein are the minimum level of acceptable performance.

3.2 General Requirements

3.2.1 Training

The JTC TRS DT shall provide training and mission rehearsal of the skills required (per the references listed in 2.1) to perform CAS and CFF missions.

3.2.2 Open Architecture

The JTC TRS DT architecture shall permit upgrades or interchange hardware, software, or peripheral components into the JTC TRS DT baseline without having to reengineer other JTC TRS DT components.

3.3 Mission Requirements

3.3.1 General Mission Requirements

3.3.1.1 Mission Types

JTC TRS DT shall be able to conduct both preplanned and immediate CAS and CFF missions.

3.3.1.2 Simultaneous Operations

JTC TRS DT shall allow simulation of a simultaneous integration of CAS, CFF, Suppression of Enemy Air Defense (SEAD), Joint Air Attack Team (JAAT) procedures with Fire Support Coordination Measures (FSCM) and Airspace Coordination Measures (ACM) missions.

3.3.1.2.1 System shall have no intrinsic limit on the number of mission types which can be conducted simultaneously. Hardware and trainee capabilities may cause a limit, but the system shall not have a hard set limit.

3.3.1.2.2 System shall have the ability to display and control multiple formations of fixed (minimum two formations of CAS and/or Forward Air Controller-Airborne (FAC-A) aircraft), rotary wing, Intelligence, Surveillance and Reconnaissance (ISR) and Unmanned Aircraft System (UAS) simultaneously, while also displaying and allowing surface and Naval fires.

3.3.2 Close Air Support (CAS) Requirements

3.3.2.1 Training Standards

JTC TRS DT shall meet Joint Terminal Attack Controller (JTAC) training and evaluation standards identified in AFI 13-112 Volume 1 & AFMAN 13-112 Volume 2, Navy/Marine Corps (NAVMC) 3500.7 and JTAC Joint Mission Essential Task List (JMETL) with the exceptions of full night or type 1 control requirements due to limited student station display capabilities.

3.3.2.2 Types of Terminal Attack Control

JTC TRS DT shall provide training and rehearsal for each of the following terminal attack controls as defined in Joint Publication (JP) 3-09.3 both day and limited night (no NVG capability) to include laser designation capability:

a) Type 2

b) Type 3

3.3.2.3 CAS Planning

Advise ground commander on Close Air Support assets in support of ground scheme of maneuver.

3.3.2.3.1 JTC TRS DT shall enable the trainee to submit Joint Tactical Air Strike Request (JTAR) per AFI 13-112 V1 Table A3.2 Task 01.1.8.

3.3.2.4 Target Acquisition

JTC TRS DT shall enable the trainee to detect targets based on provided CAS target nominations for the scenario.

3.3.2.4.1 JTC TRS DT shall execute target acquisition via aided and unaided during daytime conditions per Air Force Instruction (AFI) 13-112 V1 Table A3.2 Task 03.1.1.1.

3.3.2.4.2 JTC TRS DT shall execute target acquisition via remote observer per AFI 13-112 V1 Table A3.2 Task 03.1.1.3.

3.3.2.4.3 JTC TRS DT shall execute target acquisition via remote real-time sensor video downlink information per AFI 13-112 V1 Table A3.2 Task 03.1.1.4.

3.3.2.5 Target Location

JTC TRS DT shall enable the trainee to locate targets in a scenario via the following methods:

3.3.2.5.1 Map plot per AFI 13-112 V1 Table A3.2 Task 03.1.2.1.

3.3.2.5.2 Coupled Global Positioning System (GPS)/Laser Range Finder (LRF) System per AFI 13-112 V1 Table A3.2 Task 03.1.2.2.

3.3.2.5.3 Match target location accuracy and proper coordinate format to desired weapons system per AFI 13-112 VI Table A3.2 Task 03.2.

3.3.2.5.4 JTC TRS DT shall enable selection of available weapon system and adjust/change selections throughout the execution of a scenario as required to meet mission objectives.

3.3.2.6 Coordinate CAS Missions

3.3.2.6.1 JTC TRS DT shall enable the trainee to coordinate CAS Missions with other events within the scenario.

3.3.2.6.2 JTC TRS DT shall enable the trainee to integrate CAS missions with ground scheme of maneuver for traditional and irregular scenarios per AFI 13-112 V1 Table A3.2 Task 03.3.1.

3.3.2.6.3 JTC TRS DT shall enable the trainee to integrate CAS missions with surface-based fires per AFI 13-112 V1 Table A3.2 Task 03.3.2.

3.3.2.6.4 JTC TRS DT shall enable the trainee to integrate CAS missions with existing fire support coordination measures per AFI 13-112 V1 Table A3.2 Task 03.3.3.

3.3.2.6.5 JTC TRS DT shall enable the trainee to integrate CAS missions with existing airspace coordination measures.

3.3.2.7 Coordinate CAS Target engagement

3.3.2.7.1 JTC TRS DT shall enable the trainee to communicate and direct the scenario activity to support mission objectives

3.3.2.7.2 JTC TRS DT shall enable the trainee to receive aircraft check-in brief and provide situation update to CAS aircraft per AFI 13-112 V1 Table A3.2 Task 03.5.1.

3.3.2.7.3 JTC TRS DT shall enable the trainee to provide Gameplan and CAS Attack Brief per AFI 13-112 V1 Table A3.2 Task 03.5.2.

3.3.2.7.4 JTC TRS DT shall enable the trainee to provide weaponeering recommendation to achieve desired effects per AFI 13-112 V1 Table A3.2 Task 03.5.4.

3.3.2.8 Execute de-confliction of aviation assets

JTC TRS DT shall enable the trainee to execute procedural control of aircraft providing safe separation to achieve mission objectives.

3.3.2.8.1 JTC TRS DT shall enable the trainee to execute procedural control of aircraft to provide safe separation of aircraft per AFI 13-112 V1 Table A3.2 Task 03.4.1.

3.3.2.8.2 JTC TRS DT shall enable the trainee to execute procedural control of aircraft to provide safe separation from fires per AFI 13-112 V1 Table A3.2 Task 03.4.2.

3.3.2.9 Execute target marking for CAS assets

JTC TRS DT shall enable the trainee to conduct target marking.

3.3.2.9.1 JTC TRS DT shall enable the trainee to execute visual target marking for CAS with indirect fire assets per AFI 13-112 V1 Table A3.2 Task 03.6.1.

3.3.2.9.2 JTC TRS DT shall enable the trainee to execute sensor target marking for CAS assets per AFI 13-112 V1 Table A3.2 Task 03.6.2.

3.3.2.10 Control CAS missions in support of the ground scheme of maneuver JTC TRS DT shall enable the trainee to control CAS using the following weapon systems deliveries:

3.3.2.10.1 JTC TRS DT shall enable the trainee to control laser guided weapon system deliveries, including the capability to specify and match laser Pulse Repetition Frequency (PRF) codes.

3.3.2.10.2 JTC TRS DT shall enable laser guided munitions to acquire either the laser designator or the target based on the aircraft delivery orientation relative to the laser designator per Laser Designation Zones (JFIRE).

3.3.2.10.3 JTC TRS DT shall enable the trainee to control coordinate-dependent weapons deliveries.

3.3.2.10.4 JTC TRS DT shall enable the trainee to control sensor-guided weapons deliveries.

3.3.2.10.5 JTC TRS DT shall enable the trainee to control non-precision weapons CAS missions.

3.3.2.11 CAS Missions

3.3.2.11.1 JTC TRS DT shall support the execution phase of CAS missions per AFI 13-112 V1 Table A3.2 Task 03 with the exception of full night (limited only, no NVG capability) and Type 1 control.

3.3.2.11.2 JTC TRS DT shall enable the trainee to control in excess of 3 or more aircraft flights/sections/formations in any combination of missions herein.

3.3.2.11.3 JTC TRS DT shall integrate the following types of SEAD during the execution of CAS missions per AFI 13-112 V1 Table A3.2 Task 3.7.

a) Continuous

b) Interrupted

c) Non-Standard (per AFTTP 3-3 JTAC)

3.3.2.11.4 JTC TRS DT shall enable the trainee to control day fixed-wing CAS missions per AFI 13-112 V1 Table A3.2 Task 03.9.1.

3.3.2.11.5 JTC TRS DT shall enable the trainee to control night fixed-wing CAS missions per AFI 13-112 V1 Table A3.2 Task 03.9.2

3.3.2.11.6 JTC TRS DT shall enable the trainee to control day and night rotary-wing CAS missions per AFI 13-112 V1 Table A3.2 Task 03.9.3.

3.3.2.11.7 JTC TRS DT shall enable the trainee to execute a CAS mission utilizing a FAC- A per AFI 13-112 V1 Table A3.2 Task 03.9.5.

3.3.2.11.8 JTC TRS DT shall enable the trainee to control urban CAS missions per AFI 13- 112 V1 Table A3.2 Task 03.10.

3.3.2.11.9 JTC TRS DT shall enable the trainee to control day and night ISR/UAS missions.

3.3.2.11.10 JTC TRS DT shall enable the trainee to integrate ground-delivered illumination.

3.3.2.11.11 JTC TRS DT shall enable the trainee to control aviation-delivered illumination.

3.3.2.11.12 JTC TRS DT shall enable the trainee to control adverse weather CAS missions.

3.3.2.11.13 JTC TRS DT shall enable the trainee to control AC-130 fire missions.

3.3.2.11.14 JTC TRS DT shall respond appropriately to all JTAC Brevity Codes (JFIRE and JP 3-09.3) via interaction from either the Instructor/Operator Station (IOS) or Pilot Station Console (PSC). The codes include “Abort,” “Cleared Hot,” “Cleared to Engage,” “Continue,” and “Continue, Dry” commands.

3.3.2.12 CAS Target Location Methods

JTC TRS DT shall support target location and marking using the following methods

(JP 3-09.3):

a) Grid Coordinates

b) Polar Plot

c) Reference Point

3.3.2.13 CAS Communication

3.3.2.13.1 JTC TRS DT shall support a full CAS mission. (JP 3-09.3)

3.3.2.13.2 JTC TRS DT shall provide the trainee the capability to provide updated friendly and enemy situation to the aircraft conducting CAS missions.

3.3.2.14 Digitally Aided CAS (DACAS)

JTC TRS DT shall integrate current DACAS capability and support all applicable CAS actions as defined in section 3.3.2 CAS of this Performance Specification and DACAS JT TTP dated May 2018. It is expected that the same solution for the JTC TRS Dome will be utilized on the JTC TRS DT. Interoperability over DMO is required for all platforms that possess DACAS capability.

3.3.2.14.1 JTC TRS DT shall integrate and utilize the Android Tactical Assault Kit (ATAK) as the primary Situational Awareness (SA) tool for organizing DACAS. All menus, buttons, widgets, and features within ATAK are expected to be functional.

3.3.2.14.2 JTC TRS DT shall integrate and utilize Battlefield Airmen DataLinks (BADL) as the primary ATAK plugin for ACC units to conduct DACAS. All menus, buttons, widgets, and features within BADL are expected to be functional.

3.3.2.14.3 JTC TRS DT shall integrate and utilize Android Tactical Radio Application eXtension (ATRAX) as the primary ATAK plugin for AFSOC units to conduct DACAS. All menus, buttons, widgets, and features within ATRAX are expected to be functional.

3.3.2.14.4 JTC TRS DT shall integrate and utilize the Hand Held Link-16 (HHL- 16)/Portable Radio Communications-161 (PRC-161) simulated radio for DACAS transmissions.

3.3.3 Call for Fire (CFF) Requirements

JTC TRS DT shall accept the standard United States (US) and North Atlantic Treaty Organization (NATO) CFF Mission formats outlined in the JFIRE, Field Manual (FM) 6-30, NAVMC 3500.7 publications to include:

3.3.3.1 Adjust Fire

3.3.3.1.1 JTC TRS DT shall enable the trainee to apply target corrections based on Observer to Target (OT) line and Gun to Target (GT) line.

3.3.3.1.2 JTC TRS DT shall support target location and marking using the following methods (FM 6-30, JFIRE):

a) Grid Method

b) Polar Plot Method

c) Shift from Known Point Method

3.3.3.2 Fire For Effect

Fire-for-effect mission is used when the observer has an accurate means of determining target location and elevation. At a minimum, an eight-digit grid will be used for all fire-for-effect missions. Once a fire-for-effect request has been sent, the firing battery will fire a predetermined number of rounds intended to neutralize the target. If the rounds do not neutralize the target, an adjustment can be made before asking the battery to repeat the mission. If desired effects are not met, but the target location is accurate, simply pass repeat and the target number.

3.3.3.3 Marking

Spotting round, normally white phosphorous (WP) or illumination on the deck to indicate targets to aircraft, ground troops, or fire support.

3.3.3.4 Suppression of Enemy Air Defenses (SEAD)

JTC TRS DT shall support target fire suppression using the following methods:

a) Grid Method

b) Polar Plot Method

c) Shift from Known Point Method

3.3.3.5 Illumination

JTC TRS DT shall support illumination missions using the following methods:

a) Grid Method

b) Polar Plot Method

c) Shift from Known Point Method

3.3.3.6 Naval Surface Fire Support (NSFS) Call For Fire

JTC TRS DT shall support NSFS target location and marking using the following methods:

a) Grid Method

b) Polar Plot Method

c) Shift from Known Point Method

3.3.3.7 CFF Munitions

JTC TRS DT shall perform the above CFF missions using surface to surface assets and munitions listed in Appendix F in accordance with JFIRE, FM 6-30, NAVMC

3500.7 publications.

3.4 Simulated Battlefield Environment Requirements

All elements of the simulated battlefield and trainee interactive elements shall correlate and interact with each other to provide a continuous and cohesive virtual environment.

3.4.1 Visual System Requirements

JTC TRS DT will provide visual system interfaces to support flat screen televisions, projectors or head mounted displays. Minimum requirements are for 1080P cybersecurity compliant visual systems in order to support required training.

3.4.2 Aural Cueing Requirements

3.4.2.1 Audio Cues

3.4.2.1.1 JTC TRS DT shall provide at least minimum limited audio cues for:

a) Vehicles

b) Aircraft

c) Detonations

d) Weapons

3.4.2.1.2 Sound effects shall have a minimum of two channel speakers associated with the student station visual display consistent with front distance and direction only from the trainee’s location and orientation of the sound effect source.

3.4.2.1.3 System shall simulate audio effect degradation due to terrain effects shielding and audio line of sight.

3.4.2.1.4 System sounds shall be representative of the entity type being emulated.

3.4.2.2 Not Applicable

3.4.2.3 Audio Correlation

JTC TRS DT shall correlate audio and visual cues with the limited synthetic environment displayed to include range and atmospheric effects.

3.4.3 Entity Interaction Requirements

3.4.3.1 General Entity Interaction Requirements

3.4.3.1.1 JTC TRS DT shall use off-the-shelf Semi-Automated Forces (SAFs)/Computer Generated Forces (CGFs).

3.4.3.1.2 The SAF/CGF shall be capable of operating with the system in a stand-alone mode or in a networked mode.

3.4.3.1.3 The SAF/CGF shall encompass, at a minimum, the entities listed in Appendix E and F of this specification. If multiple variants of a listed entity are available, a minimum of two variants must be available to the IOS operator. All models provided must support CAF DMO Common Model Standards to include correct appearance bits and articulated parts.

3.4.3.1.4 Entity details shall be sufficient for detection, orientation, recognition, and identification as well as battle damage assessment by the trainee.

3.4.3.1.5 The SAF/CGF shall represent the entities as selected by the IOS/PSC.

3.4.3.1.6 The SAF/CGF shall represent and control visual models in Appendix E with detailed visual characteristics to enable the trainee to recognize and evaluate directional position, distance, and attack/landing geometry to accomplish training tasks.

3.4.3.1.7 The SAF/CGF shall be capable of simulating the emissions of those early warning, acquisition and target tracking (Surface-to-Air Missile (SAM) / Guided Anti-Aircraft Artillery(AAA)) radar systems included in Appendix E and F and provide Radar Warning Receiver indications at the PSC (to include the generation of representative emitter audio for received radar emissions) in accordance with CAF DMO standards.

3.4.3.1.8 The SAF/CGF shall support trainee and entity attachments (e.g. human entities shall be capable of attaching to buildings, vehicles and helicopters) and detachments at normal ingress/egress points, both at the direction of the instructor at the IOS station or by the trainee.

3.4.3.1.9 Entities within the environment shall behave in accordance with the established operational parameters design criteria of the entity being represented to a level of realism which allows the trainees to complete their mission.

3.4.3.1.10 Entities shall have the capability of being damaged and destroyed by ordnance impact. Damage effects shall be commensurate with appropriate level of destruction to support realistic training.

3.4.3.1.11 Damage to designated targets or objects shall be customizable by the end user, through modification of target armor class/rating, weapon blast radius, and weapon blast effect/ intensity and consistent with open source weapons data.

Damage to personnel shall be within the 0.1% Probability of Incapacitation (PI) of the munitions risk-estimate distance in accordance with the Circular Error of Probability (CEP) of the weapon in accordance with the JFIRE.

3.4.3.1.12 The SAF/CGF shall determine the level of damage to an entity (in non-networked mode) based on types of weapons/force used, and shall be consistent with damage states viewed in the visual scene. In addition to the primary undamaged entity states, models shall possess the ability to have multiple damage states to include Mobility Kill, Weapons Kill, and Catastrophic Kill, as appropriate (See Appendix B – Glossary).

3.4.3.1.13 The weapon characteristics shall model the velocity, trajectory, and distance to target to produce realistic physics-based time-of-flight (TOF) for all virtually simulated munitions and weapon systems.

3.4.3.1.14 The SAF/CGF shall consider Line of Sight (LOS) and designator code in determining whether the designator spot is compatible or can be acquired by laser guided weapons.

3.4.3.1.15 The SAF/CGF shall demonstrate accurate time on target (TOT) and time to target (TTT) based on the established time line for both CFF and CAS missions.

3.4.3.1.16 The SAF/CGF shall enable the instructor to set alternative, TOT and TTT, using the IOS, to achieve desired training or mission objectives for CFF and CAS missions.

3.4.3.1.17 Aircraft associated weapon systems and weapon loads shall be assignable and provide the option to store and reuse pre-defined (from pre-mission brief or system database) Standard Conventional Loads (SCLs) to include mixed munitions loads on individual aircraft.

3.4.3.1.18 Aircraft, weapons system and ordnance failures and malfunctions shall be capable of being implemented at the IOS during a training session. Required failures are hung bomb, gun jam, weapon miss (outside CEP), guidance failure, and fuse malfunction/dud.

3.4.3.1.19 The SAF/CGF shall have the capability to aggregate and disaggregate entities [e.g. crowds normally disperse by disappearing into the surrounding environment (woods, buildings, farm lands, etc.). They may become combatants before or after they disperse. Enemy convoys could disperse into the available cover after initial attack.]

3.4.3.1.20 The SAF/CGF shall have the capability to control ground entities from the individual to multiple platoons for a company size force. Groups of entities shall be taskable by the SAF/CGF at the group level, and at the individual entity level.

3.4.3.1.21 The SAF/CGF shall have the capability to control both individual and group movement and behaviors, to include non-combatant/civilian and combatant.

Threat, friendly, and civilian personnel shall be incorporated into the same simulation to provide shoot-no-shoot events.

3.4.3.1.22 The SAF/CGF shall simulate representative military aircraft performance, speed characteristics, and aircraft maneuver and operational profiles which realistically vary with altitude and have the capability to program tactical approaches and variable weapons attack entry profiles.

3.4.3.1.23 Each aircraft shall perform based on the airframe being simulated to a level sufficient to allow trainee to perform realistic mission objectives.

3.4.3.1.24 The SAF/CGF shall simulate aircraft maneuvers and flight profiles to include formation flights, flight break-ups and overhead holding patterns.

3.4.3.1.25 The SAF/CGF shall simulate attack maneuvers to include level, diving, loft, pop-up weapons delivery, and standoff weapons delivery from low, medium, and high altitude for fixed and rotary wing aircraft.

3.4.3.1.26 The SAF/CGF shall simulate visual CAS overhead holding operations.

3.4.3.1.27 The SAF/CGF shall simulate CAS missions, to include multiple fixed (fighter and bomber) and rotary wing aircraft types, both single ship and formation/section tactics.

3.4.3.1.28 The SAF/CGF shall allow for aircraft to dispense chaff and flare countermeasures in response to surface-to-air or air-to-air threats. Applies to both fixed (fighter and bomber) and rotary wing aircraft types, both single ship and formation/section tactics.

3.4.3.1.29 The SAF/CGF radar and infrared guided anti-aircraft weapons shall respond to chaff and flare countermeasures deployed by targeted aircraft. The radar and infrared guided weapons shall adhere to weapon type and guidance and interact with the target based on the assigned probability of hit function.

3.4.3.1.30 The SAF/CGF shall allow for aircraft to set and to send out Identification Friend or Foe (IFF) modes (to include Mode 4A and 4B) and other transponder modes in accordance with Institute of Electrical and Electronics Engineers (IEEE) 1278.1- 2012 and to the Tailored DIS Standard as if an interrogation had been received.

3.4.3.2 Entity Quantity

3.4.3.2.1 The JTC TRS DT shall support processing of a minimum of one thousand (1000) externally generated simultaneous entities in a networked mode mission training scenario.

3.4.3.2.2 The JTC TRS DT shall support SAF/CGF generation of any combination of a minimum of five hundred (500) internally generated simultaneously active entities in a non-networked mission scenario.

3.4.3.2.3 The SAF/CGF shall have an editor function capable of adding and modifying entities, units and behaviors in addition to those identified in Appendix E to support future mission requirements.

3.5 Trainee Interactive Requirements

3.5.1 Trainee Virtual Interaction

3.5.1.1 JTC TRS DT shall track and maneuver the trainee position within the virtual environment to permit trainee to maintain cover from opposition force entities and maintain a covert status.

3.5.1.2 The trainee must be portrayed as an entity in the threat environment and shall be discernible to other entities in the virtual environment for the trainee to maintain awareness of covertness of their position and to permit engagement of/by enemy forces should concealment be lost.

3.5.1.3 IOS must be capable of selecting whether or not trainee can be targeted by hostile entities.

3.5.1.4 As an entity, the trainee shall be engaged by the enemy when position is discovered by visual line of sight and within the appropriate weapons engagement envelope.

3.5.1.5 As an entity, the trainee shall be capable of being injured or destroyed by friendly fire (fratricide), appropriate for the weapons and munitions in use during the scenario.

3.5.1.6 The trainee shall receive a visual and aural indication from JTC TRS DT, when he has been injured or destroyed by the enemy or friendly fire.

3.5.1.7 As an entity, the trainee shall be capable of engaging and destroying the enemy, appropriate for the munitions assigned at scenario generation.

3.5.1.8 The trainee eye-point shall be capable of movement within the natural environment as controlled by the trainee station. Movement shall include forward, backward, rotational and side-step capabilities.

3.5.2 System Tracking

3.5.2.1 JTC TRS DT shall provide a 3 Degree of Freedom (DOF) [See Appendix B definition of 3DOF] tracker for trainee Ranger-47 equipment which requires position or orientation tracking (See Appendix C1, “Tracking Required” column).

3.5.2.2 The tracker shall provide high speed tracking with no noticeable lag or jitter.

3.5.2.3 Not applicable

3.5.2.4 Not applicable

3.5.2.5 The tracking sensors shall be small, portable, and lightweight to accommodate use on all equipment requiring tracking (See Appendix C1, “Tracking Required” column).

3.5.2.6 The tracking sensors shall not hinder or alter the accomplishment of the training task.

3.5.3 Equipment Management

Simulated equipment falls into the following categories:

a) Visual equipment (requires image generation and tracking capability) (e.g., Ground Laser Target Designator (GLTD) II)

b) Audio equipment (requires radio capability) (e.g., Portable Radio Communications (PRC)-148)

c) Active equipment (requires tracking capability) (Ranger-47)

d) Passive equipment (e.g., clock, GPS)

3.5.3.1 All emulated equipment requiring date and time data shall be correlated with the mission date and time.

3.5.3.2 All emulated equipment requiring a tracking capability shall be correlated with the visual scene (See Appendix C1 Tracking Required column).

3.5.3.3 N/A

3.5.3.4 All equipment shall be available for assignment from the IOS at scenario startup. As soon as equipment is plugged in, the IOS shall initialize the equipment for use by the trainee during scenario execution.

3.5.4 Trainee Equipment Requirements

3.5.4.1 JTC TRS DT shall emulate or virtually simulate equipment designated as described in Appendix C1. Appendix C1 identifies the requirements level to which each individual piece of equipment shall be replicated. Software shall be modular and scalable to allow the software load to be upgradeable as the form-fit toolkit changes.

3.5.4.2 JTC TRS DT shall allow trainee to deploy, relocate and retrieve marker panels and strobe lights, as listed in Appendix C1.

3.5.4.3 Equipment Cabling

3.5.4.3.1 JTC TRS DT cabling between the system and trainee equipment shall not:

a) interfere with operation of equipment

b) distract the trainee

c) hinder trainee mobility or ability to perform the mission

3.5.4.3.2 Trainee radio interface shall include connections which emulate the handset or headset connection of simulated radios to stimulate a real-world trainee handset or headset.

3.5.4.3.3 Radio connections and GPS shall provide virtual, simulated interfaces to support digital CAS over the field computing devices.

3.5.4.3.4 Trainee radio cabling shall include an extension cable from the radio interface to the trainee headset or handset which allows the trainee to maintain mobility within the simulator.

3.5.4.3.5 System will accommodate a minimum of one trainee.

3.5.4.4 Equipment Marking

All emulated and simulated equipment shall be appropriately marked, identifying it as a simulated device.

3.6 Voice Communication Requirements

3.6.1 Radio Management

3.6.1.1 IOS shall be capable of simultaneously visually monitoring and selectively listening to student frequencies for active communications.

3.6.1.2 Configurable channels shall support simulation of both radio and digital communication networks.

3.6.2 Role-Play

JTC TRS DT shall provide the capability to role-play in all voice communication networks.

3.6.3 Intercom Control Management

3.6.3.1 JTC TRS DT shall provide a selectable basic communication capability, to communicate between the instructor, IOS operator, PSC operator and trainee, selectively and separate from the emulated radio communications.

3.6.3.2 Instructor/operator shall be capable of talking with any trainee or PSC, collectively or individually.

3.7 Instructor/Operator Station (IOS) Requirements

3.7.1 General IOS Requirements

JTC TRS DT shall provide an IOS that enables a single instructor/operator to initialize, control and monitor the training or mission rehearsal session.

3.7.1.1 IOS Environment

The IOS shall provide the instructor/operator with an effective environment in which to support the JTC TRS DT simulation system (e.g., private instructor to trainee communication capability, allow instructor to observe trainee).

3.7.1.2 System Start-up and Shut-down Control

The IOS shall provide a start-up and shut-down control for all powered system components. System start up process should not exceed 20 minutes.

3.7.1.3 Status Display

The IOS shall display the up or down status of all major system components during system startup. Any system required to perform a mission is considered a major system.

3.7.1.4 Distributed Training Interface

The IOS shall provide a capability to interface the system with distributed training exercises.

3.7.1.5 Help Function

The IOS shall have a built in HELP feature for basic system operation.

3.7.1.6 Multiple User Access Profiles

The IOS shall be the principal controlled access point for the instructors, operators and training administrators. Each user’s JTC TRS DT system access shall be controlled by authorized administrators and will be compliant with security (SECRET) and control access requirements. Physical access shall be controlled by system site security.

3.7.1.6.1 The IOS shall have multiple user access profiles providing restricted privileges for administrators, instructors, and operators.

3.7.1.6.2 A password protected operator access setting shall be available for each individual system operator.

3.7.1.6.3 The operator access levels shall have default settings.

3.7.1.6.4 The operator access levels shall be editable, by the administrator, at the local level, only.

3.7.2 Pre-Mission Preparation

3.7.2.1 Scenario Generation

The IOS shall include the capability to perform pre-mission preparation, including scenario generation, scenario file management and interface with DMO events.

3.7.2.1.1 The JTC TRS DT shall have the capability to develop, modify, save and delete scenarios at the IOS.

3.7.2.1.2 The IOS shall have the capability to select each entity type for use during scenario development.

3.7.2.1.3 The JTC TRS DT shall be capable of storing a minimum of 50 scenarios.

3.7.2.2 Scenario File Transportability

3.7.2.2.1 The IOS shall allow for transfer of scenario data between J/T/OSS and JTC TRS and other Operational Training Infrastructure (OTI) approved systems, via secure network connection or security approved portable media.

3.7.2.2.2 Data included in transported scenarios shall be all information required to execute the scenario, as written, on JTC TRS and other OTI approved training systems.

3.7.2.3 IOS Support for Networked Events

3.7.2.3.1 JTC TRS DT shall provide an IOS-to-IOS voice communications channel to support coordination of IOS actions with any other networked sites.

3.7.2.3.2 JTC TRS DT shall provide the capability to conduct secure and private communications with JTC TRS when connected to a non-DMO Network.

3.7.2.3.3 Secure and private communications with other DMO Federate Systems shall be provided for DMON Operations (per current DMO standards).

3.7.2.3.4 The IOS shall have the capability to issue open communications to all networked stations simultaneously for mission brief and debrief.

3.7.3 Mission Management

3.7.3.1 Scenario Control

3.7.3.1.1 The IOS shall start, stop, pause and restart a live, non-networked training scenario.

3.7.3.1.2 The IOS shall be able to save a snap point of current status of all system federates to be able to continue training (i.e. – “flyout” [see definition in Appendix B]) in a non-networked environment. The IOS shall record a bookmark in the After Action Review (AAR) file for every snap point created in the live scenario. Snap point options shall include the ability for an operator to add a label for future reference.

3.7.3.1.3 The instructor shall have the capability to reposition trainee eye-point and provide instruction as required to reinforce training.

3.7.3.1.4 The simulator shall be able to “flyout” from any snap point and continue training at the instructor’s discretion.

3.7.3.1.5 The IOS shall have the capability to begin a training session within 5 minutes after selection of databases and scenario.

3.7.3.1.6 The IOS shall have the capability to conduct dynamic scenario changes during real time to enable the instructor to adjust the scenario according to the trainee’ progress and interaction; thereby permitting increase or decrease in decisions or actions required by the trainee. (e.g., adding/deleting entities, reducing complexity, delaying, activating or advancing entry of an entity into the scenario, changing entity type etc.)

3.7.3.1.7 The IOS shall provide a visual and/or aural notification when the trainee has been destroyed by the enemy or fratricide.

3.7.3.2 Virtual Scene Interaction

3.7.3.2.1 The IOS shall be able to position the trainee at any location in the virtual environment and display the scene on the trainee visual display.

3.7.3.2.2 All trainee views, including Emulated Military Equipment (EME) Image Generator (IG) views, shall also be capable of being provided simultaneously to the Instructor as selectable views to allow the instructor to see what the trainee is seeing.

3.7.3.3 Natural Environment

3.7.3.3.1 The IOS shall monitor and control a natural environment generator providing a variety of effects in the simulated environment such as battlefield obscuration and weapon effects, rain, fog, snow, wind velocity and direction (to include different winds aloft profiles), visibility, time of day and shadowing consistent with sun angles and location. Winds aloft profiles must be capable of being input and separate from surface winds. Surface winds cover surface to 1000 Above Ground Level (AGL). Winds above 1000 AGL up to 30,000 would be considered winds aloft.

3.7.3.3.2 JTC TRS DT shall provide changing environmental effects to the visual scene and entities during a scenario so that the trainee is required to make timely decisions based on the observed changes.

3.7.3.3.3 Cloud Formations

3.7.3.3.3.1 JTC TRS DT shall display an adjustable cloud deck selectable at 500 ft.

increments. Cloud formations shall have 3D representation.Cloud layers shall present underneath views available in 1/8, 2/8, 3/8, 4/8, 5/8, 6/8, 7/8 and 8/8 coverage or a selectable percentage of entire sky.

3.7.3.3.3.2 The user shall be able to construct a weather scenario composed of at least two cloud layers. All cloud types shall move according to exercise wind speed and direction.

3.7.3.3.3.3 The cloud layers shall exhibit appropriate effects such as steady light rain, heavy showers.

3.7.3.3.3.4 A rain shaft shall be seen as a semi transparent texture under an associated cloud. Lightning shall be provided as a visual cue for thunderstorms. A ‘flash’ effect shall be provided whereby the scene is momentarily brightened.

3.7.3.3.4 Visibility

3.7.3.3.4.1 The JTC TRS DT shall provide the capability to define and modify visibility.

The visibility range shall be modifiable as a function of:

• Fog

• Haze

• Smoke

• Sandstorm

• Rain

• Snow

3.7.3.3.4.2 The JTC TRS DT shall replicate a full range of visibility selectable from 200

ft. to unrestricted.

3.7.3.3.4.3 Weather phenomenon shall move through the area in accordance with the selected wind profiles.

3.7.3.3.5 Natural environment wind conditions shall affect smoke, dust, clouds, precipitation and parachute or other entities such as retarded weapons or illumination flares.

3.7.4 Trainee Evaluation

3.7.4.1 Electronic Documentation

System capabilities shall include video record storage.

3.7.4.2 Recorded Information

The IOS shall be capable of receiving and recording all information necessary to control, monitor and evaluate trainee performance including video, radio traffic, and digital communications.

3.7.4.3 Training Feedback Reports

3.7.4.3.1 The IOS shall have the capability to produce training feedback reports when requested by the instructor.

3.7.4.3.2 The feedback reports shall document training performance and provide feedback for trainee improvement and include weapons engagement, hits, misses, kills, battle damage assessment, ammunition expended, and the distance between the target and the ordnance impact point.

3.7.5 After Action Review (AAR)

3.7.5.1 The IOS shall be capable of recording a scenario file of up to 2 hours of continuous operation per scenario.

3.7.5.2 System shall have no intrinsic limit on the number of bookmarks. System shall be capable of creating a bookmark at any point during a live training session.

3.7.5.3 The AAR shall contain all scenario activity (i.e. database, entity behavior, communications, etc.) required to review trainee performance, including stealth-view from any perspective within the local mission environment.

3.7.5.4 The IOS shall be able to produce an AAR within 30 minutes following the completion of a training event for use within the JTC TRS DT or downloaded to portable media for use on other compatible training systems.

3.7.5.5 All audio and video shall be synchronized to the main screen’s timeline, providing a seamless means of viewing JTAC actions during debrief

3.7.5.6 The IOS shall have the capability to perform the following operations to review a recorded scenario:

a) Start

b) Stop

c) Fast forward

d) Reverse

e) Pause

f) Jump to bookmark

g) Jump to a specified time

h) Reposition eye-point

i) Re-play from start

3.7.5.7 To facilitate clear images during AAR and other playback scenarios, the IOS shall be capable of selecting or deselecting the simulated natural environment effects generated in a scenario for recording playback and AAR. For example, night time operations must be able to be reviewed in a daytime setting to ensure operation clarity.

3.8 Human-In-The-Loop (HITL) Requirements

3.8.1 Pilot Station Console (PSC) Functionality (OPTIONAL-when equipped) JTC TRS DT shall have a PSC capable of providing flight characteristics and performance for all aircraft listed in Appendix E to enable trainee to complete CAS missions.

3.8.1.1 The PSC shall interact and operate within the JTC TRS DT simulated environment as a separate subsystem.

3.8.1.2 The PSC shall allow an operator with limited aircraft knowledge to fly aircraft (using aircraft Tactics, Techniques, and Procedures (TTPs)) in the virtual environment following the direction of the trainee during a CAS mission. The PSC will provide navigation, weapon steering and release cues in addition to Heads Up Display (HUD)-displayed attitude, altitude, heading and airspeed information required to properly fly the aircraft in attack profiles.

3.8.2 PSC Configuration (OPTIONAL-when equipped)

3.8.2.1 The PSC shall have a slewable field of view with appropriate Heads-Up Display (HUD) symbology in the forward view and targeting information capabilities.

3.8.2.2 The PSC shall have a targeting pod sensor view capable of appropriately simulating switchable Forward Looking Infrared (FLIR)-White Hot, FLIR-Black Hot, and Daylight Electro-Optical (EO). Targeting Pod views shall also be provided to the emulated Remotely-Operated Video-Enhanced Receiver (ROVER) device.

Targeting pod will be controllable and slewable manually using Hands on Throttle and Stick (HOTAS).

3.8.2.3 The PSC shall have a sensor view providing targeting information and situational awareness, not including aircraft radar, appropriate to the aircraft being controlled to include ability to set laser designation codes and ability to provide laser ranging and targeting and coordinate generation.

3.8.2.4 The PSC shall provide a correlated visual display view of the mission area from zero up to and including 40K feet.

3.8.2.5 The PSC visual and sensor systems shall be impacted by conditions as they are presented in the virtual environment.

3.8.2.6 The cockpit view, instrumentation and controls shall be generic without regard to the type of fixed or rotary-wing aircraft being controlled.

3.8.2.7 A map view display of the mission area shall be selectable at the PSC.

3.8.3 PSC Entity Management (OPTIONAL-when equipped)

3.8.3.1 The entity type to be controlled shall be selectable at the PSC.

3.8.3.2 The PSC shall have the ability to control any mobile entity (such as humans and vehicles) in the scenario to control viewpoint, movement or weapons as desired when not controlling aircraft.

3.8.3.3 The PSC shall emulate communication with the trainee using the correct network according to the type aircraft or vehicle being simulated and In Accordance With (IAW) the scenario communications plan.

3.8.3.4 The PSC shall actively engage targets with a variety of munitions types according to the type aircraft or vehicle being simulated and as directed by mission.

3.8.3.5 The PSC shall have the capability of controlling up to a four aircraft flight attack (i.e., two or four ship).

3.8.3.6 The PSC shall allow an operator to assume control of a computer controlled aircraft and then return the aircraft to computer control.

3.8.3.7 The PSC shall support simulation of a two aircraft flight attack, whereas the pilot would control lead aircraft, then assume control of the trailing aircraft, to control both target executions as directed by the trainee. The pilot, via the PSC, can control either aircraft of a two aircraft attack group and be able to split the formation if needed and direct the action of the other aircraft back to computer control until formations are rejoined.

3.8.3.8 The PSC shall be capable of specifying following distance of trail aircraft to facilitate adjustments from lead aircraft’s attack, or direct wingman to hold at appropriate location for single aircraft attack.

3.8.4 PSC Auto-Pilot (OPTIONAL—when equipped)

3.8.4.1 The PSC shall have the ability to put an entity on a scripted maneuver.

3.8.4.2 The PSC shall have the ability to automatically fly a racetrack pattern, circular orbit, or an assigned heading and altitude as needed.

3.9 Integrated Simulations System Requirements

3.9.1 Network Interface Requirements

3.9.1.1 JTC TRS DT shall have both an internal and an external network capability. It shall enable training in a stand-alone or networked mode.

3.9.1.2 JTC TRS DT shall provide commonality and adhere to established DoD policy for simulation systems (i.e., be a scalable, agile, interoperable system that can be functionally compatible with the DMO architecture).

3.9.1.3 JTC TRS DT shall be functionally interoperable with current distributed training devices and their relevant networks IAW CAF DMON standards.

3.9.1.4 JTC TRS DT shall be scalable to support the spectrum of training requirements from unit-level part-task training, through stand-alone immersive training, up to large scale force on force distributed events.

3.9.1.5 JTC TRS DT shall comply with 100% of all information exchange requirements (see definition in Appendix B) IAW Chairman of the Joint Chiefs of Staff Instruction

(CJCSI) 6212.01E.

3.9.2 External Network

3.9.2.1 Distributed Network Operations

3.9.2.1.1 Initially all distributed network…