AirfieldpathOrlando Sanford International

2.54 · Proof of concept · Prove

Duties and Deadlines Real

Every recurring duty, who owns it, when it is next due and the evidence held.

Picture: Headless capture of poc/index.html?v=duties&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.

Screen · Proof of concept · Prove

Duties and Deadlines

Every recurring duty, who owns it, when it is next due and the evidence held.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. 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

Duties and Deadlines, a capture of the screen
Capture of the screen: Duties and Deadlines. Dark and light modes.

Narration line

It lists each duty with the rule that creates it, its owner role, frequency, next due date, evidence and state.

Source: poc/bearings/duties.json, beat "What it shows"

Group
Prove
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 (2)
  • List each duty with the rule that creates it, its owner role, frequency, next due date, evidence and state (REQ-SFB-066)
  • Link each duty to the rule pack that defines it (REQ-SFB-066, REQ-SFB-065)
Requirements matrix rows that name this screen (3)
RowRFP sectionRequirementStatus
M-092C 2.6Timely information for decisions through dashboards, workflows, notifications, analyticspartly met
M-120B ii; C 2.7Rules and data loaded as versioned packs, each in its true state, each rule traced to its screens; a duty registerpartly met
M-147Beyond the RFPPart 139 records: self-inspection, condition reporting and NOTAM drafts, SMSpartly met
Requirement identifiers (2)

REQ-SFB-065, REQ-SFB-066