MTBF meaning: what mean time between failures measures, the mtbf formula with example figures from a real month, and an mtbf calculation example you can copy

Updated

MTBF is mean time between failures: the average operating time an asset runs before it fails, worked out from how long it ran and how many times it stopped. For a maintenance manager it is the plainest measure of whether an asset is getting better or worse, and it is the number that says whether a preventive interval is set right. This page gives the mtbf meaning without the statistics, the mtbf formula with example figures, and an mtbf calculation example you can repeat from a work order history.

The formula, and what counts as a failure

MTBF equals total operating time divided by the number of failures in that time. Operating time is the hours the asset was actually running, not calendar hours, so a machine on one shift accrues fewer hours than one on three. A failure is an unplanned stop that needed a repair; a planned stop for a scheduled task is not a failure and is left out of the count, which is why the work order type matters: a history that does not separate reactive from planned work cannot produce an honest MTBF.

A calculation example from one month of history

Take a packaging line that ran two shifts for a month, about 340 operating hours, and stopped unplanned four times in that month according to its reactive work orders. MTBF is 340 divided by 4, which is 85 hours. The figure on its own says little; what says something is the trend. If the same line read 120 hours the month before and 60 the month after, the asset is deteriorating and the schedule against it is not keeping up. If the number climbs after a new preventive task was added, the task is earning its place.

What MTBF is not

It is not a prediction of when the next failure will come; an asset with an MTBF of 85 hours can fail twice in a day and then run for a fortnight. It is not comparable between assets of different kinds, because a conveyor and a chiller fail differently. And it is not meaningful over a short window with one or two failures, where a single event moves the number by half. Use it over months, on the same asset, from the same work order history.

Where the numbers come from

Every figure in the formula comes from records: run hours from the asset's meter or the production log, failures from the reactive work orders against that asset. A CMMS that holds both produces MTBF for every asset without anyone opening a spreadsheet, and the maintenance log worksheet on this site holds the same two columns for a team that is not there yet.

Questions people ask about mtbf meaning

Is a higher MTBF always better?

Higher means fewer unplanned stops per operating hour, which is what a maintenance team wants. The question is what it cost: an MTBF driven up by replacing parts far too early is bought with preventive hours the site did not need to spend.

What is a good MTBF?

There is no general answer. A good MTBF is one that is rising for an asset you are working on, or steady for one you are not. Compare an asset with itself over time, not with a figure from elsewhere.

How is MTBF different from MTTF?

MTTF, mean time to failure, is used for things that are replaced rather than repaired, a lamp or a fuse. MTBF is for things that are repaired and returned to service. For a maintenance team almost everything on the register is an MTBF asset.

Sources

Related answers

Price your reactive work against plannedSee what your PM schedule costs to run