The situation
The production environment had accumulated preventive-maintenance
activities over time. Many tasks had sensible historical origins, but
the maintenance programme did not always make explicit which production
function or failure consequence each task was intended to protect. As in
many established plants, the volume of maintenance activity had become
easier to measure than the reliability value created by that
activity.
The objective was not to cut maintenance cost. It was to focus
maintenance effort, operator attention and improvement expenditure on
the failures that could materially affect production, quality, safety or
continuity.
What changed
An RCM-based review was used to reconnect maintenance decisions to
the required functions of the production process. Existing tasks were
challenged against credible failure modes and consequences rather than
simply being accepted because they were already in the schedule.
This changed the allocation of effort. Some preventive activities
could be simplified or replaced where they added little control. Other
equipment required more attention, improved condition monitoring,
different operating checks or engineering changes because the
consequence of failure justified it. Operator knowledge became part of
the reliability process rather than reliability being treated as a
maintenance-department responsibility alone.
The programme therefore did not produce a simple instruction to do
less maintenance. It produced a more defensible reason for why each
important intervention existed and where additional effort was
warranted.
Outcome
Maintenance became more closely aligned with functional criticality
and credible failure behaviour. The organisation could distinguish
between activity that was historically inherited and activity that
genuinely protected reliability, while giving greater attention to
failure modes capable of disrupting production or quality.
The principle: RCM is not about maintenance. It is
about reliability. Maintenance is only one of the possible ways to
preserve a required function.
This case study describes the application and outcome. For the underlying method, see the relevant RBI or RCM Whitepaper.
Browse Whitepapers →