What Can We Do Differently to Scale Predictive Maintenance? - with Nick Leeder

Trend Detection Podcast ·

Show notes

Welcome to the Trend Detection podcast, brought to you by Senseye Predictive Maintenance – the platform which enables predictive maintenance at scale across all of your assets, across all of your plants.

You can find out more about how Senseye Predictive Maintenance can reduce unplanned downtime and contribute towards improved sustainability within your manufacturing plants, by visiting: www.siemens.com/senseye-predictive-maintenance

Transcript

Welcome to the trend detection podcast powered by Siemens. And now your host, Nel Sullivan. And so I'm going to see a hand over to our first speaker, Nick Leader, um, who's gonna talk about what can we do differently to scale predictive maintenance. So Nick's, um, an award winning coach and advisor. Um, I've interviewed him many times on our podcast. um, and one thing is for sure, you say beyond the buzzwords, Nick isn't a fan of buzzwords, so there'll be lots of actionable insights here for you. So without further ado, I'm gonna hand over to Nick um to take it away, so over to you, Nick. Thanks Noel, and, and thank you everybody for the opportunity to uh speak with you today about scaling predictive maintenance. Um, now just if you could give me two seconds, I'm gonna have a, a, a quick go at sharing and hopefully that all works for everybody. So, um, I think when we start using, uh, the phrase scaling, we have to actually put that into context, because scaling means different things to different people. Um, So what do we mean by scale? So we've all got our assets, our critical assets in our facilities, and they've got some level of sensors on them, so it's picking up the vibration, the noise, and we, we, we're using predictive maintenance to understand whether something's gonna break or not. But as we take that, we also start looking at that asset sits within a larger facility, and in that facility. There are many of those assets, and that's actually the first level of scaling for many companies and many businesses. It is kind of understanding really what, you know, where can we use this technology else within the plant. And for many people, that's as far as scaling goes, and it depends often on the responsibility of the individual and what they're trying to do. And as I'm gonna go through today, I'm gonna say the challenges here are no deference to the next level of scaling because that factory also might sit within a network of factories across your business. And again, that is scaling again, but in a different context for different people. So when we think about scaling, we don't just think about scaling within the factory, we think about scaling across all our factories. And again, back to that point, the challenges, whether we're talking about one factory or many factories, are often the same. So scaling's easy, right? I mean, it can't be that hard, it's just putting more sensors on a machine. Now, it, it, the, the reality is it's not quite that easy. And the reason being is, as you grow from just doing one or two machines into many machines all across many machines across many factories, the challenges are no longer linked really to the technology itself. The challenges start to become around the people. So what gets in the way of scaling? Well, as you unders you know, as I started to talk about a second ago. The first thing that starts to get in the way are the behaviors. People are, and rightly so, proud about the way they do things and how they, you know, particularly maintenance engineers, they know their assets. They can often walk up to uh a machine and understand if it's gonna break or not, just by listening to the sound. So there's a lot of knowledge, but there's a lot of behaviors in there. Those silos, you know, we have in the business, you know, the maintenance teams, the operations teams, sometimes there's IT teams involved. And that complexity actually means that many times that businesses run in silos across their organization, and that means that communication between those teams, working, collaboration, is a barrier that we have to overcome. And skepticism, as I mentioned like the behaviors of we've always done it this way, there's a skepticism, particularly with very experienced and knowledgeable people about what can predictive maintenance actually teach them, and we need to kind of understand that to address it. And then think the last one, but it's certainly not the least one, our priorities. Now, often, you know, when I talk to companies about starting their transformation journeys in the business, perhaps looking at predictive maintenance as one of those first steps. There's always the question of, yeah, that's great, but I don't have the time or there's no budget to do this with, and I'm sure everybody on the call gets and sees that and hears that on a regular basis. So the barriers are quite significant, and that, you know, and when you start thinking about the 3 things, or these 4 things, sorry, I mentioned a moment ago, we go back to that scaling question because they exist within a factory or a plant. But they also exist across all the plants within your business, so we have to overcome them. The other thing is money. Do we actually understand what the cost of downtime is? Well, the problem here is that to try and get people to change, we have to attribute it to a problem we're trying to solve. Downtime is often measured, but the cost of that downtime is very rarely understood. Only, you know, 80% of teams lack visibility into the cost of downtime in the business. This was done very recently by Aberdeen Research. That proves that actually the pain. The financial pain a company is feeling from not having predictive maintenance, not having the visibility of the downtime they have today. Is significant, and they're not in that position to start addressing it. So we have to start the change journey. And that's that change journey, the people, this is not again, not technology, this is people. We have to start demonstrating the value to the people that actually matter. And we need to look at making that really relevant to the people within your organization that are going to use predictive maintenance, and that's not necessarily, by the way, the managers. So what we often hear is, yes, but if we do predictive maintenance, what's that, what's the value of it? What we say often is, well, it helps us reduce downtime. It helps us save money, you know, either that's, you know, not having pumps and you know, fans on the shelf ready to be swapped over when something goes wrong, or it's just the cost of not being able to run the line because one of the machines is down. But what we need to start also understanding is what the person on the other end is receiving, what they're hearing. And that other person, you know, yes, of course, downtime, money is important, but we have to make it relevant, and make it matter for them as well. So we have to start talking about it, well, look, if we do this, you get back your weekend. You know, you're not coming in on a an extra shift to try and get something fixed or working on sociable hours, it's actually giving you back control. So that's a, you know, an important start to think about the value isn't always in time and money, but it also can actually apply to the person. That they're set, you know, and on a personal level to the individuals that it impacts. And then we start that winning them over journey. So if we can start talking about value, not just in terms of what I mentioned a second ago, but making it personal to them, then we start winning them over because we have that financial outcome. That's the first, you know, any business scale will always scale predictor maintenance on a business case. So the outcome is we're making staff more productive. We're stopping the downtimes, and planned downtimes by 20%, whatever. But then we also connect that to the emotional things, yeah, that emotional things is like, like I said a minute ago, it's not just about. Understanding whether they can get their time back, but also the feel-good factors as well. They fix issues before they become a problem. You know, in maintenance, it is a world of constant firefighting if you don't have predictive maintenance. And at some point that does become quite a demoralizing environment to be in. So little things like proactively fixing problems really taps into the emotion. And when you get the outcome and the emotion together. You really start to get the buy-in of people. And if you start getting the buy-in of people. Then you really start that change journey to scale. So let's go back to this question of value. Um, I'm gonna see, I'm, I'm probably gonna fail quite miserably here. Um, I'm gonna talk about, uh, downtime here, one second of downtime. Now this is coming from Siemens' own research here, uh, and the recent report they've released. How much does 1 2nd of downtime cost? Um, feel free to put it in the chat if anybody's got an idea. OK, I'm gonna keep going So 1 2nd of downtime is equivalent to 2 Big Macs. Now that doesn't sound very much, but one second for an average small business is, uh, around about $13. It's a, it's about well a in a Big Mac, I'm making some generalizations here, it's about $5 50s, yeah, but it's about $13 for one second. But that scales significantly. So we're deep into the Big Mac index because a Big Mac is ubiquitous, you can, it's not a dollar, you can spend it anywhere in the world. But for some larger automotive plants, that runs into the thousands of dollars in an hour, in seconds, sorry. That's 116 Big Macs for 1 2nd of downtime. Now, why am I using this, because. Actually, everybody knows what a Big Mac is, everybody knows the worth of it. In fact, even The Economist uses the Big Mac index to look at the variable um rates across different countries and the inflation, but. Actually, everybody understands this, this is something to get, and this is a 2nd in an automotive plant, just let's just absorb that for 1 2nd, yeah? Yeah, no pun intended, by the way. That's 116 Big Macs in 1 2nd for an automotive plant. 1 2nd of downtime. That's more than, more than I've probably eaten in my entire lifetime. So it probably, you know, we're starting to make some of these values more relatable, but, you know, going back to answering that 80% problem, here are some real test points that can start helping on that economic and value proposition. So we need to start that journey and tell the story, you can tell the story using Big Macs, um, but we have to take those small wins. And build that narrative up so they become big momentum in it. Now that story isn't just we did predictive maintenance and we saved X number of hours. This story has to tell you the journey that you've gone on. You know, the challenges of trying to understand which assets to sensorize and put the sensors on to measure the prediction. Um, of, you know, uh, of, of, of vibration, yeah, to understand actually how we went through understanding the first results, were they results accurate? Did we have to refine the thresholds and parameters that gave us the alerts? Did we get too many alerts, and it became confusing. Tell the story and the journey you went through and tell that story so it shows you how you overcame the challenges yourselves. And don't just keep that story to yourself, start looking at how you can share that within your organization. Now are there ways of um sharing that on bulletin boards? I don't know many companies have them physically. You know, I, I've seen some great examples of going around uh factories where every time they avoid a downtime event, they put a win on the board, they have the asset, they show what that asset is, they show the amount of time it's been saved, what they did. What the information, what the signals that actually told them it was going to fail, and actually what, who was involved in stopping it, so it's not just recognizing the success and doing it on the board, it talks about the people that were involved in it as well. So think about that success, and that success is on the shop floor, communicate on the shop floor, but also look at ways that you can actually elevate that upwards in the organization, because that continuous momentum of success stories and and what you have will build more momentum and awareness at leadership level. And I think the final one is recognize the champions. Um, I, I, I, the little story behind this is I've been, I've recently spent a day with a psychologist, um, and not on a personal level, but actually on a, on a professional level, understanding how they, they are training, um, Team GB, uh, Olympians actually on performance. And part of that was that for a long time they were struggling to convince the people in um Team GB to to follow their methodology, to spend time with them. And that flipped when one of them won gold. And they, that person was saying the thing that made the difference was spending time with this psychologist. That's, at that point in time, that psychologist no longer had to try and sell themselves. That other person was selling it for them. That champion Was actually the advocate in their business, talking about how great it was. So who would be your champions, how would you recognize them within your business? And often I see. Predictive maintenance projects coming and being driven like a project. It is a project, so it starts here and it finishes here and then we're done. But it isn't, it's a continuous journey. And it's a journey that's really starts taking a new mindset. If done well. That scaling factor, it creates a new mindset within the organization, and I mean that could be, as I said, go back, let's go back to that scale question. That could be just the teams on your, on the shop floor in your plant, or it could, and it could be just the maintenance team, for example, or it could be different plants working together and working in a different way. But the things I see very differently, that shift, it starts driving a level of curiosity within the business. They start looking at this and going, actually there there's something there that I didn't know existed. I'm now starting to see why things might be failing. It actually starts bringing forward the visibility of those problems within the organization. And actually that visibility can happen on many different levels. It can happen at the expert level, the VA's, the VA twos, the VA threes, with a detailed spectral analysis of actually understanding what the potential failures are. That visibility can then be used at an operational level, so the maintenance person can actually see well what's the health of my assets, and I don't have to go hunting around, it's on there on a single page in a single place. But it will also elevate that same information up to management level, so the management gets an overall visibility of what the health of the plant is or what the health of all the critical assets are. So that visibility and that curiosity really starts driving the next thing, which is then starting to take ownership. You actually create and allow people and empower people. To act to make sure that they feel responsible and accountable for ensuring the performance of the facility and production. And that ownership, when those 3 things start happening together, curiosity, the visibility and the ownership, you really know that you're on that journey of continuous improvement within, driven by predictive maintenance, and that journey of scaling is healthy and is ready to start, if not already started. So the things that really drive that from a pilot, cause some of those things really exist even in a pilot stage, and then look at scale and performance of four key things, and these are the four things I've seen repeatedly um when I've worked with predictive maintenance in my career. First thing is a standard level of standardization. How you go about using predictive maintenance, you should be using the same processes, the same approaches, but also the same technology because that allows you to get that visibility I mentioned earlier on. You have to think about how maintenance and predictive maintenance actually is connected in the broader processes within the business. So you have to connect those processes together. You have to think about how it works, not just in maintenance, but how it works perhaps with procurement and planning and the other teams and making sure that the scheduling and more dynamic scheduling you can now do because you can now predict when things can fail. How do those things work together, so it's not just a maintenance play, it's a connected play within production and manufacturing. The next thing I've seen which is a real man shift change is, is also a learning loops. Um, I would love to say everything in my career I've got right first time. Um, alas, that hasn't happened, and this, this presentation may be testament to one of those occasions. But one of the things here is that learning loops are really, really critical. When something doesn't go right, so perhaps you had a failure on the shop floor using predictive maintenance. Did somebody not actually pay attention to the alert? Were the thresholds set wrong? Was there something different? Were you producing something different that caused it to fail? So take that, take that learning. Get feedback on it and then fix it. Because that will make you better, and that again, we talk about continuous improvement in this world. And then start bringing everybody into that process. So on your line walks, on your uh uh that you do, make sure that predictive maintenance, that asset health becomes absolutely visible, get everybody involved in this, from the operators, from the maintenance teams, all the way through also to the management teams. So everybody can build that into their daily routines, and it then becomes institutionalized, if that's the right word to use, in how everybody works together. So how do you start? I'm gonna throw the challenge back here. You need to become a change maker, you want things to scale. You've gotta take the first steps yourself. So are you on this call asking the right questions? So what can you try differently? And using some of the things I've talked about today, have you thought about, OK, if I thought about this and I thought about things in a different way, how could I do this differently, how could I use this to start scaling within what I'm doing within my plant. Perhaps even to other plants. What will be the story that you will tell? Next, What's the journey that journey, it's not just about we did this and this is the outcome. How can you talk about this, how can you make your champ find your champions? And what will the first step you will take from the back of this presentation? So evolving scaling. It's hard, yeah, it's much, much harder than starting the projects off. So We talked about it a second ago, but you need to communicate that why. That why isn't just about the time and the money, it's about making it personal to the people that it impacts in predictive maintenance. So make that why about actually winning the time, getting control back of their time, being proactive and fixing things rather than just constantly firefighting. These are such an emotional connections. That combined with the financial benefits of predictive maintenance, really get you to scale within the business. I talked about this a lot and I'm gonna keep going on about it, hanging on about it. Celebrate success. Make sure that wins are recognized, wins are publicized, and the people involved in those wins are recognized through it as well. And that helps this point here, which is about building the culture. When we talked about being curious, getting the visibility but not being afraid of it, also recognizing that you don't get everything right first time and actually showing how you're improving things, that's the culture that will allow you to scale predictive maintenance within your facility. And that allows you to take pilots of predictive maintenance or very small deploy um deployments of predictive maintenance and drive them to scale within your plant or even further afield. Thank you very much, I'm open to any uh questions now. Thank you, Nick. That was really good, really interesting, um. …

Full transcript (WebVTT)