AirfieldpathOrlando Sanford International

2.2 · Proof of concept · Command

Local Controllers Real

Each functional area's own controller, built from the screens it already owns.

Picture: Headless capture of poc/index.html?v=controllers&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.

Screen · Proof of concept · Command

Local Controllers

Each functional area's own controller, built from the screens it already owns.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
not linked
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

Narration line

It shows the area's gauges and the live state of each screen the area owns.

Source: poc/bearings/controllers.json, beat "What it shows"

Group
Command
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 (3)
  • Give each functional area (operations, engineering and maintenance, facilities, police and security, IT, finance and grants, executive) its own controller (REQ-SFB-027)
  • Reuse each owned screen's live state as the controller's content, so nothing is written twice (REQ-SFB-029)
  • Keep the Command Center's look and status colours (REQ-SFB-028)
Requirement identifiers (3)

REQ-SFB-027, REQ-SFB-028, REQ-SFB-029