AirfieldpathOrlando Sanford International

2.48 · Proof of concept · Assets

Maintenance and Work Orders Real

The repairs in progress, read from the Authority's work order system.

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

Screen · Proof of concept · Assets

Maintenance and Work Orders

The repairs in progress, read from the Authority's work order system.

  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
RFP rowsM-004M-121
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

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

Narration line

It shows the open work orders read from the maintenance system of record, each placed on the airfield.

Source: poc/bearings/work.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 (5)
  • Show the open work orders read from the maintenance system of record, each placed on the airfield (REQ-FUNC-058, REQ-INT-004)
  • Show where each work order came from (an inspection, an outage, a find, a schedule) (REQ-FUNC-058)
  • Show preventive maintenance due and overdue against the schedule (REQ-FUNC-059)
  • Never close a work order in the twin: closing happens in the maintenance system, and the twin shows it (REQ-FUNC-060)
  • Read work orders, PM and inspections from Simplify i3, the Authority's CMMS/EAM, as the foundational interface (REQ-SFB-006, REQ-SFB-007)
Requirements matrix rows that name this screen (2)
RowRFP sectionRequirementStatus
M-004RFP 1.1; C 3.5Complement, not replace; existing systems remain authoritative systems of recordpartly met
M-121C 5.4CMMS/EAM integration is foundational: work requests, orders, PM, corrective, assets, schedules, inspections, history, labour, status, condition, documentspartly met
Requirement identifiers (2)

REQ-SFB-006, REQ-SFB-007