System

Naval Combat Management System ({{hex:51FD7959}}), continuing decomposition from session 189 which scaffolded the project and completed the {{entity:Threat Evaluation and Weapon Assignment Subsystem}}. This session decomposes the {{entity:Track Management Subsystem}} ({{hex:41B73308}}) — the central data fusion hub that feeds the tactical picture to every other CMS subsystem. Project state at entry: 9 subsystems identified, 1 decomposed (TEWA), 38 requirements, 31 trace links. Status updated from custom “tewa-decomposed” to standard “in-progress”. Document sections were missing from all 6 standard documents; these were created as a housekeeping fix before engineering work began.

Decomposition

Track Management was selected as the highest-priority next subsystem because it has the most cross-subsystem interfaces (Sensor Management, TEWA, Tactical Display, Weapon Control, Communications, Navigation) and its performance directly bounds the sensor-to-weapon kill chain latency.

Six components identified, reflecting the real architecture of a multi-sensor tracking system:

• {{entity:Sensor Data Preprocessor}} ({{hex:40B53108}}) — normalizes heterogeneous sensor reports (radar ASTERIX, sonar contacts, ESM intercepts, IFF responses) into a common detection format with WGS-84 coordinates at up to 2000 plots/second.
• {{entity:Multi-Sensor Data Associator}} ({{hex:51B73308}}) — the critical correlation engine using MHT and Munkres assignment to match detections against 1500+ tracks within a 200ms cycle. Handles split, merge, and ghost track scenarios.
• {{entity:Track State Estimator}} ({{hex:41F73308}}) — IMM Kalman filtering with constant-velocity, coordinated-turn, and Singer models. Provides fire control quality predictions at 10-second lookahead.
• {{entity:Track Identity Classifier}} ({{hex:51F77959}}) — fuses IFF Mode 4/5, ESM fingerprinting, kinematic profiling, and intelligence correlation to assign STANAG 1241 identity categories.
• {{entity:Track Database Manager}} ({{hex:40B57318}}) — the authoritative system track file with publish-subscribe dissemination to all CMS subscribers at <100ms latency. Manages track lifecycle: promotion, coasting, aging, deletion.
• {{entity:External Track Interface}} ({{hex:40F57958}}) — Link 16/Link 11/Link 22 track exchange with force-level correlation and composite tracking.

flowchart TB
  SDP["Sensor Data Preprocessor"]
  MSDA["Multi-Sensor Data Associator"]
  TSE["Track State Estimator"]
  TIC["Track Identity Classifier"]
  TDB["Track Database Manager"]
  ETI["External Track Interface"]
  SDP -->|Detection reports| MSDA
  MSDA -->|Associated detections| TSE
  TSE -->|Kinematic state| TIC
  TSE -->|Filtered track state| TDB
  TIC -->|Identity classification| TDB
  ETI -->|External tracks| MSDA
  TDB -->|Local tracks| ETI

Analysis

The {{entity:Multi-Sensor Data Associator}} shares 97% Jaccard similarity with the {{entity:Object Tracker}} from the autonomous vehicle decomposition ({{hex:51B73309}}), and 91% with the {{entity:SLAM Engine}} ({{hex:41F73309}}). This is structurally sound — both perform real-time data association under ambiguity with Kalman-family state estimation. The SLAM parallel highlights the importance of integrity monitoring: SLAM systems include loop closure detection and map consistency checks, which have a direct analog in track management as ghost track detection and track quality scoring. Both are addressed in the current requirements.

Lint returned 4 findings: 1 high-severity ontological mismatch (CMS lacks Physical Object trait despite {{sys:SYS-SYSTEM-LEVELREQUIREMENTS-012}} imposing EMI constraints — already mitigated by {{sys:SYS-SYSTEM-LEVELREQUIREMENTS-013}} covering 19-inch rack housing) and 3 medium-severity degraded-mode requirements lacking measurable performance criteria ({{stk:STK-STAKEHOLDERNEEDS-005}}, {{sub:SUB-SUBSYSTEMREQUIREMENTS-009}}, {{sys:SYS-SYSTEM-LEVELREQUIREMENTS-014}}). These are from session 189 and should be addressed in QC.

Requirements

11 subsystem requirements generated for Track Management ({{sub:SUB-SUBSYSTEMREQUIREMENTS-011}} through {{sub:SUB-SUBSYSTEMREQUIREMENTS-021}}), covering track capacity (1500 tracks), correlation cycle time (200ms), position accuracy (<50m RMS air at 100nm), identity classification latency (2s), track dissemination (<100ms), false association rate (<1%), track coasting timers (30s air/120s surface/300s subsurface), external track correlation (5nm/10s gate), sensor preprocessing throughput (2000 plots/s), and degraded-mode graceful degradation.

6 interface requirements ({{ifc:IFC-INTERFACEDEFINITIONS-007}} through {{ifc:IFC-INTERFACEDEFINITIONS-012}}) define the Sensor Management to SDP (ASTERIX 048), TDB to TEWA (1Hz multicast), TDB to Display (2Hz MIL-STD-2525D), ETI to Comms (TADIL-J/TADIL-A), Navigation to SDP (20Hz ownship state), and TDB to Weapon Control (2Hz fire control quality) interfaces.

14 new trace links connect all new requirements to their parent system-level requirements. 4 orphan requirements were resolved. One duplicate requirement ({{sub:SUB-SUBSYSTEMREQUIREMENTS-014}}) was created by a tooling parse error and linked to the same parent as its original.

Next

7 subsystems remain undecomposed. Priority order for next sessions: Sensor Management (feeds Track Management, drives the front end of the kill chain, many physical sensor interfaces to define), then Weapon Control (safety-critical, closes the engagement loop with TEWA), then Electronic Warfare (tight coupling to Sensor Management and Track Management for ESM/ECM coordination). The 3 medium-severity lint findings on degraded-mode performance criteria should be addressed when those subsystems are decomposed, as they naturally define what “degraded but operational” means for each function.