2.37 · Proof of concept · Operate
Airfield Lighting Real Which airfield lights are out, and the repair each one needs.
Picture: Headless capture of poc/index.html?v=lighting&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale. Clip: Excerpt of poc/flybys/outage.mp4, 2.0 to 6.0 seconds. A drawing of the process: A light circuit goes dark, and what follows. No sound.
Screen · Proof of concept · Operate
Which airfield lights are out, and the repair each one needs.
Sources Interchange Twin Screens Plan
Kind Screen
Status partly met
Airport layer Screens: the POC story and the spines
Airport area not linked
System not linked
Sensor type not linked Open the screen · Open the detail
Level 2 of 3 This component, complete on its own. Its files, sources and tests are the detail below. Open the detail
Open this screen in the proof of concept
Capture of the screen: Airfield Lighting. Dark and light modes.
Narration line It shows every lighting circuit and visual aid on the map with its state from the lighting control system.
Source: poc/bearings/lighting.json, beat "What it shows"
Flyby: A light circuit goes dark, and what follows. A drawing of the process, not the product. No sound.
Group Operate
Status as the app labels it Real
Basis The screen runs. Data: carefully crafted and curated test data for common use cases.
What the screen must do (4) Show every lighting circuit and visual aid on the map with its state from the lighting control system (REQ-FUNC-036, REQ-INT-006) List outages with their place, the rule they are measured against and how long they have held (REQ-FUNC-037) Show the maintenance schedule for visual aids and its record (REQ-FUNC-038) Route an outage as a work order and say when it needs a NOTAM (REQ-FUNC-037)
Requirements matrix rows that name this screen (1) Row RFP section Requirement Status M-020 RFP 3, focus area Airfield infrastructure partly met
Previous Condition and NOTAMsNext Wildlife and FOD