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
Every reading the twin uses, where it comes from, and who owns it.
- Sources
- Interchange
- Twin
- Screens
- 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
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)
| Row | RFP section | Requirement | Status |
|---|
| M-002 | RFP 1.1 | A common operational environment integrating information from selected airport systems | partly met |
| M-006 | RFP 2.19 | System of Record defined as the authoritative source in its domain | partly met |
| M-010 | RFP 3, objective 4 | Integrate selected enterprise and operational systems | target |
| M-013 | RFP 3, objective 7 | Open, standards-based, interoperable, evolving without proprietary customization | partly met |
| M-021 | RFP 3, focus area | Other assets identified during implementation | target |
| M-024 | RFP 3, data integration | Integrate CMMS/EAM, BAS/BMS, HVAC, PBB, BHS, vertical transportation and others | target |
| M-060 | B ii | Integration and data approach: APIs, middleware, web services, event-driven methods, data readiness, dependencies, interoperability | partly met |
| M-098 | C 3.5 | Existing systems remain systems of record | partly met |
| M-099 | C 3.6 | Open integration by standard interfaces, APIs, middleware, web services, event-driven methods | partly met |
| M-107 | C 4.6 | Practical integration reusing existing interfaces; incremental addition | target |
| M-108 | C 4.7 | Interfaces with CMMS/EAM, BAS/BMS, HVAC, PBB, BHS, vertical transportation, VMS with analytics | target |
| M-130 | C 6.1 | Evaluate each interface and recommend the approach; systems remain the record | target |
| M-138 | C 6.9 | Representative systems: Genetec, Acuity SensorSwitch, Allen-Bradley BHS and PBB, Simplify i3, PMX, Schneider EcoStruxure, Skidata, Business Central, generator monitoring | partly met |
Requirement identifiers (3)
REQ-SFB-011, REQ-SFB-040, REQ-SFB-041