AirfieldpathOrlando Sanford International

2.5 · Proof of concept · Terminal

Terminal Assets Now Real

What is working in the terminal right now, and what needs a person, in plain words.

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

Screen · Proof of concept · Terminal

Terminal Assets Now

What is working in the terminal right now, and what needs a person, in plain words.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. 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

Terminal Assets Now, a capture of the screen
Capture of the screen: Terminal Assets Now. Dark and light modes.

Narration line

It shows the four terminal focus areas (vertical transportation, boarding bridges, baggage handling, HVAC) with availability, alarms and open work in one view.

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

Group
Terminal
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 the four terminal focus areas (vertical transportation, boarding bridges, baggage handling, HVAC) with availability, alarms and open work in one view (REQ-SFB-024, REQ-SFB-034)
  • Say the state in one plain sentence a Board member can read (REQ-SFB-024)
  • Place each asset on the terminal plan, illustrative until the Authority's floor plans arrive (REQ-SFB-016)
  • Name each asset's source system and its connectivity as Attachment C 6.9 lists it (REQ-SFB-011, REQ-SFB-021)
  • Show the measures Attachment C 2.3 names: availability and response (REQ-SFB-058)
Requirements matrix rows that name this screen (9)
RowRFP sectionRequirementStatus
M-002RFP 1.1A common operational environment integrating information from selected airport systemspartly met
M-008RFP 3, objective 2Visibility into assets, condition, status, maintenance and lifecyclepartly met
M-027RFP 3, use casesUse cases for asset performance, maintenance optimization, status visibility, decision supportpartly met
M-065B iiiAddress the terminal and airfield focus areaspartly met
M-082C 1.1Terminal and airfield asset management integrating existing systems into one environmentpartly met
M-086C 1.3Five initial asset classes; sequence refined at initiationpartly met
M-110C 4.8Dashboards and UI for each group, with maps, plans, status, alarms, work, trends, KPIspartly met
M-112C 4.10Initial use cases (fifteen listed)partly met
M-124C 5.6Dashboards with maps, plans, locations, indicators, colour-coded conditions, charts, trends, KPIs, alarms, maintenance and work summariespartly met
Requirement identifiers (6)

REQ-SFB-011, REQ-SFB-016, REQ-SFB-021, REQ-SFB-024, REQ-SFB-034, REQ-SFB-058