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
The open standards the twin speaks, so the Authority is never locked in.
- 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: 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)
| Row | RFP section | Requirement | Status |
|---|
| M-013 | RFP 3, objective 7 | Open, standards-based, interoperable, evolving without proprietary customization | partly met |
| M-032 | RFP 3, characteristics | Commercially supported software; configuration before customization; open integration; sustainable support; measurable value; expansion | partly met |
| M-058 | B ii | Describe the platform, modules, architecture, hosting model, licensing, third-party components | target |
| M-059 | B ii | Show support for business value, simplicity, COTS, configuration first, systems of record, open integration, practical AI, spatial enablement | partly met |
| M-093 | C 2.7 | Commercially supported, configured with standard tools, vendor-agnostic | partly met |
| M-099 | C 3.6 | Open integration by standard interfaces, APIs, middleware, web services, event-driven methods | partly met |
Requirement identifiers (1)