What does MTBF actually measure?

MTBF is the average operating time between functional failures, calculated as Total Operating Hours divided by Number of Failures. A result of 600 hours means the asset runs about 600 hours on average before the next unplanned failure. It measures inherent reliability during run time only, so planned downtime and idle time are excluded from the operating hours.

How do I calculate MTBF for a machine over a year?

Sum the actual run hours in the period and count the functional failures, then divide. If a machine ran 7,200 hours and failed 12 times, MTBF = 7,200 / 12 = 600 hours per failure. Exclude weekends, planned maintenance, and idle time from the hours, and exclude PM completions from the failure count so you measure unplanned failures only.

What is a good MTBF value?

Good is relative to the equipment class and your peers, not an absolute number. Benchmark identical assets against each other and trend each one over time. Rising MTBF is the goal. A machine at 600 hours sitting beside peers at 1,200 hours is underperforming; the same 600 hours may be excellent for a high-cycle stamping press. Compare like with like.

Why did my MTBF suddenly drop?

Check three things. First, confirm you did not add PM stops or minor adjustments to the failure count, which inflates failures and lowers MTBF. Second, look for a recurring root cause, such as a bearing or sensor failing repeatedly. Third, review any recent change to PM intervals or duty cycle. A drop from 600 to 300 hours means failures doubled or run time halved.

Is MTBF measured in hours or cycles?

Either, as long as the numerator and definition match. Most maintenance teams use operating hours, giving results like 600 hours between failures. High-cycle equipment such as presses or pick-and-place machines often use cycles or strokes instead, so MTBF becomes cycles between failures. Pick one basis, use actual run time rather than calendar time, and stay consistent across all assets you compare.

MTBF vs MTTF, what is the difference?

MTBF applies to repairable assets and measures time between failures, since you fix and return the asset to service. MTTF (Mean Time To Failure) applies to non-repairable items like bearings, bulbs, or fuses that you replace rather than repair, measuring time until the single failure ends life. For a repairable production machine at 7,200 hours and 12 failures, MTBF of 600 hours is the correct metric.

Maintenance and Reliability

MTBF Formula

Mean Time Between Failures (MTBF) is the average operating time between functional failures. Use it for bad-actor ranking, PM strategy reviews, and reliability benchmarking across similar equipment.

Formula

MTBF = Total Operating Hours / Number of Failures

Variables

Total Operating Hours: Sum of actual run hours in the measurement period, excluding planned downtime
Number of Failures: Count of functional failures that stopped the asset or degraded required performance

Understanding the MTBF Formula

MTBF answers one question: how much run time do you typically get before this asset fails again. It divides Total Operating Hours by Number of Failures, so 7,200 run hours and 12 failures gives 600 hours between failures. It is a reliability measure, not an availability measure, and it only counts time the machine was actually running. Rising MTBF means your PM program and root-cause fixes are working; falling MTBF flags a bad actor worth investigating.

Get Total Operating Hours from run-time counters or OEE logs, excluding planned downtime, weekends, and idle time. Count only functional failures that stopped the asset or degraded required performance; do not count PM completions or minor adjustments. Keep the measurement window long enough to capture real failure behavior. Twelve failures over a year is defensible; three failures over a month is too noisy. Use the same failure definition across assets so bad-actor rankings compare fairly.

A single MTBF number means little without a trend or a peer. Track it quarter over quarter and rank similar equipment against each other; the machine with 200 hours MTBF next to peers at 600 is your bad actor. Pair MTBF with MTTR to see the full picture: high MTBF but long repairs still hurts uptime. When MTBF drops after a PM interval change, revisit that interval before blaming components.

Worked Example

A machine ran 7,200 hours over the year and had 12 functional failures.

MTBF = 7,200 / 12 = 600 hours per failure

Result: 600 hours between failures on average

Common Mistake

Including planned maintenance stops in the failure count. MTBF measures unplanned functional failures only. Counting PM completions as failures will inflate the failure count and make reliability look worse than it is.

Frequently Asked Questions

What does MTBF actually measure?: MTBF is the average operating time between functional failures, calculated as Total Operating Hours divided by Number of Failures. A result of 600 hours means the asset runs about 600 hours on average before the next unplanned failure. It measures inherent reliability during run time only, so planned downtime and idle time are excluded from the operating hours.
How do I calculate MTBF for a machine over a year?: Sum the actual run hours in the period and count the functional failures, then divide. If a machine ran 7,200 hours and failed 12 times, MTBF = 7,200 / 12 = 600 hours per failure. Exclude weekends, planned maintenance, and idle time from the hours, and exclude PM completions from the failure count so you measure unplanned failures only.
What is a good MTBF value?: Good is relative to the equipment class and your peers, not an absolute number. Benchmark identical assets against each other and trend each one over time. Rising MTBF is the goal. A machine at 600 hours sitting beside peers at 1,200 hours is underperforming; the same 600 hours may be excellent for a high-cycle stamping press. Compare like with like.
Why did my MTBF suddenly drop?: Check three things. First, confirm you did not add PM stops or minor adjustments to the failure count, which inflates failures and lowers MTBF. Second, look for a recurring root cause, such as a bearing or sensor failing repeatedly. Third, review any recent change to PM intervals or duty cycle. A drop from 600 to 300 hours means failures doubled or run time halved.
Is MTBF measured in hours or cycles?: Either, as long as the numerator and definition match. Most maintenance teams use operating hours, giving results like 600 hours between failures. High-cycle equipment such as presses or pick-and-place machines often use cycles or strokes instead, so MTBF becomes cycles between failures. Pick one basis, use actual run time rather than calendar time, and stay consistent across all assets you compare.
MTBF vs MTTF, what is the difference?: MTBF applies to repairable assets and measures time between failures, since you fix and return the asset to service. MTTF (Mean Time To Failure) applies to non-repairable items like bearings, bulbs, or fuses that you replace rather than repair, measuring time until the single failure ends life. For a repairable production machine at 7,200 hours and 12 failures, MTBF of 600 hours is the correct metric.