Focus on Reliability

Are Your PMs Preventing Failures? 3 PM Effectiveness Checks

Written by Jeff Shiver, CMRP | November

At a food plant I visited, the PM compliance trend looked great. It averaged 97% for months on end. In a meeting later, the supervisors told me they consistently beat the corporation's 95% target.

Out in the production areas, I found bearing fittings with two, sometimes three, different colors of grease clumped on the same zerk. Mind you, this was a food plant where food-grade grease is required. Due to overgreasing, the seals were blown, and grease was thick around the shafts.

The equipment kept failing. The PMs didn't address the likely failure modes. The team was checking boxes, not preventing failures. No one was asking, "Are we doing the right work, or just doing work to meet the metric?"

Your PMs are already in the CMMS. Most are set up on a calendar: weekly, monthly, quarterly, annually. Each time the trigger comes up, the same tasks come out again for your technicians to do. Unless someone changes the work or the frequency, the next round comes out right on schedule. Before it does, find out whether the work coming out of the system is worth doing.

It isn't a new bill each round. It's your own technicians' time, already on the schedule. The question is whether that time goes to work that identifies potential failure conditions and addresses them.

Why PM compliance doesn't answer the question

One question I'm often asked is how to tell whether a PM program itself is effective. While we want 100% availability, it's not realistic for most. There are indicators. Some are readily apparent. Others take a little sleuthing to uncover.

PM compliance is one indicator, and it's where most plants stop. It tells you the PMs got signed off. It doesn't tell you whether they were the right PMs or done right.

We want 100% of PMs done, and we target 95%. Just be careful to understand what's getting done. When a PM mixes running tasks and shutdown tasks, and the equipment is always running, expect technicians to sign off the PM after doing only the running tasks. The compliance score looks great. Much of the PM never happened.

Sometimes the PM plan is a descriptive title with no detailed tasks. It's a placeholder, and the technicians are left to their own judgment about what to do.

Findings from RCM analysis show that 40% to 60% of PM tasks don't address the asset's likely failure modes. Those PMs consume labor and production downtime and don't prevent the failures you're paying for.

PMs can also cause failures. Every time we do intrusive maintenance, we disturb an otherwise stable system and introduce the potential for failure.

Three checks to run now

Pull these from the CMMS, assuming you have worked to ensure the work order system is properly utilized and good data exists.

1. How many PMs generated corrective work orders? Most PMs should be inspections that find equipment in the act of failure. When a technician finds a potential failure, they write a corrective work order so the repair can be planned and scheduled at the right time, with the parts on hand. If your technicians are fixing everything on the PM and not generating corrective work orders, there's very little backlog to plan and schedule. You're finding failures, not potential failures.

Count the PMs completed this year and how many led to a corrective work order. If your CMMS can't tell you, that's your first finding. Set up a work type for corrective work found on a PM or PdM activity, something like "CM from PM/PdM." It's how you show what the PM program is worth.

While you're in there, check what happened to the findings from your PdM routes and operator rounds. How many became completed work before the equipment failed? Data that comes in with no one acting on it doesn't prevent anything.

2. What failed right after a PM? List the failures over the last 90 days. For each one, check whether the asset had a PM in the days or weeks before. If production gave you a window for the PM and the equipment failed two days later, what did they get in return? When equipment fails after the PM, odds are the correct work isn't being performed in the right way. If you measure rework, it tells you the same thing.

3. Do your PMs address what's actually failing? Take your top 10 bad-actor assets by downtime this year. List how each one failed. Then open the PM tasks for those assets. Does any task look for that failure mode early enough to act on it? If not, your technicians have been doing PMs that don't protect you from the failures costing you production.

Put those three answers next to your maintenance spend. High levels of PM activity, especially the wrong PMs, combined with constant failure, mean higher maintenance costs.

Why more PMs isn't the answer

When something fails, the reaction in many plants is to add a PM. Management adds to a PM without taking the time to understand the root cause, and someone slaps the new PM into the CMMS. Do that for a few years, and you'll overmaintain assets, duplicate effort, and introduce more failures.

Many organizations target 80% or more of their labor hours on preventive maintenance. World-class organizations aim for 30%. The bulk of the work should be corrective actions based on what your inspections find.

The equipment manual isn't the answer either. OEM recommendations are a conservative starting point. One manufacturing facility reviewed its OEM recommendations and found weekly inspections for components that rarely fail. After evaluating failure modes and consequences, the team eliminated 35% of its tasks. In another PM program we reviewed, 46% of the PMs technicians were being sent out to had no value, because they didn't address the likely failure modes of the asset.

What a plant manager can do

The PM program needs top-level management support. Here's where yours counts.

  1. Approve the repairs your PMs find. I sometimes see management take 4 to 6 weeks to sign off on the purchase for a corrective repair a PM identified. With an eight-week delivery on the parts, three months or more can pass before the repair is done. When technicians have to reactively fix problems they found on a PM and reported, people become tired. They check out and "go with the flow."
  2. Ask for the root cause, not another PM. When something fails, the first question should be, "Do we understand the root cause?" Then physically verify the corrective actions have been implemented. If the existing PM needs to change, update it.
  3. Get the PMs reviewed, starting with your bad actors. PM tasks and frequencies should be reviewed at least every 18 months. Use RCM2 for critical or complex assets, FMEA for design phases or less critical assets, and PMO if your team is drowning in ineffective PMs. Recognize that you can't use any of the three if you don't understand the likely failure modes.
  4. Go see the work. Field audits can be very telling, and they let you educate the team in the process. Take the operations manager with you.

Ask your maintenance manager to bring you the three checks, along with what the PM program will stop doing, not only what it will add.

Learn to run maintenance as a business decision

Our Maintenance and Reliability for Managers series is built for the people who decide what maintenance work gets done. It runs as four 3-day workshops, spaced out so your team applies each part in the plant before the next one. Topics include:

  • PM and PdM program approaches, and strategies to optimize the PM program
  • Criticality and risk assessment, and failure modes and effects analysis (FMEA)
  • Root cause analysis and a defect elimination culture
  • KPIs, metrics, and site dashboards

Who should attend: plant managers, maintenance managers and supervisors, operations managers and supervisors, and maintenance or reliability engineers. Come as a team if you can.

Want your managers making these calls with confidence? See the dates and what the series covers.

Prefer to train your whole team together? We can bring the training to your site.