MTBF in Maintenance: How to Calculate It, Use It, and Improve Asset Reliability
Learn what MTBF means, how to calculate it, and how maintenance teams use it in an EAM system to improve reliability.
What you will learn in this article:
What MTBF means and when maintenance teams should use it
How to calculate MTBF using operating time and failure events
How to handle planned downtime, preventive maintenance, and edge cases
How MTBF compares to MTTR, MTTF, MTBR, and availability
How maintenance teams can use MTBF in an EAM system to improve asset reliability.
Every maintenance team has felt it: that moment when something doesn't go according to plan. In these moments, the question isn’t just “What broke” but “Why does this keep happening?”
MTBF, also known as mean time between failures, is a useful metric for tracking recurring and unplanned failures because it measures the average amount of time equipment typically runs between failures. MTBF matters because it converts event histories into a single, actionable indicator that helps you spot unreliable assets, set preventive maintenance cadences, and measure improvement over time.
For that reason, MTBF is a core reliability metric for maintenance teams. This article covers what MTBF is, how to calculate MTBF, and how to use it for more reliable operations.
What is MTBF and when should it be used?
MTBF is the average operating time between consecutive failure events for a repairable asset. It is used when an asset is expected to be repaired and returned to service after failure.
MTBF is expressed in time units, such as hours or days,. It should only be applied when failure events and operating time can be identified reliably. Therefore, MTBF should not be used for single-use or non-repairable items. For those assets, MTTF, or mean time to failure, is usually the more appropriate metric.
MTBF is most useful when maintenance and reliability teams compare assets that operate under similar conditions, or when results are normalized by asset type, duty cycle, location, or operating context. A low MTBF may indicate poor asset reliability, but it can also reflect heavier usage, harsher conditions, or inconsistent failure reporting.
How to calculate MTBF
The formula for calculating MTBF is:
MTBF = total operating time ÷ number of failures
To calculate MTBF, maintenance teams need two inputs from the same observation period:
1. Total operating time: the amount of time the asset was running or available to run.
2. Number of failures: the number of unplanned failure events that required maintenance intervention.
If maintenance teams capture runtime directly from a PLC, SCADA system, meter, or equipment counter, they should use that runtime value. If runtime is not captured directly, teams can estimate operating time by subtracting planned downtime, unplanned downtime, and out-of-service time from planned production time.
Estimated operating time = planned production time – planned downtime – unplanned downtime – out-of-service time.
Steps to calculate MTBF in practice:
1. Define what constitutes a failure (unplanned stop that requires maintenance intervention).
2. Choose the observation window (e.g., last 12 months, life-to-date).
3. Sum operating time during the window (excluding planned downtime and out-of-service periods unless you have a reason to include them).
4. Count failure events within the same window.
5. Compute MTBF: total operating time ÷ number of failures.
6. Validate the result by checking for misclassified work orders or missing runtime data.
Example using the MTBF formula:
Imagine Asset A had 5,000 planned production hours over 12 months. However, during that period, the asset had 50 hours of planned downtime and 50 hours of unplanned downtime.
To estimate operating time, subtract planned downtime and unplanned downtime from planned production time:
5,000 – 50 – 50 = 4,900 operating hours
If the asset had 4 unplanned failures recorded during the same period, the MTBF calculation is:
MTBF = 4,900 ÷ 4 = 1,225 hours
This means Asset A ran for an average of 1,225 operating hours between failures during the 12-month period.
Edge cases and notes:
If an asset has no recorded failures during the observation window, MTBF cannot be calculated as a finite number because the number of failures is zero. In this case, maintenance teams should report “no failures observed over X operating hours” or extend the observation window.
If a failure record is missing a start, stop, or restart timestamp, maintenance teams should apply a consistent data-quality rule. For example, they can use the nearest verified timestamp, exclude ambiguous events from the calculation, or flag them for review.
MTBF should also be calculated using the same failure definition, time window, and runtime source each time. Otherwise, changes in MTBF may reflect reporting differences instead of real reliability improvement.
How planned downtime and preventive maintenance affect MTBF
Maintenance teams should exclude planned downtime from operating time when calculating MTBF. Since MTBF measures time between failures, scheduled downtime should not reduce the reliability metric.
Preventive maintenance (PM) should also be treated as non-failure activity. PM-triggered stops shouldn't be counted as failures if the work is scheduled and completed without an unplanned failure event.
MTBF vs MTTR, MTTF, MTBR and availability
MTBF is one reliability metric, but maintenance teams should review it alongside other maintenance KPIs to understand asset performance.
Key takeaways:
MTBR and MTBF can overlap in practice. MTBF tracks time between failure events, while MTBR tracks time between repair events.
Maintenance teams should check how their organization defines repair events. If repairs include planned work, preventive maintenance, or non-failure repairs, MTBR should not be treated as the same metric as MTBF.
How maintenance teams use MTBF in an EAM system to improve reliability
Maintenance teams use MTBF to identify unreliable assets, prioritize reliability work, and measure wether maintenance changes are reducing failure frequency over time.
With an EAM (Enterprise Asset Management) software, MTBF tracking works best when asset runtime, failure events, and work order history are connected. Teams can use this data to:
Baseline reliability: Calculate MTBF for all critical assets over the same window.
Prioritize assets: Focus on assets with low MTBF, highcriticality, safety risk, production impact, or repair cost.
Find recurring failure patterns: Group failures by failure code, component, location, shift, operating condition, or asset type.
Trigger follow-up work: Create RCA tasks,inspection work orders, or reliability reviews when MTBF drops below target.
Improve maintenance plans: Adjust PM frequencies, move toward condition-based maintenance, improve spare parts quality, update repair procedures, train technicians, or make changes for chronic failure modes..
Measure results: Track MTBF in rolling windows to see whether reliability actions are improving performance
Improving MTBF through maintenance tactics
Once low-MTBF assets are identified, maintenance teams can use different tactics to reduce repeat failures and improve reliability. These may include adjusting PM frequencies, moving toward condition-based maintenance, improving spare parts quality, updating repair procedures, training technicians, or making design changes for chronic failure modes.
To support accurate MTBF reporting, an EAM system should capture consistent asset data, including runtime counters, criticality, failure flags, failure codes, downtime start and end times, affected components, and repair summaries. Runtime data can come from technician entries, meters, PLCs, SCADA systems, historians, or IoT sensors.
Example EAM alert rule:
Condition: Asset MTBF over the last 90 days is below target and asset criticality is high.
Action: Create a reliability review, assign it to the reliability lead, and attach recent failure work orders.
This turns MTBF from a reporting metric into a practical workflow for improving asset reliability.
Using MTBF to improve asset reliability
MTBF converts event and runtime data into a focused reliability metric that maintenance teams can use to make better decisions. When calculated consistently, and paired with MTTR and availability, it gives maintenance leaders a clear picture of which assets are failing, how often failures occur, and where reliability efforts should be focused.
With the right EAM system, maintenance teams can capture runtime data, classify failures, automate MTBF reporting, and turn reliability trends into action.
See how TAG Mobi EAM helps maintenance teams track MTBF, improve asset reliability, and make better maintenance decisions.
FAQs
How do you calculate MTBF?
Calculate MTBF by dividing total operating time by the number of failures within the observation period. Then follow these steps: confirm failure definitions, sum operating hours (exclude planned downtime), count failures, and compute the ratio. Validate results with sample work order records and use rolling windows if failures are infrequent.
What does MTBF stand for?
MTBF stands for Mean Time Between Failures. It is the average time an asset operates between unplanned failures and is expressed in time units such as hours or days.
What is MTBF maintenance?
MTBF maintenance refers to using MTBF as a maintenance KPI to guide maintenance planning, prioritization, and reliability improvement work. Teams use MTBF to identify unreliable assets, trigger root-cause analyses, and measure the effect of maintenance changes on failure frequency.
