Calendar-based PM services equipment on a date. Usage-based PM services it on the miles, hours or cycles it actually ran. Keep the calendar for inspections, seasonal work and steady-use assets, and move critical assets with uneven use to usage triggers. Most good programs run both.
You know the drill. The PM list says the loader is due for service, so a tech pulls it in, changes oil that’s barely dark, and signs off. Meanwhile the truck that picked up a second route is 2,000 miles past due, and nothing on the calendar says so. Your PM compliance number looks great. Your backlog doesn’t. And when that truck goes down, nobody upstairs is going to ask what the PM compliance was.
This one is for the people who own the PM program: maintenance managers, reliability engineers and the techs turning the wrenches. We’ll cover when the calendar is the right trigger, when usage is, how to run both, and how to make the case to the people who sign off on the budget.
Calendar-Based PM: Why You Started There
Calendar PM fires on a fixed interval: weekly, monthly, quarterly, annually. It doesn’t care what the asset did in between.
You started there for good reasons:
- It’s easy to plan. You can staff for it in January.
- It lives in a spreadsheet. A due date is a due date.
- Some failure modes really are about time. Elastomers crack, fluids break down and inspections come due whether the machine ran or not.
The trouble starts when the calendar is standing in for wear. Then your interval is a guess about utilization, and your PM program is only as good as that guess.
Usage-Based PM: Trigger on the Work Done
Usage-based PM, also called meter-based or runtime-based PM, fires when an asset crosses a usage threshold. Pick the meter that actually tracks wear on that asset:
- Miles on trucks, vans and service vehicles
- Engine hours on loaders, mowers, generators and small engines
- Cycles or counts on presses, fillers and packaging lines
- Throughput or run hours on crushers, screens, conveyors and chillers
The PM lands when the equipment has done enough work to need it. Not before, and not three weeks after.
| Calendar-based PM | Usage-based PM | |
|---|---|---|
| Triggered by | A date or fixed time interval | Miles, engine hours, cycles or run hours |
| Best for | Compliance inspections, seasonal work, time-driven failure modes, steady-use assets | Critical assets with uneven utilization, OEM specs in hours or miles |
| What it needs | A due date | Meter readings taken at the asset and something watching the thresholds |
| Main risk | Wasted wrench time on idle assets, missed service on busy ones | Missed or guessed readings |
| Works in a spreadsheet? | Yes | Not well. A spreadsheet stores readings but won’t flag a crossed threshold |
Where the Calendar Costs You
You burn wrench time on equipment that didn’t run
The standby generator, the seasonal mower and the spare forklift all get full service on schedule. That’s tech hours and parts spent on wear that never happened. It’s also wrench time pulled away from the backlog that’s actually hurting you.
Your hardest-working assets go past their real interval
This is the expensive one. A canning line in peak season, a crusher on extra shifts, a truck on a doubled route: they all blow past their true service interval long before the calendar flags them. The PM was “on time.” The failure happened anyway, and now it’s a reactive job on your worst day.
OptiAM’s own figures put a manufacturing line down at $50,000 an hour, a brewery packaging line at $25,000 an hour, and a commercial HVAC failure at $10,000 an hour. Your numbers will be different. The pattern won’t be. The assets the calendar under-serves are usually the ones you can least afford to lose.
You can’t see your real failure intervals
If everything runs on the calendar, your history is tied to dates, not to the work the asset did. When a bearing fails you can’t tell whether the interval was wrong or the machine just ran twice as many hours as last year. That makes it hard to tune intervals, trust your MTBF or tie a failure mode back to the task that was supposed to prevent it.
When the Calendar Is Still the Right Call
The calendar isn’t wrong. It’s the wrong tool for some jobs. Keep it for:
- Compliance and safety inspections. Fire systems, elevators, pressure vessels and anything a code or auditor sets by date.
- Time-driven failure modes. Hoses, belts, seals, batteries and fluids that age even when they sit.
- Seasonal work. HVAC changeover, irrigation winterization and pre-season tune-ups.
- Steady-use assets. If an air handler runs about the same every week, time and usage track each other closely enough.
- Anything you can’t meter reliably. A sensible date beats a reading nobody takes.
If your program is small and utilization is steady, a well-kept calendar PM schedule may be all you need right now. Say so, and spend your effort where it pays.
When to Move a Task to Usage
Move a task to usage when:
- Utilization swings a lot by season, shift pattern or route
- The asset is critical and downtime hits production, customers or tenants
- The readings already exist, like odometers, hour meters or cycle counters
- The OEM spec is in hours or miles, not months
- Your history shows failures between PMs, or PMs on parts that look new every time
Most Good Programs Run Both
Mix them, often on the same asset:
- Fleet truck: oil and filters by miles, annual inspection by date
- Loader or mower: service by engine hours, pre-season inspection by date
- Packaging line: wear parts by cycle count, guard inspection weekly
- Chiller: service by run hours, refrigerant and code inspections by date
Use “whichever comes first” (for example, every 250 hours or 6 months). Usage drives the busy assets. The calendar catches the ones that sit.
What It Takes to Make Usage-Based PM Work
Meter readings your techs will actually take
Usage PM is only as good as the readings. If techs have to walk back to the shop to log hours, they won’t, or they’ll guess. Readings have to be captured where the equipment is.
Something watching the thresholds
A spreadsheet can store a reading. It won’t tell you loader #4 just crossed 500 hours. For most teams, this is where Excel stops working for PM.
Work orders that arrive ready to work
When a threshold trips, the tech should get the work order with the tasks, checklist and parts already attached. A reminder that sends them digging for the procedure isn’t enough.
Is your PM schedule outgrowing Excel?
Take the 2-minute CMMS vs. Excel check and see whether a spreadsheet can still keep up with your PM program, or whether it’s time for a system that watches the meters for you.
How to Pitch Usage-Based PM to Your Boss
You already know the calendar is wasting wrench time and missing failures. Your plant manager, ops director or CFO needs to hear it in their terms. Here’s how to frame it.
Lead with downtime, not maintenance
Leadership doesn’t buy PM intervals. They buy uptime. Start with your critical assets and what an hour down costs in lost output, idle crew and late orders. Use your own numbers if you have them. If you don’t, OptiAM’s own figures ($50,000 an hour for a manufacturing line, $25,000 for a brewery packaging line, $10,000 for a commercial HVAC failure) show the scale. Label them as OptiAM’s figures, not yours. The CMMS savings calculator will run the math on your own inputs.
Show the labor you’re wasting
Pull last year’s PMs on low-use and standby equipment. Count the tech hours. That’s labor you can move to backlog and reliability work without adding headcount. Finance understands reallocated labor.
Show the parts spend
Filters, oil and wear parts replaced on schedule but not on need are spend you can cut. Parts replaced too late show up as emergency orders and expedited freight. Your purchasing history has both.
Frame the risk and compliance side
Usage-based PM doesn’t drop your date-driven inspections. They stay on the calendar. What leadership gets is a defensible record that every critical asset was serviced on the work it did, which is a stronger story for auditors, insurers and customers than “it was on the schedule.” If audits are a pain point, the maintenance audit readiness check shows where your records stand.
Ask for a pilot, not a program
Don’t pitch a plant-wide overhaul. Ask to put your five most critical assets on usage triggers, run them for a few months, and report back on PMs skipped, failures caught and downtime avoided. Small ask, measurable result, easy yes. If you want a baseline first, the Maintenance Maturity Scorecard takes two minutes.
The one-line version
“We’re spending tech hours on equipment that didn’t run and missing service on the equipment that did. I want to schedule PM on actual usage for our critical assets, starting with a pilot, so we cut wasted labor and parts and stop paying for downtime we could have prevented.”
How OptiAM Handles It
OptiAM’s Maintenance Optimizer schedules work on actual asset usage, not arbitrary calendars. You set the usage trigger in Task Developer. When the trigger is met, Maintenance Optimizer generates the work order with its tasks and inspections attached. Calendar tasks run alongside, so compliance inspections still come due by date.
Readings come from the field through OptiAM GO. It runs on iOS, Android and Windows tablets with full offline capability, so techs can log readings, complete checklists and close work orders at the asset, whether that’s a quarry, a back lot or a basement mechanical room with no signal. It syncs when the device reconnects.
For reliability engineers, the RCM Analyzer finds likely failure modes on your critical equipment, ranks them by consequence and builds the PM plan that prevents them. The method comes from aviation. Andromeda Systems, which builds OptiAM, has supported NAVAIR and the F-35 program since 2005. You don’t have to be the military to use it. The software was built for breweries, quarries and plant floors.
Where to Start
1Pick your five most critical assets
2Choose the right meter for each
Miles, hours or cycles.
3Check the OEM interval
Compare it against your own failure history.
4Set “whichever comes first” triggers
So nothing slips while you learn.
5Review after a few months
Tighten or loosen intervals based on what you find at each PM.
Leave the rest on the calendar. Expand once the readings are flowing.
Frequently Asked Questions
What is the difference between usage-based and calendar-based PM?
Calendar-based PM triggers maintenance on a fixed time interval, like every 3 months. Usage-based PM triggers it when an asset crosses a usage threshold, like a set number of miles, engine hours or cycles. Calendar PM tracks time. Usage PM tracks the work the equipment actually did.
Is meter-based PM the same as usage-based PM?
Yes. Meter-based, runtime-based and usage-based PM all mean the same thing: the PM is scheduled off a meter reading such as miles, hours or cycles instead of a date.
What does “whichever comes first” mean in PM scheduling?
It puts two triggers on one task, one usage and one time, for example every 250 hours or 6 months. The PM comes due at whichever limit is hit first, so busy assets get serviced on usage and idle ones still get serviced on time.
Which PM tasks should stay on a calendar schedule?
Compliance and safety inspections set by date, time-driven failure modes like hoses, belts, seals and batteries, seasonal work, steady-use assets, and anything you can’t meter reliably.
How do I justify usage-based PM to management?
Lead with downtime cost on your critical assets, then show the tech hours and parts spent on low-use equipment last year. Ask for a pilot on your five most critical assets and report back on PMs skipped, failures caught and downtime avoided.
Can you run usage-based PM in a spreadsheet?
You can store readings in a spreadsheet, but it won’t tell you when an asset crosses its threshold or generate the work order. Once you have more than a handful of metered assets, most teams move PM into a CMMS that watches the readings for them.
The Bottom Line
The calendar is easy, and for inspections, seasonal work and steady-use equipment it’s the right trigger. But it can’t tell a truck that sat from a truck that ran. Schedule your critical assets on the work they actually did, and you get wrench time back, stop throwing parts at equipment that didn’t need them, and catch failures before they catch you.
Book a 30-minute walkthrough
We’ll use your assets, your locations and your real maintenance workload. No slide deck. Bring your techs to see the mobile side, and bring your plant manager or ops director so they can see the case for themselves. Or call 904-402-8641.
