AirfieldpathOrlando Sanford International

2.11 · Proof of concept · Terminal

HVAC and Building Management Real

Whether the terminal's heating, cooling and air are healthy, read from the building management system.

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

Screen · Proof of concept · Terminal

HVAC and Building Management

Whether the terminal's heating, cooling and air are healthy, read from the building management system.

  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

HVAC and Building Management, a capture of the screen
Capture of the screen: HVAC and Building Management. Dark and light modes.

Narration line

It shows equipment status, health, alarms, faults, environment, energy and runtime from Schneider EcoStruxure.

Source: poc/bearings/hvac.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 status, health, alarms, faults, environment, energy and runtime from Schneider EcoStruxure (REQ-SFB-017)
  • Keep the building management system as the control system; the twin only reads (REQ-SFB-017, REQ-SFB-008)
  • Show a trend that leaves its band as a proposed work request (REQ-SFB-037)
Requirements matrix rows that name this screen (6)
RowRFP sectionRequirementStatus
M-019RFP 3, focus areaHVAC systemspartly met
M-065B iiiAddress the terminal and airfield focus areaspartly met
M-090C 2.4Integrate systems; do not replace monitoring, control or management systemspartly 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-132C 6.3BAS/BMS and HVAC information (status, health, alarms, environment, energy, runtime, availability, indicators, faults)partly met
Requirement identifiers (3)

REQ-SFB-008, REQ-SFB-017, REQ-SFB-037