| 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 |