How to Calculate MTBF (Mean Time Between Failures), With Worked Examples

Why Your Next Failure Is Already Scheduled — You Just Don't Know When

It's a Tuesday morning when the hydraulic press stops mid-cycle. The maintenance manager pulls the repair log and finds the same cylinder seal failed eight months ago, and eleven months before that. Three failures. Nobody connected the dots. Nobody set a PM interval to catch it first.

That's exactly the problem MTBF — mean time between failures — is designed to solve. It turns a repair log full of individual incidents into a single, actionable number: on average, how long does this asset run before it fails? Once you have that number, you can set a PM interval to intervene before the next failure arrives, instead of after.

By the end of this article, you'll be able to calculate MTBF for any asset in your fleet, interpret what the number tells you, and translate it into a PM interval you can track and defend. You'll also see where a persistent, multi-asset calculation engine makes this work sustainable past the first few machines.

---

The MTBF Formula (and What Each Term Actually Means)

MTBF (mean time between failures) is defined as:

MTBF = Total Operating Time ÷ Number of Failures

Two terms need precise definitions before you plug in numbers.

Total operating time is the cumulative time the asset was actually running — not calendar time, not shift time, not time it sat idle or was down for repair. If a press runs two 8-hour shifts per day, five days a week, its weekly operating time is 80 hours, not 168 hours (one full week). Time the asset spends under repair, waiting for parts, or sitting idle does not count.

Number of failures is the count of unplanned stoppage events during the measurement window — specifically failures that interrupted production. Planned maintenance shutdowns do not count as failures.

The result — MTBF — is expressed in the same unit as your operating time: hours, days, or cycles, depending on how you measure your equipment's usage.

A high MTBF means the asset runs a long time between failures: reliable. A low MTBF means failures are arriving frequently: investigate root cause and tighten your PM interval.

---

How to Calculate MTBF: Step by Step

Step 1 — Define your measurement window

Choose a period long enough to capture several failure events. A window that contains only one failure gives you a single data point, not a pattern. Aim for at least three failures, or at least six to twelve months of operating history, whichever gives more failure events.

Step 2 — Accumulate total operating time

Pull your run hours from the equipment log, production records, or operator shift reports. Add up only the hours the machine was actively running. Exclude downtime periods — planned PM, corrective repairs, parts-waiting time — from the total.

If your records track calendar hours rather than run hours, multiply calendar hours by a realistic utilization factor. For a machine running two 8-hour shifts, five days a week, utilization is roughly 67% of a 24-hour calendar day — but use your actual shift schedule, not a generic assumption.

Step 3 — Count failure events

From the same maintenance or repair log, count every unplanned failure event in the window. Each event counts once, regardless of how long the repair took.

Step 4 — Divide and interpret

Divide total operating hours by failure count. The quotient is your MTBF in hours (or whatever unit you used).

---

Worked Example 1 — Single Asset (Hydraulic Press)

A hydraulic press runs two 8-hour shifts per day, five days per week, for 52 weeks. The maintenance log shows four unplanned failures during that period.

Inputs (illustrative):

• Shifts per day: 2
• Hours per shift: 8
• Days per week: 5
• Weeks in window: 52
• Total operating hours: 2 × 8 × 5 × 52 = 4,160 hours
• Failure events: 4

Calculation:

MTBF = 4,160 ÷ 4 = 1,040 hours

Interpretation: On average, this press runs 1,040 operating hours before an unplanned failure. At 80 operating hours per week, that's roughly 13 weeks — about one failure per quarter.

If the OEM manual recommends a hydraulic filter inspection every 1,000 hours, this MTBF confirms you're close to the OEM threshold in practice. If that interval had been set at 2,000 hours (a common mistake when tribal knowledge fills the gap left by a missing manual), four failures per year would be the predictable result.

---

Worked Example 2 — Three-Asset Comparison (Fabrication Cell)

A plant manager wants to compare reliability across three machines on the same fabrication line. All three run the same shift schedule: 80 operating hours per week, measured over 26 weeks (2,080 operating hours each).

Asset	Total Op. Hours	Failures	MTBF
CNC Mill A	2,080	2	1,040 hrs
Conveyor B	2,080	7	297 hrs
Spot Welder C	2,080	1	2,080 hrs

Calculation shown for Conveyor B:

MTBF = 2,080 ÷ 7 = 297 hours (≈ 3.7 weeks)

Interpretation: Conveyor B is failing roughly every 3.7 weeks — nearly twice a month. That frequency warrants immediate investigation: is the PM interval too long, is the asset undersized for current duty cycle, or is there a recurring root cause (a specific component that keeps failing)? Spot Welder C, by contrast, has run the entire 26-week window with a single failure; its current PM interval may be conservative relative to actual performance.

A three-asset comparison like this is manageable in a spreadsheet. Extend it to 30, 50, or 100 assets and the spreadsheet breaks — version conflicts, formula errors, no persistent history. That's the point at which a persistent, multi-asset calculation engine earns its place.

---

Worked Example 3 — MTBF in Hours vs. Days vs. Cycles

MTBF works in any unit, as long as you're consistent. For assets measured by cycles (injection molding shots, press strokes, conveyor passes), use cycles throughout:

Inputs (illustrative):

• Injection mold press: 1,200,000 cycles over the measurement window
• Failures: 3

MTBF = 1,200,000 ÷ 3 = 400,000 cycles

If the press runs 50,000 cycles per week, MTBF is 8 weeks. That becomes your PM interval anchor — and cycle-based tracking is far more precise than calendar-based tracking for this type of equipment. When cycle counts vary week to week (seasonal demand swings, product changeovers), a calendar interval will systematically over-PM during slow periods and under-PM during peak ones.

---

From MTBF to PM Interval: The Practical Bridge

MTBF answers the question how long does this asset typically run before it fails? A PM interval answers when should I intervene to prevent the next failure? The two are related, but MTBF is not your PM interval.

A common starting rule: set your PM interval at 50%–70% of MTBF, so maintenance occurs before the failure distribution's peak risk window. For the 1,040-hour hydraulic press: a PM interval somewhere in the range of 520–730 hours gives you a reasonable buffer. Always cross-reference that against the OEM manual — use whichever interval is more conservative until you have more failure data. The OEM manual, not MTBF alone, governs the minimum interval for most equipment; MTBF tells you whether your actual failure history is tracking inside or outside OEM expectations.

Confirm specific PM intervals against your equipment's OEM documentation and recognized standards (ASHRAE for HVAC systems, NFPA 70B for electrical equipment, OSHA for powered industrial trucks). Intervals vary by equipment type, duty cycle, and operating environment; what the math suggests is a starting point, not a guaranteed safe interval. For compliance-related maintenance, verify requirements with the relevant authority.

For a deeper walk through how MTBF connects to availability and to overall equipment effectiveness, see MTBF, MTTR, and OEE Explained. For the MTTR side of the equation — how long repairs actually take — see How to Calculate MTTR.

---

What MTBF Doesn't Tell You (And How to Use It Honestly)

MTBF assumes failures are random and independent — that the 1,041st hour is exactly as risky as the 500th. For many mechanical components this is a reasonable approximation; for components with wear-out failure modes (seals, bearings, belts), failure probability actually increases with age. For those components, a Weibull analysis gives a sharper picture of when risk accelerates — but MTBF remains the right starting metric when you're building a reliability baseline from a repair log, which is where most SMB maintenance programs begin.

A few practical honesty checks:

• MTBF from two failure events is fragile. A sample of two gives you a midpoint, not a pattern. Hold conclusions loosely until you have five or more events.
• Mixed failure modes inflate MTBF. If your conveyor fails for three different reasons (belt wear, motor overload, sensor fault), the aggregate MTBF blends three separate failure distributions. Separate them by failure mode if your log captures that detail.
• MTBF tracks the past. A change in duty cycle, operating environment, or product mix can shift your actual MTBF significantly. Recalculate annually at minimum, or after any major change in operating conditions.

---

Tracking MTBF Across a Fleet — And Connecting It to Cost

A single MTBF number is useful. A fleet of MTBF numbers — updated as failure history accumulates, driving PM interval recommendations, and feeding into an annual maintenance cost projection — is an operating strategy.

For a small fleet (under ten assets), a structured spreadsheet and a free MTBF calculator can get you started. Our MTBF/MTTR/OEE Calculator Workbook walks through the calculation for all three reliability metrics in a single Excel file, with worked examples you can overwrite with your own data.

For a larger fleet, the spreadsheet approach runs into its ceiling: no persistent history across assets, no automatic PM-interval recalculation as new failure events are logged, no fleet-level cost rollup that connects reliability data to budget planning. That's the gap a persistent, multi-asset calculation engine fills — not a full CMMS built for work-order execution, but a focused planning and cost-forecasting tool that keeps the math current across every asset in the register.

If you're working across more than ten assets and want to connect your MTBF baseline to PM intervals and projected annual maintenance costs, the Preventive Maintenance Interval and Cost Guide covers that connection end to end.

---

The Next Step: Do the Math on Your Own Fleet

The MTBF formula is straightforward — the work is in pulling consistent operating-time records and a clean failure log. Most maintenance managers have that data somewhere; the gap is usually the calculation engine that turns it into a PM interval and a cost estimate, and keeps both current as the fleet changes.

Download the MTBF/MTTR/OEE Calculator Workbook to work through MTBF, MTTR, and OEE for your own assets in a structured Excel format — with the formulas visible, the inputs labeled, and space to enter your actual failure history.

If you want those calculations to persist across your entire fleet — and to see how MTBF-driven PM intervals roll up into an annual maintenance cost projection — the Maintenance Cost and Interval Planner offers a 14-day free trial, no credit card required.