Usage-Based Maintenance (UBM) represents a move from ‘guessing’ to ‘knowing’ when your equipment needs attention. Rather than scheduling maintenance based on calendar intervals, this preventive maintenance strategy uses actual equipment utilization to trigger service activities. The approach relies on quantifiable metrics, such as operating hours, production cycles, or mileage, to determine maintenance timing. This strategy eliminates both over-maintenance and under-maintenance. It improves asset availability while reducing costs. In this piece, we’ll explore what usage-based maintenance is and how to implement it with best practices for maximizing equipment uptime.
What is Usage-Based Maintenance (UBM)?
Definition and Core Concept
Usage-based maintenance is a preventive maintenance strategy that schedules service activities based on the actual use of equipment rather than predetermined calendar intervals. This approach, also known as meter-based maintenance, relies on measurable metrics to determine when maintenance should occur. UBM triggers maintenance tasks only when an asset reaches a defined usage threshold, instead of servicing equipment every month or quarter whatever the amount of use.
The core concept centers on lining up maintenance intervals with actual wear. Equipment that sits idle for weeks doesn’t degrade the same way as machinery running continuously. UBM accounts for this reality and tracks equipment utilization through hour meters, cycle counters or distance measurements. You wouldn’t change your car’s oil every January. You change it every 5,000 miles because that mileage associates directly with oil degradation.
This strategy prevents both over-maintenance of lightly used assets and under-maintenance of heavily used equipment. Basing maintenance on actual use means you perform service activities when they’re needed instead of intervening too early or waiting too long and encountering unexpected breakdowns. UBM treats equipment according to its workload and makes maintenance more responsive to conditions on the ground.
How UBM Is Different from Time-Based Maintenance
Time-based maintenance follows a fixed schedule whatever the amount a machine has been used. A commercial fleet might change the oil in each vehicle on the first of every month, even if some trucks drove 500 miles while others drove 5,000 miles during that period. This calendar-based approach treats all equipment the same and schedules maintenance based on absolute time elapsed since the last activity.
Usage-based maintenance triggers service tasks when an asset reaches a specific value unit, such as miles driven or parts produced. That same commercial fleet would track miles driven and change oil in each truck when it reaches 3,000 miles. The maintenance activity generates when equipment reaches a defined usage milestone. A truck used rarely might go three months between oil changes. A heavily used truck might need service every two weeks.
The scheduling trigger itself is where the difference lies. Calendar-based maintenance asks “how much time has passed?” Usage-based maintenance asks “how much has this equipment worked?”. This difference affects maintenance timing, spare parts consumption and equipment availability directly. Scheduling maintenance around measurable use rather than arbitrary dates means you avoid servicing equipment that hasn’t accumulated enough wear to justify intervention.
Key Metrics Used in UBM
Usage-based maintenance programs track several metrics to determine when service is required. Operating hours represent the most common measurement and calculate the total time equipment has been running. Hour meters track both uptime (activity time) and downtime (inactivity time), providing accuracy on when maintenance should proceed.
Production cycles measure how many times a machine completes its operational sequence. A CNC machine might be serviced after every 1,000 operating hours. A conveyor belt could be inspected every 200,000 cycles. Mileage or distance-based metrics apply to mobile equipment and vehicle fleets, tracking total miles or kilometers traveled.
Additional metrics include temperature limits and downtime duration, which help maintenance teams identify possible failures that jeopardize production performance and quality. Energy consumption serves as another indicator of equipment utilization for machinery where power usage associates with wear patterns. These measurements are different from condition-based maintenance, which monitors the physical health of equipment through sensors measuring vibration or temperature deviations. UBM measures usage, not the actual condition of equipment. The difference matters because UBM requires sensors or hour meters to track asset utilization, along with a computerized maintenance management system to record readings, configure usage thresholds and trigger work orders when those thresholds are reached.
How Usage-Based Maintenance Works
Implementing usage-based maintenance requires a systematic approach that connects equipment monitoring with your maintenance management system. The process begins with establishing meters for critical assets and ends in automated work order generation when usage thresholds are reached.
Setting Up Meter Readings
The first step involves setting up meters in your CMMS for each asset you want to monitor. This setup requires three core pieces of information: the asset’s name, the unit of measurement (hours, cycles, miles), and how frequently readings should be recorded. Your CMMS becomes the central repository where all meter configurations live and where usage data flows in for analysis.
You can record meter readings through several methods. Enter readings manually using the Enter Readings page in your CMMS, import data through REST API integrations, or use file-based data imports. Many modern facilities connect meters directly to software platforms that track and total usage data automatically. Technicians upload readings via smartphone or tablet apps while on-site or working remotely for mobile equipment. Some organizations import meter data from spreadsheets into their CMMS, which then generates usage-based work orders automatically.
Recording frequency matters substantially. You can log readings daily, multiple times per day, or only when maintenance is completed, depending on your business requirements and asset activity. More frequent recordings provide better accuracy for forecasting future maintenance due dates. The system uses the last reading of that day for forecasting programs if multiple readings occur in a single day.
Several validation rules govern meter recording. You must record new readings sequentially by date and time, though you can enter historical readings out of sequence during data correction. The system calculates a net change value from the last reading in history, maintains a displayed reading value, and tracks a cumulative life-to-date reading. The system never permits duplicate readings by date and time for active meters.
Defining Usage Thresholds
Usage thresholds determine when maintenance activities should occur. You typically define these limits based on manufacturer recommendations or historical data from similar assets. OEM guidance provides service intervals based on extensive testing and failure analysis, making them excellent baseline settings while you collect your own operational data.
Thresholds should account for your operating environment. Temperature extremes, dust, moisture, or corrosive atmospheres can accelerate wear and require tighter intervals than standard recommendations. Configure alerts at two levels for optimal results: a warning threshold at about 80% of the service interval gives your team time to prepare parts and labor. The critical threshold at 100% of the interval triggers the actual work order. This two-tier approach prevents situations where assets exceed safe service windows because of delays in scheduling, parts procurement, or technician availability.
Triggering Maintenance Activities
The system monitors usage data continuously against configured thresholds once it flows into your CMMS. The maintenance management system triggers notifications to the maintenance team when an asset approaches its predetermined usage limit. This automatic alerting eliminates the need for manual monitoring and ensures timely intervention.
Work orders generate automatically when thresholds are reached. Your CMMS identifies the trigger asset (the equipment being monitored) and the trigger meter (which meter reading controls the schedule). Only one asset triggers the due dates, even if multiple assets are linked to the same maintenance record. The system populates current meter reading, last meter reading date, asset usage, frequency, and interval data automatically once you define the trigger asset and meter.
Tracking and Recording Data
Continuous data collection builds a historical record that is a great way to get insights for analysis. Each recorded reading has not only the reading value itself but also the calculated net change from the last reading, the displayed reading value, and the cumulative life-to-date reading. This historical record lets maintenance managers assess repair effectiveness and determine whether maintenance needs adjustment to earlier or later intervals.
We need regular meter reading updates when using meter-based scheduling. Your next due dates will slip without consistent updates because the system assumes no usage has occurred. You might also be surprised by preventive maintenance coming due unexpectedly. Scheduling a weekly work order for staff to collect and enter meter readings ensures data remains current and accurate.
The recorded data creates an asset history that improves maintenance planning over time. Runtime data offers live insights into equipment condition in ways other data cannot. This information helps you visualize usage trends, adjust thresholds as needed, forecast required tools and parts for upcoming maintenance, and generate reports for more informed decisions.
UBM vs. Other Maintenance Strategies
Think over two similar pumps operating at the same facility. Pump A runs 10 hours daily while Pump B operates only 2 hours per day. The manufacturer recommends an oil change every 500 operating hours. Under a time-based schedule, both pumps receive service every 60 days. Pump A reaches 600 hours by then (overdue for maintenance), whereas Pump B logs only 120 hours (over-maintained by more than 4x). Usage-based maintenance solves this inefficiency: Pump A triggers service at 50 days, Pump B at 250 days. Each asset receives attention when needed, not when the calendar dictates.
Usage-Based vs. Time-Based Maintenance
Time-based maintenance schedules tasks at regular calendar intervals whatever the actual equipment use. This approach works well for assets with consistent, predictable usage patterns. You might lubricate pumps every seven days or inspect machine sealant every two years. These predetermined schedules get set without equipment utilization in mind.
Calendar-based intervals often lead to servicing machines that haven’t accumulated enough wear to justify intervention. The approach wastes labor and spare parts. Components that retain substantial service life get replaced. Organizations that implement usage-based maintenance reduce spare parts inventory costs by 15-20%. Better planning and avoiding premature replacement make this possible.
Usage-based preventive maintenance triggers tasks after equipment reaches defined operating hours, production cycles, or batches processed. This method relies on predictable wear patterns. Service gets initiated when runtime meters hit predetermined thresholds rather than waiting for calendar dates. The trigger becomes “every 500 operating hours” instead of “every three months.” Maintenance actions arrange with actual equipment degradation.
Usage-Based vs. Condition-Based Maintenance
Condition-based maintenance performs work when equipment shows early signs of wear or abnormal behavior. Rather than relying on estimates or fixed schedules, CBM uses vibration analysis, temperature monitoring, load tracking and performance metrics to detect emerging issues. Teams act on condition changes that continuous sensor monitoring captures.
Usage-based maintenance is different in what it measures. UBM tracks usage metrics, not the actual physical condition of equipment. You monitor operating hours or cycles, not vibration levels or temperature deviations. Organizations that implement condition-based maintenance report reducing maintenance costs by 8-12% compared to traditional preventive approaches.
The data requirements are different between strategies:
| Strategy | Trigger | Data Required | Best Fit |
|---|---|---|---|
| Failure-Based (FBM) | Asset fails | None required upfront | Non-critical assets where failure cost is low |
| Time-Based (TBM) | Calendar interval | Manufacturer schedule | Assets with consistent, predictable use |
| Usage-Based (UBM) | Operating hours, cycles, or utilization metric | Hour meter or usage sensor + CMMS | Assets with variable utilization at shifts or sites |
| Condition-Based (CBM) | Sensor deviation from defined threshold | Continuous monitoring (vibration, temperature, etc.) | Assets where wear is driven by load or environment, not usage alone |
CBM demands reliable sensor inputs, system integrations and personnel capable of interpreting asset health data. The upfront investment in instrumentation runs higher than simpler preventive approaches. Usage-based approaches work when only runtime data or cycle counters are available. This makes the strategy available to teams without extensive condition monitoring infrastructure.
Usage-Based vs. Failure-Based Maintenance
Failure-based maintenance addresses equipment issues as they arise. Repair happens after failure occurs. This reactive approach carries higher risk than preventive strategies. Equipment operates until it breaks before corrective tasks get performed.
Usage-based maintenance belongs to the preventive maintenance category. Service executes after a given time of equipment use and catches breakdown events before they happen. The Eindhoven University of Technology has both models within its maintenance management framework. The university notes that for old assets with predictive indicators, inspection based on usage proves most recommended.
Types of Usage-Based Maintenance
Usage-based maintenance shows up in several distinct forms that line up with how equipment accumulates wear. The type you implement depends on what your assets measure and how usage translates into component degradation.
Hour-Based Maintenance
Operating hours serve as the foundation for maintenance scheduling in industries where runtime relates to wear. Equipment contains PLCs that count operation hours, and manufacturers provide guidance about which maintenance tasks should occur at specific intervals. You might change lubricants, inspect systems or replace parts based on elapsed hours rather than calendar dates.
Maintenance manuals specify service requirements every 150, 300 or 500 hours of operation. The hourmeter becomes your scheduling tool and ensures equipment availability by preventing over-maintenance that drives up costs and inflates inventory levels. This approach works well for yellow machinery, mining equipment, construction assets and medical devices.
Data capture happens in two ways. Manual interaction involves operators or technicians who record elapsed hours through daily inspections or mobile CMMS platforms. Automated capture uses communication protocols where the meter feeds information to your CMMS or software process. The platform then generates notifications and work orders that correspond to your maintenance plan programming.
Cycle-Based Maintenance
Machine cycles offer a more precise alternative to calendar-based scheduling. You can launch preventive maintenance based on actual machine cycles rather than servicing equipment on random dates. This works well in discrete manufacturing industries where you build parts and count those parts throughout the day.
The advantage lies in your ability to relate different data points. You can watch for condition changes as equipment approaches expected failure points when you know the mean time between failure and have calculated cycle counts. If failures occur without corresponding cycle counts, you adjust either your cycle thresholds or your condition monitoring processes. Cycle counting allows you to see when failures should happen and relate multiple data streams together.
Mileage and hours both qualify as cycles. The biggest problem surfaces when you cannot capture cycles in a meaningful way. Manual data collection from shop floor personnel introduces margin for error, whereas automated systems eliminate that uncertainty.
Mileage or Distance-Based Maintenance
Vehicle fleets and mobile equipment rely on distance traveled as their main usage metric. Car maintenance schedules follow mileage milestones based on decades of automotive engineering research. Most manufacturers recommend a 30-60-90 maintenance plan and perform specific tasks at 30,000, 60,000 and 90,000 mile intervals.
Specific maintenance windows include oil and filter changes every 3,000 to 7,000 miles, air filter replacement between 15,000 and 30,000 miles, and fuel filter changes around 25,000 miles. Brake components need checking after 30,000 miles. Pads require replacement around 50,000 miles and rotors between 50,000 and 70,000 miles. Power steering fluid changes occur every 50,000 miles based on manufacturer recommendations.
Mileage remains the most common factor that determines automotive maintenance needs because it serves as the main indicator dictating maintenance necessities throughout a vehicle’s life. This metric works well for any mobile asset where distance relates to component wear.
Production Volume-Based Maintenance
Production volume measures the number of products a company manufactures during a specific period. Maintenance teams trigger service activities based on units produced, cycles completed or total production output. Manufacturing facilities track this metric using spreadsheets or manufacturing execution systems. Production managers monitor the data to ensure appropriate pacing.
This approach ties maintenance to actual output rather than estimated usage. Specific wear thresholds are met when equipment produces 10,000 units, regardless of how many days or weeks that production required.
When to Use Usage-Based Maintenance
Not every asset benefits from usage-based maintenance. Your first step involves identifying where this strategy will make a difference. Assets suited for usage-based preventive maintenance share specific characteristics that make them ideal candidates for meter-based scheduling rather than calendar-based intervals.
Equipment with Variable Usage Patterns
Assets that experience inconsistent utilization across different periods present the strongest case for usage-based maintenance. Equipment heavily used during some shifts and idle during others makes calendar-based schedules inefficient. A backup generator that runs occasionally shouldn’t follow the same maintenance timeline as a primary unit operating without interruption.
So scheduling maintenance based on actual runtime ensures you address wear with precision. The approach prevents situations where lightly used equipment receives unnecessary service while heavily used assets go too long between interventions. Variable usage patterns create the exact scenario where time-based schedules fail and make usage-based maintenance the logical alternative.
Assets with Built-In Usage Meters
Equipment with integrated hour meters, cycle counters, or other usage tracking capabilities provides the foundation for reliable usage-based maintenance. These built-in monitoring systems eliminate guesswork and supply accurate data your maintenance management system needs. Look for displays showing usage metrics or mechanical counters on your equipment.
Your maintenance teams must access this information on a regular basis for the strategy to work. Check equipment manuals and spec sheets for references to built-in counters, data ports, or OEM-recommended usage-based PM intervals. Sensorized control panels and physical hour meters indicate an asset supports usage tracking.
High-Value Mobile Equipment
Vehicles and construction equipment with considerable maintenance costs represent prime candidates. Fleet management operations rely on odometer readings and engine hours to maintain vehicles. Construction companies track operating hours on excavators and bulldozers to schedule maintenance based on actual usage rather than arbitrary calendar time.
Aircraft maintenance depends on flight hours and cycle counts, similar to how mining equipment follows operating hours or material processed. The substantial investment in these assets, coupled with high repair costs, justifies the effort required to track usage metrics closely. Mobile equipment’s built-in monitoring systems make data collection straightforward.
Manufacturing and Production Machinery
Production equipment where wear relates to production volume or operating cycles works well with usage-based maintenance. Manufacturing operations track machine cycles and run times to schedule maintenance based on actual usage. Pumps operating in predictable production cycles and CNC machines benefit from this approach.
Healthcare facilities track usage metrics of medical equipment to ensure maintenance and reliability. Energy and utilities sectors monitor equipment like turbines and generators using runtime and condition metrics. Production counts provide more accurate wear indicators than elapsed time in this case and make usage-based scheduling the preferred strategy.
Benefits of Usage-Based Maintenance
Operational efficiency improves measurably once maintenance lines up with actual equipment wear rather than arbitrary schedules. Usage-based maintenance delivers quantifiable advantages that affect your maintenance budget, asset reliability, and production continuity.
Prevents Unexpected Breakdowns
Up-to-the-minute monitoring through usage-based maintenance identifies early warning signs before failures occur. Track actual utilization and maintenance teams detect subtle changes in performance that precede failures, such as increased vibration or heat after a specific number of cycles. This early detection minimizes downtime and helps you avoid operational disruptions that get pricey.
Predictive analytics provide alerts based on performance trends and allow immediate servicing that prevents minor issues from escalating into major failures. You intervene proactively by replacing worn components like belts or bearings before they snap or seize. This turns a potential catastrophe into a routine repair. Tracking usage gives you an indication of the time machines need help and reduces the chances of breakdowns.
Extends Equipment Lifespan
Timely maintenance based on real performance conditions maximizes machinery lifespan. Lubrication and component replacements happen precisely at the time needed and prevent excessive degradation caused by delayed servicing. Regular care through usage-based maintenance ensures engines run cleaner and motors stay cooler. This reduces the need to replace expensive assets.
Purchasing new equipment carries big costs that proper maintenance avoids. Keep equipment in optimal condition through accurate usage tracking and the lifespan extends considerably. This reduces capital expenditure on replacements. Maintenance up to date along with monitoring increases the chances of extending equipment lifespan.
Reduces Maintenance Costs
Usage-based maintenance reduces overall maintenance costs by 18-25% compared to traditional approaches. Perform maintenance only at the time specific machinery needs it. You reduce the risk of unexpected equipment failure and unplanned downtime while avoiding expenses related to unnecessary parts replacement. Research shows that 30% of maintenance activities are scheduled too often and contribute to waste in the maintenance budget.
Emergency repairs typically cost 3-5 times more due to premium parts pricing, overtime labor costs, and additional shipping fees. You eliminate expenses linked to premature component replacements and reduce emergency repair costs associated with sudden breakdowns. This targeted approach brings fewer maintenance expenses overall and better resource allocation.
Improves Asset Availability
Establishing a usage-based maintenance strategy guarantees assets remain in operation under safe conditions. You maximize asset availability by knowing exactly what is happening to machinery through continuous usage tracking. Equipment stays in peak condition and ensures continuous operations without unexpected interruptions.
Reduced downtime improves machine reliability and brings consistent output. This supports better workforce planning by avoiding sudden equipment failures. Production schedules become predictable rather than volatile once data dictates maintenance.
Eliminates Over-Maintenance and Under-Maintenance
Usage-based maintenance strikes the optimal balance by accounting for actual equipment usage. Over-maintained assets receive preventive maintenance too frequently and waste labor and parts on unnecessary expenses. Under-maintained assets have interval frequencies too low to enable failure detection or prevent equipment breakdowns. This results in unplanned production shutdowns.
This approach eliminates 20-35% of over- and under-maintenance events by lining up maintenance spend with actual asset utilization. UBM contributes to environmental sustainability by optimizing resources and consuming fewer unnecessary parts. It minimizes waste from replacing items prematurely and lowers energy consumption associated with excessive maintenance.
Steps to Implement a Usage-Based Maintenance Program
Transitioning from planning to execution requires a structured roadmap. The following steps guide organizations through building a usage-based maintenance program from the ground up.
Identify Critical Assets
Criticality analysis determines which assets warrant usage-based maintenance attention. This assessment evaluates potential risks and emphasizes business impacts associated with equipment failures. You start by agreeing on a risk matrix that identifies levels of risk and corresponding business value, then accomplish an accurate record of equipment hierarchies showing which assets potentially affect other assets.
Assets are evaluated based on five criteria: maintenance requirements, operational costs, environmental impact, safety risks, and quality implications. Organizations designate the top 10-20% as critical assets requiring priority maintenance efforts. Focus on equipment where failure would substantially disrupt operations, create safety hazards, or generate substantial financial losses.
Set Up Monitoring Systems
Different monitoring approaches suit different operational environments. Telematics solutions and mobile tracking apps transmit data over mobile networks, integrating into dashboards where managers view live information. IoT sensors monitor equipment conditions continuously, while some facilities rely on manual technician entries via smartphone or tablet.
Several integration methods feed data to your CMMS. API integrations make communication between software systems easier and can be customized to fit unique requirements. Connect2Asset software pulls meter readings from PLC machines, building automation systems, and SCADA systems automatically, moving data directly to the CMMS. Or you can import meter readings from spreadsheets.
Configure Usage Thresholds in CMMS
Configure alert thresholds at two levels: warning thresholds around 80% of service intervals give teams time to prepare, while critical thresholds at 100% trigger actual work orders. This prevents assets from exceeding safe service windows due to scheduling delays or parts procurement lead times.
Create Automated Work Orders
Set up rules for automatic work order generation when predetermined threshold levels are met. The CMMS identifies specific assets from sensor-to-asset mapping, attaches maintenance history, checks parts availability, selects priority levels based on asset criticality, identifies optimal technicians based on skill and location, and sets scheduling windows.
Review and Adjust Intervals
After 3-6 months of data collection, compare actual failure history against configured thresholds. Tighten thresholds if assets fail before reaching service intervals consistently. Extend thresholds if no issues occur well beyond intervals. This calibration separates mature usage-based maintenance programs from static preventive schedules.
Best Practices for Usage-Based Maintenance
Success with usage-based maintenance requires ongoing attention beyond the original setup. These practices separate programs that deliver results from those that stagnate.
Establish Accurate Usage Thresholds
OEM guidance serves as your baseline. Manufacturers provide service intervals based on extensive testing. This makes them excellent original settings while you collect operational data. Convert time-based OEM recommendations into usage equivalents when you need to.
Implement Reliable Monitoring Tools
Manual logging remains viable when automation isn’t feasible. Operators can record daily or weekly readings from counters or gages digitally or on paper. Many machines already contain hour meters and cycle counters or sensors. PLC or SCADA systems offer valuable usage data sources.
Train Your Maintenance Team
A move from calendar-based to usage-based maintenance requires a mindset alteration. Maintenance managers should explain why the alteration matters and how it improves reliability. Encourage technicians to report whether maintenance activities were early, late, or appropriate. Then adjust thresholds so.
Analyze Historical Data
After 3-6 months, compare actual failure history against configured thresholds. Tighten thresholds if assets fail before reaching service intervals consistently[624]. Extend thresholds if no issues occur well beyond intervals[624].
Continuously Optimize Your Program
Usage-based maintenance is a continuous process. Regular reviews identify improvement opportunities. Set up review meetings with operators, technicians, and managers to learn about program effectiveness.
Conclusion
Usage-based maintenance changes guesswork into precision by scheduling service activities around actual equipment utilization. This approach delivers measurable results when you implement reliable monitoring systems and configure accurate thresholds based on operational data.
Identify your critical assets with variable usage patterns. Set up meters and automated work orders in your CMMS. The configuration requires effort upfront, but you’ll see reduced maintenance costs and fewer unexpected breakdowns.
Note that optimization never stops. Review your thresholds and adjust intervals based on failure history. Your program will continue delivering better results over time.