System

Naval Combat Management System, session 194. Seven of ten subsystems now have component-level decomposition. This session tackled the two highest-priority remaining subsystems: {{entity:Communications Management Subsystem}} — the most interface-dense subsystem with connections to Track Management, TEWA, and EW — and {{entity:Navigation and Platform Interface Subsystem}}, which provides the ownship reference frame consumed by every sensor and weapon path. Project stands at 148 requirements, 146 trace links, 12 diagrams across 7 decomposed subsystems. Three subsystems remain: Tactical Display and Operator Interface, Data Processing Infrastructure, and Training and Simulation.

Decomposition

Communications Management Subsystem was decomposed into six components reflecting the real architecture of a modern naval comms suite. {{entity:Tactical Data Link Processor}} ({{hex:50F57258}}) handles Link-16/Link-22 J-series message processing with anti-jam frequency hopping. {{entity:SATCOM Interface Controller}} ({{hex:51F77018}}) manages UHF/SHF/EHF SATCOM bearers with DAMA allocation and automatic antenna handover. {{entity:Radio Circuit Manager}} ({{hex:51B57878}}) controls 30+ HF/VHF/UHF circuits with ALE per MIL-STD-188-141B. {{entity:Message Distribution Server}} ({{hex:50F77318}}) routes OTH-Gold and USMTF messages at 500/min with precedence preemption. {{entity:COMSEC Key Management Module}} ({{hex:D0B57859}}) manages Type-1 crypto keys with OTAR and emergency zeroization. {{entity:Network Management Controller}} ({{hex:51B73818}}) maintains dual-redundant combat system LAN with 50 ms failover and cross-domain guard enforcement.

flowchart TB
  TDL["Tactical Data Link Processor"]
  SAT["SATCOM Interface Controller"]
  RAD["Radio Circuit Manager"]
  MDS["Message Distribution Server"]
  CKM["COMSEC Key Management Module"]
  NMC["Network Management Controller"]
  CKM -->|Crypto keys| TDL
  CKM -->|Crypto keys| SAT
  CKM -->|Crypto keys| RAD
  TDL -->|J-series messages| MDS
  SAT -->|BLOS traffic| MDS
  RAD -->|Voice/data circuits| MDS
  NMC -->|Network transport| MDS

Navigation and Platform Interface Subsystem was decomposed into six components centred on an {{entity:Ownship Data Fusion Processor}} ({{hex:51F73218}}) that fuses INS, GPS, and speed log through a federated Kalman filter. {{entity:Inertial Navigation System Interface}} ({{hex:50B57018}}) receives 50 Hz attitude data via MIL-STD-1553B. {{entity:GPS Receiver Interface}} ({{hex:54ED7019}}) provides SAASM-encrypted P(Y)-code PVT with RAIM integrity. {{entity:Speed Log Interface}} ({{hex:54ED7218}}) delivers EM and Doppler speed measurements. {{entity:Platform Systems Gateway}} ({{hex:50A55018}}) bridges CMS to the ship’s platform management system for propulsion, power, and damage control status. {{entity:Autopilot and Helm Interface}} ({{hex:51BD7819}}) enables CMS-directed course changes with rudder safety interlocks.

flowchart TB
  INS["INS Interface"]
  GPS["GPS Receiver Interface"]
  SPD["Speed Log Interface"]
  PLT["Platform Systems Gateway"]
  ODF["Ownship Data Fusion Processor"]
  AHI["Autopilot and Helm Interface"]
  INS -->|Attitude and velocity| ODF
  GPS -->|PVT solution| ODF
  SPD -->|Speed data| ODF
  PLT -->|Platform status| ODF
  ODF -->|Helm commands| AHI

Analysis

Lint returned 5 findings: 2 high-severity ontological mismatches where requirements impose physical constraints on entities classified without the Physical Object trait ({{sys:SYS-SYSTEM-LEVELREQUIREMENTS-012}} on the CMS itself, and {{sub:SUB-SUBSYSTEMREQUIREMENTS-062}} on the EA controller), plus 3 medium-severity degraded-mode requirements lacking measurable performance criteria. The ontological mismatches are real — the CMS and EA controller are software-dominated but live in physical enclosures subject to shock, vibration, and EMI. The degraded-mode gaps need quantified thresholds in a future QC pass.

Cross-domain analysis found {{entity:Ownship Data Fusion Processor}} shares 97% trait similarity with the {{entity:Attitude and Orbit Control Subsystem}} from the Earth observation satellite project. The satellite AOCS domain has mature fault detection and exclusion (FDE) algorithms and sensor voting schemes — a pattern we captured in {{sub:SUB-REQS-081}} requiring 2-second fault exclusion with consistency cross-checks.

The {{entity:Radio Circuit Manager}} and {{entity:Network Management Controller}} show 77% Jaccard similarity, reflecting their shared nature as communication resource schedulers despite operating at different OSI layers.

Requirements

Created 19 subsystem requirements ({{sub:SUB-REQS-063}} through {{sub:SUB-REQS-081}}) and 8 interface requirements ({{ifc:IFC-DEFS-031}} through {{ifc:IFC-DEFS-038}}). Key requirements include TDL message throughput at 238 kbps with 50 ms latency ({{sub:SUB-REQS-063}}), COMSEC emergency zeroization within 10 seconds ({{sub:SUB-REQS-070}}), network failover within 50 ms at 99.99% availability ({{sub:SUB-REQS-071}}), ownship fusion at 20 Hz with 15 m CEP ({{sub:SUB-REQS-075}}), and GPS-denied drift bounded to 1 NM/hour ({{sub:SUB-REQS-076}}). All 7 orphaned requirements were linked to parent system requirements. Three verification entries added for TDL throughput, COMSEC zeroization, and network failover ({{sub:VER-METHODS-005}} through {{sub:VER-METHODS-007}}).

Next

Three subsystems remain: Tactical Display and Operator Interface (the HMI layer — multi-console architecture, tactical picture rendering, alarm management), Data Processing Infrastructure (compute backbone — redundant processors, middleware, data recording), and Training and Simulation (synthetic environment, inject/extract, live-virtual bridging). Tactical Display should be next — it has the second-highest interface count after Communications Management and directly affects operator effectiveness. The 3 degraded-mode lint findings and 2 ontological mismatches should be addressed during QC review after first-pass completion.