2.61 · Proof of concept · Set up
Intake Real
Documents and data loaded, checked and verified by a person.
Picture: Headless capture of poc/index.html?v=intake&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Screen · Proof of concept · Set up
Documents and data loaded, checked and verified by a person.
- Sources
- Interchange
- Twin
- Screens
- Plan
- Kind
- Screen
- Status
- 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: Intake. Dark and light modes.
Narration line
It lets you load documents and data (the airport layout plan, surveys, as-builts, drawings, asset lists) and let the AI draft the records.
Source: poc/bearings/intake.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)
- Load documents and data (the airport layout plan, surveys, as-builts, drawings, asset lists) and let the AI draft the records (REQ-FUNC-018)
- Match duplicates and check every value against the data standard (REQ-FUNC-018)
- Accept, fix, reject or merge each item, kept with who verified it and when (REQ-FUNC-019)
- Count only verified items (REQ-FUNC-019, REQ-FUNC-020)
- Offer data support to the Authority's staff, priced by labour category (REQ-SFB-055)
Requirements matrix rows that name this screen (1)
| Row | RFP section | Requirement | Status |
|---|
| M-067 | B iii; C 4.5 | Approach, staffing, effort and Authority participation for data collection and consolidation; data readiness risks | target |
Requirement identifiers (1)