Condition-based maintenance (CBM) is a maintenance strategy that triggers work based on the actual, measured condition of an asset — vibration, temperature, oil quality, meter readings, or inspection findings — rather than a fixed calendar date or usage interval.
It sits between preventive maintenance (schedule-driven) and predictive maintenance (forecast-driven): CBM reacts to a threshold being crossed right now, while predictive maintenance uses that same data to forecast when a threshold will be crossed in the future.
How condition-based maintenance works
CBM depends on a monitoring signal and a defined threshold that, once crossed, generates a work order:
- Vibration analysis — rising vibration amplitude on rotating equipment (motors, pumps, fans) signals bearing wear or misalignment before catastrophic failure
- Oil analysis — particle counts and chemical breakdown in lubricant indicate internal wear long before a gearbox or engine fails outright
- Thermal imaging — hot spots on electrical connections or bearings flag developing faults invisible to the naked eye
- Meter readings — runtime hours, cycle counts, or output volume crossing a defined threshold (see meter reading automation) trigger a work order regardless of calendar date
- Visual and manual inspection — a technician’s checklist finding (corrosion, leak, unusual noise) can also be a condition trigger, not just a sensor reading
The defining feature is that the work order is generated because the condition changed, not because a date arrived on the calendar.
CBM vs. preventive maintenance vs. predictive maintenance
These three strategies are often confused because all three are “proactive” in the sense of happening before a full breakdown, but they’re triggered differently:
- Preventive maintenance runs on a fixed interval — every 90 days, every 500 operating hours — regardless of the asset’s actual condition. It’s simple to schedule but can result in servicing equipment that didn’t need it yet, or missing a failure that develops faster than the interval assumes.
- Condition-based maintenance runs when a measured value crosses a defined threshold right now. It avoids unnecessary servicing but requires monitoring infrastructure (sensors, meters, or a disciplined inspection routine) to generate the trigger.
- Predictive maintenance goes a step further and uses historical and real-time data with analytics or machine learning to forecast when a threshold will be crossed, so maintenance can be scheduled proactively rather than reactively the moment a threshold trips.
In practice, CBM is often the stepping stone between the two: a facility that starts with calendar-based PM adds sensors and meter thresholds to move to CBM, then layers analytics on top of that same data to reach full predictive maintenance.
Why CBM matters for maintenance cost
Fixed-interval preventive maintenance is a compromise — the interval has to be conservative enough to catch fast-failing units, which means most assets get serviced before they actually need it. CBM removes that guesswork by tying the maintenance trigger to the asset’s real condition, which:
- Reduces unnecessary labor and parts consumption on units that are still healthy
- Catches genuinely fast-degrading units that a fixed interval would have missed
- Extends the useful life of components that are replaced based on actual wear rather than a conservative default
Implementing CBM in a CMMS
A CMMS supports condition-based maintenance by accepting meter readings or sensor feeds as PM triggers alongside calendar triggers, then automatically generating a work order once a threshold is crossed. This is the same infrastructure — IoT device monitoring and telemetry data ingestion — that predictive maintenance programs build on, which is why CBM is usually the first step toward a full predictive maintenance rollout rather than a separate initiative.
Related terms
Condition-based maintenance sits between preventive maintenance scheduling and predictive maintenance, and depends on the same meter reading automation and telemetry data infrastructure that powers both.