MTBF and MTTR: calculate availability without hiding downtime

MTBF summarizes operating time per failure. MTTR summarizes repair downtime per completed event. Neither tells a maintenance team what to do until the event boundary, asset population and failure consequences are visible. A machine that fails rarely but takes days to recover may deserve a different intervention from one with frequent five-minute stops.

FIG. 05Power at the shaft

Calculate a consistent window

Suppose one asset accumulated 1,000 operating hours, failed five times and required 20 repair hours across those five completed repairs. MTBF = 1,000 / 5 = 200 hours. MTTR = 20 / 5 = 4 hours. Repair-based availability = 200 / (200 + 4) = 98.0392%. The MTBF and MTTR calculator reproduces this example.

Operating time excludes the counted repair downtime. Dividing 1,020 elapsed hours by five failures would use a different numerator. Calendar availability can also include scheduled work, waiting for orders or periods when the asset was never required; label that boundary rather than mixing it into this calculation.

Define the repair clock

Choose whether repair duration starts at failure detection, maintenance arrival or hands-on work. Choose whether it ends at technical repair, restart or the first accepted good unit. Keep diagnosis, parts waiting and validation as separate intervals when possible. That decomposition tells you whether training, spares or the repair itself dominates recovery.

A repair still open at the end of the reporting period must remain visible. Excluding it makes a completed-event MTTR look better while operational downtime grows. Report open events and elapsed downtime alongside the completed-event mean.

Do not confuse reliability with age

An MTBF of 200 hours does not mean the next failure arrives at hour 200, or that replacement at hour 199 is justified. A mean over several assets can mix different ages, duties and failure modes. Trend repeat failures by mechanism and duty, and use the condition-monitoring guide only where the signal can detect the relevant degradation.

Zero observed failures is a valid observation. It does not justify an infinite reliability claim. Retain total operating hours and use an appropriate statistical model and confidence bounds when a consequential reliability claim is required.

Use the result to choose work

Connect the failure record to the CMMS workflow and preserve durations in the downtime worksheet.

Source

NIST's constant repair-rate model gives the total-time to failure-count estimator and discusses inference under model assumptions. The event-boundary recommendations and example here are an operational interpretation, not a prediction of an individual asset's life.