2.47 · Proof of concept · Assets
Pavement Real
The condition of the runways and taxiways, with the state's own scores for the runways.
Picture: Headless capture of poc/index.html?v=pavement&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Screen · Proof of concept · Assets
The condition of the runways and taxiways, with the state's own scores for the runways.
- Sources
- Interchange
- Twin
- Screens
- Plan
- Kind
- Screen
- Status
- 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: Pavement. Dark and light modes.
Narration line
It shows every pavement section on the map coloured by its pavement condition index.
Source: poc/bearings/pavement.json, beat "What it shows"
- Group
- Assets
- 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 (6)
- Show every pavement section on the map coloured by its pavement condition index (REQ-FUNC-061, REQ-INT-005)
- Show each section's last survey, its distresses and its recommended maintenance (REQ-FUNC-062)
- Show the pavement management program's inspection schedule and whether it is met (REQ-FUNC-063)
- Show the sections whose condition puts them in the capital plan, with their cost range (REQ-FUNC-064)
- Show the pavement classification ratings published for each runway (REQ-FUNC-065)
- Treat airfield pavement as an asset of the airfield focus area (REQ-SFB-045)
Requirements matrix rows that name this screen (1)
| Row | RFP section | Requirement | Status |
|---|
| M-020 | RFP 3, focus area | Airfield infrastructure | partly met |
Requirement identifiers (1)