The Role of the EAM in Improving Reliability with Steve Richmond
It’s our pleasure to welcome Steve Richmond, the founder, and CEO of Projetech, a company providing IBM Maximo as a service. He has a degree in mechanical engineering and is also on the Forbes Technology Council. Projetech started by building automation systems, energy management, among others. It’s currently involved in providing Enterprise Asset Management as a service, with Steve’s experience in CMMS and EAM systems spanning about 30 years.
In this episode, we will be discussing:
- What is Maximo
- How does an EAM help with improving reliability
- How do you ensure the data collected is accurate within the CMMS
- What mistakes do organizations make when they’re trying to use EAMs to improve reliability
…and so much more!
What is Maximo?
Maximo would be considered an EAM by large consulting groups like Gartner. They began as computerized maintenance management systems in the 80s. As they expanded, the name changed.
Do you need an EAM to manage your maintenance and reliability program?
There’s too much information that needs measuring for you to try and do it any other way. A lot of data needs to be managed and maintained.
How does an EAM help with improving reliability?
You have to get started by understanding what reliability is because it means different things to different organizations. However, once you’ve identified it, you need to figure out the right data points to monitor to ensure you reach that goal. That’s what EAM products aim to do.
What is the role of data within the EAM in improving reliability?
There are all kinds of things that we can measure and monitor. The question then becomes, should we? Some data points have a low bearing on reliability. While the collection of data has a cost associated with it, the storage of data also costs money. So, keeping track of insignificant data isn’t worth it. You need to hone in on key measurements that support your KPIs.
How do you ensure the data collected is accurate within the CMMS?
According to Steve, the more machine-generated data you can collect, the better. One of the challenges that have come up over the years is a human intervention with the collection and recording of data. That then leaves it up to interpretation. And, sometimes, what you measure is what you get.
What type of information can be pulled from the EAM to improve reliability?
The information about assets as they compare to one another typically in a manufacturing or a generating environment. Depending on the business that you’re in, you’re going to have similar assets. Often, you’ll even have numerous assets of the same size, manufacturer, and quantity. So, comparing their reliability alongside one another is a great place to start. Sometimes, the reliability of an asset will have to do with something as strange as its location.
How long does it take between collecting data and starting to get good information?
That depends largely on your business as well as the type of data you’re collecting. Some systems can churn out useful information within a few weeks. However, in most cases, you need larger data sets and sample sizes to be able to make definitive decisions about what’s necessary.
How else does the EAM help us improve reliability?
There’s a discipline around being conscious of the fact that reliability is important in your organization. When used by the employees and resources around them, the systems themselves give us a discipline about what we need to be doing and watching. It’s an awareness that comes from having the system.
What mistakes do organizations make when they’re trying to use EAMs to improve reliability?
In the beginning, the issue stems from naming conventions, locations, and defining systems consistently. There needs to be a discipline around what you track. Then, identify the similarities between what’s being tracked. It’s vital to have a similarity in the way you describe these assets.
It’s easier to set up the system beforehand than go back and clean retroactively.
What makes the biggest difference in being successful with an EAM system?
Involving everybody that has anything to do with the process is vital. EAMs shouldn’t be run by or owned by a select few. Everybody needs to be involved in it and have a stake in feeding the right information into the system.
What to change in a typical EAM implementation?
The simplification. More of these products are being offered as a service, which helps in moving systems forward. Make the systems a little more consistent in simplification, whether it’s naming conventions or the location conventions.
Also, these systems shouldn’t function as silos. That information shouldn’t reside in one location. The integration of your EAM over to other systems like process or HR systems is vital over time.
With CMMS and EAM systems, their operations should be owned by the business units as opposed to IT. IT’s good for quality and security.
An EAM system is a tool like any other. It needs to get exercised. You need to use it to learn as much about it as you can. Also, network with other users of the same products so that you can learn from one another. The online MORE community is a wide-open place for people to go share information, ask questions, and learn from one another. Bottom line, this whole process is a journey, not a race.
Steve Richmond Links:
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!