A preventive maintenance schedule is easy to write and hard to keep alive. Most teams build a comprehensive plan in their first month with a new CMMS — and watch it slowly fall apart over the next year as PMs get skipped, deferred, or quietly retired without anyone noticing.
The problem isn’t ambition. It’s the absence of a feedback loop.
Start with criticality, not coverage
The temptation is to build a PM for every asset. Resist it. Rank assets by impact-of-failure and start with the top tier. A focused schedule that the team executes reliably beats a comprehensive one they ignore.
Borrow before you build
For most equipment classes — pumps, motors, HVAC, conveyors — there are well-published PM templates from manufacturers and reliability associations. Start with the manufacturer’s recommendation, adjust for your operating environment, and refine from there. Reinventing every PM from scratch is one of the fastest ways to burn out a planner.
Make the task list executable in the field
A PM that says “inspect bearings” is useless. A PM that says “with a stethoscope, listen at points A and B for grinding or chirping; record any abnormal sound; replace if vibration exceeds 0.15 ips” is a job a technician can do consistently. The CMMS mobile app is the place to enforce this — checklist items, photo capture points, threshold prompts.
Track PM yield, not just compliance
Compliance tells you the work happened. Yield tells you whether it mattered. If 100 PMs ran on a class of equipment and only 5 found a defect, you’re spending too much time on those PMs. Stretch the interval, change the technique, or move to a condition-based trigger.
Re-plan, don’t just re-execute
Once a quarter, take 60 minutes with the team to look at three things: PMs that get skipped, PMs that find nothing, and failures that happened despite the PM. Each of those is a signal. The schedule should evolve every quarter, not stay frozen for years.
Tags
Writes about CMMS, reliability and operations excellence at UniCMMS.
Discussion
0 comments — join the conversation.