Attachment_2_Stryker_MTS_Phase_V_PRF-PT-684_20170726.pdf

PRF-PT-684

CAGE 57039

26 July 2017

DISTRIBUTION LIST STATEMENT A:

Approved for public release; distribution is unlimited

Performance Specification

For

Stryker Maintenance Training System

(Stryker MTS)

Phase V

U.S. Army Program Executive Office for

Simulation, Training, and Instrumentation (PEO STRI)

12211 Research Parkway

Orlando, FL 32826-3276

Engineering

Prepared By: ____________________ Approved By: ____________________ Dennis Rushing Colleen Matthews Lead Systems Engineer Chief Engineer, PdM GCTT Date: __________ Date: __________

Acquisition Logistics

Approved By: ____________________ Approved By: ____________________ Abraham Horne Destiny Laski Program Acquisition Logistician Product Support Manager, PM TRADE Date: __________ Date: __________

07 July 2017 ii

REVISION HISTORY

Revision Number Date Log of Changes Made and Description of

Reason Changes Approved By

1.0 08/18/2016 Initial Release

1.1 10/31/2016 Update

1.2 12/27/2016 Update

1.3 1/10/2017 Update

1.4 2/28/2017 Update

1.5 3/14/2017 Update comments

1.6 04/04/2017 Update with Tech Peer Review comments

1.7 15 June 2017 Clarify Specification requirements based on industry findings

1.8 30 June 2017 Update to incorporate industry comments

1.9 26 July 2017 Update to incorporate Tech review comments

07 July 2017 iii

TABLE OF CONTENTS

1 SCOPE

1.1 IDENTIFICATION

1.2 SYSTEM OVERVIEW

1.3 DOCUMENT OVERVIEW

2 REFERENCED DOCUMENTS

2.1 GOVERNMENT DOCUMENTS

2.1.1 SPECIFICATIONS, STANDARDS, AND HANDBOOKS

2.1.2 OTHER GOVERNMENT DOCUMENTS, DRAWINGS, AND PUBLICATIONS

2.2 NON-GOVERNMENT PUBLICATIONS

2.3 ORDER OF PRECEDENCE

3 REQUIREMENTS

3.1 SYSTEM WIDE DESIGN

3.2 REQUIRED MODES

3.2.1 LESSON SELECTION

3.2.2 TRAINING

3.2.3 DIAGNOSTICS

3.3 SYSTEM CAPABILITY REQUIREMENTS

3.3.1 FIDELITY REQUIREMENTS

3.3.2 TRAINING EXECUTION MODES

3.3.3 INSTRUCTOR CAPABILITIES

3.3.4 VISUAL AND AURAL CUES REQUIREMENTS

3.3.5 CAUTIONS AND WARNINGS REQUIREMENTS

3.3.6 TEST, MEASUREMENT, AND DIAGNOSTIC EQUIPMENT (TMDE) REQUIREMENTS

3.3.7 DAILY OPERATIONAL READINESS FOR TRAINING REQUIREMENTS

3.3.8 DEVICE SPECIFIC REQUIREMENTS

3.3.9 TRAINING MANAGEMENT SYSTEM (TMS)

3.3.10 SOFTWARE SUPPORT ENVIRONMENT (SSE)

3.4 SYSTEM EXTERNAL INTERFACE REQUIREMENTS

3.5 SYSTEM INTERNAL INTERFACE REQUIREMENTS

3.6 SYSTEM INTERNAL DATA REQUIREMENTS

3.7 SAFETY REQUIREMENTS

3.7.1 HAZARDOUS MATERIALS

3.7.2 FIRE PROTECTION

3.7.3 POWER OFF

3.7.4 EMERGENCY OFF SWITCHES

3.7.5 SAFETY AND EMERGENCY LIGHTING

3.7.6 OVERLOAD PROTECTION

07 July 2017 iv

3.7.7 POWER FAILURE PROVISIONS

3.7.8 GUARDS AND INTERLOCKS

3.7.9 SAFETY MARKINGS

3.8 SECURITY AND PRIVACY REQUIREMENTS

3.9 SYSTEM ENVIRONMENT REQUIREMENTS

3.10 COMPUTER RESOURCE REQUIREMENTS

3.10.1 COMPUTER HARDWARE REQUIREMENTS

3.10.2 COMPUTER HARDWARE RESOURCE UTILIZATION REQUIREMENTS

3.10.3 COMPUTER SOFTWARE REQUIREMENTS

3.10.4 COMPUTER COMMUNICATIONS REQUIREMENTS

3.11 DESIGN AND CONSTRUCTION CONSTRAINTS

3.11.1 SOFTWARE DESIGN CONSTRAINTS

3.11.2 HARDWARE DESIGN CONSTRAINTS

3.11.3 MATERIALS AND PROCESSES

3.12 PERSONNEL-RELATED REQUIREMENTS

3.13 RELIABILITY AND MAINTAINABILITY REQUIREMENTS

3.13.1 MEAN TIME BETWEEN ESSENTIAL FUNCTION FAILURE (MTBEFF)

3.13.2 MCT

3.14 NAMEPLATES AND PRODUCT MARKINGS

3.14.1 UNIQUE IDENTIFICATION

3.14.2 NAMEPLATE

3.14.3 ACCESSIBILITY

3.14.4 PARTS

3.14.5 ASSEMBLIES

3.14.6 COVERS, PANELS, AND DOORS

3.14.7 HANDLES

3.14.8 MODULAR ASSEMBLIES

4 QUALIFICATION PROVISIONS

5 NOTES

5.1 ABBREVIATIONS AND ACRONYMS

APPENDIX A - ATGM TROUBLESHOOTING TRAINING TASKS LIST

APPENDIX B - ATGM MAINTENANCE TRAINING TASKS LIST

APPENDIX C - MCV-B MAINTENANCE TRAINING TASKS LIST

APPENDIX D - MGS TROUBLESHOOTING TASK

APPENDIX E - MGS MAINTENANCE TASK

07 July 2017 v

APPENDIX F - IETM SELECTION FILTER OPTIONS

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

1 SCOPE

This Specification defines the requirements for the Stryker Phase V Maintenance Trainer System (MTS) and the methods to be used to ensure that each requirement has been met. This specification expands on the fielded MTS by adding Hands On Trainers (HOTs) for the Mobile Gun System (MGS), Anti-Tank Guided Missile (ATGM) vehicle, and Mortar Carrier Vehicle (MCV). One Part Task Trainer (PTT) for the C7 Power Pack Assembly, is also required.

1.1 Identification

The Stryker Maintenance Trainer is also referred to as “the trainer” or “the training device” within this document. The Phase V Stryker Maintenance Trainer provide maintenance training capability for the Army’s 91S Military Occupational Specialty (MOS). This capability supports familiarization, institutional and unit training. The intent is to provide training for maintenance personnel in system operation, symptom verification, troubleshooting, fault isolation, adjustment, servicing, and removal/replacement of Line Replaceable Units (LRUs).

1.2 System Overview

The Stryker vehicle is a single hull, eight-wheel vehicle delivered in multiple versions: including the Infantry Carrier Vehicle (ICV), Engineering Support Vehicle (ESV), Anti-Tank Guided Missile Vehicle (ATGM), Fire Support Vehicle (FSV), Mortar Carrier Vehicle (MCV) and Mobile Gun System (MGS). The Stryker MTS is designed to teach the soldier troubleshooting tasks and remove and replace tasks for the 91S (Stryker System Maintainer) MOS. This document presents the System Requirements of the Stryker Maintenance Trainer and the associated Training Management System (TMS). There are three classes of training devices, the Diagnostic/Troubleshooting Trainers (DTT), the Part Task Trainers (PTTs), and the Hands On Trainers (HOTs). Each of these variants targets specific training goals, but they also share common training elements. The DTT trainers are completely virtual systems. Navigation and interaction with the DTTs is via through mouse inputs. The PTT and HOT trainers integrate virtual training with physical hardware. In the case of the PTT, a specific subsystem, such as the brakes is targeted, and realistic components of that system are instrumented to be an active part of the simulation. The HOT trainers take the PTT concept one step further. The hardware in a HOT trainer is part of a more completely integrated environment that may contain more than one subsystem. It may be instrumented in the same manner as the PTT, and the hardware interacts with the virtual software simulation.

The Stryker Interim Armored Vehicle (IAV) Interactive Electronic Technical Manual (IETM) dated 14 December 2015 and Electronic Maintenance System (EMS) Next Generation (NG) viewer Version 2.1.10 is the source for the definition of each task for all supported variants and tasks other than the MGS. For the MGS the IETM released 10 December 2013 is the source for the definition of each task.

The Training Task List (TTL) identified in each variant appendix are the basis for all tasks to be incorporated into each HOT design.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

1.3 Document Overview

This document describes the system requirements of the Phase V MTS. Where a conflict with this specification and any documentation referenced by this specification regarding or applying to the Stryker MTS occurs, this specification shall take precedence. There is

Appendix A - TTL includes a list of the supported Troubleshooting tasks for the ATGM.

Appendix B - TTL includes a list or the supported Maintenance tasks for the ATGM.

Appendix C - TTL includes a list or the supported Maintenance tasks for the MCV-Type B.

Appendix D -TTL includes a list of the supported Troubleshooting tasks for the MGS Appendix E - TTL includes a list of the supported Maintenance tasks for the MGS.

Appendix F - IETM Selection Filter Options

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

2 REFERENCED DOCUMENTS

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

2.1 Government Documents

2.1.1 Specifications, Standards, and Handbooks

The following specifications, standards, and handbooks form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

MIL-STD-130 Identification Marking of U.S. Military Property MIL-STD-810 Environmental Engineering Considerations and Laboratory

Tests MIL-STD-1472 Human Engineering

Copies of these documents are available from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094 or http://quicksearch.dla.mil/

2.1.2 Other Government Documents, Drawings, and Publications

21 CFR 1040 Performance Standards for Light-emitting Products 29 CFR 1910.302 Electric Utilization Systems EM 0269 Stryker Interactive Electronic Technical Manual PCN:12930 System Architectural Design for the Stryker Maintenance

Training System Program

2.2 Non-Government Publications

ANSI EIA RS-471 Symbol and Label for Electrostatic Sensitive Devices ANSI Z535.1 Safety Colors ANSI Z535.2 Environmental and Facility Safety Signs ANSI Z535.4 Standard for Product Safety Signs and Labels ISO 2533:1975 Standard Atmosphere NFPA 70 National Electrical Code NFPA 72 National Fire Alarm and Signaling Code NFPA 101 Life Safety Code NFPA 780 Standard for the Installation of Lightning Protection

Systems

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

Copies of these documents are available from American National Standards Institute (ANSI) Standards Store www.ansi.org. or the ISO store. http://www.iso.org/iso/store.htm

2.3 Order of Precedence

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

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

3 REQUIREMENTS

3.1 System Wide Design

Although there are unique requirements for each of the three classes of Stryker trainers (DTT, PTT, HOT), the software approach to supporting them shall use a common framework to support the simulation modeling. The DTT and HOT trainers are provided with an Executive (Exec), Instructor Operators Station (IOS), Display and Control (D&C), Training Management System (TMS) and Model components. These five primary software components are integrated to provide the software simulation in the DTT and HOT. The Stryker MTS software architectural design is defined in PCN 12930.

To support communication between the IOS and the Student Workstation (SWS), the current systems are networked using a 1-Gigabit Ethernet connection. For the HOTs added in Phase V, each HOT SWS shall be networked wirelessly to its corresponding IOS. Since the TMS is the central repository for class, lesson, and student performance data, it shall be networked to all three classes of devices. Each IOS added to the MTS in Phase V shall interface to the TMS located in the DTT classroom via a 1-Gigabit Enternet connection. The DTT devices shall be on a separate subnet in order to keep the real-time Ethernet transfers confined to just that device.

The PTTs and HOTs shall be on a second subnet for the same reason.

To support the physical interaction required on the HOTs, this system shall have a hardware interface to the Input/Output (I/O) that is used to instrument each device. The executive software shall transfer the appropriate I/O points to and from the real-time simulation. The DTTs are completely virtual, and as a result do not require I/O to or from the hardware on the HOTs. The C7 Power Pack Assembly PTT and MCV HOT will not be instrumented and does not connect to any IOS or the TMS. The following is a functional block diagram of the current Stryker MTS components and MTS interfaces.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

Current Functional Block Diagram

The overall system architecture shall be retained in the design of the MGS and AGTM HOTs and each IOS shall interface with the TMS over the facility ethernet.

3.2 Required Modes

The trainer will operate in or support various modes. The modes include Lesson Selection, Training, and Diagnostics. The Lesson Selection and Diagnostics modes are operator selectable.

The characteristics of all supported modes are addressed in the relative paragraphs of this section.

3.2.1 Lesson Selection

The MTS shall provide the capability for the instructor to select a lesson. The Training Management System (TMS) maintains a library of lessons that can be selected for training. All lessons for the ATGM, and MCV HOTsshall follow Interactive Electronic Technical Manual (IETM) dated 14 December 2015 using viewer v2.1.10 and all lessons for the MGS shall follow the IETM with release date of 10 December 2013. Filter options for each TM are defined in Appendix F. The filter options shall be pre-loaded but modifiable by the student. From the Instructor Operator Station (IOS), the instructor can select an appropriate lesson from that library to use for training. Specific troubleshooting and maintenance lessons are defined in Appendix A through E for the various weapon variants.

Current Stryker MTS Interfaces

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

3.2.2 Training

In this mode, the instructor sets up a scenario for students and observes their progress. A scenario is essentially a virtual representation of the steps required to perform a given Enabling Learning Objective (ELO). The use of the term “scenario” throughout this document is synonymous with an ELO. Execution of all training tasks is assumed to be International Standard Atmosphere (ISA) Standard Day as defined by ISO 2533:1975. Refer to Section 3.3.2 Training Execution Modes for additional information on supported training modes.

3.2.3 Diagnostics

During the loading phase of the computational system, available diagnostics that require no interaction by the operator shall be executed. If all tests are passed, the simulator initialization shall proceed without operator intervention. If any of the diagnostic tests fail, the simulator shall automatically enter the diagnostic mode. In addition, after the trainer has been initialized for simulation, the operator shall have the ability to enter the diagnostic mode and select from any of the available diagnostics and alignment procedures that have been provided with the operating system.

3.3 System Capability Requirements

The Stryker MTS is both a training device and a training management tool. The maintenance training systems shall provide a familiarization, institutional, unit training and skill level development capability for system operation, fault diagnosis, troubleshooting, adjustments, and removal or replacement tasks required by the Stryker vehicle systems. The MGS and ATGM HOT devices delivered under the Phase V effort shall interface to the existing DTT classroom TMS to allow management to retrieve, review, update, correct, delete, archive, and printout selected student performance (by name or Identification (ID) number) or group performance data. Refer to the Section 3.3.9 Training Management System (TMS) section of this document for a complete listing of the reporting capabilities.

The appendices contain the TTL listing the troubleshooting and maintenance tasks to be supported by the Phase V MTS. The maintenance training systems shall provide training for the tasks defined in the TTL. The MTS shall provide a library of preprogrammed training scenarios to train the ELOs contained in the TTL.

For these preprogrammed training scenarios, the fault symptoms shall be predetermined by the scenario content and shall not be alterable by the instructor. The training system(s) shall simulate faults that require the replacement of one or more LRUs to correct the symptoms, as dictated by the tasks identified in the TTL. Completion of the proper fault response sequence by the student shall cancel the fault symptoms in the simulation.

3.3.1 Fidelity Requirements

The MTS shall train the functional application of the vehicle system through the student interface, providing those external stimuli and visual effects that prompt crewmember action/reaction. The MTS HOTs shall simulate to an appropriate level of fidelity, the features, 26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document functions, and performance of the tactical vehicle crew compartment. The MGS and ATGM HOT shall include physical obstructions evident in the actual vehicle that have to be dealt with when performing the tasks identified in the TTL.

The MTS shall simulate the tactical vehicles with the fidelity required to train students on the tasks identified in the TTL. All simulated vehicle subsystems and components shall replicate the appearance, function, and application of actual vehicle components at the fidelity and level of detail necessary to train the tasks specified in this document. Where applicable, the audio-visual feedback shall replicate the vehicle equipment.

The user shall be given the capability to perform pre-defined ancillary tasks (e.g., road test) in a single action. These tasks are not the focus of the training, but may be required to be accomplished to complete the assigned task.

The TMS shall provide the capability to select Troubleshooting ELOs that do not require the student to perform detailed maintenance actions (i.e., Single Action LRU Replacements), as dictated by the content of the TTL. Single Action LRU replacement shall account for all steps within a referenced Remove/Install Maintenance Task, including those steps that occur under the "Conditions" and "Follow-on" sections in the IETM for that Maintenance Task. Upon completion of a Single Action LRU Replacement, the state of the vehicle system models shall reflect any impact that would result from the execution of the Maintenance Task activities accounted for in the Single Action as described above. The resultant state of the execution of a Single Action LRU Replacement, or any Button Task, shall be achieved without presenting any of the transitory states (i.e., graphical transitions, aural cues, etc.) to the user.

To support the objectives of the tasks defined in the TTL, there are certain system parameters that have no impact on the success of achieving these objectives. Those parameters can assume to be constant with no impact on the value of training. The following is a list of such parameters:

a. The Battery Power Source will always be fully charged at a battery capacity of 100 ampere hours.

b. Maintenance Support Device's (MSD) internal batteries shall have limitless power to support the MSD's normal operation.

The MTS shall provide the controls, scenarios, visual cues, and sound cues required to train the ELOs identified in the TTL. Scenarios shall be unique, consisting of a set of training tasks to be completed. A scenario can be considered either preprogrammed or free-run. All preprogrammed scenarios for the Stryker MTS are identified in the TTLs. A free-run scenario is not listed in the TTL; is not selectable by the instructor; and has no scoring capabilities but will alert the user when a hazardous condition has occurred. For each preprogrammed scenario, the instructor shall be provided with digitized text describing the tasks to be trained and grading criteria of the scenario. The activities of the student(s) and the status of the student’s training scenario shall be available to be displayed to the instructor on a monitor and remote Tablet. For each preprogrammed scenario, the instructor shall be provided with digitized text describing the tasks to be trained and grading criteria of the scenario.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

3.3.1.1 Mobile Gun System (MGS) Fidelity Requirements

To support MGS training, the HOT shall:

a. Include the Ammunition Handling System and shall support each instance of ammunition handling in the MGS TTL.

b. Support the "Service Breechlock" task identified in MGS Troubleshooting TTL ID

33, BREECH OBSTRUCTION MESSAGE FLASHES ON CENTRAL CONTROL

PANEL.

c. Simulate Ammunition Select Controls.

d. Simulate Primary Armament.

e. Simulate Secondary Armament.

f. Simulate Commanders Weapon.

g. Simulate Fighting Compartment.

h. Simulate the Target Acquisition and Firing Control System. The turret shall drift approximately 0.5 degrees per second in support of Fire Control System troubleshooting procedure "Main, Gun, Turret, or CMS Reticle Drifts" (TTLs 60 and 61).

i. Simulate Turret Electrical Power.

j. Simulate Turret Electronics.

k. Simulate the Turret Drive System. The "uncontrolled movement" in Turret Drive System troubleshooting procedure "Main Gun and/or Turret Has Uncontrolled Movement" (TTL 66) shall be approximately a 10 degree movement over 3 seconds repeatedly in each direction.

l. Provide a training system button task capability corresponding to each instance of software loading in the MGS TTL.

m. Provide a button task to perform MGS boresighting in the MGS TTL.

n. Allow the MGS turret to traverse and elevate based on commander and gunner controls.

o. Allow the MGS ammunition handling system and ammunition loader to rotate and position based on the loaders commands.

p. Provide a laser Range Finder shall be eye safe or simulated.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

Upon completion of a TTL, the student shall be able to perform a complete checkout of the MGS starting with an empty system, load training ammunition, and ending with a simulated firing and cartridge ejection. The system checkout shall consist of the following IETM tasks to the degree necessary to ensure that the associated system is operational:

1. AUTOLOADER INVENTORY

2. EJECT MAIN GUN AMMUNITION

3. FIRING CIRCUIT TEST

4. LOAD MAIN GUN USING AUTOLOADER

5. OPEN/CLOSE COMMANDERS PANORAMIC VIEWER COVERS

6. OPERATE AMMUNITION HANDLING SYSTEM

7. ADJUST CENTRAL CONTROL PANEL DISPLAY

BRIGHTNESS/CONTRAST

8. OPERATE COMMANDERS CONTROL HANDLE

9. OPERATE COMMANDERS DISPLAY UNIT (CDU)

10. OPERATE COMMANDERS PANORAMIC VIEWER

11. OPERATE COMMANDERS MODULAR SIGHT DAYLIGHT SIGHT

12. OPERATE COMMANDERS MODULAR SIGHT THERMAL SIGHT

13. OPERATE GUNNERS CONTROL HANDLE

14. OPERATE MAIN GUN AND TURRENT MANUALLY

15. OPERATE MAIN GUN FROM COMMANDERS STATION

16. OPERATE MAIN GUN FROM GUNNERS STATION

17. PERFORM CENTRAL COINTROL PANEL DATA CHECK

18. POWER DOWN COMMANDERS STATION AND TURRET

19. POWERUP COMMANDERS STATION AND TURRET

20. REMOVE AMMUNITION FROM AUTOLOADER CAROUSEL

21. REMOVE AMMUNITION FROM REPLENISHER

22. REPLENISH AUTOLOADER CAROUSEL

23. REPLENISHER INVENTORY

24. RESTOCK REPLENSIHER WITH 105MM AMMUNITION

25. RESTOW MAIN GUN AMMUNITION

26. VIDEO DISPLAY TERMINAL OPERATIONS

3.3.1.2 ATGM Fidelity Requirements

The Monitoring and Warning subsystem's Video Display Terminal (VDT) shall support the fault codes as described in the ATGM TTL.

The ATGM HOT shall support the following functions:

a. Troubleshooting TTL 1, AZIMUTH DRIVE TRAVERSES WITHOUT COMMAND; the symptom indicating that the platform traverses without command shall be designed so that the platform keeps rotating beyond 0 Degrees Azimuth and does not stop.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

b. Troubleshooting TTL 12, GUNNER GYRO SWITCH FAILURE, FAULT CODE 0000 77B1, the last continuity check shall indicate continuity at the Gunner's Panel Assembly, J1, between Pins 14 and 79, indicating that the Gunner's Panel Assembly is internally damaged.

c. Troubleshooting TTL 13, GUNNER'S HANDLE GRIPS TEST FAILED, the symptom indicating that the GRIPS test Fails shall be designed so that the Tube-launched, Optically-tracked, Wire-guided (TOW) unit will not slew based on gunner's handle input.

d. Troubleshooting TTLs 15 and 16, GUNNER'S PANEL ASSEMBLY (GPA) LAMP TEST FAILED, none of the lamps shall light during lamps test.

e. Troubleshooting TTLs 17, INCORRECT OR NO AZIMUTH INDICATION, none of the azimuth position indicators will illuminate when the azimuth position assembly is “Failed” in this path.

f. Troubleshooting TTLs 18 and 19, LASER RANGE FINDER RANGE (LRF) NOT DISPLAYED, the laser range finder range displayed on the gunner's display will initialize to zero and not update.

g. Troubleshooting TTL 20, LOADER CANNOT CONTROL PLATFORM, the last continuity check shall indicate continuity at the Loader's Panel Assembly, J1, between Pins 3 and 1, indicating that the Loader's Panel Assembly is internally damaged.

h. Troubleshooting TTLs 22 and 23, LOADER'S CONTROL PANEL LAMP TEST FAILED, none of the lamps shall light during lamps test.

i. Troubleshooting TTL 25, MAST LIMIT SWITCH FAILURE 1, FAULT CODE 0000 7740; the last continuity check shall indicate continuity at the Mast Lower Limit Switch's jack between Pins A and C, indicating that the switch is internally damaged.

j. Troubleshooting TTL 32, NO POWER AT PRIMARY WEAPON STATION, the symptom indicating that the Elevated TOW System (ETS) does not power up properly shall be that no Light Emitting Diode (LED) on the Gunner's Control Panel illuminate in response to their respective switches.

k. Troubleshooting TTL 33, PLATFORM DEPRESSES/ELEVATES WITHOUT COMMAND, the symptom indicating that the platform depresses/elevates without command shall be that the platform elevates to its stop without command and then halts.

l. Troubleshooting TTL 36, PLATFORM WILL NOT STABILIZE, the symptom indicating that the platform will not stabilize in elevation shall be that the platform shall drift to maximum elevation and stay there.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

m. Troubleshooting TTLs 41 and 42, TARGET ACQUISITION SYSTEM (TAS) COOLING FAN FAILURE, FAULT CODE 0000 7780, the indication that the TAS Cooling Fan is operating properly shall be designed as an inspection of the fan.

n. Upon completion of a TTL, the student shall be able to perform any of the following tasks :

1. LOAD TOW LAUNCHER

2. LOWERING MAST ASSEMBLY FROM RAISED POSITION

3. OPERATE GUNNER'S HANDLE

4. OPERATE MAST LOCKING HANDLES

5. OPERATE TARGET ACQUISITION SYSTEM

6. PERFORM GRIPS TEST

7. PERFORM TARGET ACQUISITION SYSTEM POWER-UP

8. POWER DOWN ELEVATED TOW SYSTEM

9. POWER UP ELEVATED TOW SYSTEM

10. RAISING MAST ASSEMBLY FROM STOWED POSITION

11. STOW TOW MISSILE

12. UNLOAD TOW LAUNCHER

13. VIDEO DISPLAY TERMINAL OPERATION

The Gunner's Display system alert "SELECT NVS BEFORE SELECTING TARGET TRACKER" shall be displayed if the “TRK GATE” switch is pressed in day TV mode. The Gunner's Display system alert "FOV CHANGE NOT ALLOWED DURING TARGET TRACKER USE" shall be displayed if the Field of View (FOV) button on the gunner's handle is pressed after target lock-on.

When CANCEL is selected from the Gunner's Display Main Menu, the menu shall disappear.

When CANCEL is selected from the Gunner's Display Built-In Test (BIT) Menu, the BIT menu shall disappear. When TAS is selected from the Gunner's Display BIT Menu, the Gunner's Display shall display a system alert message that says "TAS ONLY BIT NOT VALID FOR ATGM VEHICLE." When “TAS” or “MAINT” is selected from the Gunner's Display BIT Menu, the student shall receive an indication that this action is not supported on the trainer.

The umbilical status shall indicate AGTM on the Gunner's Display.

The state indicator box on the Gunner's Display shall display the following:

DAY (alternate NIGHT)

Wide FOV (alternate Narrow FOV)

LAST

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

When the Improved Target Acquisition System (ITAS) is powered on from the Gunner's Control Panel, the Gunner's Display shall default to day display, wide field of view, and surveillance mode following the completion of Power-on Built-In Test (PBIT).

The gunner's handle buttons shall only be enabled when the gunner's handle is in its neutral position (i.e. the ETS is at rest).

The laser Range Finder shall be eye safe or simulated.

3.3.1.3 MCV-B Fidelity Requirements

To support MCV-B training of:

a. Pull Back operation.

b. Recuperator oil and nitrogen fill.

3.3.1.4 C-7 Power Pack Fidelity Requirements

To support power pack training of the following remove and replace actions:

a. Turbocharger.

b. Water Pump.

c. Alternator.

d. Transmission pan and filter.

e. Hydraulic module manifold.

f. Helipump.

g. Fan Tower.

h. Hydraulic pump for the Fan.

i. AC compressor with recharging.

All wiring harness with end connectors that are repeatedly disconnected and connected as part of the training scenario shall incorporate an additional connector along the harness but away from the end connector to facilitate rapid replacement of the end connectors as they get damaged during use.

A closed storage space with lock shall be included as part of the power pack maintenance stand to house spare replacement harness ends.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

3.3.2 Training Execution Modes

The ELOs identified in the TTL will be available for training on the designated devices, as indicated in the list. These tasks (i.e., preprogrammed scenarios) can be run only in free play mode (a.k.a. “scored”) mode. The free play mode allows the student to deviate from the expected path of execution. The MTS is also capable of running without the selection of any task in the TTL. This is considered a “free-run scenario”. If no lesson is currently active, the trainer defaults to a free-run mode.

3.3.3 Instructor Capabilities

3.3.3.1 Lesson Planning

The training system shall allow the instructor to build a Lesson Plan consisting of one or more Terminal Learning Objectives (TLO). The training system(s) shall allow the instructor to select a TLO and one or more Enabling Learning Objectives (ELO) to build the Lesson Plan. It will provide the Instructor with the capability to further customize the Lesson Plan by adding notes, pertinent to each ELO, either for the Instructors own use or for display to the students. The notes added by the instructor shall be either for display to the student stations or viewable only at the IOS/Tablet. The instructor will be given the capability to save these customized lessons. The instructor shall be able to view the associated symptom description and scoring criteria (refer to Section 3.3.9 Training Management System (TMS)) for each ELO in the TTL. The instructor will be able to alter the scoring thresholds (i.e., the number of occurrences of given criteria that are allowed before a score of NO-GO is assigned). The Stryker MTS TTL is composed entirely of ELOs. The text for the ELO titles will be pulled directly from IETM.

A Lesson may include a single or multiple fault scenarios and/or maintenance task scenarios.

The scenarios are performed in sequence. That is, one scenario must complete, either by resolution from student actions or instructor removal, before another will begin. Some of these fault scenarios will require multiple LRU replacements to remedy the symptoms. Each of these selectable faults is listed within the TTL.

Lesson creation shall limit the selection of ELOs for the HOTs platform to only those available in the current variant TTL. At the TMS, during lesson creation, the capability to select a weapon variant shall be part of the criteria for filtering and selecting ELOs. Lesson creation shall only permit a single vehicle variant per lesson.

The training system(s) shall provide the following feature for the instructor to utilize for the effective instruction of the student(s) and control of the training system(s):

a. Allow enrollment of students.

b. Selection of training scenarios and instructor functions.

c. Provide work surface and seating for instructor.

d. Display a list of available lessons.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

e. Select a previously constructed lesson for modification or assignment to the class.

f. From the IOS, distribute/assign the Lessons to the Student Workstations.

3.3.3.2 Simulation Control

The training system(s) shall provide the following feature for the instructor to utilize for the effective control of the training system(s):

a. Capability to reset the student to the last successfully completed step following an unscheduled interrupt.

b. Capability to cancel the fault during training.

On the HOTs, an Initial Condition Set (IC Set) representing a "Safe for Maintenance" condition shall be provided as a default initial condition. This IC Set shall be defined as:

a. Wheels are chocked.

b. Parking brake is on.

c. Gear selector lever is in the neutral position.

d. Automotive Master switch on Power Distribution Panel is in the OFF position.

e. Auxiliary Master switch on Power Distribution Panel is in the OFF position.

f. Battery Interconnect switch on Power Distribution Panel is in the OFF position.

g. Engine Start/Run switch on Driver's Instrument Panel is in the OFF position.

3.3.3.3 Student Monitoring and Scoring

The instructors shall be capable of real-time, non-intrusive monitoring of students’ performance.

The training system(s) shall provide an automatic capability to monitor the performance of students on all scored tasks. The training system(s) shall provide the ability for the instructor to manually grade those aspects of a lesson that cannot be automatically evaluated by the trainer software.

The training system(s) shall provide the following feature for the instructor to utilize for the effective instruction of the student(s) and control of the training system(s):

a. Ability to select and display performance analysis data (present and past training sessions).

b. Provide real time display of errors generated by student(s) as they occur during scenario, within the capabilities of the device to detect them.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

c. Real-time monitoring and control (limited to such things as freeze, reset, and record/review) of executing scenarios.

d. Access to performance data including retrieving, reviewing, and modifying student records after completion of training.

e. Display and/or provide status of all appropriate instruments, gauges, and menus from the crew compartment to enable the instructor to monitor student actions/reactions.

f. Instructor shall receive an alert when a student has received a NO-GO score for a scenario.

g. Ability to view the reason(s) why a student Failed a lesson or training exercise.

h. View the status of up to five (5) HOTs simultaneously on a single IOS or Tablet display.

i. Each First Article HOT shall be delivered with a single IOS and a single Tablet. Each Subsequent HOT shall be delivered with only a single tablet. The IOS delivered with the First Article HOT shall interface to all other HOTs of the same variant type. Each Tablet delivered with a HOT shall interface to all HOTs of the same variant type.

3.3.3.4 Trainer Control

The training system(s) shall provide the following feature for the instructor to utilize for the effective instruction of the student(s) and control of the training system(s):

a. Access to maintenance and diagnostic software.

b. Ability to power up/down training system(s).

c. Ability to perform emergency training system(s) power shutdown.

A computer control function shall provide control of the computational system and shall include start-up from a powered-down condition, loading training system(s) operational programs, initialization to a ready-for-training status, management of system diagnostics, training session reset or termination, and system shutdown. The full use of the control function shall not require more than one person.

3.3.3.5 Tablet IOS Capabilities

A Tablet computer shall be provided that will supply the instructor with a subset of those capabilities available at the HOT desktop IOSto include:

a. Activation of the Lesson.

b. Monitor in real time progress of any workstation.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

c. View next expected action for any workstation.

d. Freeze a workstation or all five workstations.

e. Ability to record the session of a workstation.

f. Ability to review of a previously recorded session of a student.

g. Provide real time display of errors generated by student(s) as they occur during scenario, within the capabilities of the device to detect them.

h. Receive an alert when a student has received a NO-GO score for a scenario

i. Manually enter a student score.

j. Vary the size and location of individual windows on the Table display.

k. View the status of up to five (5) workstations simultaneously on a single adjustable window.

3.3.4 Visual and Aural Cues Requirements

The training system(s) shall provide realistic real-time aural cues appropriate to the vehicle faults. The training system(s) shall have the capability of generating multiple aural cues simultaneously when required by the training conditions. When training conditions require more than six simultaneous aural cues, the six indicated cues with the highest priority (importance) are generated and heard. Speakers generating the aural cues shall be located so that they are not noticeable by the student during normal maintenance and troubleshooting actions.

At a minimum, the following aural cues will be simulated to support the training of the tasks defined in the TTL:

a. Engine Revolutions Per Minute (RPM).

b. Modulate the pitch and volume of the engine RPM aural cue.

3.3.5 Cautions and Warnings Requirements

To support the training of safe procedures the MTS will monitor student activities and report any unsafe actions it detects. The source for determining what constitutes unsafe actions will be the Cautions and Warnings paragraphs from the IETM for the tasks listed in the TTL. Specific vehicle associated hazards, which would need to be represented in the training system(s) to ensure training realism, shall be specifically addressed and covered in training scenarios. The residual safety hazards in the vehicle shall be replicated or simulated in the training system(s), as practical, to provide safety hazard awareness and avoidance.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

3.3.6 Test, Measurement, and Diagnostic Equipment (TMDE) Requirements

The training system(s) shall provide both normal and realistically faulted system components that can be identified using troubleshooting techniques; be inspected and tested; and be corrected by the students (e.g. TMDE, procedures specified in the IETM). The system shall show equipment with all fault conditions displayed. Training system TMDE shall accurately simulate (or stimulate) the display and functionality of real test and measurement equipment.

The following is a list of the TMDE simulated or stimulated by the training system to the extent required to support the ELOs listed in the TTL:

a. Infrared Thermometer.

b. Heat gun.

If applicable, standard test sets, kits, tool sets and special tools shall be compatible with mechanical interfaces within all the training system(s).

3.3.7 Daily Operational Readiness for Training Requirements

The Stryker MTS will provide the system maintainer with the capability to assess system health and trainer readiness. Readiness test will generate a trainer health status report that can be displayed at the IOS, saved to a file, or sent to the printer.

This built in capability will assist the system maintainer in evaluating current system status and in identifying those components in need of repair or replacement. The training systems Built-In- Test BIT shall be composed of three components: (1) operational diagnostics, (2) performance monitoring and (3) fault detection and locating.

The operational diagnostics shall be designed and implemented to enable operating personnel to determine that the training system is ready for operation. This will include:

a. Detailed diagnostics which shall be available for selection at each student station and IOS, to assess the system health of that individual station.

b. Diagnostic capabilities which shall include testing the operation of the computers, peripheral equipment and other training system(s) hardware, and for identifying malfunctioning components.

c. Daily Readiness diagnostics check which shall be capable of executing automatically and shall not exceed five (5) minutes from power on until completion of the diagnostics check.

d. Operational diagnostics which shall verify that all HOT computational, electrical, and electronic hardware is fully operational and shall include a capability to perform verification of the Input/Output (I/O) system.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

e. An I/O test which shall be capable of individually verifying all digital and analog inputs and outputs.

f. A system which shall be designed to not allow execution of training until all diagnostics faults have been cleared.

g. Diagnostic procedures which shall be used to isolate faulty hardware to the extent provided by the vendor-supplied diagnostic routines and procedures upon indication of failures of Commercial-Off-The-Shelf (COTS) equipment.

The performance monitoring component shall function on-line, be entirely self-contained, and shall require no external stimuli or measurement equipment. The operating system for the trainer shall be the approved DoD Win10 Secure Host Baseline-Army (SHB-A) operating system. The performance monitoring function shall utilize the capabilities of the Windows Events viewer and logs provided by the operating system to monitor and record all relevant system events to include warnings, errors, and information messages. The operating system logs shall record the date, time, source and category of all system generated warnings, errors, and messages.

The Fault Detection and Location capability shall allow the maintainer (from a networked computer station) to verify that all HOT computational, electrical, and electronic hardware is fully operational and shall include a capability to perform automatic or manual verification of the Input/Output (I/O) system, including individual verification of all digital and analog signals and levels. The Fault Detection and Location capability shall be capable of identifying specific hardware failures down to a replaceable part (e.g., switches, sensors, power supplies. I/O cards, LRUs).

3.3.8 Device Specific Requirements

3.3.8.1 IOS Capability Requirements

The training system(s) shall provide the capability for one instructor to control five individual HOTs from one IOS. Once the training system has been initialized, any requirement for the IOS shall also apply to the tablet. The training system shall allow any instructor to control any one of the five HOTs from a tablet. The training system(s) shall provide the capability for the instructor to select a specific HOT and monitor the performance of students on all tasks. A recording function is required to give the IOS the capability to capture each step the student takes on their workstation. The Instructor shall have the capability to review all steps taken by a student during completion of each scenario, either as a complete record or by manually or automatically stepping through the recoded steps in the same sequence taken by the student. The IOS shall allow the instructor to review recorded steps at any time during or after execution of a scenario.

The training system(s) shall provide the following features:

a. Ability to freeze and bookmark the entire class and resume the class from the bookmark in the event of an intentional or other interruption.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

b. Ability to freeze and bookmark selected or all individual workstation at any time during the training session and then resume training from the point the scenario was frozen.

c. When in the freeze state, allow the student to only perform non-maintenance activities (e.g. review activity log or lesson materials).

d. Once frozen, the instructor shall have the capability, at a minimum, to review steps, exit scenario, display student performance analysis, print student performance analysis and unfreeze.

e. Ability to restart a scenario, which allows repeat of a currently frozen or just-completed scenario.

The IOS shall provide the capability to see Student Notes. The Student Notes displayed at the IOS shall be relevant to the ELO currently being performed at that IOS. The instructor shall be able to distribute the common set of Sticky Notes to all workstations in the class.

The training system(s) shall include a “bookmark” which enables the user to return to the same place in a procedure after an interruption. The student(s) shall have the option of reviewing material presented or actions accomplished prior to initiating the bookmark, before completing the training session. The bookmark shall freeze that student's simulation and allow him to perform non-maintenance activities (e.g., review his activity log or lesson materials) within the simulation.

If a student performs an action, which is considered a safety hazard on the actual vehicle, the workstation shall freeze and the instructor/operator will be notified. Once frozen, instructor intervention shall be required to unlock (“unfreeze”) the workstation.

In addition, the IOS performance monitor shall provide the instructor with the capability to view the actions required to complete a step for a selected workstation. The following capabilities compose this feature:

a. The IOS Performance Monitor View Actions capability shall display all actions, including those not explicitly stated in the IETM (e.g., actions stated in Sticky Notes) the student must take to complete the selected step.

b. The information displayed via the View Actions capability shall be constant for any given step. That is, the content does not change, regardless of whether the student has already completed one or more of the actions required of the relevant step.

c. The View Actions capability shall be available when the selected workstation is executing in Scored Mode.

When a student is either Reset or Restarted by the instructor, the Student Log shall record the event.

26 July 2017

Use or disclosure of this data is subject to the restriction on the title page of this document

The instructor shall control the training system(s) through a mouse and touch-screen controls.

The leftmost display of the IOS shall be reserved for the Instructor Controls GUI. The instructor shall have available at the IOS all capabilities available at the workstation.

3.3.8.2 HOT Student Workstation (SWS)

The Student Workstation (SWS) on the HOT includes not only the computer system interface but the training area where the student interfaces with the physical components as well. The training system shall provide an interface to the students that allows the student to indicate when they believe an ELO has been completed. The performance data shall be transferred to TMS at completion of a lesson. When operating in a degraded mode (i.e., TMS not available on the network), the performance data shall be buffered and retained until the system is returned to normal operations and the data can be transferred to the TMS. The Sticky Notes in IETM will highlight the known errors relevant to the currently displayed IETM page. The workstation on the training system shall provide an IETM interface. The IETM used for training shall be configured to require manual entry of all multimeter readings. The Student Notes dialog shall be displayed at the beginning of each ELO.

At the beginning of each ELO, the Student Notes dialog shall be displayed. It shall include a standard statement in bold red font instructing the student to “Refer to this Notes Dialog throughout the task”. The Student Notes dialog content shall be a static list containing all of the Trainer Notes and Button Tasks that apply to the current ELO. The Student Notes dialog shall separate the display of Trainer Notes text from the display of Button Tasks information. When the failed step is the execution of a Button Task, the Student Assist message shall direct the student to the Student Notes. The default message for the Student Assist message shall be to remind the student to carefully read the IETM including all Sticky Notes. When a student receives a Student Assist message, the IOS interface shall alert the instructor.

The button task dialog shall group the button tasks under common category headings. When the user selects a category heading on the button tasks dialog, the dialog shall display all button tasks that belong to that category. The display of button tasks shall be in alphabetical order. Button task will be categorized as follows:

a. The button task dialog shall display those button tasks that perform LRU replacements under a category heading of “LRU Replacements”.

b. The button task dialog shall display those button tasks that perform Wiring Harness Inspections under a category of “Wiring Harness Inspections”.

c. The button tasks dialog shall display all tasks other than LRU Replacements and Wiring Harness Inspections under a common “Other Tasks” heading.

If the instructor has enabled the Single Action Pin Checks capability for an ELO, the…