NSST_PRF_210025A(23MAY2023)FINAL.pdf

PRF 210025A

23 MAY 2023

SUPERSEDING

PRF 210025

21 SEP 2022

SYSTEM SPECIFICATION

FOR

DEVICE 1B17

THE NAVIGATION, SEAMANSHIP, AND SHIPHANDLING TRAINER (NSST)

DEPARTMENT OF THE NAVY

NAVAL AIR WARFARE CENTER

TRAINING SYSTEMS DIVISION

12350 RESEARCH PARKWAY

ORLANDO, FL 32826-3275

APPROVED BY:

Luis DeJesus Project Manager, Surface Warfare Training Products Branch

Daniel Chwalisz Head, Surface Warfare Training Branch

Chad Guillet Navy Integration Management Branch Head/APML (GT411)

DISTRIBUTION STATEMENT D - Distribution authorized to the Department of Defense and U.S. DoD contractors only for Administrative or Operational Use, 21 SEP 2022. Other requests for this document shall be referred to Commander, Naval Air Warfare Center Training Systems Division (NAWCTSD PJM), 12211 Science Drive, Orlando, FL 32826.

DESTRUCTION NOTICE - For unclassified, limited distribution documents, destroy by a method that prevents disclosure of contents or reconstruction of the document.

ii

1. SCOPE

2. APPLICABLE DOCUMENTS

2.1 General

2.2 Government documents

2.2.1 Specifications, standards, and handbooks

2.2.2 Other Government documents, drawings, and publications

2.3 Non-Government publications

2.4 Order of precedence

3. REQUIREMENTS

3.1 Performance and functional requirements

3.1.1 Architectural Requirements

3.1.1.1 Proprietary and Vendor-Specific Software

3.1.1.2 Simulation Runtime Interface

3.1.1.2.1 Application Program Interface (API)

3.1.1.2.2 High Level Architecture (HLA) and Distributed Interface

Simulation (DIS)

3.1.1.3 Scalability

3.1.1.4 Maritime Simulation Software

3.1.1.5 Software licenses

3.1.1.5.1 Enterprise license agreement

3.1.2 Watchstander Task Requirements

3.1.2.1 General Navigation Tasks

3.1.2.2 General Seamanship Tasks

3.1.2.3 General Shiphandling Tasks

3.1.2.4 Communication Tasks

3.1.2.5 Mooring and Anchoring Tasks

3.1.2.6 Connected Replenishment (CONREP)

3.1.2.7 Towing Tasks

3.1.2.8 Other Special Evolution Tasks

3.1.2.9 Casualty, Emergency, and Weather Response Tasks

3.1.2.10 Electronic Chart Operation Tasks

3.1.2.11 Radar and Automatic Radar Plotting Aid (ARPA) Operation Tasks

3.1.2.12 NAVDORM Checklist Tasks

3.1.3 Simulation Requirements

3.1.3.1 Physics Simulations

3.1.3.1.1 Ownship physics

3.1.3.1.2 Traffic vessel physics

3.1.3.1.2.1 Traffic vessel physics effects

3.1.3.1.3 Floating object physics

3.1.3.1.4 Collision and Allision

3.1.3.1.5 Anchor physics

3.1.3.2 Visualization and sensor simulations

3.1.3.2.1 Contacts

iii

3.1.3.2.2 Celestial

3.1.3.2.3 Navigational aids

3.1.3.2.4 Geographic features

3.1.3.2.5 Signals

3.1.3.2.6 Depth and grounding

3.1.3.2.7 Lines

3.1.3.2.8 Tugs

3.1.3.2.9 CONREP

3.1.3.2.10 Flight deck

3.1.3.2.11 Boat deck

3.1.3.2.12 Buoy mooring

3.1.3.2.13 Towing hawser

3.1.3.2.14 Weapons

3.1.3.2.14.1 Weapon types

3.1.3.2.14.2 Engagement orders

3.1.3.2.14.3 Damage effects

3.1.3.2.14.4 Anti-terrorism/force protection (ATFP) threat cues

3.1.3.2.14.5 Warning flare

3.1.3.2.14.6 Torpedo

3.1.3.3 Sound simulation requirements

3.1.3.4 Environmental Simulations

3.1.3.4.1 Wind

3.1.3.4.2 Tide and Current

3.1.3.4.3 Waves

3.1.3.4.4 Weather

3.1.3.4.5 Environmental Effect Zones

3.1.3.4.5.1 Geographic Lee

3.1.3.4.5.2 Large Vessel Lee

3.1.3.4.5.3 Pier Slip

3.1.3.4.5.4 Fog Bank

3.1.3.4.5.5 Weather Cell

3.1.3.5 Ship system simulation

3.1.3.5.1 Propulsion systems

3.1.3.5.2 Steering Systems

3.1.3.5.3 Gyrocompass simulations

3.1.3.5.4 Magnetic compass simulations

3.1.3.5.5 Whistle simulations

3.1.3.5.6 Stadimeter and laser range finder simulations

3.1.3.5.7 Global positioning system (GPS) simulations

3.1.3.5.8 Fathometer simulations

3.1.3.5.9 Towed bodies

3.1.3.5.10 Chronometer

3.1.3.5.11 Course and Speed sensors

iv

3.1.3.5.12 Ship Control GUIs and Ship Control Consoles (SCC)

3.1.3.5.12.1 Universal Ship Control GUI

3.1.3.5.12.2 Desktop Ship Control Console

3.1.3.5.12.3 Universal Ship Control Console

3.1.3.5.12.4 Ship Control System – Government (SCS-GOV) GUI

3.1.3.5.12.5 Ship Control System – Government (SCS-GOV) SCC

3.1.3.5.12.6 Integrated Bridge Navigation System (IBNS) GUI

3.1.3.5.12.7 Integrated Bridge Navigation System (IBNS) SCC

3.1.3.5.13 Bridge Manual Pump Controller

3.1.3.5.14 Digital Rudder Angle Display System (DRADIS)

3.1.3.5.15 Navigation Data Display (NDD)

3.1.3.6 Virtual watchstander system

3.1.3.7 Electronic chart simulations

3.1.3.8 Radar simulations

3.1.3.8.1 SPS-73 Radar Console

3.1.3.8.2 SPA-25H Radar Console

3.1.3.8.3 Reconfigurable CIC and Bright Bridge Console

3.1.3.9 Automated Identification System (AIS)

3.1.3.10 Remote Optical Sight (ROS)

3.1.3.11 Communication systems

3.1.3.11.1 External communication system

3.1.3.11.2 Internal communication system

3.1.3.11.3 LS-654

3.1.3.11.4 Flag hoist communication systems

3.1.3.11.5 Flashing light communication systems

3.1.4 Watch station Requirements

3.1.4.1 NSST Devices

3.1.4.1.1 Conning Officer NSST (NSST-1)

3.1.4.1.1.1 Conning Officer (CONN) Watch Station

3.1.4.1.2 Advanced Conning Officer NSST (NSST-2)

3.1.4.1.2.1 CONN Watch Station

3.1.4.1.2.2 Ownship Control Station

3.1.4.1.2.3 CONN Support Watch Station

3.1.4.1.3 Bridge Wing NSST (NSST-3)

3.1.4.1.3.1 Bridge Wing Watch Station

3.1.4.1.4 Bridge Team NSST (NSST-4)

3.1.4.1.4.1 Bridge Officer Watch Station

3.1.4.1.4.2 Helm Station

3.1.4.1.4.3 Radar and Communication Station

3.1.4.1.4.4 Navigation Station

3.1.4.1.4.5 CIC Station

3.1.4.1.5 Full Navigation Team NSST (NSST-5)

3.1.4.1.5.1 Bridge Officer Watch Station

v

3.1.4.1.5.2 Port and Starboard Bridge Wing Stations

3.1.4.1.5.3 Helm Station

3.1.4.1.5.4 Radar and Communication Station

3.1.4.1.5.5 Bridge Navigation Station

3.1.4.1.5.6 Boatswain Mate of the Watch (BMOW) Station

3.1.4.1.5.7 Bright Bridge Station

3.1.4.1.5.8 Hot Wash Station

3.1.4.1.5.9 Chart Room Station

3.1.4.1.5.10 Combat Information Center (CIC) Stations

3.1.4.1.5.11 After Steering Station

3.1.4.1.5.12 NSST-5 Watch Station Layout

3.1.4.1.6 Reconfigurable Full Navigation Team NSST (NSST-5A)

3.1.4.1.6.1 NSST-5A Re-configurability

3.1.4.1.6.2 NSST-5A Watch Station Layout

3.1.4.1.7 Radar Navigation (RADNAV) NSST (NSST-6)

3.1.4.1.7.1 CIC-1 station

3.1.4.1.7.2 CIC-2/chart room station

3.1.4.1.7.3 CIC-3/bridge station

3.1.4.2 General Watch Station Requirements

3.1.4.2.1 Watch Station Assignment Functionality

3.1.4.2.2 Ship Control Console (SCC)

3.1.5 Instructional Station Requirements

3.1.5.1 Instructor Operator Station (IOS)

3.1.5.2 Master IOS (MIOS)

3.1.5.2.1 Controlled Access MIOS tools and functionality

3.1.5.3 Briefing station

3.1.5.4 Integrated Scenario System

3.1.6 Maintenance Station Requirements

3.1.6.1 Dual Baseline Support

3.1.7 Database Requirements

3.1.7.1 Geographic Database Requirements

3.1.7.2 Ownship Model Requirements

3.1.7.3 Entity Model Requirements

3.1.8 General System Requirements

3.1.8.1 Procedural Thresholds

3.1.8.2 Indications

3.1.8.3 Stress Performance

3.1.8.4 Light Management

3.1.8.5 Instructor Operator Workload Management

3.1.9 NSST Development Seat Requirements

3.1.9.1 Development Seat – Database

3.1.9.2 Development Seat - API

3.1.9.3 Development Seat – Cold Start

vi

3.1.10 Visual Display System (VDS) Requirements

3.1.10.1 Seamless Projection Display System Requirements

3.1.10.1.1 Day and Night Training Modes

3.1.10.1.2 Projection Screen Requirements

3.1.10.1.3 Projection System Mounting Structure Requirements

3.1.10.2 Flat Panel Display System Requirements

3.1.10.3 Virtual Reality (VR) Display System Requirements

3.1.10.4 Panorama Display

3.1.10.5 VDS Testing Tool Requirements

3.1.11 Site Specific Requirements

3.1.11.1 San Diego Site Specific Requirements

3.1.11.2 Norfolk Site Specific Requirements

3.1.11.3 Yokosuka Site Specific Requirements

3.1.11.4 Sasebo Site Specific Requirements

3.1.11.5 Pearl Harbor Site Specific Requirements

3.1.11.6 Everett Site Specific Requirements

3.1.11.7 Mayport Site Specific Requirements

3.1.11.8 Rota Site Specific Requirements

3.1.11.9 Government In-plant systems

3.2 Additional Requirements

3.2.1 Additional Database Requirements

3.2.1.1 Additional Geographic Databases

3.2.1.2 Additional Ownship Models

3.2.1.3 Additional Entity Models

3.2.2 Baseline Modifications

3.3 Ancillary Requirements

3.3.1 System stability

3.3.2 Maintainability

3.3.3 Reliability

3.3.4 Environmental conditions

3.3.5 Materials and processes

3.3.5.1 Parts

3.3.5.1.1 Custom designed microelectronic devices

3.3.5.1.2 Power supplies

3.3.5.2 Materials

3.3.5.2.1 Flammable materials

3.3.5.2.2 Fungus-inert materials

3.3.5.2.3 Hazardous materials

3.3.5.2.4 Metals

3.3.5.2.5 Wood products

3.3.5.2.6 Radioactive material

3.3.5.3 Manufacturing processes

3.3.6 Nameplates and product markings

vii

3.3.6.1 Device nameplate

3.3.6.2 Marking of units, assemblies, subassemblies, and parts

3.3.6.2.1 Units

3.3.6.2.2 Plug-in assemblies

3.3.6.2.3 Fuse holders

3.3.6.2.4 Function and operation marking

3.3.6.2.5 Sockets

3.3.6.2.6 Printed wiring boards

3.3.6.2.7 Terminals, terminal blocks, and strips

3.3.6.2.8 Electrostatic Discharge (ESD) marking

3.3.6.2.8.1 ESD sensitive equipment

3.3.6.3 Reference designators

3.3.6.4 Cable and wire markings

3.3.6.4.1 Damage due to markings

3.3.6.4.2 Cable and wire marking location

3.3.6.4.3 Cable marking method

3.3.6.4.4 Cable and wire marking information

3.3.6.4.4.1 “W” and “P” cable and wire designations

3.3.6.4.4.2 To-from designators

3.3.6.4.4.3 Assembly and part number

3.3.6.5 Warning marking for simulated and modified equipment

3.3.6.6 Safety markings

3.3.6.6.1 Safety marking of guards, barriers, and access doors, covers, and plates

3.3.6.6.2 Marking of internal safety hazards

3.3.6.6.3 Equipment energized from multiple power sources

3.3.6.7 Hardware warranty markings

3.3.7 Electromagnetic Environmental Effects (E3)

3.3.7.1 Compromising emanations

3.3.8 Safety

3.3.9 Human engineering

3.3.9.1 Human engineering performance

3.3.10 Security and privacy

3.3.10.1 Cybersecurity

3.3.10.2 Processing of national security information

3.3.10.3 Cybersecurity requirements for operating systems

3.3.10.4 Network devices

3.3.10.5 Intrusion detection and virus protection

3.3.10.5.1 HBSS modules

3.3.10.6 Configuration criteria

3.3.10.6.1 Configuration criteria order of precedence

3.3.10.7 Audit logging

3.3.10.8 Software management system

viii

3.3.10.9 Backup management system

3.3.10.10 Encryption

3.3.10.10.1.1 Cryptography requirements

3.3.10.10.1.2 Recovery of encrypted data

3.3.11 Computational system requirements

3.3.11.1 Modular design

3.3.11.2 Computational system hardware

3.3.11.2.1 Computational system hardware fail-safe

3.3.11.2.2 Computational hardware components and peripherals

3.3.11.2.2.1 Computers

3.3.11.2.2.2 Computer networks

3.3.11.2.2.3 Computer mass storage devices

3.3.11.2.2.4 Computer Displays

3.3.11.2.2.5 Computer display touchscreens

3.3.11.3 Training device software

3.3.11.3.1 Software Higher Order Languages (HOLs)

3.3.11.3.2 Software stability and reliability

3.3.11.3.3 Software failures

3.3.11.3.4 Software coding and style

3.3.11.3.4.1 Header blocks

3.3.11.3.4.2 Source code commenting

3.3.11.3.4.3 Source code readability

3.3.12 Logistics

3.3.12.1 Maintenance

3.3.12.1.1 Maintenance concept

3.3.12.1.2 Maintenance design

3.3.12.1.2.1 Tools

3.3.12.1.3 Enclosure Lighting

3.3.12.1.4 Maintenance intercommunications system

3.3.12.1.5 Accessibility

3.3.12.1.6 Cable slack

3.3.13 Facilities and facility equipment

3.3.13.1 Trainer power requirements

3.3.13.1.1 Uninterruptible Power Supply (UPS)

3.3.13.2 Grounding

3.3.14 Workmanship

3.3.14.1 Cleaning

3.3.14.2 Threaded fasteners

3.3.14.3 Wiring

3.3.14.3.1 Harnesses and cable form containment

3.3.14.3.2 Insulation deformation

3.3.14.3.3 Burns, abrading, and pinch marks

3.3.14.3.4 Wires and cables clearance

ix

3.3.14.4 Shielding

3.3.14.4.1 Fraying

4. VERIFICATION

4.1 Methods of verification

4.2 Classification of verifications

4.3 Inspections and tests

4.3.1 Verification of Architectural Requirements

4.3.2 Development Seat Verification

4.3.3 Verification of Simulation and Ownship Models

4.3.3.1 Virtual Watchstander System Verification

4.3.3.2 Validation of Simulation and Ownship Models

4.3.4 Verification of Geographic Databases

4.3.5 Verification of Entity Models

4.3.6 Station Verification

4.3.6.1 Stress tests

4.3.6.2 Workload assessment

4.3.7 Visual system tests

4.3.7.1 Visual system maintenance test

4.3.7.2 Luminance verification method

4.3.7.3 Luminance uniformity verification method

4.3.7.4 Contrast ratio verification method

4.3.7.5 Color Uniformity verification method

4.3.7.6 Geometric accuracy verification

4.3.7.6.1 Total Geometric Distortion verification method

4.3.7.6.2 Relative Geometric Distortion verification method

4.3.7.7 Resolution verification method

4.3.7.8 Image stability

4.3.7.9 Gamma Verification

4.3.7.10 VR Display Bearing Correlation Error Verification

4.3.8 Verification of Watchstander Task Requirements

4.3.9 Ancillary and Workmanship Verification

4.3.9.1 System stability verification

4.3.9.2 Reliability assessment

4.3.9.3 Maintainability assessment

4.3.9.3.1 Component failure demonstration

4.3.9.3.2 Facility power loss demonstration

4.3.9.3.3 Instability recovery demonstration

4.3.9.4 Cybersecurity verifications

5. Packaging, Handling, Storage, & Transportation (PHS&T)

6. NOTES

6.1 Definitions

6.1.1 Failure definitions and criteria

6.1.1.1 Chargeable failures

x

6.1.1.2 Non-chargeable failures

6.1.1.3 Non-relevant failures

6.1.1.4 Relevant failures

6.1.2 IA-Enabled Operating System

6.1.3 Navigation terms

6.1.4 Operator Action

6.1.5 Operational State

6.1.7 Trainer Peculiar Equipment (TPE)

6.1.8 User Interface

6.1.9 Verification methods

6.1.9.1 Analysis

6.1.9.2 Demonstration

6.1.9.3 Examination

6.1.9.4 Test

xi

FIGURES

Fig. No. Title Page FIGURE 1. OJ-727A Stand-Alone Operator (SAOP) Console FIGURE 2. SPA-25H Stand Up Configuration Console FIGURE 3. Reconfigurable CIC and Bright Bridge Console FIGURE 4. Sample Trainer Nameplate FIGURE 5. Unit ID Plate FIGURE 6. ESD Symbols FIGURE 7. ESD Caution Label FIGURE 8. Examples of Cable Markings FIGURE 9. Trainer Use Only Identification FIGURE 10. Multiple Power Source Label FIGURE 11. Warranted Item Label

System Specification For

Device 1B17 Navigation, Seamanship, and Shiphandling Trainer (NSST)

1. SCOPE

This specification establishes the performance requirements for the design, development, fabrication, and test of device 1B17, NSST, for the delivery and modification of new and existing NSS training sites.

2. APPLICABLE DOCUMENTS

2.1 General

The documents listed in this section are specified in sections 3, 4, or 5 of this specification.

While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet the specified requirements of documents cited in sections 3, 4, or 5 of this specification, whether or not they are listed in this “Applicable Documents” section.

2.2 Government documents

2.2.1 Specifications, standards, and handbooks

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

Department of Defense (DoD) Standard Practices

MIL-STD-130N - Identification Marking of U.S. Military Property MIL-STD-461G - Requirements for the Control of Electromagnetic

Interference Characteristics of Subsystems and Equipment

MIL-STD-464D - Electromagnetic Environmental Effects Requirements for Systems

MIL-STD-1472H - Human Engineering (Copies of these documents are available online at http://quicksearch.dla.mil/)

2.2.2 Other Government documents, drawings, and publications

The following Government documents, drawings, and publications of the exact revision level shown form a part of this document to the extent specified herein.

DoD Handbooks MIL-HDBK-454C - General Guidelines For Electronic Equipment MIL-HDBK-470A - Designing and Developing Maintainable Products and Systems (Copies of these documents are available online at http://quicksearch.dla.mil/) http://quicksearch.dla.mil/ http://quicksearch.dla.mil/

DoD Security Documents

DODI 8510.01 - Risk Management Framework (RMF) for DoD Information Technology (IT), dated 7 October 2019

NIST SP 800-53 - Security and Privacy Controls for Information Systems and Organizations, dated 23 September

CNSSI 1253 - Security Categorization and Control Selection for National Security Systems, dated 27 March 2014

(The above documents are downloadable from:

https://www.esd.whs.mil/Directives/issuances/dodi/;

https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r5.pdf;

https://www.dcsa.mil/portals/91/documents/ctp/nao/CNSSI_No1253.pdf)

Federal Regulations

29 CFR 1910 - Occupational Safety and Health Standards (Copies of these regulations are downloadable from http://www.gpo.gov/fdsys/browse/collectionCfr.action?collectionCode=CFR)

National Institute of Standards and Technology (NIST) - Federal Information Processing Standards (FIPS)

FIPS 140-3 - Security Requirements for Cryptographic Modules, dated 22 March 2019

The above document is downloadable from https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-3.pdf Navigation Rules

USCG Navigation Rules - U.S. Coast Guard Navigation Rules and Regulations Handbook

(Available at https://www.navcen.uscg.gov/navigation-rules-amalgamated)

NAVDORM

NAVDORM 3530.4G - Surface Ship Navigation Department Organization and Regulations Manual (NAVDORM)

COMNAVSURFPAC/COMNAVAIRPAC/COMNA

VAIRLANT/COMNAVSURFLANTINST 3530.4G,

dated 28 October 2021

2.3 Non-Government publications

The following documents of the exact revision listed below form a part of this document to the extent specified herein.

Commercial Bridge Watchstanding Training Standards

DNV-ST-0033 - Standard for Maritime simulator systems, dated June

(Copies of this document is available from https://rules.dnv.com/servicedocuments/dnv/#!/home)

American National Standards Institute (ANSI)

ANSI Z535.1-2017 - Safety Colors ANSI Z535.2-2011 (R2017) - Environmental and Facility Safety Signs https://www.esd.whs.mil/Directives/issuances/dodi/ https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r5.pdf http://www.gpo.gov/fdsys/browse/collectionCfr.action?collectionCode=CFR

ANSI Z535.3-2011 (R2017) - Criteria for Safety Symbols ANSI Z535.4-2011 (R2017) - Product Safety Signs and Labels ANSI Z535.5-2011 (R2017) - Safety Tags and Barricade Tapes (for Temporary

Hazards) (Copies of these documents are available from www.ansi.org)

American Society of Mechanical Engineers (ASME)

ASME Y14.44-2008(R2014) - Reference Designations for Electrical and Electronics Parts and Equipment

(Copies of this document are available from http://www.asme.org)

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

3. REQUIREMENTS

3.1 Performance and functional requirements

NSST systems shall meet the performance and functional requirements specified herein. When a delivered product is replacing or modifying an existing training device, the delivered product shall provide features and functionality present in the existing training device that are germane to U.S. Navy training without performance degradations and without instructor, operator, and maintainer workload growth. In the event of a conflict, requirements specified herein shall supersede existing features and functionality.

3.1.1 Architectural Requirements

The NSST system shall employ a Modular Open System Approach (MOSA) that uses a system architecture with severable system components. Modularity shall support adding, removing, and replacing components throughout the system life cycle for the purposes of enhanced competition, sustainment, and innovation. Fully documented, as used in this section, means providing the details necessary to solicit the addition, removal, and replacement of components in an open competitive contract action.

3.1.1.1 Proprietary and Vendor-Specific Software

The use of proprietary software and vendor-specific software shall be isolated to stand-alone and severable software modules. New software modules and software to which the Government has other than limited rights shall include executable code and source code that is free of proprietary restrictions and markings. Proprietary software modules and vendor-unique software modules shall be individually replaceable with alternative software modules that perform the same types of functions. Proprietary software modules and vendor-unique software modules shall connect to other system components using interfaces that are open, non-proprietary, and fully documented in the Technical Data Package (TDP). Proprietary and Vendor Specific Software shall only be used if associated form, fit, and function data, as defined in FAR 52.227-14, is delivered in the TDP.

http://www.ansi.org/ http://www.asme.org/

3.1.1.2 Simulation Runtime Interface

Simulation applications shall connect to the runtime interface using widely accepted, supported, and consensus-based standards, except where the TDP documents a program-unique specification.

3.1.1.2.1 Application Program Interface (API)

The NSST system shall only use open, supported, extensible, non-proprietary, and fully documented Application Program Interfaces (APIs).

3.1.1.2.2 High Level Architecture (HLA) and Distributed Interface Simulation (DIS) The NSST system shall have fully documented High Level Architecture (HLA) and Distributed Interface Simulation (DIS) interfaces for future integration with other training devices and components.

3.1.1.3 Scalability

The NSST system shall be scalable to support individual student training, team training, and multi-ship team training. The NSST system shall support the simultaneous execution of one (1) scenario per IOS, MIOS, and briefing station on a training site’s system network. The NSST system shall provide functionality to conduct stand-alone training for each configuration specified in section 3.1.4.1 (NSST Devices). For each scenario run on an IOS and MIOS, the NSST system shall provide functionality to conduct integrated multi-ship training using every potential combination of NSST devices on the training site’s system network.

3.1.1.4 Maritime Simulation Software

NSST maritime simulation software shall have a Class A statement of compliance (SOC) for Bridge Operation in accordance with (IAW) DNV-ST-0033.

3.1.1.5 Software licenses

Licensed computer software items used in NSST systems shall have perpetual and irrevocable licenses free of limitations on storage, usability, and distribution. Non-perpetual licenses shall be limited to use on development seats and only if:

a. The software is not provided by a party of this contract

b. Perpetual licenses are not available for procurement

c. The duration of the non-perpetual license exceeds the duration of the contract by a minimum of 6 months

3.1.1.5.1 Enterprise license agreement

Software licensed by parties of this contract (prime contractor and sub-contractors) shall have enterprise license agreements that provide:

a. Unlimited use of the delivered software in systems classified by the Government as NSST systems, to include:

1. NSST systems, devices, and components procured and modified under this contract

2. NSST systems, devices, and components procured and modified by other means

b. Fixed price licensing for non-NSST systems

3.1.2 Watchstander Task Requirements

For every watchstander task specified herein:

a. NSST devices shall present information, and provide functional indicators and controls necessary for watchstanders to train in the proper performance of each specified task

b. NSST devices shall simulate outcomes that provide positive feedback for correct watchstander actions and negative feedback for incorrect watchstander actions

c. NSST devices shall provide instructional tools that output information in the form of metrics, graphics, and visualizations that communicate the degree to which the watchstander successfully/unsuccessfully performed each specified task

d. NSST devices shall simulate the unique task variations for each ownship model in section

3.1.7.2 (Ownship Model Requirements)

3.1.2.1 General Navigation Tasks

NSST devices shall provide components and functionality to train the following general navigation tasks:

a. Determine ship’s position using visual, radar, GPS, and electronic chart information

b. Plot a fix by three Lines of Position (LOPs) using the following LOP sources:

1. Visual

2. Radar

c. Determine the following based on two fixes:

1. Set and drift

2. Course and speed made good

3. Course and speed to regain Plan of Intended Movement (PIM)

4. Course and speed to maintain desired track

d. Identify Navigational Aids (NAVAIDS) available for use during piloting

e. Observe and report true and relative bearings to charted objects

f. Track and report the bearings of NAVAID designated for turn and drop bearing

g. Track and report the bearings of NAVAID designated as the head bearing for an anchorage

h. Determine gyrocompass error using a range

i. Apply gyrocompass error to indicated course to obtain a true heading and course

j. Apply variation and deviation to compass course to obtain true course

k. Determine course to steer by magnetic compass

l. Operate fathometer to obtain water depth

m. Compare fathometer readings with the charted depth

n. Plan and construct a track for a restricted water route, costal route, and great-circle route

3.1.2.2 General Seamanship Tasks

NSST devices shall provide components and functionality to train the following general seamanship tasks:

a. Detect, classify, and identify visual objects in daylight and at night

b. Detect and recognize fog signals, marine mammals, and distress signals

c. Visually determine contact target angle under day and night conditions

d. Determine risk of collision based on bearing drift

e. Determine contact and object range using the stadiametric rangefinding method

f. Compute desired and true wind speed

g. Operate and utilize Automatic Identification System (AIS)

h. Operate general announcing system and alarms

i. Operate whistle in manual and automatic modes

j. Display appropriate lights and flags

3.1.2.3 General Shiphandling Tasks

NSST devices shall provide components and functionality to train the following general shiphandling tasks:

a. Maneuver the ship using standard commands, line commands, and tug commands

b. Maneuver the ship to avoid collisions and mitigate damage in imminent collision situations

c. Maneuver the ship to avoid grounding and mitigate damage in imminent grounding situations

d. Maneuver the ship correcting for:

1. Tides and currents

2. Winds

3. Venturi effects

4. Bank effects

5. Shallow water effects

6. Wave effects

7. Draft state

e. Operate the ship control console (SCC), helm, autopilot, throttle, Engine Order Telegraph (EOT), and thrusters

f. Maintain course by gyrocompass and magnetic compass

g. Transfer steering and thrust control between bridge and non-bridge watch stations

h. Maneuver the ship while rafting

3.1.2.4 Communication Tasks

NSST devices shall provide components and functionality to train the following communication tasks:

a. Setup, test, monitor, and operate internal and external communication circuits

b. Communicate with traffic vessels over Bridge to Bridge radio

c. Communicate with U.S. and alliance vessels over secure radio circuits, unsecure radio circuits, by flag hoist, and by flashing light

d. Communicate with non-bridge watch stations over internal ship communication networks

e. Operate ship’s general announcing system and alarms

f. Communicate with navigation team stations over internal ship communication networks

3.1.2.5 Mooring and Anchoring Tasks

NSST devices shall provide components and functionality to train the following mooring and anchoring tasks:

a. Maneuver and navigate the ship from underway in the channel to moored to the pier

b. Maneuver and navigate the ship from moored to the pier to underway in the channel

c. Issue orders to tugs during a mooring evolution

d. Maneuver and navigate the ship from underway in the channel to moored to a buoy

e. Maneuver and navigate the ship from moored to a buoy to underway in the channel

f. Maneuver and navigate the ship from underway in the channel to anchored

g. Maneuver and navigate the ship from anchored to underway in the channel

h. Identify and respond to a dragging anchor situation

i. Maneuver and navigate the ship from underway in the channel to Mediterranean moored to the pier

j. Maneuver and navigate the ship from Mediterranean moored to the pier to underway in the channel

k. Maneuver and navigate the ship from underway in the channel to nested alongside a moored vessel

l. Maneuver and navigate the ship from nested alongside a moored vessel to underway in the channel

3.1.2.6 Connected Replenishment (CONREP)

NSST devices shall provide components and functionality to train the following CONREP tasks:

a. Maneuver the ship during a CONREP approach and breakaway

b. Maneuver the ship alongside during a CONREP evolution

c. Respond to the following emergencies during a CONREP evolution:

1. Ownship steering casualty

2. Ownship propulsion casualty

3. Delivery ship steering casualty

4. Delivery ship propulsion casualty

5. Loss of gyrocompass

6. Man overboard

7. Rapid closure to ship alongside

8. Emergency breakaway

d. Conduct astern refueling (Auxiliary, MCM, and PC vessels only)

e. Deliver fuel at sea (Auxiliary, LHA, and LHD vessels only)

3.1.2.7 Towing Tasks

NSST devices shall provide components and functionality to train the following towing tasks:

a. Maneuver the ship into position to tow a dead in the water (DIW) vessel

b. Maneuver the ship from alongside with connected slack towline to towing at speed

c. Maneuver the ship from towing at speed to towline disconnected and recovered

d. Maneuver the ship while being towed by another vessel

e. Respond to a parted towing line

3.1.2.8 Other Special Evolution Tasks

NSST devices shall provide components and functionality to train the following other special evolution tasks:

a. Conduct flight operations from the bridge

b. Conduct small boat operations from the bridge

c. Maneuver the ship during a Division Tactic (DIVTAC) exercise

d. Maneuver the ship to approach, maintain, and breakaway from plane guard station and lifeguard station

e. Maneuver and navigate the ship during a minehunting and channel/Q-route exercise

f. Maneuver and navigate the ship while the towed array sonar and SLQ-25 Nixie are deployed, being deployed, and being recovered

g. Maneuver the ship and issue engagement orders during a small arms weapon engagement

h. Maneuver the ship during a Visit Board Search and Seizure (VBSS) evolution

3.1.2.9 Casualty, Emergency, and Weather Response Tasks

NSST devices shall provide components and functionality to train to respond to the following casualties, emergencies, and weather conditions:

a. Casualties:

1. Loss and degradation of communications

2. Loss, degradation, and spoofing of GPS

3. Loss of gyrocompass

4. Failure of gyrocompass repeater

5. Loss of steering control and jammed rudder

6. Steering unit, pump, and motor component failure

7. Rudder angle indication error

8. Loss of throttle control

9. Indication of unanswered Bell, pitch, and Revolutions Per Minute (RPM)

10. SCC display failure and loss of power

11. Loss of main engines

12. Loss of main propulsion train

13. Loss of VMS node

b. Emergencies:

1. Man overboard (ship and boat recovery)

2. Vessel in distress

3. Aircraft in the water

4. Aircraft crash on deck

5. Aircraft in-flight emergency

6. Small boat attack

7. Torpedo attack

8. Mine sighting

9. Mine explosion

10. Marine mammal strike

c. Weather conditions:

1. Heavy weather

2. Restricted visibility

3.1.2.10 Electronic Chart Operation Tasks

NSST devices shall provide components and functionality to train the following electronic chart operation tasks:

a. Interpret electronic chart data

b. Setup the electronic chart

c. Identify electronic chart sensor inputs

d. Choose and display appropriate charts

e. Properly display all navigation information

f. Enter and evaluate navigation information

g. Create and monitor a voyage plan

h. Operate the electronic chart while underway

i. Operate man overboard function

3.1.2.11 Radar and Automatic Radar Plotting Aid (ARPA) Operation Tasks

NSST devices shall provide components and functionality to train the following radar and ARPA operation tasks:

a. Tune the radar repeater based on environmental conditions

b. Switch display modes

c. Identify false echoes, sea return, radar beacons (RACONs), and search and rescue transponders (SARTs)

d. Determine range and bearing

e. Determine direction of relative motion (DRM), speed of relative motion (SRM), closest point of approach (CPA), and time to the CPA (TCPA)

f. Detect speed and course changes of other ships

g. Change course to control target DRM

h. Change speed to control target DRM

i. Determine true course and speed of target vessels

j. Confirm vessel track using parallel indexing

k. Setup and maintain an ARPA display

l. Manual target acquisition

m. Establish an exclusion area

n. Set vector characteristics

o. Designate targets

p. Cancel targets

q. Display target history

r. Establish CPA and TCPA

s. Establish alarm area

t. Conduct trial maneuver

u. Switch stabilization modes

v. Display navigation lines

w. Determine set and drift

x. Set variable range markers

y. Set electronic bearing lines

3.1.2.12 NAVDORM Checklist Tasks

NSST devices shall provide components and functionality to train in the execution of NAVDORM 3530.4G Appendix A – Squadron/Group Staff Navigation Assessment Checklist for Underway Operations

3.1.3 Simulation Requirements

For every simulation requirement herein:

a. NSST system simulations shall present information to watchstanders that are consistent with real world presentations of information.

b. NSST system simulations shall provide watchstanders the same level of information, type of information, and format of information as what is available to watchstanders aboard U.S. Navy ships.

c. NSST system simulations shall provide information and interfaces necessary to learn how to perform the watchstander tasks specified in section 3.1.2 (Watchstander Task Requirements) without negative transfer. Negative transfer means an aspect of the simulation that effectively trains the watchstander to perform the task in an incorrect way.

d. NSST systems shall simulate the unique characteristics for each ownship model in section 3.1.7.2 (Ownship Model Requirements)

3.1.3.1 Physics Simulations

NSST systems shall provide physics simulations that conform to real world data and information.

When real world data and information is not available, physics simulation shall conform to a documented and validated physics model.

3.1.3.1.1 Ownship physics

NSST systems shall simulate ownship vessels with a six (6) degree of freedom physics based model that realistically reacts to the effects of the following forces:

a. Wave field forces

b. Wind forces

c. Current forces

d. Propulsion system forces

e. Thruster system forces

f. Propeller walk forces

g. Rudder drag and lift forces

h. Line forces

i. Tug forces

j. Pier, vessel, and object fendering forces

k. Venturi effect forces between vessels

l. Bow and stern wave forces

m. Shallow water effect forces:

1. Squat effect

2. Bank effect

3. Increased turn radius effect

n. CONREP tensioning forces for one and two spanwires

o. Buoy moored forces

p. Towing hawser forces

q. Anchor chain forces

3.1.3.1.2 Traffic vessel physics

NSST systems shall simulate traffic vessels with a physics based model that realistically reacts to the effects of the following forces:

a. Wave field forces

b. Wind forces

c. Current forces

d. Line forces

e. Tug forces

f. Pier, vessel, and object fendering forces

g. Bow and stern wave forces

3.1.3.1.2.1 Traffic vessel physics effects

NSST systems shall simulate traffic vessels that emulate vessel advance, transfer, acceleration, and deceleration behavior with non-linear course and speed changes.

3.1.3.1.3 Floating object physics

NSST systems shall simulate anchored and non-anchored floating objects with a physics based model that realistically reacts to the effects of the following forces:

a. Wave field forces

b. Wind forces

c. Current forces

d. Pier, vessel, and object fendering forces

e. Bow and stern wave forces

3.1.3.1.4 Collision and Allision

NSST systems shall simulate the detection of collisions and allisions between ownship models, entity models, and physical objects modeled in geographic databases.

3.1.3.1.5 Anchor physics

NSST systems shall dynamically simulate ground tackle holding power and resulting forces on the ship based on bathymetry, scope of the chain, and relative location of the ground tackle to the ownship.

3.1.3.2 Visualization and sensor simulations

NSST systems shall present information about an object consistently across every interface except for intentional differences implemented for training purposes.

3.1.3.2.1 Contacts

NSST systems shall simulate perceptually accurate visualizations and sensor effects of vessels, aircraft, floating objects, fixed objects, marine mammals, and distress signals under the full range of simulated weather and celestial illumination conditions. Visualizations shall be compliant with USCG Navigation Rules.

3.1.3.2.2 Celestial

NSST systems shall simulate illumination, directional shadowing, and celestial sphere orientation based on geographic location, date, and time.

3.1.3.2.3 Navigational aids

NSST systems shall simulate geographically and perceptually accurate visualizations and sensor effects of navigational aids based on Electronic Navigational Charts (ENC) data. Perceptibility shall be configurable based on display type and sensor type to make navigational aids detectable and identifiable at the appropriate ranges.

3.1.3.2.4 Geographic features

NSST systems shall simulate visualizations and sensor effects of shorelines, land elevations, cultural features, navigationally relevant features, and night lighting.

3.1.3.2.5 Signals

NSST systems shall simulate visualizations of distress signals, flashing light signals, and flag hoist signals.

3.1.3.2.6 Depth and grounding

NSST systems shall simulate ownship depth readings and the detection of grounding based on hull shape, state of the tides, and geographic bathymetry within geographic database extents.

NSST systems shall provide functionality for operators to override and manually set depth states.

3.1.3.2.7 Lines

NSST systems shall simulate dynamic visualizations of line states based on standard line commands that accurately depict line handler responsiveness to commands and associated forces applied by the lines. NSST systems shall simulate the unique characteristics of the following line types:

a. Kevlar

b. Nylon

c. Spectra

3.1.3.2.8 Tugs

NSST systems shall simulate dynamic visualizations of tug behavior based on standard tug commands that accurately depict tug responsiveness to commands and associated forces applied by the tugs for both conventional tugs and z drive tugs.

3.1.3.2.9 CONREP

NSST systems shall simulate dynamic visualizations of:

a. Phone and distance lines that accurately depict distance between vessels (day and night)

b. Fueling rigs that accurately depict state of the rigs and associated forces applied to the ownship

3.1.3.2.10 Flight deck

NSST systems shall simulate visualizations of flight deck state for each phase of rotary wing aircraft launch and recovery.

3.1.3.2.11 Boat deck

NSST systems shall simulate visualizations of small boat operations through each phase of small boat launch, recovery, and personnel transfer.

3.1.3.2.12 Buoy mooring

NSST systems shall simulate dynamic visualizations and associated forces of vessels moored to buoys.

3.1.3.2.13 Towing hawser

NSST systems shall simulate dynamic visualizations and associated forces of towing hawsers.

3.1.3.2.14 Weapons

3.1.3.2.14.1 Weapon types

NSST systems shall simulate ballistics, probabilistic calculations, visual effects, and aural effects for the following weapon types:

a. 50 caliber machine gun

b. M240 type machine gun

c. Mk 15 20mm Close-in weapon system (CIWS)

d. 25mm chain gun

e. 30mm chain gun

f. 57mm gun

g. 5-inch gun

h. Rocket propelled grenade (RPG)

3.1.3.2.14.2 Engagement orders

NSST systems shall simulate visualizations of weapon engagements based on engagement orders issued using:

a. A student interface for crew served weapons

b. An operator interface for non-crew served weapons

3.1.3.2.14.3 Damage effects

NSST systems shall simulate visualizations of the following damage effects that are activated by manual and configurable automatic triggers:

a. Smoke

b. Fire

c. Sinking

3.1.3.2.14.4 Anti-terrorism/force protection (ATFP) threat cues

NSST systems shall simulate visualizations and animations of objects, weapons, and personnel on vessels that present varied levels of vessel hostility.

3.1.3.2.14.5 Warning flare

NSST systems shall simulate visual and aural warning flare effects activated through a student interface.

3.1.3.2.14.6 Torpedo

NSST systems shall simulate torpedo wake effects.

3.1.3.3 Sound simulation requirements

NSST systems shall simulate perceptibly accurate audio cues with respect to direction of sound source, range of sound source, and reconizability of sound type. NSST systems shall provide the following sound cues:

a. Sound signals IAW USCG Navigation Rules

b. Vessel propulsion system sounds

c. Weather and ocean sounds

d. NAVAID sounds

e. Bridge equipment alerts and alarms

f. Weapon fire and explosion sounds

g. User defined sounds

3.1.3.4 Environmental Simulations

NSST systems shall simulate the following environmental conditions and effects:

3.1.3.4.1 Wind

NSST systems shall simulate visualizations, sensor inputs, and force effects on objects based on wind velocity, object type, and object surface area.

3.1.3.4.2 Tide and Current

NSST systems shall simulate current force effects on vessels and floating objects based on state of the tides and historical current data. NSST systems shall simulate eddy effects caused by currents interacting with buoys and other fixed objects in the water. NSST systems shall provide functionality for operators to override and manually set tide and current states.

3.1.3.4.3 Waves

NSST systems shall simulate complex ocean wave field visualizations and force effects on objects based on wind wave direction, wind wave magnitude, swell wave direction, and swell wave magnitude.

3.1.3.4.4 Weather

NSST systems shall simulate fog, rain, snow, sand, and haze effects with associated visual, aural, and sensor degradations based on adjustable precipitation intensities and visibility ranges.

3.1.3.4.5 Environmental Effect Zones

NSST systems shall simulate the following types of environmental effect zones. NSST systems shall simulate gradual transitions and visual predictive cues of the transitions into and out of environmental effect zones.

3.1.3.4.5.1 Geographic Lee

NSST systems shall automatically simulate the effect of landmass and fetch on wave fields.

3.1.3.4.5.2 Large Vessel Lee

NSST systems shall automatically simulate the effect of a large vessels freeboard on waves and winds in the vessel’s lee.

3.1.3.4.5.3 Pier Slip

NSST systems shall automatically simulate the effect of piers on waves and currents.

3.1.3.4.5.4 Fog Bank

NSST systems shall simulate fog banks with adjustable size, shape, intensity, course, and speed and the effect of fog banks on visibility, audio cues, and sensor degradation.

3.1.3.4.5.5 Weather Cell

NSST systems shall simulate heavy weather cells with adjustable size, shape, intensity, course, and speed and the effect of heavy weather cells on wind, waves, visibility, audio cues, and sensor degradation. Weather cells shall have functionality to simulate false contact effects.

3.1.3.5 Ship system simulation

NSST systems shall provide the following ship system simulations. When tactical hardware and software is used, the tactical hardware and software shall operate without functional and performance degradations caused by NSST systems, interfaces, or databases.

3.1.3.5.1 Propulsion systems

NSST systems shall accurately model pitch, shaft and engine RPM, resulting forces, Ship Control Console (SCC) indications, and CONN indications based on Engine Order Telegraph (EOT), throttle, and thruster control inputs for the following propulsion system states. For Controllable Reversible Pitch (CRP) ownships, shaft RPM and propeller pitch shall have independently simulated ship system models:

a. Plant States:

1. Full Power

2. Split Plant

3. Trail Shaft

4. Locked Shaft

b. Casualty States:

1. Loss of engine

2. Loss of main propulsion train

3. RPM limitations

4. Loss of Controllable Reversible Pitch (CRP) control

5. SCC loss of power

6. Loss of throttle control

7. Incorrect indications

c. Station in control located at:

1. Bridge

2. After Steering

3. Engineering

3.1.3.5.2 Steering Systems

NSST systems shall accurately model rudder angles, resulting forces, SCC indications, and CONN indications based on helm and autopilot control inputs for the following steering system states:

a. Steering Gear States:

1. Primary and alternate units, pumps, and motors

b. Casualty States:

1. Loss of autopilot control

2. Loss of helm control

3. Jammed rudder

4. Loss and degradation of units, pumps and motors

5. Incorrect indications

6. Hydraulic system leak

c. Station in control located at:

1. Bridge

2. After Steering

3.1.3.5.3 Gyrocompass simulations

NSST systems shall simulate gyrocompass indications and the following gyrocompass errors and casualties:

a. Gyrocompass error

b. Gyrocompass repeater errors

c. Loss of gyrocompass (frozen and spinning)

d. Loss of gyrocompass repeaters (frozen and spinning)

3.1.3.5.4 Magnetic compass simulations

NSST systems shall simulate magnetic variation, magnetic deviation, magnetic compass indications, and digital fluxgate magnetic compass (DFGMC) indications. Variation shall be calculated based on ownship geographic location and the World Magnetic Model.

3.1.3.5.5 Whistle simulations

NSST systems shall simulate manual and automatic ship whistle modes.

3.1.3.5.6 Stadimeter and laser range finder simulations

NSST systems shall simulate a virtualized stadimeter and laser range finder using the virtual binocular display system.

3.1.3.5.7 Global positioning system (GPS) simulations

NSST systems shall simulate GPS output to navigational systems, Figure of Merit (FOM), chart datum, degradations to GPS accuracy, offset errors, alternate sources, GPS operation, and AN/PSN-13 DAGR operation.

3.1.3.5.8 Fathometer simulations

NSST systems shall simulate fathometer depth sensing, loss of fathometer, fathometer false readings, AN/UQN-4A operation, and AN/UQN-10 operation.

3.1.3.5.9 Towed bodies

NSST systems shall simulate deployed, deploying, and recovering towed arrays and SLQ-25 Nixies, and shall detect unsafe ownship maneuvers that could result in damage to towed bodies.

3.1.3.5.10 Chronometer

NSST systems shall simulate chronometers, chronometer synchronization errors, and loss of time.

3.1.3.5.11 Course and Speed sensors

NSST systems shall simulate course over ground (COG) sensing, speed over ground (SOG) sensing, speed through the water (STW) sensing, COG sensor errors, SOG sensor errors, STW sensor errors, loss of COG sensor, loss of SOG sensor, and loss of STW sensor.

3.1.3.5.12 Ship Control GUIs and Ship Control Consoles (SCC)

NSST systems shall simulate the following types of ship control Graphical User Interfaces (GUIs) and specified NSST devices shall have the following ship control consoles (SCC). Every ship control GUI shall be functionally compatible with every SCC. Every ship control GUI shall function without a SCC present.

3.1.3.5.12.1 Universal Ship Control GUI

The NSST system shall have a universal ship control GUI that provides controls and indications that are functionally compatible with every ownship model.

3.1.3.5.12.2 Desktop Ship Control Console

Specified NSST devices shall have a desktop ship control console that provides a small footprint console that provides physical controls that are functionally compatible with every ownship model.

3.1.3.5.12.3 Universal Ship Control Console

Specified NSST devices shall have a universal SCC that provides a full sized SCC with controls and indications that are functionally compatible with every ownship model.

3.1.3.5.12.4 Ship Control System – Government (SCS-GOV) GUI

The NSST system shall have a SCS-GOV GUI that utilizes tactical SCS-GOV software for the following ownship models:

a. Nimitz Class

b. Wasp Class

c. America Class

d. Whidbey Island Class

e. Harpers Ferry Class

f. San Antonio

3.1.3.5.12.5 Ship Control System – Government (SCS-GOV) SCC

Specified NSST devices shall have a Ship Control System – Government (SCS-GOV) SCC that emulates the appearance, interface layout, haptic feedback (tactile and kinesthetic), and functional behaviors of the shipboard SCS-GOV SCC. The SCS-GOV SCC shall have three (3) slots for SCC reconfigurable subcomponents. Each SCS-GOV SCC shall be delivered with the following SCC reconfigurable subcomponents that emulate shipboard SCS-GOV SCC subcomponents in appearance, interface layout, haptic feedback (tactile and kinesthetic), and functional behaviors:

a. One (1) physical helm wheel unit

b. Two (2) functional selector switch panel types

c. Two (2) physical throttle types

d. One (1) blank access panel

3.1.3.5.12.6 Integrated Bridge Navigation System (IBNS) GUI

The NSST system shall have an IBNS GUI that is identical to the shipboard IBNS GUI in appearance and functional behavior for the Arleigh Burke class ownship models.

3.1.3.5.12.7 Integrated Bridge Navigation System (IBNS) SCC

Specified NSST devices shall have an IBNS SCC that emulates the appearance, interface layout, haptic feedback (tactile and kinesthetic), and functional behaviors of the shipboard IBNS SCC with a removable physical throttle.

3.1.3.5.13 Bridge Manual Pump Controller

The NSST system shall have an emulated Bridge Manual Pump Controller (BMPC) that matches the appearance and functional behaviors of the shipboard BMPC.

3.1.3.5.14 Digital Rudder Angle Display System (DRADIS)

The NSST system shall have an emulated Digital Rudder Angle Display System (DRADIS) that matches the appearance and functional behaviors of the shipboard DRADIS.

3.1.3.5.15 Navigation Data Display (NDD)

NSST systems shall simulate the Navigation Data Display (NDD) utilizing tactical software.

3.1.3.6 Virtual watchstander system

NSST systems shall simulate a virtual watchstander that functions IAW the following requirements:

a. The virtual watchstander system shall use a speaker independent speech recognition engine

b. The virtual watchstander system shall recognize the following types of spoken standard commands and effect…