To calculate MTTR (Mean Time to Repair), divide the total repair time across all incidents by the number of incidents in a given period. For example, if your team spent 12 hours repairing equipment across four breakdowns in a month, your MTTR is 3 hours. The lower the number, the faster your team restores equipment to operation.
MTTR is one of the most closely watched reliability metrics in industrial manufacturing because it directly reflects how quickly field technicians can diagnose, fix, and verify a repair. It sits alongside MTBF (Mean Time Between Failures) as a foundational measure of asset health and service performance. The sections below unpack what MTTR actually includes, how to benchmark it, and what drives it down in practice.
What does MTTR actually measure?
MTTR measures the average time it takes to restore a piece of equipment to full working order after a failure. It captures the entire repair window, from the moment a fault is detected to the moment the asset is confirmed operational again. It is not just the time a technician spends turning wrenches; it includes detection, dispatch, diagnosis, and verification.
In manufacturing environments, MTTR is particularly meaningful because every hour of equipment downtime cascades through production schedules, SLA commitments, and customer contracts. A low MTTR signals that your team has the right information, the right parts, and the right processes in place to respond quickly. A high MTTR usually points to delays in one or more of those areas, not necessarily to slow technicians.
MTTR is also closely related to MTBF. While MTBF tells you how often equipment fails, MTTR tells you how long each failure costs you. Together, they give a complete picture of asset reliability and the true cost of unplanned downtime.
What is the MTTR formula?
The MTTR formula is straightforward:
MTTR = Total Repair Time / Number of Repairs
Apply it over a defined period, such as a calendar month or a quarter, and across a defined asset group. For example, if five chillers experienced breakdowns in a quarter and the combined repair time across all five incidents was 20 hours, your MTTR is 4 hours per incident.
A few practical notes on applying the formula correctly:
- Use consistent time boundaries. Decide whether you measure from fault detection or from the moment a work order is opened, and stick to that definition across all incidents.
- Exclude planned maintenance. MTTR applies to unplanned failures, not scheduled PM work orders.
- Track at the asset-type level. An MTTR of 6 hours for a boiler and 1.5 hours for a split system are both useful; averaging them together loses the insight.
- Record repair completion, not technician departure. An asset is repaired when it passes a functional check, not when the technician leaves the site.
What counts as ‘repair time’ in an MTTR calculation?
Repair time in an MTTR calculation covers the full elapsed time from failure detection to confirmed restoration. That means it includes time spent waiting for a technician to be dispatched, travel time to the site, diagnostic work, parts sourcing, the physical repair itself, and any post-repair verification or leak checks required before the asset is signed off.
This is where many manufacturing teams undercount their true MTTR. They measure only the active wrench time and miss the delays that inflate the real number:
- Detection lag: Time between when a fault occurs and when it is reported or flagged in the system.
- Dispatch delay: Time between fault notification and a technician being assigned and en route.
- Diagnostic time: Time spent identifying the root cause, especially when asset history or documentation is not immediately available.
- Parts wait time: Time lost when a technician arrives on site and discovers a required component is not in stock.
- Verification time: Time to run functional checks, refrigerant recovery procedures, or EPA 608 / F-gas compliance sign-offs before the asset is cleared.
Including all of these components gives you an honest MTTR figure and, more importantly, shows you exactly where time is being lost so you can target improvements.
What is a good MTTR benchmark for manufacturing?
A good MTTR benchmark for industrial manufacturing varies by asset type and criticality, but most operations teams target an MTTR under four hours for mission-critical process equipment. For less critical assets, an MTTR of eight hours or less is commonly considered acceptable. The right benchmark for your operation depends on your SLA commitments, production schedules, and the cost of downtime per asset.
Context matters significantly here. A chiller or RTU supporting a cleanroom or cold storage environment carries a much lower tolerance for downtime than general facility equipment. For those assets, teams often target MTTR under two hours because the cost of extended failure, whether product loss or regulatory non-compliance, is disproportionately high.
It is also worth benchmarking MTTR alongside MTBF. An operation with a high MTBF (failures are rare) can tolerate a slightly higher MTTR. An operation with a low MTBF (failures are frequent) must drive MTTR down aggressively to protect production throughput. The relationship between the two metrics tells you whether your reliability problem is a prevention problem or a response problem.
How can field service teams reduce their MTTR?
Field service teams reduce MTTR by attacking the delays that inflate repair time before, during, and after a technician reaches the asset. The biggest gains typically come from faster fault detection, better information access at the point of repair, and smarter dispatch planning, not from pushing technicians to work faster.
The following actions have the most consistent impact on MTTR reduction in manufacturing environments:
- Give technicians offline access to full asset documentation. Diagnostic time spikes when a technician has to call back to the office for a wiring diagram or service history. Mobile apps that store asset records, previous work orders, and PM checklists locally, without requiring a network connection, cut diagnostic time significantly on factory floors and in mechanical rooms where connectivity is unreliable.
- Match the right technician to the work order at dispatch. Sending a generalist to a complex VRF system adds diagnostic time that a specialist would avoid. Skills-based scheduling that accounts for asset type, certification level (EPA 608, F-gas), and parts inventory reduces both MTTR and repeat visits.
- Digitize work order checklists by asset type. Structured digital checklists for each asset type, boiler, chiller, RTU, industrial refrigeration unit, guide technicians through the diagnostic sequence and ensure no verification step is skipped before sign-off.
- Integrate your FSM platform with your ERP. Parts availability data, asset warranty status, and service history should be visible to both dispatchers and technicians in real time. When that data lives in a separate system, delays compound at every handoff.
- Track MTTR by asset type, not just in aggregate. Aggregate MTTR hides the assets that are driving your average up. Tracking at the asset-type level reveals where to focus preventive maintenance investment and where technician training gaps exist.
How Gomocha Helps You Reduce MTTR
Unplanned equipment downtime is the most expensive problem in industrial manufacturing, and a high MTTR is often the symptom of information gaps, dispatch inefficiencies, and disconnected systems rather than technician capability. That is exactly where we built Gomocha to make a difference.
Our field service platform is purpose-built for asset-heavy industrial operations. Here is what that means in practice for MTTR:
- Offline-capable mobile app: Technicians access full asset history, service documentation, and digital checklists on the plant floor with or without a network connection, cutting diagnostic time and eliminating return visits caused by missing information. Teams using Gomocha have improved first-time fix rates by up to 19%.
- Skills-based dispatch planning: Work orders are matched to technicians based on certification, asset expertise, and parts availability, so the right person arrives with the right information the first time.
- No-code Workflow Designer: Operations teams configure PM checklists and repair workflows by asset type, including refrigerant tracking and leak check forms, without waiting on IT. Adapt processes as equipment or regulations change.
- Guaranteed ERP integration: Native integrations with AFAS and Microsoft Dynamics, plus connectors for SAP and JDE, ensure asset data, parts inventory, and work order history are always in sync across your systems.
Across our industrial manufacturing customers, teams using Gomocha have reduced unplanned equipment downtime by up to 41%. If you want to see where your operation is losing time, start with our Efficiency Assessment to identify the specific gaps in your current field service process.
Request your Efficiency Assessment and find out where your MTTR is being inflated and what it is costing you.
Frequently Asked Questions
How is MTTR different from MTBF, and should I be tracking both?
Yes, you should track both — they answer different questions. MTBF (Mean Time Between Failures) tells you how often your equipment fails, while MTTR tells you how long each failure costs you in downtime. Together, they reveal whether your reliability problem is a prevention issue (low MTBF) or a response issue (high MTTR), which points you toward very different solutions — whether that’s investing in preventive maintenance programs or improving dispatch and diagnostic processes.
What's the most common mistake teams make when calculating MTTR?
The most common mistake is measuring only active wrench time and ignoring the surrounding delays — detection lag, dispatch time, parts wait, and post-repair verification. This produces an artificially low MTTR that masks where time is actually being lost. To get an accurate and actionable number, always measure from the moment a fault is detected to the moment the asset passes its functional verification check, not just the time a technician is physically on the job.
How often should we recalculate and review our MTTR?
For most industrial manufacturing operations, a monthly review cadence is the right starting point — it gives you enough incidents to spot trends without letting problems compound for too long. For high-criticality assets like chillers, cleanroom HVAC, or cold storage units, reviewing MTTR on a rolling 30-day basis or even weekly is worthwhile given the disproportionate cost of downtime. The key is consistency: use the same time boundaries and asset groupings every cycle so your comparisons remain meaningful.
Can MTTR be improved without investing in new software or tools?
Yes, meaningful MTTR reductions are achievable through process changes alone. Start by standardizing how faults are detected and reported so detection lag is minimized, then audit your dispatch process to ensure technicians are matched to work orders based on skills and parts availability rather than just proximity or availability. Documenting asset-specific diagnostic checklists — even in paper or spreadsheet form — also reduces diagnostic time significantly. That said, these manual improvements tend to hit a ceiling quickly, and digital tools that put asset history and checklists in a technician’s hands at the point of repair typically unlock the next level of gains.
How do parts availability and inventory management affect MTTR?
Parts wait time is one of the single largest contributors to inflated MTTR, and it’s often invisible until you start tracking repair time in detail. When a technician arrives on site only to discover a required component isn’t in stock, the entire repair window stalls while a part is sourced or shipped. Integrating your field service management platform with your ERP or inventory system so technicians and dispatchers can see real-time parts availability before a work order is assigned is one of the highest-ROI changes an operation can make to drive MTTR down.
Is a lower MTTR always better, or are there trade-offs to consider?
A lower MTTR is almost always desirable, but pursuing it without context can lead to trade-offs. For example, rushing through post-repair verification to close a work order faster can result in repeat failures that ultimately raise your MTTR over time. Similarly, over-investing in MTTR reduction for low-criticality assets may not justify the cost. The right approach is to prioritize MTTR improvement on assets where downtime is most expensive — those tied to production throughput, SLA commitments, or regulatory compliance — and set realistic benchmarks based on asset criticality rather than chasing a single organization-wide number.
How do I get started tracking MTTR if my team isn't measuring it at all today?
Start simple: define your time boundaries (fault detection to confirmed restoration), identify the asset group you want to track first — ideally your most critical equipment — and begin logging repair start and end times on every unplanned work order. Even a basic spreadsheet will surface patterns within one or two months. Once you have a baseline, you can identify which phase of the repair window (detection, dispatch, diagnosis, parts, or verification) is driving your average up and prioritize improvements from there. The goal in the first 90 days is a reliable baseline, not a perfect number.