The CMMS Playbook: Lessons from 25+ Years in Maintenance Tech - with Greg Christensen

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.

This episode discusses:

Industry Expert Insights: Greg, host of CMMS Radio, shares his 25+ years of experience in maintenance management, CMMS, and business development, offering valuable perspectives on industry evolution.

The Role of CMMS in a Digital Age: Discussion on the continued relevance of CMMS amidst AI advancements, the importance of foundational maintenance practices, and the risks of over-reliance on technology without strong processes.

Implementation Challenges & Best Practices: Key mistakes organizations make when deploying CMMS, including lack of buy-in, poor vendor selection, and failure to maintain engagement post-implementation.

Future Trends in Maintenance Tech: Predictions on AI-driven CMMS improvements, the potential for voice-enabled CMMS interaction, and a renewed focus on simplifying maintenance operations for efficiency.

Real Talk on Vendor & Client Relationships: Greg emphasizes the need for vendors to be honest about their capabilities, the importance of asking tough questions before selecting a solution, and how strong partnerships drive real business outcomes.

CMMS Radio: CMMSradio

Follow Greg on LinkedIn: https://www.linkedin.com/in/greg-c-7b97648/

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

If you're gonna continue to neglect the basic foundational elements of what right looks like. If you don't have that in place first, it doesn't matter what technology you're going to put in place. 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 someone I've got to know very well, um, via LinkedIn. I've actually been on, um, your podcast as well, Greg, but it's really lovely to invite you onto trend detection. Um, today, um, we're gonna talk about, um, CMMS, which I do struggle to say, so I'm gonna try to limit how much I say it. It's gonna be difficult because we're actually gonna talk about Greg's experience, over 25+ years. I don't wanna give away your age there, Greg, but, um, you've got a lot of experience in this area, and it's gonna be really fascinating to sort of discuss this topic with you as it's obviously very closely. Relates to a lot of the work we're doing at Sens side and predictive maintenance as well, lots of overlap there, but I guess before we get started, um, Greg, it'd be great if you sort of introduce yourself to the audience, um, yeah, over to you. All right. Well, Nile, it's awesome to be here. Thanks for inviting me. Uh, my name's Greg. I'm the host of CMMS Radio and been doing the podcast for a little over 3 years and my background was in the CMMS space. I was a co-founder of a solution. Uh, thanks to our awesome founder. We did a couple of businesses together and everything I've done really up until starting the podcast had to do with the maintenance management industry, a little bit in e-commerce and Um The, the whole idea behind, you know, like SASS and CMMS for me, it was born out of, out of past experiences, uh, work I did when I was younger, a business we built prior to launching the CMMS, and then I've stuck with it after we sold it, um, a couple of years and Then, uh, kind of left that gig one way or another, and here I am doing the podcast. It's a real pleasure for me. Love connecting with people like you, people to get their journey stories. Um, so that's kind of, that's kind of me in a nutshell, I guess. No, fantastic. We're gonna, we're gonna dive much deeper into that as well, um, but I guess the, the only place to start really, I guess is, you know, talk about your sort of vast experience, Greg, um, I guess what, you know, what drew you into sort of this space and, and has kept you in this space for so long, I guess that's, and, and started a podcast based on it as well, because that, that shows you, you know, you've obviously got a great passion for it, so where did that come from? So It really goes back to my teen years, the kind of work that I did being from the Midwest. Uh, we did things like janitorial, we worked in manufacturing, big or small. Uh, and then, you know, when I say we, uh, when I, when I got into the CMMS space, it was because of our, our founder of a solution platform. His name is Sean Dawson. Now, uh, he's dearly departed watching us from above, but I want to shout him out because I'm more of a co-founder on the ventures that we did together, kind of like, uh, living in that #2 spot, doing a lot of that work, business development, road paving, and all that. So, uh, what I mean by that is for the business, not actually working on roads. When we were, when we were young, we worked in different trades-related, manufacturing-related, and other similar businesses, um, not just together, but for others, and we would learn and then getting out to the West Coast, um, Sean started a building maintenance company and I jumped in and helped him grow it. Then I went off, did a few other things, then I came back and we grew it some more. And It was right there where we really Essentially dialed in our process for how we manage facilities and building maintenance operations, how we manage customer relationships and all those, you know, things, the goodness, and we. We did that the hard way, you know, with paper, uh, we really wanted to follow through and differentiate by doing what we said we were going to do, and that required documentation. We later got some software. We used a couple of other pieces of technology. Such as spreadsheets to manage different aspects of what we do. Fast forward into the early 2000s and Sean started to build a platform to manage that whole process the way we worked, and our clients were the ones using it with our account management process, all of that. They wanted to Use it for other workloads that we weren't involved in, so. He started another company, another venture, and then I jumped in to build that. That's where I really got deep in the weeds on CMMS. What is it? Why is it? Is it just work orders? Is it assets? Is it preventive maintenance? Is it inventory, on and on like that and been doing something with that ever since. We sold that bad boy in 2018. A little bit bittersweet for me because Uh, I wasn't ready to sell, but our two partners were ready to do some other stuff. So I said, all right, let's do it, guys. I don't want to hold you back. And then I went along for that ride. I kind of mentioned that earlier, uh, for about 2 years, and that leads me up to right here and right now. Um, I think I answered your question, but there's one little part you, I might have missed, which was where the passion comes from. Is that, am I right about that? Yeah, yeah, exactly. Yeah, for so long, you know, as well. So the, the passion, I think for me is really in how I've been in different parts of the industry, worked with so many facilities managers, maintenance managers. I now talk to countless maintenance and reliability professionals like Real Deal, and all those things kind of feed that passion. And I think maintenance people, top to bottom, all of them are salt of the earth. They really want to get stuff done. I love being a part of telling and sharing that story. I like to try to learn from every conversation, and I, I really am after this idea of chasing the elusive win-win. I want conversations, business dealings, all these things. To really yield dividends for, for all parties. So, I think that's where it really comes from, is a, a passion for what I've been involved in and seeing it unfold with success for so many people and solving problems one way or another. I think it is always fascinating when you can get somebody the outcome that they want rather than just taking their money. So, I kind of, I like to play with that theme a lot. I call people out kind of hard, maybe not too hard, but that's where the passion comes from. I mean, Uh, even with what you do, I mean, you see it, the people you get to talk to all these years with what you've been doing. It's rewarding and I'm not talking about money. Yeah, yeah, right, exactly, exactly, um, and I like that focus on business outcomes because when I, when I joined Sens I, it was a pre acquisition, um, I was always impressed by that focus. It wasn't about, you know, cos it's a great product, great AI product, you know, Gen AI product really cool, but it was always focused on like the outcomes for the customer, not on, hey, look at our cool AI product, look how cool it is. It does this and this. It was always a focus on that from the very start, and so I just wanted to call that out as well. Um, but, but on your, your journey, Greg, you know, selling two businesses are very, very impressive, but you must have learned a lot from that, you know. But I mean, what did you learn? What are the key, key things you learned from both of those, you know, Wow, that's a. That's a simple yet really, really big question because There's so many ways I can go in on that and Things I learned were really throughout my career and throughout being in industry, I think what I learned is it's far more important to listen to what the needs are. Focusing on what the problem is to solve that rather than pushing what you're selling. I think I learned that. I also learned a lot about, I'm not the best at being coachable, you know, I'm pretty, I'm pretty aggressive at times and it takes me a minute to let that sink in, but I was, I was pretty good, I think, at learning from the people I was around. And that really, I think is what helps me the most is when I realize, oh, you're not learning anything here, slow down and listen instead of, you know, waiting for your turn to talk, that kind of stuff. I think when it comes to overall industry and maintenance or manufacturing, anything in between, I also learned a lot about What the real outcomes are. Environment by environment and the realization that even if they're the same environments, they're not the same. You, you gotta always slow down a minute to kind of understand what's really, really happening in that environment. So, for example, If I have two manufacturers that, let's say, for example, they want to leverage technology or not, maybe they've got things going on with production, um, Of, let's say, tires, tire manufacturers. Well, they might be identical in the industry, but their environment's going to be different. The pieces of equipment they use might be the same, but different brands, the way they run them, how they're operated, and they might also have differing cultures in how they achieve their own maintenance excellence or operational excellence for throughput, and you have to always Give that little bit of space. I think I learned to understand them from where they're at before you come over the top with your solutions and your ideas, um. Yeah, and I've got a story about that, a recent one, if, if you want to hear it. Yeah, go for it. Yeah, so, uh, recently I was out in, um, Spartanburg, South Carolina, and I was, uh, I was with a friend of mine, Brian Bieski, and a bunch of great people at a manufacturing facility, and we were having a little conversation and kind of work, working some stuff out, whiteboarding some naming conventions within their CMMS platform, and That concept came up where, you know, sometimes people come in and they want to fit their perspective and understanding to the client's environment and it really has to be the other way around. The takeaway, just to keep the story short, was that if you've got something in place that's working in your naming conventions, your asset hierarchies, the way you manage, let's say, uh, tool rooms and parts rooms and inventory storage. If that's working, you don't always have to meet a particular standard. Say, for example, like an ISO standard, spot on, like top to bottom. There, there's kind of a hierarchy within those standards. And the bottom line is you got to go with what works for the client rather than trying to change them to what you know and understand. I don't know if that makes sense, but, uh, it's pretty, It's pretty common out there. And I think, I think a lot of, a lot of folks, software consultants, even team members, they're trying to do what they do rather than taking that breath, taking that beat and going, wait a minute, what's working here? So I kind of went, I went from a story to a soapbox. Sorry about that. That's, it's, I mean, you often see, maybe, you know, from a CMMS point of view that. Um, the technology is, you know, we want to see MMS, but there's often not too much talk about why, you know, and, and when we mention our business outcomes, is that, is that, you know, quite often the case. It's like, and it's the same with predictive maintenance, it certainly is from our point of view. Yeah, well, first of all, it, it, it's all over the board as to the why, the how, the when, when we're getting CMMS platforms, and there's also this ongoing theme of having technologies in place that are not built on people in process. And what I mean by that is, um, you might have systems that aren't meeting the needs, you might have systems in place that are meeting the needs, but somebody says they don't like it and they come in and want to change it. There's also a tendency for Clients and vendors alike, I wanna be mindful, right? I want to be fair, but There are no magic silver bullets, the CMMS, the EAM, the other technologies, the AI, whether it's surface level or actual, you know, real. Impactful functionality or or technology. None of that is going to work unless you take a very intentional approach to how you're implementing those solutions. It, it, it is always going to go back to the basics, your team, you got to get buy-in, you gotta get leadership understanding maintenance and operations. You got to get them kind of understanding leadership. That's really hard to do. That's why we're always going to see this change over and over and over and over. The thing you can do there is have contingency plans. Now, obviously, we could spin out and go on this, you know, CMMS 101 journey, um, but I'll sum that up too. When you're dealing with CMMS or related technologies in your maintenance, maintenance and reliability programs, facilities management, all of it. You've got to know what you're doing and why you're doing. And if you don't, um, there might be a few exceptions, but. Slow down just a little bit before you move forward and put your vendors to the test when they're trying to help you. If they're helping you, you're golden. If they're selling you, just be wary. Ask them really hard questions. I think most of them want to come through for you. So, um, sorry about the background noise. We got, we got a little noise going on if you hear any howling. No, that's OK. Often my, my cat likes to make an appearance. Um, hasn't done yet. I, I, but it's all good. pet pets are well contra detection. It's. Oh yeah, uh. Um, but in terms of that role, you know, we talk about technology, but the role of CMMS cos I think there's been a lot of advancements in, you know. Over in over the past year I guess we know Gen AI and things going on, onto the scene, but how do you sort of see, is CMMS still sort of relevant in this world of Gen AI, um. Yeah, I guess we could start there. I mean, yeah, yeah, yeah, yeah, it's, uh, it's absolutely relevant. And the thing that's not going to go away and the thing that's at risk is if those basics go away, if people continue, people, whoever, you know, you decide for yourself. I'm not here to judge anybody, but If you're gonna continue to neglect the basic foundational elements of what right looks like, if you don't have that in place first, it doesn't matter what technology you're going to put in place. And I will tell you something interesting I learned recently about AI as it relates to CMMS is. If, if it's the right kind of AI, the right kind of, you know, programmatic algorithmic, uh, machine learning tool that is taught right and is doing the right things, that can really help you. But I don't think CMMS is really going to go away. I do think there's going to be a few. Changes where people are going to go in from a technology angle that was once tried in the past that's gonna actually Maybe make a strong comeback, but I'm not, I'm not much of a, uh, you know, like a sage or an oracle when it comes to that. But, uh, I, I think part of your question was where the technology is really going. And I think there's gonna be, uh, A couple of companies out there that go in on the VR technology again, because now there's so much more understanding of what it is, how it is, and we're seeing good use case support for how that actually works where you can actually See what's potentially going to be done and all these different things about leveraging that technology. I do think on the AI. I think we're gonna see a continued washout of the surface-level AI. There's gonna be a few that sneak in there that don't do much, but it looks and sounds like it's really great stuff, but it's not doing anything. Um, sorry, just being straight up. Not sorry. Uh, the other thing you're gonna see is, uh, actual AI. When it, when the smoke clears, you're gonna see some real, real good things. I see a few companies out there that are doing that. I'm not the expert. This is what's really important about me and CMMS radio is Like maybe I'm a certain type of expert, but that's kind of problematic. My, my job is to find stories, tell stories, chirp a little bit about stuff I don't like. I don't know if I'm right, and I'm here to take the smoke, but the AI thing really is concerning to me overall in CMMS or otherwise because It makes, it can potentially make us lazy in what we do, or more so what we don't do. We stop maintaining the AI, we stop maintaining the CMMS, we stop maintaining our, our people and processes that were actually making an impact because There's that set it and forget it mentality, and that is not a thing. It just is not a thing. If, if that's where you're at, well, oh, we can just set that and forget it, rare, very, very rare. That, that's it. Soapbox over. No, no, of course, I mean, we're always talking about, um, within the context and the importance of, you know, human. You know, it's not a replacement tool, it's actually a supplementary. It's like a virtual, like virtual reliability engineer or something like that, so it's it's almost another team mate, but it's not a replacement for. For anyone, it's not gonna be there, you know, you won't get as much value out of it if, if humans actually use it and take action based on what it's telling you, right? So augmentation, yeah, yeah, exactly, exactly. Um, I mean, you know, we haven't talked about sort of like the implementation side either because um we know, um, sort of implementing predictive maintenance can be challenging, but from a TMMS perspective, um, Greg, what, what's your sort of take on that, um, you know what do organizations need to think about what, what often what mistakes often occur during. The most common mistake that I've seen and I still continue to see, I don't really know how to solve it, but the, the, the most common kind of pitfall is Seeking out Acquiring A CMMS or similar type platform and then not really doing much with it. And what I mean by that is sometimes when we as an organization initiate a project to either replace or find for the first time a CMMS or a similar technology, that's a lot of work in and of itself and then once that's done, there can be, I don't know if I'd call it a cooling period, but there's. There's a period of time where we can lose the kind of buy-in and the vigor for the project that's ahead of us because the project we just did, we landed it. OK, we made our choice, we selected it. The other thing that happens with that is once you have successful deployments and you have buy-in, you've got good frontline worker adoption, leaderships getting their appropriate KPIs, you're starting to get those outcomes, right? You're, you're essentially reducing. Some of your downtime, cause any reduction in downtime is going to be highly impactful in one way, shape or form, because you're eliminating a lot of waste. What invariably happens is there can be another series of tuning out, where maybe your champion leaves the company and now other people are less bought in on leveraging the platform and using it. Uh, a new leader or manager of some kind parachutes in and says, oh, I don't like that system and we're gonna get this one cause I love that one and I've been working with them for 1520 years, right? And the team's over there going, whoa, we've had this 23 years, we love this. We're getting good stuff done and like, I don't care. Those things can happen too. But what is really important when you select, implement, deploy, and start using your CMMS is that you have a, a cadence, a regular schedule of reinforcement with your team, regular check-ins, how's this going? Hey, you're all doing good with completing items, you're getting good details in there. …

Full transcript (WebVTT)