Ask two maintenance managers how reliable their plant is and you will get two anecdotes. Ask them for MTBF and MTTR and you get two numbers you can compare, trend and act on. These two metrics — mean time between failures and mean time to repair — are the language reliability is measured in, and they are simpler than the acronyms make them sound.
This guide walks through both. It covers what each one means, the formula and a worked example for each, how they differ, how availability is derived from the two, a few related metrics (MTTF and MTTA) worth knowing, and how a CMMS computes and trends them for you from breakdown data. If you want the wider picture first — the whole asset lifecycle these metrics sit inside — start with our pillar guide, what is CMMS software? Every number in the examples below is illustrative, chosen to show the arithmetic.
1. Two numbers, two questions
Reliability engineering splits a very human worry — "can I count on this machine?" — into two precise questions, and gives each its own metric.
- How often does it fail? That is reliability, measured by MTBF (mean time between failures) — the average time the asset runs between one failure and the next. A higher MTBF means a machine you can leave running with confidence.
- How long does it take to fix? That is maintainability, measured by MTTR (mean time to repair) — the average time to restore the asset once it has failed. A lower MTTR means a breakdown costs you less time.
The reason both matter is that they are independent. A machine can be very reliable but slow to fix (high MTBF, high MTTR) — rare failures, but each one drags on for a day because the spare is not on the shelf. Or it can be quick to fix but unreliable (low MTBF, low MTTR) — it fails constantly, but each fix takes minutes. You cannot judge a machine on one number alone, which is exactly why a CMMS tracks both.
2. MTBF — the formula and a worked example
MTBF (mean time between failures) is the average operational time between failures for a repairable asset. The formula is straightforward:
MTBF = total operational (uptime) hours ÷ number of failures
| # | Step | What you do |
|---|---|---|
1 |
Choose a period | Pick the window you are measuring — a month, a quarter — and the asset it applies to. |
2 |
Add up uptime | Total the hours the asset was operational and available to run over that period (exclude the downtime). |
3 |
Count the failures | Count how many times the asset failed in the period — each breakdown ticket is one failure. |
4 |
Divide | Divide uptime hours by the number of failures. The result is the average time the asset runs between failures. |
Worked example (illustrative). Suppose a machine is operational for 600 hours in a period and fails 4 times. Its MTBF is 600 ÷ 4 = 150 hours — on average, it runs 150 hours between failures. If preventive maintenance and reliability work later cut the failures to 2 over the same 600 hours, MTBF doubles to 300 hours: the machine is now twice as reliable, without you touching how fast you repair it.
3. MTTR — the formula and a worked example
MTTR (mean time to repair) is the average time to restore the asset after a failure — from the moment it goes down to the moment it is running again. The formula mirrors MTBF but uses downtime:
MTTR = total repair (downtime) hours ÷ number of repairs
Worked example (illustrative). Take the same machine: across its 4 failures, the total repair time was 20 hours. Its MTTR is 20 ÷ 4 = 5 hours per repair. Now suppose the right spare had been on the shelf and the technician better prepared, halving the average repair to 2.5 hours. MTTR drops to 2.5 hours — each breakdown now costs half the downtime, without the machine failing any less often.
The two worked examples make the central point: MTBF and MTTR are two different levers. Raising MTBF is about stopping failures — preventive maintenance, reliability work, root-cause fixes. Lowering MTTR is about recovering faster — spare-part availability, skilled and well-instructed response, and good asset history so the technician knows the machine. A CMMS is where both efforts are recorded and their effect made visible.
The single biggest driver of a long repair is usually a spare that was not on the shelf. Linking each asset to its spare parts list and setting reorder levels keeps the critical spare available, so the repair is a fix rather than a wait. See how spare parts & BoM and spare-part inventory management keep MTTR down.
4. MTBF vs MTTR — side by side
Because they are so often quoted together and so easily confused, it helps to see the two metrics against each other.
| Aspect | MTBF | MTTR |
|---|---|---|
| Stands for | Mean time between failures | Mean time to repair |
| Measures | Reliability — how often it fails | Maintainability — how fast you fix it |
| Formula | Uptime hours ÷ number of failures | Downtime hours ÷ number of repairs |
| Higher is better? | Yes — longer between failures | No — lower means faster repair |
| Improved by | Preventive maintenance, reliability work | Spare availability, faster skilled response |
| Illustrative value | 600 h ÷ 4 = 150 hours | 20 h ÷ 4 = 5 hours |
Keeping them distinct matters because they point to different actions. If MTBF is low, the machine is failing too often and the answer is a preventive schedule and root-cause work. If MTTR is high, the failures are dragging on and the answer is spares, staffing and better work instructions. A single blended "downtime" number tells you there is a problem but not which of the two to fix.
5. Deriving availability
MTBF and MTTR combine into the number most plants ultimately care about: availability — the share of time an asset is available to run. It is derived directly from the two:
Availability = MTBF ÷ (MTBF + MTTR)
Availability combines both metrics. With the illustrative MTBF of 150 h and MTTR of 5 h, availability is 150 ÷ 155 ≈ 96.8%. The numbers are illustrative — the formula is the point.
Worked example (illustrative). Using our machine's MTBF of 150 hours and MTTR of 5 hours, availability is 150 ÷ (150 + 5) = 150 ÷ 155 ≈ 96.8%. The machine is available to run about 97% of the time. Now look at what the two levers do to that number:
| Scenario | MTBF | MTTR | Availability |
|---|---|---|---|
| Baseline | 150 h | 5 h | ≈ 96.8% |
| Halve MTTR (better spares) | 150 h | 2.5 h | ≈ 98.4% |
| Double MTBF (preventive) | 300 h | 5 h | ≈ 98.4% |
| Both together | 300 h | 2.5 h | ≈ 99.2% |
Illustrative figures — not real plant data. The point is that you can lift availability from either direction: fail less often, or recover faster. Pulling both levers compounds the gain.
6. MTTF, MTTA and the metrics around them
MTBF and MTTR have a few cousins that are worth knowing so you use the right one for the right asset. They are captured the same way — by timestamping events in the maintenance record.
- For non-repairable items you replace, not repair
- Average life until the item fails — e.g. a bearing, a bulb
- Use MTTF for consumables; MTBF for repairable machines
- Time from a breakdown being reported to it being acknowledged
- Measures response speed before repair even begins
- A hidden chunk of downtime a CMMS makes visible
The distinction between MTBF and MTTF is the one people most often get wrong: MTBF is for assets you repair and return to service (it measures the running time between failures), while MTTF is for items you throw away and replace (it measures the life until failure). And MTTA is a useful reminder that MTTR is often longer than the actual wrench time — some of it is the gap before anyone even acknowledges the breakdown. Because a CMMS timestamps when a breakdown is reported, acknowledged and restored, it can break total downtime into acknowledge time and repair time, and show where the delay really is.
7. Tracking them in a CMMS
Calculating MTBF and MTTR by hand once, for one machine, is easy. Doing it for every asset, every month, and trending it — that is where a CMMS earns its place. The trick is that the metrics fall out automatically once maintenance is recorded properly.
- Every breakdown is a ticket with downtime. The ticket records when the asset went down and when it was restored, so each failure and its repair time are captured at source — no separate log.
- Every asset accrues operational hours. With uptime and failure counts both in the system, MTBF and MTTR are computed for you, per asset, without a manual tally.
- The dashboard trends them over time. A machine-breakdown dashboard plots MTTR over time and MTBF over time, and lets you drill into machine-wise MTTR and MTBF for a selected machine, alongside breakdown-maintenance hours and downtime analysis.
- A live machine status board shows the now. Running, breakdown or idle for every asset at a glance — the real-time companion to the historical trend.
A machine-breakdown dashboard: MTBF trending up and MTTR trending down for a selected machine is what improvement looks like. The values shown are illustrative.
The value of trending rather than snapshotting is that a single month's MTBF can be noise — one bad week distorts a small sample. A rising MTBF line over several months is signal: the preventive programme is working. Likewise a falling MTTR line says your spares and response are getting better. See Dashboards & MTTR/MTBF.
8. How Fast Maintenance tracks reliability
Fast Maintenance Software turns the maintenance you already do into these metrics as a by-product, so reliability reporting is not extra work:
- Breakdown tickets with downtime capture. Every breakdown records time-down and time-restored, and consumes the spares issued against it — the raw material for MTBF and MTTR. See Breakdown & Emergency.
- MTTR and MTBF over time. The machine-breakdown dashboard plots MTTR-over-time and MTBF-over-time, with machine-wise trends you can select per machine, alongside breakdown-maintenance hours and downtime analysis. See Dashboards & MTTR/MTBF.
- A live machine status board. Running, breakdown or idle for every asset, so the real-time picture sits beside the historical trend.
- Preventive maintenance to raise MTBF. Time- and usage-based PM schedules with checklists push failures further apart. See Preventive & Planned.
- Spare-part availability to lower MTTR. A spare BoM per asset with reorder levels keeps the right part on the shelf, so repairs are fixes not waits. See Spare Parts & BoM.
- Dhruv AI on the causes. Dhruv AI summarises breakdown and downtime patterns and clusters breakdown-cause remarks into labelled themes, so the recurring causes dragging MTBF down or MTTR up stand out.
The result is that MTBF, MTTR and availability stop being spreadsheet exercises done once a quarter and become live, per-machine trends you can act on — cloud or on-premise, for manufacturers of every kind across India and worldwide. For how the pieces connect, start with what CMMS software is, and read how preventive vs breakdown maintenance is the strategy behind a rising MTBF.
9. Frequently asked questions
See your MTTR and MTBF trending on screen
A 30-minute demo — breakdown tickets, MTBF and MTTR over time per machine, and the live machine status board, on your own assets.