PMO with Rick Clonan
PMO is a process where you make efficient use of your PMs to understand the operating context of your assets in a better way. Once you have identified your critical assets, you can plan your PMs accordingly. These routine PMs should be designed in a way that they serve the purpose that you want from your assets. It is not just about reducing number of PMs, it is about finding failures and mitigating them. Our primary focus should be to make the PMs, more effective and then we can focus on the efficiency as well.
In this episode, we covered:
- What is PMO?
- Learn how you can define your critical assets so you can eliminate the bad factors!
- Why should there be a team dedicated to carry out PMO activities?
- And much more!
Our main goal is to identify the bad factors that are hurting you and your assets the most. As PMO is a live process, the bad factors and main issues are always dynamic. Once you have successfully defined your critical assets, you can start eliminating the bad factors. As you go about implementing solutions, the bad actors will be changing regularly and you will be dealing with newer issues on a consistent basis. As it a systemic process, you have to identify your critical systems. Then you have to collect data on those systems. Collecting meaningful data is very important as it helps you eliminate failures in an efficient manner.
There should be a dedicated team to carry out PMs and implement PMO activities to achieve consistent results to get the support of your bosses. There is also a need of having a work order management system in place. You have to define your work orders and then have a data set against each word order. It helps you maintain records, check historical data, and then carry out your PMs after careful planning. You also need to have your failure rate so that you can assign that PM to someone who would be fit for the job.
There should be data points set up intelligently and you have to identify the failure modes at the very start of the process as it helps the technicians carry out the task within the constraints. RCM and FMA are advanced ways to perform failure analysis but you can just start by gathering your failure data. Once you made sense of that failure data and run it against a relevant failure mode, you should be able to understand the problem. You also have to have an asset hierarchy and understand the constraints of the task. You can run the analysis at asset level but study should be done at the component level.
Having access to historical failure data helps you link your failure codes with the CMMS and identify patterns. It is always great to consult with your team members and learn from your senior members when you find something that you don’t fully understand. There should always be some performance measuring metrics in place. These metrics can be set based on costs, PM success rate, or anything that you are looking for in your PMs. In the end, you are just making sure that your asset run the way you want them, for as long as you want them.
Eruditio Links:
Rick Clonan Links:
- Rick Clonan LinkedIn
- SMRP.org
- Making Common Sense, Common Practice by Ron Moore (book)
- The Goal by Eliyahu M. Goldratt & Jeff Cox
- Maintenance & reliability best practices by Ramesh Gulati (Book)
- Social:
- Link:
- Embed:
Rooted In Reliability podcast is a proud member of Reliability.fm network. We encourage you to please rate and review this podcast on iTunes and Stitcher. It ensures the podcast stays relevant and is easy to find by like-minded professionals. It is only with your ratings and reviews that the Rooted In Reliability podcast can continue to grow. Thank you for providing the small but critical support for the Rooted In Reliability podcast!
