MTBF and MTTR sound like two separate numbers, but they're mathematically locked together — get one wrong and your availability figure, and every maintenance decision built on it, is wrong too. This page gives you the exact formulas, a fully worked example you can follow with a pen and your own numbers, and the reference points to know whether your result is actually healthy for a critical asset. Sign up free and let OxMaint calculate these automatically from your existing work order history whenever manual maths gets tedious.
A Fully Worked Example
Formulas are easier to trust once you've seen them applied to real numbers. Here's a centrifugal pump that ran for a quarter with three recorded failures — the same calculation works for any asset once you have uptime, repair time and a failure count.
Scheduled operating time
2,160 hours
Downtime from 3 failures
18 hours
Total uptime
2,160 − 18 = 2,142 hours
MTBF
2,142 ÷ 3 = 714 hours
Repair times: 2.5h, 4.0h, 3.5h
Total = 10 hours
Availability
714 ÷ (714 + 3.33) = 99.5%
Two Assets, Same Availability, Different Problems
Availability alone can hide very different underlying situations. Two assets can land on the same headline number while needing completely opposite fixes — which is exactly why MTBF and MTTR need to be read together, not as a single combined score.
Asset A — Rare but Severe
MTBF1,800h
MTTR36h
Fix: reduce MTTR — parts staging, clearer repair procedures, faster escalation
Asset B — Frequent but Quick
MTBF88h
MTTR1.8h
Fix: reduce failure frequency — root cause analysis, condition monitoring, better PM
Both land near 98% availability. The maintenance strategy that fixes one would do nothing for the other.
Reading availability without breaking it back into MTBF and MTTR would have missed this distinction entirely.
Is Your Result Actually Good?
A raw MTBF or MTTR number means little on its own — what matters is where it sits against your asset's criticality and industry norms. World-class organisations often push availability above 99% on their most critical equipment, but that target isn't realistic or necessary for every asset in the plant. An MTTR above 4 hours on a critical line is generally treated as a red flag worth investigating; the same figure on a non-critical asset may be entirely acceptable.
Availability
99%+ world-class, 90-95% common for well-managed assets
MTTR on critical assets
Under 4 hours is a common target; above signals a red flag
MTBF trend
The direction matters more than the absolute number — rising is good
Where Manual Calculation Breaks Down
The maths itself is simple — the difficulty is keeping the underlying data clean. Should a 12-minute stoppage an operator clears without maintenance count as a failure? Does wait time for parts belong in MTTR, or only hands-on repair time? Answered inconsistently across a spreadsheet, these small judgement calls quietly corrupt the numbers leadership relies on. Book a free demo to see consistent KPI tracking that removes the guesswork.
These aren't edge cases — they're the normal, day-to-day questions any real dataset throws up.
Inconsistent failure definition
Counting minor stoppages sometimes but not others makes results incomparable month to month
Mixing MTTR with total downtime
Repair time and wait-for-parts time are different measures — blending them understates the real gap
Excluding planned maintenance incorrectly
Scheduled PM shouldn't count as a failure, but forgetting to exclude it inflates failure counts
Too short a data window
A single month rarely has enough failures for MTBF to be statistically meaningful
None of these mistakes are obvious from the final number alone — they only show up when the underlying assumptions get checked. Sign up free and apply one consistent definition across every asset from day one.
Stop Recalculating MTBF and MTTR by Hand
See how OxMaint calculates reliability KPIs automatically from your existing work order history, updated every time a job closes.
Expert Perspective: Reading MTBF and MTTR Together
MTBF and MTTR answer different questions, and reading either one alone gives an incomplete picture. High MTBF with high MTTR describes equipment that rarely fails but becomes a crisis when it does. Low MTBF with low MTTR describes a team that's become excellent at firefighting — which looks fine on paper but signals a reactive culture with no time for proactive work. The combination is what actually tells you where to focus.
Improve MTBF to Fail Less Often
Root cause analysis and condition monitoring shift failures further apart rather than just responding faster.
Improve MTTR to Recover Faster
Parts staging, clear SOPs and technician training cut the time between failure and running again.
Define "Failure" Consistently
Agree in advance what counts as a failure and what counts toward repair time, or the numbers won't be comparable over time.
Neither metric alone tells the full story — the fix that helps one asset can be irrelevant to another.
Tracking These KPIs Without the Manual Work
Once MTBF and MTTR are calculated correctly, the real value comes from tracking them consistently over time — a single snapshot tells you where you are, but the trend tells you whether maintenance strategy is actually working. Sign up free and connect your first asset's history to see these KPIs calculate themselves going forward.
A single MTBF or MTTR reading tells you where an asset stands today; three or four consecutive readings tell you whether your maintenance strategy is actually working. Rising MTBF alongside falling MTTR is the pattern worth aiming for — it means failures are becoming both rarer and faster to resolve.
Getting the Most From These Numbers
Start by calculating MTBF, MTTR and availability for your most critical assets first — these are the ones where a red flag actually changes what you do next. Track them monthly rather than once, since a single data point can't show whether reliability is trending up or down. Book a free demo to see these KPIs tracked automatically for every asset in your plant.
The formulas work equally well by hand or automatically — what matters most is applying them the same way every time.
Agree a written definition of what counts as a failure
Decide whether MTTR includes wait time or only hands-on repair
Exclude planned maintenance from your failure count
Use at least a full quarter of data — a single month rarely has enough failures
Frequently Asked Questions
What's the difference between MTTR and MTTF?
MTTR (Mean Time To Repair) applies to repairable equipment and measures how long it takes to fix something after it fails. MTTF (Mean Time To Failure) applies to non-repairable items and measures how long something lasts before it's replaced entirely. If your asset can be repaired and returned to service, MTTR is the correct metric to track.
Does MTTR include waiting time for parts, or only hands-on repair?
This depends on which definition your organisation uses. Some teams track only active repair time (a narrower measure sometimes called Mean Time To Repair in the strictest sense), while others use Mean Down Time, which includes detection, diagnosis, parts wait, repair and testing. Whichever definition you choose, apply it consistently — mixing the two produces numbers that look better or worse than reality without any real change in performance.
What counts as a "failure" for MTBF calculations?
Most organisations define a failure as any stoppage requiring maintenance intervention, excluding planned preventive maintenance. A minor stoppage an operator clears without calling maintenance is often excluded, though this should be a documented policy decision rather than an inconsistent judgement call made differently each time — inconsistent definitions are one of the most common sources of unreliable MTBF data.
Can I calculate MTBF and MTTR from a spreadsheet, or do I need a CMMS?
The formulas work fine on a spreadsheet with accurate uptime, downtime and failure count data. The challenge is usually data quality and consistency over time, not the maths itself — a CMMS helps by capturing failure and repair times automatically as work orders are logged and closed, removing the manual data entry that's the most common source of error.
How does OxMaint calculate these KPIs automatically?
OxMaint calculates MTBF, MTTR and availability directly from your work order history — every time a corrective work order is created and closed, the underlying data feeds the calculation automatically. This removes the manual spreadsheet work and keeps the numbers current without anyone needing to recalculate them by hand each month.
Let Reliability KPIs Calculate Themselves
Connect your work order history and watch MTBF, MTTR and availability update automatically. See it with your own assets in a free 30-minute walkthrough.
