Resources / Metrics

How to calculate MTBF, MTTR and availability

MTBF (mean time between failures) is operating time divided by the number of failures. MTTR (mean time to repair) is total repair time divided by the number of repairs. Availability is the share of time an asset could do its job: uptime divided by uptime plus downtime, which for repairable equipment is approximately MTBF divided by MTBF plus MTTR.

Metrics 4 min read

Key points

  • MTBF tells you how often an asset fails. MTTR tells you how quickly you recover. Availability combines the two.
  • Agree on what counts as a failure before you measure. Planned servicing is not a failure.
  • State which hours you used: operating hours from the meter, or calendar hours. Both are valid, but they give different numbers.
  • A median repair time is often more honest than the mean, because one long repair can dominate the average.

The three formulas

MTBF = operating time ÷ number of failures

MTTR = total repair time ÷ number of repairs

Availability = uptime ÷ (uptime + downtime) ≈ MTBF ÷ (MTBF + MTTR)

The approximation in the third line holds when downtime is mostly repair time. If machines also stand idle waiting for an operator or for work, measure availability directly from recorded downtime rather than deriving it.

A worked example

The figures below are invented to show the arithmetic. One excavator over a 30-day month, working a single 10-hour shift, 26 working days:

ItemValue
Scheduled operating time260 h
Failures (unplanned stops needing repair)3
Repair times2 h, 4 h and 14 h
Total downtime20 h
  • Uptime = 260 − 20 = 240 h
  • MTBF = 240 ÷ 3 = 80 operating hours between failures
  • MTTR = 20 ÷ 3 ≈ 6.7 h (the median repair is 4 h)
  • Availability = 240 ÷ 260 ≈ 92.3%

Note how the single 14-hour repair pulls the mean repair time well above the typical one. Reporting both the mean and the median tells the reader whether the problem is slow repairs in general or one bad week, usually waiting for a part.

What counts as a failure

MTBF is only comparable across assets and months if everyone counts the same events. A workable definition:

  • Count: any unplanned stop where the asset could not do its job and needed a repair.
  • Do not count: planned services, inspections, waiting for work or an operator, and reports raised in error.
  • Decide once: whether a repeat of the same fault within a few days is a new failure or the same one reopened, and apply it consistently.

Operating hours or calendar hours?

Operating MTBF uses the hours the machine actually ran, from its hour meter. Calendar MTBF uses elapsed time. Operating MTBF is the better measure of reliability, because a machine that worked twice as hard should be allowed to fail twice as often. Calendar MTBF is easier to get, because it needs no meter readings. Either is fine; mixing them in one report is not. Label the basis next to the number.

Common mistakes

  1. Averaging small numbers. One failure in a month gives an MTBF equal to the whole month. Use a longer window or group similar assets before drawing conclusions.
  2. Repair time that is really waiting time. Split downtime into response, waiting for parts and actual repair. MTTR alone hides which one is slow.
  3. Counting from when a repair was logged, not when the machine stopped. If faults are reported late, downtime is understated.
  4. Including off-site assets. Machines that have been transferred or are off hire are not part of your availability figure.

Frequently asked questions

What is a good MTBF?
There is no universal figure: it depends on the asset type, its age, how hard it works and how failures are counted. The useful comparison is the same asset class against itself over time, and similar machines against each other on your own site.
What is the difference between MTTR and downtime?
Downtime is the total time an asset was unavailable. MTTR is the average time per repair. A machine can have a short MTTR and still a lot of downtime if it fails often.
Should planned maintenance count as downtime?
For MTBF and MTTR, no: they measure failures. For availability, decide and say so. Some teams report availability against all downtime, others only against unplanned downtime. Both are valid when labelled.

Start free today.

Try the Business plan free for 14 days, with no card. After that, one user and up to 25 assets stay free for as long as you like.