SC-01: Pre-Event Setup
| Field | Value |
|---|---|
| Scenario ID | PER-002-SC-01 |
| Context / Trigger | Jason’s unit has been assigned to provide airspace awareness for a major outdoor concert at a municipal stadium. 40,000 attendees expected. The event security plan designates a 2-nautical-mile radius around the stadium as the airspace awareness zone. Jason is at the field office 90 minutes before the event, configuring his tablet for the shift. |
Narrative
Jason logs into the ATOMx mobile field application on his ruggedized tablet. He opens the area-of-interest configuration and defines his awareness zone: a circle centered on the stadium with a 2nm radius, surface to 400ft AGL [UERQ-SYS-1837]. He configures his event subscription filters [UERQ-SYS-1843]: all Critical and Warning severity events within his area, all event types, no altitude band filter (he wants full coverage of the “last 400 feet”).
He verifies the data feed status: the system shows a green connectivity indicator and confirms the Traffic Service track subscription is active for his area [UERQ-SYS-1814]. The COP loads on his tablet: a map centered on the stadium with his area of interest boundary drawn. Currently, 3 tracks are visible within the area: 2 are conforming authorized operations (a news helicopter and a pre-approved aerial photography drone), and 1 is an active track tagged as conforming at the boundary. All three show green conformance indicators and trust scores above 0.8.
Jason confirms with the TOC (Jessica Cooper’s shift) via radio that the COP picture matches their view. He downloads the satellite imagery and pre-caches the area’s track data for offline resilience, knowing that 40,000 people with phones will likely degrade cellular connectivity during the event. He briefs his field partner on the three known tracks and they deploy to their observation post at the stadium perimeter.
Traceability
| Linked End Goals | Know immediately when data feed is degraded or disconnected. Distinguish “no activity” from “no data.” |
| Linked Capabilities | Incident Monitor Area of Interest (UERQ-SYS-1837), Event Subscription Filtering (UERQ-SYS-1843), Track Subscription Interface (UERQ-SYS-1814), In-Band Status Flags (UERQ-SYS-1664), In-Field Device Data Feed (UERQ-SYS-1730), Fused Track Output Schema (UERQ-SYS-1813). |
| Safety Relevance | Yes: the pre-event configuration determines what Jason will and will not be alerted to during the event. A misconfigured area of interest (too small, wrong altitude band) could leave blind spots. Verifying the COP against the TOC’s view ensures the field picture is consistent with the command picture. |