Back to Glossary

Entry · KPIs

Mean Time Between Failures

Mean time between failures, usually shortened to MTBF, is the average amount of running time a piece of equipment or a system delivers between one unplanned breakdown and the next. It is a reliability measure: a higher MTBF means the asset keeps working for longer before something goes wrong.

Businesses track it because every failure carries a cost in lost output, repair labour and disappointed customers.

What it means

MTBF answers a simple question that finance and operations both care about: how often does this thing break? It is calculated from real operating hours rather than calendar time, so a machine that runs one shift a day and one that runs three shifts are compared fairly.

The measure applies to physical assets such as pumps and delivery vans, and equally to servers, payment terminals and software services. The business case for tracking MTBF is that unplanned downtime is almost always more expensive than planned maintenance.

A production line that stops without warning wastes material in progress, idles paid staff and can trigger late delivery penalties, while the same hours taken deliberately at a quiet time cost a fraction of that. Improving MTBF therefore converts chaotic spending into predictable spending.

In practice, teams log operating hours and failure events, then review MTBF monthly by asset class rather than for the fleet as a whole. Aggregating everything hides the problem: one poorly maintained machine with a 200 hour MTBF can sit inside a fleet average of 1,200 hours and never be noticed.

Splitting the number by asset, site and shift is where the useful insight lives. There are important nuances about what counts as a failure.

Most organisations count only unplanned stoppages that require intervention, excluding scheduled maintenance and short operator adjustments, and the definition has to be written down or the number becomes meaningless when compared across sites. MTBF also assumes the asset is repaired and returned to service, which is why single-use or non-repairable items use mean time to failure instead.

Finally, MTBF alone does not describe availability. An asset that fails rarely but takes three days to fix may deliver less usable time than one that fails more often but is back running within an hour, which is why MTBF is almost always read alongside mean time to repair.

In practice

Real-world examples.

1

Example

A regional bakery tracks MTBF on its dough mixers and finds the oldest unit averages 340 hours against a fleet average of 1,100. Replacing that single mixer costs $28,000 but removes roughly two production stoppages a month, and the site manager uses the MTBF gap to win approval for the spend.

2

Example

A payments company reports MTBF for its card terminals to a retail client during a contract renewal. Showing 4,000 operating hours between failures against the client's previous supplier at 1,500 hours becomes the strongest argument in the negotiation, even though the per-terminal price is higher.

3

Example

A cloud software team measures MTBF for its checkout service and sees it fall from 900 hours to 260 hours after a release. The drop triggers an engineering review that traces the problem to a memory leak, and the metric recovers to 850 hours the following quarter.

Think of it

MTBF shows how long equipment typically runs before breaking-your reliability measure.

Formula

Calculation

MTBF = Total operating hours / Number of unplanned failures A packaging plant runs 20 filling machines, and over the past month each machine operated for 500 hours, giving 20 x 500 = 10,000 total operating hours. Maintenance logs record 8 unplanned failures across the fleet in that period. MTBF = 10,000 / 8 = 1,250 operating hours between failures. The plant's finance team costs each unplanned failure at $4,200 in lost output, overtime and scrapped product, so the month's failures cost 8 x $4,200 = $33,600. If a maintenance programme lifts MTBF to 2,000 hours, the same 10,000 operating hours would produce 10,000 / 2,000 = 5 failures, cutting the monthly cost to 5 x $4,200 = $21,000. The saving is $33,600 - $21,000 = $12,600 a month, or $151,200 a year, which is the number that justifies the maintenance budget.

Case study

Seen in the real world.

Consider Ridgeway Bottling, an illustrative and entirely fictional drinks canning business running three lines across two sites. Head office knew downtime was costly but only tracked total hours lost, which had sat stubbornly around 190 hours a quarter for two years despite steadily rising maintenance spending.

When the operations director began calculating MTBF per line, the picture changed. Two lines averaged 1,400 operating hours between failures while the third averaged 310, and almost the entire maintenance overspend was being absorbed by that one line without anyone framing it as a single problem. A targeted rebuild of the third line's capping head cost $65,000 and lifted its MTBF to 1,200 hours.

Quarterly downtime fell to 70 hours and the company reduced its overtime budget accordingly. The lasting change was cultural: every capital request at Ridgeway now carries a before and after MTBF estimate, which makes reliability arguments concrete rather than anecdotal.

Watch out

Common mistakes.

  • Using calendar hours instead of actual operating hours, which flatters equipment that sits idle and makes heavily used assets look unreliable by comparison.
  • Counting planned maintenance stoppages as failures, which drags the number down and quietly punishes the sites doing preventive work properly.
  • Reporting one fleet-wide MTBF, so a small number of badly performing assets hide inside a comfortable average and never get fixed.

Questions

People also ask.

Does a high MTBF always mean high availability?

No, because an asset that fails rarely but takes days to repair can deliver less usable time than one that fails more often and is fixed within the hour.

How much history do I need before MTBF is meaningful?

Enough operating hours to capture several failures, so a rough guide is at least five to ten recorded failures per asset class before you draw conclusions.

Is MTBF only for machinery?

No, it is used just as widely for software services, networks and payment hardware, where operating hours are simply uptime and failures are unplanned outages.

From the founder's library

Accounting Fundamentals: A Non-Finance Manager's Guide to Finance and Accounting, by Shihan Sheriff

Take it further with the book.

Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.

US$2.24US$2.99

25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.

View the book and save 25%
Last updated · September 5, 2026
Browse all terms →

Disclaimer

The information provided in this finance dictionary is for educational and informational purposes only. It should not be construed as financial, investment, legal, or tax advice. Always consult with a qualified professional before making any financial decisions. Money Master HQ makes no representations or warranties about the accuracy, completeness, or suitability of this information. Use of this content is at your own risk.