AirfieldpathOrlando Sanford International

2.60 · Proof of concept · Set up

Systems of Record Real

Every system the twin reads, and proof that each one stays the record.

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

Screen · Proof of concept · Set up

Systems of Record

Every system the twin reads, and proof that each one stays the record.

  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
SheetA-10

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

Systems of Record, a capture of the screen
Capture of the screen: Systems of Record. Dark and light modes.

Narration line

It lets you prove the Authority's systems stay the record: every value on every screen names the system that owns it, and the twin holds no value of its own for a function a system of record covers.

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

Group
Set up
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 (7)
  • Prove the Authority's systems stay the record: every value on every screen names the system that owns it, and the twin holds no value of its own for a function a system of record covers (REQ-FUNC-007, REQ-FUNC-014)
  • List every system of record and public source with its state (proposed, approved, active, paused, blocked, retired) and the age of its last reading (REQ-FUNC-011)
  • Show the probe, the licence or data agreement, the freshness target and the approver for each source (REQ-FUNC-012, REQ-FUNC-013)
  • Refuse to activate a source without a probe, a confirmed licence and an approver who is not the activator (REQ-FUNC-012, REQ-SEC-002)
  • Show the selected airport systems the RFP names as awaiting RFP until the document is read (REQ-FUNC-017)
  • Show which values each source owns, so the system of record is never in doubt (REQ-FUNC-014, REQ-FUNC-016)
  • Name each of the Authority's systems as Attachment C 6.9 lists them, with their connectivity (REQ-SFB-011, REQ-SFB-021, REQ-SFB-022, REQ-SFB-023)
Requirements matrix rows that name this screen (15)
RowRFP sectionRequirementStatus
M-002RFP 1.1A common operational environment integrating information from selected airport systemspartly met
M-004RFP 1.1; C 3.5Complement, not replace; existing systems remain authoritative systems of recordpartly 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-024RFP 3, data integrationIntegrate CMMS/EAM, BAS/BMS, HVAC, PBB, BHS, vertical transportation and otherstarget
M-059B iiShow support for business value, simplicity, COTS, configuration first, systems of record, open integration, practical AI, spatial enablementpartly met
M-060B iiIntegration and data approach: APIs, middleware, web services, event-driven methods, data readiness, dependencies, interoperabilitypartly met
M-090C 2.4Integrate systems; do not replace monitoring, control or management systemspartly met
M-098C 3.5Existing systems remain systems of recordpartly met
M-106C 4.5Identify, configure, test and implement interfaces; data support on request with job descriptions and ratestarget
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-136C 6.7Additional systems may be recommended: VMS, security, fire alarm, electrical, utility, passenger and flight information, energytarget
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 (4)

REQ-SFB-011, REQ-SFB-021, REQ-SFB-022, REQ-SFB-023