MTBF (Mean Time Between Failures) and MTTR (Mean Time To Repair) measure opposite ends of the same reliability equation. MTBF tells you how long equipment runs before it fails; MTTR tells you how long it takes to restore it after it does. Together, they define the true availability of any industrial asset.
For manufacturing operations where unplanned downtime can cascade through production schedules and SLA commitments within minutes, understanding both metrics is not optional. This article breaks down how each is calculated, why they must be managed together, and how field service teams use them to keep critical equipment running.
What do MTBF and MTTR actually measure?
MTBF measures the average operating time between one failure and the next on a repairable asset. MTTR measures the average time required to diagnose, repair, and return that same asset to service. MTBF reflects how reliable a piece of equipment is; MTTR reflects how effective your maintenance and field service operation is at responding when reliability breaks down.
Think of MTBF as the asset’s track record and MTTR as your team’s response capability. A chiller with a high MTBF fails infrequently, which is ideal. But if your MTTR is high when it does fail, the operational damage can be just as severe as if failures happened twice as often.
Both metrics apply directly to asset-heavy industrial environments: process cooling systems, RTUs, boilers, VRF systems, and any mission-critical equipment where failure interrupts production or violates compliance requirements. Neither number means much in isolation.
How is MTBF calculated versus MTTR?
MTBF is calculated by dividing total uptime by the number of failures in a given period. MTTR is calculated by dividing total repair time by the number of repair events in the same period. Both formulas are straightforward, but the quality of the inputs determines whether the results are actionable.
Calculating MTBF
The formula is: MTBF = Total Uptime / Number of Failures
If a piece of industrial refrigeration equipment ran for 4,200 hours across a year and failed three times, the MTBF is 1,400 hours. That figure becomes a planning baseline for PM scheduling and parts stocking. The challenge is that “total uptime” must exclude planned maintenance windows, which are not failures.
Calculating MTTR
The formula is: MTTR = Total Repair Time / Number of Repairs
If those same three failures took a combined 18 hours to resolve, the MTTR is 6 hours per incident. MTTR includes everything from the moment failure is detected to the moment the asset is confirmed back in service: diagnosis time, parts sourcing, travel, repair, and verification. Operations teams that track only wrench time consistently underestimate their true MTTR.
Why can’t you optimize one without the other?
Optimizing MTBF without addressing MTTR creates a false sense of security. Optimizing MTTR without improving MTBF means you are getting faster at fixing problems that should not be occurring as frequently. Asset availability, which is what production schedules actually depend on, is a function of both metrics simultaneously.
The relationship is captured in the availability formula: Availability = MTBF / (MTBF + MTTR)
A system with a 500-hour MTBF and a 10-hour MTTR runs at roughly 98% availability. If MTTR doubles to 20 hours without any change in failure frequency, availability drops to 96%. In a continuous production environment, that 2-point difference can translate to significant lost output over a year.
This is why manufacturing field service teams increasingly track both metrics together rather than reporting them in separate silos. A PM program that extends MTBF is only as valuable as the dispatch and diagnostic capability that keeps MTTR low when failures still occur.
What’s a good MTBF or MTTR benchmark for industrial equipment?
There is no universal benchmark because acceptable MTBF and MTTR values depend heavily on asset criticality, industry sector, and the cost of downtime in your specific operation. That said, directional benchmarks exist for common asset categories and can anchor realistic target-setting.
- Process cooling and chillers: Leading operators target MTBFs measured in thousands of operating hours between unplanned failures, with MTTR under four hours for critical assets.
- RTUs and HVAC in manufacturing facilities: Industry experience suggests MTTR targets of two to six hours, depending on parts availability and technician proximity.
- Mission-critical data center cooling: Uptime Institute research indicates that cooling-related failures can cost approximately $9,000 per minute across the sector, making sub-two-hour MTTR a hard operational requirement rather than a stretch goal.
- General industrial machinery: Operations with mature PM programs typically achieve MTBF improvements of 15 to 30% within the first year of structured preventive maintenance, compared to reactive-only approaches.
The most useful benchmark is your own historical data, trended over time. If MTBF is decreasing quarter over quarter on a specific asset class, that signals deterioration in asset health or inadequate PM frequency. If MTTR is increasing, it typically points to skills gaps, parts availability issues, or diagnostic inefficiency in the field.
How do field service teams use MTBF and MTTR to reduce downtime?
Field service teams use MTBF data to schedule preventive maintenance before failure probability spikes, and MTTR data to identify where diagnostic speed, parts access, or technician skills are creating repair delays. Together, the two metrics turn reactive firefighting into a structured, data-driven maintenance operation.
In practice, this means connecting work order history to asset records so that every completed repair feeds back into MTBF and MTTR calculations automatically. Technicians who can access full asset history, previous repair notes, and PM checklists on the plant floor, including in areas without connectivity, diagnose faster and fix correctly the first time. Industry experience shows that offline access to complete asset documentation drives meaningful improvement in first-time fix rates, which directly compresses MTTR.
Structured PM workflows tied to MTBF data also shift maintenance from calendar-based to condition-informed. Instead of servicing a boiler every 90 days regardless of operating hours, teams can align PM intervals with actual failure patterns observed in the MTBF data for that asset class.
- Capture complete work order data: Every repair event, including diagnosis time, travel time, and parts used, must be recorded to produce reliable MTTR calculations.
- Link failures to asset records: Failure events tied to specific assets and asset ages reveal which equipment is approaching end of useful life and where MTBF is declining.
- Use MTBF to drive PM scheduling: Set preventive maintenance intervals based on observed failure patterns, not generic manufacturer recommendations alone.
- Identify MTTR outliers: Work orders that significantly exceed average MTTR point to training gaps, parts stocking issues, or dispatch inefficiencies worth addressing systematically.
- Review both metrics together at a cadence: Monthly or quarterly reviews of MTBF and MTTR trends give operations leaders an early warning system before downtime costs escalate.
How Gomocha Helps Reduce Downtime Through MTBF and MTTR Visibility
Tracking MTBF and MTTR is only as useful as the data feeding those calculations. If work orders are paper-based, incomplete, or disconnected from asset records, the metrics become unreliable and the decisions built on them suffer accordingly. That is the operational gap we built Gomocha to close.
Our field service platform connects every work order to the asset it touches, capturing diagnosis time, repair time, and outcome data automatically. Technicians access full asset history, EPA 608-compliant refrigerant tracking forms, and PM checklists directly on their mobile device, whether they are on a factory floor, in a mechanical room, or at a remote site with no signal. The platform works fully offline and syncs when connectivity returns, so MTTR is never extended because a technician could not access the documentation they needed.
Specific capabilities that directly support MTBF and MTTR improvement include:
- Offline-capable mobile app: Full asset history and work order access without connectivity, reducing diagnostic time and repeat visits
- No-code Workflow Designer: Ops teams configure PM checklists per asset type and failure category without waiting on IT
- Native ERP integration: Work order data flows directly into AFAS, Microsoft Dynamics, SAP, and JDE, keeping asset records current without manual entry
- Purpose-built for asset-heavy industrial operations: Across 177,484 work orders, manufacturing service teams using Gomocha have reduced downtime by up to 41% and improved first-time fix rates by up to 19%
If unplanned equipment failure is compressing your margins and your current FSM tool was not designed for the plant floor, the right starting point is understanding where your operation is losing time. Request an Efficiency Assessment and we will identify the specific gaps in your MTBF and MTTR data that are costing you the most.
Frequently Asked Questions
How often should we recalculate MTBF and MTTR for our assets?
For most industrial operations, a monthly calculation cycle is the minimum cadence needed to catch meaningful trends before they become costly problems. High-criticality assets — chillers, boilers, or process cooling systems tied directly to production — warrant more frequent review, ideally after every failure event. The key is consistency: calculating on the same interval with the same data inputs ensures that trend lines reflect real operational changes rather than measurement artifacts.
What's the most common mistake teams make when tracking MTTR?
The most widespread mistake is measuring only wrench time — the hands-on repair window — rather than the full failure-to-restoration cycle. True MTTR must include fault detection time, technician dispatch and travel, parts sourcing delays, and post-repair verification. Underreporting MTTR by excluding these phases creates an artificially optimistic picture that masks the real cost of downtime and hides the most actionable improvement opportunities, such as parts stocking strategies or dispatch routing.
Can MTBF and MTTR be applied to newer assets, or do you need years of historical data first?
You can begin tracking both metrics from the first failure event, even on new assets. Early data will have wider statistical variance and should be interpreted cautiously, but it still establishes a baseline and starts surfacing patterns. For newly installed equipment, manufacturer reliability data and industry benchmarks can serve as provisional targets while your own operational history accumulates. The goal is to replace those external benchmarks with your own asset-specific data as quickly as possible.
How do parts availability and supply chain issues affect MTTR, and what can teams do about it?
Parts sourcing delays are one of the largest and most controllable contributors to extended MTTR. When a technician arrives on-site but cannot complete the repair because a critical component is unavailable, every hour waiting is added directly to your MTTR calculation. The practical fix is to use MTBF data to identify which components fail most frequently on your highest-criticality assets, then stock those parts strategically — either on service vehicles or at nearby staging locations. Reviewing MTTR outliers in your work order history will typically reveal a short list of parts responsible for a disproportionate share of repair delays.
What's the difference between MTTR and MTRS, and does it matter for industrial operations?
MTTR (Mean Time To Repair) specifically measures active repair work, while MTRS (Mean Time To Restore Service) encompasses the entire outage window from failure detection through confirmed return to full operation. In practice, many industrial teams use the terms interchangeably, but the distinction matters when reporting to operations leadership or comparing against SLA commitments, which are almost always tied to restoration time rather than repair time alone. For the purposes of availability calculations, MTRS is the more accurate input because it reflects the actual production impact of each failure event.
How do preventive maintenance programs interact with MTBF — does more frequent PM always improve it?
Not necessarily. Over-maintaining an asset can introduce failure risk through unnecessary component disturbance, and it consumes technician time that could be directed at higher-priority work. The goal is to align PM intervals with the actual failure patterns observed in your MTBF data, not to maximize maintenance frequency. If your MTBF data shows a specific asset class failing around 1,200 operating hours, scheduling PM at 900 hours provides a meaningful buffer — but scheduling it at 400 hours delivers diminishing returns and increases labor cost without proportional reliability gains.
At what point does declining MTBF signal that an asset should be replaced rather than repaired?
When MTBF for a specific asset is declining consistently across multiple measurement periods and MTTR is simultaneously increasing — often because aging components are harder to source or diagnose — the total cost of ownership calculation typically shifts in favor of replacement. A useful rule of thumb is to flag assets where the annualized repair and downtime cost exceeds 40–60% of replacement cost, though the exact threshold depends on asset criticality and capital budget constraints. MTBF trend data is the clearest early indicator that an asset is entering the end-of-life phase of its reliability curve.