Enter MTTR Inputs
Use summary fields, event-level durations, or both. When event durations are entered, the calculator prioritizes those values for the most granular result.
Example Data Table
This example uses six failures in a 720-hour period, with 24 planned maintenance hours. Paired event entries make the restore pattern visible beyond the average.
| Failure | Repair Hours | Delay Hours | Total Restore Hours |
|---|---|---|---|
| 1 | 3.4 | 1.0 | 4.4 |
| 2 | 4.1 | 0.5 | 4.6 |
| 3 | 2.8 | 0.8 | 3.6 |
| 4 | 5.0 | 1.4 | 6.4 |
| 5 | 3.6 | 1.0 | 4.6 |
| 6 | 4.4 | 1.3 | 5.7 |
From this dataset, total restore time is 29.3 hours and MTTR is about 4.88 hours per failure. Event statistics also reveal the slowest restore case.
Formula Used
The calculator reports both active repair MTTR and total restore MTTR, because engineering teams often track them separately.
How to Use This Calculator
Start by entering the observation period and planned maintenance hours. Add either a manual failure count with summary repair times, or paste event-level repair durations.
Include waiting or logistics delays when you want a fuller restore metric. Enter a target restore time to estimate maintainability and measure actual compliance from event data.
Submit the form to place the results block above the input area. Then export the displayed metrics with the CSV or PDF buttons.
Why These Metrics Matter
MTTR helps maintenance, operations, and reliability teams understand how quickly equipment returns to service after failure. Looking only at the average can hide important delay patterns, so this page also shows event-based distribution metrics when data is available.
Using both active repair time and full restore time supports better staffing, spares planning, response targets, and availability improvement work.
Frequently Asked Questions
1. What does MTTR mean?
MTTR means Mean Time To Repair. It is the average time needed to restore an asset after a failure event, based on the repair scope you choose.
2. Should waiting for parts be included?
Include waiting time when you want a total restore metric. Exclude it when you only want the technicians’ active repair effort. Many teams track both values together.
3. Is planned maintenance part of MTTR?
No. Planned maintenance is normally excluded from MTTR because MTTR focuses on unplanned failure recovery. This page subtracts planned maintenance from available hours before estimating availability.
4. Why use event-level durations?
Event data shows spread, extremes, and target compliance. Two systems can share the same MTTR while having very different best-case and worst-case repair behavior.
5. What is a good MTTR value?
A good MTTR depends on asset criticality, process risk, staffing, and spare access. Compare MTTR against internal targets, similar equipment, and service-level requirements rather than a universal benchmark.
6. Why show active and total MTTR separately?
Separating them helps identify whether problems come from technical repair work or from delay sources such as parts, access, approvals, or travel. Improvement actions differ for each cause.
7. How does MTTR affect availability?
Lower MTTR usually improves availability because each failure removes less operating time. Availability also depends on how often failures happen, so MTTR and failure frequency should be reviewed together.
8. What does restore probability show?
It estimates the chance of recovering service within the chosen target time, using an exponential maintainability model. It is useful for screening targets, not replacing detailed reliability studies.