When Preventive Maintenance Becomes the Problem

Walk into almost any asset-intensive facility, and you’ll find the same story: a maintenance backlog that never shrinks, a PM schedule no one has challenged in years, and a reliability team running flat-out yet still putting out fires. More tasks, more work orders, more budget, but not necessarily more reliability.

This is PM creep. And it’s more common and more costly than most organizations admit.

While the maintenance workload continues to grow, reliability performance often does not improve at the same rate. Organizations find themselves investing more labor hours, more spare parts, and larger maintenance budgets without a clear understanding of whether those activities are actually reducing risk or improving asset performance.

This challenge was the focus of Cenosco’s recent webinar with Harry van Teijlingen and Ahmed El Sherif on Reliability-Centered Maintenance (RCM), which explored how organizations can move beyond maintenance routines driven by history and habit and instead build maintenance strategies based on risk, failure consequences, and business value.

Maintenance programs don’t bloat overnight. They grow one well-intentioned decision at a time.

A pump fails unexpectedly – a new inspection is added. An audit flags a gap – a preventive task is introduced. A vendor recommends a service interval – it goes straight into the schedule and stays there indefinitely. Over months and years, teams accumulate hundreds, sometimes thousands, of preventive maintenance activities that were never reviewed after they were created.

What almost never happens is the reverse process. Tasks are rarely removed. Existing activities are rarely challenged. The question “is this task actually reducing risk?” is rarely asked.

The result is a maintenance program that looks comprehensive on paper but functions as a liability in practice. Teams spend more time planning and executing work orders while struggling to distinguish between activities that genuinely reduce failure risk and activities that simply exist because they’ve always been there.

Volume alone does not guarantee reliability; it just guarantees cost.

The instinct to respond to failures by adding maintenance is understandable — but it leads organizations in the wrong direction.

Every maintenance hour spent on a low-value task is an hour not invested in managing a high-risk failure mode. And in asset-intensive industries, maintenance resources are always finite. The challenge isn’t doing more. It’s doing the right things.

This is the central insight behind Reliability-Centered Maintenance (RCM): the value of a maintenance activity is not determined by how often it is performed, but by whether it addresses a failure mode that actually matters to the business.

Both extremes create problems. Insufficient maintenance increases the likelihood of failures, unplanned downtime, and emergency repairs. Excessive maintenance introduces unnecessary cost, increased resource demand, and even additional risk through intrusive maintenance activities that introduce new failure opportunities. The goal is to find the balance point where reliability, risk, and cost are optimally aligned, and to defend that position with evidence.

Intuition won’t get you there. A structured methodology will.

Reliability-Centered Maintenance is a structured analytical process designed to identify the most effective and efficient maintenance strategy for each asset, based on its operating context, failure behavior, and the business consequences of failure.

The methodology is built around seven fundamental questions:

These questions sound straightforward. In practice, working through them systematically forces organizations to confront assumptions they have been making for years.

Take the question of consequences. A local pressure gauge may fail without creating any immediate operational risk. The equipment continues operating. Maintenance is planned during a convenient window. In that scenario, a run-to-failure strategy is entirely appropriate, and spending resources on preventive tasks would simply be a waste.

A critical compressor handling process gas is a different story entirely. Degradation may affect production rates, energy consumption, and plant availability. Condition-based monitoring and proactive intervention are not optional; they are essential.

By asking these questions asset by asset and failure mode by failure mode, RCM creates a defensible, evidence-based maintenance strategy rather than one inherited from history and habit.

One of the most important, and most frequently violated, principles in maintenance management is this: two identical pieces of equipment can require completely different maintenance strategies depending on how they are used, what they are handling, and what happens when they fail.

Standard maintenance templates applied to equipment categories ignore this reality. Every centrifugal pump gets the same schedule. Every motor gets the same PM tasks. Every compressor follows the same inspection cycle. It is efficient to administer, but not for maintenance.

Consider two pumps in the same facility. One transfers hydrocarbons through a critical production process; a seal failure results in product loss, environmental exposure, safety risks, and a production stop. The other circulates cooling water in a redundant system with a standby pump available.

Both pumps may be physically identical. The consequences of failure are not. Treating them identically means either over-maintaining the low-consequence pump or under-protecting the high-consequence one. Usually both.

RCM forces organizations to evaluate maintenance decisions through the lens of consequence and risk rather than equipment classification. That shift alone can dramatically change where maintenance effort is focused, and where it can safely be reduced.

A recurring challenge in any reliability improvement program is ensuring the quality of the data. It tends to surface at the worst possible moment, when you are trying to use historical data to understand failure behavior.

Organizations frequently discover that their asset hierarchy is incomplete, equipment records are inconsistent, or maintenance history lacks the detail needed to support effective analysis. These gaps are invisible during normal operations. Work orders still get completed. Equipment still gets repaired. But reliability analysis places much greater demands on data than day-to-day execution does.

To understand how equipment fails and which maintenance strategies are effective, you need accurate asset structures, reliable failure records, and consistent maintenance histories. Without these, analysis becomes guesswork.

There is, however, a useful side effect: RCM often becomes a catalyst for improving data quality. As teams begin asking deeper questions about equipment behavior and failure mechanisms, gaps in information become hard to ignore. The analysis itself identifies what data is missing and makes the business case for capturing it properly going forward.

One reason RCM initiatives fail to deliver lasting value is that they are treated as projects. A study is completed, recommendations are made, and then the organization moves on. Two years later, the maintenance program looks much like it did before.

Reliability is not a project. It is an ongoing business process.

An effective RCM program has a defined lifecycle: preparation, data collection, and team alignment; analysis and maintenance strategy selection; implementation into maintenance plans and work management systems; and continuous review as operating conditions, asset performance, and business priorities evolve.

That last step is the one most commonly skipped. Maintenance strategies that made sense when the equipment was new may be inappropriate after years of operational experience. A failure mode that seemed unlikely at commissioning may prove to be a recurring problem in practice. Regular review is not overhead; it is how the value of the initial analysis is maintained and compounded over time.

The outputs of RCM must also be fully implemented into enterprise asset management systems and daily workflows. An analysis that exists only as a report has zero operational value. The recommendations have to become actual maintenance plans, executable work orders, and auditable records.

The true value of RCM is not measured by the number of tasks in the maintenance plan. In fact, one of the most reliable indicators that RCM is working is that the preventive maintenance workload decreases, because low-value tasks have been eliminated and effort has been redirected toward higher-risk failure modes.

Well-implemented RCM programs consistently demonstrate the ability to reduce PM workloads while improving asset availability, lower maintenance costs without increasing failure rates, optimize spare parts inventories, and protect safety and environmental performance.

More fundamentally, RCM programs change the conversation within maintenance organizations. Instead of asking, “What maintenance should we add?” teams start asking, “What maintenance genuinely creates value?” This shift in focus from quantity to quality is what distinguishes a maintenance program that grows indefinitely from one that continuously improves.

If you looked at your current PM schedule and had to justify every task on it, not based on history, but based on its actual effect on risk, how many tasks would survive?

For most organizations, the honest answer to that question is where RCM begins.