Attachment 2_FoS_PSpec.pdf

FA8621-20-R-0003

Section J, Attachment 02, JTC TRS Performance Specification

PERFORMANCE SPECIFICATION

JOINT TERMINAL CONTROL TRAINING AND REHEARSAL SYSTEM

(JTC TRS)/U

FAMILY OF SYSTEMS (FOS)

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

Version 1.0 xx January 2020

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) (29 August 2018). Other requests shall be referred to AFLCMC/WNS.

FA8621-20-C-XXXX

CHANGES & REVISIONS

Document History BASIS ECP / NOR DATE REVISION Paragraph

Initial (8.0) n/a 5 Aug 15 n/a n/a Revision (1.0) JTC TRS Re-compete RFP P-

Spec FoS Xx Jan 20 9.6 1. Removed Link 16 PRC-161 ATAK from 3.3.2.15

2. Removed updated references in section 2.1 and DACAS JT TTP

3. Removed updates in Appendix C to include the HHL-16/PRC-161

4. Updated 1.1 to include scope for all JTC TRS devices

5. Updated section 3.3.2 to define requirements for device types.

6. Updated Appendix C

7. Updated Appendix G

Table of Contents

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.3.2 Close Air Support (CAS) Requirements

3.3.3 Call for Fire (CFF) Requirements

3.4 Simulated Battlefield Environment Requirements

3.4.1 Visual System Requirements

3.4.2 Aural Cueing Requirements

3.4.3 Entity Interaction Requirements

3.5 Trainee(s) Interactive Requirements

3.5.2 System Tracking

3.5.3 Equipment Management

3.5.4 Trainee(s) Equipment Requirements

3.6 Voice Communication Requirements

3.6.2 Role-Play

3.6.3 Intercom Control Management

3.7 Instructor/Operator Station (IOS) Requirements

3.7.2 Pre-Mission Preparation

3.7.3 Mission Management

3.7.4 Trainee(s) Evaluation

3.7.5 After Action Review (AAR)

3.7.6 JTAC Instructor Station:

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

3.8.2 PSC Configuration

3.8.3 PSC Entity Management

3.8.4 PSC Auto-Pilot

3.9 Integrated Simulations System Requirements

3.9.2 External Network

3.10 Design and Construction

3.10.1 Physical Characteristics

3.10.2 Software

3.10.3 System Network Management

3.10.4 Diagnostic Software

3.10.5 Hardware

3.10.6 Technology Insertion, System Evolution, and Mission Concurrency

3.10.7 Parts, Materials, and Processes

3.10.8 Lighting and Illumination

3.10.9 Environmental Conditions

3.10.10 Electromagnetic Compatibility (EMC)

3.10.11 Availability

3.10.12 Maintenance

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

4.1.1 Analysis

4.1.2 Demonstration

4.1.3 Examination

4.1.4 Test

5 PACKAGING

6 RESERVED FOR FUTURE USE – BLANK

APPENDIX A – ACRONYMS

APPENDIX B – DEFINITIONS

APPENDIX C – EQUIPMENT REQUIREMENTS

APPENDIX D – RADIO FREQUENCIES

APPENDIX E – MODELS/ENTITIES

APPENDIX F – ORDNANCE/ENTITIES

APPENDIX G – VISUAL REQUIREMENTS

APPENDIX H – REMOTE SCANNING AND PATCHING

1 SCOPE

1.1 Scope

This performance specification covers the family of Joint Terminal Control Training and Rehearsal System (JTC TRS) devices. This document establishes the Government’s requirements for system performance of all JTC TRS devices. From this point forward, references to “JTC TRS” will signify requirements for all three devices: immersive dome, desktop (DT), and portable/deployable (PT), unless specifically noted.

NOTE: The EME and visual requirements in Appendix C and Appendix G will outline the training requirements and equipment that pertain to each device configuration. For example, the desktop and portable/deployable configuration do not have M4 Carbine in their EME package, and therefore none of the M4 Carbine training requirements would pertain to those systems.

1.2 System Overview

JTC TRS is a mission simulation system that has applicability for training personnel in all services (Army, Navy, Marines, and Air Force). The JTC TRS functionality 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 provides a robust, interactive multimedia, High Level Architecture (HLA) or Distributed Interactive Simulation (DIS) compliant system. The system will provide constructive entity control, realistic flight mission profiles, representative ordnance and effects, and support or include actual or simulated military equipment. The JTC TRS supplements field training to provide realistic introductory training, upgrade training, proficiency training, continuation training and mission rehearsal in a synthetic battlespace. The JTC TRS 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 an accurate air/ground scene representing virtual and constructive forces generated locally or in the DMO environment. The JTC TRS utilizes a simulated, stimulated, and emulated equipment suite to support the immersive environment. System configuration and performance capabilities are interoperable, modular, and scalable to allow selectable configuration options. JTC TRS is planned to be procured as a production ready off the shelf device to meet this performance specification. The foreseeable life of the JTC TRS shall be a minimum of 15 years.

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 Training (JTAC) Program

29 SEP 17

AFI 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 T h l d N i l S i S

21 MAR 12

Field Manual (FM) 6 30

Tactics, Techniques, and Procedures for Observed Fire 16 JUL 91

JFIRE

Multi-Service Tactics, Techniques, and Procedures for the J i A li i f Fi (Alli d T i l P bli i

JAN 16

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

25 NOV 14

JTAC JMETL Joint Terminal Attack Controller (JTAC) Joint Mission E i l T k Li (JMETL) (f MOA d d 1 J 12)

1 DEC 17

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

NAVMC 3500.7 Artillery Training and Readiness Manual 18 JUN 15

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-

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.

http://cigi.sourceforge.net/index.php

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 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 architecture shall permit upgrades or interchange hardware, software, or peripheral components into the JTC TRS baseline without having to reengineer other JTC TRS components.

3.3 Mission Requirements

3.3.1 General Mission Requirements

3.3.1.1 Mission Types

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

3.3.1.2 Simultaneous Operations

JTC TRS shall simulate 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 missions 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 (minimum of four aircraft), 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 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).

3.3.2.2 Types of Terminal Attack Control

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

a) Type 1 (excluding the DT and PT configurations that are not configured with Head Mounted Displays)

b) Type 2

c) 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 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 shall enable the trainee(s) to detect targets based on provided CAS target nominations for the scenario.

3.3.2.4.1 JTC TRS shall execute target acquisition via aided or unaided day vision per

Air Force Instruction (AFI) 13-112 V1 Table A3.2 Task 03.1.1.1.

3.3.2.4.2 JTC TRS shall execute target acquisition via aided or unaided night vision per AFI 13-112 V1 Table A3.2 Task 03.1.1.2. (excludes DT and non-HUD

PT)

3.3.2.4.3. JTC TRS shall execute target acquisition via remote observer per AFI 13-112

V1 Table A3.2 Task 03.1.1.3.

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

3.3.2.5 Target Location

JTC TRS 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 Match Target location/accuracy/format

3.3.2.6.1. JTC TRS shall enable the trainee to submit Joint Tactical Air Strike Request

(JTAR) per AFI 13-112 V1 Table A3.2 Task 01.19.

3.3.2.6.2. JTC TRS shall enable the trainee(s) to determine accuracy of target location per AFI 13-112 V1 Table A3.2 Task 03.2.

3.3.2.6.3. JTC TRS shall enable the trainee(s) to transmit the proper coordinate format to desired weapon systems per AFI 13-112 V1 Table A3.2 Task 03.2.

3.3.2.6.4. JTC TRS 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.7 Coordinate CAS Missions

3.3.2.7.1. JTC TRS shall enable the trainee to submit JTAR per AFI 13-112 V1 Table

2.1 Task 01.19

3.3.2.7.2. JTC TRS shall enable the trainee(s) to coordinate CAS Missions with other events within the scenario.

3.3.2.7.3. JTC TRS shall enable the trainee(s) 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.7.4. JTC TRS shall enable the trainee(s) to integrate CAS missions with surface-based fires per AFI 13-112 V1 Table A3.2 Task 03.3.2.

3.3.2.7.5. JTC TRS shall enable the trainee(s) 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.7.6 JTC TRS shall enable the trainee(s) to integrate CAS missions with existing airspace coordination measures per AFI 13-112 V1 Table A3.2 Task 03.3.4.

3.3.2.8 Coordinate CAS Target engagement

3.3.2.8.1. JTC TRS shall enable the trainee(s) to communicate and direct the scenario activity to support mission objectives

3.3.2.8.2. JTC TRS shall enable the trainee(s) to receive aircraft check-in brief per AFI

13-112 V1 Table A3.2 Task 03.4.1.

3.3.2.8.3. JTC TRS shall enable the trainee(s) to provide situation update to CAS aircraft per AFI 13-112 V1, Table A3.2, Task 03.4.2.

3.3.2.8.4. JTC TRS shall enable the trainee(s) to provide CAS Brief per AFI 13-112, V1 Table A3.2, Task 03.4.3.

3.3.2.8.5. JTC TRS shall enable the trainee(s) to provide weaponeering guidance to achieve desired effects per AFI 13-112, V1 Table A3.2, Task 03.4.4.

3.3.2.9 Execute de-confliction of aviation assets

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

3.3.2.9.1. JTC TRS shall enable the trainee(s) to execute procedural control of aircraft to provide safe separation of aircraft per AFI 13-112 V1, Table A3.2, Task 03.5.1.

3.3.2.9.2. JTC TRS shall enable the trainee(s) to execute procedural control of aircraft to provide safe separation from fires per AFI 13-112 V1, Table A3.2, Task 03.5.2.

3.3.2.10 Execute target marking for CAS assets

JTC TRS shall enable the trainee to conduct target marking.

3.3.2.10.1. JTC TRS shall enable the trainee(s) to execute visual target marking for CAS assets per AFI 13-112 V1 Table A3.2 Task 03.6.1.

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

3.3.2.11 Control weapons during CAS missions in support of the ground scheme of maneuver JTC TRS shall enable the trainee to control the following weapon systems deliveries:

3.3.2.11.1. JTC TRS shall enable the trainee(s) to control laser guided weapon system deliveries per AFI 13-112 V1 Table A3.2 Task 03.9.1., including the capability to specify and match laser Pulse Repetition Frequency (PRF) codes.

3.3.2.11.2. JTC TRS 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.11.3. JTC TRS shall enable the trainee(s) to control coordinate-dependent weapons deliveries per AFI 13-112 V1 Table A3.2 Task 03.9.2.

3.3.2.11.4. JTC TRS shall enable the trainee(s) to control sensor-guided weapons deliveries per AFI 13-112 V1 Table A3.2 Task 03.9.3.

3.3.2.11.5. JTC TRS shall enable the trainee(s) to control non-precision weapons CAS missions per AFI 13-112 V1 Table A3.2 Task 03.10.

3.3.2.12 CAS Missions

3.3.2.12.1. JTC TRS shall fully support the execution phase of CAS missions per AFI

13- 112 V1 Table A3.2 Task 03.

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

3.3.2.12.3. JTC TRS 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.12.4. JTC TRS shall enable the trainee(s) to control day fixed-wing CAS missions per AFI 13-112 V1 Table A3.2 Task 03.11.1.

3.3.2.12.5. JTC TRS shall enable the trainee(s) to control day rotary-wing CAS missions per AFI 13-112 V1 Table A3.2 Task 03.11.2.

3.3.2.12.6. JTC TRS shall enable the trainee(s) to control day ISR/UAS missions per

AFI 13-112 V1 Table A3.2 Task 03.11.3.

3.3.2.12.7. JTC TRS shall enable the trainee(s) to control night fixed-wing CAS missions per AFI 13-112 V1 Table A3.2 Task 03.12.1. (excludes DT and non-HUD

PT)

3.3.2.12.8. JTC TRS shall enable the trainee(s) to control night rotary-wing CAS missions per AFI 13-112 V1 Table A3.2 Task 03.12.2. (excludes DT and non-HUD PT)

3.3.2.12.9. JTC TRS shall enable the trainee(s) to control night ISR/UAS missions per

AFI 13-112 V1 Table A3.2 Task 03.12.3. (excludes DT and non-HUD PT)

3.3.2.12.10. JTC TRS shall enable the trainee(s) to integrate ground-delivered illumination per AFI 13-112 V1 Table A3.2 Task 03.12.4.1.

3.3.2.12.11. JTC TRS shall enable the trainee(s) to control aviation-delivered illumination per AFI 13-112 V1 Table A3.2 Task 03.12.4.2.

3.3.2.12.12. JTC TRS shall enable the trainee(s) to control adverse weather CAS missions per AFI 13-112 V1 Table A3.2 Task 03.13.

3.3.2.12.13. JTC TRS shall enable the trainee(s) to control urban CAS missions per AFI

13-112 V1 Table A3.2 Task 03.14.

3.3.2.12.14. JTC TRS shall enable the trainee(s) to control AC-130 fire missions per AFI

13-112 V1 Table A3.2 Task 03.15.

3.3.2.12.15. JTC TRS shall enable the trainee(s) to execute a CAS mission utilizing a

FAC-A per AFI 13-112 V1 Table 5.1 Task 5.16.

3.3.2.12.16. JTC TRS 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.13 CAS Target Location Methods

JTC TRS 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.14 CAS Communication

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

3.3.2.14.2. JTC TRS shall provide the trainee(s) the capability to provide updated friendly and enemy situation to the aircraft conducting CAS missions.

3.3.3 Call for Fire (CFF) Requirements

JTC TRS 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 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 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

3.3.3.3 Marking

3.3.3.3.1 JTC TRS shall support the employment of indirect fires (artillery, mortars, rocket/missile fire and Naval Surface Fire Support (NSFS)) to provide visual target marking to support a CAS mission.

3.3.3.4 SEAD

JTC TRS 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 shall support illumination missions using the following methods:

d) Grid Method

e) Polar Plot Method

f) Shift from Known Point Method

3.3.3.6 Naval Surface Fire Support (NSFS) Call For Fire

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

g) Grid Method

h) Polar Plot Method

i) Shift from Known Point Method

3.3.3.7 CFF Munitions

JTC TRS 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(s) interactive elements shall correlate and interact with each other to provide a continuous and cohesive virtual environment.

3.4.1 Visual System Requirements

See Appendix G for detailed visual requirements.

3.4.2 Aural Cueing Requirements

3.4.2.1 Audio Cues

3.4.2.1.1 JTC TRS shall provide audio cues for:

a) Friendly personnel (to be treated as indiscernible background noise)

b) Enemy personnel (e.g. shouted commands to be treated as indiscernible background noise)

c) Vehicles

d) Aircraft

e) Detonations

f) Weapons

3.4.2.1.2 All sound effects shall be consistent with distance and direction 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 Doppler Effect

The audio cues shall be representative of the distance, direction and Doppler Effect at the trainee(s); relative to the sources of the audio cue.

3.4.2.3 Audio Correlation

JTC TRS shall correlate audio and visual cues with the synthetic environment 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 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(s).

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 integrrogation had been received.

3.4.3.2 Entity Quantity

3.4.3.2.1 The JTC TRS shall support processing of up to one thousand seven hundred (1700) externally generated simultaneous entities in a networked mode mission training scenario.

3.4.3.2.2 The JTC TRS shall support SAF/CGF generation of any combination of up to one thousand (1000) internally generated simultaneously active entities in a non-networked mission scenario.

3.4.3.2.3 Visual system requirements for display of entities in the JTC TRS fields of view, either networked or non-networked training modes, are identified in Appendix G.

3.4.3.2.4 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(s) Interactive Requirements

3.5.1 Trainee Virtual Interaction

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

3.5.1.2 The trainee(s) must be portrayed as an entity in the threat environment and shall be discernible to other entities in the virtual environment for the trainee(s) 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(s) can be targeted by hostile entities.

3.5.1.4 As an entity, the trainee(s) 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(s) 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(s) shall receive a visual and aural indication from JTC TRS, when he has been injured or destroyed by the enemy or friendly fire.

3.5.1.7 As an entity, the trainee(s) 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 shall provide a 6 Degree of Freedom (DOF) [See Appendix B definition of 6DOF] tracker for all trainee equipment which requires position or orientation tracking (See Appendix C1 & C2, “Tracking Required” column). The DT and PT may use 3DOF.

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

3.5.2.3 The tracker shall be capable of tracking equipment position and orientation relative to the virtual environment without regard to equipment combinations. Individual team member positions relative to each other or the environment are not required to be tracked.

3.5.2.4 Multiple instances of the same piece of equipment shall track separately.

3.5.2.5 JTC TRS shall be capable of tracking positional and a full 360° Angular Range on all axes (X, Y, Z, Pitch, Yaw, Roll) with no restrictions to use of equipment by the trainee(s). The DT and PT my utilize only Pitch, Yaw, and Roll.

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

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

3.5.3 Equipment Management

Simulated and stimulated 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) (e.g.- compass, Infrared Zoom Laser Illuminator Designator (IZLID), M-4 carbine)

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

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

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

3.5.3.3 JTC TRS shall enable use of any equipment combination. Multiple copies of the same device (i.e. two or more binoculars) shall be capable of operating in the system simultaneously and independently without interfering with each other.

(See Appendix C1 & C2, Number Required column).

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(s) Equipment Requirements

3.5.4.1 JTC TRS shall stimulate, emulate, or virtually simulate equipment designated as described in Appendix C1 & C2. Appendix C1 & C2 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 Touch-screen communications equipment displays shall be accompanied by a compatible connector(s) for connection of any style of trainee headset or handset.

The connector shall be appropriate for the radios being emulated. An M55116/1- 03 5-pin connector is an example of a standard connector.

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

3.5.4.3.1 Visualization of selectable resources (as listed in Appendix C1 & C2) shall be displayable on the lower portion of the dome, outside of the trainee’s main field of view.

3.5.4.4 Equipment Cabling

3.5.4.4.1 JTC TRS cabling between the system and trainee(s) equipment shall not:

a) interfere with operation of equipment

b) distract the trainee(s)

c) hinder trainee(s) mobility or ability to perform the mission

3.5.4.4.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.4.3 Radio connections and GPS shall provide virtual, simulated interfaces to support digital CAS over the field computing devices.

3.5.4.4.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.4.5 System will accommodate up to 3 trainees. Cable interfaces shall be allocated to support all possible equipment configurations (per Appendix C1 and C2). Total number of connections shall be sufficient to account for each trainee using multiple pieces of equipment, simultaneously. This requirement can partially be mitigated through use of plug-and-play equipment, which can be swapped out during a live training scenario.

3.5.4.5 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 all student frequencies for active communications.

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

3.6.1.3 Configurable channels, at a minimum, shall consist of:

a) Command Net

b) Command Net (one echelon above)

c) Fire Support Net

d) Tactical Air Direction Net (Strike Primary)

e) Tactical Air Direction Net (Strike Secondary)

f) Tactical Air Coordination Net

g) Air Force (Joint) Air Request Net

h) Tactical Air Control Party Administrative Net

3.6.1.4 Radio frequencies (UHF & VHF) shall be incremental in accordance with Appendix D and be set up to allow scanning, utilizing the same scan function controls seen on the actual radios.

3.6.1.5 Scan function controls shall be incorporated into each radio (see appendix C1 and C2) and accessible to the user(s) in the dome and at the combined workstation.

3.6.1.6 Scan function shall have, at a minimum, the following options

a) List of frequencies to be scanned

b) Priority receive and transmit nets

c) Hang time

d) Hold time

3.6.2 Role-Play

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

3.6.3 Intercom Control Management

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

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

3.6.3.3 JTC TRS shall provide the capability of conducting tactical chat between the trainee, IOS, PSC, MVP and Instructor Station over DMO networks to interface with distributed training entities such as an ASOC.

3.7 Instructor/Operator Station (IOS) Requirements

3.7.1 General IOS Requirements

JTC TRS 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 simulation system (e.g., private instructor to trainee(s) communication capability, allow instructor to observe trainee(s)).

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 30 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 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 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 shall be capable of storing a minimum of 50 scenarios.

3.7.2.1.4 The IOS shall have the capability to create routes for entity movement.

Streets shall be displayed utilizing technology similar to “OpenStreetMap” allowing users ability to attach entities to entire route on streets/roads.

3.7.2.1.5 The IOS shall provide the capability for the Virtual Reality Scene Generator

(VRSG) Remote to default to the master entity when scenarios are opened.

3.7.2.2 Scenario File Transportability

3.7.2.2.1 The IOS shall allow for transfer of scenario data to or from other JTC

TRS 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 other JTC TRS systems and other compatible training systems.

3.7.2.3.1 JTC TRS 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 shall provide the capability to conduct secure and private communications with other 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(s)’ 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(s) has been destroyed by the enemy or fratricide.

3.7.3.1.8 The IOS shall have the capability to degrade/jam user’s GPS signals to simulate a Contested Degraded Operationally Limited Operations (CDO) environment. The IOS shall provide the following GPS settings:

a) Magnitude (distance in meters)

b) Direction (angle in degrees)

The IOS shall provide adjustment to 1 meter and 1 degree granularity

3.7.3.1.9 The IOS shall have the capability to add digital and analog noise/interference to the ROVER feed without affecting other VRSG channels. The IOS shall provide two noise modes:

a) Auto noise: Noise levels to be determined by line of sight

(LOS) considerations and impacted by distance to source signal and atmospheric effects

b) b) Instructor selected noise: A slider selection to determine level of noise – 0% to 100%

3.7.3.1.10 The IOS shall have the capability to replicate a Synthetic Aperture

Radar (SAR) picture based on aircraft selected. The SAR picture shall be realistic and include selectable map sizes typical of the selected aircraft.

3.7.3.1.11 The IOS shall have the capability to modify the MVP ROVER visual spectrum to night vision without changing either of the student station ROVER visual spectrums. Night vision helps instructors track student training tasks but would provide negative training to students; night vision is not a real world capability of the ROVER.

3.7.3.2 Virtual Scene Interaction

3.7.3.2.1 The IOS shall be able to position the trainee(s) at any location in the virtual environment and display the scene on the trainee(s) 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.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 shall provide changing environmental effects to the visual scene and entities during a scenario so that the trainee(s) 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 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 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 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(s) 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(s) 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 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 JTC 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) Variable-speed 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.7.6 JTAC Instructor Station:

The following sections become applicable when the respective CLIN(s) have been awarded, until then they are not included within the performance of this contract.

3.7.6.1 The JTAC Instructor Station shall consist of at least two display screens connected to a computational system. One of the display screens shall consist of a touchscreen monitor.

3.7.6.2 One JTAC Instructor Station display screen shall display a mirror of the JTAC's

DAGR GPS.

3.7.6.3 One JTAC Instructor Station…