2.67 · Proof of concept · Set up
Platform Family Real
The sister products this one is built beside, and what each actually holds.
Picture: Headless capture of poc/index.html?v=family&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Screen · Proof of concept · Set up
The sister products this one is built beside, and what each actually holds.
- Sources
- Interchange
- Twin
- Screens
- Plan
- Kind
- Screen
- Status
- not offered, target, partly met
- 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: Platform Family. Dark and light modes.
Narration line
It shows the sister products (roads and corridors, farm fields, drone spraying) by what each one holds, built or POC only.
Source: poc/bearings/family.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 (5)
- Show the sister products (roads and corridors, farm fields, drone spraying) by what each one holds, built or POC only (REQ-FUNC-115)
- Show what exists toward a cloud-hosted, multi-tenant service and what is a target (REQ-FUNC-116, REQ-ARCH-004)
- Show the Florida state systems the airport sits inside, each with its source (REQ-FUNC-117)
- Claim nothing a sister repository does not hold (REQ-FUNC-115)
- Show how the platform expands by configuration (REQ-SFB-056)
Requirements matrix rows that name this screen (8)
| Row | RFP section | Requirement | Status |
|---|
| M-001 | RFP 1.1 | Configure, integrate, deploy and support a commercially available Digital Twin Platform | not offered |
| M-007 | RFP 3, objective 1 | A scalable platform for operations, maintenance and asset management | target |
| M-032 | RFP 3, characteristics | Commercially supported software; configuration before customization; open integration; sustainable support; measurable value; expansion | partly met |
| M-051 | RFP 10.2.1; B II i | Two-page statement of ability with digital twin or comparable experience | target |
| M-054 | B i; RFP 10.4.1 | Experience implementing digital twin, asset visualization or integrated OT platforms | partly met |
| M-058 | B ii | Describe the platform, modules, architecture, hosting model, licensing, third-party components | target |
| M-096 | C 3.3 | COTS preferred; standard capabilities; minimal custom development | not offered |
| M-143 | Beyond the RFP | A platform proven on other places | partly met |
Requirement identifiers (1)