Unplanned equipment failures cost industrial manufacturers an estimated 5–20% of productive capacity — and most of that loss is preventable with better reliability data. MTBF (Mean Time Between Failures) is the foundational metric that makes that prevention possible. To calculate MTBF, divide the total operational time of an asset by the number of failures that occurred during that period. For example, if a machine ran for 1,000 hours and failed four times, its MTBF is 250 hours. This single formula gives maintenance and field service teams a reliable baseline for predicting equipment reliability.
MTBF is most useful when applied consistently across comparable assets and time periods. For industrial manufacturers managing complex, high-value equipment, it is a foundational metric that connects directly to uptime targets, preventive maintenance scheduling, and service contract performance.
The sections below walk through exactly how to apply the formula, what data you need, how MTBF compares to related metrics, and how field service teams can put it to work on the plant floor.
What does MTBF actually measure?
MTBF (Mean Time Between Failures) measures the average operating time between one failure and the next for a repairable asset. It is a reliability metric that tells you how long a piece of equipment is expected to run before it fails again. A higher MTBF means greater reliability; a lower MTBF signals a pattern of frequent failures that warrants investigation.
It is important to understand what MTBF does not measure. MTBF does not capture repair time, and it only applies to assets that are repaired and returned to service after each failure. It also represents an average, meaning individual failure intervals will vary around that number. Two machines with identical MTBF values can have very different failure patterns in practice.
For operations teams in industrial manufacturing, MTBF is most valuable as a trending metric. Tracking MTBF over time reveals whether reliability is improving or degrading, which directly informs decisions about preventive maintenance (PM) intervals, spare parts stocking, and technician scheduling.
What is the MTBF formula and how do you apply it?
MTBF = Total Operational Time ÷ Number of Failures. Total operational time is the cumulative time the asset was actually running and available for use, excluding any time it was down for repairs or scheduled maintenance. The number of failures is the count of unplanned breakdowns within that same period.
Here is how to apply the MTBF formula step by step:
- Define the measurement window. Choose a consistent time period, such as a calendar quarter or a full year, to make comparisons meaningful.
- Record total run time. Sum the hours the asset was operational and available. Exclude planned downtime and repair windows.
- Count confirmed failures. Log only unplanned failures that caused the asset to stop functioning. Exclude scheduled PM events.
- Divide and record. Apply the formula and log the result against the asset ID and time period.
- Repeat consistently. MTBF becomes actionable only when tracked over multiple periods so trends become visible.
For example: a process cooling unit ran for 2,200 hours over six months and experienced five unplanned failures. MTBF = 2,200 / 5 = 440 hours. If the same unit delivered an MTBF of 620 hours the previous six months, that downward trend is a clear signal to review the PM schedule or inspect for wear.
What data do you need to calculate MTBF accurately?
Accurate MTBF calculation depends on three categories of data: operational run time, failure events, and asset identity. Without clean records across all three, the resulting number is unreliable and can lead to poor maintenance decisions.
The core data requirements are:
- Asset run hours: Logged automatically via sensors, BAS integration, or technician-recorded start and stop times on each work order.
- Failure timestamps: The exact time an asset failed, not when the work order was opened. The gap between these two matters for accuracy.
- Failure classification: A clear distinction between unplanned failures and planned PM events. Mixing these corrupts the calculation.
- Asset ID consistency: Every data point must be tied to a specific asset, not a location or a general equipment category.
- Work order history: Completed work orders are the most reliable source of failure data when they capture failure cause, repair action, and return-to-service time.
The most common source of MTBF error in manufacturing environments is incomplete work order data. When field technicians close work orders without recording failure codes or actual repair times, the data set becomes too thin to support reliable reliability analysis. Digital work order capture — completed on the plant floor at the time of the repair — is the single biggest lever for improving MTBF data quality.
What is the difference between MTBF, MTTR, and MTTF?
MTBF, MTTR, and MTTF are three related but distinct reliability metrics used in maintenance and field service operations. MTBF (Mean Time Between Failures) measures average time between failures for repairable assets. MTTR (Mean Time To Repair) measures how long it takes to restore an asset after a failure. MTTF (Mean Time To Failure) measures the average lifespan of non-repairable assets before they fail permanently. Using the wrong metric for a given asset type produces misleading data and poor maintenance decisions.
MTBF vs. MTTF: which applies to your asset?
MTBF applies to equipment that is repaired and returned to service repeatedly — chillers, RTUs, compressors, and production line machinery are typical examples. MTTF applies to components that are replaced rather than repaired, such as bearings, seals, or circuit boards. Applying MTBF logic to a non-repairable component produces a meaningless number and can lead to incorrect PM scheduling.
MTBF vs. MTTR: how the two metrics work together
MTBF and MTTR measure different dimensions of the same problem. MTBF tells you how often failures happen; MTTR tells you how long each failure costs you in downtime. A high MTBF is ideal because failures are infrequent. A low MTTR is also ideal because when failures do occur, they are resolved quickly. Together, MTBF and MTTR feed into overall equipment effectiveness (OEE) calculations and SLA compliance tracking. For field service managers, reducing MTTR is often the faster operational win because it depends on technician readiness and parts availability — both of which are directly controllable through better dispatch and work order management.
How should field service teams use MTBF to reduce downtime?
Field service teams should use MTBF as an active input to PM scheduling, not just as a back-office reporting metric. When MTBF data is current and asset-specific, it allows teams to schedule preventive maintenance before the next predicted failure window rather than reacting after the fact. This shift from reactive to predictive service is where MTBF delivers its highest operational value.
Practical applications for field service teams include:
- Adjusting PM intervals by asset: If a specific chiller model consistently shows an MTBF of 300 hours but the PM schedule runs every 500 hours, that gap is a recurring source of unplanned downtime. Tighten the interval to match the reliability data.
- Prioritizing dispatch for high-risk assets: Assets with declining MTBF trends should be flagged for earlier inspection. Scheduling tools that surface this data help dispatchers assign the right technician before a failure occurs.
- Stocking parts to match failure patterns: MTBF data by failure type tells inventory managers which components fail most frequently on which asset classes, reducing first-visit delays caused by missing parts.
- Benchmarking technician performance: Comparing MTBF before and after a PM visit reveals whether the maintenance work is actually extending asset reliability or just closing the work order.
The limiting factor for most manufacturing service teams is data accessibility on the plant floor. Technicians who cannot pull up asset history, previous failure codes, and PM records at the point of service are working blind. Offline access to full asset documentation is what bridges the gap between MTBF as a back-office metric and MTBF as a live decision-making tool for the technician standing in front of the equipment.
How Gomocha helps you act on MTBF data across your entire asset base
Calculating MTBF is straightforward. Acting on it consistently — across dozens of assets and a distributed field team — is where most manufacturing service operations fall short. Incomplete work order data, disconnected systems, and technicians without plant-floor access to asset history all degrade the reliability of MTBF tracking before the metric can drive a single maintenance decision. That is the operational gap we built our field service platform to close.
Here is what that looks like in practice for industrial manufacturing teams:
- Offline-capable mobile app: Technicians access full asset history, failure codes, and PM checklists directly on the plant floor, with or without connectivity. This is what makes work order data complete enough to support reliable MTBF tracking — and it is why teams using our platform have improved first-time fix rates by up to 19%.
- No-code Workflow Designer: Ops teams configure PM checklists and failure classification forms by asset type without waiting on IT. When the form captures the right data, every work order feeds clean inputs into your reliability calculations.
- Purpose-built for asset-heavy operations: We are designed for organizations dispatching technicians to complex, high-value assets. Across 13 customers and 177,484 work orders, manufacturing service teams using our platform have reduced unplanned downtime by up to 41%.
- Guaranteed ERP integration: Native integrations with AFAS and Microsoft Dynamics, plus SAP and JDE via connectors, mean asset data and work order records stay synchronized across systems rather than living in silos.
If unplanned equipment failures are eating into your production schedule and you want to understand where the inefficiency is actually coming from, start with our Efficiency Assessment. It is a low-friction way to map your current field service operation against what is possible, and it gives you a concrete starting point for improving reliability metrics like MTBF across your asset base.
Frequently Asked Questions
How many data points do I need before my MTBF calculation is statistically meaningful?
As a general rule, you need a minimum of five to ten failure events per asset before MTBF becomes a reliable indicator. With fewer failures, a single outlier event can skew the average significantly and lead to poor maintenance decisions. For newer assets or low-failure equipment, consider pooling data across identical asset models to build a more statistically robust baseline before making PM schedule changes based on MTBF alone.
What is a 'good' MTBF value, and how do I know if mine needs improvement?
There is no universal benchmark for a good MTBF because it varies widely by asset type, operating environment, and industry. The most practical approach is to compare MTBF against your own historical baseline for each specific asset, against manufacturer specifications, and against identical assets operating under similar conditions. A declining MTBF trend over consecutive measurement periods is always a signal worth investigating, regardless of the absolute number.
Can I calculate MTBF if my team still uses paper-based work orders?
Yes, but it requires significant manual effort and introduces a higher risk of data gaps and errors. You would need to manually extract run hours, failure timestamps, and failure classifications from paper records and enter them into a spreadsheet for calculation. The bigger risk with paper-based systems is incomplete data — missed failure codes, estimated rather than actual timestamps, and inconsistent asset identification — all of which directly undermine the accuracy of your MTBF output. Digitizing work order capture is the most impactful step you can take to improve data quality.
How does planned downtime for scheduled maintenance affect my MTBF calculation?
Planned downtime should always be excluded from your total operational time when calculating MTBF. Including it artificially inflates the denominator and produces a misleadingly high MTBF value. Only the hours an asset was actively running and available for production count as operational time. This is why consistent failure classification — clearly distinguishing unplanned failures from scheduled PM events in every work order — is a non-negotiable data quality requirement.
What is the most common mistake teams make when first implementing MTBF tracking?
The most common mistake is calculating MTBF at a location or equipment category level rather than at the individual asset level. For example, tracking MTBF for ‘all chillers on Floor 2’ rather than for each specific chiller unit masks the performance differences between individual assets and makes it impossible to identify which specific machine is driving downtime. Always tie every data point to a unique asset ID to ensure your reliability metrics are actionable at the asset level.
How do I use MTBF to make the case for capital equipment replacement?
A consistently declining MTBF trend over multiple measurement periods, combined with rising MTTR and repair costs, builds a compelling data-driven case for asset replacement. Calculate the total cost of ownership for the failing asset — including parts, labor hours, and lost production time per failure cycle — and compare it against the annualized cost of a replacement. When the cost-per-operating-hour of keeping an aging asset running exceeds the cost of replacement, MTBF data gives maintenance and finance teams a shared, objective basis for that capital decision.
How often should I recalculate and review MTBF for my assets?
For most industrial manufacturing environments, a quarterly review cadence strikes the right balance between responsiveness and statistical stability. Reviewing too frequently — such as monthly on low-failure assets — can cause teams to overreact to normal statistical variation. However, for critical assets where a single failure causes significant production loss, a rolling 90-day MTBF calculation reviewed monthly gives teams an earlier warning of degrading reliability trends before they result in unplanned downtime.