← All reports
PDF Excel ReqIF

Naval Combat Management System

System Decomposition Report — Generated 2026-03-27 — UHT Journal / universalhex.org

About this report

This report was generated autonomously by the UHT Journal systems engineering loop. An AI agent decomposed the system into subsystems and components, classified each using the Universal Hex Taxonomy (a 32-bit ontological classification system), generated traced requirements in AIRGen, and built architecture diagrams — all without human intervention.

Every component and subsystem is assigned an 8-character hex code representing its ontological profile across 32 binary traits organised in four layers: Physical (bits 1–8), Functional (9–16), Abstract (17–24), and Social (25–32). These codes enable cross-domain comparison — components from unrelated systems that share a hex code or high Jaccard similarity are ontological twins, meaning they occupy the same structural niche despite belonging to different domains.

Duplicate hex codes are informative, not errors. When two components share the same code, it means UHT classifies them as the same kind of thing — they have identical trait profiles. This reveals architectural patterns: for example, a fire control computer and a sensor fusion engine may share the same hex because both are powered, synthetic, signal-processing, state-transforming, system-essential components. The duplication signals that requirements, interfaces, and verification approaches from one may transfer to the other.

Requirements follow the EARS pattern (Easy Approach to Requirements Syntax) and are traced through a derivation chain: Stakeholder Needs (STK) → System Requirements (SYS) → Subsystem Requirements (SUB) / Interface Requirements (IFC) → Verification Plan (VER). The traceability matrices at the end of this report show every link in that chain.

Referenced Standards

StandardTitle
ARINC 653-compliant Avionics application software standard interface
IEEE 1588 Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems
STANAG 4193 —
STANAG 4420 —
STANAG 4545-compliant —

Acronyms & Abbreviations

AcronymExpansion
ARC Architecture Decisions
CCCS Completeness, Consistency, Correctness, Stability
EARS Easy Approach to Requirements Syntax
IFC Interface Requirements
STK Stakeholder Requirements
SUB Subsystem Requirements
SYS System Requirements
UHT Universal Hex Taxonomy
VER Verification Plan
206
Requirements
69
Classified Entities
10
Subsystems
15
Diagrams
239
Relationships

System Context

flowchart TB
  n0["system<br>Naval Combat Management System"]
  n1["actor<br>Radar Systems"]
  n2["actor<br>Sonar Systems"]
  n3["actor<br>EO/IR Sensors"]
  n4["actor<br>Weapon Systems"]
  n5["actor<br>Ship Navigation and Propulsion"]
  n6["actor<br>External Data Links"]
  n7["actor<br>Ship Command Authority"]
  n8["actor<br>Damage Control System"]
  n1 -->|Track data, detection reports| n0
  n2 -->|Sonar contacts, bearing data| n0
  n3 -->|Visual tracks, IR signatures| n0
  n0 -->|Engagement orders, target designation| n4
  n5 -->|Own-ship position, course, speed| n0
  n0 -->|Link 16 messages, SATCOM data| n6
  n7 -->|Weapon release authority, ROE| n0
  n0 -->|System status, battle damage reports| n8

Naval Combat Management System — Context

System Decomposition

flowchart TB
  n0["system<br>Naval Combat Management System"]
  n1["subsystem<br>Sensor Management"]
  n2["subsystem<br>Track Management"]
  n3["subsystem<br>Threat Evaluation and Weapon Assignment"]
  n4["subsystem<br>Weapon Control"]
  n5["subsystem<br>Electronic Warfare"]
  n6["subsystem<br>Communications Management"]
  n7["subsystem<br>Tactical Display and Operator Interface"]
  n8["subsystem<br>Navigation and Platform Interface"]
  n9["subsystem<br>Data Processing Infrastructure"]
  n10["subsystem<br>Training and Simulation"]
  n11["system<br>Naval Combat Management System"]
  n12["subsystem<br>Sensor Management"]
  n13["subsystem<br>Track Management"]
  n14["subsystem<br>TEWA"]
  n15["subsystem<br>Weapon Control"]
  n16["subsystem<br>Electronic Warfare"]
  n17["subsystem<br>Communications Management"]
  n18["subsystem<br>Tactical Display"]
  n19["subsystem<br>Navigation and Platform Interface"]
  n20["subsystem<br>Data Processing Infrastructure"]
  n21["subsystem<br>Training and Simulation"]
  n1 -->|Sensor reports| n2
  n2 -->|Correlated tracks| n3
  n3 -->|Engagement orders| n4
  n5 -->|ESM bearings| n2
  n6 -->|Data link tracks| n2
  n2 -->|Tactical picture| n7
  n8 -->|Own-ship data| n2
  n10 -->|Simulated sensor data| n1
  n12 -->|Raw detections| n13
  n13 -->|Fused tracks| n14
  n14 -->|Engagement commands| n15
  n15 -->|Weapon status| n14
  n14 -->|Decision displays| n18
  n16 -->|ESM/ECM data| n14
  n17 -->|CEC/Link 16 data| n14
  n12 -->|ESM bearings| n16
  n19 -->|Ownship nav data| n13
  n20 -->|Processing services| n13
  n18 -->|Display injection| n21

Naval Combat Management System — Decomposition

Decomposition Tree

Stakeholder Requirements (STK)

Ref Requirement V&V Tags
STK-STAKEHOLDERNEEDS-001 The Naval Combat Management System SHALL provide the Commanding Officer with a comprehensive, real-time tactical picture of all detected air, surface, and subsurface contacts within sensor range to support timely engagement authorization decisions. — stakeholder, command, session-187
STK-STAKEHOLDERNEEDS-002 The Naval Combat Management System SHALL enable simultaneous coordination of anti-air, anti-surface, anti-submarine, and electronic warfare operations by dedicated warfare coordinators without mutual interference between warfare domains. — stakeholder, operations, session-187
STK-STAKEHOLDERNEEDS-003 The Naval Combat Management System SHALL exchange tactical data with allied naval and joint forces via NATO-standard tactical data links to enable coordinated multi-ship and joint force operations. — stakeholder, interoperability, session-187
STK-STAKEHOLDERNEEDS-004 The Naval Combat Management System SHALL support engagement of close-in threats with a sensor-to-weapon reaction time sufficient to counter sea-skimming anti-ship missiles with flight times under 30 seconds from radar horizon to impact. — stakeholder, reaction-time, session-187
STK-STAKEHOLDERNEEDS-005 The Naval Combat Management System SHALL maintain combat capability with degraded but operationally useful functionality following battle damage that disables up to 30 percent of system processing nodes or display consoles. — stakeholder, survivability, session-187
STK-STAKEHOLDERNEEDS-006 The Naval Combat Management System SHALL provide built-in test and fault isolation to the line-replaceable unit level, enabling shipboard maintenance personnel to diagnose and repair faults without shore-based technical support. — stakeholder, maintenance, session-187
STK-STAKEHOLDERNEEDS-007 The Naval Combat Management System SHALL support embedded training with synthetic scenario generation that exercises crew proficiency in all warfare domains without requiring live sensor feeds or expending ordnance. — stakeholder, training, session-187
STK-STAKEHOLDERNEEDS-008 The Naval Combat Management System SHALL enforce weapon safety interlocks that prevent inadvertent weapon release, including bearing and elevation safety arcs, friendly force deconfliction, and a multi-level authorization chain requiring positive human confirmation before lethal engagement. — stakeholder, safety, session-187

System Requirements (SYS)

Ref Requirement V&V Tags
SYS-SYSTEM-LEVELREQUIREMENTS-001 The Naval Combat Management System SHALL simultaneously maintain at least 1000 correlated tracks across all sensor domains with a track update rate of not less than 1 Hz for threat-class contacts. — system, performance, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-002 The Naval Combat Management System SHALL present new sensor detections on the tactical display within 200 milliseconds of sensor report receipt under maximum track load conditions. — system, latency, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-003 The Naval Combat Management System SHALL process anti-air, anti-surface, anti-submarine, and electronic warfare engagements concurrently without degradation to any single warfare domain's track update rate or engagement timeline. — system, concurrent, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-004 The Naval Combat Management System SHALL transmit and receive tactical data via Link 16 (MIL-STD-6016) with message latency not exceeding 3 seconds for J3.2 track messages under normal network loading. — system, datalink, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-005 When a close-in threat is detected within 15 nautical miles, the Naval Combat Management System SHALL complete threat evaluation and present a weapon assignment recommendation to the operator within 2 seconds of initial track correlation. — system, reaction-time, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-006 The Naval Combat Management System SHALL automatically fail over from a primary processing node to a hot-standby backup node within 500 milliseconds without loss of track state or engagement timeline data. — system, redundancy, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-007 The Naval Combat Management System SHALL detect and isolate hardware faults to the line-replaceable unit level within 60 seconds of fault occurrence and report the fault to the operator console with a recommended corrective action. — system, bit, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-008 While in training mode, the Naval Combat Management System SHALL prevent all simulated engagement commands from reaching weapon control circuits through a hardware-enforced train/operate interlock that cannot be overridden by software. — system, safety, training, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-009 The Naval Combat Management System SHALL enforce a minimum three-level authorization chain for weapon release consisting of operator designation, warfare coordinator approval, and commanding officer confirmation, with no single point of failure capable of bypassing this chain. — system, safety, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-010 When EMCON condition is set, the Naval Combat Management System SHALL suppress all active sensor emissions and data link transmissions within 500 milliseconds of EMCON command receipt while maintaining passive sensor processing and track management. — system, emcon, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-011 The Naval Combat Management System SHALL implement network intrusion detection and cross-domain security guards to prevent unauthorized access to classified track data and weapon control functions across all internal and external network interfaces. — system, cybersecurity, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-012 The Naval Combat Management System SHALL operate continuously in a maritime electromagnetic environment with ambient temperatures of 0 to 55 degrees Celsius, relative humidity up to 95 percent, and ship motion up to Sea State 6 without performance degradation. — system, environmental, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-013 The Naval Combat Management System equipment SHALL be housed in standard 19-inch equipment racks with shock-mounted line-replaceable units conforming to MIL-S-901D Grade A shock requirements and MIL-STD-167 vibration limits for shipboard installation in the combat information center and adjacent electronics spaces. — system, physical, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-014 While operating in degraded mode following loss of up to 30 percent of processing capacity, the Naval Combat Management System SHALL maintain a minimum track capacity of 500 tracks, sensor-to-display latency of not more than 500 milliseconds, and single-warfare-domain engagement capability. — system, degraded-mode, session-187
SYS-SYSTEM-LEVELREQUIREMENTS-015 The Naval Combat Management System equipment SHALL be distributed across no fewer than two physically separated compartments on the ship, with sufficient equipment in each compartment to maintain degraded-mode combat operations following loss of one compartment due to battle damage or flooding. — system, survivability, physical, session-197, validation
SYS-SYSTEM-LEVELREQUIREMENTS-016 While operating in degraded mode following loss of up to 30 percent of processing capacity, the Naval Combat Management System SHALL maintain a minimum of 500 simultaneous correlated tracks, a sensor-to-display latency not exceeding 500 milliseconds, a COP refresh rate of at least 10 Hz, and single-warfare-area engagement capability. — system, degraded-mode, session-197, validation

Subsystem Requirements (SUB)

Ref Requirement V&V Tags
SUB-SUBSYSTEMREQUIREMENTS-001 The Threat Evaluation Engine SHALL complete a full threat priority re-evaluation cycle within 100 milliseconds for up to 200 simultaneous tracks. — subsystem, tewa, performance, session-188
SUB-SUBSYSTEMREQUIREMENTS-002 When a threat is classified as close-in (within 15 nautical miles), the Weapon Assignment Optimizer SHALL produce an initial weapon assignment within 500 milliseconds of threat priority list update. — subsystem, tewa, performance, session-188
SUB-SUBSYSTEMREQUIREMENTS-003 The Kill Assessment Module SHALL provide an engagement outcome determination with confidence level within 5 seconds of estimated weapon impact time. — subsystem, tewa, performance, session-188
SUB-SUBSYSTEMREQUIREMENTS-004 The Engagement Scheduler SHALL deconflict all weapon engagements to ensure no two engagements require the same fire control channel simultaneously, accounting for illumination time, flyout time, and terminal guidance requirements. — subsystem, tewa, safety, session-188
SUB-SUBSYSTEMREQUIREMENTS-005 The Doctrine and Rules of Engagement Database SHALL enforce weapon release authority levels such that no engagement command is issued without the required authorization level for the threat category and engagement mode. — subsystem, tewa, safety, session-188
SUB-SUBSYSTEMREQUIREMENTS-006 The Tactical Decision Aid SHALL support fully automatic, semi-automatic, and manual engagement modes, with mode selection requiring Tactical Action Officer authorization. — subsystem, tewa, functional, session-188
SUB-SUBSYSTEMREQUIREMENTS-007 The Weapon Assignment Optimizer SHALL support shoot-look-shoot engagement doctrine, withholding second salvo assignment until kill assessment is received or assessment timeout expires. — subsystem, tewa, functional, session-188
SUB-SUBSYSTEMREQUIREMENTS-008 The Doctrine and Rules of Engagement Database SHALL prevent weapon engagement commands for any target whose predicted intercept point falls within a defined no-fire zone polygon. — subsystem, tewa, safety, session-188
SUB-SUBSYSTEMREQUIREMENTS-009 While operating with degraded processing capacity, the Threat Evaluation Engine SHALL prioritize evaluation of tracks classified as hostile over tracks classified as unknown or pending, maintaining evaluation cycle time for the highest-priority 50 tracks. — subsystem, tewa, degraded, session-188
SUB-SUBSYSTEMREQUIREMENTS-010 When EMCON condition is set, the Engagement Scheduler SHALL exclude weapon systems requiring active radar illumination from the engagement plan unless overridden by the Commanding Officer. — subsystem, tewa, emcon, session-188
SUB-SUBSYSTEMREQUIREMENTS-011 The Track Management Subsystem SHALL maintain at least 1500 simultaneous correlated system tracks across air, surface, and subsurface domains with no degradation in update rate or correlation accuracy. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-012 The Multi-Sensor Data Associator SHALL complete a full detection-to-track correlation cycle within 200 milliseconds for the worst-case load of 2000 sensor detections against 1500 active tracks. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-013 The Track State Estimator SHALL achieve a root-mean-square position error of less than 50 metres for air tracks at 100 nautical miles range and less than 200 metres for surface tracks at 50 nautical miles range when receiving updates from at least one tracking sensor. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-014 The Track Management Subsystem SHALL maintain at least 1500 simultaneous correlated system tracks across air, surface, and subsurface domains with no degradation in update rate or correlation accuracy. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-015 The Track Identity Classifier SHALL determine initial track identity category (friendly, assumed friendly, neutral, suspect, hostile, unknown) within 2 seconds of receiving the first IFF response or ESM intercept correlation for a new track. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-016 The Track Database Manager SHALL disseminate track state updates to all subscribed CMS subsystems within 100 milliseconds of the track state being updated by the Track State Estimator or Track Identity Classifier. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-017 The Multi-Sensor Data Associator SHALL achieve a false track-to-detection association rate of less than 1 percent under conditions of 200 or more active tracks with crossing geometries within a 5 nautical mile radius. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-018 When a tracked target is no longer detected by any sensor, the Track State Estimator SHALL maintain a predicted track using the last known kinematic state for at least 30 seconds for air tracks, 120 seconds for surface tracks, and 300 seconds for subsurface tracks before the track is flagged for operator review. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-019 The External Track Interface SHALL correlate tracks received via Link 16 and Link 11 with locally-held tracks using a gating window of 5 nautical miles in position and 10 seconds in time, and SHALL present uncorrelated external tracks as composite tracks within 3 seconds of message receipt. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-020 The Sensor Data Preprocessor SHALL accept and normalize sensor reports from at least 8 concurrent sensor feeds at a combined peak rate of 2000 plots per second, performing coordinate transformation from sensor-relative to WGS-84 geographic coordinates within 10 milliseconds per report. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-021 While operating with one or more sensor feeds failed, the Track Management Subsystem SHALL continue tracking using remaining sensors with graceful accuracy degradation, and SHALL flag affected tracks with reduced confidence indicators within 1 second of sensor loss detection. — subsystem, track-management, session-190
SUB-SUBSYSTEMREQUIREMENTS-022 The Fire Control Computer SHALL complete a full firing solution update cycle within 100 milliseconds for anti-air engagements and within 500 milliseconds for anti-surface engagements. — subsystem, weapon-control, fire-control, session-191
SUB-SUBSYSTEMREQUIREMENTS-023 The Fire Control Computer SHALL support at least 8 simultaneous engagement channels across all weapon types, with independent firing solutions computed for each channel. — subsystem, weapon-control, fire-control, session-191
SUB-SUBSYSTEMREQUIREMENTS-024 The Missile Engagement Controller SHALL support salvo launches from a vertical launch system with a minimum interval of 2 seconds between successive missiles from the same cell group. — subsystem, weapon-control, missile, session-191
SUB-SUBSYSTEMREQUIREMENTS-025 The Missile Engagement Controller SHALL generate midcourse guidance commands for semi-active and command-guided missiles at a rate of not less than 2 Hz until seeker handover. — subsystem, weapon-control, missile, session-191
SUB-SUBSYSTEMREQUIREMENTS-026 The Gun Fire Control System SHALL achieve a first-round hit probability of not less than 50 percent against a 10-metre radar cross-section surface target at 12 kilometres range in sea state 4. — subsystem, weapon-control, gun, session-191
SUB-SUBSYSTEMREQUIREMENTS-027 The Fire Control Computer SHALL update the launch acceptability region for each assigned target at a rate of not less than 10 Hz. — subsystem, weapon-control, fire-control, session-191
SUB-SUBSYSTEMREQUIREMENTS-028 The Gun Fire Control System SHALL provide continuous aim-point corrections to gun servo systems at a rate of 50 Hz with ballistic model corrections for barrel wear, muzzle velocity variation, and environmental conditions. — subsystem, weapon-control, gun, session-191
SUB-SUBSYSTEMREQUIREMENTS-029 The Close-In Weapon System Interface SHALL support CMS-directed, autonomous, and standby operating modes and SHALL transition between modes within 500 milliseconds of operator command. — subsystem, weapon-control, ciws, session-191
SUB-SUBSYSTEMREQUIREMENTS-030 The Close-In Weapon System Interface SHALL enforce CMS-defined no-fire safety sectors and SHALL inhibit CIWS engagement of targets within those sectors even in autonomous mode. — subsystem, weapon-control, ciws, session-191
SUB-SUBSYSTEMREQUIREMENTS-031 When a missile threat warning is received from the Electronic Warfare Subsystem, the Decoy and Countermeasure Controller SHALL compute and initiate the appropriate countermeasure deployment sequence within 2 seconds. — subsystem, weapon-control, decoy, session-191
SUB-SUBSYSTEMREQUIREMENTS-032 The Decoy and Countermeasure Controller SHALL compute chaff bloom dispersion patterns corrected for measured wind speed and direction to ensure effective radar cross-section coverage of the defended area. — subsystem, weapon-control, decoy, session-191
SUB-SUBSYSTEMREQUIREMENTS-033 The Weapon Safety Interlock Manager SHALL enforce a three-level authorization sequence for weapon release: weapon system power-on by operator, weapon arming by Officer of the Watch, and weapon release authority by Commanding Officer or delegated authority. — subsystem, weapon-control, safety, session-191
SUB-SUBSYSTEMREQUIREMENTS-034 When communication with any weapon system is lost or an interlock signal is in an indeterminate state, the Weapon Safety Interlock Manager SHALL command the affected weapon to safe condition within 100 milliseconds. — subsystem, weapon-control, safety, session-191
SUB-SUBSYSTEMREQUIREMENTS-035 The Weapon Safety Interlock Manager SHALL prevent weapon discharge into operator-defined no-fire sectors and SHALL dynamically update sector definitions based on own-ship heading and friendly unit positions from the tactical picture. — subsystem, weapon-control, safety, session-191
SUB-SUBSYSTEMREQUIREMENTS-036 The Weapon Inventory Manager SHALL maintain real-time status for every individual weapon round and missile, tracking states of stowed, loaded, armed, expended, and failed, with status updates propagated within 1 second of state change. — subsystem, weapon-control, inventory, session-191
SUB-SUBSYSTEMREQUIREMENTS-037 The Weapon Inventory Manager SHALL compute remaining engagement capacity by threat category and SHALL alert operators when any weapon type falls below 25 percent of initial load-out. — subsystem, weapon-control, inventory, session-191
SUB-SUBSYSTEMREQUIREMENTS-038 The Sensor Management Subsystem SHALL simultaneously manage at least 12 sensor feeds including multi-function phased array radar, fire control illuminators, hull-mounted sonar, towed array sonar, ESM receivers, IFF interrogator, and EO/IR sensors, with independent data paths for each sensor type. — subsystem, sensor-management, session-192
SUB-SUBSYSTEMREQUIREMENTS-039 The Radar Interface Manager SHALL deliver formatted radar detection reports to the Sensor Data Preprocessor within 25 milliseconds of detection event, including range (to 0.1 NM resolution), bearing (to 0.1 degree), elevation (to 0.5 degree), radial velocity (to 1 m/s), and signal-to-noise ratio. — subsystem, sensor-management, radar, session-192
SUB-SUBSYSTEMREQUIREMENTS-040 The Sonar Interface Processor SHALL process hull-mounted sonar returns in both active and passive modes, providing bearing accuracy of 1 degree or better for contacts within the first convergence zone, and SHALL support simultaneous towed array passive narrowband processing at frequency resolution of 0.1 Hz. — subsystem, sensor-management, sonar, session-192
SUB-SUBSYSTEMREQUIREMENTS-041 When a new emitter is intercepted, the Electronic Support Measures Interface SHALL identify the emitter type against the Emitter Parameter Library within 2 seconds and SHALL generate a threat warning alert within 500 milliseconds when the emitter matches a known fire control radar or missile seeker signature. — subsystem, sensor-management, esm, session-192
SUB-SUBSYSTEMREQUIREMENTS-042 The IFF Interrogator Controller SHALL support Mode 5 Level 2 interrogation compliant with STANAG 4193 Edition 3, managing cryptographic key loading, interrogation scheduling synchronized with radar scan, and SHALL achieve a probability of correct identification of 0.95 or greater for cooperative targets within 200 NM. — subsystem, sensor-management, iff, session-192
SUB-SUBSYSTEMREQUIREMENTS-043 The Electro-Optical and Infrared Sensor Manager SHALL provide target imagery at sufficient resolution for visual identification at ranges up to 15 NM in clear conditions, supporting slew-to-cue positioning from radar track data within 3 seconds of operator command, and SHALL provide automatic contrast target tracking with handoff to the Fire Control Computer. — subsystem, sensor-management, eoir, session-192
SUB-SUBSYSTEMREQUIREMENTS-044 The Sensor Resource Scheduler SHALL resolve conflicting sensor tasking requests within 50 milliseconds using a priority-weighted allocation algorithm that balances surveillance search coverage, track maintenance dwells, fire control illumination requests, and ESM collection requirements. — subsystem, sensor-management, scheduler, session-192
SUB-SUBSYSTEMREQUIREMENTS-045 When EMCON state transitions to a more restrictive level, the Sensor Resource Scheduler SHALL suppress all affected active emitters within 200 milliseconds and SHALL automatically reallocate tasking to passive sensors (ESM, passive sonar, EO/IR) to maintain maximum situational awareness consistent with the emission control state. — subsystem, sensor-management, emcon, session-192
SUB-SUBSYSTEMREQUIREMENTS-046 The Sensor Health Monitor SHALL continuously monitor all sensor equipment, detect hardware faults within 5 seconds of occurrence, and SHALL report degraded sensor capability to the Sensor Resource Scheduler with quantified performance impact so that sensor tasking is adjusted to exclude failed elements or assign reduced-capability modes. — subsystem, sensor-management, health, session-192
SUB-SUBSYSTEMREQUIREMENTS-047 The Radar Interface Manager SHALL coordinate phased array radar resource allocation between volume search (maintaining 360-degree coverage with revisit rate of 4 seconds or less), precision track dwells (track accuracy of 0.3 degrees in azimuth/elevation), and missile illumination windows, ensuring that no single function consumes more than 60 percent of total radar time. — subsystem, sensor-management, radar, session-192
SUB-SUBSYSTEMREQUIREMENTS-048 While the ship speed exceeds 15 knots, the Sonar Interface Processor SHALL apply adaptive own-ship noise cancellation to maintain a detection performance degradation of no more than 6 dB relative to quiet-ship baseline for hull-mounted sonar. — subsystem, sensor-management, sonar, session-192
SUB-SUBSYSTEMREQUIREMENTS-049 The Electronic Attack Controller SHALL initiate jamming against a newly detected threat emitter within 500 milliseconds of receiving the emitter identification and parameters from the EW Threat Library. — subsystem, electronic-warfare, ea, session-193
SUB-SUBSYSTEMREQUIREMENTS-050 The Electronic Attack Controller SHALL support simultaneous jamming of at least 4 independent threat emitters across the 0.5-18 GHz frequency range using independently steerable jamming beams. — subsystem, electronic-warfare, ea, session-193
SUB-SUBSYSTEMREQUIREMENTS-051 The EW Threat Library SHALL maintain a database of at least 10,000 emitter parametric sets and SHALL correlate an intercepted emitter against the database within 200 milliseconds of initial intercept with a correct identification rate of at least 95% for known emitter types. — subsystem, electronic-warfare, threat-library, session-193
SUB-SUBSYSTEMREQUIREMENTS-052 The EW Threat Library SHALL support field-programmable updates to emitter parametric data via the Communications Management Subsystem without requiring system restart, with updates applied within 30 seconds of receipt. — subsystem, electronic-warfare, threat-library, session-193
SUB-SUBSYSTEMREQUIREMENTS-053 The Electronic Attack Controller SHALL initiate jamming against a newly detected threat emitter within 500 milliseconds of receiving the emitter identification and parameters from the EW Threat Library. — subsystem, electronic-warfare, ea, session-193
SUB-SUBSYSTEMREQUIREMENTS-054 The Electronic Attack Controller SHALL support simultaneous jamming of at least 4 independent threat emitters across the 0.5-18 GHz frequency range using independently steerable jamming beams. — subsystem, electronic-warfare, ea, session-193
SUB-SUBSYSTEMREQUIREMENTS-055 The EW Threat Library SHALL maintain a database of at least 10,000 emitter parametric sets and SHALL correlate an intercepted emitter against the database within 200 milliseconds of initial intercept with a correct identification rate of at least 95% for known emitter types. — subsystem, electronic-warfare, threat-library, session-193
SUB-SUBSYSTEMREQUIREMENTS-056 The EW Threat Library SHALL support field-programmable updates to emitter parametric data via the Communications Management Subsystem without requiring system restart, with updates applied within 30 seconds of receipt. — subsystem, electronic-warfare, threat-library, session-193
SUB-SUBSYSTEMREQUIREMENTS-057 The EMCON Manager SHALL enforce EMCON state transitions across all ship radiating subsystems within 2 seconds of receiving a state change command, and SHALL verify compliance of all controlled emitters within 5 seconds. — subsystem, electronic-warfare, emcon, session-193
SUB-SUBSYSTEMREQUIREMENTS-058 While in EMCON silent state, the EMCON Manager SHALL inhibit all ship RF emissions and SHALL generate an immediate alert to the commanding officer if any unauthorized emission is detected from a controlled subsystem. — subsystem, electronic-warfare, emcon, safety, session-193
SUB-SUBSYSTEMREQUIREMENTS-059 The Countermeasure Sequencer SHALL generate and initiate a soft-kill countermeasure deployment sequence within 2 seconds of threat declaration, selecting countermeasure type based on the identified missile seeker type (RF, IR, or dual-mode). — subsystem, electronic-warfare, countermeasure, session-193
SUB-SUBSYSTEMREQUIREMENTS-060 The EW Situational Awareness Processor SHALL maintain a real-time electronic order of battle updated at a minimum rate of 2 Hz, correlating ESM detections with kinematic tracks and geo-locating emitters to an accuracy of 2 degrees RMS in bearing using single-ship triangulation. — subsystem, electronic-warfare, ew-sa, session-193
SUB-SUBSYSTEMREQUIREMENTS-061 The EW Situational Awareness Processor SHALL compute and display threat engagement zones (weapon engagement rings) for all identified emitter-weapon platform pairings, updating threat ring geometry within 1 second of track state change. — subsystem, electronic-warfare, ew-sa, session-193
SUB-SUBSYSTEMREQUIREMENTS-062 The Electronic Attack Controller SHALL cease jamming within 100 milliseconds of receiving an EMCON inhibit command from the EMCON Manager, regardless of active engagement status. — subsystem, electronic-warfare, ea, emcon, safety, session-193
SUB-SUBSYSTEMREQUIREMENTS-063 The Tactical Data Link Processor SHALL transmit and receive Link-16 J-series messages at the full JTIDS terminal rate of 238.095 kbps with message processing latency not exceeding 50 ms from receipt to internal distribution. — subsystem, comms, tdl, session-194
SUB-SUBSYSTEMREQUIREMENTS-064 The Tactical Data Link Processor SHALL maintain simultaneous participation in up to 3 Link-16 networks and 1 Link-22 multicast group, with automatic network time reference unit synchronization accuracy within 11.98 microseconds. — subsystem, comms, tdl, session-194
SUB-SUBSYSTEMREQUIREMENTS-065 The SATCOM Interface Controller SHALL maintain at least one beyond-line-of-sight communication channel with 99.5% availability, automatically switching between UHF, SHF, and EHF SATCOM bearers based on link quality and precedence requirements. — subsystem, comms, satcom, session-194
SUB-SUBSYSTEMREQUIREMENTS-066 The Radio Circuit Manager SHALL support simultaneous management of at least 30 radio circuits across HF (2-30 MHz), VHF (30-88 MHz), and UHF (225-400 MHz) bands with circuit switching time not exceeding 200 ms. — subsystem, comms, radio, session-194
SUB-SUBSYSTEMREQUIREMENTS-067 The Message Distribution Server SHALL route at least 500 formatted messages per minute across all precedence levels (Flash, Immediate, Priority, Routine) with guaranteed delivery confirmation and duplicate detection. — subsystem, comms, message, session-194
SUB-SUBSYSTEMREQUIREMENTS-068 When a Flash precedence message is received, the Message Distribution Server SHALL preempt lower-precedence message processing and deliver the Flash message to all addressed subscribers within 500 ms. — subsystem, comms, message, session-194
SUB-SUBSYSTEMREQUIREMENTS-069 The COMSEC Key Management Module SHALL manage at least 200 concurrent Type-1 cryptographic keys across all communication circuits with automated key period rollover and over-the-air rekeying per EKMS procedures. — subsystem, comms, comsec, session-194
SUB-SUBSYSTEMREQUIREMENTS-070 When an emergency zeroize command is issued, the COMSEC Key Management Module SHALL destroy all stored key material across all connected crypto devices within 10 seconds with confirmation reporting. — subsystem, comms, comsec, safety, session-194
SUB-SUBSYSTEMREQUIREMENTS-071 The Network Management Controller SHALL maintain combat system LAN availability of at least 99.99% through dual-redundant network paths with automatic failover completing within 50 ms of primary path failure detection. — subsystem, comms, network, session-194
SUB-SUBSYSTEMREQUIREMENTS-072 The Network Management Controller SHALL enforce VLAN-based classification domain separation between UNCLASSIFIED, SECRET, and TS/SCI network segments with cross-domain guard policies preventing unauthorised data transfer between domains. — subsystem, comms, network, cybersecurity, session-194
SUB-SUBSYSTEMREQUIREMENTS-073 When EMCON condition is set, the Communications Management Subsystem SHALL suppress all RF transmissions on tactical data links, SATCOM uplinks, and radio circuits within 500 ms while maintaining receive-only capability on all bearers. — subsystem, comms, emcon, session-194
SUB-SUBSYSTEMREQUIREMENTS-074 The Radio Circuit Manager SHALL support automatic link establishment on HF circuits per MIL-STD-188-141B with link setup time not exceeding 15 seconds and automatic frequency selection from a scan list of at least 20 preset frequencies. — subsystem, comms, radio, session-194
SUB-SUBSYSTEMREQUIREMENTS-075 The Ownship Data Fusion Processor SHALL provide a fused ownship state vector (position, velocity, heading, attitude) to all subscribing CMS subsystems at a minimum rate of 20 Hz with position accuracy better than 15 metres CEP under GPS-aided conditions. — subsystem, nav, ownship, session-194
SUB-SUBSYSTEMREQUIREMENTS-076 When GPS signal is lost, the Ownship Data Fusion Processor SHALL continue providing ownship position using INS-only dead reckoning corrected by speed log, with position drift not exceeding 1 nautical mile per hour of GPS denial. — subsystem, nav, gps-denied, session-194
SUB-SUBSYSTEMREQUIREMENTS-077 The Inertial Navigation System Interface SHALL receive attitude data (roll, pitch, heading) at 50 Hz via MIL-STD-1553B with heading accuracy of 0.1 degrees secant latitude and attitude accuracy of 0.05 degrees. — subsystem, nav, ins, session-194
SUB-SUBSYSTEMREQUIREMENTS-078 The GPS Receiver Interface SHALL detect loss of GPS integrity via RAIM and report GPS-denied condition to the Ownship Data Fusion Processor within 1 second of integrity threshold violation. — subsystem, nav, gps, session-194
SUB-SUBSYSTEMREQUIREMENTS-079 The Platform Systems Gateway SHALL receive and distribute ship platform status including propulsion plant state, electrical power generation status, and damage control reports to the CMS with update rate of at least 1 Hz and latency not exceeding 500 ms. — subsystem, nav, platform, session-194
SUB-SUBSYSTEMREQUIREMENTS-080 The Autopilot and Helm Interface SHALL enforce safety interlocks preventing CMS-commanded course changes that would result in rudder angles exceeding 35 degrees at speeds above 20 knots or helm rates exceeding 5 degrees per second. — subsystem, nav, helm, safety, session-194
SUB-SUBSYSTEMREQUIREMENTS-081 The Ownship Data Fusion Processor SHALL detect and exclude faulty navigation sensor inputs within 2 seconds of fault onset using consistency cross-checks between INS, GPS, and speed log, and SHALL report the excluded source to the operator. — subsystem, nav, fault-detection, session-194
SUB-SUBSYSTEMREQUIREMENTS-082 The Common Operating Picture Generator SHALL render a unified geospatial display incorporating at least 1500 simultaneous tracks with MIL-STD-2525D symbology, threat range rings, weapon engagement zones, and sensor coverage arcs at a minimum refresh rate of 30 Hz. — subsystem, display, cop, session-195
SUB-SUBSYSTEMREQUIREMENTS-083 The Common Operating Picture Generator SHALL support simultaneous display of at least four independent map views with selectable projections (Mercator, polar stereographic, Gnomonic) and scale levels from 1 nm to 500 nm range. — subsystem, display, cop, session-195
SUB-SUBSYSTEMREQUIREMENTS-084 The Alert and Warning Manager SHALL implement a four-level alert priority hierarchy (critical, warning, caution, advisory) with configurable suppression rules to prevent alarm fatigue, and SHALL annunciate critical alerts within 200 milliseconds of trigger receipt. — subsystem, display, alert, session-195
SUB-SUBSYSTEMREQUIREMENTS-085 The Operator Action Processor SHALL enforce role-based access control with at least five distinct operator roles (TAO, AAWC, ASUWC, ASWC, EWC) and SHALL require two-person confirmation for weapon engagement commands. — subsystem, display, operator, safety, session-195
SUB-SUBSYSTEMREQUIREMENTS-086 The Tactical Data Recorder SHALL continuously record all CMS data flows with GPS-synchronized timestamps and a minimum recording capacity of 72 hours at full system load, with battery-backed write cache to survive power interruptions. — subsystem, display, recorder, session-195
SUB-SUBSYSTEMREQUIREMENTS-087 The Display Configuration Manager SHALL support hot-switching between warfare area display configurations (AAW, ASUW, ASW, EW) in under 2 seconds during operator role handover. — subsystem, display, config, session-195
SUB-SUBSYSTEMREQUIREMENTS-088 The Tactical Console Workstation SHALL provide at least three high-resolution displays (minimum 2560x1440 each) with NVG-compatible backlighting and luminance adjustable from 0.1 to 300 cd/m2 for darkened CIC operations. — subsystem, display, console, session-195
SUB-SUBSYSTEMREQUIREMENTS-089 The Operator Action Processor SHALL log all operator actions with timestamp, operator ID, console ID, and command parameters to the Tactical Data Recorder within 50 milliseconds of action execution. — subsystem, display, operator, audit, session-195
SUB-SUBSYSTEMREQUIREMENTS-090 When a track is designated hostile by the Track Identity Classifier, the Alert and Warning Manager SHALL generate an audible warning tone and flash the track symbol on all active tactical displays within 500 milliseconds. — subsystem, display, alert, threat, session-195
SUB-SUBSYSTEMREQUIREMENTS-091 The Tactical Data Recorder SHALL support real-time replay of recorded data at variable speed (0.25x to 8x) with time-indexed search by event type, track ID, and operator action. — subsystem, display, recorder, replay, session-195
SUB-SUBSYSTEMREQUIREMENTS-092 While in degraded mode with reduced processing capacity, the Common Operating Picture Generator SHALL maintain a minimum refresh rate of 10 Hz and SHALL prioritize rendering of hostile and unknown tracks over neutral tracks. — subsystem, display, cop, degraded, session-195
SUB-SUBSYSTEMREQUIREMENTS-093 The Combat System Server SHALL provide sufficient processing capacity to host all CMS application partitions with a minimum 30 percent processing headroom under peak combat load, using ARINC 653-compliant temporal and spatial partitioning. — subsystem, infra, server, session-195
SUB-SUBSYSTEMREQUIREMENTS-094 The Redundancy and Failover Controller SHALL detect processor or bus failures within 50 milliseconds and complete automatic failover to a hot-standby server with full application state transfer within 500 milliseconds. — subsystem, infra, failover, session-195
SUB-SUBSYSTEMREQUIREMENTS-095 The Combat System LAN Switch SHALL provide dual-redundant 10 Gbps backbone transport with deterministic latency below 50 microseconds per hop and hardware-enforced VLAN-based classification domain separation. — subsystem, infra, network, session-195
SUB-SUBSYSTEMREQUIREMENTS-096 The Time Distribution Unit SHALL maintain system-wide time synchronization accuracy within 100 nanoseconds using IEEE 1588 PTP grandmaster, with rubidium holdover drift less than 1 microsecond per day during GPS-denied operations. — subsystem, infra, timing, session-195
SUB-SUBSYSTEMREQUIREMENTS-097 The System Health and Diagnostics Monitor SHALL continuously monitor all processing nodes and network switches, detect degradation trends, and trigger preventive maintenance alerts at least 100 operating hours before predicted failure. — subsystem, infra, health, session-195
SUB-SUBSYSTEMREQUIREMENTS-098 The Data Processing Infrastructure Subsystem SHALL achieve overall availability of 99.99 percent through N+1 redundancy of combat system servers, dual-redundant LAN switches, and automatic workload redistribution. — subsystem, infra, availability, session-195
SUB-SUBSYSTEMREQUIREMENTS-099 The Scenario Generator SHALL support at least 200 pre-built training scenarios covering AAW, ASUW, ASW, and multi-warfare exercises, with the ability to generate up to 500 simultaneous synthetic tracks with realistic kinematics and radar cross-section profiles. — subsystem, training, scenario, session-195
SUB-SUBSYSTEMREQUIREMENTS-100 The Synthetic Environment Interface SHALL inject synthetic sensor data into the CMS processing pipeline using identical message formats and timing characteristics as live sensor feeds, with a hardware-enforced relay preventing synthetic data from reaching weapon control channels. — subsystem, training, synthetic, safety, session-195
SUB-SUBSYSTEMREQUIREMENTS-101 The Training Mode Controller SHALL require Commanding Officer authorization to transition between live and training modes, and SHALL maintain a persistent, non-overridable LIVE or TRAINING mode indicator on all operator displays with distinct color coding. — subsystem, training, mode, safety, session-195
SUB-SUBSYSTEMREQUIREMENTS-102 When training mode is active, the Training Mode Controller SHALL inhibit all weapon engagement commands and SHALL ensure that the Weapon Safety Interlock Manager blocks all weapon discharge paths regardless of operator input. — subsystem, training, safety, weapon, session-195
SUB-SUBSYSTEMREQUIREMENTS-103 The After-Action Review Processor SHALL replay recorded training exercises with synchronized tactical data, operator actions, and instructor annotations at variable playback speeds from 0.25x to 8x, and SHALL compute operator performance metrics including threat reaction time and engagement success rate. — subsystem, training, aar, session-195
SUB-SUBSYSTEMREQUIREMENTS-104 The Electronic Attack Controller SHALL be housed in a single 6U VME line-replaceable unit with MIL-STD-461G EMI shielding, integrated forced-air cooling, and a mean time between failures of not less than 5,000 hours in the shipboard combat information center environment. — subsystem, ew, physical, qc-fix, session-196
SUB-SUBSYSTEMREQUIREMENTS-105 The Electronic Attack Controller SHALL be housed in a single 6U VME line-replaceable unit with MIL-STD-461G EMI shielding, integrated forced-air cooling, and a mean time between failures of not less than 5000 hours in the shipboard combat information center environment. — subsystem, ew, physical, qc-fix, session-196
SUB-SUBSYSTEMREQUIREMENTS-106 While operating with degraded processing capacity of 70 percent or less of nominal, the Threat Evaluation Engine SHALL complete threat evaluation for the highest-priority 50 tracks within 3 seconds per evaluation cycle, and SHALL provide weapon assignment recommendations for the 10 highest-threat tracks within 5 seconds of track correlation. — subsystem, tewa, degraded-mode, qc-fix, session-196
SUB-SUBSYSTEMREQUIREMENTS-107 While operating with degraded processing capacity of 70 percent or less of nominal, the Threat Evaluation Engine SHALL complete threat evaluation for the highest-priority 50 tracks within 3 seconds per evaluation cycle, and SHALL provide weapon assignment recommendations for the 10 highest-threat tracks within 5 seconds of track correlation. — subsystem, tewa, degraded-mode, qc-fix, session-196
SUB-SUBSYSTEMREQUIREMENTS-108 The Torpedo Fire Control Processor SHALL compute torpedo launch solutions for lightweight and heavyweight torpedoes within 2 seconds of target designation, incorporating target bearing, range, depth, course, and speed from sonar track data with weapon preset calculations for enable run, search depth, and acquisition cone. — subsystem, weapon-control, asw, session-197, validation
SUB-SUBSYSTEMREQUIREMENTS-109 The Torpedo Fire Control Processor SHALL interface with the torpedo tube launch system via MIL-STD-1553B dual-redundant data bus, providing weapon presets and launch commands with a safety interlock requiring Weapons Officer authorization before torpedo release. — subsystem, weapon-control, asw, session-197, validation
SUB-SUBSYSTEMREQUIREMENTS-110 The Towed Array Sonar Processor SHALL perform narrowband (LOFAR) and broadband (DEMON) analysis on passive acoustic data from a variable-depth towed hydrophone array, providing bearing accuracy of 0.5 degrees or better in the 10 Hz to 2 kHz frequency band with automatic contact detection and left-right ambiguity resolution. — subsystem, sensor-management, asw, session-197, validation
SUB-SUBSYSTEMREQUIREMENTS-111 While the towed array is deployed and the ship maintains a speed below 12 knots, the Towed Array Sonar Processor SHALL detect submarine contacts at convergence zone ranges exceeding 60 nautical miles with a probability of detection of 0.7 or greater against a quiet diesel-electric submarine. — subsystem, sensor-management, asw, session-197, validation
SUB-SUBSYSTEMREQUIREMENTS-112 The Torpedo Fire Control Processor SHALL compute torpedo launch solutions for lightweight and heavyweight torpedoes within 2 seconds of target designation, incorporating target bearing, range, depth, course, and speed from sonar track data with weapon preset calculations for enable run, search depth, and acquisition cone. — subsystem, weapon-control, asw, session-197, validation, duplicate-of-108

Interface Requirements (IFC)

Ref Requirement V&V Tags
IFC-INTERFACEDEFINITIONS-001 The interface between the Track Management Subsystem and the Threat Evaluation Engine SHALL deliver fused multi-sensor track updates containing track ID, classification, kinematics (position, velocity, acceleration), identification status, and associated confidence levels at a minimum rate of 1 Hz per track via the Combat System Data Bus. — interface, tewa, track-management, session-188
IFC-INTERFACEDEFINITIONS-002 The interface between the Engagement Scheduler and the Weapon Control Subsystem SHALL transmit engagement commands containing target designation, weapon type, fire control channel assignment, and engagement timeline via a dedicated low-latency message queue with guaranteed delivery and command acknowledgement within 200 milliseconds. — interface, tewa, weapon-control, session-188
IFC-INTERFACEDEFINITIONS-003 The interface between the Weapon Control Subsystem and the Kill Assessment Module SHALL provide weapon status reports including launcher readiness, missile flyout status, detonation confirmation, and fire control radar tracking quality at a minimum rate of 2 Hz during active engagements. — interface, tewa, weapon-control, session-188
IFC-INTERFACEDEFINITIONS-004 The interface between the Tactical Decision Aid and the Tactical Display Subsystem SHALL provide threat priority overlays, engagement envelope visualizations, recommended courses of action, and engagement timeline displays formatted as structured display messages compatible with the Multi-Function Console protocol. — interface, tewa, display, session-188
IFC-INTERFACEDEFINITIONS-005 The interface between the Threat Evaluation Engine and the Electronic Warfare Subsystem SHALL exchange threat emitter classification data, jamming effectiveness assessments, and decoy deployment coordination messages to ensure soft-kill and hard-kill engagement plans are mutually consistent. — interface, tewa, electronic-warfare, session-188
IFC-INTERFACEDEFINITIONS-006 The interface between the Weapon Assignment Optimizer and the Communications Management Subsystem SHALL support exchange of cooperative engagement data including own-ship engagement plans and remote track quality sufficient for engage-on-remote capability via Link 16 and CEC data links. — interface, tewa, comms, session-188
IFC-INTERFACEDEFINITIONS-007 The interface between the Sensor Management Subsystem and the Sensor Data Preprocessor SHALL deliver radar plot messages in ASTERIX Category 048 format at the sensor scan rate, sonar contact reports in a standardized UDP datagram format at 1 Hz minimum, and ESM intercept reports with bearing, frequency, and pulse descriptor word within 500 milliseconds of intercept. — interface, track-management, session-190
IFC-INTERFACEDEFINITIONS-008 The interface between the Track Database Manager and the Threat Evaluation and Weapon Assignment Subsystem SHALL provide real-time track state messages containing position, velocity, identity, threat classification, and engagement status at a rate of 1 Hz per track via a multicast publish-subscribe bus with maximum latency of 100 milliseconds. — interface, track-management, session-190
IFC-INTERFACEDEFINITIONS-009 The interface between the Track Database Manager and the Tactical Display and Operator Interface Subsystem SHALL provide the complete system track picture including all track attributes, identity symbology per MIL-STD-2525D, and operator annotations, updated at a minimum rate of 2 Hz for display rendering. — interface, track-management, session-190
IFC-INTERFACEDEFINITIONS-010 The interface between the External Track Interface and the Communications Management Subsystem SHALL exchange tactical data link messages in J-series format for Link 16 (TADIL-J) and M-series format for Link 11 (TADIL-A), with message queuing, prioritization, and time-slot coordination conforming to MIL-STD-6016 and MIL-STD-6011 respectively. — interface, track-management, session-190
IFC-INTERFACEDEFINITIONS-011 The interface between the Navigation and Platform Interface Subsystem and the Sensor Data Preprocessor SHALL provide ownship position (GPS/INS), heading, speed, roll, pitch, and yaw at 20 Hz to support real-time coordinate transformation of sensor-relative detections to geographic coordinates. — interface, track-management, session-190
IFC-INTERFACEDEFINITIONS-012 The interface between the Track Database Manager and the Weapon Control Subsystem SHALL provide fire control quality track data including smoothed position, predicted intercept point, velocity vector, and track quality indicator at 2 Hz per designated track, with position accuracy sufficient for weapon engagement solution computation. — interface, track-management, session-190
IFC-INTERFACEDEFINITIONS-013 The interface between the Fire Control Computer and the Track Management Subsystem SHALL deliver target track state vectors (position, velocity, acceleration in WGS-84) at a rate of not less than 10 Hz per engaged target via the combat system data bus. — interface, weapon-control, session-191
IFC-INTERFACEDEFINITIONS-014 The interface between the Fire Control Computer and the Missile Engagement Controller SHALL transmit firing solution data including target designation, predicted intercept point, launch acceptability region, and time-of-flight via MIL-STD-1553B data bus with a maximum latency of 20 milliseconds. — interface, weapon-control, session-191
IFC-INTERFACEDEFINITIONS-015 The interface between the Fire Control Computer and the Gun Fire Control System SHALL transmit target parameters and engagement mode selection, and SHALL receive gun system status including barrel temperature, rounds remaining, and servo position feedback at 50 Hz. — interface, weapon-control, session-191
IFC-INTERFACEDEFINITIONS-016 The interface between the Weapon Safety Interlock Manager and each weapon effector component SHALL use dual-redundant hardwired discrete signals for safety-critical interlock states, independent of the software data bus, with a maximum detection latency of 10 milliseconds for any interlock state change. — interface, weapon-control, safety, session-191
IFC-INTERFACEDEFINITIONS-017 The interface between the Decoy and Countermeasure Controller and the Electronic Warfare Subsystem SHALL transmit threat warning messages containing threat type, bearing, estimated range, and recommended countermeasure type with an end-to-end latency of less than 500 milliseconds. — interface, weapon-control, decoy, session-191
IFC-INTERFACEDEFINITIONS-018 The interface between the Missile Engagement Controller and the Sensor Management Subsystem SHALL support target illumination scheduling requests and confirmations for semi-active homing missiles, with illuminator assignment confirmed within 200 milliseconds of request. — interface, weapon-control, missile, session-191
IFC-INTERFACEDEFINITIONS-019 The interface between the Radar Interface Manager and the Sensor Data Preprocessor SHALL use a UDP multicast message format on the combat system data bus, carrying detection reports at a sustained rate of up to 2000 detections per second during volume search, with each message containing radar ID, detection time (UTC, 1 microsecond resolution), range, bearing, elevation, Doppler shift, SNR, and waveform identifier. — interface, sensor-management, radar, session-192
IFC-INTERFACEDEFINITIONS-020 The interface between the Electronic Support Measures Interface and the Sensor Data Preprocessor SHALL carry emitter intercept reports including frequency band, pulse characteristics, bearing (to 2 degree accuracy), signal strength, and emitter library match ID, at a rate of up to 500 intercepts per second during dense electromagnetic environments. — interface, sensor-management, esm, session-192
IFC-INTERFACEDEFINITIONS-021 The interface between the Sensor Resource Scheduler and the Track Management Subsystem SHALL support bidirectional messaging: track update requests from Track Management specifying track ID, required accuracy, and priority; and sensor schedule acknowledgements from the Scheduler confirming or denying tasking with expected time of next update. — interface, sensor-management, scheduler, session-192
IFC-INTERFACEDEFINITIONS-022 The interface between the IFF Interrogator Controller and the Track Identity Classifier SHALL carry IFF response decode messages including Mode 1/2/3A/C codes, Mode S address, Mode 5 national origin and platform ID, interrogation timestamp, associated radar track number, and decode confidence level. — interface, sensor-management, iff, session-192
IFC-INTERFACEDEFINITIONS-023 The interface between the Electro-Optical and Infrared Sensor Manager and the Fire Control Computer SHALL provide target angular position (azimuth and elevation) at a minimum update rate of 30 Hz with angular accuracy of 0.5 milliradians, target angular rate, and automatic track lock status for fire control quality tracking. — interface, sensor-management, eoir, session-192
IFC-INTERFACEDEFINITIONS-024 The interface between the Electronic Support Measures Interface and the EW Threat Library SHALL deliver raw intercept data including frequency, pulse repetition interval, pulse width, scan pattern, signal strength, and bearing in STANAG 4545-compliant format at a maximum latency of 50 milliseconds. — interface, electronic-warfare, sensor-management, session-193
IFC-INTERFACEDEFINITIONS-025 The interface between the EW Threat Library and the Electronic Attack Controller SHALL provide emitter identification, operating parameters, and recommended jamming technique in a structured message at a maximum latency of 100 milliseconds from identification completion. — interface, electronic-warfare, session-193
IFC-INTERFACEDEFINITIONS-026 The interface between the EW Situational Awareness Processor and the Track Management Subsystem SHALL exchange track state vectors and ESM-to-track correlation data bidirectionally at a minimum rate of 2 Hz using the combat system data bus. — interface, electronic-warfare, track-management, session-193
IFC-INTERFACEDEFINITIONS-027 The interface between the Countermeasure Sequencer and the Decoy and Countermeasure Controller SHALL transmit countermeasure deployment commands specifying launcher assignment, expendable type, salvo timing, and bloom pattern within 200 milliseconds of sequence generation. — interface, electronic-warfare, weapon-control, session-193
IFC-INTERFACEDEFINITIONS-028 The interface between the EMCON Manager and all ship radiating subsystems SHALL provide positive-sense inhibit/enable control signals, where loss of the control signal SHALL default to the inhibit state (fail-safe silent). — interface, electronic-warfare, emcon, safety, session-193
IFC-INTERFACEDEFINITIONS-029 The interface between the EW Situational Awareness Processor and the Tactical Display and Operator Interface Subsystem SHALL provide the EW tactical picture including geo-located emitter symbols, threat engagement rings, and jamming status overlays, refreshed at a minimum rate of 1 Hz. — interface, electronic-warfare, display, session-193
IFC-INTERFACEDEFINITIONS-030 The interface between the Countermeasure Sequencer and the Threat Evaluation and Weapon Assignment Subsystem SHALL exchange threat declarations and soft-kill/hard-kill coordination messages to enable layered defense scheduling, with a maximum interface latency of 100 milliseconds. — interface, electronic-warfare, tewa, session-193
IFC-INTERFACEDEFINITIONS-031 The interface between the Tactical Data Link Processor and the Track Management Subsystem SHALL exchange track data using J3.2 (air track) and J3.3 (surface track) message formats with track correlation identifiers mapped to internal track numbers within 100 ms of message receipt. — interface, comms, tdl, track, session-194
IFC-INTERFACEDEFINITIONS-032 The interface between the Tactical Data Link Processor and the Threat Evaluation and Weapon Assignment Subsystem SHALL transmit and receive J12.6 engagement status and J7.0 information management messages to support cooperative engagement capability with a maximum end-to-end latency of 200 ms. — interface, comms, tdl, tewa, session-194
IFC-INTERFACEDEFINITIONS-033 The interface between the Message Distribution Server and the Tactical Display and Operator Interface Subsystem SHALL deliver formatted messages for operator display within 1 second of message receipt, with visual and audible alerts for Flash and Immediate precedence messages. — interface, comms, display, session-194
IFC-INTERFACEDEFINITIONS-034 The interface between the COMSEC Key Management Module and the Tactical Data Link Processor SHALL support KGV-11 key loading and OTAR distribution using DS-102 fill interface protocol with crypto key changeover synchronised to Link-16 network time. — interface, comms, comsec, tdl, session-194
IFC-INTERFACEDEFINITIONS-035 The interface between the Network Management Controller and the Data Processing Infrastructure Subsystem SHALL provide SNMP v3-based network health telemetry at 1-second intervals including port utilisation, error rates, and redundancy path status for all combat system LAN segments. — interface, comms, network, infra, session-194
IFC-INTERFACEDEFINITIONS-036 The interface between the Ownship Data Fusion Processor and the Track Management Subsystem SHALL provide ownship position, velocity, and attitude at 20 Hz in WGS-84 geodetic coordinates with a timestamped message format synchronised to GPS time within 1 microsecond. — interface, nav, track, session-194
IFC-INTERFACEDEFINITIONS-037 The interface between the Ownship Data Fusion Processor and the Weapon Control Subsystem SHALL provide ownship kinematic state including roll, pitch, and heading rates at 20 Hz for fire control solution computation with angular rate accuracy of 0.01 degrees per second. — interface, nav, weapon, session-194
IFC-INTERFACEDEFINITIONS-038 The interface between the Platform Systems Gateway and the Tactical Display and Operator Interface Subsystem SHALL present ship platform status including propulsion, power, and damage control states on a dedicated platform overview display with alarm priority colour coding per STANAG 4420. — interface, nav, platform, display, session-194
IFC-INTERFACEDEFINITIONS-039 The interface between the Common Operating Picture Generator and the Track Database Manager SHALL receive track state updates via the combat system LAN using a publish-subscribe protocol with maximum latency of 100 milliseconds from track update to display primitive generation. — interface, display, track, session-195
IFC-INTERFACEDEFINITIONS-040 The interface between the Alert and Warning Manager and the Threat Evaluation Engine SHALL receive threat priority updates and engagement status changes via a dedicated message queue with guaranteed delivery and message ordering. — interface, display, tewa, alert, session-195
IFC-INTERFACEDEFINITIONS-041 The interface between the Operator Action Processor and the Weapon Control Subsystem SHALL transmit weapon engagement commands using a confirmed-delivery protocol with cryptographic authentication of operator identity and role authorization. — interface, display, weapon, safety, session-195
IFC-INTERFACEDEFINITIONS-042 The interface between the Common Operating Picture Generator and the EW Situational Awareness Processor SHALL receive electronic order of battle updates including geo-located emitter positions, threat rings, and jamming effectiveness overlays. — interface, display, ew, session-195
IFC-INTERFACEDEFINITIONS-043 The interface between the Tactical Data Recorder and the Data Processing Infrastructure Subsystem SHALL provide a continuous data capture bus carrying all CMS message traffic at sustained throughput of at least 500 Mbps with no data loss. — interface, display, recorder, infra, session-195
IFC-INTERFACEDEFINITIONS-044 The interface between the Combat System LAN Switch and all CMS subsystems SHALL provide deterministic message delivery with maximum jitter of 10 microseconds for real-time weapon control and sensor data paths. — interface, infra, network, session-195
IFC-INTERFACEDEFINITIONS-045 The interface between the Time Distribution Unit and the GPS Receiver Interface SHALL receive 1PPS and NMEA time data, and SHALL propagate PTP time to all CMS nodes within 100 nanoseconds of GPS reference. — interface, infra, timing, nav, session-195
IFC-INTERFACEDEFINITIONS-046 The interface between the System Health and Diagnostics Monitor and the Tactical Display and Operator Interface Subsystem SHALL provide system readiness status, BIT results, and maintenance alerts for display on the TAO status overview panel. — interface, infra, display, health, session-195
IFC-INTERFACEDEFINITIONS-047 The interface between the Synthetic Environment Interface and the Sensor Management Subsystem SHALL replicate live sensor data message formats including timestamp, data quality flags, and sensor ID fields, ensuring that downstream processing cannot distinguish synthetic from live data. — interface, training, sensor, session-195
IFC-INTERFACEDEFINITIONS-048 The interface between the Training Mode Controller and the Weapon Safety Interlock Manager SHALL provide a hardwired safety signal that physically inhibits weapon discharge circuits when training mode is active, independent of software control paths. — interface, training, weapon, safety, session-195
IFC-INTERFACEDEFINITIONS-049 The interface between the After-Action Review Processor and the Tactical Data Recorder SHALL retrieve recorded training data with time-indexed random access at any point in the recorded exercise within 2 seconds. — interface, training, aar, recorder, session-195
IFC-INTERFACEDEFINITIONS-050 The interface between the Torpedo Fire Control Processor and the Fire Control Computer SHALL exchange torpedo engagement data including target motion analysis parameters, computed launch solutions, and weapon readiness status via the combat system LAN at a minimum update rate of 2 Hz. — interface, weapon-control, asw, session-197, validation
IFC-INTERFACEDEFINITIONS-051 The interface between the Torpedo Fire Control Processor and the Sonar Interface Processor SHALL receive active and passive sonar track data including bearing, range, depth, Doppler, and classification with updates at minimum 1 Hz for designated ASW tracks. — interface, weapon-control, sensor-management, asw, session-197, validation
IFC-INTERFACEDEFINITIONS-052 The interface between the Towed Array Sonar Processor and the Track Management Subsystem SHALL provide passive sonar contact reports with bearing, frequency, and signal-to-noise ratio at a minimum rate of 1 Hz per contact, using the standard CMS sensor report format. — interface, sensor-management, asw, session-197, validation

Architecture Decisions (ARC)

Ref Requirement V&V Tags
ARC-ARCHITECTUREDECISIONS-001 QUALITY NOTE: Requirements SUB-SUBSYSTEMREQUIREMENTS-053 and SUB-SUBSYSTEMREQUIREMENTS-054 are textual duplicates of SUB-SUBSYSTEMREQUIREMENTS-049 and SUB-SUBSYSTEMREQUIREMENTS-050 respectively. Requirements SUB-SUBSYSTEMREQUIREMENTS-055 and SUB-SUBSYSTEMREQUIREMENTS-056 are textual duplicates of SUB-SUBSYSTEMREQUIREMENTS-051 and SUB-SUBSYSTEMREQUIREMENTS-052. The duplicate instances should be consolidated in a future session. — qc-finding, duplicates, session-196

Verification Plan (VER)

Ref Requirement V&V Tags
VER-VERIFICATIONMETHODS-001 The Weapon Safety Interlock Manager authorization sequence SHALL be verified by test demonstrating that weapon release is inhibited when any of the three authorization levels is not satisfied, including single-point failure injection of each interlock channel. — verification, weapon-control, safety, session-191
VER-VERIFICATIONMETHODS-002 The CIWS no-fire sector enforcement SHALL be verified by test with the CIWS in autonomous mode, confirming that targets within defined no-fire sectors are not engaged across all sector boundary conditions. — verification, weapon-control, ciws, session-191
VER-VERIFICATIONMETHODS-003 The Weapon Safety Interlock Manager fail-safe behaviour SHALL be verified by test injecting communication failures on each weapon data bus and confirming weapon-safe state is achieved within 100 milliseconds for all weapon types. — verification, weapon-control, safety, session-191
VER-VERIFICATIONMETHODS-004 The Fire Control Computer firing solution update cycle time SHALL be verified by analysis of timing measurements over 1000 consecutive cycles under maximum engagement load (8 simultaneous channels) confirming 99th percentile completion within 100 milliseconds. — verification, weapon-control, fire-control, session-191
VER-VERIFICATIONMETHODS-005 The Tactical Data Link Processor message throughput (SUB-REQS-063) SHALL be verified by test using a Link-16 network simulator generating J-series traffic at maximum rate while measuring internal distribution latency with instrumented message timestamps. — verification, comms, tdl, session-194
VER-VERIFICATIONMETHODS-006 The COMSEC emergency zeroization (SUB-REQS-070) SHALL be verified by demonstration using test key material loaded into all connected crypto devices, executing the emergency zeroize command, and confirming key destruction within the 10-second threshold via device status query. — verification, comms, comsec, session-194
VER-VERIFICATIONMETHODS-007 The network failover time (SUB-REQS-071) SHALL be verified by test, injecting a link failure on the primary combat system LAN path and measuring switchover time to the redundant path using network analyser capture with microsecond resolution. — verification, comms, network, session-194
VER-VERIFICATIONMETHODS-008 The COP Generator 30 Hz refresh rate (SUB-SUBSYSTEMREQUIREMENTS-082) SHALL be verified by test, measuring actual frame delivery rate under peak track load of 1500 simultaneous targets with all overlay layers active. — verification, display, cop, session-195
VER-VERIFICATIONMETHODS-009 The Redundancy and Failover Controller failover time (SUB-SUBSYSTEMREQUIREMENTS-094) SHALL be verified by test, injecting hardware fault signals into each combat system server and measuring time from fault detection to application resumption on the backup node. — verification, infra, failover, session-195
VER-VERIFICATIONMETHODS-010 The Training Mode Controller weapon inhibit (SUB-SUBSYSTEMREQUIREMENTS-102) SHALL be verified by demonstration, activating training mode and confirming that all weapon discharge circuits are physically interrupted and that no weapon engagement command is accepted by the Weapon Control Subsystem. — verification, training, safety, session-195
VER-VERIFICATIONMETHODS-011 The Time Distribution Unit synchronization accuracy (SUB-SUBSYSTEMREQUIREMENTS-096) SHALL be verified by test, comparing PTP-distributed time at each CMS node against an independent calibrated reference clock over a 24-hour period including simulated GPS denial. — verification, infra, timing, session-195
VER-VERIFICATIONMETHODS-012 The system-level degraded mode capability (SYS-SYSTEM-LEVELREQUIREMENTS-014) SHALL be verified by test, progressively disabling processing nodes to 70 percent capacity and measuring track capacity, sensor-to-display latency, and engagement capability in each warfare domain against the specified thresholds. — verification, degraded-mode, qc-fix, session-196
VER-VERIFICATIONMETHODS-013 The EMCON Manager emission suppression (SUB-SUBSYSTEMREQUIREMENTS-057) SHALL be verified by test using calibrated RF receivers at all ship emission points, commanding EMCON transitions at each restriction level, and confirming that all controlled emitters cease transmission within 2 seconds with zero unauthorized emissions detected over a 30-minute monitoring period. — verification, emcon, qc-fix, session-196
VER-VERIFICATIONMETHODS-014 The network intrusion detection and cross-domain security (SYS-SYSTEM-LEVELREQUIREMENTS-011) SHALL be verified by test using a red-team penetration test against all CMS network interfaces with attack vectors including network scanning, protocol exploitation, and cross-domain data leakage attempts, confirming zero unauthorized access to classified data and weapon control functions. — verification, cybersecurity, qc-fix, session-196
VER-VERIFICATIONMETHODS-015 The torpedo launch safety interlock (SUB-SUBSYSTEMREQUIREMENTS-109) SHALL be verified by demonstration, confirming that torpedo launch commands are inhibited unless Weapons Officer authorization is present, and that all interlock states are correctly reported on the safety console display. — verification, asw, weapon-control, session-197, validation
VER-VERIFICATIONMETHODS-016 The degraded mode performance criteria (SYS-SYSTEM-LEVELREQUIREMENTS-016) SHALL be verified by test, progressively disabling processing nodes to 70 percent capacity and measuring track capacity, sensor-to-display latency, COP refresh rate, and confirming single-warfare-area engagement capability under controlled scenario conditions. — verification, degraded-mode, session-197, validation
VER-VERIFICATIONMETHODS-017 The physical distribution requirement (SYS-SYSTEM-LEVELREQUIREMENTS-015) SHALL be verified by inspection of equipment installation drawings and analysis of compartment separation against ship survivability standards, confirming that loss of any single compartment preserves degraded-mode combat operations. — verification, survivability, session-197, validation

Internal Diagrams

flowchart TB
  n0["component<br>Threat Evaluation Engine"]
  n1["component<br>Weapon Assignment Optimizer"]
  n2["component<br>Engagement Scheduler"]
  n3["component<br>Kill Assessment Module"]
  n4["component<br>Doctrine and ROE Database"]
  n5["component<br>Tactical Decision Aid"]
  n6["external<br>Track Management Subsystem"]
  n7["external<br>Weapon Control Subsystem"]
  n8["external<br>Tactical Display Subsystem"]
  n0 -->|Threat priority list| n1
  n1 -->|Weapon assignments| n2
  n3 -->|Kill/miss assessment| n0
  n4 -->|Weapon-target pairing rules| n1
  n4 -->|Engagement authority levels| n0
  n5 -->|Operator overrides| n1
  n1 -->|Recommended COAs| n5
  n6 -->|Fused track data| n0
  n6 -->|Post-engagement tracks| n3
  n2 -->|Engagement commands| n7
  n7 -->|Weapon status/impact data| n3
  n5 -->|Decision displays| n8

TEWA Subsystem — Internal

flowchart TB
  n0["component<br>Sensor Data Preprocessor"]
  n1["component<br>Multi-Sensor Data Associator"]
  n2["component<br>Track State Estimator"]
  n3["component<br>Track Identity Classifier"]
  n4["component<br>Track Database Manager"]
  n5["component<br>External Track Interface"]
  n0 -->|Detection reports| n1
  n1 -->|Associated detections| n2
  n2 -->|Kinematic state| n3
  n2 -->|Filtered track state| n4
  n3 -->|Identity classification| n4
  n5 -->|External tracks| n1
  n4 -->|Local tracks| n5

Track Management Subsystem — Internal

flowchart TB
  n0["component<br>Fire Control Computer"]
  n1["component<br>Missile Engagement Controller"]
  n2["component<br>Gun Fire Control System"]
  n3["component<br>CIWS Interface"]
  n4["component<br>Decoy and Countermeasure Controller"]
  n5["component<br>Weapon Safety Interlock Manager"]
  n6["component<br>Weapon Inventory Manager"]
  n7["external<br>Track Management Subsystem"]
  n8["external<br>Electronic Warfare Subsystem"]
  n9["external<br>Sensor Management Subsystem"]
  n10["external<br>TEWA Subsystem"]
  n0 -->|Firing solution| n1
  n0 -->|Target params| n2
  n0 -->|Target designation| n3
  n5 -->|Safety status| n0
  n5 -->|Launch authorization| n1
  n5 -->|Fire authorization| n2
  n5 -->|CIWS safety sectors| n3
  n5 -->|Decoy authorization| n4
  n6 -->|Missile inventory| n1
  n6 -->|Ammo status| n2
  n6 -->|CIWS rounds| n3
  n6 -->|Decoy inventory| n4
  n7 -->|Track state vectors| n0
  n8 -->|Threat warning| n4
  n1 -->|Illumination request| n9
  n10 -->|Engagement orders| n0

Weapon Control Subsystem — Internal

flowchart TB
  n0["component<br>Radar Interface Manager"]
  n1["component<br>Sonar Interface Processor"]
  n2["component<br>ESM Interface"]
  n3["component<br>IFF Interrogator Controller"]
  n4["component<br>EO/IR Sensor Manager"]
  n5["component<br>Sensor Resource Scheduler"]
  n6["component<br>Sensor Health Monitor"]
  n7["external<br>Track Management"]
  n8["external<br>Fire Control"]
  n9["external<br>Electronic Warfare"]
  n5 -->|Radar tasking| n0
  n5 -->|Sonar tasking| n1
  n5 -->|ESM tasking| n2
  n5 -->|IFF tasking| n3
  n5 -->|EO/IR tasking| n4
  n6 -->|Availability status| n5
  n6 -->|BIT commands| n0
  n6 -->|BIT commands| n1
  n0 -->|Radar detections| n7
  n1 -->|Sonar contacts| n7
  n2 -->|ESM intercepts| n7
  n3 -->|IFF decodes| n7
  n4 -->|Tracking data| n8
  n2 -->|Threat warnings| n9
  n7 -->|Track update requests| n5

Sensor Management Subsystem — Internal

flowchart TB
  n0["system<br>Electronic Warfare Subsystem"]
  n1["system<br>Electronic Warfare Subsystem"]
  n2["component<br>Electronic Attack Controller"]
  n3["component<br>EW Threat Library"]
  n4["component<br>EMCON Manager"]
  n5["component<br>Countermeasure Sequencer"]
  n6["component<br>EW Situational Awareness Processor"]
  n7["actor<br>ESM Interface (Sensor Mgmt)"]
  n8["actor<br>Track Management Subsystem"]
  n9["actor<br>TEWA Subsystem"]
  n10["actor<br>Decoy Controller (WCS)"]
  n11["actor<br>Tactical Display"]
  n7 -->|Intercept data| n3
  n3 -->|Emitter ID and jamming technique| n2
  n3 -->|Emitter identification| n6
  n6 -->|EW picture and tasking| n2
  n6 -->|ESM-track correlation| n8
  n6 -->|EW tactical picture| n11
  n4 -->|EMCON inhibit/enable| n2
  n5 -->|CM deploy commands| n10
  n5 -->|Soft-kill coordination| n9
  n5 -->|Threat assessment| n6

Electronic Warfare Subsystem — Internal

flowchart TB
  n0["component<br>Tactical Data Link Processor"]
  n1["component<br>SATCOM Interface Controller"]
  n2["component<br>Radio Circuit Manager"]
  n3["component<br>Message Distribution Server"]
  n4["component<br>COMSEC Key Management Module"]
  n5["component<br>Network Management Controller"]
  n0 -->|J-series messages| n3
  n1 -->|BLOS message traffic| n3
  n2 -->|Voice/data circuits| n3
  n4 -->|Crypto keys| n0
  n4 -->|Crypto keys| n1
  n4 -->|Crypto keys| n2
  n5 -->|Network transport| n3

Communications Management — Internal

flowchart TB
  n0["component<br>Inertial Navigation System Interface"]
  n1["component<br>GPS Receiver Interface"]
  n2["component<br>Speed Log Interface"]
  n3["component<br>Platform Systems Gateway"]
  n4["component<br>Ownship Data Fusion Processor"]
  n5["component<br>Autopilot and Helm Interface"]
  n0 -->|Attitude and velocity| n4
  n1 -->|PVT solution| n4
  n2 -->|Speed data| n4
  n3 -->|Platform status| n4
  n4 -->|Helm commands| n5

Navigation and Platform Interface — Internal

Classified Entities

Entity Hex Code Description
After-Action Review Processor 40E57B08 Software component that replays recorded training exercises with synchronized tactical data, operator actions, and decision timeline for debriefing. Retrieves data from the Tactical Data Recorder, overlays instructor annotations, and computes performance metrics (reaction time to threats, engagement success rate, track management accuracy). Generates quantitative training assessment reports comparing operator performance against doctrinal standards. Supports multi-workstation synchronized playback so the entire CIC team can review their collective performance.
Alert and Warning Manager 55FD7B58 Software component managing prioritized visual, audible, and tactile alerts for CMS operators. Receives alert triggers from threat evaluation, weapon safety interlocks, sensor health, platform alarms, and communications precedence events. Implements alert priority hierarchy per STANAG 4586 with suppression rules to prevent alarm fatigue. Generates audible warnings through CIC sound system, visual alerts on operator displays with flash coding.
Autopilot and Helm Interface 51BD7819 Interface between the naval CMS and the ship's autopilot and steering system. Enables CMS-directed course changes for threat avoidance manoeuvres, formation keeping, and weapon engagement geometry optimisation. Provides recommended course/speed to the officer of the watch display. Receives helm orders acknowledgement and rudder angle feedback. Must enforce safety interlocks preventing CMS from commanding unsafe helm angles at speed. Interfaces via dual-redundant serial links to the steering gear control unit.
Close-In Weapon System Interface 50B77819 Interface module between the naval CMS and autonomous Close-In Weapon System (CIWS) mounts such as Phalanx or Goalkeeper. In CMS-directed mode, provides target designation and engagement authorization to CIWS. In autonomous mode, monitors CIWS self-defence engagements and reports status back to CMS for tactical picture updates. Manages CIWS operating mode transitions (standby, manual, auto-engage), safety sector definitions to prevent fratricide, ammunition status monitoring, and engagement coordination when multiple CIWS mounts cover overlapping sectors. Communicates via dedicated high-reliability serial link with < 5ms latency for last-ditch defence scenarios against sea-skimming anti-ship missiles.
Combat System LAN Switch D4A57058 Ruggedized managed Ethernet switch providing the primary data transport fabric for the naval combat management system. Dual-redundant 10 Gbps backbone with deterministic latency below 50 microseconds per hop. Implements IEEE 802.1Q VLAN-based classification domain separation (Secret, NATO Secret, Unclassified) with hardware-enforced cross-domain isolation. Supports IEEE 1588 Precision Time Protocol for nanosecond-level time synchronization across all CMS nodes. MIL-STD-461G EMI compliant.
Combat System Server D2A51018 Ruggedized multi-processor computing node forming the core processing element of the naval CMS data processing infrastructure. Blade-based architecture with dual-redundant Intel Xeon processors, 256 GB ECC RAM, and hardware-accelerated encryption. Runs real-time operating system (VxWorks or LynxOS) for deterministic task scheduling. Hosts CMS application partitions with ARINC 653-style temporal and spatial isolation. Designed for MIL-STD-810G shock and vibration, operates on 440V 60Hz ship power with integrated UPS. MTBF target 20,000 hours.
Common Operating Picture Generator 50F5FB18 Software component that aggregates track data, ownship navigation, chart data, sensor coverage overlays, and engagement status into a unified geospatial display model. Receives track updates from Track Database Manager at up to 1500 tracks, renders MIL-STD-2525D symbology, computes threat range rings, weapon engagement zones, and sensor coverage arcs. Outputs display primitives at 30 Hz refresh to Tactical Console Workstations. Supports multiple simultaneous map projections (Mercator, polar stereographic) and scale levels from 1 nm to 500 nm.
Communications Management Subsystem 50E57918 Manages all internal and external communications for a naval combat management system aboard a surface combatant. Handles tactical data links including Link 16 (JTIDS/MIDS terminal, J-series messages for track reporting, weapon coordination, and electronic warfare), Link 11 (legacy HF/UHF TADIL-A), and Link 22 (NILE). Manages SATCOM circuits (UHF FLTSATCOM, SHF DSCS, EHF AEHF) for beyond-line-of-sight command and intelligence. Provides HF/VHF/UHF radio management for voice communications. Routes messages between internal CMS subsystems and external networks using NATO STANAG message formats. Implements communications security (COMSEC) including key management (KMI/KOV-21), encryption device control, and frequency-hopping coordination. Manages communication plans and EMCON-coordinated transmission scheduling.
COMSEC Key Management Module D0B57859 Communications security key management module for naval CMS. Manages Type-1 NSA-approved cryptographic keys for Link-16 (KGV-11), SATCOM (KG-84/KIV-7), and voice circuits (KY-68/KY-100). Handles over-the-air rekeying (OTAR), key loading from KYK-13/AN/CYZ-10, key inventory tracking, crypto period management, and zeroization on compromise. Interfaces with ship's COMSEC material system. Must comply with EKMS (Electronic Key Management System) and NSA COMSEC accounting requirements.
Countermeasure Sequencer 51F77A19 Soft-kill countermeasure coordination module within a naval EW subsystem. Generates time-ordered countermeasure deployment sequences combining chaff (multiple types: distraction, seduction, centroid), flares, towed radar decoys, and active off-board decoys. Selects countermeasure type and timing based on incoming threat characteristics (missile seeker type, approach bearing, time-to-impact). Coordinates with TEWA for integrated hard-kill/soft-kill layered defense. Manages countermeasure expendable inventory. Interfaces with the Weapon Control Subsystem's Decoy and Countermeasure Controller for physical launcher actuation. Must generate and initiate a countermeasure sequence within 2 seconds of threat declaration.
Data Processing Infrastructure Subsystem 50B73019 Core computing and networking infrastructure for a naval combat management system. Comprises redundant multi-processor server clusters (typically dual-redundant with hot standby) running a real-time operating system certified to DO-178C DAL-A or equivalent military safety standard. Provides deterministic task scheduling with guaranteed worst-case execution times for safety-critical weapon engagement computations. Implements a dual-redundant switched Fibre Channel or 10Gbit Ethernet backbone with hardware-enforced traffic prioritization (time-triggered Ethernet or AFDX-like deterministic networking). Manages automatic failover between primary and backup processing nodes within <500ms to maintain combat capability under battle damage. Provides cybersecurity functions including network intrusion detection, data-at-rest encryption for classified databases, and cross-domain guard for interfacing different security classification levels. Supports system recording (all tracks, engagements, operator actions) for post-mission analysis.
Decoy and Countermeasure Controller 51B77A39 Controls deployment of soft-kill countermeasures from a naval vessel. Manages chaff launchers (SRBOC/DL-12T class), infrared decoy launchers, towed torpedo decoys (SLQ-25 Nixie class), and expendable acoustic countermeasure (sonobuoy) launchers. Receives threat warning data from the Electronic Warfare subsystem and computes optimal decoy deployment patterns based on threat bearing, threat type (radar-guided missile, IR-guided missile, torpedo), wind conditions, and own-ship manoeuvre. Implements pre-programmed countermeasure response sequences that can execute within 2 seconds of threat detection. Tracks decoy inventory and launcher readiness. Interfaces with ship's navigation system for wind-corrected chaff bloom prediction.
Display Configuration Manager 40B57908 Software component that manages operator display layouts, role-based presets, and runtime reconfiguration of tactical console workstations. Stores predefined display configurations per warfare area (AAW, ASUW, ASW, EW) with optimized panel layouts, symbology filters, and alert routing. Supports hot-switching between configurations in under 2 seconds during role handover. Manages multi-console coordination for TAO supervisory overview.
Doctrine and Rules of Engagement Database 40B57B51 Structured data store within the TEWA subsystem that encodes and enforces engagement rules, weapon employment constraints, and command authority levels. Contains weapon-target pairing matrices defining which weapons may engage which threat categories, minimum and maximum engagement ranges per weapon type, no-fire zones defined as geographic polygons, identification friend-or-foe requirements before engagement authorization, escalation thresholds requiring higher command authority, and EMCON-dependent weapon restrictions. Supports real-time doctrine modification by the Tactical Action Officer. All doctrine changes are logged with timestamp and operator identity for post-action review.
Electro-Optical and Infrared Sensor Manager 55F57819 Component of the Naval CMS Sensor Management Subsystem managing shipboard EO/IR sensor systems including TV cameras, forward-looking infrared (FLIR), and laser rangefinders. Controls sensor pointing (slew-to-cue from radar tracks), zoom, focus, and polarity settings. Receives video feeds and overlays track designation symbology. Provides visual identification imagery to operator consoles and automatic contrast target tracking output to the fire control loop. Operates in degraded visibility (smoke, fog) using thermal bands. Critical for rules of engagement compliance requiring positive visual identification before weapons release.
Electronic Attack Controller 51F77A39 Active electronic countermeasures controller within a naval EW subsystem. Manages shipboard jammer transmitters including noise jammers, deception jammers, and Digital RF Memory (DRFM) systems operating across 0.5-18 GHz. Selects jamming techniques (spot noise, barrage, gate pull-off, velocity gate steal, cross-eye) based on threat emitter parameters received from ESM. Generates jamming waveforms matched to target radar characteristics. Manages jammer power budgets and antenna pointing. Must respond to new threat detections within 500ms. Coordinates with EMCON Manager to ensure jamming does not compromise own-ship emissions discipline.
Electronic Support Measures Interface 40A53019 Component of the Naval CMS Sensor Management Subsystem providing the interface between the ESM/ELINT receiver system and the combat management system. Receives intercept reports from wideband digital receivers covering 0.5-40 GHz, including emitter parameters (frequency, pulse width, PRI, scan rate, modulation). Performs emitter identification by matching received parameters against the ship's Emitter Parameter Library (EPL). Correlates ESM bearings with radar and sonar tracks for multi-source track enrichment. Provides threat warning alerts for fire control radar lock-on or missile seeker detection. Operates entirely passively, critical during EMCON Silent conditions when active sensors are secured.
Electronic Warfare Subsystem 51F77219 Coordinates electronic warfare operations within a naval combat management system. Integrates electronic support measures (ESM) for passive detection and classification of hostile radar and communication emitters using interferometric direction-finding and pulse descriptor word matching against a threat library. Controls electronic countermeasures (ECM) including noise jamming, deception jamming (range-gate pull-off, velocity-gate pull-off), and chaff/decoy deployment (SRBOC launchers, Nulka-type active decoys). Manages electronic counter-countermeasures (ECCM) by coordinating friendly radar waveform agility to avoid fratricide with own-ship ECM. Provides electronic order of battle (EOB) compilation and emitter correlation with track database. Operates under EMCON plan coordination with sensor management subsystem to balance detection avoidance against situational awareness needs.
EMCON Manager 40B57A51 Emissions Control (EMCON) management module within a naval EW subsystem. Enforces EMCON policy across all ship radiating systems including radar, communications, IFF, navigation radar, and EW transmitters. Implements EMCON states from full emission (wartime free-to-radiate) through partial emission (selected sensors only) to full EMCON silence. Receives EMCON state commands from the commanding officer via the Tactical Display subsystem and propagates inhibit/enable signals to each radiating subsystem via their respective controllers. Monitors compliance by cross-checking actual emission status against commanded EMCON state. Critical for ship survivability — unauthorized emissions during EMCON silence can reveal ship position to hostile ESM at ranges exceeding 500 nautical miles.
Engagement Scheduler 40B73B01 Temporal scheduling component within the TEWA subsystem that sequences weapon engagements to optimize engagement timeline feasibility. Accounts for missile flyout times, gun burst durations, launcher reload cycles (typically 3-8 seconds for VLS, 15-30 seconds for gun reloading), firing arc restrictions per mount, simultaneous engagement limits per fire control channel (typically 2-4 per illuminator), and minimum/maximum engagement ranges. Produces a time-ordered engagement plan that deconflicts overlapping engagements and ensures continuous defensive coverage. Updates the schedule reactively when kill assessments or new threats alter the engagement picture.
EW Situational Awareness Processor 51F77219 Electronic warfare operational picture processor within a naval EW subsystem. Maintains a real-time electronic order of battle (EOB) by correlating ESM detections with tracks from the Track Management Subsystem, geo-locating emitters using bearing triangulation and time-difference-of-arrival, and fusing EW data from cooperative platforms via tactical data links. Produces the EW tactical picture including threat rings (weapon engagement zones based on identified emitter-weapon pairings), jamming effectiveness assessments, and electromagnetic environment characterization. Updates the EW picture at minimum 2Hz. Provides electronic warfare situational awareness to operators via the Tactical Display subsystem and to automated systems via TEWA.
EW Threat Library 50B77109 Emitter parametric database and identification engine within a naval EW subsystem. Maintains a database of over 10,000 emitter types with parameters including frequency range, pulse repetition interval, pulse width, scan pattern, and antenna characteristics. Receives intercept data from ESM sensors and correlates against stored parameters to identify specific emitter types, platforms, and weapons systems. Provides threat lethality assessments based on emitter-weapon pairing. Supports field-programmable updates from intelligence sources via the Communications subsystem. Supplies identification results to the EW Situational Awareness Processor and TEWA within 200ms of initial intercept.
External Track Interface 40F57958 Tactical data link track exchange module in a naval CMS Track Management Subsystem. Handles incoming and outgoing track data via Link 16 (TADIL-J, MIL-STD-6016), Link 11 (TADIL-A, MIL-STD-6011), and Link 22 (NILE). Performs track correlation between locally-held tracks and tracks received from other units in the task force using geographic gating and identity matching. Manages the composite tracking picture by merging force-level track data with the local picture. Implements track forwarding rules based on reporting responsibility and track custody. Converts between internal track format and TADIL message formats (J-series for Link 16). Handles network participation group management and time-slot allocation for TDMA-based links.
GPS Receiver Interface 54ED7019 Interface to military GPS receiver (AN/WRN-6 or equivalent) providing precise position, velocity, and time (PVT) to the naval CMS. Receives SAASM-encrypted P(Y)-code signals on L1/L2 frequencies providing sub-10m CEP accuracy. Monitors GPS integrity via RAIM and provides GPS-denied fallback indication. Feeds position to track management for ownship reference and to tactical data links for PPLI (Precise Participant Location and Identification) message generation.
Gun Fire Control System 51F73B19 Computes ballistic firing solutions for naval gun systems (76mm/127mm main gun, 20-30mm secondary guns) within a naval CMS Weapon Control Subsystem. Implements exterior ballistic models accounting for projectile drag, Coriolis effect, wind drift, muzzle velocity variation with barrel temperature and wear, and own-ship motion compensation. Provides continuous aim-point corrections to gun servo systems via high-speed serial link at 50Hz update rate. Supports surface engagement (anti-surface warfare), shore bombardment (naval gunfire support), and anti-air barrage modes. Computes burst length, fuze settings (proximity/contact/time), and ammunition selection. Must achieve first-round hit probability of 50% at 12km for anti-surface targets.
IFF Interrogator Controller 51F57A59 Component of the Naval CMS Sensor Management Subsystem managing Identification Friend or Foe operations. Controls Mode 1/2/3A/C/4/5/S interrogation sequences via the ship's IFF antenna. Schedules interrogation dwells synchronized with radar scan, manages crypto key loading for Mode 4/5 secure identification, and processes response decodes. Outputs IFF correlation results (friend, assumed friend, unknown, hostile) tagged with confidence levels to the Track Identity Classifier in the Track Management Subsystem. Must enforce interrogation rate limits to avoid fratricide-risk misidentification and comply with STANAG 4193 for Mode 5 operations.
Inertial Navigation System Interface 50B57018 Interface processor for ship's ring-laser gyro inertial navigation system (e.g., Raytheon AN/WSN-7) in a naval CMS. Receives attitude (roll, pitch, heading), position (lat/lon), velocity, and acceleration data via MIL-STD-1553B at 50 Hz. Performs coordinate transformations from ship-relative to geographic reference frames. Provides ownship kinematic state to track management for sensor stabilisation and to weapon control for fire control solutions. Critical for CMS accuracy — single point of failure for ownship reference.
Kill Assessment Module 41F73309 Post-engagement analysis component within the TEWA subsystem that determines engagement outcome (kill, damage, miss) by correlating pre-engagement track predictions with post-engagement sensor observations. Ingests radar track data, infrared imagery, and ESM emissions changes to detect target destruction indicators: track termination, velocity discontinuities, radar cross-section changes, infrared bloom patterns, and cessation of threat emissions. Provides kill probability confidence estimates (high/medium/low) within 5 seconds of weapon impact. Feeds results back to Threat Evaluation Engine for re-engagement decisions on surviving threats.
Message Distribution Server 50F77318 Internal message routing and distribution server for naval CMS. Routes OTH-Gold, USMTF, and VMF formatted messages between CMS subsystems and external communication circuits. Implements store-and-forward queuing, message precedence handling (Flash, Immediate, Priority, Routine), automatic routing based on JANAP 128 addressing, and message journaling for audit trail. Processes up to 500 messages per minute with guaranteed delivery and duplicate detection.
Missile Engagement Controller 51B57A39 Controls the full engagement lifecycle for shipboard guided missiles within a naval CMS Weapon Control Subsystem. Manages pre-launch checks (missile health, launcher ready, safety interlocks), launch sequencing, midcourse guidance command generation (for semi-active and command-guided missiles), target illumination scheduling for semi-active homing missiles, and handover to terminal seeker. Supports concurrent engagements across multiple missile types including surface-to-air (SM-2/ESSM class), anti-ship (Harpoon class), and land-attack (Tomahawk class). Interfaces with vertical launch system and trainable launchers via weapon data bus. Must handle salvo firing with minimum 2-second intervals between launches from the same launcher.
Multi-Sensor Data Associator 51B73308 Core correlation engine in a naval CMS Track Management Subsystem. Matches incoming sensor detections from radar, sonar, ESM, and IFF against existing system tracks using statistical gating with Mahalanobis distance thresholds. Implements multiple hypothesis tracking (MHT) for ambiguous associations and Munkres assignment algorithm for global nearest-neighbor track-to-detection pairing. Handles track splitting when a single track resolves into multiple targets (e.g., formation breakup), track merging when separate tracks are identified as the same physical target, and ghost track detection in multipath environments. Must process 1000+ concurrent track-detection pairs within a 200ms correlation cycle.
Naval Combat Management System 51FD7959 Integrated shipboard command and control system for surface combatant warships. Fuses sensor data from radar, sonar, electronic warfare, and electro-optical systems to build a comprehensive tactical picture. Provides threat evaluation, weapon assignment, and engagement coordination for anti-air warfare (AAW), anti-surface warfare (ASuW), anti-submarine warfare (ASW), and electronic warfare (EW). Interfaces with ship navigation, propulsion, damage control, and external command networks (Link 16, SATCOM). Operates in high-EMI maritime environments with stringent real-time latency requirements (<100ms sensor-to-display), redundant architecture for battle damage survivability, and NATO STANAG interoperability. Crew complement of 15-30 operators across multiple warfare consoles. Safety-critical weapon release authority chain with multiple interlock layers.
Navigation and Platform Interface Subsystem 41B77810 Interfaces the naval combat management system with own-ship navigation sensors and platform systems on a surface combatant. Ingests GPS position (with selective availability anti-spoofing module, SAASM), inertial navigation system (ring-laser gyro INS) outputs, speed log, compass heading, wind speed/direction, and depth sounder data. Provides dead-reckoning position when GPS is denied or jammed. Interfaces with ship propulsion control for automated maneuvering recommendations (e.g., optimum intercept course, torpedo evasion maneuvers). Receives damage control system status including watertight integrity, fire zones, and casualty power routing to assess CMS equipment availability. Provides own-ship data to all CMS subsystems for coordinate frame reference, weapons envelope calculations, and relative motion computations. Uses NMEA 0183 and MIL-STD-1397 serial interfaces for legacy sensor connections and switched Ethernet for modern digital bus.
Network Management Controller 51B73818 Shipboard tactical network management controller for naval CMS. Manages the combat system LAN (typically dual-redundant Fibre Channel or Gigabit Ethernet) connecting all CMS consoles, processors, and subsystems. Monitors network health, performs bandwidth allocation, manages VLAN segmentation between classification domains (UNCLASS, SECRET, TS/SCI), handles network failover between primary and backup paths, and enforces cross-domain guard policies. Must maintain network availability of 99.99% with automatic switchover in under 50ms.
Operator Action Processor 41BD7B09 Software component that interprets operator inputs (trackball clicks, keyboard commands, touch gestures, function key sequences) and translates them into validated CMS commands. Enforces role-based access control — TAO has weapon release authority, AAWC can assign air engagements, watchstanders can only view and report. Implements command confirmation dialogs for destructive actions (weapon engagement, EMCON changes). Logs all operator actions with timestamps for post-action reconstruction.
Ownship Data Fusion Processor 51F73218 Dedicated processor that fuses ownship navigation data from INS, GPS, speed log, and gyrocompass into a single best-estimate ownship state vector using a federated Kalman filter. Provides authoritative ownship position, velocity, heading, attitude, and time to all CMS subsystems at 20 Hz. Detects and excludes faulty navigation sources. Manages GPS-denied navigation using INS-only with bounded drift correction from speed log. Essential single-source-of-truth for ownship reference frame used by all combat system functions.
Platform Systems Gateway 50A55018 Gateway processor bridging the combat management system to the ship's platform management system (PMS). Receives and distributes ship state data including propulsion status, power generation status, damage control status, stability (draught/trim/heel), and machinery alarms. Provides CMS with situational awareness of platform readiness. Uses serial (RS-422) and Ethernet interfaces to legacy and modern platform systems. Critical for damage control correlation — maps physical damage reports to combat system degradation.
Radar Interface Manager 51B57A08 Component of the Naval CMS Sensor Management Subsystem that provides the interface layer between multiple shipboard radars and the combat system. Manages concurrent operation of S-band volume search radar (AN/SPY-class phased array providing 360° hemispheric coverage at ranges to 200+ NM), X-band target illumination/tracking radar, and navigation radar. Controls radar scheduling (search sectors, track dwells, missile illumination windows), waveform selection, pulse repetition frequency management, and beam steering commands. Receives raw detection reports (range, bearing, elevation, Doppler, SNR) and formats them for the Sensor Data Preprocessor. Must manage radar-to-radar interference and coordinate with EMCON states imposed by the Electronic Warfare Subsystem.
Radio Circuit Manager 51B57878 HF/VHF/UHF radio circuit management processor for naval CMS. Controls allocation and switching of up to 40 radio circuits across multiple transceivers (HF 2-30 MHz, VHF/UHF 225-400 MHz). Manages voice and data circuit assignments, ALE on HF per MIL-STD-188-141B, Have Quick II anti-jam UHF voice. Provides circuit patching, conferencing, and priority preemption for command nets.
Redundancy and Failover Controller 51B77A18 Hardware/software component managing automatic failover between primary and standby combat system servers. Monitors heartbeat signals from all processing nodes at 100 Hz, detects processor or bus failures within 50 ms, and initiates state transfer to backup node. Manages hot-standby replication of application state across dual server pairs. Supports graceful degradation when spare capacity is exhausted by redistributing processing loads across remaining nodes. Implements STANAG 4586 availability requirements for combat system continuity.
SATCOM Interface Controller 51F77018 Satellite communications interface controller for naval CMS, managing UHF SATCOM (FLTSATCOM), SHF SATCOM (WGS), and EHF SATCOM (AEHF) channels. Handles message queuing, priority-based bandwidth allocation, DAMA channel allocation. Provides beyond-line-of-sight connectivity to shore command centres. Must maintain connectivity during ship manoeuvres with automatic antenna handover.
Scenario Generator 41F77B18 Software component that creates and manages tactical training scenarios for the naval CMS embedded training capability. Generates synthetic tracks (air, surface, subsurface) with realistic kinematics, radar cross-sections, and electronic signatures. Supports scripted scenarios with branching logic based on operator responses. Injects synthetic sensor data into the CMS processing pipeline through the Synthetic Environment Interface. Models environmental conditions (sea state, weather, ducting) affecting sensor performance. Stores a library of at least 200 pre-built scenarios covering AAW, ASUW, ASW, and multi-warfare exercises.
Sensor Data Preprocessor 40B53108 Front-end processing module in a naval combat management system's Track Management Subsystem. Receives raw sensor reports from multiple shipboard sensors including 3D air search radar (AN/SPY-type phased array), surface search radar, hull-mounted and towed-array sonar, IFF interrogator (Mk XII/Mode 5), and ESM receivers. Normalizes heterogeneous sensor data into standardized detection reports containing geographic position (WGS-84), bearing, range, Doppler velocity, classification confidence, and sensor quality metadata. Performs coordinate transformations from sensor-relative polar coordinates to ship-relative and geographic reference frames at rates up to 2000 plots per second. Applies sensor-specific bias corrections and clutter rejection filters before passing detections to the correlator.
Sensor Health Monitor 55F77218 Component of the Naval CMS Sensor Management Subsystem providing continuous monitoring of all sensor equipment status. Coordinates Built-In Test (BIT) execution for radar transmitters, sonar arrays, ESM receivers, IFF transponders, and EO/IR systems. Tracks calibration state, detects degradation trends (transmitter power decay, receiver sensitivity loss, array element failures), and generates maintenance alerts. Reports sensor availability status to the Sensor Resource Scheduler so degraded sensors are excluded from tasking or assigned reduced-capability modes. Maintains equipment operating hour logs for planned maintenance scheduling.
Sensor Management Subsystem 51B77A18 Manages and controls all sensor inputs for a surface combatant's combat management system. Interfaces with phased-array and rotating surveillance radars (S-band, X-band), hull-mounted and towed-array sonar, electro-optical/infrared directors, and electronic support measures (ESM) receivers. Provides sensor scheduling to avoid mutual interference, controls radar transmission modes (search, track, illuminate), manages sonar ping sequences, and routes raw sensor data to the track management subsystem. Handles sensor health monitoring, automatic degraded-mode fallback, and sensor fusion preprocessing. Operates under strict EMCON (emission control) policies that can selectively silence active sensors.
Sensor Resource Scheduler 41B73B18 Component of the Naval CMS Sensor Management Subsystem responsible for coordinating sensor resource allocation across all sensor types. Implements priority-based scheduling that balances search coverage (maintaining surveillance picture) against track dwells (maintaining existing tracks with required accuracy). Receives sensor tasking requests from Track Management (track update requests), TEWA (threat confirmation requests), and Weapon Control (fire control illumination requests). Allocates radar time, sonar processing bandwidth, ESM receiver channels, and EO/IR pointing. Enforces EMCON constraints by masking active emitters per current emission control state. Must resolve resource conflicts within 50ms to maintain real-time responsiveness.
Sonar Interface Processor 51F57018 Component of the Naval CMS Sensor Management Subsystem that interfaces with shipboard acoustic sensors. Manages hull-mounted sonar (active/passive modes, frequency-hopping for LPI operation), towed array sonar (passive broadband and narrowband processing, array depth/speed management), and torpedo alert system. Receives digitized acoustic data streams, performs beamforming coordination, and outputs bearing-time records, contact classifications (biological, merchant, submarine, torpedo), and automatic alert triggers. Handles convergence zone and bottom bounce propagation path selection. Interfaces with the ship's own-noise monitoring to blank self-generated interference.
Speed Log Interface 54ED7218 Interface to electromagnetic and Doppler speed log sensors on a naval vessel. Receives speed-through-water from hull-mounted EM log and speed-over-ground from bottom-tracking Doppler log. Provides ownship speed data at 10 Hz to track management for dead reckoning and to weapon control for engagement geometry calculations. Must handle speed ranges from 0-35 knots with resolution of 0.1 knot.
Synthetic Environment Interface 50B57919 Hardware/software gateway that injects synthetic sensor data into the CMS processing pipeline and intercepts weapon engagement commands during training mode. Replaces real sensor feeds with scenario-generated data while maintaining identical message formats and timing characteristics. Implements a hardware-enforced training/live mode switch that prevents synthetic data from reaching weapon systems. Ensures zero leakage between synthetic and live data paths through physical relay isolation on weapon control channels.
System Health and Diagnostics Monitor 45F77308 Software component providing continuous monitoring of all CMS processing infrastructure health. Collects CPU utilization, memory usage, network throughput, temperature, and power supply status from all combat system servers and switches. Detects degradation trends using statistical process control, triggers preventive maintenance alerts before failures. Provides BIT (Built-In Test) coordination across all subsystems. Generates readiness reports showing system availability and weapon system operational status for the Commanding Officer.
Tactical Console Workstation D6FD5018 Multi-screen operator workstation for naval combat management system. Consists of 2-4 high-resolution LCD displays (minimum 2560x1440), ruggedized trackball/keyboard input devices, and dedicated graphics processing unit. Presents the recognized maritime picture including radar video overlay, electronic chart display, track symbology per MIL-STD-2525D, and engagement status panels. Operates in darkened CIC environment with NVG-compatible backlighting. Must support configurable display layouts per operator role (TAO, AAWC, ASUWC, ASWC).
Tactical Data Recorder D4A43219 Hardware/software component that continuously records all CMS data flows for post-mission reconstruction and analysis. Captures track history, operator actions, sensor data, weapon events, communications logs, and alert sequences with nanosecond-precision timestamps synchronized to GPS time. Stores to redundant solid-state recording media with at least 72 hours continuous recording capacity. Supports real-time replay, time-indexed search, and export to NATO NFFI and OTH-Gold formats.
Tactical Decision Aid 40FD7B09 Operator-facing decision support component within the TEWA subsystem that presents recommended courses of action to the Tactical Action Officer and Anti-Air Warfare Coordinator. Visualizes threat approach corridors, weapon engagement envelopes, defended area coverage diagrams, and timeline-to-impact displays. Supports three engagement modes: fully automatic (system engages per doctrine without operator confirmation), semi-automatic (system recommends, operator confirms), and manual (operator selects weapon-threat pairings). Provides what-if analysis capability for doctrine changes and weapon inventory scenarios. Interfaces with the Tactical Display subsystem for rendering.
Tactical Display and Operator Interface Subsystem 50EDF079 Provides the human-machine interface for a naval combat management system. Consists of 15-20 multi-function console workstations arranged across combat information center (CIC) positions: Anti-Air Warfare Coordinator (AAWC), Anti-Surface Warfare Coordinator (ASuWC), Anti-Submarine Warfare Coordinator (ASWC), Electronic Warfare Supervisor (EWS), Tactical Action Officer (TAO), and Force Track Coordinator. Each console features large-format tactical displays (2560x1600 minimum) showing geographic tactical picture overlays, tabular track data, engagement timelines, and sensor coverage diagrams. Supports configurable display symbology per MIL-STD-2525D. Provides context-sensitive soft-key menus for engagement authorization workflow, track management actions, and sensor control. Includes audio alerts, voice intercom integration, and battle-short override controls. Must maintain display update rate >5 Hz under full track load with <200ms input-to-display latency.
Threat Evaluation and Weapon Assignment Subsystem 51B73B19 Automated decision-support subsystem within a naval CMS that evaluates incoming threats and recommends optimal weapon-target pairings. Performs threat evaluation based on target kinematics (range, bearing, course, speed, closest point of approach), platform type, electronic emissions, and declared hostile intent. Ranks threats by composite danger index incorporating time-to-impact, lethality, and defended asset value. Weapon assignment algorithm considers weapon inventory, engagement envelope geometry (min/max range, altitude, bearing sector), probability of kill (Pk), multi-salvo scheduling, and doctrine constraints (preferred weapon for threat type). Supports both automated recommendations requiring operator confirmation and fully automatic engagement modes for close-in threats with <15 second reaction time. Interfaces with weapon control subsystem for engagement execution and with external command authority for rules of engagement updates.
Threat Evaluation Engine 51F73359 Real-time software component within the TEWA subsystem of a naval combat management system. Ingests fused track data from the Track Management Subsystem and intelligence overlays to compute threat priority rankings. Uses kinematics-based time-to-impact estimation, weapon type classification from ESM/IFF data, defended asset criticality weighting, and engagement geometry analysis. Produces an ordered threat priority list updated at 1Hz minimum for up to 200 simultaneous threats. Implements NATO STANAG 4420 threat evaluation algorithms. Must operate deterministically with bounded worst-case execution time under 100ms per evaluation cycle.
Time Distribution Unit 50E57208 Precision timing source that distributes GPS-disciplined time reference to all CMS processing nodes and subsystems. Receives 1PPS and NMEA from GPS Receiver Interface, maintains rubidium atomic clock holdover for GPS-denied operations with drift less than 1 microsecond per day. Distributes time via IEEE 1588 PTP grandmaster and IRIG-B hardware signals. Provides nanosecond-precision timestamps for tactical data recording, sensor data fusion, and engagement timeline correlation.
Torpedo Fire Control Processor 50B53259 Computes torpedo launch solutions for lightweight (Mk 54) and heavyweight (Mk 48) torpedoes, processing target bearing, range, depth, and course from sonar tracks. Calculates weapon presets including enable run, search depth, acquisition cone, and snake/circle search patterns. Interfaces with the torpedo tube launch system via MIL-STD-1553B. Provides real-time target motion analysis for submarine and surface ASW engagements.
Towed Array Sonar Processor 50F53219 Processes passive acoustic data from a variable-depth towed linear hydrophone array (typically 300+ elements), performing narrowband (LOFAR) and broadband (DEMON) analysis for submarine detection and classification. Implements adaptive beamforming with left-right ambiguity resolution using twin-line array or manoeuvring techniques. Provides bearing-time-frequency displays and automatic contact detection. Operates in the 10 Hz to 2 kHz band with convergence zone detection capability out to 100+ nautical miles.
Track Database Manager 40B57318 Real-time track picture repository in a naval CMS Track Management Subsystem. Maintains the authoritative system track file containing all correlated tracks with kinematic state, identity, engagement status, and sensor association history. Handles track numbering (local track numbers and Link 16 reference numbers), track lifecycle management including promotion from tentative to firm track, track aging with configurable coast timers (air: 30s, surface: 120s, subsurface: 300s), and automatic track deletion. Provides concurrent read access to all CMS subscribers (TEWA, display, weapons, comms) via a publish-subscribe interface. Capacity: 1500 simultaneous system tracks with 100ms maximum query latency.
Track Identity Classifier 51F77959 Identity determination engine in a naval CMS Track Management Subsystem. Assigns track identity categories (friendly, assumed friendly, neutral, suspect, hostile, unknown) per STANAG 1241 / MIL-STD-6016 standards. Fuses IFF Mode 4/5 cryptographic responses, ESM radar fingerprint matches against threat library, kinematic behavior analysis (speed/altitude/maneuver profiles vs known platform databases), and intelligence correlation from the recognized maritime/air picture. Implements identity confidence scoring with operator-configurable thresholds for automatic promotion from unknown to suspect/hostile. Outputs feed directly to TEWA threat evaluation and tactical display symbology.
Track Management Subsystem 41B73308 Correlates and fuses sensor reports from radar, sonar, ESM, EO/IR, and data link sources into a unified track database for a naval combat management system. Performs multi-sensor data association using nearest-neighbor and probabilistic data association algorithms. Maintains track state (position, velocity, acceleration) using Kalman filtering with adaptive process noise. Assigns track identity (hostile, friendly, neutral, unknown) based on IFF responses, ESM correlation, and intelligence databases. Manages track-to-track correlation for deconfliction with force-level tracks received via Link 16. Handles up to 1000 simultaneous tracks with update rates of 1-10 Hz depending on threat priority. Implements track promotion, demotion, and drop logic based on measurement consistency and time-since-update.
Track State Estimator 41F73308 Kinematic filtering and prediction engine in a naval CMS Track Management Subsystem. Maintains track state estimates (position, velocity, acceleration, course, speed, altitude/depth) using Interacting Multiple Model (IMM) Kalman filters with constant-velocity, coordinated-turn, and Singer acceleration models. Provides 10-second predicted positions for weapon fire control and 30-second predictions for display extrapolation. Operates across air, surface, and subsurface domains with update rates from 1-4s (radar) to 10-60s (sonar). Target accuracy: <50m RMS position error for air tracks at 100nm range.
Training and Simulation Subsystem 40F57B58 Provides embedded training and simulation capability within the naval combat management system, allowing crew training without live sensor feeds or weapon firing. Generates synthetic tactical scenarios with realistic multi-threat environments including air, surface, and subsurface contacts with configurable behavior models (closing attacks, stand-off missile launch, submarine torpedo attack profiles). Injects simulated sensor data into the track management pipeline indistinguishable from real sensor feeds at the operator console level. Supports partial simulation mode where real sensor data and simulated contacts coexist, enabling training during transit without compromising operational readiness. Provides scenario recording, playback, and after-action review with operator performance metrics. Implements hard-wired safety interlocks that prevent simulated engagements from reaching real weapon control circuits (train/operate switch with physical lockout). Compliant with NATO training interoperability standards for distributed simulation exercises.
Training Mode Controller 40B57B59 Software component that manages transitions between live combat operations and embedded training mode. Enforces the safety-critical separation between training and live weapon systems. Coordinates with all CMS subsystems to switch between live sensor feeds and synthetic data injection. Maintains a clear visual indication on all operator displays showing current mode (LIVE/TRAINING) with distinct color coding that cannot be overridden. Requires Commanding Officer authorization to enter and exit training mode. Logs all mode transitions with operator ID and timestamp.
Weapon Assignment Optimizer 41F73B19 Optimization engine within the TEWA subsystem that allocates available weapons to prioritized threats to maximize defended asset survival probability. Solves a constrained assignment problem considering weapon-target pairing suitability (missile vs gun vs decoy), weapon inventory levels, launcher availability and reload status, engagement timelines, and fire doctrine constraints. Supports shoot-look-shoot and salvo doctrines. Implements both greedy heuristic for real-time response (<500ms) and optimal branch-and-bound solver for planning horizon. Outputs weapon-to-threat assignments with expected probability of kill for each pairing.
Weapon Control Subsystem 51B73B19 Manages weapon system engagement execution for a naval combat management system on a surface combatant. Controls fire-control radars (X-band illuminators for semi-active missiles), missile vertical launch system (VLS) cell selection and launcher sequencing, naval gun fire-control computers (ballistic solution computation for 76mm/127mm guns), close-in weapon system (CIWS) autonomous engagement modes, and torpedo tube firing circuits. Implements weapon safety interlocks including bearing/elevation safety arcs, own-ship keep-out zones, friendly force deconfliction, and multi-layer authorization chain (operator confirm, warfare coordinator approve, CO authorize). Provides engagement timeline management, time-on-target coordination for salvo attacks, and battle damage assessment from post-engagement sensor data. Handles weapon system degradation and automatic reallocation when a weapon channel fails.
Weapon Inventory Manager 40B53B19 Tracks the complete weapon and ammunition inventory for a naval vessel within the CMS Weapon Control Subsystem. Maintains real-time counts for all missile types in vertical launch system cells and trainable launchers, gun ammunition by type (HE, AP, proximity-fuzed, illumination) in magazines, CIWS ammunition drums, chaff and decoy rounds, and torpedo tubes. Monitors weapon readiness states (stowed, loaded, armed, expended, failed) for each individual round/missile. Computes remaining engagement capacity for each threat category and provides sustainability assessments to the Tactical Decision Aid. Interfaces with magazine handling equipment status sensors. Generates automated replenishment requirements. Provides weapon load-out configuration management for pre-deployment planning.
Weapon Safety Interlock Manager 44B57871 Enforces all weapon safety interlocks within the naval CMS Weapon Control Subsystem. Implements a multi-level authorization chain: weapon system power-on requires operator action, weapon arming requires Officer of the Watch authorization, and weapon release requires Commanding Officer or delegated authority authorization via authenticated key/token. Monitors physical safety interlock states (launcher door position, barrel elevation limits, magazine door states) via hardwired discrete signals. Enforces no-fire sectors around own-ship structure, friendly units within exclusion zones, and land masses when rules of engagement prohibit. Provides continuous safety status to the tactical display. Implements fail-safe design: any interlock communication failure defaults to weapon-safe state. Safety-critical SIL 3 function.

Decomposition Relationships

Part-Of

ComponentBelongs To
Sensor Management SubsystemNaval Combat Management System
Track Management SubsystemNaval Combat Management System
Threat Evaluation and Weapon Assignment SubsystemNaval Combat Management System
Weapon Control SubsystemNaval Combat Management System
Electronic Warfare SubsystemNaval Combat Management System
Communications Management SubsystemNaval Combat Management System
Tactical Display and Operator Interface SubsystemNaval Combat Management System
Navigation and Platform Interface SubsystemNaval Combat Management System
Data Processing Infrastructure SubsystemNaval Combat Management System
Training and Simulation SubsystemNaval Combat Management System
Threat Evaluation EngineThreat Evaluation and Weapon Assignment Subsystem
Weapon Assignment OptimizerThreat Evaluation and Weapon Assignment Subsystem
Engagement SchedulerThreat Evaluation and Weapon Assignment Subsystem
Kill Assessment ModuleThreat Evaluation and Weapon Assignment Subsystem
Doctrine and Rules of Engagement DatabaseThreat Evaluation and Weapon Assignment Subsystem
Tactical Decision AidThreat Evaluation and Weapon Assignment Subsystem
Track Database ManagerTrack Management Subsystem
Sensor Data PreprocessorTrack Management Subsystem
Track Identity ClassifierTrack Management Subsystem
Track State EstimatorTrack Management Subsystem
Multi-Sensor Data AssociatorTrack Management Subsystem
External Track InterfaceTrack Management Subsystem
Fire Control ComputerWeapon Control Subsystem
Missile Engagement ControllerWeapon Control Subsystem
Gun Fire Control SystemWeapon Control Subsystem
Close-In Weapon System InterfaceWeapon Control Subsystem
Decoy and Countermeasure ControllerWeapon Control Subsystem
Weapon Safety Interlock ManagerWeapon Control Subsystem
Weapon Inventory ManagerWeapon Control Subsystem
Radar Interface ManagerSensor Management Subsystem
Sonar Interface ProcessorSensor Management Subsystem
Electronic Support Measures InterfaceSensor Management Subsystem
IFF Interrogator ControllerSensor Management Subsystem
Electro-Optical and Infrared Sensor ManagerSensor Management Subsystem
Sensor Resource SchedulerSensor Management Subsystem
Sensor Health MonitorSensor Management Subsystem
Electronic Attack ControllerElectronic Warfare Subsystem
EW Threat LibraryElectronic Warfare Subsystem
EMCON ManagerElectronic Warfare Subsystem
Countermeasure SequencerElectronic Warfare Subsystem
EW Situational Awareness ProcessorElectronic Warfare Subsystem
Tactical Data Link ProcessorCommunications Management Subsystem
SATCOM Interface ControllerCommunications Management Subsystem
Radio Circuit ManagerCommunications Management Subsystem
Message Distribution ServerCommunications Management Subsystem
COMSEC Key Management ModuleCommunications Management Subsystem
Network Management ControllerCommunications Management Subsystem
Inertial Navigation System InterfaceNavigation and Platform Interface Subsystem
GPS Receiver InterfaceNavigation and Platform Interface Subsystem
Speed Log InterfaceNavigation and Platform Interface Subsystem
Platform Systems GatewayNavigation and Platform Interface Subsystem
Ownship Data Fusion ProcessorNavigation and Platform Interface Subsystem
Autopilot and Helm InterfaceNavigation and Platform Interface Subsystem
Tactical Console WorkstationTactical Display and Operator Interface Subsystem
Common Operating Picture GeneratorTactical Display and Operator Interface Subsystem
Alert and Warning ManagerTactical Display and Operator Interface Subsystem
Operator Action ProcessorTactical Display and Operator Interface Subsystem
Tactical Data RecorderTactical Display and Operator Interface Subsystem
Display Configuration ManagerTactical Display and Operator Interface Subsystem
Combat System ServerData Processing Infrastructure Subsystem
Redundancy and Failover ControllerData Processing Infrastructure Subsystem
Combat System LAN SwitchData Processing Infrastructure Subsystem
Time Distribution UnitData Processing Infrastructure Subsystem
System Health and Diagnostics MonitorData Processing Infrastructure Subsystem
Scenario GeneratorTraining and Simulation Subsystem
Synthetic Environment InterfaceTraining and Simulation Subsystem
After-Action Review ProcessorTraining and Simulation Subsystem
Training Mode ControllerTraining and Simulation Subsystem
Torpedo Fire Control ProcessorWeapon Control Subsystem
Towed Array Sonar ProcessorSensor Management Subsystem

Connections

FromTo
Threat Evaluation EngineWeapon Assignment Optimizer
Weapon Assignment OptimizerEngagement Scheduler
Kill Assessment ModuleThreat Evaluation Engine
Doctrine and Rules of Engagement DatabaseWeapon Assignment Optimizer
Doctrine and Rules of Engagement DatabaseThreat Evaluation Engine
Tactical Decision AidWeapon Assignment Optimizer
Engagement SchedulerWeapon Control Subsystem
Threat Evaluation and Weapon Assignment SubsystemTrack Management Subsystem
Threat Evaluation and Weapon Assignment SubsystemWeapon Control Subsystem
Threat Evaluation and Weapon Assignment SubsystemTactical Display and Operator Interface Subsystem
Threat Evaluation and Weapon Assignment SubsystemElectronic Warfare Subsystem
Threat Evaluation and Weapon Assignment SubsystemCommunications Management Subsystem
Track Database ManagerExternal Track Interface
Sensor Data PreprocessorMulti-Sensor Data Associator
Multi-Sensor Data AssociatorTrack State Estimator
Track State EstimatorTrack Identity Classifier
Track Identity ClassifierTrack Database Manager
External Track InterfaceMulti-Sensor Data Associator
Track State EstimatorTrack Database Manager
Track Management SubsystemSensor Management Subsystem
Track Management SubsystemTactical Display and Operator Interface Subsystem
Track Management SubsystemNavigation and Platform Interface Subsystem
Track Management SubsystemCommunications Management Subsystem
Fire Control ComputerMissile Engagement Controller
Fire Control ComputerGun Fire Control System
Fire Control ComputerClose-In Weapon System Interface
Weapon Safety Interlock ManagerFire Control Computer
Weapon Safety Interlock ManagerMissile Engagement Controller
Weapon Safety Interlock ManagerGun Fire Control System
Weapon Safety Interlock ManagerClose-In Weapon System Interface
Weapon Safety Interlock ManagerDecoy and Countermeasure Controller
Weapon Inventory ManagerMissile Engagement Controller
Weapon Inventory ManagerGun Fire Control System
Weapon Inventory ManagerClose-In Weapon System Interface
Weapon Inventory ManagerDecoy and Countermeasure Controller
Decoy and Countermeasure ControllerElectronic Warfare Subsystem
Fire Control ComputerTrack Management Subsystem
Missile Engagement ControllerSensor Management Subsystem
Radar Interface ManagerSensor Resource Scheduler
Sonar Interface ProcessorSensor Resource Scheduler
Electronic Support Measures InterfaceSensor Resource Scheduler
IFF Interrogator ControllerSensor Resource Scheduler
Electro-Optical and Infrared Sensor ManagerSensor Resource Scheduler
Sensor Health MonitorSensor Resource Scheduler
Sensor Health MonitorRadar Interface Manager
Sensor Health MonitorSonar Interface Processor
Radar Interface ManagerSensor Data Preprocessor
Sonar Interface ProcessorSensor Data Preprocessor
Electronic Support Measures InterfaceSensor Data Preprocessor
IFF Interrogator ControllerTrack Identity Classifier
Electro-Optical and Infrared Sensor ManagerFire Control Computer
Sensor Resource SchedulerTrack Management Subsystem
Electronic Support Measures InterfaceElectronic Warfare Subsystem
EW Threat LibraryElectronic Attack Controller
EW Threat LibraryEW Situational Awareness Processor
EW Situational Awareness ProcessorElectronic Attack Controller
Countermeasure SequencerEW Situational Awareness Processor
EMCON ManagerElectronic Attack Controller
Electronic Attack ControllerSensor Management Subsystem
EW Situational Awareness ProcessorTrack Management Subsystem
EW Situational Awareness ProcessorTactical Display and Operator Interface Subsystem
Countermeasure SequencerThreat Evaluation and Weapon Assignment Subsystem
Countermeasure SequencerDecoy and Countermeasure Controller
EMCON ManagerSensor Management Subsystem
EMCON ManagerCommunications Management Subsystem
EW Threat LibraryCommunications Management Subsystem
Tactical Data Link ProcessorMessage Distribution Server
SATCOM Interface ControllerMessage Distribution Server
Radio Circuit ManagerMessage Distribution Server
COMSEC Key Management ModuleTactical Data Link Processor
COMSEC Key Management ModuleSATCOM Interface Controller
COMSEC Key Management ModuleRadio Circuit Manager
Network Management ControllerMessage Distribution Server
Network Management ControllerTactical Data Link Processor
Tactical Data Link ProcessorTrack Management Subsystem
Tactical Data Link ProcessorThreat Evaluation and Weapon Assignment Subsystem
Message Distribution ServerTactical Display and Operator Interface Subsystem
Inertial Navigation System InterfaceOwnship Data Fusion Processor
GPS Receiver InterfaceOwnship Data Fusion Processor
Speed Log InterfaceOwnship Data Fusion Processor
Ownship Data Fusion ProcessorAutopilot and Helm Interface
Platform Systems GatewayOwnship Data Fusion Processor
Ownship Data Fusion ProcessorTrack Management Subsystem
Ownship Data Fusion ProcessorWeapon Control Subsystem
Ownship Data Fusion ProcessorSensor Management Subsystem
Platform Systems GatewayTactical Display and Operator Interface Subsystem
Common Operating Picture GeneratorTactical Console Workstation
Alert and Warning ManagerTactical Console Workstation
Operator Action ProcessorCommon Operating Picture Generator
Operator Action ProcessorAlert and Warning Manager
Display Configuration ManagerTactical Console Workstation
Display Configuration ManagerCommon Operating Picture Generator
Tactical Data RecorderOperator Action Processor
Tactical Data RecorderCommon Operating Picture Generator
Redundancy and Failover ControllerCombat System Server
Combat System LAN SwitchCombat System Server
Time Distribution UnitCombat System LAN Switch
System Health and Diagnostics MonitorCombat System Server
System Health and Diagnostics MonitorCombat System LAN Switch
Time Distribution UnitTactical Data Recorder
Scenario GeneratorSynthetic Environment Interface
Synthetic Environment InterfaceSensor Management Subsystem
Training Mode ControllerSynthetic Environment Interface
Training Mode ControllerWeapon Safety Interlock Manager
After-Action Review ProcessorTactical Data Recorder
Training Mode ControllerTactical Display and Operator Interface Subsystem
Towed Array Sonar ProcessorTrack Management Subsystem
Towed Array Sonar ProcessorTorpedo Fire Control Processor
Torpedo Fire Control ProcessorFire Control Computer
Torpedo Fire Control ProcessorSonar Interface Processor

Produces

ComponentOutput
Threat Evaluation EngineOrdered threat priority list
Weapon Assignment OptimizerWeapon-to-threat assignment plan
Engagement SchedulerTime-ordered engagement schedule
Kill Assessment ModuleEngagement outcome assessment
Tactical Decision AidRecommended courses of action
Track Database ManagerAuthoritative system track picture
Track Identity ClassifierTrack identity classification with confidence
Track State EstimatorFiltered kinematic track state and predictions
Sensor Data PreprocessorStandardized detection reports
External Track InterfaceCorrelated composite track picture
Multi-Sensor Data AssociatorTrack-detection association assignments
Fire Control ComputerFiring solution (target bearing, elevation, range, time-of-flight, launch acceptability)
Missile Engagement ControllerMissile guidance commands and launch sequencing orders
Gun Fire Control SystemGun aim-point corrections at 50Hz with fuze and ammunition selection
Close-In Weapon System InterfaceCIWS target designations and engagement status reports
Decoy and Countermeasure ControllerCountermeasure deployment commands and decoy bloom predictions
Weapon Safety Interlock ManagerWeapon safety status and engagement authorization signals
Weapon Inventory ManagerReal-time weapon inventory state and sustainability assessments
Radar Interface ManagerFormatted radar detection reports (range, bearing, elevation, Doppler, SNR) from all active radar sensors
Sonar Interface ProcessorAcoustic contact reports with bearing, classification, and alert notifications from hull and towed array sonars
Electronic Support Measures InterfaceEmitter identification reports with bearing, threat classification, and radar warning alerts
IFF Interrogator ControllerIFF response decodes with identity classification (friend/foe/unknown) and confidence levels
Electro-Optical and Infrared Sensor ManagerVisual identification imagery and automatic contrast target tracking data for fire control
Sensor Resource SchedulerSensor tasking schedules allocating radar time, sonar bandwidth, ESM channels, and EO/IR pointing
Sensor Health MonitorSensor availability status, degradation alerts, BIT results, and maintenance scheduling data
Electronic Attack ControllerJamming waveforms and technique commands for noise, deception, and DRFM transmitters
EW Threat LibraryEmitter identification reports with platform association and threat lethality assessment
EMCON ManagerEMCON state commands (inhibit/enable signals) to all ship radiating subsystems
Countermeasure SequencerTime-ordered soft-kill countermeasure deployment sequences with launcher commands
EW Situational Awareness ProcessorElectronic order of battle with geo-located emitters, threat rings, and jamming effectiveness assessments
Tactical Data Link ProcessorJ-series track and engagement messages
SATCOM Interface Controllerbeyond-line-of-sight message channels
Radio Circuit Managerallocated voice and data circuits
Message Distribution Serverrouted and prioritized messages
COMSEC Key Management Modulecrypto key material and OTAR distributions
Network Management Controllermanaged network paths and failover events
Inertial Navigation System Interfaceattitude and velocity data at 50 Hz
GPS Receiver InterfacePVT solution with integrity flag
Speed Log Interfacespeed through water and over ground
Platform Systems Gatewayship platform status and alarms
Ownship Data Fusion Processorauthoritative ownship state vector at 20 Hz
Autopilot and Helm Interfacehelm command acknowledgements and rudder feedback
Tactical Console WorkstationRendered tactical displays with operator interaction surfaces
Common Operating Picture GeneratorUnified geospatial display model with track symbology, range rings, and overlays at 30 Hz
Alert and Warning ManagerPrioritized visual, audible, and haptic alerts with acknowledgement tracking
Operator Action ProcessorValidated CMS commands with role-based authorization and action audit log
Tactical Data RecorderContinuous timestamped recording of all CMS data flows for post-mission replay
Display Configuration ManagerActive display layout configurations and role-based presets
Combat System ServerDeterministic real-time computation hosting CMS application partitions
Redundancy and Failover ControllerAutomatic failover commands and hot-standby state synchronization
Combat System LAN SwitchDeterministic low-latency data transport with VLAN classification domain isolation
Time Distribution UnitGPS-disciplined precision time reference via PTP and IRIG-B
System Health and Diagnostics MonitorSystem readiness reports, BIT results, and preventive maintenance alerts
Scenario GeneratorSynthetic tracks and sensor data with realistic kinematics and signatures
Synthetic Environment InterfaceInjected synthetic sensor feeds in live CMS message formats
After-Action Review ProcessorTraining performance metrics, assessment reports, and synchronized exercise replay
Training Mode ControllerTraining/live mode state and safety interlock signals
Torpedo Fire Control Processortorpedo launch solutions with weapon presets and target motion analysis
Towed Array Sonar Processorpassive acoustic bearings and LOFAR/DEMON analysis for submarine detection at convergence zone ranges

Traceability Matrix — Derivation

SourceTargetTypeDescription
SYS-SYSTEM-LEVELREQUIREMENTS-008 IFC-INTERFACEDEFINITIONS-048 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 IFC-INTERFACEDEFINITIONS-052 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 IFC-INTERFACEDEFINITIONS-051 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-050 derives
SYS-SYSTEM-LEVELREQUIREMENTS-007 IFC-INTERFACEDEFINITIONS-043 derives
SYS-SYSTEM-LEVELREQUIREMENTS-008 IFC-INTERFACEDEFINITIONS-049 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 IFC-INTERFACEDEFINITIONS-001 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 IFC-INTERFACEDEFINITIONS-002 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-003 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 IFC-INTERFACEDEFINITIONS-004 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-005 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 IFC-INTERFACEDEFINITIONS-006 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 IFC-INTERFACEDEFINITIONS-008 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 IFC-INTERFACEDEFINITIONS-009 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 IFC-INTERFACEDEFINITIONS-010 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 IFC-INTERFACEDEFINITIONS-007 derives
SYS-SYSTEM-LEVELREQUIREMENTS-012 IFC-INTERFACEDEFINITIONS-011 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 IFC-INTERFACEDEFINITIONS-012 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-013 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-014 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-015 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 IFC-INTERFACEDEFINITIONS-016 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 IFC-INTERFACEDEFINITIONS-017 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-018 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 IFC-INTERFACEDEFINITIONS-019 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-020 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 IFC-INTERFACEDEFINITIONS-021 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 IFC-INTERFACEDEFINITIONS-022 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 IFC-INTERFACEDEFINITIONS-023 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-024 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-025 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-026 derives
SYS-SYSTEM-LEVELREQUIREMENTS-010 IFC-INTERFACEDEFINITIONS-028 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 IFC-INTERFACEDEFINITIONS-027 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-INTERFACEDEFINITIONS-029 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 IFC-INTERFACEDEFINITIONS-030 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 IFC-DEFS-031 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 IFC-DEFS-032 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 IFC-DEFS-034 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 IFC-DEFS-033 derives
SYS-SYSTEM-LEVELREQUIREMENTS-011 IFC-DEFS-035 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 IFC-DEFS-036 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 IFC-DEFS-037 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 IFC-DEFS-038 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 IFC-INTERFACEDEFINITIONS-039 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 IFC-INTERFACEDEFINITIONS-040 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 IFC-INTERFACEDEFINITIONS-041 derives
SYS-SYSTEM-LEVELREQUIREMENTS-010 IFC-INTERFACEDEFINITIONS-042 derives
SYS-SYSTEM-LEVELREQUIREMENTS-006 IFC-INTERFACEDEFINITIONS-044 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 IFC-INTERFACEDEFINITIONS-045 derives
SYS-SYSTEM-LEVELREQUIREMENTS-007 IFC-INTERFACEDEFINITIONS-046 derives
SYS-SYSTEM-LEVELREQUIREMENTS-008 IFC-INTERFACEDEFINITIONS-047 derives
SYS-SYSTEM-LEVELREQUIREMENTS-010 SUB-SUBSYSTEMREQUIREMENTS-045 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 SUB-SUBSYSTEMREQUIREMENTS-111 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 SUB-SUBSYSTEMREQUIREMENTS-110 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 SUB-SUBSYSTEMREQUIREMENTS-109 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-108 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-SUBSYSTEMREQUIREMENTS-106 derives
SYS-SYSTEM-LEVELREQUIREMENTS-012 SUB-SUBSYSTEMREQUIREMENTS-104 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-SUBSYSTEMREQUIREMENTS-107 derives
SYS-SYSTEM-LEVELREQUIREMENTS-012 SUB-SUBSYSTEMREQUIREMENTS-105 derives
SYS-SYSTEM-LEVELREQUIREMENTS-008 SUB-SUBSYSTEMREQUIREMENTS-103 derives
SYS-SYSTEM-LEVELREQUIREMENTS-008 SUB-SUBSYSTEMREQUIREMENTS-099 derives
SYS-SYSTEM-LEVELREQUIREMENTS-006 SUB-SUBSYSTEMREQUIREMENTS-093 derives
SYS-SYSTEM-LEVELREQUIREMENTS-007 SUB-SUBSYSTEMREQUIREMENTS-091 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 SUB-SUBSYSTEMREQUIREMENTS-089 derives
SYS-SYSTEM-LEVELREQUIREMENTS-012 SUB-SUBSYSTEMREQUIREMENTS-088 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-087 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-084 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-083 derives
SYS-SYSTEM-LEVELREQUIREMENTS-008 SUB-SUBSYSTEMREQUIREMENTS-100 derives
SYS-SYSTEM-LEVELREQUIREMENTS-008 SUB-SUBSYSTEMREQUIREMENTS-101 derives
SYS-SYSTEM-LEVELREQUIREMENTS-008 SUB-SUBSYSTEMREQUIREMENTS-102 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-SUBSYSTEMREQUIREMENTS-098 derives
SYS-SYSTEM-LEVELREQUIREMENTS-011 SUB-SUBSYSTEMREQUIREMENTS-095 derives
SYS-SYSTEM-LEVELREQUIREMENTS-007 SUB-SUBSYSTEMREQUIREMENTS-097 derives
SYS-SYSTEM-LEVELREQUIREMENTS-006 SUB-SUBSYSTEMREQUIREMENTS-094 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-090 derives
SYS-SYSTEM-LEVELREQUIREMENTS-007 SUB-SUBSYSTEMREQUIREMENTS-086 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-SUBSYSTEMREQUIREMENTS-092 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 SUB-SUBSYSTEMREQUIREMENTS-085 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 SUB-SUBSYSTEMREQUIREMENTS-082 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-082 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 SUB-REQS-080 derives
SYS-SYSTEM-LEVELREQUIREMENTS-007 SUB-REQS-079 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-REQS-078 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 SUB-REQS-074 derives
SYS-SYSTEM-LEVELREQUIREMENTS-011 SUB-REQS-069 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 SUB-REQS-068 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-REQS-076 derives
SYS-SYSTEM-LEVELREQUIREMENTS-012 SUB-REQS-077 derives
SYS-SYSTEM-LEVELREQUIREMENTS-007 SUB-REQS-081 derives
SYS-SYSTEM-LEVELREQUIREMENTS-006 SUB-REQS-081 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 SUB-REQS-075 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-REQS-071 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-REQS-067 derives
SYS-SYSTEM-LEVELREQUIREMENTS-011 SUB-REQS-072 derives
SYS-SYSTEM-LEVELREQUIREMENTS-010 SUB-REQS-073 derives
SYS-SYSTEM-LEVELREQUIREMENTS-006 SUB-REQS-071 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 SUB-REQS-066 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 SUB-REQS-065 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 SUB-REQS-064 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 SUB-REQS-063 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 SUB-SUBSYSTEMREQUIREMENTS-052 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-051 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-050 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-049 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 SUB-SUBSYSTEMREQUIREMENTS-056 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-059 derives
SYS-SYSTEM-LEVELREQUIREMENTS-010 SUB-SUBSYSTEMREQUIREMENTS-062 derives
SYS-SYSTEM-LEVELREQUIREMENTS-010 SUB-SUBSYSTEMREQUIREMENTS-058 derives
SYS-SYSTEM-LEVELREQUIREMENTS-010 SUB-SUBSYSTEMREQUIREMENTS-057 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-061 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-060 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-055 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-054 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-053 derives
SYS-SYSTEM-LEVELREQUIREMENTS-012 SUB-SUBSYSTEMREQUIREMENTS-048 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-SUBSYSTEMREQUIREMENTS-046 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-043 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-047 derives
SYS-SYSTEM-LEVELREQUIREMENTS-007 SUB-SUBSYSTEMREQUIREMENTS-046 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-001 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-002 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-003 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-004 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 SUB-SUBSYSTEMREQUIREMENTS-005 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-006 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-007 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 SUB-SUBSYSTEMREQUIREMENTS-008 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-SUBSYSTEMREQUIREMENTS-009 derives
SYS-SYSTEM-LEVELREQUIREMENTS-010 SUB-SUBSYSTEMREQUIREMENTS-010 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 SUB-SUBSYSTEMREQUIREMENTS-011 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-016 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 SUB-SUBSYSTEMREQUIREMENTS-012 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-013 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-015 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-012 derives
SYS-SYSTEM-LEVELREQUIREMENTS-004 SUB-SUBSYSTEMREQUIREMENTS-019 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-SUBSYSTEMREQUIREMENTS-021 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 SUB-SUBSYSTEMREQUIREMENTS-017 derives
SYS-SYSTEM-LEVELREQUIREMENTS-014 SUB-SUBSYSTEMREQUIREMENTS-018 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-020 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 SUB-SUBSYSTEMREQUIREMENTS-014 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-022 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-023 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-024 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-025 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-026 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-027 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-028 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-029 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-030 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 SUB-SUBSYSTEMREQUIREMENTS-033 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 SUB-SUBSYSTEMREQUIREMENTS-034 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 SUB-SUBSYSTEMREQUIREMENTS-035 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-031 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-032 derives
SYS-SYSTEM-LEVELREQUIREMENTS-006 SUB-SUBSYSTEMREQUIREMENTS-036 derives
SYS-SYSTEM-LEVELREQUIREMENTS-006 SUB-SUBSYSTEMREQUIREMENTS-037 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-038 derives
SYS-SYSTEM-LEVELREQUIREMENTS-002 SUB-SUBSYSTEMREQUIREMENTS-039 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 SUB-SUBSYSTEMREQUIREMENTS-038 derives
SYS-SYSTEM-LEVELREQUIREMENTS-001 SUB-SUBSYSTEMREQUIREMENTS-040 derives
SYS-SYSTEM-LEVELREQUIREMENTS-003 SUB-SUBSYSTEMREQUIREMENTS-041 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-041 derives
SYS-SYSTEM-LEVELREQUIREMENTS-005 SUB-SUBSYSTEMREQUIREMENTS-044 derives
SYS-SYSTEM-LEVELREQUIREMENTS-009 SUB-SUBSYSTEMREQUIREMENTS-042 derives
STK-STAKEHOLDERNEEDS-005 SYS-SYSTEM-LEVELREQUIREMENTS-016 derives
STK-STAKEHOLDERNEEDS-005 SYS-SYSTEM-LEVELREQUIREMENTS-015 derives
STK-STAKEHOLDERNEEDS-007 SYS-SYSTEM-LEVELREQUIREMENTS-008 derives
STK-STAKEHOLDERNEEDS-005 SYS-SYSTEM-LEVELREQUIREMENTS-014 derives
STK-STAKEHOLDERNEEDS-005 SYS-SYSTEM-LEVELREQUIREMENTS-013 derives
STK-STAKEHOLDERNEEDS-001 SYS-SYSTEM-LEVELREQUIREMENTS-012 derives
STK-STAKEHOLDERNEEDS-005 SYS-SYSTEM-LEVELREQUIREMENTS-011 derives
STK-STAKEHOLDERNEEDS-002 SYS-SYSTEM-LEVELREQUIREMENTS-010 derives
STK-STAKEHOLDERNEEDS-008 SYS-SYSTEM-LEVELREQUIREMENTS-009 derives
STK-STAKEHOLDERNEEDS-008 SYS-SYSTEM-LEVELREQUIREMENTS-008 derives
STK-STAKEHOLDERNEEDS-007 SYS-SYSTEM-LEVELREQUIREMENTS-008 derives
STK-STAKEHOLDERNEEDS-006 SYS-SYSTEM-LEVELREQUIREMENTS-007 derives
STK-STAKEHOLDERNEEDS-005 SYS-SYSTEM-LEVELREQUIREMENTS-006 derives
STK-STAKEHOLDERNEEDS-004 SYS-SYSTEM-LEVELREQUIREMENTS-005 derives
STK-STAKEHOLDERNEEDS-003 SYS-SYSTEM-LEVELREQUIREMENTS-004 derives
STK-STAKEHOLDERNEEDS-002 SYS-SYSTEM-LEVELREQUIREMENTS-003 derives
STK-STAKEHOLDERNEEDS-001 SYS-SYSTEM-LEVELREQUIREMENTS-002 derives
STK-STAKEHOLDERNEEDS-001 SYS-SYSTEM-LEVELREQUIREMENTS-001 derives

Traceability Matrix — Verification

RequirementVerified ByTypeDescription
SYS-SYSTEM-LEVELREQUIREMENTS-011 VER-VERIFICATIONMETHODS-014 verifies
SUB-SUBSYSTEMREQUIREMENTS-092 VER-VERIFICATIONMETHODS-016 verifies
SUB-SUBSYSTEMREQUIREMENTS-109 VER-VERIFICATIONMETHODS-015 verifies
SUB-SUBSYSTEMREQUIREMENTS-057 VER-VERIFICATIONMETHODS-013 verifies
SUB-SUBSYSTEMREQUIREMENTS-107 VER-VERIFICATIONMETHODS-012 verifies
SUB-SUBSYSTEMREQUIREMENTS-096 VER-VERIFICATIONMETHODS-011 verifies
SUB-SUBSYSTEMREQUIREMENTS-102 VER-VERIFICATIONMETHODS-010 verifies
SUB-SUBSYSTEMREQUIREMENTS-094 VER-VERIFICATIONMETHODS-009 verifies
SUB-SUBSYSTEMREQUIREMENTS-082 VER-VERIFICATIONMETHODS-008 verifies
SUB-REQS-071 VER-METHODS-007 verifies
SUB-REQS-070 VER-METHODS-006 verifies
SUB-REQS-063 VER-METHODS-005 verifies
SUB-SUBSYSTEMREQUIREMENTS-022 VER-VERIFICATIONMETHODS-004 verifies
SUB-SUBSYSTEMREQUIREMENTS-034 VER-VERIFICATIONMETHODS-003 verifies
SUB-SUBSYSTEMREQUIREMENTS-030 VER-VERIFICATIONMETHODS-002 verifies
SUB-SUBSYSTEMREQUIREMENTS-033 VER-VERIFICATIONMETHODS-001 verifies

Orphan Requirements (no trace links)

RefDocumentRequirement
IFC-INTERFACEDEFINITIONS-031 interface-requirements The interface between the Tactical Data Link Processor and the Track Management Subsystem SHALL exchange track data usin...
IFC-INTERFACEDEFINITIONS-032 interface-requirements The interface between the Tactical Data Link Processor and the Threat Evaluation and Weapon Assignment Subsystem SHALL t...
IFC-INTERFACEDEFINITIONS-033 interface-requirements The interface between the Message Distribution Server and the Tactical Display and Operator Interface Subsystem SHALL de...
IFC-INTERFACEDEFINITIONS-034 interface-requirements The interface between the COMSEC Key Management Module and the Tactical Data Link Processor SHALL support KGV-11 key loa...
IFC-INTERFACEDEFINITIONS-035 interface-requirements The interface between the Network Management Controller and the Data Processing Infrastructure Subsystem SHALL provide S...
IFC-INTERFACEDEFINITIONS-036 interface-requirements The interface between the Ownship Data Fusion Processor and the Track Management Subsystem SHALL provide ownship positio...
IFC-INTERFACEDEFINITIONS-037 interface-requirements The interface between the Ownship Data Fusion Processor and the Weapon Control Subsystem SHALL provide ownship kinematic...
IFC-INTERFACEDEFINITIONS-038 interface-requirements The interface between the Platform Systems Gateway and the Tactical Display and Operator Interface Subsystem SHALL prese...
SUB-SUBSYSTEMREQUIREMENTS-063 subsystem-requirements The Tactical Data Link Processor SHALL transmit and receive Link-16 J-series messages at the full JTIDS terminal rate of...
SUB-SUBSYSTEMREQUIREMENTS-064 subsystem-requirements The Tactical Data Link Processor SHALL maintain simultaneous participation in up to 3 Link-16 networks and 1 Link-22 mul...
SUB-SUBSYSTEMREQUIREMENTS-065 subsystem-requirements The SATCOM Interface Controller SHALL maintain at least one beyond-line-of-sight communication channel with 99.5% availa...
SUB-SUBSYSTEMREQUIREMENTS-066 subsystem-requirements The Radio Circuit Manager SHALL support simultaneous management of at least 30 radio circuits across HF (2-30 MHz), VHF ...
SUB-SUBSYSTEMREQUIREMENTS-067 subsystem-requirements The Message Distribution Server SHALL route at least 500 formatted messages per minute across all precedence levels (Fla...
SUB-SUBSYSTEMREQUIREMENTS-068 subsystem-requirements When a Flash precedence message is received, the Message Distribution Server SHALL preempt lower-precedence message proc...
SUB-SUBSYSTEMREQUIREMENTS-069 subsystem-requirements The COMSEC Key Management Module SHALL manage at least 200 concurrent Type-1 cryptographic keys across all communication...
SUB-SUBSYSTEMREQUIREMENTS-070 subsystem-requirements When an emergency zeroize command is issued, the COMSEC Key Management Module SHALL destroy all stored key material acro...
SUB-SUBSYSTEMREQUIREMENTS-071 subsystem-requirements The Network Management Controller SHALL maintain combat system LAN availability of at least 99.99% through dual-redundan...
SUB-SUBSYSTEMREQUIREMENTS-072 subsystem-requirements The Network Management Controller SHALL enforce VLAN-based classification domain separation between UNCLASSIFIED, SECRET...
SUB-SUBSYSTEMREQUIREMENTS-073 subsystem-requirements When EMCON condition is set, the Communications Management Subsystem SHALL suppress all RF transmissions on tactical dat...
SUB-SUBSYSTEMREQUIREMENTS-074 subsystem-requirements The Radio Circuit Manager SHALL support automatic link establishment on HF circuits per MIL-STD-188-141B with link setup...
SUB-SUBSYSTEMREQUIREMENTS-075 subsystem-requirements The Ownship Data Fusion Processor SHALL provide a fused ownship state vector (position, velocity, heading, attitude) to ...
SUB-SUBSYSTEMREQUIREMENTS-076 subsystem-requirements When GPS signal is lost, the Ownship Data Fusion Processor SHALL continue providing ownship position using INS-only dead...
SUB-SUBSYSTEMREQUIREMENTS-077 subsystem-requirements The Inertial Navigation System Interface SHALL receive attitude data (roll, pitch, heading) at 50 Hz via MIL-STD-1553B w...
SUB-SUBSYSTEMREQUIREMENTS-078 subsystem-requirements The GPS Receiver Interface SHALL detect loss of GPS integrity via RAIM and report GPS-denied condition to the Ownship Da...
SUB-SUBSYSTEMREQUIREMENTS-079 subsystem-requirements The Platform Systems Gateway SHALL receive and distribute ship platform status including propulsion plant state, electri...
SUB-SUBSYSTEMREQUIREMENTS-080 subsystem-requirements The Autopilot and Helm Interface SHALL enforce safety interlocks preventing CMS-commanded course changes that would resu...
SUB-SUBSYSTEMREQUIREMENTS-081 subsystem-requirements The Ownship Data Fusion Processor SHALL detect and exclude faulty navigation sensor inputs within 2 seconds of fault ons...
SUB-SUBSYSTEMREQUIREMENTS-112 subsystem-requirements The Torpedo Fire Control Processor SHALL compute torpedo launch solutions for lightweight and heavyweight torpedoes with...
VER-VERIFICATIONMETHODS-005 verification-plan The Tactical Data Link Processor message throughput (SUB-REQS-063) SHALL be verified by test using a Link-16 network sim...
VER-VERIFICATIONMETHODS-006 verification-plan The COMSEC emergency zeroization (SUB-REQS-070) SHALL be verified by demonstration using test key material loaded into a...
VER-VERIFICATIONMETHODS-007 verification-plan The network failover time (SUB-REQS-071) SHALL be verified by test, injecting a link failure on the primary combat syste...
VER-VERIFICATIONMETHODS-017 verification-plan The physical distribution requirement (SYS-SYSTEM-LEVELREQUIREMENTS-015) SHALL be verified by inspection of equipment in...