AirfieldpathOrlando Sanford International

2.18 · Proof of concept · Maintenance

Backlog Real

How much work is waiting, and how long it has waited.

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

Screen · Proof of concept · Maintenance

Backlog

How much work is waiting, and how long it has waited.

  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
ScreensBacklog

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

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

Narration line

It shows the backlog by age and in weeks of crew time.

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

Group
Maintenance
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)
  • Show the backlog by age and in weeks of crew time (REQ-SFB-062)
  • Place backlog items on the plan with their criticality and condition (REQ-SFB-062)
Requirements matrix rows that name this screen (3)
RowRFP sectionRequirementStatus
M-009RFP 3, objective 3Better preventive and corrective maintenance through access to informationpartly met
M-089C 2.3Proactive maintenance; customer service, response times, availability, workflowpartly met
M-119C 5.3; C 5.4Asset records, work orders, PM calendar, backlog, trends, alarm logs and KPIs in the shape maintenance staff knowpartly met
Requirement identifiers (1)

REQ-SFB-062