Calculate Mean Time To Repair by dividing total repair hours by number of repairs. Track maintenance efficiency and improve equipment uptime.
Mean Time To Repair (MTTR) measures the average time required to diagnose and fix a failed system and return it to operational status. Calculated by dividing total repair time by the number of repairs performed, MTTR quantifies maintenance team effectiveness and directly impacts equipment availability.
A high MTTR means extended downtime during every failure event, reducing throughput, delaying deliveries, and increasing labor costs. Reducing MTTR involves improving diagnostic tools, stocking the right spare parts, training technicians, and designing equipment for serviceability.
This calculator takes total repair hours and repair count to compute MTTR. Combined with MTBF, it calculates equipment availability. Use it to benchmark maintenance performance, set repair time targets, and justify investments in maintenance tools and training.
Tracking this metric consistently enables manufacturing teams to identify performance trends early and take corrective action before minor inefficiencies escalate into significant production losses. This measurement forms a critical foundation for capacity planning, helping teams align production capabilities with demand forecasts and strategic business objectives throughout the planning cycle.
MTTR determines how quickly you recover from breakdowns. Even with excellent MTBF, a high MTTR means long outages when failures do occur. Reducing MTTR is often the fastest path to improved availability because it requires process improvements rather than capital equipment changes. Data-driven tracking enables proactive decision-making rather than reactive problem-solving, ultimately saving time, materials, and labor costs in production operations.
MTTR = Total Repair Time / Number of Repairs Availability (%) = MTBF / (MTBF + MTTR) × 100 Downtime per Year = (Annual Failures) × MTTR
Result: 4.0 hours MTTR
With 48 total repair hours across 12 events, MTTR = 48 / 12 = 4.0 hours. Combined with MTBF of 720 hours, availability = 720 / (720 + 4) × 100 = 99.45%.
MTTR can be decomposed into four phases: detection and notification time, diagnostic time, repair execution time, and verification and restart time. Each phase offers different improvement opportunities. Often, waiting for parts or waiting for a qualified technician dominates total MTTR.
Availability is the metric management cares about most: what percentage of scheduled production time is the equipment running? Availability depends on both how often equipment fails (MTBF) and how quickly it is fixed (MTTR). Improving either metric improves availability.
The most effective long-term MTTR reduction strategy is designing equipment for easy maintenance. Quick-release panels, color-coded connectors, modular subassemblies, and built-in diagnostics all reduce repair time. Involve maintenance teams in equipment specification and selection decisions.
It depends on equipment complexity. Simple machine repairs may target under 1 hour. Complex CNC equipment might accept 4–8 hours. The key is that MTTR should be decreasing over time as maintenance processes improve.
Yes. MTTR covers the full time from failure to return to operation, including diagnosis, parts procurement, actual repair, and verification. This comprehensive measure captures all sources of downtime.
Availability = MTBF / (MTBF + MTTR). Reducing MTTR from 8 hours to 4 hours with MTBF of 200 hours improves availability from 96.2% to 98.0%, recovering nearly 2% of productive time.
MTTR measures active repair time. Mean Down Time (MDT) includes all downtime — logistics delays, administrative approval, waiting for technicians, and MTTR. MDT is always greater than or equal to MTTR.
Improve diagnostic tools, maintain spare parts inventory for critical components, create repair checklists, cross-train maintenance staff, and design equipment for modular replacement rather than in-situ repair. Sharing these results with team members or stakeholders promotes alignment and supports more informed decision-making across the organization.
At least 10–15 repair events provide a reasonable average. Fewer data points can be skewed by one unusually long or short repair. Track MTTR continuously and update the average as new data accumulates.