Maintenance KPIs
Six-month trend per KPI — and, behind each one, the causes and what the copilot did to prevent it.
| KPI | JunCurrent · partial | MayLast full month | Apr | Mar | Feb | Jan |
|---|---|---|---|---|---|---|
Overdues WOs | 39 | 47 | 55 | 51 | 42 | 48 |
Plan attainment % | 88 | 85 | 82 | 78 | 79 | 76 |
Unplanned work % | 26 | 28 | 30 | 34 | 33 | 36 |
Backlog wks | 5.7 | 6.1 | 6.6 | 6.4 | 6.0 | 6.2 |
WO cycle time days | 12 | 14 | 17 | 16 | 14 | 15 |
Maintenance costs % budget | 96 | 103 | 111 | 107 | 99 | 104 |
Overdues — what went overdue, and why
New overdues per cause, and how far the copilot’s prevention loop got: an alert was raised, the planner logged a cause and acted, and the follow-up (e.g. an engineer BOM update) closed the loop to prevent recurrence.
Copilot prevention loop · Jun
New overdue
Copilot alerted
Planner acted
Resolved · recurrence prevented
By cause
BOM outdated
Material late
Permit delay
Engineering review
Capacity
Other
Example: a planner alert to set a WO “ready to schedule” is flagged by the planner as a wrong BOM — logged under BOM outdated. When the engineer completes the BOM-update task, the loop closes and it counts under Resolved. Hover a cause for how its loop closes.