N6134019R1203_DRAFT_DO1_VA_ICL_PerformanceSpecification.docx

MRTS 3D ACTS IDIQ DO

ICL Performance Specification

1 JUNE, 2018

MRTS 3D ACTS IDIQ DO

ICL Performance Specification

1 JUNE, 2018

PERFORMANCE SPECIFICATION

FOR

MRTS 3D® INTERNAL COUNTERMEASURES LAUNCHER (ICL) SIMULATION

DEPARTMENT OF THE NAVY

NAVAL AIR WARFARE CENTER

TRAINING SYSTEMS DIVISION

12211 SCIENCE DRIVE

ORLANDO, FL 32826-3275

APPROVED BY: DATE:

Mark Reemsnyder Lead Engineer, Undersea/MRTS 3D Code 4.6.8.4

APPROVED BY: DATE:

David Thomas Program Manager, Undersea/MRTS 3D Code 1.3.6.2.1

DISTRIBUTION STATEMENT C - Distribution authorized to U.S. Government agencies and their contractors. Other requests for this document shall be referred to COMMANDING OFFICER, NAVAL AIR WARFARE CENTER, TRAINING SYSTEMS DIVISION, 12211 Science Drive, Orlando, FL 32826-3224

ACTS IDIQ

DO# 0001

11 April, 2018

Multipurpose Reconfigurable Training System (MRTS) 3D, MRTS 3D, and the MRTS 3D logo are registered trademarks of the U.S. Navy

1. SCOPE

This Specification defines the effort required for the design, fabrication, installation, testing, and delivery of the VIRGINIA (VA) class submarine’s Internal Countermeasures Launch System (ICL) simulation, hereafter referred to as “MRTS 3D® ICL”. The MRTS 3D ICL shall provide US Navy VA class submarine ICL operator training for Navy personnel in grades E-3 and above in the rate of Machinist Mate Weapons. The MRTS 3D ICL shall be installed and have final testing conducted at the Advanced Computer-based Training System (ACTS) IDIQ contractor’s site.

1.1. Background

The MRTS 3D concept consists of networked, PC-based systems utilizing flat panel touch screen technology to simulate tactical equipment for operations and maintenance training. MRTS 3D uses the Unity 3D Game Engine and a MRTS 3D Instructor Operating System (IOS) Middleware and Software Development Kit (M&SDK), hereafter referred to as the MRTS 3D M&SDK. The MRTS 3D M&SDK supplements the Unity 3D gaming engine with software modules designed for reuse across multiple programs. All MRTS 3D software is either Government owned or royalty free and incurs no licensing fees. MRTS 3D provides a suitable training environment to support the hands-on, skills training required by the selected training tasks.

The Fleet would like to conduct operational training on the VA Class Submarine’s Internal Countermeasures Launch Systems on a MRTS 3D system.

1.2. System Overview

The MRTS 3D ICL simulates tactical system components necessary for an ICL operator training using the MRTS 3D concept.

2. APPLICABLE DOCUMENTS

The following Government Furnished Documents (GFD) form a part of this SOW to the extent specified herein. In the event of a conflict between documents referenced herein and the contents of this SOW, the contents of this SOW take precedence. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

2.1. Referenced Government Documents

The following specifications, standards, and handbooks of the exact revision listed below form a part of this specification to the extent specified herein.

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

2.2. Other Government documents, drawings, publications and media Government documents, drawings, publications and media of the ACTS IDIQ SOW shall be used as needed.

2.3. Non-Government Furnished Documents

Non-Government documents listed in the ACTS IDIQ SOW shall be used as needed.

2.4. Government Furnished Information (GFI)

MRTS Documentation:

Fault Insertion Guide (FIG) template

Self-explanatory

ICL Documentation:

S9SSN-ZQ-SSM-CQ0 SHIP SYSTEMS MANUAL SSN774 CLASS

SSM 2-23-1 INTERNAL COUNTERMEASURE LAUNCHER SYSTEM CHG 3

Ship Systems Operation Volume 6. Internal Countermeasure Launcher System Operation OI 631-10.

S9SSN-ZQ-SSM-LK0/(U)774V6P3

SSN774 CLASS WEAPON DELIVERY SYSTEMS EQUIPMENT MANUAL; VOLUME 3 PART 1, INTERNAL COUNTERMEASURE LAUNCHER SYSTEM MECHANICAL EQUIPMENT Internal Countermeasure Launcher System Operation Manual. Configuration of the installed systems, equipment, and components.

3. REQUIREMENTS

3.1. Performance and functional requirements

3.1.1. Software Requirements

3.1.1.1. Simulation Functionality

3.1.1.1.1. The ICL simulation shall enable the student to virtually execute all procedures in the MRTS 3D ICL Operating Procedure (OP) and Casualty Procedure (CP) Spreadsheet.

3.1.1.1.2. The ICL simulation shall allow the student to perform procedural steps in a logical order as defined in the introduction section of OD 44979 Volume 1 and OD 44979 Vol 2 Part 2 Sec E, Procedural Guide (PG) 9, page PG 9-1, “scope” section.

3.1.1.1.3. The ICL simulation shall simulate the actions and consequences of the actual system and the individuals involved when a student deviates from the operation procedure.

3.1.1.1.4. The ICL simulation shall have the “ghost hands” capability as described in the MRTS 3D Style Guide Specification and IAW the MRTS M&SDK.

3.1.1.1.5. The MRTS 3D ICL shall correctly simulate the interlocks that exist on the actual VIRGINIA ICL as described in the associated OD 44979 and technical documentation:

3.1.1.1.5.3. Section 2.4 of S9SSN-ZQ-SSM-CQ0, SSN774 Class Volume 2, Part 23, Introduction to Countermeasure Launcher System

3.1.1.2. Instructor Operating Station:

3.1.1.2.1. Instructor Operator Station (IOS) Software

3.1.1.2.1.1. The IOS shall provide the capability to connect to and manage up to forty (40) Student Stations. This functionality is provided by the MRTS 3D IOS Framework. The contractor shall ensure the ICL IOS plugin connectivity requirements do not degrade this capability.

3.1.1.2.1.2. The IOS shall have the controls and displays to assign each student to a Student Station. This functionality is provided by the MRTS 3D IOS Framework. The ICL IOS plugin shall receive student station assignments from the MRTS 3D IOS Framework.

3.1.1.2.1.3. The IOS software shall have controls and displays to task each student independently or in groups. This functionality shall be built into an IOS plugin IAW the MRTS 3D M&SDK.

3.1.1.2.1.4. The IOS software shall be able to have controls and displays to assign operations procedures designated in 3.1.1.3 Student Station Software to students. This functionality shall be built into an IOS ICL plugin IAW the MRTS 3D M&SDK.

3.1.1.2.1.5. The IOS software shall have controls and displays to assign multiple students, up to forty (40) and including the instructor, and Student Stations to a common virtual ship environment. Student, station and group assignment is provided by the MRTS 3D IOS Framework. The contractor shall build the ICL specific group requirements into the IOS ICL plugin IAW the MRTS 3D Style Guide Specification.

3.1.1.2.1.6. The IOS software shall have the controls and displays to designate a workstation involved in a procedure be operated by a student or simulated.

3.1.1.2.1.7. The IOS software shall have controls and displays to insert procedure faults listed under the fault sections of Section 3.1.1.3 Student Station Software into the virtual ship instances for any one of the forty (40) Student Stations or a collaborating group.

3.1.1.2.2. The IOS software shall have controls and displays to track and monitor the progress of each student. Many of these features are provided by the MRTS 3D IOS Framework or in part by the MRTS 3D SDK through an API. The contractor shall determine the appropriate method and ensure they are used and supported, and augmented where required.

3.1.1.2.2.1. The IOS software shall allow the instructor to track each student at the procedural level.

3.1.1.2.2.2. The IOS software shall retain student performance data and consolidate into a single report for each student.

3.1.1.2.2.3. Once an operator procedure, corrective maintenance procedure or a fault has been inserted into a Student Station, the IOS shall be able to provide a real-time display of the procedural steps being performed by each student.

3.1.1.2.2.4. The IOS software shall display the procedure assigned to a student in its entirety, including all subtasks, and track the student’s progress on it IAW the MRTS 3D Style Guide Specification. The following rules shall apply:

3.1.1.2.2.4.1. The IOS shall mark each step in the procedure IAW the MRTS 3D Style Guide Specification.

3.1.1.2.2.4.2. The IOS shall display student entries from the Student Station procedure display as described below in section 3.1.1.6 exactly as the student enters it as they check off their procedure list.

3.1.1.2.2.4.3. Student station procedure list entries shall be colored successful if the student marks them off at the time the IOS considers this step to be the current or previous step, otherwise it shall be colored as a deviation IAW the MRTS 3D Style Guide Specification.

3.1.1.2.2.4.4. The IOS software shall allow the instructor to determine where a student deviated from the applicable procedure.

3.1.1.2.2.4.5. During execution of operator procedures at a Student Station, when the student performs an invalid procedural compliance step, the IOS shall display an error message indicating as such.

3.1.1.2.2.4.6. Once a procedure has been completed by the student, the IOS shall indicate as such for that student.

3.1.1.2.2.4.7. Once a procedure has been completed by the student or manually cleared by the Instructor, the IOS shall display the total number of invalid procedural compliance steps that the student performed during execution of that procedure.

3.1.1.2.2.4.8. The invalid procedural compliance logging shall reset each time a new fault is inserted at the IOS.

3.1.1.2.2.5. The IOS shall log and save a history of each student’s performance data for each procedure performed to include the following:

3.1.1.2.2.5.1. Student name

3.1.1.2.2.5.2. Procedure title

3.1.1.2.2.5.3. Faults inserted

3.1.1.2.2.5.4. Completion status for latest attempt

3.1.1.2.2.5.5. Time on procedure for latest attempt

3.1.1.2.2.5.6. Number of attempts

3.1.1.2.2.5.7. Number of failed attempts

3.1.1.2.2.5.8. Failure to select required safety Equipment

3.1.1.2.2.5.9. Safety Violations

3.1.1.2.2.5.10. Instructor Notes

3.1.1.2.2.6. The IOS shall provide the capability for the Instructor to create notes pertinent to evaluating each student’s performance.

3.1.1.2.2.7. The IOS shall provide the Instructor the capability to generate a report of the data defined in above in Adobe PDF format, with the file’s location specified by the Instructor via a standard Windows file-save interface.

3.1.1.2.3. Communications

3.1.1.2.3.1. Audio Communications (comms) - All audio comms features of the MRTS 3D IOS Framework shall be supported. Audio comms is part of the core MRTS 3D SDK IOS Framework capabilities through the Student Management System (SMS). In particular, the following features shall be available:

3.1.1.2.3.1.1. The IOS software shall allow the instructor to talk to an individual student via the MRTS 3D SMS.

3.1.1.2.3.1.2. The IOS software shall allow the instructor to talk with groups of students in a virtual ship instance via the MRTS 3D SMS.

3.1.1.2.3.1.3. The IOS software shall allow the instructor to talk to broadcast to all students via the MRTS 3D SMS.

3.1.1.2.3.2. Chat Communications – All chat features of the MRTS 3D IOS Framework shall be supported. Chat is part of the core MRTS 3D SDK IOS Framework capabilities.

3.1.1.3. Student Station Software

3.1.1.3.1. ICL Equipment Simulation

ICL Student Station software shall provide simulations of the following equipment to support training for each ICL subsystem to the extent necessary to perform the procedures in the MRTS 3D ICL OP and CP Spreadsheet.

3.1.1.3.1.1. Port Side Wall

3.1.1.3.1.1.1. All components listed below shall have all the necessary functionality required to train the procedures in OD 44979 Volume 2 Part 2 Section E (Appendix A).

3.1.1.3.1.1.1.1. Primary and Secondary Launcher Barrel Assemblies.

3.1.1.3.1.1.1.2. Primary and Secondary Launcher Support Superstructure (Gray and Green) Components

3.1.1.3.1.1.1.3. Piping

3.1.1.3.1.1.1.4. Hull Valve ICL-31

3.1.1.3.1.1.1.5. Backup Hull Valve ICL-30

3.1.1.3.1.2. Forward Side Wall

3.1.1.3.1.2.1. All components listed below shall have all the necessary functionality required to train the procedures in OD 44979 Volume 2 Part 2 Section E (Appendix A).

3.1.1.3.1.2.1.1. Impulse Cylinder Isolation Box and Valve ICL-21

3.1.1.3.1.2.1.2. Secondary Launcher Impulse Cylinder

3.1.1.3.1.2.1.3. Impulse Cylinder Isolation Box and Valve ICL-15

3.1.1.3.1.2.1.4. Primary Launcher Impulse Cylinder

3.1.1.3.1.2.1.5. Launcher Air Firing Valve (Reference Figure 11 - Launcher Air Firing Valve)

3.1.1.3.1.2.2. The Internal CM Launcher Control and Display Panel (LCDP) shall implement all necessary controls, buttons and indicators available on the control panel and displays required to train the procedures in OD 44979 Volume 2 Part 2 Section E (Appendix A). Reference Figure 9 - Internal CM Launcher Control and Display Panel.

3.1.1.3.1.3. Starboard Side Wall

3.1.1.3.1.3.1. All components listed below shall have all the necessary functionality required to train the procedures in OD 44979 Volume 2 Part 2 Section E (Appendix A).

3.1.1.3.1.3.1.1. Launcher Gauge Board

3.1.1.3.1.3.1.2. Hydraulic Hand Pump Handle

3.1.1.3.1.3.1.3. ICL ON/OFF Rotary Power Switch

3.1.1.3.1.4. AFT Side Wall

3.1.1.3.1.4.1. All components listed below shall have all the necessary functionality required to train the procedures in OD 44979 Volume 2 Part 2 Section E (Appendix A).

3.1.1.3.1.4.1.1. ICL Hand Pump Station

3.1.1.3.1.4.1.2. PYRO Wrench Locker

3.1.1.3.1.4.1.3. Loading Stick

3.1.1.3.1.4.1.4. EAB Stowage Locker

3.1.1.3.1.4.1.5. Expandable Probes Connector Box

3.1.1.3.1.5. Ceiling

3.1.1.3.1.5.1. All components listed below shall have all the necessary functionality required to train the procedures in OD 44979 Volume 2 Part 2 Section E (Appendix A).

3.1.1.3.1.5.1.1. Primary Control Valve Manifolds

3.1.1.3.1.5.1.2. Secondary Control Valve Manifolds

3.1.1.3.1.6. Virtual Environment

3.1.1.3.1.6.1. In order to simulate the ICL tactical system for training, the ICL student station software shall depict the required portions of a VA class Block IV submarine’s Forward Compartment Middle Level (FCML) as depicted in Figure 1 - VA Wardroom Stateroom No. 1 and ICL area. The dashed green line in Figure 1 - VA Wardroom Stateroom No. 1 depicts where to cut off the virtual environment with sea foam green walls.

Figure 1 - VA Wardroom Stateroom No. 1 and ICL area

3.1.1.3.1.6.2. The MRTS 3D VA ICL simulation shall realistically depict the dimensions and layout of all spaces that contain the equipment necessary to perform the operations procedures in OD 44979 Volume 2 Part 2 Section E (Appendix A). Reference Figure 2 - ICL area Port View.

Figure 2 - ICL area Port View

3.1.1.3.1.6.3. The ICL student station software shall depict the room configuration in a VA Class Submarine Internal Countermeasure Launcher (ICL) Room as depicted in Figure 3 - Internal Countermeasure Launcher Room Arrangement.

Figure 3 - Internal Countermeasure Launcher Room Arrangement

3.1.1.3.1.6.4. The ICL VA class submarine Internal Countermeasure Launcher (ICL) Room shall realistically depict the dimensions and layout of all spaces that contain the equipment necessary to perform the operations procedures in OD 44979 Volume 2 Part 2 Section E (Appendix A). Reference Figure 5 - From ICL to Stateroom Starboard View, Figure 6 - ICL Room Aft View, Figure 7 - ICL Room Port View, Figure 8 - ICL Room Fwd View, and Figure 11 - Launcher Air Firing Valve.

Figure 4 - From Passageway into ICL Port View

Figure 5 - From ICL to Stateroom Starboard View

Figure 6 - ICL Room Aft View

Figure 7 - ICL Room Port View

Figure 8 - ICL Room Fwd View

Figure 9 - Internal CM Launcher Control and Display Panel

Figure 10 - Launcher Air Firing Valve

3.1.1.3.2. Simulated Operating Procedures

3.1.1.3.2.1. The ICL simulation shall enable the student to virtually execute the Procedural Guide, the Operating Procedures and Checklists found in the MRTS 3D ICL OP and CP Spreadsheet. The MRTS 3D ICL OP and CP Spreadsheet was derived from OD 44979 Volume 2 Part 2 Section E. Within the MRTS 3D ICL OP and CP there are two tabs (Operating Procedures and Casualty Procedures). Reference above mentioned GFI as necessary to derive all the ICL functionalities needed to support procedural execution.

3.1.1.3.2.2. All tools and cleaning methods shall be implemented in the simulation IAW with the MRTS 3D Style Guide Specification.

3.1.1.3.3. Simulated Casualty Procedures

3.1.1.3.3.1. The ICL simulation shall enable the student to virtually execute the Casualty Procedures found in the MRTS 3D ICL OP and CP Spreadsheet. The MRTS 3D ICL OP and CP Spreadsheet was derived from OD 44979 Volume 2 Part 2 Section E. Reference above mentioned GFI as necessary to derive all the ICL functionalities needed to support procedural execution

3.1.1.3.3.2. All tools and cleaning methods shall be implemented in the simulation IAW with the Style Guide.

3.1.1.3.4. Student Station Procedure Checklists (Example)

3.1.1.3.4.1. The student station software shall display the derived procedure list as defined in the MRTS 3D ICL OP and CP Spreadsheet for the appropriate procedure assigned to the student.

3.1.1.3.4.2. The student shall be able to check off the list IAW a circle/slash method defined to be (see Figure 11 – Procedure Checking Example):

3.1.1.3.4.2.1. Each step in the procedure shall initially have a blank bar listed to the right of it as shown in the OD 44979 and other GFI documents.

3.1.1.3.4.2.2. The student shall be able to click on each bar in the procedure list and select an appropriate status from a list.

3.1.1.3.4.2.3. A “O”, or circle, shall be shown indicating that the student has begun the step.

3.1.1.3.4.2.4. A “O”, or circle, with a “X”, or slash, through it shall be shown to indicate that the student believes they have completed the step.

3.1.1.3.4.2.5. Procedure step status shall be sent to the IOS.

OPERATING PROCEDURE 1.11

PLACING CD INTO LAPTOP CD TRAY

OPERATING PROCEDURES/CHECKLISTS

PG3………… LAPTOP COMPUTERS

EQUIPMENT/TOOLS

Laptop Compact Disc (CD)

SUPPORTING DOCUMENTATION

NAVY LP023-HG-YAT-010

OPERATIONS

1. At laptop open CD Tray by pressing “OPEN”

2. Place CD inside the laptop’s CD Tray and press down until you hear a click

3. Open Windows Explorer

Figure 11 – Procedure Checking Example

3.1.1.3.5. Communications

3.1.1.3.5.1. Audio Communications (comms) - MRTS 3D audio comms is a core feature of the MRTS 3D M&SDK through the Student Management System (SMS). In particular, the following features shall be available:

3.1.1.3.5.1.1. The student station software shall allow the student to talk to the instructor via the MRTS 3D SMS.

3.1.1.3.5.1.2. The student station software shall allow the student to talk with their assigned group of students in a virtual ship instance via the MRTS 3D SMS.

3.1.1.3.5.2. Chat Communications

3.1.1.3.5.2.1. All student stations shall have chat capabilities. MRTS 3D chat is a core feature of the MRTS 3D M&SDK through the Student Management System (SMS).

3.1.1.3.5.2.2. Incoming chat messages shall appear in the Student Station Heads Up Display (HUD) as defined in the MRTS 3D Style Guide Specification.

3.1.1.3.5.3. Canned Responses – During performance of a procedure, the student shall have the capability to input system reports to external watch-standers. External watch-standers shall be simulated and respond appropriately while the student performs the procedure. As the student checks off procedure steps that involve reporting to external watch-standers, the student station software shall automatically initiate the report and respond with the appropriate watch-standers response. Automated watch-standers shall respond with both audio and chat messages replicating actual watch-stander responses.

3.1.1.3.5.3.1. For example, on board the actual submarine, the Internal Countermeasures Remote Control Panel is located in the Command and Control Center (CACC). Inside the MRTS 3D simulation, when student transfers control of the Internal Countermeasures to the CACC, the student software shall notify the IOS and allow the simulated watch-stander to operate the CACC, e.g. launch the primary and secondary countermeasures for each student at the appropriate step in the procedures to be simulated.

image2.png image3.jpeg image4.png image5.png image6.png image7.png image8.jpeg image9.png image10.jpeg image11.jpeg image12.jpeg image13.png image14.png image1.jpeg