AirfieldpathOrlando Sanford International

2.58 · Proof of concept · Set up

Rules and Data Library Real

Every body of rules and data the platform has loaded, and what each one drives.

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

Screen · Proof of concept · Set up

Rules and Data Library

Every body of rules and data the platform has loaded, and what each one drives.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
partly met, target
Airport layer
Screens: the POC story and the spines
Airport area
not linked
System
not linked
Sensor type
not linked
SheetA-10
How it worksHow it works: Data

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

Rules and Data Library, a capture of the screen
Capture of the screen: Rules and Data Library. Dark and light modes.

Narration line

It shows the layers (federal, state, county and city, standards, the Authority's systems, drone stations) with their packs.

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

Group
Set up
Status as the app labels it
Real
Basis
The screen runs. The bodies of rules are loaded from docs/domain-registry.json.
What the screen must do (3)
  • Show the layers (federal, state, county and city, standards, the Authority's systems, drone stations) with their packs (REQ-SFB-065)
  • Show each pack's true state: loaded with its counted records, listed, or awaiting (REQ-SFB-065)
  • Trace a rule to the screens and records it drives (REQ-SFB-065)
Requirements matrix rows that name this screen (7)
RowRFP sectionRequirementStatus
M-005RFP 1.2A foundation for a long-term capability that evolvespartly met
M-007RFP 3, objective 1A scalable platform for operations, maintenance and asset managementtarget
M-021RFP 3, focus areaOther assets identified during implementationtarget
M-093C 2.7Commercially supported, configured with standard tools, vendor-agnosticpartly met
M-120B ii; C 2.7Rules and data loaded as versioned packs, each in its true state, each rule traced to its screens; a duty registerpartly met
M-129C 5.10Expansion to more systems, facilities, terminals, assets, dashboards, workflows, analytics, use cases, emerging technologiestarget
M-138C 6.9Representative systems: Genetec, Acuity SensorSwitch, Allen-Bradley BHS and PBB, Simplify i3, PMX, Schneider EcoStruxure, Skidata, Business Central, generator monitoringpartly met
Requirement identifiers (1)

REQ-SFB-065