Maintenance Reports
One report covers the machine side, and it is the one that turns a wall of red tiles into an argument for a capital purchase.
Machine Maintenance
Machine Maintenance lists every machine assigned to a Work Center, over a rolling window (90 days by default — change it with the Days filter).
Columns:
| Column | What it tells you |
|---|---|
| Machine / Name | The Asset and its label. |
| Work Center / Unit | Where it sits. |
| Critical | Whether its failure takes the station offline. |
| Health | Its state right now — Running, Service Due, Under Maintenance, Breakdown. |
| Breakdowns | Failures logged in the window. |
| MTTR (h) | Mean time to repair, across completed repairs. |
| Downtime (h) | Total hours lost. Open breakdowns count up to now. |
| Availability % | Uptime as a share of the window. |
| Last Breakdown | When it last failed. |
How to read it
- Sort by Downtime. The top few machines usually account for most of the loss. That is your list, not the machine that failed most recently.
- Compare Breakdowns against MTTR. Many failures with a low MTTR is a maintenance-routine problem — the machine is being nursed. Few failures with a high MTTR is a spare-parts problem — nobody had the part.
- Filter to Critical. Availability on critical machines is the number that actually maps to lost production.
- Watch Availability on a machine near end of life. Two quarters of falling availability, with the downtime hours priced against a line's hourly rate, is a replacement case that finance can read.
Open it from the Maintenance sidebar under Reports, from the launch pad tile, or with Cmd/Ctrl + K → machine maintenance.
The same numbers elsewhere
The fleet-wide version of these metrics — availability, breakdowns, MTTR, MTBF and downtime across every internal Work Center — sits on the KPI strip of Floor Monitor, so you get the headline without opening a report.
MTBF (mean uptime between failures) appears there rather than in the report, because it only means something across a fleet: a single machine that failed once has no meaningful "between".
Costs
Repair cost lives on the Asset Repair — both ERPNext's own repair cost and GarmentFlow's Logged Repair Cost for work done in-house — and consumed parts sit in the repair's consumed-items table. That means machine spend reconciles through ERPNext's standard asset and stock reporting rather than through a parallel set of numbers here.
To see what a machine has eaten in parts, open its drawer and read the spare-parts tab: quantity, value and how many times each part was consumed.
What to do next
That closes Maintenance. Head back to the Maintenance hub, or over to Production Units to see how Work Centers feed production capacity.