2.14 · Proof of concept · Terminal
Sensor Gaps (concept) Real
A proposed way to add sensors where no equipment maker's data reaches. A design, not built.
Picture: Headless capture of poc/index.html?v=inflector&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Screen · Proof of concept · Terminal
A proposed way to add sensors where no equipment maker's data reaches. A design, not built.
- 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: Sensor Gaps (concept). Dark and light modes.
Narration line
It shows the gaps no maker data reaches and what fills each one, commercial retrofit sensors first.
Source: poc/bearings/inflector.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 (3)
- Show the gaps no maker data reaches and what fills each one, commercial retrofit sensors first (REQ-SFB-042)
- Show the proposed sensor node design, labelled conceptual (REQ-SFB-042)
- Offer it as an option on the roadmap, never as base scope (REQ-SFB-042, REQ-SFB-057)
Requirements matrix rows that name this screen (2)
| Row | RFP section | Requirement | Status |
|---|
| M-069 | B iii | Future roadmap for expansion | partly met |
| M-145 | Beyond the RFP | Sensors where no maker data reaches | target |
Requirement identifiers (2)