Skip to content

Free template

Updated

Maintenance KPI tracker

A maintenance KPI tracker puts the few numbers that show how equipment and the maintenance team are doing on one sheet, worked out the same way every month. This one tracks mean time between failures (MTBF = operating hours ÷ failures), mean time to repair (MTTR = repair hours ÷ repairs), availability from those two (MTBF ÷ (MTBF + MTTR)), PM compliance (PMs done on time ÷ PMs due), planned maintenance percentage (planned hours ÷ all maintenance hours) and backlog in weeks (approved hours not done ÷ crew hours per week). Page 1 is a monthly sheet with one row per asset and the plant row worked out from the totals. Page 2 has the definitions, a 12-month trend and a worked example. The Excel version has an asset log, a plant sheet by month with targets and charts, a by-asset view for any period that ranks the lowest MTBF, and the worked example.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Page 1 of the maintenance KPI trackerFields for site, month and who prepared it, a table with one row per asset for operating hours, failures, repair hours, repairs, MTBF, MTTR, availability, PMs due, PMs done on time and PM compliance, a plant row, and a strip for planned and unplanned hours and backlog weeks.
MTBFMTTRAvailabilityPM compliancePlanned maintenance %Backlog weeksPlant row from totals12-month trend

When to use it

When to use a maintenance KPI tracker

  • For the monthly maintenance review, so the same numbers are worked out the same way every time.
  • When breakdowns feel worse but nobody can show it.
  • To see whether a PM program is keeping up, before you add more PMs.
  • To pick which assets need a reliability project first.

How to fill it in

  1. 1

    Agree the definitions first

    What counts as a failure, whether repair time is the whole outage or hands-on time, and what counts as a PM done on time. Write them on the sheet and do not change them mid-year.

  2. 2

    Collect operating hours per asset

    The hours each asset actually ran, from the run log or the production schedule, not the hours the plant was open.

  3. 3

    Take failures and repair hours from the work orders

    Count corrective work orders for breakdowns and add up the repair hours. Repairs are usually the same as failures; fill them in when one failure took two repairs.

  4. 4

    Count PMs due and done on time

    From the PM schedule. A PM done after its due date, or after the grace window you set, counts as done but not as on time.

  5. 5

    Work out the plant row from the totals

    Plant MTBF is all operating hours ÷ all failures, not an average of the assets' MTBFs. The same goes for MTTR and PM compliance.

  6. 6

    Review the trend and act

    Look at the direction over months, then at the assets with the lowest MTBF and the most missed PMs. Pick one or two to work on.

A filled-in example

Illustrative, not a benchmark

An example: one month, three assets (illustrative numbers).

The example month's three assets

  1. Press 4: 4 failures in 600 h150 h
  2. Conveyor C3: 2 failures in 640 h320 h
  3. Robot welder W2: 7 failures in 560 hLowest80 h
  1. Press 4: 5 of 683%
  2. Conveyor C3: 4 of 4100%
  3. Robot welder W2: 3 of 560%

MTBF: press 4 150 hours, conveyor C3 320 hours, robot welder W2 80 hours. PMs on time: 5 of 6, 4 of 4 and 3 of 5.

W2 has the lowest MTBF and missed two of its five PMs, so it is the one to act on. Plant: MTBF 138.5 h, MTTR 2.77 h, PM compliance 80%.
  • Press 4: 600 operating hours, 4 failures, 10 repair hours: MTBF 150 h, MTTR 2.5 h, availability 98.4%. 5 of 6 PMs on time (83%).
  • Conveyor C3: 640 h, 2 failures, 5 repair hours: MTBF 320 h, MTTR 2.5 h, availability 99.2%. 4 of 4 PMs on time.
  • Robot welder W2: 560 h, 7 failures, 21 repair hours: MTBF 80 h, MTTR 3.0 h, availability 96.4%. 3 of 5 PMs on time (60%).
  • Plant: MTBF 1,800 ÷ 13 = 138.5 h, MTTR 36 ÷ 13 = 2.77 h, availability 1,800 ÷ 1,836 = 98.0%, PM compliance 12 ÷ 15 = 80%. Labor: 520 planned and 280 unplanned hours = 65% planned; backlog 360 h ÷ 120 crew hours a week = 3.0 weeks.

W2 had the lowest MTBF and missed two of its five PMs, so the two missed PMs went on next week's schedule and the team started a review of its seven failures. The other two assets needed no action that month.

Common mistakes

  • Averaging the assets' MTBFs

    An asset that ran 20 hours with one failure would count as much as one that ran 600. Work the plant figure out from the totals.

  • Using calendar hours as operating hours

    A machine that ran one shift of three has a third of the hours. Calendar hours make MTBF look three times better than it is.

  • Counting late PMs as on time

    PM compliance that counts every PM eventually done stays near 100% while the schedule slips. Count on time separately.

  • Changing definitions without saying so

    If MTTR moves from hands-on time to the whole outage, it jumps overnight and the trend means nothing. Note any change on the sheet.

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

LeanSuite's KPI Dashboards track each KPI against its target with Red-Amber-Green ranges and whether up or down is good, and values come from LeanSuite forms, ERP, MES or Excel, on a schedule from Excel on SharePoint or OneDrive or Google Sheets, or from a CSV upload.

See it in a 45-minute demo

FAQ

Maintenance KPI tracker: common questions

  1. MTBF = operating hours ÷ number of failures. MTTR = repair hours ÷ number of repairs. An asset that ran 600 hours with 4 failures and 10 hours of repairs has an MTBF of 150 hours and an MTTR of 2.5 hours.

  2. The share of preventive maintenance tasks due in a period that were done on time: PMs done on time ÷ PMs due. Many plants count a PM as on time inside a grace window they set, for example 10% of the interval.

  3. Start with a few you can collect reliably: MTBF and MTTR per asset, PM compliance, planned maintenance percentage and backlog. Add more only when these are worked out the same way every month.

  4. MTBF ÷ (MTBF + MTTR) counts only breakdowns. OEE availability counts every stop against planned production time, including setups and waiting, so it is usually lower.

  5. Add up the estimated hours of approved work not yet done and divide by the crew hours available per week. 360 hours of backlog with 120 crew hours a week is 3 weeks.

More free templates

All templates
Browse all 199 templates

Can't find the template you need?

Tell us what you're looking for. We'll make it and send it to your inbox, free.

A shift handover sheet, a red tag log, a changeover checklist for one machine: if your team uses it on the floor, ask.

By sending this form you agree to our Terms of Service and Privacy Policy.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.