Time-based maintenance and usage-based maintenance are the two most common preventive maintenance scheduling strategies - and choosing the wrong one for an asset can cost you more than a breakdown ever would. Time-based maintenance triggers service at fixed calendar intervals (every 30 days, every quarter). Usage-based maintenance triggers service based on actual asset activity - hours run, miles driven, or cycles completed. According to a Plant Engineering survey, organizations that match their PM scheduling strategy to the right asset type reduce maintenance costs by up to 18% and cut unplanned downtime significantly.
Time-based maintenance (TBM) is a preventive maintenance strategy where service tasks are scheduled at fixed calendar intervals - regardless of how much the asset has actually been used. A technician services a compressor every 90 days, changes HVAC filters every month, or inspects fire safety equipment every six months. The schedule is driven purely by the calendar, not by the machine's actual workload.
A time-based PM schedule is simple by design. You set a start date and a recurrence interval, and the system generates work orders automatically on that cadence. Common examples: daily lubrication checks on high-speed packaging lines, monthly filter replacements on HVAC units, quarterly electrical panel inspections, and annual boiler overhauls. The strength here is predictability - your team knows exactly when work is coming, procurement can plan parts in advance, and compliance audits are straightforward.
Usage-based maintenance (UBM) schedules service based on actual asset utilization rather than elapsed time. Instead of "every 90 days," the trigger becomes "every 500 operating hours," "every 10,000 miles," or "every 50,000 production cycles." The maintenance clock only ticks when the asset is actually running - making this approach far more accurate for assets with variable usage patterns.
Usage-based PM requires a way to track asset activity - a meter, sensor, odometer, or runtime counter. Modern CMMS platforms can read these values automatically via IoT integrations or manual meter entry, then trigger a work order when the threshold is reached. Common metrics: operating hours for generators and compressors, mileage for fleet vehicles and forklifts, production cycles for presses and conveyor systems, and fuel consumed for diesel generators.
Understanding where each strategy excels helps you build a smarter maintenance program. Usage-based wins on accuracy for wear-driven failures - wear is driven by operation, not time sitting idle. Time-based wins on ease of administration - no special tracking equipment required. Time-based carries a higher risk of over-maintaining low-utilization assets. Usage-based fits motors, vehicles, and production machinery where wear correlates directly with runtime. Time-based suits HVAC, safety equipment, and assets where age and environmental exposure drive degradation.
Time-based maintenance is the right call when degradation is driven more by time than use, when usage is consistent and predictable, or when regulatory standards mandate calendar-based intervals.
Usage-based maintenance delivers its highest value on assets with highly variable utilization. Apply UBM to fleet and mobile equipment like forklifts and trucks, production machinery like CNC machines and injection molding presses, high-cost rotating equipment like centrifugal pumps and compressors, and IoT-connected assets where real-time sensor data feeds runtime hours directly into your CMMS.
Yes - and for many critical assets, using both together is the most effective approach. Either/Or scheduling triggers the work order when the first condition is met - whichever comes first. For example: service a generator every 250 hours OR every 6 months. And scheduling triggers only when both conditions are met simultaneously - for example, after 500 hours AND at least 3 months have passed. This prevents over-maintenance on low-utilization assets while still enforcing a maximum service interval.
Setting up both trigger types in a preventive maintenance platform is straightforward when your CMMS supports dynamic scheduling.
Cryotos CMMS supports both static (time-based) and dynamic (usage-based) PM schedules natively, including Either/Or and And combined trigger logic, IoT meter integration, and automated work order generation. See how Cryotos helps maintenance teams schedule smarter and reduce unplanned downtime by up to 30%.
Time-based maintenance triggers service at fixed calendar intervals regardless of how much the asset was used. Usage-based maintenance triggers service when the asset reaches a specific activity threshold - operating hours, miles, or production cycles. Usage-based is more accurate for wear-driven failures; time-based is easier to administer and better suited for compliance-driven or age-degradation scenarios.
Usage-based maintenance works best on assets where wear directly correlates with operation: fleet vehicles, forklifts, CNC machines, compressors, generators, and production machinery with variable utilization.
Yes. Modern CMMS platforms like Cryotos support combined scheduling logic - you can configure a PM to trigger based on whichever condition is met first (Either/Or) or only when both conditions are satisfied simultaneously.
You risk over-maintaining during low-use periods (wasting labor and parts) and under-maintaining during high-use periods (increasing failure risk). Usage-based scheduling eliminates both issues.
Cryotos AI predicts failures, automates work orders, and simplifies maintenance—before problems slow you down.
