AirfieldpathOrlando Sanford International

2.53 · Proof of concept · Prove

Accountability and Records Real

The records the airport must keep, and the ones it must protect.

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

Screen · Proof of concept · Prove

Accountability and Records

The records the airport must keep, and the ones it must protect.

  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

Accountability and Records, a capture of the screen
Capture of the screen: Accountability and Records. Dark and light modes.

Narration line

It shows each record the rules require, its retention period and how the twin keeps it.

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

Group
Prove
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 (5)
  • Show each record the rules require, its retention period and how the twin keeps it (REQ-FUNC-109)
  • Mark sensitive security information and exempt records and keep them out of every public view (REQ-FUNC-110, REQ-SEC-003, REQ-SEC-004)
  • Answer a public records request with what can be released and what is exempt, with the reason (REQ-FUNC-111)
  • Show the accessibility standard and its date for the Authority (REQ-COMP-005)
  • Show the prohibited equipment check for every device joined to the twin (REQ-COMP-001)