Stryker_MTS_Phase_V_DRAFT_SRD_2016_10_27.docx
DOCX document 468 KB Posted
- Attached to
- Stryker Maintenance Training System (Stryker-MTS) Federal contract opportunity
- Solicitation number
- W900KK-17-R-0016
About this file
Draft Specification for Industry input and review
View the file
Other files for this federal contract opportunity
Show all 50
Stryker Maintenance Training System (Stryker-MTS) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PERFORMANCE SPECIFICATION
SYSTEM SPECIFICATION
FOR
(APPROVED NAME OF TRAINER
BEING PROCURED)
U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI) 12350 Research Parkway Orlando, FL 32826-3276
PREPARED BY: [Authorizing Signature] DATE:
| PE’s Name |
| Project Engineer |
| PEO-STRI |
APPROVED BY: [Authorizing Signature] DATE:
| PE’s Lead Engineers Name |
| PM Name |
| PEO-STRI |
REVISION HISTORY
| Revision |
| Reason for Change |
| Affected Pages |
| Submit Date |
| - |
| Initial Release |
08/18/2016
PRF-PT-684
CAGE 57039
XX XXXX 2016
PRF-PT-XXX
CAGE 57039
XX XXXX 2016
v
TABLE OF CONTENTS
| 1 scope | 1 |
| 1.1 Identification | 1 |
| 1.2 System Overview | 1 |
| 1.3 Document Overview | 2 |
| 2 referenced documents | 4 |
| 2.1 Government Documents | 4 |
| 2.1.1 Specifications, standards, and handbooks. | 4 |
| 2.1.2 Other Government documents, drawings, and publications | 4 |
| 2.2 NonGovernment publications | 4 |
| 2.3 Order of Precedence | 4 |
| 3 requirements | 5 |
| 3.1 Required Modes | 5 |
| 3.1.1 Lesson Selection | 5 |
| 3.1.2 Lecture | 5 |
| 3.1.3 Demonstration | 5 |
| 3.1.4 Training | 6 |
| 3.1.5 Diagnostics | 6 |
| 3.2 System Capability Requirements | 6 |
| 3.2.1 Fidelity Requirements | 7 |
| 3.2.2 Training Execution Modes | 13 |
| 3.2.3 Instructor Capabilities | 13 |
| 3.2.4 Visual and Aural Cues Requirements | 17 |
| 3.2.5 Cautions and Warnings Requirements | 18 |
| 3.2.6 Test, Measurement, and Diagnostic Equipment (TMDE) Requirements | 18 |
| 3.2.7 Daily Operational Readiness for Training Requirements | 19 |
| 3.2.8 Device Specific Requirements | 21 |
| 3.2.9 Training Management System (TMS) | 28 |
| 3.2.10 Software Support Environment (SSE) | 31 |
| 3.3 System External Interface Requirements | 31 |
| 3.4 System Internal Interface Requirements | 31 |
| 3.5 System Internal Data Requirements | 31 |
| 3.6 Safety Requirements | 32 |
| 3.6.1 Hazardous Materials | 32 |
| 3.6.2 Fire Protection | 32 |
| 3.6.3 Power Off | 32 |
| 3.6.4 Emergency Off Switches | 32 |
| 3.6.5 Overload Protection | 32 |
| 3.6.6 Power Failure Provisions | 33 |
| 3.6.7 Guards and interlocks | 33 |
| 3.7 Security and Privacy Requirements | 33 |
| 3.8 System Environment Requirements | 33 |
| 3.9 Computer Resource Requirements | 34 |
| 3.9.1 Computer Hardware Requirements | 34 |
| 3.9.2 Computer Hardware Resource Utilization Requirements | 34 |
| 3.9.3 Computer Software Requirements | 34 |
| 3.9.4 Computer Communications Requirements | 35 |
| 3.10 Design and Construction Constraints | 35 |
| 3.10.1 Software Design Constraints | 35 |
| 3.10.2 Hardware Design Constraints | 36 |
| 3.11 Personnel-Related Requirements | 36 |
| 3.12 Logistics-Related Requirements | 36 |
| 3.12.1 Nameplates and Product Markings | 36 |
| 3.12.2 Accessibility | 38 |
| 3.12.3 Parts | 38 |
| 3.12.4 Assemblies | 38 |
| 3.12.5 Covers, panels, and doors | 39 |
| 3.12.6 Handles | 39 |
| 3.12.7 Modular assemblies | 39 |
| 4 Qualification Provisions | 40 |
| 5 Notes | 41 |
| 5.1 Abbreviations and Acronyms | 41 |
| Appendix A - Automotive Troubleshooting Training Task List | 1 |
| Appendix B - Automotive Maintenance Training Tasks List | 1 |
| Appendix C - Vehicle Operations List | 1 |
| Appendix D - Components | 1 |
| Appendix E - Button Tasks | 1 |
| Appendix F - RWS Troubleshooting Training Task List | 1 |
| Appendix G - RWS Maintenance Training Tasks List | 1 |
| Appendix H - ATGM Troubleshooting Training Tasks List | 1 |
| Appendix I - ATGM Maintenance Training Tasks List | 1 |
| Appendix J - FSV Troubleshooting Training Task List | 1 |
| Appendix K - FSV Maintenance Training Tasks List | 1 |
| Appendix L - MCV-B Troubleshooting Tasks List | 1 |
| Appendix M - MCV-B Maintenance Training Tasks List | 1 |
| Appendix N - MGS Troubleshooting Task | 1 |
| Appendix O - MGS Maintenance Task | 1 |
| Appendix P - MGS IETM Selection Filter Options | 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 (HOT) for the Mobile Gun System (MGS), Anti-Tank Guided Missile Vehicle (ATGM), Mortar Carrier Vehicle (MC), and conversion of two existing Hull HOTs to the Stryker A1 configuration. The existing Remote Weapon System (RWS) HOT size and footprint is being reduced. Two additional Part Task Trainers (PTT) for the the new C7 amd C9 caterpillar engines. Along with a Tech Refresh to the existing five (5) HOT hulls currently at Ft. Lee. Envious
Identification 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).
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 (MC) and Mobile Gun System (MGS). The Stryker MTS Hull HOT is designed to teach the soldier troubleshooting tasks and remove and replace tasks for the 91S (wheeled vehicle automotive mechanic) military occupational specialties (MOS). The Hull HOT is capable of training critical tasks contained in this MOS on the ICV vehicle variant. The RWS HOT is designed to teach the soldier troubleshooting tasks and remove and replace tasks for the armament tasks. The RWS HOT is capable of training critical tasks, contained in the 91S MOS, on the weapon systems for the ICV Remote Weapon System. The Hull HOT and the RWS HOT trainer are physical devices integrating the vehicle software models developed and tested on the 91S Diagnostic Troubleshooting Trainer (DTT) with the actual or simulated vehicle components and Test, Measurement and Diagnostic Equipment (TMDE). The Stryker MTS DTT is also designed to teach the soldier troubleshooting tasks and remove and replace tasks for the 91S military occupational specialties (MOS) but in a virtual environment. The DTT is currently fielded and capable of training critical tasks contained in this MOS on the each vehicle variant.
This document presents the Program-Unique Requirements of the Stryker Phase V MTS. The STRYKER Interactive Electronic Technical Manual (IETM) dated 14 December 2015 and Electronic Maintenance System (EMS) 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 Electronic Maintenance System (EMS) Next-Generation (NG) IETM released 10 December 2013 is the source for the definition of each task.
For Phase V, additional hands-on trainers for the MGS, AGTM and MC are added to the Stryker MTS suite of trainers. Additional Part Task Trainers (PTTs) for the caterpillar C7 and C9 engine are added to the Stryker MTS suite. While maintaining all of the existing critical tasks training capability, The RWS HOT will be redesigned to minimize the physical size and incorporate mounts and tasks for additional RWS weapon variants.
Portions of the Stryker fleet are being upgraded to the Stryker A1 configuration. The “A1” configuration will include additional armor, the C9 engine, improved suspension, digitized vehicle controls and other improvements. Correspondently two existing Hull Hots will be converted to match the A1 configuration.
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 no classified material used in the generation or execution of this software.
Appendix A - Training Task List (TTL) includes a list of the supported Automotive Troubleshooting training tasks for the Phase V PTT and HOTs.
Appendix B - TTL includes a list of the supported Stryker ICV Automotive Maintenance training tasks for the Phase V Hull HOTs.
Appendix C – Vehicle Operations List includes a list of supported Stryker ICV operational tasks for the Phase V.
Appendix D - Components contains a list of the vehicle components supported by the Phase V. (This list must be expanded based on the final design) Appendix E - Button Tasks contains a list of the button tasks (i.e., single action user tasks that accomplish multiple maintenance activities such as “Perform Road Test”) supported by the Phase V. (THIS LIST MUST BE EXPANDED BASED ON THE FINAL DESIGN) Appendix F – TTL includes a list of the supported Troubleshooting tasks for the RWS and RWS HOTs.
Appendix G – TTL includes a list or the supported Maintenance tasks for the RWS and RWS HOTs.
Appendix H – TTL includes a list of the supported Troubleshooting tasks for the ATGM.
Appendix I – TTL includes a list or the supported Maintenance tasks for the ATGM.
Appendix J – TTL includes a list of the supported Troubleshooting tasks for the FSV.
Appendix K – TTL includes a list or the supported Maintenance tasks for the FSV.
Appendix L – TTL includes a list of the supported Troubleshooting tasks for the MCV-B.
Appendix M – TTL includes a list or the supported Maintenance tasks for the MCV-B.
Appendix N –TTL includes a list of the supported Troubleshooting tasks for the MGS Appendix O – TTL includes a list of the supported Maintenance tasks for the MGS.
Appendix P –List of filter options applicable to the IETM for the MGS.
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.
Government Documents 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 (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/ Other Government documents, drawings, and publications Stryker Phase V Requirements Traceability Matrix NonGovernment publications ANSI NFPA 101 Life Safety Code ANSI NFPA 70 National Electrical Code ANSI NFPA 72 National Fire Alarm Code ANSI NFPA 780 Standard for the Installation of Lightning Protection Systems ANSI Z535.4 Standard for Product Safety Signs and Labels (Copies of these documents are available from ANSI Standards Store www.ansi.org.)
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.
requirements Required Modes The trainer will operate in or support various modes. The modes include Lesson Selection, Lecture, Demonstration, Training, and Diagnostics. The Lesson Selection and Diagnostics modes are operator selectable. The Lecture, Demonstration, and Training modes are a common mode of execution, but differ in how the instructor makes use of that mode. The characteristics of these modes are addressed in the relative paragraphs of this section.
Lesson Selection The trainer 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 automotive, Remote Weapon Station (RWS), Anti-tank guided Missile (ATGM), and Mortar Carrier (MC) shall follow Integrated Electronic technical Manual (IETM) version 2.8.2.10 and all lessons for the Mobile Gun System (MGS) shall follow the next-generation IETM viewer version 2.1.7 and IETM with release date of 10 December 2013 using the filter options in Appendix P. For the non-MGS variants the filter options shall be a) Vehicle is equipped with CAT 3126 power pack; b) Vehicle is not equipped with improved battery box; and c) Vehicle is equipped with VDET. From the Instructor Operator Station (IOS), the instructor can select an appropriate lesson from that library to use for training. Refer to Section 3.2.3.1 Lesson Planning for further definition of the Lesson Planning/Selection capabilities of the trainer.
Lecture The DTT trainers provide a classroom environment where the instructor presents both normal and faulted system functionality. The IOS on the DTT shall allow the operator to optionally select displays for projection on two screens, supporting the instructor’s lecture with high fidelity references to actual vehicle systems and panels. IOS capability shall be provided to:
a. Select normal or faulted operation.
b. Select the presentation method (equipment graphics, functional block diagrams, electrical schematics, IETM)
c. Control the lesson (refer to Section 3.2.3 Instructor Capabilities)
d. Project a large screen video display.
Demonstration The HOT, PTT and DTT trainers provide an environment where the instructor has the option to demonstrate both normal and faulted system functionality. IOS capability shall be provided to:
a. Select normal or faulted operation.
b. Select the presentation method (equipment graphics, functional block diagrams, electrical schematics, IETM)
c. Control the lesson (refer to Section 3.2.3 Instructor Capabilities)
d. Project a large screen video display.
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. For the PTTs and HOTs, the trainer mode shall:
a. Support individual lockstep mode on the PTTs and HOTs. In the individual lockstep mode, the student must perform all of the operations required by the IETM in the same order as that document describes. There is no interaction with other students.
b. Support knowledge based training by displaying the schematics or system diagram in sufficient detail to allow the student to demonstrate their understanding of the system operation.
c. Provide instructional features and controls to support the learning objectives and instructional tasks during trainer simulation operations. The student workstations simulate the vehicle and support operations of the maintainer.
d. The STRYKER Interactive Electronic Technical Manual (IETM) dated 14 December 2015 and Electronic Maintenance System (EMS) viewer Version 2.1.10 shall be the source for the definition of each task for all supported variants and tasks other than the MGS. For the MGS the Electronic Maintenance System (EMS) Next-Generation (NG) IETM released 10 December 2013 shall be the source for the definition of each task.
The default vehicle variant selected on the IOS for an instructor or warrant officer shall be the ICV. Execution of all training tasks is assumed to be ISA Standard Day. Refer to Section 3.2.2 Training Execution Modes for additional information on supported training modes.
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 should 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 COTS system.
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, removal/replacement tasks required by the Stryker vehicle systems. A training management workstation, networked, but separate from the training system(s), shall be provided to allow management to retrieve, review, update, correct, delete, archive, and printout selected student performance (by name or ID number) or group performance data. Refer to the Section 3.2.9 Training Management System (TMS) section of this document for a complete listing of the reporting capabilities.
The appendices contain the Training Task List (TTL) listing the troubleshooting and maintenance tasks to be supported by the Phase V. The maintenance training systems shall provide training for the tasks defined in the TTL. The training system(s) shall provide a library of preprogrammed training scenarios to train the ELOs contained in the TTL. For the automotive related ELOs, the vehicle variant supported for Phase V training shall be the ICV and the Stryker ICV-A1.
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.
Fidelity Requirements The training system(s) 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 training system(s) shall simulate to an appropriate level of fidelity the features, functions, and performance of the vehicle crew compartment. The vehicle systems to be simulated for required training shall include the following:
a. Remote Weapon Station
b. Anti-Tank guided Missile (ATGM) System
c. Fire Support Vehicle (FSV) System
d. Mortar Carrier Vehicle – B (MCV-B) System
e. Main Gun System (MGS)
f. Power Pack
g. Engine
h. Transmission
i. Power Module
j. Pneumatic System
k. Fuel System
l. Exhaust System
m. Driveline
n. Suspension
o. Doors, Hatches and Grilles
p. Cooling Module
q. Central Tire Inflation System
r. Pneumatic Brake System
s. Steering System
t. Electrical System
u. Height Management System
v. Climate Control
w. Automatic Fire Extinguisher System (AFES)
x. Hydraulic System
y. Winch Assembly
z. Lighting System
aa. Seating Assemblies
ab. Covers, Guards and Access Panels
ac. Monitoring and Warning Devices The training system(s) shall simulate the actual vehicle with sufficient fidelity to adequately train students based on simulations of these vehicle systems. All simulated vehicle subsystems and components shall replicate the appearance, function, and application of actual vehicle components as 3-D graphics 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. A complete listing of these single action (i.e., Button Task) tasks can be found in the Appendix of this specification.
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) on the PTTs and HOTs, 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. Any LRU replacement that occurs under a Troubleshooting path in the TTL shall be performed as a Single Action LRU Replacement. 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:
· Engine oil quantity shall always be at a constant value of full
· Hour Meter shall display a constant value of accumulated engine operating hours
· Odometer shall display a constant value of accumulated distance in miles
· Fuel tank quantity shall always be at a constant value of full, when not faulted or drained
· The Battery Power Source will always be fully charged at a battery capacity of 100 ampere hours
· Maintenance Support Device's (MSD) internal batteries shall have limitless power to support the MSD's normal operation The training system(s) 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 TTL. 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.
RWS Fidelity Requirements To support RWS-I training of:
· Troubleshooting TTL 24 and 25, and Maintenance TTL 14, the RWS simulation shall support operation, removal, installation and replacement of STORM LRF.
· Maintenance TTL 13, the STORM LRF shall be capable of being adjusted while installed on the RWS.
· Troubleshooting TTL 26, and Maintenance TTL 15, the RWS simulation shall support operation, removal, and installation of the Low Ammo Sensor.
· Troubleshooting TTL 25 and 26, the RWS simulation shall support functionality of wiring harness W19 linking STORM LRF and Low Ammo Sensor to FCU.
· Operational checkout following LRF Remove and Install, the RWS simulation shall support LCD functionality and MODE, L, and R buttons on LRF unit.
The Fire Control Unit (FCU) screen shall display range data from the STORM Laser Range Finder (LRF).
ATGM Fidelity Requirements The Monitoring and Warning subsystem's Video Display Terminal (VDT) shall support the fault codes as described in the ATGM TTL.
To support ATGM training of:
· Troubleshooting TTL 1, AZIMUTH DRIVE TRAVERSES WITHOUT COMMAND; the symptom indicating that the platform traverses without command shall be modeled as the platform keeps rotating beyond 0 Degrees Azimuth and does not stop.
· 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.
· Troubleshooting TTL 13, GUNNER'S HANDLE GRIPS TEST FAILED, the symptom indicating that the GRIPS test Fails shall be modeled as the TOW unit will not slew based on gunner's handle input.
· Troubleshooting TTLs 15 and 16, GUNNER'S PANEL ASSEMBLY (GPA) LAMP TEST FAILED, none of the lamps shall light during lamps test.
· 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.
· 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.
· 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.
· Troubleshooting TTLs 22 and 23, LOADER'S CONTROL PANEL LAMP TEST FAILED, none of the lamps shall light during lamps test.
· 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.
· Troubleshooting TTL 32, NO POWER AT PRIMARY WEAPON STATION, the symptom indicating that the ETS does not power up properly shall be that no LEDs on the Gunner's Control Panel illuminate in response to their respective switches.
· Troubleshooting TTL 33, PLATFORM DEPRESSES/ELEVATES WITHOUT COMMAND, the symptom indicating that the platform depresses/elevates without command shall be modeled as the platform elevates to its stop without command and then halts.
· Troubleshooting TTL 36, PLATFORM WILL NOT STABILIZE, the symptom indicating that the platform will not stabilize in elevation shall be modeled as the platform shall drift to maximum elevation and stay there.
· 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 modeled as an inspection of the fan.
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 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 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) WFOV (alternate NFOV)
LAST
When the ITAS is powered on from the Gunner's Control Panel, the Gunner's Display shall default to day TV, wide field of view, and surveillance mode following the completion of 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).
FSV Fidelity Requirements The Driver’s Vision Enhancer (DVE) shall support power up and simulated video display.
To support FSV training of:
· Troubleshooting TTL 16, TROUBLESHOOT CUPOLA INSTALLATION, the fault with the initial "Perform cupola installation functionality check" shall be modeled as the cupola drifts after releasing the force stick.
· The Monitoring and Warning subsystem's Video Display Terminal shall display FS3 & DVE Video to support FSV TTL 17..
· Troubleshooting TTL 17, VDT NOT DISPLAYING FS3 VIDEO; the simulation shall support swapping W35 P2/ VDT J2 with W501 P2/VDT J3.
MCV-B Fidelity Requirements There are no fidelity requirements specific to the MCV-B variant.
Main Gun System (MGS) Fidelity Requirements To support MGS training of:
· Ammunition Handling System with corresponding button task for each instance of ammunition handling in the MGS TTL.
· Button task for the "Service Breechlock" task identified in MGS Troubleshooting TTL ID 33, BREECH OBSTRUCTION MESSAGE FLASHES ON CENTRAL CONTROL PANEL.
· Ammunition Select Controls
· Primary Armament
· Secondary Armament
· Commanders Weapon
· Fighting Compartment
· 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).
· Turret electrical Power
· Turret Electronics
· 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.
· The training system button task capability shall provide a corresponding button task for each instance of software loading or version verification in the MGS TTL.
· The training system button task capability shall provide a button task to perform MGS boresighting in the MGS TTL Automotive Fidelity Requirements The simulated Engine system shall support the ability to start and shut down the engine. Hydraulic pressure shall be represented as a function of engine RPM. The speed of the engine compartment fan shall be based on engine temperature.
The simulated Transmission system shall support the ability to shift into all gear ranges. Visual cues can be necessary to convey information to the student that he would not otherwise be able to sense in the virtual environment. The simulation shall provide the student with a visual cue if the student attempts to release the parking brake with the vehicle in gear. The simulation shall provide the student with a visual cue if the student attempts to put the vehicle in gear without the parking brake engaged. The student shall receive a visual cue if the Transmission Lock-Up Clutch does not properly disengage during braking. The simulation shall provide the student with a visual cue if the transmission shifter does not operate freely through all gears.
The Monitoring and Warning subsystem’s Video Display Terminal (VDT) shall support the display of fault codes as described in the Phase V PTTS and HOTs TTLs (see Appendix).
The training system shall support the mechanical lowering and raising of the troop ramp as well as the capability to lower and raise the ramp manually.
The simulated HMS system shall support the ability to lower/raise the front and back of the vehicle.
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 in either a free play mode or lockstep mode. The free play mode allows the student to deviate from the expected path of execution. The lockstep mode prevents the student from deviating from the sequence of steps of the given task as defined in the IETM. 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. All students in a class are assigned the same lesson.
Instructor Capabilities 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 two 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. 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.2.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 PTTs and HOTs platform to only those available in the current TTL.
The TMS shall provide a mechanism to support coexistence of legacy lessons for the PTTS and HOTs. 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 and students
d. Display a list of available lessons
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 Simulation 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. Capability to by-pass normal vehicle engine start sequence
b. Cancel the scenario for the entire class
c. Capability to select from a set of predefined rates to either speed up or slow down the simulation. The virtual environment graphical representation shall update the graphics at a rate reflective of the current simulation rate.
d. Capability to speed the simulation rate up to 2X or 4X the normal simulation rate. The virtual environment graphical representation shall be capable of updating the graphics at a rate up to 2X or 4X the normal rate.
e. Capability to slow the simulation rate down to 1/2X the normal simulation rate. The virtual environment graphical representation shall be capable of updating the graphics at a rate up of 1/2X the normal rate.
f. Capability to create Initial Condition Sets (i.e., select the step in the ELO at which the student will start the scenario) that will allow him to define the state of the simulation at the start of a scenario. The virtual environment graphical representation shall depict the vehicle and any required TMDE as if the student had successfully completed all actions up to the point of the Initial Conditions Set selected by the instructor.
g. Capability to reset the student to the last successfully completed step following an unscheduled interrupt
h. Capability to cancel the fault during training.
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 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 tasks.
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
c. Real-time monitoring and control (limited to such things as freeze, reset, and record/playback) 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. Access to Functional Block Diagrams (FBD) that allow the monitoring of vehicle power distribution of the current simulation, within the scope of the information depicted in the diagram(s) and access to electrical schematics associated with the current ELO.
i. Select either the aural cues or 2-way communication to be relayed to the student headset/speakers.
j. View the status of up to 20 students simultaneously on a single IOS or Tablet display.
k. Notify the instructor when a given student station has been idle (i.e., No interaction with simulation while not in Freeze) for more than 5 minutes during the course of a training scenario 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. The virtual environment graphical representation shall depict the vehicle and any required TMDE as defined by the simulation data captured for the point of the Reset selected by the instructor.
Tablet IOS Capabilities A Tablet computer shall be provided that will supply the instructor with a subset of those capabilities available at the desktop IOS. A list of those capabilities is:
a. Classroom Freeze Control
b. Selected Workstation Freeze Control
c. Place a student station currently in scored mode into workstation lockstep mode
d. Activation of the Lesson Plan
e. Ability to select a student station to be recorded
f. Provide real time display of errors generated by student(s) as they occur during scenario, within the capabilities of the device to detect them
g. Ability to control playback of a previously recorded session on the student’s station
h. View the status of up to 20 students simultaneously on a single adjustable IOS window
i. Send a hardcopy of a student’s display to the printer
j. Vary the size and location of individual windows on the Table display
k. The capability to display the next expected action for the currently selected student
l. Receive an alert when a student has received a NO-GO score for a scenario
m. Manually enter a student score 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.
The visual simulation shall provide the essential cues required by the student to assess simulated vehicle characteristics and other information necessary perform maintenance or to troubleshoot the simulated vehicle in training scenarios. The training system(s) shall provide real-time color computer generated visual images of sufficient detail to adequately train maintenance personnel.
There may be instances where a strict virtual representation of a given component does not present a user-friendly interface. When this occurs, a graphical cue shall be used to indicate such to the observer. Every effort shall be made to keep these occurrences to a minimum.
To provide feedback to the student as assurance that certain activities have been performed, it may be necessary to enhance his view with certain visual cues. Two such types of cues are LRU Replacement cues and Navigational cues. The following paragraphs describe how each would assist the user in executing his tasks on the PTTs and HOTs:
a. The simulation shall provide the observer with a visual cue if the student attempts to fire the gunner’s trigger without the firing circuit tester in place.
b. The simulation shall provide the observer with a visual cue if the student attempts to release the parking brake with the vehicle in gear.
c. If the Transmission Lock-Up Clutch does not properly disengage during braking, the observer shall receive a visual cue indicating that.
d. The simulation shall provide the observer with a visual cue if the transmission shifter does not operate freely through all gears.
The following aural cues will be simulated to support the training of the tasks defined in the TTL:
a. Engine RPM
b. Modulate the pitch and volume of the engine RPM aural cue while the Transfer Pump in Height Control Manifold is cycling
c. Fuel pump shall hum while examined while operating
d. Troop and driver fans operation
e. The AFES alarm system when the engine fire extinguisher sensors are activated
f. Operation of the Hydraulic Ramp Manifold Solenoid
g. Hissing sound coming from the height control manifold when the solenoid-controlled relief valve opens
h. Detecting if the cupola is working properly (FSC Trouble shooting TTL 16)
i. Do audio alerts sound? (FSV Troubleshooting TTL 1)
j. MGS Ammunition Handler and Carousel rotation operations.
k. MGS Ammunition autoloader operations.
l. MGS replenisher operations.
m. MGS Turret traverse and elevation movement; Breech opening and closing; Rammer operations.
n. Pitch of the MGS Turret shall rise and fall in correlation to the Turret movement acceleration and deceleration.
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.
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 must 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 training system shall support the use of the MGS Breakout Box to the extent required to support the ELOs listed in the TTL. The training system shall support the use of the Firing Circuit Tester to the extent required to support the ELOs listed in the TTL. The training system(s) shall simulate the use of diagnostic techniques (BIT/Built-In-Test Equipment (BITE) and Maintenance Support Device (MSD)) and fault isolation of each vehicle. Faults reported by on-board vehicle computers to the MSD shall be retrievable by the MSD until either corrected by the student, removed by the instructor, or power is removed to the vehicle. The training system shall support the operation of the Maintenance Support Device (MSD) to retrieve fault codes from the Diagnostic Control Unit (DCU), Engine ECM and Power Pack Interface (PPI) unit. The simulation must show proper point conditions for all connector and troubleshooting points. Conditions for all test points simulated on a given device will be active, regardless of the scenario being executed.
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
c. Photo Tachometer
d. Radiator Testing Kit
e. Nitrogen Charging Kit to perform Height Management System calibration
f. Brake Drum Micrometer
g. Ultrasonic leak detector
h. External Compressed Air Source
i. Test Pressure Gage Assembly
j. Hydraulic Test Set
k. Fire Suppression System Test Set
l. HMS calibration tool
m. Maintenance Support Device (MSD)
n. Internal Combustion Tester
o. Pressure Gage
p. The ATGM simulation shall support the use of a 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).
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. Detailed diagnostics shall be available for selection at each student station and IOS, to assess the system health of that individual station. The diagnostic capabilities shall include testing the operation of the computers, peripheral equipment and other training system(s) hardware, and for identifying malfunctioning components.
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) daily readiness check, (2) performance monitoring (PM), and (3) fault detection and locating. The BIT shall provide an assessment of the overall training systems integrity in not more than five minutes upon command.
Daily readiness check program(s) shall be designed and implemented to enable operating personnel to determine that the training systems are ready for operation. Daily readiness check shall not exceed 15 minutes from power on until completion of daily readiness check. The initialization and start up time shall be 30 minutes from power off to initialization of scenario for training (30 minutes includes the daily readiness check).
The Performance Monitoring (PM) 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 an approved Army Gold Master Windows operating system. The PM function shall utilize the capabilities of the Windows Events viewer and logs provided by the operating system.
Event Viewer tracks information in several different logs. Windows Logs include:
· Application or program events. Events are classified as error, warning, or information, depending on the seriousness of the event. An error is a significant problem, such as loss of data. A warning is an event that isn't necessarily significant, but might indicate a possible future problem. An information event describes the successful operation of a program, driver, or service.
· Security-related events. These events are called audits and are described as successful or Failed depending on the event, such as whether a user trying to log on to Windows was successful.
· Setup events. Computers that are configured as domain controllers will have additional logs displayed here.
· System events. System events are logged by Windows and Windows system services, and are classified as error, warning, or information.
· Forwarded events. These events are forwarded to this log by other computers.
The logs provide the date, time, source and category of the error messages.
The Fault Localization (FL) component shall function off-line. The FL component shall require manual initiation. It will utilize COTS vendor-supplied diagnostic software and troubleshooting procedures. Upon indication of Failures of COTS equipment, diagnostic routines, procedures, test units, and other procedures shall be used to isolate faulty hardware to the extent provided by the vendor-supplied diagnostic routines and procedures. Computational systems shall provide an automated capability for verifying the operational readiness of all training system(s) functions and subsystems.
Device Specific Requirements IOS Capability Requirements The training system shall allow the instructor to select from one of 4 modes for training: classroom free-run, classroom lockstep, classroom free play, or workstation lockstep/free play. (Refer to Section 3.2.2 Training Execution Modes for explanation of each of these modes). When a student has received a NO-GO score for an ELO, the instructor shall be provided with the immediate capability to restart the student’s execution of that ELO in a workstation lockstep mode for remedial help.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .