Free MTBF and MTTR calculator: formulas, worked example and Excel log

The MTBF and MTTR formulas

Both indicators start from the same failure count over the same period. MTBF looks at the time the asset was running between those failures; MTTR looks at the time it was down being repaired. Measured together on one asset, they describe two different problems: how often it breaks, and how long each breakdown costs you.

Operating time is the observed period minus the repair downtime. The observed period is the time the asset was meant to run: 720 hours for 30 days around the clock, or the shift hours for an asset that only runs during the day. Planned stops, preventive maintenance and periods with no production scheduled come out of the period, not out of operating time.

• Operating time = observed period − total repair time
• MTBF = operating time ÷ number of failures
• MTTR = total repair time ÷ number of failures
• Availability = MTBF ÷ (MTBF + MTTR) = operating time ÷ observed period
• Failure rate = number of failures ÷ operating time (often quoted per 1,000 hours)

MTBF, MTTF, MTTR: which one to use

MTBF applies to repairable assets: a pump, a press or a conveyor that fails, gets repaired and runs again. MTTF, mean time to failure, applies to items that are replaced rather than repaired, such as a bearing, a fuse or a lamp. Using MTBF for a consumable part, or MTTF for a whole machine, mixes two different questions.

Two conventions exist for MTBF. Some definitions measure the time between the start of one failure and the start of the next, which includes the repair; the maintenance practice used here, and in standards such as EN 13306, counts operating time only. Neither is wrong, but a figure is only comparable with another figure calculated the same way. Write the definition next to the number.

MTTR has the same trap. Some teams count only hands-on repair time; others count from the moment the asset stopped until it was back in service, including waiting for a technician or a part. The second definition is what the production line actually feels, and it is the one this calculator uses.

What counts as a failure, and what does not

A failure is an unplanned event that stops the asset from doing its job, or forces it to run in a degraded mode you would not accept. Agree on the list before you start counting, because the definition changes MTBF more than any improvement will.

• Counts: a breakdown that stops the asset, a trip that needs an intervention before restart, a fault that forces the asset to be taken out of service.
• Does not count: preventive maintenance, inspections, planned changeovers, cleaning, and stops caused by missing material or operators.
• Decide once for minor stops that the operator clears in seconds. Most sites leave them out of MTBF and track them through OEE performance losses instead.
• One event, one failure: a breakdown that needs three visits before it is fixed is one failure with a long repair time, not three failures.

How to improve MTBF

MTBF improves when the same failures stop coming back. That starts with knowing which ones they are: an asset with a low MTBF almost always has two or three failure modes that account for most breakdowns.

• Record a cause for every breakdown, using a short list of failure codes rather than free text, so the repeated ones become visible.
• Turn the recurring causes into preventive tasks: lubrication, inspections, filter or belt changes at a frequency based on the failure history.
• Fix the root cause, not the symptom: a motor that keeps tripping may be overloaded, misaligned or badly ventilated.
• Check operating conditions such as load, speed, temperature and cleanliness, which shorten the life of components faster than age does.
• Watch the effect: recalculate MTBF for the same asset over the next periods, with the same definitions.

How to reduce MTTR

MTTR is rarely dominated by the repair itself. Most of the time goes into noticing the failure, getting the right person there, finding the cause and waiting for the part.

• Get the breakdown reported immediately, for example with a QR code on the asset that opens a request from any phone.
• Keep the critical spare parts in stock, with a minimum quantity, and know where they are.
• Give technicians the asset history and a repair procedure on their phone, so the diagnosis starts from what happened last time.
• Measure the phases separately when you can: waiting, diagnosis, repair and restart. The longest phase is the one to work on.

Common MTBF and MTTR calculation mistakes

Most disagreements about reliability figures come from definitions and small samples, not from the arithmetic.

• Using calendar time for an asset that only runs one shift. MTBF then looks three times better than it is.
• Counting preventive maintenance as failures. It lowers MTBF and punishes exactly the work that improves it.
• Drawing conclusions from two or three failures. With so few events, one breakdown more or less changes MTBF dramatically; watch the trend over several periods.
• Averaging the MTBF of different assets. Add up their operating time and their failures, then divide, or better, keep them separate.
• Comparing two sites that define failure or repair time differently.

When a spreadsheet is no longer enough

A failure log in Excel works while one person keeps it up to date for a handful of assets. It breaks down when breakdowns are typed in days later from memory, when repair times are estimated, and when the log lives apart from the work orders that actually repaired the asset.

In FreeMaint, a breakdown is recorded when it happens: the corrective work order, plus the downtime that opens when the asset is set to Down and closes when it runs again. MTBF, MTTR and availability are then computed per asset from that record. The free Core tier covers assets, work orders, downtime, failure codes and time-based preventive maintenance for unlimited users; the failure analysis report is part of Business, $99 per company per month (flat, never per user).

FreeMaint Research, 2026, found that 27.1% of sites log no preventive maintenance at all, a gap that tends to show up as a low MTBF.