AirfieldpathOrlando Sanford International

2.12 · Proof of concept · Terminal

Point Registry Real

Every reading the twin uses, where it comes from, and who owns it.

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

Screen · Proof of concept · Terminal

Point Registry

Every reading the twin uses, where it comes from, and who owns it.

  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

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

Point Registry, a capture of the screen
Capture of the screen: Point Registry. Dark and light modes.

Narration line

It lists each system with its interface, the points it gives, their tags, their state and the owner of the record.

Source: poc/bearings/points.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 (4)
  • List each system with its interface, the points it gives, their tags, their state and the owner of the record (REQ-SFB-041)
  • Register, probe, license and approve each point before it counts (REQ-SFB-041, REQ-SFB-011)
  • Build no sensor for equipment that already reports; read what it reports (REQ-SFB-040)
  • Draw on one semantic model for points and assets (Brick or Haystack, IFC and COBie, ISO 55000) (REQ-SFB-041)
Requirements matrix rows that name this screen (13)
RowRFP sectionRequirementStatus
M-002RFP 1.1A common operational environment integrating information from selected airport systemspartly met
M-006RFP 2.19System of Record defined as the authoritative source in its domainpartly met
M-010RFP 3, objective 4Integrate selected enterprise and operational systemstarget
M-013RFP 3, objective 7Open, standards-based, interoperable, evolving without proprietary customizationpartly met
M-021RFP 3, focus areaOther assets identified during implementationtarget
M-024RFP 3, data integrationIntegrate CMMS/EAM, BAS/BMS, HVAC, PBB, BHS, vertical transportation and otherstarget
M-060B iiIntegration and data approach: APIs, middleware, web services, event-driven methods, data readiness, dependencies, interoperabilitypartly met
M-098C 3.5Existing systems remain systems of recordpartly met
M-099C 3.6Open integration by standard interfaces, APIs, middleware, web services, event-driven methodspartly met
M-107C 4.6Practical integration reusing existing interfaces; incremental additiontarget
M-108C 4.7Interfaces with CMMS/EAM, BAS/BMS, HVAC, PBB, BHS, vertical transportation, VMS with analyticstarget
M-130C 6.1Evaluate each interface and recommend the approach; systems remain the recordtarget
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 (3)

REQ-SFB-011, REQ-SFB-040, REQ-SFB-041