MTTR vs MTBF, Explained: Reliability vs Maintainability

MTBF and MTTR are two sides of equipment uptime. MTBF (Mean Time Between Failures) measures reliability, how long an asset runs before it fails. MTTR (Mean Time To Repair) measures maintainability, how long it takes to get it running again. MTBF is about failing less often. MTTR is about recovering faster. Together they determine availability.

What each metric measures

MTBF answers: on average, how long does this equipment run between failures? A higher MTBF means a more reliable asset that breaks down less often. It applies to repairable equipment, the kind you fix and put back into service.

MTTR answers: on average, how long does it take to restore the equipment after it fails? A lower MTTR means a more maintainable asset and a faster, better-prepared response. It covers the time from failure to back-in-service.

Reliability and maintainability are different problems with different fixes, which is exactly why the two metrics are tracked separately.

MTBF vs MTTR at a glance

	MTBF	MTTR
Full name	Mean Time Between Failures	Mean Time To Repair
Measures	Reliability: how long it runs before failing	Maintainability: how long it takes to fix
Question it answers	How often does it fail?	How fast do we recover?
Formula	Operating time ÷ number of failures	Repair time ÷ number of repairs
Better when	Higher	Lower
Improve it by	Better design, condition monitoring, removing root causes	Stocked spares, clear procedures, trained crews

The formulas

MTBF = Total Operating Time ÷ Number of Failures. Count only the time the asset was actually running, divided by how many times it failed.

MTTR = Total Repair Time ÷ Number of Repairs. Add up the time spent restoring the asset, divided by the number of repair events.

For a deeper walk-through of the first one, see how to calculate MTBF.

A worked example

Take a pump monitored over a 720-hour month: 3 failures and 6 hours of total repair time.

Metric	Formula	Calculation	Result
Uptime	Monitored time - repair time	720 - 6	714 h
MTBF	Uptime ÷ failures	714 ÷ 3	238 h
MTTR	Repair time ÷ repairs	6 ÷ 3	2 h

In plain terms, the pump runs about ten days between failures and takes roughly two hours to fix each time.

How they combine into availability

MTBF and MTTR feed directly into inherent availability, the share of time an asset is ready to run.

Availability = MTBF ÷ (MTBF + MTTR). Using the example: 238 ÷ (238 + 2) = 0.9917, about 99.2 percent.

This is why the two metrics matter together. You can raise availability by failing less often (higher MTBF) or by fixing faster (lower MTTR). Both move the same outcome, and the cheaper lever depends on the asset. Availability also flows straight into the availability factor of OEE.

Calculate availability from MTBF and MTTR

Enter an asset's MTBF and MTTR to get its inherent availability. The defaults match the worked example above.

The four meanings of MTTR

MTTR is one acronym for several different clocks, and mixing them up causes endless confusion. Define which you mean before you report it.

• Mean Time To Repair: hands-on wrench time only.
• Mean Time To Recover: failure until the asset is back in service.
• Mean Time To Respond: failure until someone starts working on it.
• Mean Time To Resolve: the full cycle, including the follow-up to stop it recurring.

Pick one definition and apply it consistently, or your trend lines will measure nothing.

Which one to focus on

Focus on MTBF when failures are frequent and the cost is in the disruption itself. You raise it through better design, condition monitoring, predictive maintenance, and removing the root causes of repeat failures.

Focus on MTTR when failures are tolerable but slow to fix. You lower it through stocked spares, clear procedures, better access to the equipment, and trained crews who are not improvising at 2 a.m.

If you have to choose, start with whichever has the worse ratio against its target. A long MTTR on a frequently failing asset is a double penalty and usually the first thing to attack.

Both MTBF and MTTR are lagging indicators: they summarize what already happened. Their leading drivers, the things you act on this week, are activities like PM compliance and planned-work percentage. See leading vs lagging indicators for how to pair them, and note that frequent failures also feed your maintenance backlog, so reliability work pays off twice.

Common mistakes

• Mixing the four meanings of MTTR. Comparing repair-only time on one asset against recover time on another makes the numbers meaningless.
• Counting planned downtime as failures. Scheduled maintenance and changeovers are not failures and do not belong in the MTBF failure count.
• Inconsistent repair clocks. Including wait-for-parts time in MTTR some months and not others hides the real trend. Decide what the clock includes and keep it fixed.
• Optimizing one metric in isolation. A fast MTTR on an asset that fails constantly is still a problem. Read both against availability, not on their own.

From tracking failures to preventing them

MTBF and MTTR tell you how often things break and how long they take to fix, but not which asset to address first, what is actually driving the repeat failures, or whether reliability or speed is the better investment for a given line. Those answers live in maintenance history, sensor data, and production records that rarely sit in one place.

This is the part SteelTree handles. It connects to those systems, and where the data is scattered or missing, it captures what it needs directly from the work itself. It turns the trend into a decision: which assets are quietly eroding availability, what is causing it, and the next action that buys back the most uptime, with the reasoning attached. And because it captures the reasoning behind each decision, the system compounds. It gets sharper at your plant the longer you run it.

See how SteelTree can transform your operational processes →