AirfieldpathOrlando Sanford International

2.62 · Proof of concept · Set up

Open Standards Real

The open standards the twin speaks, so the Authority is never locked in.

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

Screen · Proof of concept · Set up

Open Standards

The open standards the twin speaks, so the Authority is never locked in.

  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

Open Standards, a capture of the screen
Capture of the screen: Open Standards. Dark and light modes.

Narration line

It lists the standards the twin reads and writes, each with its body, version and source.

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

Group
Set up
Status as the app labels it
Real
Basis
The screen runs. The standards table is read from the registry.
What the screen must do (5)
  • List the standards the twin reads and writes, each with its body, version and source (REQ-FUNC-073)
  • Export the airport's data in open formats on request (REQ-FUNC-074)
  • Show the same action on the screen, through the API and in the terminal (REQ-ARCH-003)
  • Show which standards the RFP names as awaiting RFP (REQ-FUNC-075)
  • Use industry-standard interfaces and methods (REQ-SFB-022)
Requirements matrix rows that name this screen (6)
RowRFP sectionRequirementStatus
M-013RFP 3, objective 7Open, standards-based, interoperable, evolving without proprietary customizationpartly met
M-032RFP 3, characteristicsCommercially supported software; configuration before customization; open integration; sustainable support; measurable value; expansionpartly met
M-058B iiDescribe the platform, modules, architecture, hosting model, licensing, third-party componentstarget
M-059B iiShow support for business value, simplicity, COTS, configuration first, systems of record, open integration, practical AI, spatial enablementpartly met
M-093C 2.7Commercially supported, configured with standard tools, vendor-agnosticpartly met
M-099C 3.6Open integration by standard interfaces, APIs, middleware, web services, event-driven methodspartly met
Requirement identifiers (1)

REQ-SFB-022