How does LRCM “improve” RCM?

Difficult discussions take place whenever people engage in the reconciliation of theory with practice. In many maintenance situations, the reality of a given maintenance event will be at odds with the current structure of the RCM hierarchy.

The failure mode will be identified at one level of causality in the RCM knowledge base and at an entirely different level and with a different viewpoint on the work order. The reliability engineer, supervisors, downtime administrators, and technicians repeatedly ask and discuss the same questions: “At what level do we need to analyze the failure mode?”, “Do the Consequences as surmised from the RCM Effects justify the level of detail proposed?”, “Is a failure analysis justified?” The consultant, engineers, and supervisor’s, during the LRCM pilot, try to keep the basic questions from getting buried under excessive detail. This is hard work. People hold opinions and time is at a premium. The more immediate pressures of production will invariably conflict with the desire to make the RCM knowledge better.

Nevertheless these “RCM” types of discussions must take place. We call the process “LRCM” only for the reason that it happens outside the formal “initial” RCM review group meeting room. It takes place in the shops, corridors, and in the maintenance offices, formally and informally. RCM principles of clarity, consensus, and friendly debate pervade these discussions, that will sometimes culminate in agreement to adjust or augment the RCM record. The reliability engineer will justify and document such changes, including any dissenting opinion, in the RCM Effects.

© 2011, Murray Wiseman. All rights reserved.

This entry was posted in LRCM and tagged , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>