System

Naval Combat Management System, fifth subsystem decomposition session. The {{entity:Electronic Warfare Subsystem}} is now fully decomposed into 5 components. Prior sessions covered {{entity:Track Management Subsystem}}, {{entity:Weapon Control Subsystem}}, {{entity:Sensor Management Subsystem}}, and {{entity:Threat Evaluation and Weapon Assignment Subsystem}}. Two subsystems remain undecomposed: {{entity:Communications Management Subsystem}} and {{entity:Tactical Display and Operator Interface Subsystem}}. Project stands at 118 requirements (62 subsystem, 30 interface, 14 system, 8 stakeholder, 4 verification) across 6 documents with 115 trace links.

Decomposition

The {{entity:Electronic Warfare Subsystem}} {{hex:51F77219}} was decomposed into 5 components reflecting the real functional architecture of a naval EW suite:

• {{entity:Electronic Attack Controller}} {{hex:51F77A39}} — manages active jamming transmitters (noise, deception, DRFM) across 0.5–18 GHz. Selects techniques matched to threat emitter parameters. 500ms response time to new threats.
• {{entity:EW Threat Library}} {{hex:50B77109}} — emitter parametric database (10,000+ entries) with real-time identification engine. 200ms correlation time, 95% correct identification rate. Field-programmable via comms subsystem.
• {{entity:EMCON Manager}} {{hex:40B57A51}} — enforces emissions control policy across all ship radiating systems. Implements full/partial/silent states. Fail-safe design: loss of control signal defaults to inhibit.
• {{entity:Countermeasure Sequencer}} {{hex:51F77A19}} — generates soft-kill deployment sequences combining chaff, flares, towed decoys, and active off-board decoys. Selects based on missile seeker type. 2-second initiation from threat declaration. Coordinates with TEWA for layered hard-kill/soft-kill defense.
• {{entity:EW Situational Awareness Processor}} {{hex:51F77219}} — maintains electronic order of battle at 2Hz, geo-locates emitters via bearing triangulation, computes threat engagement rings from emitter-weapon pairings.

flowchart TB
  ESM["ESM Interface"]
  TL["EW Threat Library"]
  EAC["Electronic Attack Controller"]
  EWSA["EW SA Processor"]
  EM["EMCON Manager"]
  CS["Countermeasure Sequencer"]
  TMS["Track Mgmt"]
  TEWA["TEWA"]
  DC["Decoy Controller"]
  TD["Tactical Display"]

  ESM -->|Intercept data| TL
  TL -->|Emitter ID and technique| EAC
  TL -->|Emitter identification| EWSA
  EWSA -->|EW picture and tasking| EAC
  EWSA -->|ESM-track correlation| TMS
  EWSA -->|EW tactical picture| TD
  EM -->|EMCON inhibit/enable| EAC
  CS -->|CM deploy commands| DC
  CS -->|Soft-kill coordination| TEWA
  CS -->|Threat assessment| EWSA

The EMCON Manager’s fail-safe interface design ({{ifc:IFC-INTERFACEDEFINITIONS-028}}) uses positive-sense signals where loss of the control signal defaults to inhibit — a critical survivability pattern that ensures the ship goes silent rather than radiating if the EW subsystem fails.

Analysis

The {{entity:Countermeasure Sequencer}} and {{entity:Electronic Attack Controller}} share a notably similar hex code ({{hex:51F77A19}} vs {{hex:51F77A39}}), differing only in bit 21 ({{trait:Normative}}). The EA Controller has this trait because it actively prescribes jamming actions, while the Sequencer generates recommended sequences. This ontological distinction reflects a real architectural boundary: the Sequencer plans countermeasure deployment but the Weapon Control Subsystem’s {{entity:Decoy and Countermeasure Controller}} executes it.

Lint flagged 2 high-severity findings: the Naval CMS and Electronic Attack Controller lack {{trait:Physical Object}} trait but have physical constraint requirements. This is architecturally correct — the CMS and EA Controller are functional subsystems, not individual physical boxes — but the requirements referencing physical constraints ({{sys:SYS-SYSTEM-LEVELREQUIREMENTS-012}}, {{sub:SUB-SUBSYSTEMREQUIREMENTS-062}}) should specify which LRU or equipment rack embodies these functions. Three medium-severity findings flagged degraded-mode requirements without measurable performance criteria, carried forward from prior sessions.

Requirements

10 subsystem requirements ({{sub:SUB-SUBSYSTEMREQUIREMENTS-053}} through {{sub:SUB-SUBSYSTEMREQUIREMENTS-062}}) and 7 interface requirements ({{ifc:IFC-INTERFACEDEFINITIONS-024}} through {{ifc:IFC-INTERFACEDEFINITIONS-030}}) created. All traced to parent system requirements: EW attack and situational awareness requirements derive from {{sys:SYS-SYSTEM-LEVELREQUIREMENTS-003}} (multi-warfare processing), EMCON requirements from {{sys:SYS-SYSTEM-LEVELREQUIREMENTS-010}} (EMCON suppression), and countermeasure requirements from {{sys:SYS-SYSTEM-LEVELREQUIREMENTS-005}} (close-in threat reaction). Key performance budgets: 500ms jamming initiation, 200ms emitter identification, 2s countermeasure sequence generation, 2Hz EW picture refresh.

Next

Two subsystems remain: {{entity:Communications Management Subsystem}} (tactical data links, SATCOM, internal comms, crypto) and {{entity:Tactical Display and Operator Interface Subsystem}} (operator consoles, tactical picture rendering, alert management). Communications is the higher-priority target — it underpins Link 16, intelligence updates to the EW Threat Library, and inter-platform cooperative EW. Once both are decomposed, the system moves to first-pass-complete for QC review. The lint findings on physical embodiment and degraded-mode criteria should be addressed during QC.