.png)
Most equipment doesn't fail without warning. It degrades — slowly, predictably, measurably. The problem is that most facility teams aren't measuring the right things to catch it in time.
Mean time between failures (MTBF) is one of the clearest reliability metrics available to maintenance and facility management teams. It tells you, on average, how long an asset operates before it breaks down. Simple in concept. Powerful in practice — if you're actually using it.
This blog breaks down what MTBF means, how to calculate it, how it compares to related metrics, and how facility teams managing complex building portfolios can use it to move from reactive firefighting to genuine predictive maintenance.
What Is Mean Time Between Failures (MTBF)?
Mean time between failures is a measure of how reliably a repairable asset performs over time. It represents the average time elapsed between one failure and the next — during normal operating conditions.
The keyword here is repairable. MTBF applies to assets that are fixed and returned to service after a breakdown — think chillers, AHUs, elevators, pumps, or electrical panels in a commercial building. It does not apply to components that are replaced and discarded after failure (that's a different metric: MTTF, or Mean Time to Failure).
A high MTBF means an asset fails infrequently. A low MTBF means it's breaking down often — a signal that something is wrong with the asset, its maintenance schedule, its operating conditions, or all three.
For facility managers overseeing large, multi-system buildings, MTBF isn't just a maintenance number. It's a portfolio health indicator.
The Mean Time Between Failures Formula
The mean time between failures formula is straightforward:
MTBF = Total Operational Time ÷ Number of Failures
Total Operational Time is the cumulative hours an asset was running and available for use — excluding any time it was down for repairs or scheduled maintenance.
Number of Failures is the count of unplanned breakdowns within the measurement period.
A Quick Example
Say your building's primary chiller ran for 8,000 hours over the past year. During that period, it experienced 4 unplanned failures.
MTBF = 8,000 ÷ 4 = 2,000 hours
On average, the chiller runs 2,000 hours before the next failure. Whether that's acceptable depends on your building's operational demands, the criticality of the asset, and how that figure compares to the manufacturer's design specifications and your historical baseline.
Mean Time Between Failures Calculation: What to Include (and What Not To)
Getting the mean time between failures calculation right matters more than most teams realize. A few common mistakes:
- Don't include planned downtime. Scheduled maintenance windows, inspections, or shutdowns are not failures. Including them inflates your failure count and gives you a misleadingly low MTBF.
- Only count unplanned failures. MTBF is specifically about unexpected breakdowns — the events your maintenance team didn't see coming and had to respond to reactively.
- Use consistent time units. Whether you measure in hours, days, or weeks — be consistent across assets and time periods so comparisons are meaningful.
- Track at the asset level. Aggregating MTBF across an entire asset class (e.g., "all HVAC units") can mask individual outliers. A single underperforming unit hiding inside a healthy average is a liability.
MTBF vs. MTTR vs. MTTF: Clearing Up the Confusion
These three metrics frequently appear together — and they serve distinct purposes.
- MTBF (Mean Time Between Failures): Average time between one failure and the next. Used for repairable assets. Measures reliability.
- MTTR (Mean Time to Repair): Average time it takes to restore an asset to working condition after a failure. Measures maintenance responsiveness and repair efficiency.
- MTTF (Mean Time to Failure): Average time until a non-repairable component fails and must be replaced. Used for consumable parts like sensors, filters, or fuses.
Together, MTBF and MTTR give you a complete picture of asset performance. A high MTBF tells you the asset is reliable. A low MTTR tells you that when it does fail, your team responds and resolves it quickly. You want both working in your favour.
A building running on high MTBF + low MTTR is a building where downtime is rare and short. That's the target.
What's a Good MTBF? It Depends on the Asset
There's no universal benchmark — MTBF norms vary significantly by asset type, age, and operating environment. A few reference points for common building systems:
- HVAC units and AHUs: Well-maintained commercial HVAC systems typically achieve MTBF figures in the range of 15,000–25,000 operating hours. Anything significantly below 10,000 hours warrants a closer look at maintenance practices or equipment age.
- Elevators and lifts: Modern elevators in commercial buildings are designed for very high reliability. Frequent unplanned failures — more than 3–4 per year — signal a maintenance or component issue.
- Electrical panels and switchgear: These are designed for extremely long operational life with minimal failures. Any recurring unplanned failure here is a serious flag.
- Pumps and motors: Reliability varies heavily by load, lubrication quality, and operating environment. MTBF data over 12–24 months gives a cleaner baseline than short observation windows.
The most useful benchmark isn't an industry average — it's your own historical data. Track MTBF per asset over time and look for trends: is reliability improving, holding steady, or declining? Declining MTBF is one of the clearest early warning signs that an asset is approaching end-of-useful-life.
Why MTBF Matters More When You're Managing Multiple Buildings
For a single building, MTBF tracking is good practice. For a portfolio of buildings, it becomes essential infrastructure.
When you're managing 10, 20, or 50 buildings across multiple cities, the volume of assets — chillers, air handling units, elevators, generators, electrical systems — makes intuitive oversight impossible. You can't rely on a technician's gut feel or a spreadsheet updated once a month. Asset failures compound. A pattern of low MTBF across a building class or a specific supplier's equipment is a signal you need to catch early, not after three emergency callouts have already strained your opex budget.
This is where connected building management platforms shift the equation. When asset data flows in real time — run hours, fault alerts, temperature deviations, energy anomalies — MTBF calculations happen continuously, not quarterly. You're not looking at history; you're watching reliability in motion.
IQnext's IoT-based building management platform connects directly to critical building systems, pulling real-time operational data that feeds into maintenance intelligence. Instead of manually logging downtime events, facility teams get a live view of asset health across their entire portfolio — giving MTBF and related metrics the data quality they need to actually be useful.
The Cost of Ignoring MTBF
Facility teams that don't track MTBF aren't operating without a metric — they're operating on a worse one: how many emergencies happened this month.
Reactive maintenance consistently costs 3–5x more than planned maintenance when you factor in emergency labour rates, expedited parts procurement, secondary damage from uncontrolled failures, and tenant or occupant disruption.
Beyond direct costs, low asset reliability drives up energy consumption. Equipment running outside its optimal operating range uses more energy to deliver the same output — a direct hit to both opex and ESG targets.
MTBF gives facility managers a way to quantify reliability, spot deterioration early, and build a maintenance strategy grounded in evidence rather than intuition. In a portfolio where margins are tight and sustainability targets are non-negotiable, that's not a nice-to-have.
Start Small, Scale Fast
You don't need to overhaul your entire maintenance operation to start benefiting from MTBF tracking. Pick your five most critical assets. Log their run hours and failure events consistently for 90 days. Calculate the baseline. Then use that baseline to schedule your next maintenance intervention — not the calendar, not a hunch.
That's the shift from reactive to predictive. One asset at a time, then one building at a time, then a portfolio.
The data already exists in your building systems. The question is whether you're capturing it, connecting it, and acting on it.
FAQs
1. What is a good MTBF value?
There's no single benchmark — a good MTBF depends on the asset type, its age, and how critical it is to building operations. The most reliable benchmark is your own historical data. Track MTBF per asset over time and watch for trends. A declining MTBF is a warning sign regardless of the absolute number.
2. What is the difference between MTBF and MTTR?
MTBF measures how often an asset fails — the average time between one failure and the next. MTTR measures how quickly your team recovers — the average time it takes to repair an asset and return it to service. Together, they give a complete picture of asset reliability and maintenance efficiency.
3. Does MTBF include planned maintenance downtime?
No. MTBF only accounts for unplanned failures — unexpected breakdowns your team didn't anticipate. Scheduled maintenance, inspections, and planned shutdowns are excluded from the calculation. Including them would distort your failure count and produce a misleadingly low MTBF.
4. Can MTBF be used for all building assets?
MTBF applies to repairable assets — equipment that is fixed and returned to service after a failure, such as chillers, AHUs, elevators, and pumps. For non-repairable components like sensors or filters that are simply replaced after failure, MTTF (Mean Time to Failure) is the more appropriate metric.
5. How does MTBF support predictive maintenance?
MTBF gives you a reliability baseline for each asset. Once you know an asset's average failure interval, you can schedule maintenance interventions before the next failure window opens — rather than waiting for a breakdown. Over time, tracking MTBF trends helps you spot deteriorating assets early and prioritise maintenance resources where they matter most.
.png)
.png)
