Why Reliability Centered Maintenance (RCM) Studies Fail | IBM Maximo Asset Management скачать в хорошем качестве

Why Reliability Centered Maintenance (RCM) Studies Fail | IBM Maximo Asset Management

For More Info: https://www.banetti.com There is a reason why 85% of Reliability Centered Maintenance (RCM) studies fail. Matt from Banetti, welcome to Reliability Radio. For our listeners, do you mind just giving a quick overview of what is Banetti? We come from 25 years in the world of Maximo, implementing across all industries, doing pretty much anything you can do with Maximo. We've been there, done that. Customer improvement and maturity, that's our real focus. There are two products I want to highlight here. The first one is called RCMax. Can you walk us through what RC max is, why did you create it and what it does? So backing up just a little bit here, it was about 5 years ago, we really got deeply involved with Reliability Web. About 3 years ago, Terry finally got me to sit in one of the CRL classes. Two days into it, and I was just like, wow! We are a bunch of idiots in the world. Reliability was sitting right beside us this entire maintenance and CMMS journey. And we just never knew to look for it. I guess part of the reason it really clicked for me, was because our mission at Banetti had always been customer improvement. In January of this year, I met Nick, with JMS software. We were talking and he's like, yeah, 85% of these RCM studies fail. So, how do we fix that? How do we close this gap? We have to get the data in Maximum, get it in the CMMS. This is not about importing data because the way you do things when you go about that RCM study are not the way you do things in Maximo. So we're now blending process culture in order to get the data in Maximo. We use the Maximo tools to actually build the screens in Maximo, and it's an RCM that flows in the traditional method with the addition of the technological capabilities of Maximo. Honestly, it's improved because now you have technology helping you do things along the process. Just click insert, and now it's there. It's done! It's complete RCM with the data intact, and it's implemented. The risk is calculated. The recommended tasks are automated. All you have to do is say, accept. It's the equivalent of the easy button. I had never seen this stuff. It's not on IBM's radar at all. They're nowhere even near thinking about this and the other partners, we know there are other partners that do reliability stuff, but none of them are doing this. We are never really going to get these maintenance departments to move to true Reliability until their tools support the activity. So that's our mission. We've changed our mission. There you go. The tools support their activity. The other product is similar naming convention called Max BI. Anyone who's used Maximo knows that it may come with 200 out of box reports, but it comes with a dozen you're going to use most likely. But the real problem with most Maximo implementations, is that the data sucks. That's really the core problem. I know you guys on the AI side, you have to see this as well. Every time you go in to do something, you need data, right? You can't analyze air. That's right. You've got to have data. And so, we took a look at that and we said, okay, we've been writing reports for years and, I think if you were to talk to the guys over at an asset analytics and other reliability partner, they'll tell you the same thing. We said, okay, we're going to build what I would call a hierarchy of analytics to help you improve. We ended up building this out in the Microsoft Power BI platform because the majority of our enterprise customers have an office 365 enterprise license. They have access to Power BI at no additional charge. So, this actually enables them to mature their data in the system through the process such that it becomes a tool that helps them grow and get better. That makes it easy to deploy it across the enterprise and it doesn't let them change the SQL query, keeping the data consistent. It allows the users based upon their role to view it the way they need to view it for their job. It needs to be really simple. It needs to feel simple. The delivery has to be incredibly user friendly to them. It has to be very intuitive. Thank you, Matt. It's been a pleasure. This podcast is copyrighted by Reliability Web, Inc. all rights reserved reliabilitywe.com and Reliability Radio are trademarks of a Reliability Web Inc. For more information visit: https://www.banetti.com