AirfieldpathOrlando Sanford International

2.16 · Proof of concept · Maintenance

Work Orders Real

The repairs and inspections in hand, as the maintenance team sees them.

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

Screen · Proof of concept · Maintenance

Work Orders

The repairs and inspections in hand, as the maintenance team sees them.

  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
SheetA-10

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

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

Narration line

It lists work orders by type, priority, asset, status and age.

Source: poc/bearings/wo.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 (4)
  • List work orders by type, priority, asset, status and age (REQ-SFB-060)
  • Show one record with its lifecycle from requested to closed (REQ-SFB-060)
  • Show failure code, problem, cause, remedy, labour, parts and the times to respond and repair (REQ-SFB-060)
  • Show the sign-off and audit trail; never close a work order in the twin (REQ-SFB-060, REQ-SFB-008)
Requirements matrix rows that name this screen (8)
RowRFP sectionRequirementStatus
M-004RFP 1.1; C 3.5Complement, not replace; existing systems remain authoritative systems of recordpartly met
M-009RFP 3, objective 3Better preventive and corrective maintenance through access to informationpartly met
M-015RFP 3, initial scopeAsset management optimization as the first focuspartly 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
M-121C 5.4CMMS/EAM integration is foundational: work requests, orders, PM, corrective, assets, schedules, inspections, history, labour, status, condition, documentspartly met
M-122C 5.4Complement the CMMS/EAM, never replace its core functionspartly met
M-131C 6.2CMMS/EAM information to present (records, hierarchies, locations, requests, orders, PM, corrective, inspections, history, condition, availability, documents)partly met
Requirement identifiers (2)

REQ-SFB-008, REQ-SFB-060