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
The repairs and inspections in hand, as the maintenance team sees them.
- 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: 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)
| Row | RFP section | Requirement | Status |
|---|
| M-004 | RFP 1.1; C 3.5 | Complement, not replace; existing systems remain authoritative systems of record | partly met |
| M-009 | RFP 3, objective 3 | Better preventive and corrective maintenance through access to information | partly met |
| M-015 | RFP 3, initial scope | Asset management optimization as the first focus | partly met |
| M-089 | C 2.3 | Proactive maintenance; customer service, response times, availability, workflow | partly met |
| M-119 | C 5.3; C 5.4 | Asset records, work orders, PM calendar, backlog, trends, alarm logs and KPIs in the shape maintenance staff know | partly met |
| M-121 | C 5.4 | CMMS/EAM integration is foundational: work requests, orders, PM, corrective, assets, schedules, inspections, history, labour, status, condition, documents | partly met |
| M-122 | C 5.4 | Complement the CMMS/EAM, never replace its core functions | partly met |
| M-131 | C 6.2 | CMMS/EAM information to present (records, hierarchies, locations, requests, orders, PM, corrective, inspections, history, condition, availability, documents) | partly met |
Requirement identifiers (2)