Condition-Based vs Calendar-Based Maintenance: A Decision Guide
Why this matters
Once a shop commits to preventive maintenance, the next question is timing: do you service on a fixed schedule (calendar-based) or when the equipment shows it needs it (condition-based)? Pick wrong and you either over-service good equipment, wasting labor and parts, or under-service the things that wear unpredictably and let them fail. Most real PM programs use both. This card helps you decide which mode each asset deserves.
The two approaches defined
Calendar-based maintenance services on a fixed interval: every so many months, run-hours, or cycles, you do the work regardless of the equipment's actual condition. Simple to schedule, easy to sell as a plan, predictable for the office.
Condition-based maintenance (CBM) services when measured wear signs say it is time. You monitor the equipment (temperature, vibration, pressure, visible wear) and act on the reading, not the date. It avoids both over-servicing and surprise failures, but it requires that you can actually measure the condition and that you trust your baseline.
Neither is universally better. The right choice depends on the asset.
Decision matrix
| Factor | Lean calendar-based | Lean condition-based |
|---|---|---|
| Wear pattern | Predictable, steady over time | Variable, depends on use |
| Measurability | Hard to read condition | Condition is easy to measure |
| Failure warning | Little warning, sudden | Clear, readable wear signs |
| Monitoring cost | Cheap to just do the work | Worth the cost to monitor |
| Duty cycle | Steady, consistent load | Highly variable load |
| Consequence | Low cost of early service | High cost of unneeded service |
| Access | Easy to reach on schedule | Hard to access casually |
When to pick calendar-based
Use a fixed schedule when wear is predictable and steady, when the condition is hard to measure, or when the work is cheap enough that doing it on a date beats the cost of monitoring. Consumables that deplete at a known rate, lubrication on a published interval, and seals with a known service life all fit a calendar. If a part wears the same amount every month no matter what, the calendar captures that perfectly and you do not need to measure anything.
When to pick condition-based
Use CBM when wear depends heavily on use, when you can read the condition cheaply (heat, noise, vibration, pressure, visible wear), and when servicing too early wastes a costly part or a long-lead component. A motor that runs hard some seasons and idle others wears unpredictably; replacing its bearing on a calendar either wastes good life or misses an early failure. Watch its condition instead and act on the reading.
CBM is also right for high-consequence parts where you want the earliest possible warning. Monitoring a critical pump's temperature and vibration buys you lead time a calendar cannot.
The honest mixed program
Real PM blends both. A single piece of equipment often has calendar items (lubricate on schedule, replace the consumable every interval) and condition items (watch the bearing temperature, act when vibration climbs). Do not force one mode across a whole site. Walk it part by part and assign each component to the mode that fits its wear pattern and consequence.
What CBM requires from you
Condition-based maintenance only works if you do three things: establish a real baseline so you know what normal looks like, measure consistently so trends are comparable, and document every reading so the next visit can see the trend. Without a baseline, a reading is just a number. The whole value of CBM is in the trend, not the single measurement. If you cannot or will not measure consistently, default that asset to a calendar and do the work.
References
- Manufacturer documentation: published service intervals and condition limits
- Reliability-centered maintenance, trade-standard practice on selecting maintenance strategy
- Predictive and condition-monitoring practice across mechanical and electrical systems
- See related: Preventive vs Reactive Maintenance; Documenting a Maintenance Baseline