Meter-Based Maintenance: When Usage-Based PM Beats Calendar PM
Meter-based maintenance schedules work from running hours, cycles, kilometers, or production count so service happens when equipment usage justifies it.
Meter-based maintenance schedules work based on actual equipment usage instead of calendar time.
Instead of servicing a machine every month, the team services it after a defined number of running hours, cycles, kilometers, strokes, batches, or units produced.
This approach is useful when wear depends more on usage than time.
Simple example
Two identical machines are installed in the same plant. One runs three shifts every day. The other runs only during peak demand.
If both machines receive the same monthly PM, one may be under-maintained and the other may be over-maintained.
Meter-based maintenance solves this by asking: How much work has the asset actually done?
Common meter types
Plants use different meters depending on the asset:
- Running hours
- Loaded hours
- Production cycles
- Stroke count
- Kilometers
- Compressor hours
- Pump operating hours
- Number of starts
- Batch count
- Energy consumption
- Flow volume
The meter should reflect the condition that drives wear.
Where meter-based maintenance works well
Meter-based PM is useful for:
- Compressors
- Forklifts
- Fleet assets
- DG sets
- Pumps
- Presses
- Packaging machines
- Conveyors
- HVAC equipment
- Rotating equipment with usage variation
It is especially useful when operating hours vary between assets or production areas.
Meter-based versus time-based maintenance
Time-based maintenance is useful for compliance routines, safety checks, cleaning schedules, and tasks where calendar time matters.
Meter-based maintenance is better when usage drives wear.
For example, a filter may not need replacement every month if the machine barely runs. But a heavily used asset may need service earlier than the calendar suggests.
The best plants often use both methods. Some tasks remain time-based, while usage-driven tasks become meter-based.
How to set meter thresholds
Start with one of these sources:
- OEM recommendation
- Historical failure data
- Technician experience
- Criticality of the asset
- Operating conditions
- Warranty requirement
- Safety or quality risk
Then improve the threshold over time.
If failures happen before the due reading, reduce the interval or improve inspection steps. If PMs are repeatedly done with no findings and no risk, review whether the interval is too conservative.
Common mistakes
The biggest mistake is capturing readings but not using them to trigger work.
Other mistakes include:
- Choosing the wrong meter
- Entering readings inconsistently
- Not validating abnormal readings
- Setting thresholds without reviewing failures
- Ignoring asset criticality
- Not linking readings to PM work orders
- Allowing overdue meter-based work to stay hidden
Meter-based maintenance only works when readings are reliable and action is triggered at the right point.
Practical workflow
A simple workflow looks like this:
- Select assets where usage drives wear.
- Define the correct meter type.
- Capture the current reading.
- Set the service interval.
- Calculate the next due reading.
- Generate a PM work order when the threshold is reached.
- Record the completed work and next due reading.
- Review failures and adjust intervals if needed.
This creates a maintenance plan that follows real equipment usage.
Where MaintBoard fits
MaintBoard supports meter-based maintenance by allowing teams to capture readings, define service intervals, generate PM work orders, and track maintenance history against the asset.
This helps supervisors see which assets are approaching due readings, which service work is overdue, and whether usage-based maintenance is reducing failures.
Meter readings also improve asset management because the asset history shows not only dates, but actual usage context.
What managers should review
Useful reports include:
- Assets due by meter reading
- Overdue meter-based PMs
- Reading history by asset
- Failure before due reading
- PM completed after threshold
- Usage pattern by asset
- Parts consumed per usage interval
These reports help managers avoid both over-maintenance and under-maintenance.
Bottom line
Meter-based maintenance is valuable when equipment wear follows usage.
It helps maintenance teams move beyond fixed calendars and service assets based on real work done. The key is to choose the right meter, capture reliable readings, and make sure readings create maintenance action.
Frequently asked questions
- What is meter-based maintenance?
Meter-based maintenance triggers work based on actual usage such as runtime hours, cycles, mileage, production count, pressure cycles, or energy consumption.
- When is meter-based maintenance better than calendar PM?
It is better when equipment usage varies. High-use assets need service sooner, while low-use assets may not need maintenance just because the calendar date arrived.
- What meter readings are useful for maintenance?
Useful readings include runtime hours, mileage, cycles, strokes, starts, pressure, temperature, flow, and energy consumption depending on the asset type.
- Can meter-based maintenance reduce unnecessary work?
Yes. It helps teams avoid over-maintaining lightly used equipment and prevents under-maintaining heavily used equipment.
- How does CMMS manage meter-based PMs?
A CMMS stores meter readings, compares them against thresholds, and generates work orders when the asset reaches the defined service interval.