AirfieldpathOrlando Sanford International

2.10 · Proof of concept · Terminal

Baggage Handling Real

Whether bags are moving, and where a jam or fault needs a person.

Picture: Headless capture of poc/index.html?v=bhs&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Clip: Capture of poc/index.html?v=bhs&m=light, 4 seconds of the screen as it runs, 10 frames a second. No sound.

Screen · Proof of concept · Terminal

Baggage Handling

Whether bags are moving, and where a jam or fault needs a person.

  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

Baggage Handling, a capture of the screen
Capture of the screen: Baggage Handling. Dark and light modes.

Narration line

It shows equipment and conveyor status, alarms and faults.

Source: poc/bearings/bhs.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 (3)
  • Show equipment and conveyor status, alarms and faults (REQ-SFB-019)
  • Show maintenance, performance, events, condition and trends (REQ-SFB-019)
  • Show the path to the Allen-Bradley baggage controls, listed Not Connected (REQ-SFB-019, REQ-SFB-023)
Requirements matrix rows that name this screen (5)
RowRFP sectionRequirementStatus
M-018RFP 3, focus areaBaggage handling systemspartly met
M-065B iiiAddress the terminal and airfield focus areaspartly met
M-109C 4.7Recommend information exchanges per systempartly met
M-123C 5.5Systems integration with status, state, alarms, faults, availability, performance, events, indicators, energypartly met
M-134C 6.5Baggage information (status, conveyor status, alarms, faults, maintenance, performance, events, condition, trends)partly met
Requirement identifiers (2)

REQ-SFB-019, REQ-SFB-023