2.36 · Proof of concept · Operate
Condition and NOTAMs Real
Airfield conditions and the notices pilots receive, drafted here and filed by a person.
Picture: Headless capture of poc/index.html?v=notam&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Screen · Proof of concept · Operate
Airfield conditions and the notices pilots receive, drafted here and filed by a person.
- 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: Condition and NOTAMs. Dark and light modes.
Narration line
It shows every airport condition in force, each with its NOTAM, its time and its source.
Source: poc/bearings/notam.json, beat "What it shows"
- Group
- Operate
- 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 every airport condition in force, each with its NOTAM, its time and its source (REQ-FUNC-025)
- Draft a NOTAM from a closure or a condition on the map, in the format of the NOTAM manual, for a person to file in the FAA's system (REQ-FUNC-026)
- Never file a NOTAM itself: the FAA system stays the system of record, and the twin shows what was filed there (REQ-FUNC-026)
- Show the runway condition codes when reported, with the matrix they came from (REQ-FUNC-028)
- Close the loop: a condition ends when its NOTAM is cancelled in the FAA system, and the twin shows both (REQ-FUNC-027)
Requirements matrix rows that name this screen (1)
| Row | RFP section | Requirement | Status |
|---|
| M-147 | Beyond the RFP | Part 139 records: self-inspection, condition reporting and NOTAM drafts, SMS | partly met |