SC-02: Multi-Alert Triage
| Field | Value |
|---|---|
| Scenario ID | PER-006-SC-02 |
| Context / Trigger | At 10:15 AM during a high-traffic period (14 active flights across all sectors), Rafael’s sector receives three alerts within 8 seconds: (1) a lateral geofence breach 90 meters outside authorized boundary, 0.4nm from a military restricted zone; (2) an altitude deviation 40 feet above authorized ceiling, self-correcting; (3) a C2 link degradation warning for a flight 3nm from any restricted area. |
Narrative
Three alerts fire in rapid succession. The system presents them in the event feed, color-coded by severity [UERQ-SYS-1840]: Alert 1 (geofence breach near military zone) is Critical — red background, distinct audible tone, screen flash. Alert 2 (altitude deviation, self-correcting) is Warning — amber background, standard tone. Alert 3 (C2 link degradation, no proximity risk) is Informational — blue background, no audible.
Rafael processes them in severity order.
Alert 1: he clicks the Critical alert. The COP zooms to the affected track, showing the aircraft’s position, authorized volume boundary, military restricted zone, deviation vector, and trend indicator. The deviation is sustained and increasing. He opens the structured escalation form: the system pre-populates track ID, position, deviation magnitude (90m lateral, increasing at 1.5m/s), proximity to restricted area (0.4nm and closing), trust score (0.91), and data source (ADS-B + MLAT corroborated). Rafael adds his assessment: “Sustained lateral breach, trajectory toward MIL-RESTRICT-07, not self-correcting. Recommend rescind.” He submits the escalation to Jessica.
Jessica receives the escalation at her station with full context. She reviews Rafael’s assessment, concurs, and issues the rescind. Total time from Rafael’s first alert to Jessica’s rescind: 42 seconds.
Alert 2: Rafael returns to the altitude deviation — it has already self-corrected (the aircraft is now back within its authorized ceiling). He classifies it as “Warning — resolved, no escalation required” and logs the event.
Alert 3: the C2 link degradation is in an area with no nearby restricted zones. He monitors for 2 minutes; the link stabilizes. He classifies as “Informational — transient, no escalation.”
All three events are logged in the shift record.
Traceability
| Linked End Goals | Triage Critical alerts within 15 seconds. Have a structured assessment ready for Jessica within 30 seconds. |
| Linked Capabilities | Event Severity Levels (UERQ-SYS-1840), Incident Notification Latency (UERQ-SYS-1841), Operational Event Types (UERQ-SYS-1838), Event Notification Content (UERQ-SYS-1839), Trust Scoring (UERQ-SYS-1638), Fused Track Output (UERQ-SYS-1813), Incident Monitor Audit Trail (UERQ-SYS-1844). |
| Safety Relevance | Critical: Rafael’s correct prioritization of Alert 1 over Alerts 2 and 3 enabled Jessica’s 42-second rescind response. If Rafael had processed them in arrival order instead of severity order, the geofence breach response would have been delayed by the time spent assessing the self-correcting altitude deviation. |