The Cultural Shift: Embracing Predictive Maintenance - with Brad Parsons
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.
In this episode, we discuss:
The Cultural Key to Predictive Maintenance: Brad Parsons, CEO of Rely Ability, joins the podcast to explore why cultural readiness—not just technology—is crucial for successful predictive maintenance adoption.
Understanding Organizational Culture: Brad breaks down four dominant workplace cultures—collaborate, control, compete, and create—and explains how each affects technology adoption and transformation.
Leadership & Metrics Matter: Leadership alignment and shared performance metrics between teams (like maintenance and production) are essential to eliminate conflict and drive collaboration around new initiatives.
Capturing and Sharing Successes: Real-world examples, like averting catastrophic equipment failures, demonstrate how sharing early wins internally can help build momentum and drive broader cultural adoption.
Beyond the Buzzword – What PdM Really Means: Predictive maintenance is more than tech—it’s a systems-level change requiring data trust, behavior shifts, and readiness to act on insights across the business.
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
I, I guess from culture's a thing that happened when no one's looking, right? Whether you're running a business or whether you're working in a large multinational, um, you can pretty much see how the culture or how effective the culture is, uh, in terms of, you know, what's actually happening when, when the boss isn't there. Welcome to the trend detection podcast powered by Siemens, and now your host, Nel Sullivan. Hello and welcome to the latest episode of the Trend Detection podcast. Um, I'm really pleased to be joined by a brand new guest. Um, I know we have a lot of recurring guests, but it's always great to have a brand new face or voice, I should say on the podcast. Um, Brad Parsons, who's the CEO and co-founder of Reliability, um, all the way in Australia, so we're in completely different time zones at the moment. Um, but we're, we're gonna have a really great conversation today. It's something we at Sensi Predictive Maintenance, the team within Siemens, we're, we're often talking about this cultural shift required for embracing predictive maintenance, and that's exactly what we're gonna talk about today. And it'll be great to get, um, Brad's unique sort of perspective on this. But I guess before we go into the topic in more detail, Brads, if you could just sort of introduce yourself to the audience, that'd be, that'd be really cool. Hi everyone, my name is Brad Parsons. Uh, I know I might have mentioned I've got a business called Reliability. I'm the CEO and founder of that business, but I also might try and talk through another business that I founded prior to reliability called Movis. Um, Movis is a product and product and services business, but reliability is a consulting and solutions business. So, 22 sides of that coin. Um, one has built a product, multiple products and gone to market, uh, with services attached. That's Movis, and with reliability, um, we're really a consulting house, so we have our in-house methodologies, but we also bring the best of breed solutions from around the world, um, such as the Siemens product, um, Sentai in particular. Um, but yeah, like, excited to be here and see where this goes. Yeah, no, fantastic. Thanks for joining us. And, um, what I like about that, is so, so, essentially what you're saying completely independent in the sense that, you know, you're not, you know, focused on Siemens, for example. It's, it's actually what's, you know, you know, talking to the customers and understanding what do they need and then picking, not as easy as this, picking off the shelves, what you, What you think's the, and putting it together, orchestrating. I mean, what you described yourself just before we, we came on air as, um, it's a really interesting term. Yeah, the, the title, I kind of called myself on LinkedIn where you can find me as ecosystem orchestrator. Uh, I don't see myself as a CEO traditionally, like I was with the Movis business. Um, with reliability, we're more about generating value outside the business than inside the business. So, that's really trying to find, as I said, best of breed, best of breed solutions, best of breed technologies, and bringing them together, um, to solve the customer's problem. There's no cus customer's problem, unfortunately, is exactly the same. You need to kind of bring different um capabilities to the fore and really understand the challenges that they're trying to solve. And that, and yeah, and I guess what, what we're covering today is, is an important, but maybe, I mean, maybe you disagree or agree, but an overlooked aspect of like adopting new technologies, which is this cultural element. Um, so from your point of view, Brian, you've been involved in many sort of projects in, you know, around technology, but how would you sort of define cultural adoption in this, in the context of adopting new technologies? I, I guess from culture's a thing that happened when no one's looking, right? Whether you're running a business or whether you're working in a large multinational, um, you can pretty much see how the culture or how effective the culture is, uh, in terms of, you know, what's actually happening when, when the boss isn't there. Um, so I, I certainly know that from experience, but, I, I guess in terms of understanding how culture supports technology adoption, I, I did a, I did a similar sort of, uh, webinar last year, um, and I was asked to kind of define that in more specifics. And there's, from, from look kind of looking back at my experience and looking back and, and talking to others, there's really kind of four cultures, if you like. Um, there's a collaborative culture, um, there's a control culture, and we'll talk about that a little bit later. Um, there's a compete culture, you know, that always wants to be the first and the best, and then there's a create culture, you know, which is the invented here syndrome, which can, which can work against you if you're a technology provider. Um, really it's trying to understand the culture that's present, um, and maybe there's a cultural transformation going on as well as part of a digital transformation effort, but really understanding the foundation of what's there, um, particularly if you're a technology or services provider, knowing what you're going into, um, really understands it. I mean, people define culture in many ways, uh, but that's it, that's kind of how I see it. And And you, you, you mentioned those different areas. Is that quite broadly, can that be quite broadly used to define implementations of all different types of products? I mean, maybe today we're, we're leaning towards predictive maintenance, but if we talk about, you know, other, other products as well, is it, can it be broadly applied to other products as well? Absolutely. I think it can be broadly applied, you know, fortunately my wife's a change manager of 30 years, so I, I kind of hear, hear this, and she's run large program teams as the head of change. So, I kind of hear a lot of this, you know, not just at home, uh, but at work, not just at work, but at home as well. Depending on that culture that's present, that will really influence the way in which you want to engage in terms of predictive maintenance, and we'll talk through it a little bit further, but maybe there's multiple cultures that actually exist and particularly in the sort of digital transformation, you know, I've been doing these, these sort of projects uh for the last sort of 1010 plus years, back in the, you know, sort of 2012, 2013 was when I first started. And what you'll find is, it can actually, culture can vary not only out of the site level at the company level, but sort of down to the department level. One culture, um, you know, is not dominant, you're not dealing with, you know, um, the vanilla, um, you're actually dealing with the chocolate, the strawberry, and the vanilla, um, and really depends, you need to understand the audience you're, you're working with and. You need to kind of adjust the way you work with them um to be conscious of that culture, um, you know, don't, don't assume everyone's the same, I think it's probably the general guys there. No, exactly, and I think one thing again we, we briefly spoke about before is this sort of, you know, when you're rolling out technology globally as well, is that it, that you becomes even more, uh, even more important to consider, right? So even in the same organization doesn't mean the culture is same in this part to this part, right? Yeah, absolutely, um. Yeah, I was just reflecting back on that sort of question and, and, and really having done dope global deployments with Movis, we got out to sort of 18 countries, so with multiple different um cultures span that and, you know, you can make assumptions, you can make an assumption that the, the Chinese, the Japanese, the Indian culture is very top-down, and, you know, maybe um stereotypically that's the case, and you'd look at Australia and the US where it's very bottom up. Um, going in with a particular approach, um, and, and in my experience in talking to some of the solutions that we provide as part of the reliability fleet or the ecosystem, selling bottom up and top-down, making sure that you're addressing the needs of both of those, um, you know, both of those parts of the business. The senior management, you know, wanna, wanna know things like performance, they wanna know long-term visibility, obviously wanna know financial outcomes. Um, whereas the, the, the shop floor, particularly in the predictive maintenance, they want to know how is it going to impact them on a day to day basis. They want to know what their jobs look like in the future, they want to know what tomorrow's like when they come into, you know, into the shop, uh, into the factory. You need to address all those concerns, um, you know, and that is part of the cultural transformation that any technologies or any solutions in the predictive maintenance space, um, have to understand and compensate for. And look at, yeah, and it's interesting you mentioned different stakeholders require different, you know, levels of engagement and, and that kind of thing, but I guess if we go into the actual detail of that in terms of. You know, how does a culture, you know, good or bad, sort of affect the deployment of, let's say, predictive maintenance, you know, what, what, what can affect it, what factors can affect the, the success or failure, let's say. Um, yeah, there's quite a, quite a few, I mean, I, back to those sort of seas, um, you know, does, does the business have a culture of being able to adopt and adapt technology as part of their business? Uh, often when you, when we work with, you know, big multinationals, they actually have kind of figured this out a little bit, and they will have an adoption site, a site that they know is innovative, a site that, you know, is open to new ideas, that is open to be challenged. And at the plant floor and at the executive level, there's an understanding that mistakes can happen. There's an understanding that, um, you know, there's an adoption and learning curve. There, there's an understanding that we might not have all the answers upfront, but we're all sort of driving in the same, in, in the same direction. And I think that's, that's, that's one element. Um, if I look at, The success of predictive maintenance solutions, there's this sort of pivot point, you know, when you get the basics right in terms of implementation, you know, you've got a networking up and running, you've got the technology deployed. You get to a point where you've, you've kind of expanded beyond the, the, the target customer segment. Say it was the maintenance team, you know, that's, that's your first target audience. When you start to mature that solution and start to evolve that within the business, you have to involve other parts of the business, uh, you know, for, for production's the most obvious one, right? So, if there is not a culture of working collaborative, collaboratively, if there's not a culture of open and shared communication, And even shared performance indicators, um, there was a guy called, there's a guy called Drew Troyer, I don't know if you you've come across him, but he's a real maintenance leader, um, and he put a note out this morning on, on LinkedIn, I, I saw that and commented, and he was actually talking about culture and cultural adoption and had a whole bunch of recommendations, but I sort of had to chime in and sort of say, you know, in order for businesses to adopt this broadly, I, I think one of the key things that's often overlooked and missed is, is around performance metrics. If you have a team like maintenance and you have a team like production, and they're both being measured on an independent set, that's fine, but if they don't have shared um performance metrics, then they're working against each other. So, maintenance want to take down the machines so they can do their work, that's obvious. Production want to keep the machines running, so they can get their targets as well. You've, you've got two polar opposites trying to compete, uh, really for the same time on machines. And if you don't have universal metrics, um, and there's obviously the high ones, profitability, you know, um, throughput, they're the, they're the big ones, but if you don't start to target down the shop floor and do operational performance metrics at the floor, the one we like to use, and it's really the foundation of reliability is energy productivity. So that's really, How much juice, you know, how much electricity is required to produce an output or a widget or a bottle or whatever you're producing, maybe in food and be, but what that does is unify those two groups to say, OK, if we run this machine harder, the performance of the machine will decay, it will use more energy, right? And you may, knowing that, you may, you may make the call to run that. If the priority is production, then you, you, at that time, you might want to put, you know, more productivity through the business, but if you're getting to the point where that cost is driving up too highly, where it impacts the profitability of the business down to the product line, process. bottle, for example, um, then you want to do that trade-off, um, and that kind of metric gives you a unifying way to, to, to kind of look at it, rather than those sort of very high level profitability, it's very targeted, uh, between those 22 groups, if that makes sense. No, of course. Uh, no, it does make sense. Um, and I guess, uh, just sort of time what you're saying, um, together, sorry, time what you're saying together, Brad. Um, I guess a lot of this comes down to sort of leadership as well, you know, at various different levels, um. Yeah, and leadership sort of pulling together, so it's not about one person necessarily, but it's like a, a leadership group pulling together, maybe in those different areas that you mentioned, but yeah, how important is leadership to this whole, you know, to the success of these type of projects? Ah, I mean, you, you're kind of stating the obvious, leadership is pretty key, if the, if the leaders aren't able to demonstrate the behavior that they're trying to influence and, ah, and the outcomes that they're trying to achieve, Nobody, no-one in their right mind's going to follow it. Um, leadership, the leadership have to demonstrate that the behavior that they want to see. Now, that, that goes all the way down to, you know, how do they make decisions, and, and the key part of sort of this predictive, uh, maintenance and digital adoption is really transitioning from, What is sort of hero mentality or what is, we've always done it that way, towards more data-centric behaviors. Now, that is a, that is a big shift, you know, that's a big shift from, um, you know, we, we've had people in the plant for 30 years, and now they've need to look at the data, you know, why, why should they have to go down that, that, that, that approach? And I think in my experience, you've got to, you've got to work with both of those factors, you've got to transition towards a data-led, but in doing so, look to the experience of the people in the, in, in the plant. They understand these machines and they understand how to operate them, and they've been there a long time, they understand how these things fail. If you're deploying sensors, for example, you may, this experience may be able to be drawn upon to understand at what levels can we set alarms, at what tolerances can we get, you know, can we live with. Um, how can, you know, the, the technology enable the capability that's already there. We're not, we're not talking about direct replacement, what we're talking about is, um, sort of systemizing the knowledge that's already there, building that repository so you can be, Repeatable and scalable. That wealth of knowledge, unfortunately, in, in a lot of Western worlds is walking out the door. Um, you know, I'm in my mid-50s, but a lot of the customers that we talk to and work with, um, are in their late 50s, 60s, In a very short space of time, we're going to see a lot of people walking out of the workforce. I, I think the US is, is slightly ahead of us, uh, but certainly I know that, um, a wealth of experience is working out the door. This digital adoption we're talking about, um, predictive maintenance in particular, is an opportunity to help capture that and, We've seen projects, um, you know, in the US and Europe and here in Australia where that is a goal of the, of the, of the transformation, a goal of the project is to capture that knowledge, capture that tacit, um, you know, untouchable knowledge that, that goes, that has come with these people that have been in these plants for a long time. I think that's, that's probably a key tenement that's probably not understood that, that particularly well is when you're losing that knowledge, these tools are a way to capture and retain that. Um, so you want to kind of work with the existing skills that are there, is, is probably a, um, a point I'd like to raise there. And I guess that's an interesting point what you're saying about the change in workforce, because that also, of course, means there's a, there's a change in culture as well. I mean, the, the, I guess the two go, they go hand in hand, and it maybe it's almost. It's almost not, yeah, I guess it's forcing companies in some respects to, to change their culture is that the workforce changes and people have been there a long time, maybe with a certain mentality, not all the time, but, um, a lot of the time, and, and that's leading to this new, new embrace of technologies like predictive maintenance, maybe. Yeah, I mean you can generalize all you like, um and and you know, you can do a little bit of that. So I, I guess a younger workforce generally ah tends to be, tends to be more agile at technology adoption, you know, a lot of the younger, younger workforce is so used to technology adoption that, you know, it's a, it's a core capability or a core skill or or even a core behavior in which they learn to do. The younger workforce typically uh looks to data, um, A, because they don't have the experience that an older workforce um can draw upon, so, providing them with the tools um that is, you know, um, really supported by the workforce that's been there a long time. Using those tools, gives them a bit of a leg up and and kind of gets the experience to be shared, so we're we're all looking at the same, the same data, we're all looking at the same, Um, piece of paper, we can all start to learn, and both of those groups, um, are going to have different perspectives, so, you know, they come from different backgrounds, they come from different, um, sort of skills and, and experiences, so having, you know, the data to be there, having the technology to be there to, to look from two different lenses, um, same coin, different sides, uh, I think is, um, is also invaluable as well. Yeah, and you know, like I said, both both perspectives, it's almost you're looking for a blend, a blend of both, they both bring things to the table, right? Lots of positives to the table. Absolutely, yeah, just, just before we came on, we were talking about that sort of top down, bottom up, you know, that, those cult those different cultural aspects. Senior leaders have a perspective they're trying to, to hit, they have goals and targets they're trying to hit. Uh, people in the shop floor have a different set of targets, but ultimately, you know, they're working towards the same outcomes, but they're measured differently, and I think that's probably kind of key. Understanding how people are measured is probably a, a real indication of, you know, the sort of culture that's there. …