FINAL_-_CDT_VPL_SRD_Common_20180803.docx

SYSTEM REQUIREMENTS DOCUMENT (SRD)

FOR THE

VISUAL SYSTEM FOR THE COMMON DRVER TRAINER (CDT)

FOR

THE COMMON DRIVER TRAINER (CDT) VIRTUAL PRODUCT LINE (VPL) SYSTEM

COMMON SRD

VERSION 2.1

21 JUNE 2018

Prepared by:

U.S. Army Program Executive Office Simulation, Training and Instrumentation

(PEO STRI)

Product Manager for Virtual Training Systems (PdM VTS) 12211 Science Drive Orlando, Florida 32826-3276

DISTRIBUTION STATEMENT A: APPROVED FOR PUBLIC RELEASE; DISTRIBUTION IS UNLIMITED.

CHANGE HISTORY

This page intentionally left blank

PRF-PT-00024B

PRF-PT-685

CDT Common SRD – Version 2.0 21 June 2018 ii

Table of Contents

This System Requirements Document (SRD) describes the requirements for the Common Driver Trainer (CDT). The CDT will assist in the training of tactical vehicle drivers during Initial Entry Training (IET) and sustainment as described in this document’s Appendices. The simulator(s) will enable training in the critical driver tasks that can repetitively train in a simulator and are dangerous and/or infrequently trained in the "real world" (i.e. driving on ice, fording streams, driving under blackout conditions, driving down steep embankments when coming off an improved road, etc.). The CDT will be reconfigurable to accommodate the different vehicle variants as defined in the individual SRDs included as appendices to this document. The CDT vehicle platform will be composed of common modules along with a specific module for the different vehicle variants. The components of the specific module will be the driver’s compartment, instruments, controls, for the driver, and the software required operating the driver compartment and interacting with the common modules. The driver training scenarios can be "scripted" to practice driving the same tactical, terrain and traffic conditions repetitively, with random variations in traffic along the same route. The training scenarios can also be executed “unscripted,” allowing instructor commanded variations of route and environmental conditions. Automated scoring of the driver during trainer scenarios ensures that training evaluation is consistent among all the students. In addition, as future vehicles define, the CDT Virtual Product Line (VPL) will grow to accommodate any new requirements that are not currently define in this document.

1.2 Background

The U.S. Army Program Executive Office for Simulation, Training and Instrumentation (PEO STRI), Product Manager for Virtual Training Systems (PdM VTS) has a requirement for driver training simulators to support the Training and Doctrine Command (TRADOC) schools with institutional drivers training and to support operational units with sustainment drivers training. The United States Marine Corps (USMC) Operator Driver Simulator (ODS) program’s primary purpose is to provide both entry-level and sustainment-level training for USMC Motor Transport and incidental motor vehicle operators. USMC also has requirements for driver training simulator to support The Training Education Command (TECOM). Schools with institutional driver training will support operational units with sustainment driver training. The CDT product line is the Army’s and USMC preferred solution for initial entry level and sustainment driver trainer needs. This product line encompasses driver training simulators for military wheeled, tracked and specialty vehicles, to include both tactical and non-tactical vehicles, utilizing a common platform. Each CDT system will be reconfigurable to accommodate the different vehicle variants as defined in the product system specifications.

Currently, the Army has procured 53 CDT systems (13 in the mobile system trailer training configuration and 40 in the fixed/facility configuration) and 69 specific variant cabs. This includes a Stryker Variant (SV) cab, Mine Resistance Ambush Protected (MRAP) Variant (MV) cab, Tank Variant (TV) cab that can configure as a Tank Engineering Variant (TEV) and a Tactical Wheeled Variant (TWV) cab under development. Currently, USMC PM TRASYS has procured 96 ODS systems (54 in the mobile system trailer training configuration, i.e. 19 at active duty sites and 35 at reserve sites; along with 42 in the fixed/facility configuration, i.e. 41at active duty sites and one at a reserve site). The variants ODS currently include: the High Mobility Multipurpose Wheeled Vehicle (HMMWV) cab, the Medium Tactical Vehicle Replacement (MTVR) cab, the Mine-Resistant Ambush Protected (MRAP) Buffalo and Cougar cabs, and the MRAP All-Terrain Vehicle (M-ATV) cab. New variants include the High Mobility Artillery Rocket System (HIMARS) cab, the Logistics Vehicle System Replacement (LVSR) cab, and the Joint Light Tactical Vehicle (JLTV) cab.

The Government’s intent is to maximize reuse of the existing architecture (to include software and hardware design and implementation) to preserve training capability and update this base architecture into a product line configuration providing user interoperability requirements, technical refreshes due to obsolescence and/or supportability requirements. The current driver training simulators for CDT allocate to vehicle configurations as follows:

SV vehicle variants consisting of an SV cab, Ten (10) software configurable instances with unique dynamics (each with slat armor option additionally) simulating equipment or components of the following:

(1) Infantry Carrier Vehicle (ICV)

(2) Mobile Gun System (MGS)

(3) Reconnaissance Vehicle (RV)

(4) Mortar Carrier (MC)

(5) Commander Vehicle (CV)

(6) Fire Support Vehicle (FSV)

(7) Medical Evacuation Vehicle (MEV)

(8) Anti-Tank Guided Missile Vehicle (ATGMV)

(9) Nuclear, Biological and Chemical (NBC) RV (NBCRV)

(10) Engineer Squad Vehicle (ESV) (Plow or Roller) MV vehicle variants consisting of an MV cab, five (5) hardware (dash kits) and software configurable instances with unique dynamics simulating equipment or components of the following:

(11) RG 33L

(12) RG 31

(13) Caiman

(14) MaxxPro with and without Independent Suspension System (ISS)

(15) MRAP All-Terrain Vehicle (M-ATV) TV vehicle variants consisting of a M1A2 System Enhancement Package (SEP) V2 cab baseline, three (3) hardware (dash kit) and software configurable instances with unique dynamics simulating equipment or components (panels) of the following:

(16) M1A1 (with plow or roller) (each effects dynamics)

(17) M1A2 SEP V2 (with plow or roller) (each effects dynamics)

(18) AutoFlug Variant (AV) cab hardware only used standalone for egress with modular AutoFlug or regular driver seat TEV vehicle configuration consisting of a M1A2 SEP V2 cab baseline with M1A1 panels, two hardware and software configurable instances with unique dynamics simulating equipment or components of the following:

(19) Joint Assault Bridge (JAB) (adding or removing bridge effects dynamics)

(20) Assault Breacher Vehicle (ABV) (adding or removing plow effects dynamics) TWV vehicle variants consisting of a TWV cab, variant specific interchangeable dashes with other equipment or components simulating the following:

(21) M1083A1, 5-Ton Truck with M1095 Light Tactical Vehicle Trailer (LTVT)

(22) M915 A3 Line Haul Truck with M872A4 Flatbed Trailer

(23) M915 A5 Line Haul Truck with M872A4 Flatbed Trailer

(24) M1120A4 Truck with M1077A1 Palletized Load System (PLS) Flatrack and M1076 Palletized Load System Trailer (PLST) New TWV vehicle variants consisting of a variant specific TWV cab, and dash components are:

(25) High Mobility Multipurpose Wheeled Vehicle (HMMWV) (i.e. M1113, M1114, M1151, M1151A1, M1152, M1152A1, M1165, M1165A1, M1167 and M997A3 utility trucks)

(26) Medium Tactical Vehicle Replacement (MTVR) (i.e. MK/AMK-23, MK/AMK-25, MK/AMK-27, MK/AMK-28, MK/AMK-29, MK/AMK-30, MK/AMK-31 and AMK/MK36 7 -Ton trucks)

(27) MK23 MTVR w/MAS (Marine Armor System)

(28) Joint Light Tactical Vehicle (JLTV)

(29) Mine-Resistant Ambush Protected (MRAP) (4x4 and 6x6 both with and without ISS) (i.e. CAT I A1, CAT 1 A1 ISS, CAT II A1, CAT II A1 ISS, CAT I A2, CAT I A2 ISS, CAT II A2, CAT II A2 ISS, CAT III Buffalo)

(30) MRAP All-Terrain Vehicle (M-ATV) (i.e. M1240, M1240A1 and M1245)

(31) Logistics Vehicle System Replacement (LVSR) (i.e. MKR18, AMKR18, MKR16 and AMKR16)

(32) High Mobility Artillery Rocket System (HIMARS)

(33) M1101/M1102 Trailer, Light Tactical; M353 Trailer, General Purpose; M105, Trailer Cargo 1 ½ Ton; MK38, Trailer, Cargo Resupply, HIMARS; MK593 6Ton 4 Wheel Cargo Trailer; M149A2 Water Tank Trailer; Engineer Equipment Trailer (EET); M777 Howitzer, MK/AMK970 Aircraft Refueler Each CDT system configuration also contains modules, consoles or workstations to facilitate training in a network system as identified below:

1. Instructor Operator Station (IOS) After Action Review (AAR) / Ancillary Station (AS) Scenario Generation System (SGS) Semi-Automated Forces (SAF) Joint Capabilities Release Logistics (JCR Log) Interface (Applicable to TWV M1083A1, M915A3, M915A5 and M1120A4 vehicles only) Local Area Network (LAN) Drivers Vision Enhancer (DVE) SV associated items MV associated items TV associated items TV Rear View Sensor System (RVSS) TEV associated items TEV ABV Commander’s station associated items New products delivered under the CDT product line will be extensions to the existing CDT product line.

The CDT common system will employ a common mechanical, electrical and data interface for all the cabs. The CDT simulation software and variant vehicle simulation software architecture and data requirements maintained. Physically, any cab will be able to interface with any CDT common platform. In order to ensure proper vehicle variant operation, a system will require the addition of specific vehicle dynamics, vehicle operating simulation software, and variant scoring software.

All current CDT product line functionality and performance maintained unless an Engineering Change Proposal (ECP) submitted and approved by the Government.

The CDT systems will be able to connect within CDT family platforms to achieve the specific networking training objective:

Interoperation with CDT systems will meet Cybersecurity (CS) requirements.

2. APPLICABLE DOCUMENTS

The following documents of the exact issue listed form a part of this specification to the extent specified herein. This specification designates as a first tier document. The documents referenced directly in this specification designates as second tier documents and consider part of this specification to the extent specified herein. Documents referenced in successive tiers are not part of this specification and use for guidance only.

DA Form 348

Identification Marking of U.S. Military Property Management / Records

Equipment Operator’s Qualification Record

AR 600-55

The Army Driver and Operator Standardization Program

MIL-STD-1472G

Department of Defense Design Criteria Standard, Human Engineering

DoD Joint Technical Architecture (JTA)

Human-Computer Interface Standards Version 6.0

DoDI 8500.01

Cybersecurity (CS)

DoDI 8510.01

MIL-DTL-83511A

Risk Management Framework for DoD Information Technology

General Specification for Headset-Microphone and Headset-Electrical (Medium Noise Attenuation, Hearing Protective)

DoD 8570.01- M

Information Assurance Workforce Improvement Program

(Copies of specifications, standards, drawings, and publications required by suppliers in connection with specific procurement functions will be obtained from the procuring activity or as directed by the Procuring Contracting Officer (PCO).)

2.2 Other Government Documents

The following documents of the issue in effect on date of request for proposals, for a part of this requirements document to the extent specified herein.

PRF-PT-685 System Requirements Document (SRD) for the Common Driver Trainer (CDT): Common, Appendixes A to G

CNSSI 1253 Committee on National Security Systems Instruction (CNSSI) 1253

NIST SP 800-53 National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53: Security and Privacy Controls for Federal Information Systems and Organizations

AR25-2 Information Assurance

AR 380-5 Army Information Security Program

FAR clause 52.204-9 Personal Identity Verification of Contractor Personnel

Army Directive 2014-05 Policy and Implementation Procedures for CAC Credentialing and Installation Access for Un-cleared Contractors

AR 190-13 Army Physical Security Program

PEO STRI BAM Program Executive Office for Simulation, Training & Instrumentation Basic Accreditation Manual (BAM)

29CFR1910.1200 Occupational Safety and Health Standards Toxic and hazardous Substances

EM-385-1-1 Department of Army Manuals, US Army Corp of Engineers Safety and Health Requirements Manual 2014 (Manual is downloadable from www.usace.army.mil/CESO/Pages/EM385-1-1.aspx).

29 CFR 1910 Code of Federal Regulations (CFR), 29 CFR 1910 Occupational Safety and Health Standards (OSHA) (standards are downloadable from http://www.osha.gov)

NFPA 70 National Fire Protection Association (NFPA) 70 National Electrical Code, 2017 Edition (Copies of this document are available from http://www.nfpa.org/Catalog/ or National Fire Protection Association, 11 Tracy Drive, Avon, MA 02322)

NFPA 72 National Fire Alarm and Signaling Code

OSHA 1910 Occupational Safety and Health Administration (OSHA) Regulations OSHA 1910, Subpart S Electrical (Copies of the above regulations are available from http://www.osha.gov)

ANSI Z53.1 Safety Color Code for Marking Physical Hazards

ANSI Z535.4 Marking Voltage Hazards

21 CFR 1040 Performance Standards for Light-Emitting Products

ANSI Z535.3 Safety Symbols

ANSI Z535.4 Product Safety Signs and Labels

NFPA 75 Standard for the Fire Protection of Information Technology Equipment

NFPA 101 Life Safety Code

CFR Title 29 Labor

ANSI/HFES 100-2007 Human Factors Engineering

GEIA-STD-0007 Rev B Logistics Product Data

NFPA 780 Installation of Lightning Protection Systems

49 CFR 393 Parts and Accessories Necessary for Safe Operation

SAE J318 Automotive Air Brake Line Couplers

SAE J702 Brake and Electrical Connection Locations – Truck Tractor

SAE J700 Upper Coupler Kingpin – Commercial Trailers and Semitrailers

MIL-HDBK-1002/2 Loads Handbook

SAE J1292 Automobile and Motor Coach Wiring

SAE J560 Society of Automotive Engineers for Standard J560

FED-STD-595 Color Specification, Fan Decks and Paint Chips

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 obtained.

The configuration for each CDT system derives based on the user training requirements. The configuration for each CDT system defines in the applicable CDT Variant appendices.

Each of the major subcomponents that exist within the current CDT product line shows in Figure 1, System Conceptual Diagram, and listed as follows:

a. Instructor/Operator Station (IOS)

b. Student Training Station (STS)

c. Variant Specific Cab

d. Ancillary Station (AS) / AAR

e. Common Data Server (CDS)

f. Disk Duplicator

g. Maintenance Mobile Device

Figure 1 - CDT System Conceptual Block Diagram

3.1.1 Stand-Alone Driver Training:

The CDT shall provide initial and sustainment training of an individual’s driver training requirements detailed in the variant’s appendices. Figure 2 shows two modes of individual setup configurations for Independent mode operation.

a. Independent Mode (Single-Vehicle – Driver Only training).

(1) The Driver Station shall operate in an independent mode to provide individual training.

(2) Driver Station operating in a single scenario controlled by an IOS

STS

Scenario X

STS 1

Scenario A

IOS

1:1 1 : N<=8 (Pod)

STS 2

Scenario B

STS N

Scenario F

IOS

Figure 2 - CDT Independent Mode (2 Examples)

3.1.2 Crew Training:

The CDT shall provide initial and sustainment training the driver’s tasks and include other crew members for that variant vehicle (Commander’s Station, Gunner’s Station, etc.). The set of training stations shall interoperate together as an integrated CDT training system representing a single variant vehicle type. Figure 3 shows CDT Integrated modes.

a. Integrated Mode (Single-Vehicle – Driver and Crew training)

(1) The Driver Station shall interoperate with the Ancillary Station in an integrated mode acting as one vehicle to provide crew driver training

(2) AAR/AS and Driver Station in a single scenario controlled by an IOS

STS

Scenario X Ancillary Station

STS 1

Scenario A Ancillary Station

IOS

1:1 1 : N<=8 (Pod)

STS 2

Scenario B

Ancillary Station

STS N

Scenario F Ancillary Station

IOS

Figure 3 - CDT Integrated Mode (2 Examples)

b. Network Mode (Multiple Vehicles – Driver Only and/or Driver and Crew training). Figure 4 shows CDT Network mode operation.

(1) Multiple STSs (up to 8) operating in the same scenario, up to the limitations of the computational systems

(2) An IOS shall control the overall simulation including control of all STS’s

Figure 4 - CDT Network Mode

c. Hybrid Mode (Multiple Vehicles – Driver Only and/or Driver and Crew training).Figure 5 shows CDT Hybrid mode operation

(1) For a CDT base 1: N (pod – N<=8) configuration, the IOS shall allow a combination of individual and integrated modes of training

(2) Multiple STSs operating in the same scenario and other remaining STS pod operating independently, up to the limitations of the computational systems.

(3) An IOS shall control the overall simulation including control of all STS’s in a pod (networked and individual training)

Ancillary Station

STS 4

Scenario B

IOS

STS 1

Scenario A

STS 2

Scenario A

STS 3

Scenario A

STS 8

Scenario F

Figure 5 - CDT Hybrid Mode

3.1.3 Instructor/Operator Station (IOS)

The IOS is the instructor’s primary workstation. Each IOS shall include one Common Access Card (CAC) reader capable of reading the data on the card. Information from CAC will define per Delivery Order (DO).

The IOS shall allow the instructor to select a scenario, set initial conditions, initiate the scenario, and monitor a student’s progress throughout the scenario. There are two types of IOS configurations:

a. Single Configuration mode, i.e. one IOS shall be able to monitor, control, and provide real-time feedback to one STS or one STS/AAR/AS combination.

b. N-Configuration/Network mode (Pod), i.e. one IOS shall be able to monitor, control and provide real-time feedback to up to eight co-located STS/AAR/AS combinations. In network mode, all CDT systems shall be able to interact with one another on a common terrain/environmental database while executing a single scenario. In network mode, the requirement is to allow up to eight simulated vehicles to interact and allow man-in-the-loop convoy and collective training exercises.

Each IOS shall be able to monitor, control, and provide real-time feedback up to eight simultaneous scenarios and eight STS(s). In other words, an STS shall be able to run a different scenario as another STS or run a same scenario as another STS; therefore, up to eight different scenarios executed at the same time, monitored, and controlled by one IOS.

The CDT IOS shall contain hardware and software for system start-up, initialization and runtime which allows the system operators (e.g. administrators, instructors and maintainers) to perform their respective functions on the CDT. The IOS equipment set-up shall include, at a minimum:

1. A large flat work surface

2. Safety (emergency) buttons

3. Communications controls

4. Ability to manually control simulated features and applications (e.g. joystick)

5. A mouse

6. A keyboard

7. CAC smartcard reader

8. An array of color flat screen monitors to control and monitor CDT operations

9. Chairs (for an Instructor and Observer)

Figure 6 and referenced in Table 1 shows a typical station set-up.

Figure 6 - Notional IOS Layout

Table 1 – Notional CDT TWV IOS Layout

3.1.3.1 IOS Interfaces

The interfaces shall provide bi-directional communications between connected hardware and software features and functionalities, which as a result, shall provide access to all the control and monitoring functions of the CDT. The CDT IOS shall allow system start up and initialization; allow the system administrators to create, maintain and access student and class records; allow the instructors to control training scenarios and monitor the student’s performance in real time; allow communications with students and allow maintenance personnel to access diagnostic and maintenance software.

3.1.3.2 IOS Monitors

The IOS monitors set-up shall have an array of monitors that allows the CDT operators to accomplish the various tasks such as administrator, instructor, and maintainer. All monitor displays shall be color and flat screen monitors. Each monitor shall have a minimum diagonal measurement of 22 inches for a 16:9 format (wide screen) display. The minimum native resolution shall be 1920 x 1080. The array of monitors shall include the following:

a. CDT Computer Imagery Generator (CIG) Monitors (One monitor per channel)

b. Topographical Map Monitor

c. Master Display Monitor

d. Instructor’s Stealth View Monitor

e. Camera Monitor

f. Display Monitor for the Instructor JCR Log (Applicable to TWV only)

3.1.3.2.1 Topographical Map Display

The IOS shall have the capability to display a topographical map. The topographical map display shall show the simulation from a point directly above the database (perpendicular to the ground plane) at an altitude that depends on the magnification selected. The topographical map display shall have the following characteristics:

a. Regardless of the selection of magnification, the display shows all database detail (i.e. roads, structures, rivers, obstacles, and foliage). The highest magnification shall display the database detail with a resolution consistent with the native resolution of the topographical map display monitor. The topographical map display shall display without any display scintillation, flashing, or low resolution blocky artifacts.

b. The topographical map display shall provide a minimum of the following magnification selections.

(1) Zoom capability that can display any area from the entire database down to a 50 meter or closer radius around a selected map location while maintaining full resolution.

(2) Highest magnification shall show a radius of 50 meter around the selected map center.

(3) Terrain features and scenario model objects shall change detail levels automatically based on the zoom level.

c. The topographical map display shall show own vehicle position and orientation in the database by a distinctive, own vehicle icon.

d. Each icon shall distinguish by a unique color and associated code/number to distinguish each vehicle (driver/crew) in a scenario.

e. The topographical map display shall distinctively show the actual path of own vehicle progression during the scenario.

f. The topographical map display shall show all moving entity positions and orientations in the database. Each category of moving entities shall have a distinctive icon to differentiate from other moving entity categories and own vehicle.

g. The topographical map display shall show the prescribed vehicle path in scripted scenarios.

h. The topographical map display shall show the cue trigger points in scripted scenarios.

i. The topographical map display shall have the capability to selectively center the map on own vehicle or manually position the map center.

j. Each STS shall have its own dedicated topographical map view rendered.

k. The Instructor shall be able to dynamically allocate any STS’s topographic map to any IOS display using its segmented and/or single view.

l. The topographical map display shall have contour lines to show elevation and pitch of grade change.

3.1.3.2.2 Master Display Monitoring

The IOS shall have a master display monitor which displays all IOS function, control and monitoring Graphical User Interface (GUI) windows and all maintenance application windows. There shall be a mouse and keyboard with the master display monitor. This shall be the input/output interface for all administrator, instructor, and maintainer functions.

All CDT control and monitor windows shall present on the master display monitor. All control and monitor GUI windows shall continuously update in real time during scenario execution. Multiple, resizable windows shall be able to be displayed simultaneously (the number of windows and the clarity of information shall be dependent on the number and size of windows selected) on the master display monitor. The control and monitor windows shall minimize (reduced to a single icon) or maximize (expanded to full screen).

The IOS shall display runtime scoring based upon Government-provided scoring standards. The IOS shall provide an embedded training course to support sustainment training. Scoring is not required for the embedded sustainment training course. The IOS shall contain an embedded electronic operator user and maintenance manuals, Commercial Off The Shelf (COTS) and military manuals with searchable text capabilities.

3.1.3.2.3 Instructor’s Stealth View Monitoring

The IOS shall have a color and flat screen monitor to display the manual input device controlled by the instructor’s eye point view. The instructor’s eye point view shall either tethered to the simulated training vehicle or a stealth view with free unrestricted movement throughout the training database for each simulated training vehicle. The tethered view shall present the CIG imagery of the training environment as seen from a fixed point relative to the own vehicle. The manual input device shall control the azimuth position relative to own vehicle, distance from the vehicle, elevation above own vehicle and the viewing angle of the eye point. When not being positioned by the manual input device, the attached view shall remain in a constant position and look angle relative to own vehicle throughout the training session. The stealth view shall allow unrestricted movement of the instructor’s eye point view throughout the training database. The default position for the stealth view shall tethered directly above the vehicle looking forward. The CDT system shall generate an independent stealth view for each STS. A 2 Dimension (2D) on-screen text shall overlay a unique identification number next to each ownship in the exercise.

3.1.3.2.4 In-Cab Camera Monitoring

The IOS shall have an in-cab camera monitoring capability that shall display a view of the inside of the driver’s compartment and student.

3.1.3.3 IOS Driving Control – Normal

When the instructor selects the own vehicle control, the manual input device shall provide control for both the normal instructor control and control with vehicle limitations override in effect. In the selection of the normal instructor control, the manual input device shall have a button that shall allow the user to set/release the parking brake. The manual input device shall have a button that shall allow the user to change transmission gear selection. The manual input device shall have a button that shall allow the user to start/shutdown the engine.

Forward deflection of the manual input device shall result in inputs to the vehicle dynamics model simulating the application of throttle to the ownship. Rearward deflection shall result in inputs to the vehicle dynamics model simulating the application of the ownship brakes. Deflection of the manual input device to the right shall provide input to the vehicle dynamics model simulating deflection of the steering mechanism that results in a right turn. Deflection of the manual input device to the left shall provide input to the vehicle dynamics model simulating deflection of the steering mechanism that results in a left turn. The simulated steering deflection shall increase as the manual input device left/right deflection angle increases.

3.1.3.4 IOS Driving Control – Vehicle Limitations Override (VLO) The instructor shall be able to select whether the driver’s compartment or the IOS has driving control over the vehicle simulation by way of the IOS manual input device. In the selection of the IOS driving control, the instructor shall be able to select normal vehicle dynamics mode or vehicle limitations override vehicle dynamics mode. When vehicle limitations override mode is selected, the vehicle equations of motion shall be suspended so that the own vehicle can traverse any terrain that the simulated vehicle could not normally negotiate. While in vehicle limitations override mode, the own vehicle shall be capable of maneuvering on slopes too steep for normal operation and on surfaces that normally provide insufficient traction.

3.1.3.5 IOS Communications

Each CDT IOS shall include a headphone/microphone set for both the instructor/operator (I/O) and an observer in order to communicate with the STS and ancillary stations. The IOS station shall be equipped with a mixer, amplifier, and a voice communications control software using built-in sound device in the IOS computer. The IOS computer shall support up to four (4) attached headsets. Each headphone set (I/O & observer) shall have an independent jack and volume control. The headsets provided for use at the IOS shall be closed-ear headset/boom noise-cancelling mic/computer. The cab shall provide communication devices that replicate the form, fit, and function of the MIL-DTL-83511A (or most current) tactical headsets for use by the trainee. The communication devices utilized by the trainee shall replicate the form, fit, and function of the headset, communication switch with wearable inline push-to-talk adapter, and harnesses utilized in the tactical environment.

3.1.3.6 IOS Rack

The CDT IOS shall include a COTS standard roll around electronics rack for housing components necessary to support the functionality of the IOS. The IOS rack shall include:

a. Door latches with locks

b. CDT power controls,

c. Printer,

d. Computer and networking resources,

e. Cable harness space

3.1.3.7 Power Control and Initialization

The IOS shall have a simplified procedure and capability to power-on the CDT system(s) and initialize the system(s) to a state where all systems and subsystems (i.e. STSs and Ancillary Stations) power up and ready to operate. The CDT system shall be initialized and ready to operate within ten minutes of initial power-on. From the initialized, ready to operate state, operators shall be able to initiate administrator, instructor, or maintenance functions The IOS shall also have the capability to power-down the CDT in a controlled, safe manner consistent with the CDT hardware and software (both application and operating system) requirements.

3.1.3.8 IOS Printer

The IOS rack shall have a printer to print hard copies of student reports, class reports, and student performance analysis. The IOS printer shall be able to print information from the master display monitor windows at the operator’s request. The IOS printer shall also be able to print out diagnostic data from diagnostic and maintenance applications.

3.1.3.9 IOS Computer

The IOS rack shall contain computer(s) which meets the technical specifications defined in paragraph titled ‘Computational Hardware’. The IOS computer shall be capable of running all of the IOS software defined in paragraph titled ‘IOS Software’ without noticeable lags, lockups, or system crashes.

3.1.3.10 IOS Setup Window

The IOS Setup Window shall appear on the master display monitor by default. It can move to any IOS linked monitor.

3.1.3.11 IOS Software

3.1.3.11.1 Class Manager (CM) Application

The CDT IOS shall include Class Manager Software which allows users with appropriate privileges (administrators and instructors) to perform the following functions as a minimum:

a. Group one or more scenarios into custom Program of Instructions (POIs).

b. Create student records for each student.

c. Create a database of instructors.

d. Group one or more students into a Class.

e. Assign one or more instructors to a Class.

f. Assign a POI to a Class.

g. Print student reports.

h. Print Class reports.

i. Create archives of records.

j. Export readable records/reports to external media.

k. Import records/reports in Government provided format (e.g. Excel, Word, PDF or TXT)

l. Restore all records from external media.

m. Import Resident Individual Training Management (RITM) system data from external media.

n. Retrieve all relevant personal information from an inserted CAC card automatically.

3.1.3.11.2 Administrator Capabilities

The administrator shall be able to accomplish the Class Manager functions listed herein from a single GUI administrator window. The administrator GUI window shall have radio button selections to Manage POI, Manage Scenarios, Manage Student Records, Manage Instructor Records, and Manage Class Records. The selection of the specific administrator function shall present a GUI window with data entry fields, pull down menus and radio buttons appropriate to the type of CDT training data being managed.

a. Manage POI – When selecting the Manage POI function, the administrator shall have the capability to create POIs by adding available scenarios in a specific sequence. The administrator shall also have the capability to edit POIs by changing the sequence of scenarios and deleting scenarios. The administrator shall also have the capability to delete a POI. The Manage POI function shall accomplish from a single, user friendly GUI window. Exiting the Manage POI GUI function without saving the data shall prompt an option to save the data, exit the function without saving, or cancel the operation.

b. Manage Scenarios – When selecting the Manage Scenarios function, the administrator shall have the capability to configure scenarios from the library of training scenarios available in the training database. The administrator shall be able to configure scenarios by editing the scoring limits, edit the scoring modifiers, edit the scenario configuration data, and select available configuration options. The manage scenarios function shall be accomplished from a set of selectable user friendly GUI window.

c. Manage Student Records – When selecting the Manage Student Records function, the administrator shall have the capability to manage student data in the training records database. The administrator shall be able to accomplish the following functions from the Manage Student Records GUI window:

(1) Create a student record in the training records database. Student identification shall be loaded manually by the instructor or by scanning the student’s CAC. Scanning a student’s CAC card shall copy the Student’s personal information into the CDT database. The student’s personal information shall include at a minimum: email, rank, first and last name.

(2) Permanently delete students and their personal information from the training records database. An appropriate warning shall present to the administrator advising of the action taken and an option to cancel the action before actual deletion.

(3) Archive a student’s record (one year or older) to an external storage media, removing the student record from the training records database.

(4) Retrieve a student’s record from an external storage media, adding the student record into the training records database.

(5) Create student reports for viewing and printing.

d. Manage Instructor Records – When selecting the manage instructor records function; the administrator shall have the capability to manage the instructor data in the training records database. The administrator shall have the capability to perform the following functions from the manage instructor records GUI:

(1) Add instructor’s personal information to the training records database.

(2) Permanently delete instructors and their personal information from the training records database. An appropriate warning shall present to the administrator advising of the action taken with an option to cancel the action before actual deletion.

e. Manage Class Records – When selecting the Manage Class Records function, the administrator shall have the capability to manage the training class data in the training records database. The administrator shall have the capability to perform the following functions from the Manage Class Records GUI window:

(1) The administrator shall be able to create a training class by establishing the class ID, class name, class location and the class start and end dates. The administrator shall also be able to assign an instructor or instructors to the class from a selection of instructors in the training database.

(2) The administrator shall be able to populate a training class by either manually entering student data via the keyboard or by importing student data from RITM (see section 7 RITM for a sample report) via a comma, delimited data file on digital media in accordance with DODI 8500.01 Cybersecurity guidance.

(3) The administrator shall be able to modify a training class by removing either an instructor or a student from the class and adding additional instructors or students. When deleting an instructor or student from a training class, the instructor or student data remains in the training records data base.

(4) The administrator shall be able to permanently delete a class and its associated data from the training records data base. An appropriate warning shall present to the administrator advising of the action taken and an option to cancel the action before actual deletion.

(5) The administrator shall be able to archive a class record to an external storage media, removing the class record from the training records database.

(6) The administrator shall be able to retrieve a class record from an external storage media, adding the class record into the training records database.

(7) The administrator shall be able to generate class reports for viewing or printing

f. Access Archived Operation Data – The administrator shall be able to access any cumulative archived data stored in the Class Manager, the CDS or on external media.

3.1.3.11.3 Instructor Capabilities

The instructor shall be able to accomplish the Class Manager functions listed herein from a single GUI instructor window. The instructor GUI window shall have radio button selections for each function. The selection of the specific instructor function shall present a GUI window with data entry fields, pull down menus, and radio buttons appropriate to accomplish.

a. Training Initialization – The instructor shall be able to login a student by either scanning the student’s CAC or manually entering the student’s identification (ID) information in the appropriate GUI field(s). If the student is not in the training records database, a warning shall generate stating a student record shall establish in the training records database before training can proceed. The instructor shall also be able to retrieve student scoring history from the student data in the training records database.

b. Create/Delete Student Record – The instructor shall be able to create or delete a student record in the training records database. Student information shall be loaded manually by the instructor or by scanning the student’s CAC. The student record shall contain all information necessary to create and print the reports and forms specified in paragraph section ‘Administrator/Instructor Reports and Forms’ (below).

3.1.3.11.4 Administrator/Instructor Reports and Forms

The administrator and instructor shall have the capability to print, export, modify, and save student and class reports and forms, at a minimum.

a. Student Performance Report – The student performance report shall document the analysis of the student’s performance on a scenario. The Student Performance Report shall include, at a minimum, student name, date, scenario identifier, class identifier, instructor name, miles driven in scenario, time to execute scenario, simulated fuel used in scenario, final student score for scenario, final rating and any instructor comments.

b. Student Transcript Report – The student transcript report shall document the student’s training on the CDT. The Student Transcript Report shall include, at a minimum, facility name, student name, current date, dates that the report covers, class identifier in the report header. The body of the report shall include an itemized list, sorted by date of the following information for each training session:

1) CDT identifier

2) Date of training

3) Instructor’s name

4) Non-scripted scenario identifier (if applicable)

5) Scripted scenario identifier (if applicable)

6) Miles driven in scenario

7) Time to execute scenario

8) Simulated fuel used in the scenario

9) Final score for scenario and the

10) Final rating for the scenario The report shall also include a total of the quantitative data (number of scenarios run, miles, time, fuel, etc.) in the report.

c. Enrolled Student Class Report – The student class report shall document the data for the students in a class. The Student Class Report shall include facility name, current date, class identifier, and dates that the report covers in the report header. The body of the report shall include a list of students, sorted by name with the following information for each student:

1) Soldier’s name

2) Number of non-scripted scenarios completed

3) Number of scripted scenarios completed

4) Number of scenario miles driven

5) Amount of scenario time driven

6) Amount of simulated scenario fuel consumed

7) Number of student training sessions

8) The average score of the completed scenarios The report shall also include a total of the quantitative data (number of scenarios run, miles, time, fuel, etc.) in the report.

d. Class Status Report – The class status report shall document data for the classes at a facility. The Class Status Report shall include the facility name, current date, and the dates covered by the report in the report header. The body of the report shall include a list of classes, sorted by name with the following information for each class:

1) Number of students in the class

2) Number of non-scripted scenarios completed by the class

3) Number of scripted scenarios completed by the class

4) Total number of scenario miles run by the class

5) Total scenario time for the class

6) Number of student training sessions

7) The total simulated fuel consumed by the class The report shall also include a total of the quantitative data (number of students, number of scenarios run, miles, time, fuel, etc.) in the report.

3.1.3.12 IOS Application

3.1.3.12.1 Simulation Control and Information Window

The Simulation Control and Information Window shall provide real-time data during scenario execution. The simulation control and information window shall allow the Instructor to control scenario execution. The simulation control and information window shall allow the Instructor to control the display mode of the Instructor stealth view monitor.

a. Simulation Information – The simulation information portion of the window shall provide to the instructor the scenario (scripted and unscripted) run time/scenario elapsed time, scenario miles driven/scenario odometer, scenario fuel consumed for the scenario being executed. The simulation portion of the window shall also present malfunction alerts and automated scenario scoring for the scenario executed. During scripted scenario execution, the program vehicle malfunctions shall alert the instructor when they activate no matter in which of the possible scenario control and monitoring windows view. The malfunction alert shall have visual display characteristics (e.g., color, flashing, font size, separate window, etc.) for timely recognition. The vehicle malfunction alert window shall provide the Instructor the capability to deactivate the malfunction and continue the scenario execution without the malfunction. During either scripted or non-scripted scenario execution, the instructor shall alert to any driver action that generates a scoring deduction. The scoring deduction alert shall have visual display characteristics (e.g., color, flashing, font size, separate window, etc.) for timely recognition but different from the malfunction alert. Each scoring deduction alert shall also include a time tag listing the time of occurrence from the start of the scenario. The scoring deduction alert shall accumulate from the beginning to the end of the scenario with only the latest five scoring deductions shown instantaneously. There shall be the capability for the instructor to select the scoring deduction alerts with the cursor and show all scoring deduction alerts along with their time tag that have accumulated to that time. There shall also be continuous display of the current cumulative score for the scenario that updates each time a scoring deduction event is registered.

b. Simulation Control – The instructor shall be able to control the execution of the selected training scenario after the scenario begins. The instructor shall be able to start, stop, jump the scenario to the next section (instructor placed flag(s) or beginning) forwards and/or backwards, pause and resume the selected training scenario from a scenario control GUI window. The instructor shall be able to set flags during the execution of the scenario that identifies points of interest in the scenario. The instructor shall then be able to position the scenario at the flagged locations and either replay the scenario from that point or have the student re-drive the scenario from that point. The instructor shall also have the capability to jump back 30 seconds in the scenario and either replay the last 30 seconds over, or to allow the student to re-execute that section of the scenario. A separate control shall be provided that clears a hard collision (i.e. resets all visuals, states, and controls); and jumps back to either the last flagged point in the scenario or a point 30 seconds before the collision (whichever is closer to the collision point) to allow the student to continue execution of the ongoing scenario prior to the collision. The instructor shall also be able to select whether the driver’s compartment or the IOS has driving control over the vehicle simulation by way of the IOS manual input device. In the selection of the IOS driving control, the instructor shall be able to select normal vehicle dynamics mode or vehicle limitations override mode. When the instructor is controlling the own vehicle, steering, throttle, service brake, and transmission control inputs from the driver compartment shall be ignored by the simulation. If normal vehicle dynamics mode is selected, all movement of the own vehicle shall be subject to the limitations of the vehicle equations of motion and terrain traversability. In normal vehicle dynamics mode, the own vehicle shall not move in a manner that would not be possible if control was exercised from the driver compartment controls. When vehicle limitations override mode is selected, the vehicle equations of motion shall be suspended so that the own vehicle can traverse terrain that the simulated vehicle could not normally negotiate. When vehicle limitations override mode is selected, the own vehicle shall be capable of maneuvering on slopes too steep for normal operation and on surfaces that normally provide insufficient traction.

c. Stealth Capability Control –The instructor shall be able to select the function and view of the IOS Stealth capability for each STS. The Stealth capability shall allow either the vehicle tethered view capability or the Stealth view capability with free unrestricted movement throughout the training database. The tethered view capability shall present the CIG of the training environment as seen from a fixed point relative to the own vehicle.