General

Question 1

What is the purpose of CMS 330

Answer 1

The purpose of CMS 330 is to integrate the ship’s weapons and sensor systems into a single user interface, and to provide a seamless detect to engage sequence for the operators!

Question 2

Hardware components include (6)

Answer 2

12 MCEs - ruggetized COTS cabinets

15 MFWs - (14 ops, 1 bridge) - CMS HMI

2 MCTs - access into CMS subsystems

2 Command Chairs - for Command

2 FC Consoles - Operator control of AHWCS, CIWS, and 57 mm Gun

1 ESM Console - Allows control of ELISRA

Question 3

Software components include

Answer 3

Adaptation
Situational awareness
Tactical operations
Tactical execution

Doctrine
Mission support
High priority
Entity pattern mapping

Question 4

Modes of Operation

Answer 4

Standalone - training purposes

Operational

• auto engage
• auto assign (fire switch)
• no support (no support)
• manual (manually)
• semi auto - approval -> auto assign
  - auto fire -> auto engage
  - no support -> manual

-urgent (if pressed, immediately fires weapon)

Question 5

System interfaces (4)

Answer 5

EPG&D - Switchboards - SABT
HVAC - Chilled Water - 60 Glycol
Radar suite - RDU n VSU
NDDS - GPS time

Question 6

Redundancy and Survivability (9)

Answer 6

2 core switches via fibre

Shared resource approach (run any app on any available processor)

Both core switches: 15 + MFWs

Tactical servers

2 SABTs - no UPS

Core switch 1: 10
Core switch 2: 6

No backups for RDU, VSU, and DCA

Physical separation

Question 7

Composition of MFW

Answer 7

Thin client for CSNI

Computer 32 GB ram