The essential maintenance KPIs & reports every plant head needs

Why maintenance runs on numbers, not feel

Ask three people on a shop floor which machine is the biggest headache and you will get three answers — the loudest failure, the most recent one, and the one that stopped a big dispatch. None of them is a fact. The machine that quietly loses two hours a week to small stoppages can cost more in a year than the one that failed dramatically once. Maintenance is full of impressions like this, and impressions are exactly what a reporting discipline exists to replace.

The good news is that if maintenance work is recorded properly, the reports are almost free. A CMMS holds every asset, every preventive job and every breakdown as a linked record, so a report is a live view over documents that already reference each other — not a spreadsheet somebody rebuilds each month from a diary. Get the capture right at the point of work and the numbers reconcile with each other and with the plant's actual experience.

This guide walks the seven reports a plant head genuinely uses, the KPIs each one surfaces, and the decision it drives. It is deliberately practical: no vanity metric that looks good on a slide but changes nothing on the floor.

Leading vs lagging KPIs — and why you need both

Maintenance KPIs split into two kinds, and confusing them is the most common reporting mistake. Lagging indicators tell you what already happened: downtime hours, MTBF, MTTR, breakdown count, maintenance cost. They are the scoreboard. Leading indicators tell you whether the future is being protected: PM compliance, the size of the PM backlog, calibration recalls done on time, spare-stock coverage on critical items. They are the training.

The trap is managing only the scoreboard. A plant that watches downtime but ignores PM compliance is watching the crash instead of the driving. Downtime is a lagging result of a leading cause — preventive work that did or did not get done weeks earlier. The strongest maintenance functions lead with a leading KPI (PM compliance) and confirm with a lagging one (MTBF trend), so effort and outcome are both visible.

1. The PM-due report — what preventive work falls due

The PM-due report is the daily starting point of a planned maintenance function. It lists every preventive maintenance task falling due — now, this week, and overdue — for every asset, whether the trigger is calendar-based (every N days) or usage-based (every N running hours or cycles). Next to it sits the calibration-recall list: measuring instruments due for recalibration, which in Fast Maintenance is functionally a PM schedule for gauges run through the same due-list.

Two columns make it useful rather than decorative. First, an overdue flag, because a PM that is three days late is a leading indicator of a breakdown, not an administrative footnote. Second, criticality, so the planner can protect the assets whose failure hurts most when the week is tight. A plant that works its PM-due list to zero overdue on critical assets is doing the single most valuable thing in maintenance: preventing the failure instead of chasing it.

2. Breakdown ageing — what is open and getting older

Where the PM-due report looks forward, the breakdown-ageing report looks at the present backlog: every open breakdown ticket, grouped by how long it has been open, its priority, and the technician it is assigned to. It mirrors the ticket-follow-up dashboards the platform already runs for complaints and service calls, adapted to maintenance.

It answers the questions a maintenance manager asks at the morning meeting: which machines are down right now; which tickets have been open too long and why; whether a technician is overloaded; and whether anything is stuck waiting on a spare that should have been reordered. A ticket sitting for two days with the note "waiting for bearing" is not a repair problem — it is a spare-stock problem the ageing report just surfaced. Used daily, it stops small breakdowns from quietly ageing into big ones.

3. Downtime analysis — where the lost hours concentrate

Downtime is the core loss maintenance exists to reduce, and the downtime-analysis report is where the loss becomes specific. Built from the time-down and time-restored timestamps on breakdown tickets, it slices downtime hours by asset, by production line, by failure cause, and by period. That slicing is the whole point: total downtime is a number, but downtime by cause is a to-do list.

The classic finding is a Pareto pattern — a handful of assets or a couple of recurring causes account for most of the lost hours. When "hydraulic seal failure" shows up as the top cause on the press line month after month, the report has just told you exactly where a reliability project or a preventive task change will pay back. Without the report, that same failure feels like bad luck each time it happens; with it, it is a pattern you can attack.

4. MTBF, MTTR and availability — the reliability scoreboard

These are the headline reliability KPIs, and a CMMS computes them automatically so nobody tallies by hand. MTBF (mean time between failures) is the average running time between failures — a measure of reliability; higher is better. MTTR (mean time to repair) is the average time to restore a failed asset — a measure of maintainability; lower is better. Availability is derived from the two: MTBF ÷ (MTBF + MTTR).

The value is in the trend, not the single number. Fast Maintenance plots MTBF-over-time and MTTR-over-time per machine, so you can see whether a reliability effort is actually working. Crucially, the two numbers point at two different fixes: raising MTBF comes from preventive maintenance and reliability work, while lowering MTTR comes from spare availability and faster, better-instructed response. Reading them together stops you from throwing preventive effort at a machine whose real problem is that the spare is never on the shelf.

For the full formulas and worked examples, see MTTR, MTBF and availability explained and the Dashboards & MTTR/MTBF feature.

5. Maintenance cost — where the budget actually goes

Maintenance cost is the report that gets a maintenance manager taken seriously in the boardroom, because it speaks the language finance speaks. It rolls up, per asset and per period, the three components of maintenance spend: labour (technician time booked to work orders), spares (parts issued against repairs and preventive jobs), and external service (outside repair and AMC bills procured through the maintenance purchase route).

Read per asset, it exposes the money pit — the machine whose annual maintenance cost is quietly approaching the price of replacing it, a fact no one can see when costs are scattered across stores issues and vendor invoices. Read as a ratio of planned-to-reactive spend, it shows whether the plant is buying down future failures or paying premium prices for emergency ones. Cost framing is what turns a request for a preventive-maintenance budget from a plea into a business case. For the full treatment, see how to reduce maintenance costs.

6. Spare consumption and stock — the hidden half of maintenance

A large share of maintenance cost and a large share of downtime both live in spares, which is why spare consumption and stock deserve their own report. It shows what was consumed, against which asset and work order, and what remains on the shelf against each spare's reorder level. In Fast Maintenance this is grounded in the spare-part master and its spare bill of materials — spares linked to the parent asset — with issues booked against the specific job through the stores engine.

Two questions it answers weekly: which critical spares are below reorder level and need a purchase raised now, and which slow-moving spares are tying up cash on the shelf for a failure that rarely happens. The first prevents a stockout turning a two-hour repair into a two-day one; the second stops the store quietly becoming a graveyard of parts bought in panic and never used. See Spare Parts & BoM and the deeper guide to spare parts inventory management.

7. PM compliance — the leading indicator that predicts the rest

If a plant head could keep only one number, it should be PM compliance: the percentage of scheduled preventive jobs completed on time within their due window. Sixty PM tasks due in a month, fifty-one closed inside their window, gives 85% compliance. It is the best leading indicator in maintenance because it measures discipline before the failures it prevents — a plant that lets compliance slide will usually see breakdown frequency climb a few weeks later, exactly the lag between skipped preventive work and the failure it would have caught.

It is also the report auditors ask for. For ISO 9001 and IATF 16949, a PM-compliance report is direct evidence that a preventive-maintenance programme exists and is followed — not a policy on a shelf but a completed record. Indian auto-component suppliers, in particular, are asked for exactly this at surveillance audits, and a CMMS that produces it on demand turns audit week from a scramble into a print.

A reporting cadence that actually gets followed

Reports only change behaviour when they arrive on a rhythm someone owns. The workable pattern is three tiers. Daily, on the floor: the live machine-status board, the PM-due-today list, and any open high-priority breakdowns — the views that keep work moving. Weekly, at the maintenance meeting: breakdown ageing, PM compliance for the week, and the spare-reorder list — the leading views that keep the backlog from building. Monthly, at the management review: MTBF/MTTR and availability trends, downtime by cause, and maintenance cost per asset — the lagging views that drive reliability and budget decisions.

Alerts close the loop between reports and action. PM-due, breakdown and reorder notifications go out over email, SMS and WhatsApp, so the person who needs to act does not have to remember to open a screen. A report that only lives on a dashboard nobody opens is a report whose schedules slip.

How Fast Maintenance Software builds the stack

Fast Maintenance Software produces every report above from one connected database, built by Improsys in Pune on the shared Fast Suite platform and available cloud or on-premise. Because each maintenance event is a linked record, the reports are live views, not monthly spreadsheet builds.

Frequently asked questions