11 a Digital Training Range System (DRTS) Perf Spec PRF-PT-768.pdf

PRF-PT- 768

CAGE 57039

Version 1.0 3 December 2021

DIGITAL RANGE TRAINING SYSTEMS (DRTS)

PERFORMANCE SPECIFICATION

U.S. Army Program Executive Office for

Simulation, Training and Instrumentation (PEO STRI)

12211 Science Drive

Orlando, FL 32826-3276

Engineering:

Prepared By: ____________________ Concurrence: ______________

Nicole Steib James Todd

Systems Engineer, PdM LTS Chief Engineer, PdM LTS, FOT

Distribution Statement A:

Approved for Public Release, Distribution is Unlimited

Version 1.0 3 December 2021 ii

Revision History

Date Version Author Paragraph Revision Description 3 Dec 2021 1.0 DRTS Team All New DRTS Specification

Version 1.0 iii

TABLE OF CONTENTS

1. Digital Range Training Systems (DRTS)

1.1. Scope

1.2. Overview

2. Applicable Documents

2.1. Government Regulations, Directives, and Instructions

2.2. Military Specifications, Standards, and Handbooks

2.3. Other Government Documents

2.4. Non-Government Standards and Publications

3. Requirements

3.1. General Performance

Systems Start, Shut Down and Restart Requirements Scalability Availability

3.2. Control Tower

General Design Considerations Control Tower (CT) System Performance Exercise Management Video System Suite (VSS) Ingest Workstation (WS) Hand-Held Target Control Function Scenario Development Tool (SDT) Range Data Editor (RDE)

3.3. AAR Facility

AAR Presentation Workstation (PWS) Podium Theater Audiovisual Equipment

3.4. Field Support Equipment (FSE)

3.5. Target System

Targetry System (TS) General Target Types Battlefield Effects Simulators (BES)

3.6. AWSS

3.7. Field Cameras

Field Cameras General Field Cameras Control

3.8. Player Units (PU)

PU Coverage Area

3.9. Range Digital Communications System (RDCS)

Version 1.0 iv

RDCS Architecture RDCS Network RDCS Network Controller RDCS Network Administration Network Management RDCS PU Administration Global Positioning System (GPS) Reference Receiver RDCS Time base RDCS Coverage Area

Range Digital Communications System (RDCS) Capacity Transmission Rate Transmission/Reception Update and Reporting Rates Voice & Data Communications Interface (VDCI) Video Telemetry Priority Assignment Talk Groups or Sub-Nets Commercial Net Relays Interfaces

3.10. Firmware

3.11. Electromagnetic Compatibility (EMC)

Electromagnetic Environmental Effects (E3) Intra-system EMC Inter-system EMC Electromagnetic Radiation Hazards (EMRADHAZ) Non-Developmental Items (NDI) and Commercial Items Life cycle, E3 Hardness

3.12. Cybersecurity (CS)

3.13. Security

System Access Portable Electronic Devices (PEDS)

3.14. System Safety

Environmental Safety Electrical Safety Hazardous Materials Personnel Safety Mechanical Safety Antenna Safety Battery Box Design Safety Electronic and System Protection Environmental Outdoor Conditions

Version 1.0 v

3.15. Logistics

Maintenance Concept

3.16. Facilities

3.17. Reliability

3.18. Maintainability

3.19. Human Engineering

4. Verification

4.1. DRTS General Performance Requirements

Systems Start, Shut Down and Restart Requirements Scalability Availability

4.2. Control Tower

General Design Considerations Control Tower System Performance Exercise Management Video System Suite (VSS) Ingest Workstation (WS) Hand-Held Target Control Function Scenario Development Tool (SDT) Range Data Editor (RDE)

4.3. AAR Facility

AAR Presentation Workstation (PWS) Podium Theater Audiovisual Equipment

4.4. Field Support Equipment (FSE)

4.5. Target System

Targetry System (TS) General Target Types Battlefield Effects Simulators (BES)

4.6. AWSS

4.7. Field Cameras

Field Cameras General Field Cameras Control

4.8. Player Units (PU)

PU Coverage Area

4.9. Range Digital Communications System (RDCS)

RDCS Architecture RDCS Network RDCS Network Controller RDCS Network Administration Network Management RDCS PU Administration

Version 1.0 vi

Global Positioning System (GPS) Reference Receiver RDCS Time base RDCS Coverage Area

Range Digital Communications System (RDCS) Capacity Transmission Rate Transmission/Reception Update and Reporting Rates Voice & Data Communications Interface (VDCI) Video Telemetry Priority Assignment Talk Groups or Sub-Nets Commercial Net Relays Interfaces

4.10. Firmware

4.11. Electromagnetic Compatibility (EMC)

Electromagnetic Environmental Effects (E3) Intra-System EMC Inter-System EMC Electromagnetic Radiation Hazards (EMRADHAZ) Non-Developmental Items (NDI) and Commercial Items Life Cycle, E3 Hardness

4.12. Cybersecurity (CS)

4.13. Security

System Access Portable Electronic Devices (PEDS)

4.14. System Safety

Environmental Safety Electrical Safety Hazardous Materials Personnel Safety Mechanical Safety Antenna Safety Battery Box Design Safety Electronic and System Protection Environmental Indoor HVAC Controlled Facility Conditions Outdoor Conditions

4.15. Logistics

Maintenance Concept

4.16. Facilities

4.17. Reliability

4.18. Maintainability

Version 1.0 vii

4.19. Human Engineering

APPENDIX A : DRTS Diagram APPENDIX B : Abbreviations and Acronyms

Version 1.0

1. DIGITAL RANGE TRAINING SYSTEMS (DRTS)

The Digital Range Training System (DRTS) provides advanced instrumentation specifically required for live fire gunnery training and qualification with the Abrams, Bradley, Stryker and Apache Aircraft on larger mounted maneuver Instrumented “Digital” Ranges. DRTS provides crew, section, platoon and company training and qualification capabilities above and beyond any other range in the Army inventory.

Dismounted Tracker (DMT) provides situational awareness during section, platoon, and company training to track movement of troops on ground on the entire range complex.

These ranges interface with the tactical vehicles through an Integrated Player Unit Recorder (IPUR) or Smart Onboard Data Interface Module (SMODIM) to provide both real-time feedback to leaders and rapid development of complete After Action Reviews (AARs) and Take Home Packages (THPs). These AAR and THPs include synchronized Thru-Sight Video (TSV) from the Commander/Gunner sights, crew camera video from inside the vehicles, thermal field camera video from the range cameras and internal crew audio for a complete evaluation tool. Ten of these DRTS ranges also incorporate Aerial Weapons Scoring System (AWSS) to interface with Aviation and Unmanned Aerial System gunnery training and qualification in a similar manner. The five standard training ranges identified utilize all available combat systems capabilities and digitally integrate them to manage all forces undergoing crew through collective live-fire training and qualification: Digital Multi-Purpose Range Complex (DMPRC) supports all gunnery tables and Combined Arms Live Fire Exercise (CALFEX) for Armor, Infantry and Aviation; Digital Multi-Purpose Training Range (DMPTR) supports crew and section qualification for Armor and Infantry; Battle Area Complex (BAX) supports crew through company CALFEX for Stryker & Infantry Brigade Combat Team (SBCT/IBCT); Digital Air Ground Integration Range (DAGIR) supports all gunnery tables and CALFEX for Armor, Infantry and Aviation platforms; Aerial Gunnery Range (AGR) at Fort Bragg supports crew through Company CALFEX for manned/unmanned aviation platforms.

To provide the necessary Aviation gunnery training with Instrumented Range capabilities, the DRTS can be fully integrated with Aerial Weapon Scoring System (AWSS) and the Aviation player unit to support Aviation units on a DAGIR. Other Instrumented Ranges (IR) / DRTS Range types may also support integration with the portable AWSS and Aviation player units in support of Aviation gunnery. DRTS will have the embedded capability to provide a gateway to the Constructive and Virtual training environments.

The DRTS is a product of the Live Training Transformation (LT2) family. The LT2 Product Line is a "Family of Systems" utilizing the Common Training Instrumentation Architecture (CTIA) Compliant Components. The common components include standard interfaces to Virtual and Constructive simulation systems, Army Battle Command Systems (ABCS), Army Training Information Architecture (ATIA), targetry systems, and other training systems that require interoperability with LT2 Product Line systems. CTIA provides reusable components to implement a common Objective

Version 1.0

Instrumentation System (OIS) for the Maneuver Combat Training Centers (MCTC) home-station training, Integrated Military Operations on Urbanized Terrain (MOUT) Training System (I-MTS) facilities, and the IR / DRTS.

1.1. SCOPE

This specification establishes the performance and validation requirements for the DRTS program. The requirements include the following major components:

a. Control Tower (CT)

b. After Action Review (AAR)

c. Integrated Player Unit Recorder (IPUR)

d. Target Systems

e. Aerial Weapons Scoring System (AWSS)

f. Exterior Video Cameras

g. Aviation

h. Range communications for voice and data transmissions

i. Battlefield Effects Simulators (BES)

j. Single Channel Ground-Air Radio System (SINCGARS)

k. Blue Force Tracker (BFT)

1.2. OVERVIEW

DRTS provides real time monitoring, data collection, analysis, and review. Data shall be collected while monitoring, controlling, and recording the Force on Target (FOT) engagements that occur in the battlefield environment. The DRTS gateway to the constructive and virtual world shall be through the Common Training Instrumentation Architecture (CTIA). The following DRTS ranges are defined in the Department of the Army Training Circular (TC) 25-8. Training Range.

a. Digital Multi-Purpose Range Complex (DMPRC)

b. Digital Multi-Purpose Training Range (DMPTR)

c. Battle Area Complex (BAX)

d. Digital Air/Ground Integration Range (DAGIR)

e. Aerial Gunnery Range (AGR)

This product line of instrumented ranges provides enhanced training data collection for AAR, utilization of interfaces compliant with the CTIA, and Future Army System of Integrated Targets (FASIT) to represent realistic threats.

2. APPLICABLE DOCUMENTS

In the event of a conflict between documents referenced herein and the contents of this Performance Specification, the contents of this Performance Specification shall be the governing requirement.

2.1. GOVERNMENT REGULATIONS, DIRECTIVES, AND INSTRUCTIONS

Document Number Document Title Army Regulation 25-2 Cybersecurity (CS)

Version 1.0

09-EC-M-0010 Wireless Security Standards, Version 3.0, 2 January 2009

DODD 5000.1 The Defense Acquisition System DODI 8510.01 Risk Management Framework (RMF) for

Department of Defense (DOD) Information Technology (IT)

Table 1: Government Documents

2.2. MILITARY SPECIFICATIONS, STANDARDS, AND HANDBOOKS

The following specifications, standards, and handbooks form a part of this document to the extent specified herein.

Number Title MIL-STD-188/220 Digital Message Transfer Device Subsystems MIL-STD-810G Environmental Engineering Considerations And

Laboratory Tests MIL-STD-461 Requirements for Control of Electromagnetic Interference

Characteristics of Subsystems and equipment MIL-STD-1275 DOD Characteristics of 28 Volt DC Electrical systems in military vehicles MIL-STD-1472G DOD Design Criteria Standard: Human Engineering MIL-STD-1474 Noise Limits MIL-STD-1553 Digital Time Division Command/Response Multiplex Data

Bus MIL-STD-2301 Computer Graphics Metafile (CGM) Implementation

Standard MIL-STD-2401 DOD Standard Practice, World Geodetic System (WGS

84) MIL-STD-2525 Military Symbology

CEHNDM 1110-1 Army Corps of Engineers Design Manual

Table 2: Specifications, Standards and Handbooks

2.3. OTHER GOVERNMENT DOCUMENTS

The following other Government documents, drawings, and publications form a part of this specification to the extent specified herein.

Document Number Document Title PRF-PT-769 Visual System Suite (VSS) Performance Specification PRF-PT-765 Integrated Player Unit Recorder Specification LT2 Publication Version 3.0

Video Live Training Transformation (LT2) Service Oriented Architecture (SOA) Interface Control Document

(ICD)

PRF-PT-00468 FASIT Performance Specification http://164.214.2.59/publications/specs/printed/2401/2401.pdf

Version 1.0

ICD.FASIT.SYS FASIT System Devices Interface Control Document ICD.FASIT.AUDIO FASIT Audio Devices Interface Control Document ICD.FASIT.PD FASIT Presentation Devices Interface Control Document ICD.FASIT.PYRO FASIT Pyrotechnic Device Interface Control Document

DMPRC-HOOD-BES-

TARGET-ICD

BES Target Interface Control Document

PRF-PT-767 Dismounted Tracker (DMT) Performance Specification PRF-PT00588 Interface Standard for the Multi-Function Vehicle Port

(MFVP)

ICD SA16575 Independent Thermal Viewer (CITV) (Abrams) ICD 19200-12956704 Improved Bradley Acquisition Subsystem (IBAS)

Commander’s Independent Viewer (CIV) (Bradley) ICD 12991282(A) Second Generation Forward Looking Infrared Radar (2nd

Generation FLIR)

ICD SA16575

Gunner’s Primary Sight-Line of Sight (GPS-LoS) captured through the Gunner’s Primary Sight Extension (GPSE) on the Abrams

TM-VPU-1553-IDD Player Unit Interface Design Document (IDD) for the Tactical Micro Player Unit 1553 Interface, version 1, 11 Nov 13

809194SW-2-IDD Interface Design Description, Scoring User Control, AWSS

809200SW-2-IDD Interface Design Description, Scoring Service Client, AWSS

TC 3-04.3 Aviation Gunnery (None) DRTS System Security Plan (SSP) Operational Requirements Document (ORD), dated 27 Sept

Digital Multi-Purpose Range Complex (DMPRC)

Table 3: Other Government Documents

2.4. NON-GOVERNMENT STANDARDS AND PUBLICATIONS

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

Standard Number Standard Title 29 CFR 1910 Occupational Safety and Health Standards ATA 300 Specification for Container Requirements ANSI/NFPA 70-2002 National Fire Protection Association’s National Electrical

Code IEEE-1394 IEEE Standard for a High Performance Serial Bus FIPS 140-2 Security Requirements for Cryptographic Modules FPA

70-2001 NEMA 12 OR 13 National Electrical Manufacturers Association ratings for enclosures http://www.access.gpo.gov/nara/cfr/waisidx_01/29cfr1910_01.html http://standards.ieee.org/index.html

Version 1.0

Table 4: Non-Government Standards and Publications Copies of specifications, standards, and drawings may be obtained as directed by the Contracting Officer (PCO).

3. REQUIREMENTS

3.1. GENERAL PERFORMANCE

This specification provides the performance requirements applicable to the complete DRTS. The DRTS shall be comprised of the appropriate hardware and software elements required to fulfill the requirements of this specification. The requirements for the Visual System Suite (VSS) and the Player Units (IPUR and DMT) are provided in sub-ordinate specifications as referenced in this document. Throughout this document whenever the term Player Unit (PU) is used it includes both the IPUR and DMT.

SYSTEMS START, SHUT DOWN AND RESTART REQUIREMENTS

The System Start, Shut Down, and Restart requirements shall apply to components installed in the CT, to include Aerial Weapons Scoring System (AWSS) Control Station Subsystem (CSS), DRTS servers, Communications Systems (i.e. ClearCom, SINCGARS), SYSCON WSs, EXCON WSs, and any other evaluation room workstation (i.e. EDC), as well as After Action Review (AAR) components to include the Podium workstations (PWS), Take-Home Package WS, and CMUR Ingest WS.

SYSTEM STARTUP AND RESTART

System startup refers to the start of the system or system components from a completely powered down condition to the last saved configuration. The restart process shall restore the system to the same functional condition prior to system restart. The DRTS shall:

a. Provide a full system startup of all components referenced in section 3.1.1 to include hardware (HW) and Operating System (OS).

b. Have the capability to be in a full operational state (systems and sub systems) in 30 minutes or less from full system start.

c. Have an Auto Start capability that enables all CT and AAR Building components to power up from a single location.

d. Start all server and WS applications within 20 minutes from full system start up.

e. Have all WSs ready for use in 1 minute or less from full system startup.

f. Include all sub-system infrastructure as part of the startup process (i.e.

IPUR, DMT, UAS, Field Cameras infrastructure).

Note: The individual DRTS Sub-Systems listed under 3.1.1.1f will be manually powered on.

SYSTEM SHUTDOWN

The DRTS shall:

Version 1.0

a. Provide an orderly shutdown of all systems referenced in section 3.1.1.

b. Have an Auto Shutdown capability that enables all CT and AAR Building components to power down from a single location.

c. Attain a powered-off condition within 20 minutes.

d. Not lose any database or configuration data when a shutdown is performed.

SCALABILITY

The DRTS shall be implemented in a modular and scalable manner to support the Department of the Army Training Circular (TC) 25-8 Training Range doctrine on the following range types/configurations:

a. Digital Multi-Purpose Range Complex (DMPRC).

b. Digital Multi-Purpose Training Range (DMPTR).

c. Battle Area Complex (BAX).

d. Digital Air/Ground Integration Range (DAGIR).

e. Aerial Gunnery Range (AGR).

The modular implementation shall maximize common component reuse across the configurations and allow for scalable components additions to achieve range configuration capabilities.

AVAILABILITY

The DRTS shall:

a. Achieve an operational availability of 99%.

b. Operate continuously for 22 days without a system restart.

c. Enable main servers to be re-cycled after the 11th consecutive day of operation with either all data flushed or with no data loss.

d. Sustain data due to loss of power, environmental control, or weather within the 11-day cycle.

3.2. CONTROL TOWER

GENERAL DESIGN CONSIDERATIONS

The DRTS shall:

a. Utilize the Government Furnished Information (GFI) SW.

b. Utilize CTIA, LT2 Product Line components, and commercial products.

c. Minimize specially developed SW or HW.

d. Have visual SW displays that conform to the CTIA Common Graphical User

Interface (GUI) Style Guide and Framework.

e. Provide access to menus, icons, and other GUI devices through a pointing device and the keyboard ("hot keys" and function keys).

f. Have visual displays with scroll bars, zoom, or drag hands to ensure all displayed data is viewable.

g. Have operator error messages, which include the nature of the error, the correction method, and the name of the packages/object that generated the message.

Version 1.0

h. Display formatting text tips to augment operator's understanding of displays;

for example, displaying data constraints, format, and units when pointer is over the field.

i. Integrate displays through menus, icons, buttons, and other GUI devices.

j. Have adjustable displays with operator palette control.

k. Have default palettes that are recoverable.

l. Have palettes (colors) annotated in the application such as standard colors for icons, symbology, event depiction, and other effects.

m. Be capable of saving application configuration changes as preferences and recovering those preferences for later use.

n. Have non-destructive display windows (i.e. the opening of an application shall not force the abnormal end of a running application).

o. Have the capability to overlap displays without corrupting data (e.g. closing a window shall automatically restore the underlying display.)

p. Refresh displays within 1 second.

q. Display Security Classification, date, and time at all times.

r. Allow operators the option of displaying exercise time (time since start of exercise) and one of the following: local time, Coordinated Universal Time (UTC), or Greenwich Mean Time (GMT).

s. Allow the time format be selectable at any time.

t. Ensure the time in the system is traceable to UTC (GPS) or UTC maintained by the U.S. Naval Observatory.

u. Have all servers and WSs compliant with the current DRTS Security Plan

(SSP).

CONTROL TOWER (CT) SYSTEM PERFORMANCE

The DRTS CT shall:

a. Be equipped to conduct exercises at that fixed location.

b. Enable all WSs the capability of executing all required CT SW and functionality.

c. Include all the servers and WS required to support the GFI DRTS SW.

d. Provide a 50% spare CPU and memory capacity for servers and WS.

e. Be in a network controller and relay environment.

f. Contain all equipment required for hosting the CT database including, AWSS CSS Real Time Processes (RTP), Aviation Data Translators (ADT), logging of exercise data, interfacing range components to the Range Digital Communications System (RDCS), the technical operations, maintenance SW, video/audio recording, and playback.

g. Enable each WS to have the capability to create and read commonly available removable media (e.g. CD-R, CD-RW, and DVD-RW).

h. Utilize media via industry standard parallel or serial interfaces (i.e. Small Computer Systems Interface (SCSI), Fire Wire (IEEE1394), and Universal Serial Bus (USB)).

i. Ensure each WS has the necessary user input and display devices required to operate.

http://www.greenwichmeantime.com/ http://www.t10.org/

Version 1.0

j. Ensure all WSs and associated equipment shall support system security controls.

k. Include headsets and distribution equipment for communicating with other WSs and radio systems.

l. Provide access to tactical/administrative radio systems via the WSs.

m. Include monitors capable of displaying the exercise area (4km x 6km for

DMPRC and 2.5km x 5km for other DRTS range types) 1:25,000 Arc Digitized Raster Graphics (ADRG) map at a 2.5X zoom-in.

n. Provide graphics cards capable of 3D graphics (e.g. rendering, texturing, and Z-buffering) using Commercial Off-The-Shelf (COTS) graphics formats (e.g. DirectX, OpenGL).

o. Enable back-up and archival of data (Hard Drive or CD).

p. Include printer(s) for graphics and text printout in black-and-white and color.

q. Include a Weather Station capable of showing the Barometric Pressure, Wind Speed, Air Temperature, & Wind Direction.

r. Integrate the BFT/BFT2 and MIL-STD-188/220 or satellite terminals.

s. Provide the ability to interface with SINCGARS voice and Push-To-Talk

(PTT) distribution.

t. Include a separate Uninterruptible Power Supplies (UPS) for all equipment or a single UPS with power conditioning as the source of all equipment power.

u. Provide a UPS with enough backup power to execute an orderly power shutdown. (Orderly power shutdown is defined as successful if all data and states are saved as well as successful resumption of the training scenario from the point it was halted due to the loss of power.)

v. Provide the Audio/Video interfaces necessary to ingest aircraft recorded audio and video from the Aviation Workstation (AWS) for AAR.

WORKSTATIONS (WS)

The DRTS WSs shall:

a. Control and manage the DRTS components (i.e. FC, Targets).

b. Be configurable as a Technical Operations and Maintenance Control

(TOMC) WS.

c. Be configurable as a Range Safety Officer (RSO) WS.

d. Be configurable as a System Control (SYSCON) WS.

e. Be configurable as a Crew Evaluator WS (CEWS).

f. Be configurable as a Presentation WS (PWS).

g. Be configurable as a Take Home Package (THP) WS.

h. Be configurable as a CMUR Ingest WS.

i. Be configurable as an Aviation WS (AWS).

j. Be configurable to connect with interface devices such as mouse, keyboard, and joysticks at the WS desks.

OPERATIONAL MODE

The DRTS CT shall:

Version 1.0

a. Be modular and expandable.

b. Support a free maneuver area.

c. Operate continuously for 22 days.

d. Support a battalion training cycle.

e. Operate with 1 range configuration/maintenance day after the 11th day permitted.

f. Support system restart due to loss of power, environmental control, or weather with no data loss.

g. Support both ground and aviation training events.

h. Support communications between the CT and PUs within the range maneuver space.

i. Provide an operator workspace designed for comfort and safety based on a continuous 12-hour period of operation.

SYSTEM CONTROL (SYSCON)

The SYSCON WS shall:

a. Support preparation of exercises.

b. Include the VSS Application.

c. Control and manage the DRTS SW.

d. Distribute, confirm distribution, and log Range Operations SW versions in use at the start of an exercise.

e. Load schema and table structures used for the database.

f. Initialize the default configuration database for an exercise.

g. View and copy configuration data from previous exercises.

h. Log all operator and automatic actions for subsequent review (i.e. login name and SW accessed).

PLAYER ADMINISTRATION

The SYSCON shall:

a. Create Individual PU configuration data for each exercise.

b. Control and manage the PU Instrumentation, targets, and players.

c. Keep the configuration data generated for a PU specific to that PU.

d. Modify PU operating modes (e.g. sleep, power management, position update rates) by individual or logical groups of PU.

e. Administratively kill (target down) individual or logical groups of PU.

f. Administratively reset individual or logical groups of PU.

g. Administratively reload individual or logical groups of PU.

h. Administratively resurrect (target up) individual or logical groups of PU.

i. Transmit any command event to a PU.

j. Maintain a count of all player events by player.

k. Report missing events.

l. Initiate verification data for all PU components.

m. Log configuration data for all PU components.

n. Generate player configuration data.

o. Clear player configuration data.

Version 1.0

p. Load configuration data via the Field Support Equipment (FSE) or transmitted via the RDCS to connected devices.

q. Generate Ground PU Configuration data.

r. Generate Aviation PU Configuration data.

EXERCISE ADMINISTRATION

The SYSCON shall:

a. Provide an application for the control and management of each exercise.

b. Initialize an exercise.

c. Reset/re-initialize an exercise.

d. Recover archived databases.

e. Initialize the database.

f. Initialize WSs with the data needed to conduct exercises.

g. Assign exercise control permissions (e.g. application, data, role (Force), PU control, etc.).

h. Confirm and establish exercise specific login and WS configurations.

i. Assign operator access to specific voice channels.

j. Provide a summary system status from other management applications.

k. Administratively kill all Instrumented Ranges (IR) controlled players in an exercise.

l. Administratively reset all IR controlled players in an exercise.

m. Administratively reload all IR controlled players in an exercise.

n. Administratively resurrect all IR controlled players in an exercise.

o. Start exercises.

p. End exercises.

q. Archive databases after the corresponding AAR for subsequent reuse.

r. Archive voice and video after the corresponding AAR for subsequent reuse.

s. Provide sufficient capacity to maintain archive until 24-hours after the run is set to AAR complete.

PLAYER CONFIGURATION

Individual player configuration data shall be created for each exercise. Configuration data generated for a player shall be specific to that player. The player configuration shall include provision for replacement players.

TECHNICAL OPERATIONS AND MAINTENANCE CONSOLE (TOMC)

FUNCTION

3.2.2.7.1. SYSTEM ADMINISTRATION

The TOMC shall:

a. Provide tools for the management of all subsystems.

b. Provide tools for the management of the Local Area Network (LAN)

c. Provide tools for the management of any external networks that may be attached to the CT.

Version 1.0

d. Use a distributed-management protocol to enable the control of managed devices.

e. Provide the tools to configure the digital network (LAN).

f. Provide the tools to maintain the digital network (LAN).

g. Provide network management using Bilingual Simple Network Management

Protocol (SNMP) with user-defined security as specified in the Joint Technical Architecture – Army (JTA-A).

h. Provide a system diagnostic display capability that provides system status for each component.

i. Provide a system diagnostic display capability that is operational whenever the system is powered on.

j. Monitor system level performance.

k. Monitor subsystem level performance.

l. Monitor HW component level performance.

m. Monitor the LAN status.

n. Report LAN anomalies to the operator.

o. Detect instrumentation failures.

p. Detect equipment failures.

q. Report instrumentation failures.

r. Report equipment failures.

s. Monitor the voice communications networks.

t. Initialize the Tactical Voice and Tactical Data, assign nets, and configure the selection menus for the WSs.

u. Initialize the Administrative Voice network. Assign nets, set-up recorders, and configure the selection menus for the WSs.

v. Provide GPS synchronized real time to all WSs.

w. Provide an interface to a meteorological station.

x. Provide an interface to administer the station.

y. Provide the tools and equipment necessary for the archival and restoration of exercise files.

z. Provide the tools and equipment necessary for the archival and restoration of manage servers.

aa. Provide the tools and equipment necessary to manage databases.

bb. Provide the tools and equipment necessary to manage the mounted PU database.

cc. Provide the tools and equipment necessary to manage the dismounted PU database.

dd. Provide the tools and equipment necessary to perform a system checkout in preparation for an exercise.

ee. Provide the tools necessary to create and provide Configuration

Management (CM) of all installed SW.

ff. Provide the tools necessary to create and provide CM of all scenarios.

gg. Provide the tools necessary to create and provide CM of all scripts.

hh. Provide the tools necessary to create and provide CM of all configuration data.

Version 1.0

ii. Provide the capability to monitor the communications data quality.

jj. Provide the capability to achieve reliable communication information transfer with at least 95% first time message transmissions.

kk. Provide the Element Management System (EMS) SW to enable control of the DMTs as described in the DMT Specification PRF-PT-767.

3.2.2.7.2. SYSTEM DIAGNOSTIC STATUS DISPLAY CAPABILITY (SDSD)

The SDSD shall:

a. Perform Built-In Test (BIT) during startup or when requested.

b. Perform continuous status testing of system components.

c. Display the updated status.

d. Provide status information pages.

e. Maintain a minimum 22-day historical record of diagnostic data.

f. Perform complete system checks within 10 minutes.

3.2.2.7.3. SDSD HOME PAGE

The SDSD Home Page shall provide access to status pages for:

a. Servers Status (SVRS) Page.

b. SW Status (SWS) Page.

c. Network Component (NC) Page.

d. System Interfaces Status (IS) Page.

e. Alarm Status (ALRMS) Page.

f. Boot-up Status (BTS) Page.

g. Stream Status (STRMS) Page.

h. BIT Page.

3.2.2.7.4. SDSD HOME PAGE CONTENT

The SDSD Status Page for each system identified above shall:

a. Provide access to each of the status pages.

b. Provide one of the following status states for that component:

1. Status State #1: All items are in working order.

2. Status State #2: One or more items are not in working order.

3.2.2.7.5. STATUS PAGE CONTENTS

The Status Pages for each component shall:

a. Provide the summary status of each component.

b. Provide the summary status of each sub-component.

c. Provide access to each of detailed status pages.

d. Provide a summary status indication for the components and sub-components:

1. Status State #1: All items are in working order.

2. Status State #2: One or more items are not in working order.

e. Provide access back to the main parent page.

f. Provide return to last viewed diagnostic page.

Version 1.0

g. Set parameters for Alerts or Alarms.

3.2.2.7.6. SERVERS (SVRS) STATUS PAGE

The individual SVRS Status Page shall provide:

a. Server overall HW status.

b. Server memory status.

c. Server disk status.

d. Server operating system status.

e. Server application SW status.

f. Server application SW version.

g. Detailed error report for failed HW.

3.2.2.7.7. SOFTWARE STATUS (SWS) PAGE

The SWS Page shall provide:

a. The status of each the system SW application component.

b. Access to each of the individual SWS SDSD pages.

c. The SW version of each VSS Computer Software Configuration Item

(CSCI).

d. The detailed error report for any failed CSCI.

e. The detailed error report for any failed Computer Software Component

(CSC).

f. The detailed error report for any failed Computer Software Unit (CSU).

3.2.2.7.8. NETWORK COMPONENTS (NC) STATUS PAGE

The NC Status Page shall provide:

a. Overall HW status.

b. Memory status.

3.2.2.7.9. SYSTEM INTERFACES STATUS (SIS) PAGE

The SIS Page shall provide information on:

a. Field Cameras (individual cameras).

b. Targets System (as a unit not for individual targets).

c. Ground and Aviation Player Unit Systems (as a unit not for individual PU).

d. Weather Station.

e. Video System.

f. Other main components.

g. AWSS subsystems.

h. Battlefield Effects Simulators (BES).

i. The SIS Status Page shall provide:

1. Overall HW status.

2. Interface status.

3. Memory status.

4. Disk status.

5. Operating system status.

6. Application SW status.

Version 1.0

7. Other information as applicable to the specific external interfaces.

3.2.2.7.10. ALARMS STATUS PAGE

The Alarms Status Page shall:

a. Monitor the alarms diagnostic display capability.

b. Provide an updated status when the following occurs:

1. Equipment failure (HW – servers, client, storage device, server, each HW component of System).

2. Interface failure (external systems, Client, and Server).

3. SW process failure.

4. Video and Audio Stream recording failure.

5. Video and Audio Stream playback failure.

6. Network failure.

7. Audio and Video storage capacity.

8. Time and date of failure.

c. Have the capability to review lower level detail information.

d. Have the capability to perform the following actions:

1. Acknowledge.

2. Set.

3. Reset/Clear.

4. Inhibit.

e. Have a 22-day minimum historical record of system alarms.

3.2.2.7.11. BOOT-UP STATUS PAGE

The Boot-up Status Page shall provide a startup check and status report for all of the following:

a. Servers.

b. WS.

c. External interfaces.

d. AWSS sensors and CSS Server.

e. Aviation PU Relay Base Stations processor.

f. PUs.

3.2.2.7.12. STREAM STATUS (STRMS) PAGE

The STRMS Page shall:

a. Display the source name of the stream source.

b. Provide indication/visual notification for any stream source with a failure.

c. Display the status of each active stream source.

3.2.2.7.13. BUILT-IN TEST (BIT)

The BIT capability shall:

a. Enable IPURs to report their ID when entering the network.

b. Have the ability to be initiated by the IPUR.

c. Have the ability to be initiated remotely from the SYSCON.

d. Have the ability to be initiated by the FSE laptop/computers.

Version 1.0

e. Be able to continuously monitor the status of the communications relays and communications links.

f. Provide the means of determining the functional status of the subsystems down to the Line Replaceable Unit (LRU).

g. Provide the means of displaying the functional status of the subsystems down to the LRU.

h. Provide controls and readout reports that they can be easily used and interpreted by the range and maintenance personnel.

i. Provide SW applications that perform BIT and fault isolation functions that do not cause failure of PU functions.

j. Provide the ability to monitor switches system performance that are not placed in series paths for purposes of introducing stimuli, diverting normal signals.

k. Identify power supply faults to the failed power supply.

l. Isolate 75% of all Circuit Card Assembly (CCA) faults no more than 1 CCA.

m. Isolate 90% of all CCA faults to no more than 2 CCAs.

n. Isolate 100% of all CCA faults to no more than 3 CCAs.

o. Utilize diagnostic routines, procedures, test units, and other means from the vendor to isolate the faulty HW to the LRU, upon indication of failures of COTS equipment.

p. Provide results, limited to what the PU provides for BIT and status reports, when initiated from the FSE and CT.

MAPPING ADMINISTRATION

A mapping administration function shall:

a. Provide the capability to maintain terrain databases for the generation and printing of maps, Situational Awareness Window (SAW) 2D, and AARs.

b. Combine map files (e.g. elevation, features, and lines of communication).

c. Scale, scanned or digital products such as photos, drawings, plot plans, and photographic views.

d. Register scanned or digital products such as photos, drawings, plot plans, and photographic views.

e. Overlay scanned or digital products such as photos, drawings, plot plans, and photographic views.

f. Provide edit capability for terrain databases.

g. Allow overlay of terrain elevation data with digitized data from imagery sources.

h. Provide a graphics overlay editor capable of ground and aviation graphics such as air corridors and waypoints.

DATABASE ADMINISTRATION

Database Administration shall include:

a. A CTIA compliant database with management and development tools.

b. All tables necessary to support specific Range Operations.

c. All tables necessary to support scoring.

Version 1.0

d. All tables necessary to support aviation SW functions.

e. WS configurations.

f. Instrumentation configurations.

g. Weather parameters.

h. Message sets.

i. Scenarios.

j. Audio and video metadata.

k. Ability to link data elements and store as unique types (e.g. unique units, unique references).

l. Automated conversion routines for known data formats.

m. The ability to support manual conversion of data.

n. User selectable data format (coordinates or datum).

o. Supporting multiple concurrent exercises (a firing table qualification run).

p. Segregating the data in such a manner that each exercise can operate independently.

q. Maintaining the integrity of any database Logs.

r. The ability to link player lists, player type, weapon type, and descriptions.

s. The ability to link weapon types, ammunition types, and vulnerability data.

t. The ability to maintain data synchronization among all the elements (i.e., scenario, forces, PU data, video, audio) of a scenario run, so all related data from planning, execution and AAR are accessible through a single scenario instance identifier (name).

EXERCISE MANAGEMENT

CREW EVALUATOR WORKSTATIONS (CEWS)

The CEWs shall:

a. Control the exercise.

b. Control the AAR.

c. Monitor the exercise.

d. Monitor the AAR.

e. Control execution of training exercises.

f. Provide a control interface to the Voice Communications Interface (VCI).

g. Provide the HW required for monitoring the radio networks.

h. Provide command screens for interacting with the PU in an exercise.

i. Provide a SAW that displays symbology overlaid on the SAW map or area graphic.

j. Provide a SAW that displays tactical graphics overlaid on the SAW map or area graphic.

k. Provide an ability to enter administrative commands to kill individual players in an exercise.

l. Provide an ability to enter administrative commands to reset individual players in an exercise.

m. Provide an ability to enter administrative commands to reload individual players in an exercise.

Version 1.0

n. Provide an ability to enter administrative commands to resurrect individual players in an exercise.

o. Provide near real time event status of events on a tactical map display by icon color changes.

p. Enable scrolling text display of all types of events in a window.

q. Enable scrolling to be controlled with a “scroll mouse” or by slider.

r. Enable scrolling to display any event occurring within the previous 5 minutes.

s. Provide a graphical display of ground PU (i.e. location and state) events in the exercise area.

t. Allow an operator to select a minimum of 12 video feeds such as the Thru-

Site-Video (TSV) from ground vehicles, range cameras, and UAS video via a Common Ground Station (CGS).

u. Monitor multiple concurrent exercises.

v. Segregate displays of exercise data.

w. Support the SAW, VSS, and Evaluation Display Console functionality.

x. Provide the SW and HW necessary to support run execution operations.

y. Provide the SW and HW necessary to support replay.

z. Provide the SW and HW necessary to support AAR preparation.

SITUATIONAL AWARENESS WINDOW (SAW)

The SAW requirements are applicable to any exercise and system control display system. The SAW shall:

a. Accurately overlaid through a common coordinate system on 2D maps or representations of the terrain (i.e., PU, entities, devices, tactical overlays, air corridors, range fans, fields of view, and other graphics).

b. Accurately sequence overlay graphics that are scanned drawings (e.g.

tactical overlays), dynamically drawn (e.g. air corridor), computed (e.g.

range fans), symbols (e.g. unit symbology), map product files (e.g. terrain databases), photographs (e.g. aerial photographs), video (e.g. UAS video), or vector graphics.

c. Provide the capability to support multiple SAW in either tiled or cascaded view.

d. Provide a graphical display of Aviation events, when appropriate, (i.e.

location and status) in the exercise and installation area covered by the Aviation PU radio range.

e. Display the Forward Area Refueling Point (FARP) within the exercise area and installation areas when applicable.

SAW EXERCISE AWARENESS

The SAW Exercise Awareness function shall:

a. Depict player events within one second.

b. Reflect player status changes based in the setting of the PU.

c. Reflect player position within one second after its report is received at the corresponding system server.

Version 1.0

d. Display pairing information.

e. Display platform heading.

f. Support triggered dynamic plots of Line Alerts.

g. Support triggered dynamic plots of Area Alerts.

h. Support display of weapon fans for all 1553 platforms.

i. Selectively display the weapon fan as an outline, a fill color, or a pattern.

j. Display scalable symbols.

k. Enable scaling by operator action or by rules.

l. Allow selection of symbols for scaling to permit the use of a pointer right-click.

m. Allow selection of symbols for scaling to permit the use of a magnifier tool.

n. Allow selection of symbols for scaling to permit the capability to manually select from menu.

o. Allow scaling to be by percentage of default size.

p. Allow scaling by rules to include magnify on fly-over pointer.

q. Allow scaling by rules to include magnify with map scale.

r. Allow scaling by rules to include magnify with map scale but within a stated range.

s. Support player orientation symbology.

t. Support weapon orientation symbology.

u. Support display of a group as a single icon.

v. Support displaying a player by entering the player ID.

w. Support displaying a player by selecting the player ID.

x. Ensure the map display can pan to display the player in the current window.

y. Display only members in a group that are assigned to an active run.

z. Support annotation of symbology display of only player ID.

aa. Allow different options for annotation of symbology.

bb. Allow annotating with player ID's upon operator action.

cc. Support annotation of symbology with bumper numbers.

dd. Provide history trails on operator request.

ee. Allow history trails to be selected based on start time.

ff. Allow history trails to be selected based on end time.

gg. Allow history trails to be selected based on duration of the track.

hh. Allow History trails to be selectable by individual player.

ii. Allow History trails to be selectable by group.

jj. Allow History trails to be selectable by all players.

kk. Toggle or displace overlapping symbols with position lines to preclude loss of information presentation to the operator.

ll. Reflect status changes through readily identifiable changes to the player symbology.

mm. Display non-persistent effects with sufficient duration to allow an operator to react to their presence.

nn. Allow selectable icons and symbology on map displays through "mouse click to change the focus for subsequent status displays and command actions.

Version 1.0

oo. Allow selectable icons and symbology on map displays through keyboard action (e.g., tabbing through all icons) to change the focus for subsequent status displays and command actions.

pp. Provide a zoom and scaling feature.

qq. Allow map scaling (zoom) within the display.

rr. Allow zooming to be continuous for vector graphics.

ss. Allow zooming to be done as a step function for raster graphics.

tt. Allow zooming to be provided in fixed multipliers of existing scale.

uu. Enable scaling to be provided relative to standard map scale representations (1:1000, 1:25,000).

vv. Display the current scale constantly on the map window.

ww. Provide a capability to adjust the portion of the map displayed.

xx. Provide a capability to spawn a second SAW from an active window.

yy. Ensure that when spawning a second SAW display (for monitor mode) that the initial spawned window is created from within an existing SAW.

zz. Ensure that when spawning a second SAW display (for monitor mode) that it will inherit all settings from the controlling SAW.

aaa. Ensure any settings are modifiable at or after the new SAW creation.

bbb. Ensure each SAW retains its own properties (e.g. scale, overlays, filters, etc.).

ccc. Enable the operator to toggle through the windows to quickly progress to different areas of interest.

ddd. Provide map-centering functions through operator-entered coordinates or

“mouse” action.

eee. Allow scrolling of the map through "mouse" action ("click and drag").

fff. Enable dragging the pointer to any window edge to continue the scrolling in the same direction as the edge chosen.

ggg. Support use of coloring to display difference in terrain elevation.

hhh. Define and reflect exclusion zones.

iii. Ensure exclusion zones be polygons whose vertices are defined.

jjj. Ensure exclusion zones shall include altitude and firing points for aircraft engagements.

kkk. Define and reflect demarcation lines.

lll. Ensure demarcation lines (Line Alerts and Area Alerts) consist of lines between 2 or more points.

mmm. Provide the capability to save or retrieve exclusion zones between exercise iterations.

nnn. Provide the capability to save or retrieve demarcation lines between exercise iterations.

ooo. Provide a method for drawing exclusion zones with the pointer or by keyboard entry.

ppp. Provide a method for drawing demarcation lines with the pointer or by keyboard entry.

qqq. Provide the capability for demarcation line crossing to generate alerts to operators.

Version 1.0 rrr. Provide the capability for exclusion zone line crossing to generate alerts to operators.

sss. Provide the capability of predefining a step target, PU, or scoring system action and automatically executing a command (e.g. initialize scoring on a target, change PU reporting rates, etc.) as a result of the action.

SAW EXERCISE EVALUATION

The SAW Exercise Evaluation function shall:

a. Provide a capability to display a terrain profile between any 2 points in a separate window within 20 seconds.

b. Provide calculation of distance between any 2 selected points.

c. Provide calculation of azimuth between any 2 selected points.

d. Ensure the azimuth is referenced to the first point selected.

e. Ensure the back-azimuth is referenced to the second point selected.

f. Display the elevation of any selected point on the map.

g. Support the Military Grid References System (MGRS) as the default.

h. Support Universal Transverse Mercator (UTM).

i. Support Latitude/Longitude.

j. Support local coordinate systems.

k. Ensure the coordinate system displayed is dynamically selectable.

l. Display on mouse-click the coordinates of any location in the current coordinate system.

m. Ensure the datum used in converting coordinates use the World Geodetic

System (WGS)-84, in accordance with (IAW) MIL-STD-2401.

SAW SYMBOLOGY

The SAW Symbology function shall:

a. Use symbology or icons to display individual players, objects, and military units.

b. Provide an application tool to generate and maintain a symbol library.

c. Provide an application tool to attach descriptors to a symbol.

d. Provide an application tool to provide symbols to other applications.

e. Provide the initial library consisting of MIL-STD-2525 symbology and its descriptors.

f. Ensure the symbol tool supports the generation of symbols as described in the standard.

g. Ensure each symbol has an anchor to indicate the unit’s position.

h. Ensure each symbol has an anchor to indicate the unit’s orientation.

i. Provide Military Symbology that can be composed of several individual symbols representing the Unit.

j. Provide Military Symbology that can be composed of several individual symbols representing the mission.

k. Provide Military Symbology that can be composed of several individual symbols representing the text annotation for the Unit descriptors.

Version 1.0

l. Use the player name or descriptor from the SAW and then compose and return the appropriate symbol.

m. Not obscure the graphics on which it is overlaid.

n. Utilize display management techniques to de-clutter the screen presentation.

o. Provide symbols in a standard size which are scalable by the SAW, or filtering.

p. Ensure overlapping symbols can be toggled or displaced with position lines.

q. Maintain the symbols and their corresponding descriptors in the database.

EXERCISE CONTROL (EXCON)

The table names shall be displayed as a drop down list. Selection of a specific table name shall permit the entry and selection of the following:

a. Symbology derived from the unit name.

b. Instrumentation.

c. Call signs.

d. Assigned video channels (i.e. TSV, aircraft data recorders, and crew).

e. Assigned voice channels.

f. Military Symbology.

g. Crew.

h. Weapon platform, weapons, ammunition loads, etc.

EXERCISE CONTROL FUNCTION

The Exercise Control function shall:

a. Provide the scenario and the target control GUI.

b. Provide the ability to activate a run.

c. Provide the ability to activate a step.

d. Provide the ability to start an active step.

e. Provide the ability to pause an active step, which will conceal targets.

f. Provide the ability to resume step.

g. Provide the ability to stop an active step.

h. Provide the ability to complete a step.

i. Provide the ability to copy a step.

j. Provide the ability to extend a step.

k. Provide the ability to replay a step.

l. Provide the ability to deactivate a run.

m. Reset (Conceal) targets immediately upon Pause or Stop commands, which are set by the operator.

n. Support transfer of "click position" information to other input screens.

o. Ensure click position information is translated to the coordinate system selected by the operator or required by the receiving application.

p. Allow a current view to be saved and viewed as a named file.

q. Ensure SAW files are saved in such a manner that when retrieved each file retains all its’ capabilities.

Version 1.0

r. Ensure SAW files are saved in such a manner that when retrieved the operator can replay from that point.

s. Support multi-colored maps and displays.

t. Support use of false coloring to display difference in…