TRANSCRIPT 🔗
WEBVTT
00:00:00.080 --> 00:00:03.120
Hello, welcome back to another episode of the Reliability Gang podcast.
00:00:03.279 --> 00:00:05.280
I have a very special person with me today.
00:00:05.440 --> 00:00:06.879
I would like to introduce Jay Hack.
00:00:06.959 --> 00:00:07.839
How are you keeping, Jay?
00:00:08.000 --> 00:00:08.880
I'm keeping well.
00:00:09.039 --> 00:00:10.320
It's great to be here.
00:00:10.480 --> 00:00:13.519
It's great to have you at Accelerate 2026.
00:00:13.839 --> 00:00:23.839
And this is just a fantastic conference, and I loved sitting down with people like you who are out on the front lines and leading companies and leading people, moving maintenance and reliability forward.
00:00:24.079 --> 00:00:25.359
What an event it's been this year.
00:00:25.440 --> 00:00:26.960
Honestly, I've enjoyed it so much.
00:00:27.120 --> 00:00:36.960
Every time I come in, I get invited, meet so many people, so many people network, and so many engineering managers and people that obviously adopting the e-mailing software or other products and seeing everything like that.
00:00:37.039 --> 00:00:40.719
And I've got to say, like, Jay brings an incredible energy to this as well.
00:00:40.799 --> 00:00:45.600
So, like, really honored to have you on here to have a chat about some of the new features as well that we've seen.
00:00:45.679 --> 00:00:49.600
So, Jay's been kind of giving me a little bit of an insight to some of the cool features.
00:00:49.759 --> 00:01:00.079
And one thing we did do on Fort Leadership Day was trying to bridge generational gaps, trying to see how we can use technology to also make it easier for maybe different generations and what we've got.
00:01:00.320 --> 00:01:04.560
Jay was so excited the other day because he was like, Will, I wanted to pick your brains up, we've got some new features.
00:01:04.640 --> 00:01:05.120
What do you think?
00:01:05.280 --> 00:01:09.519
Because I think we have some good convos about kind of how we can use tech to influence what we're doing.
00:01:09.680 --> 00:01:13.680
I want you to talk about some of the new features that we've got with e-Main and what you've got.
00:01:13.840 --> 00:01:17.599
And how does that have an impact with general people that come in here?
00:01:17.760 --> 00:01:18.159
Absolutely.
00:01:18.319 --> 00:01:21.439
And I'll start off with a little bit about what I shared in my keynote.
00:01:21.599 --> 00:01:27.280
One of the key insights we've looked over over the past few years is generative AI and a lot of these technology features.
00:01:27.359 --> 00:01:28.799
I mean, it's like a rocket ship.
00:01:29.200 --> 00:01:30.640
You know, it's a sci-fos, isn't it?
00:01:30.799 --> 00:01:35.760
You know, I shared my personal story about how I use Chad GPT for uh my health goals.
00:01:35.840 --> 00:01:39.200
You know, I'm like tracking uh my sleep on my Apple Watch.
00:01:39.359 --> 00:01:48.640
I got my strength training goals and my food and you know, lab reports,
Load full transcript
you know, you upload it into Chad GPT and it'll say, you're not sleeping enough, you need to eat better.
00:01:48.799 --> 00:01:50.959
And like you can really accomplish some stuff.
00:01:51.040 --> 00:01:56.959
But if you look at how we do this in industry and professional corporations uh with maintenance reliability, we're not there yet.
00:01:57.040 --> 00:02:02.480
And so this was this was one of our insights uh kind of coming out of Accelerate last year.
00:02:02.560 --> 00:02:09.919
So we said that we're gonna figure out and we set the goal is by Accelerate 2026, we will have three new features launched.
00:02:10.000 --> 00:02:11.280
We ended up with four, which is really cool.
00:02:11.439 --> 00:02:23.759
Well, you know, about the about the Tolegate, then we might said we're gonna find three solid use cases, and so how we thought about this, Will, is we didn't just want technology for technology's sake, we wanted three practical applications.
00:02:23.919 --> 00:02:25.199
And so here's what we came up with.
00:02:25.360 --> 00:02:27.680
First one we came up with was talking to your data.
00:02:27.759 --> 00:02:32.960
This is the most obvious one, and there are other companies doing this, but we thought we'll tell you about our little twist on it.
00:02:33.039 --> 00:02:40.879
But we want to be able to actually ask for information in the system of record with emaint and get back actual like results.
00:02:41.280 --> 00:02:41.919
Okay, wow.
00:02:42.080 --> 00:02:43.199
So think about this.
00:02:43.280 --> 00:02:44.960
Uh, and this is the classic example.
00:02:45.120 --> 00:02:50.000
When I first tested this maybe six or eight months ago, I asked, How many forklifts do we have in all of our facilities?
00:02:50.080 --> 00:02:53.599
And we had a mock email account, it'll tell you what kind of batteries are we using.
00:02:53.680 --> 00:02:55.360
How often do the batteries need to be changed?
00:02:55.680 --> 00:03:09.439
And it's just spitting back information where before you had to go through and like triangulate reports, and you know, you had to be a primary user of the system that's working in e-main daily in some cases, or at least familiar with the reporting structure now.
00:03:09.520 --> 00:03:15.360
Like you may be the casual user, so we've expanded the people that can access the email database for information.
00:03:15.599 --> 00:03:16.159
Super cool.
00:03:16.400 --> 00:03:25.520
That is so handy because I think one thing that I found in my experience with CMMS, and we are maintained to a lot of optimization, and we kind of look for the gaps and see how they can work across lots of different CMMS systems.
00:03:25.599 --> 00:03:27.919
And we've experienced lots across the past, to be honest.
00:03:28.000 --> 00:03:36.719
And I think one thing about industry, one challenge is that if they've been using it for a long period of time, there's a lot of fear of changing and oh, we've done all of this work, how are we going to lose anything?
00:03:36.800 --> 00:03:41.599
Or you've got embedded purchasing systems that are very difficult to move away from different things and stuff like that.
00:03:41.759 --> 00:03:53.680
But what I do see a lot of is a lot of people struggle to use a system for basic things, and I think that feature there is very valuable in the sense that anyone can find information by voice, voicing it.
00:03:53.759 --> 00:03:54.719
Is it a voice recognition?
00:03:55.039 --> 00:03:55.919
We that's a separate feature.
00:03:56.000 --> 00:03:56.479
We'll get to that.
00:03:57.120 --> 00:03:58.319
We go, I'm jumping ahead of me.
00:03:58.400 --> 00:03:59.199
You're jumping ahead of me.
00:03:59.520 --> 00:04:00.319
We're gonna jump ahead.
00:04:00.400 --> 00:04:07.439
So let's just think of Chat GPT, yeah, except you're querying your system of record within EMA, you're querying the database.
00:04:07.680 --> 00:04:11.439
So you basically ask it, I want to see this, it will generate everything from it and it'll give you what you need.
00:04:11.680 --> 00:04:14.639
And so here's the important thing: really easy to set that up.
00:04:14.800 --> 00:04:20.160
What's really, really hard, harder than actually programming the AI, is thinking through all the implications.
00:04:20.399 --> 00:04:20.959
Okay, I see.
00:04:21.120 --> 00:04:25.439
And so we've done this in a very, very safe manner and a professional manner for our customers.
00:04:25.519 --> 00:04:27.040
And so I'll give you a few examples.
00:04:27.279 --> 00:04:36.160
The first time we we did this in the mock environment, you know, facility A can see all facility B's information and it gets mixed together, and you're like, okay, that's probably not great.
00:04:36.399 --> 00:04:44.000
Or uh maybe there's some proprietary information that you don't want the average person, you need some role to use cool stuff.
00:04:44.560 --> 00:04:51.120
Or maybe, you know, we had a write feature, which uh, you know, it's writing something to the database and it maybe it's going to the other plant.
00:04:51.360 --> 00:05:06.079
So we went through and we really were thoughtful and we partitioned this in a way where we think we nailed it in terms of uh having someone be able to consume information where they're supposed to and access what they're supposed to, and actually really think through this.
00:05:06.160 --> 00:05:08.160
So everyone should feel really good about this.
00:05:08.319 --> 00:05:16.079
It'll be in beta, still uh access for all e-mail customers and X5 now for the next month or two, and then it'll be uh fully in the production environment.
00:05:16.800 --> 00:05:26.800
But the second order effects, I'm gonna make a prediction in the industrial space that will be an increasing issue as people kind of for probably the next year or two, as people kind of work to think through all the implications.
00:05:26.959 --> 00:05:27.920
It's massive.
00:05:28.160 --> 00:05:28.639
Wow, yeah.
00:05:28.720 -->
00:05:29.920
I can I can see that being huge.
00:05:30.000 --> 00:05:35.519
And I think with software in in general, usually sometimes the smallest updates have the biggest impact.
00:05:35.600 --> 00:05:38.240
But you've got to really think your way through them problem-solving things.
00:05:38.319 --> 00:05:43.199
And how do you say, well, if I can solve a small problem, how's that able to solve a bigger problem across the whole organization?
00:05:43.279 --> 00:05:44.879
Which I really love that feature for that.
00:05:44.959 --> 00:05:51.120
That definitely, for me, if I was using that as a maintenance manager, I'd find lots of value within that as well.
00:05:51.199 --> 00:05:52.240
So that's that's amazing.
00:05:52.319 --> 00:05:53.759
So, what's the other feature today?
00:05:53.920 --> 00:05:55.759
So let's talk about our build feature.
00:05:55.920 --> 00:05:58.079
Yeah, it's an SOP generation.
00:05:58.240 --> 00:05:59.279
So this is really cool.
00:05:59.360 --> 00:06:05.199
If you think about how many OEM manuals there are across the world, you see them on the shelf, don't you?
00:06:05.920 --> 00:06:09.120
You walk in, there's a whole massive bookshelf of manuals.
00:06:09.680 --> 00:06:10.240
Yeah, I get it.
00:06:10.399 --> 00:06:23.199
And what ends up happening is one of our observations is let's say you have a motor or pump, you know, you'll upload the procedures you need into your CMMS, but then there's a procedure that's in the manual that you didn't, and then five years later you need it, you have to go back.
00:06:23.439 --> 00:06:27.199
So this feature is really cool because it allows you to do this in an automated fashion.
00:06:27.279 --> 00:06:34.399
You take manual, upload the PDF, it'll scan, or any type of maybe it's a non-OEM manual and it's just a general maintenance thing.
00:06:34.480 --> 00:06:39.600
It'll scan that PDF document and generate the SOPs that you need for work orders.
00:06:39.839 --> 00:06:40.079
Wow.
00:06:40.480 --> 00:06:42.240
And it's automatically.
00:06:42.319 --> 00:06:48.000
So you you put their manual in, it will feed it'll say we found these 30 different things in the manual.
00:06:48.319 --> 00:06:49.439
This is what we need to do.
00:06:49.759 --> 00:06:56.000
And these are the four different motors it applies to, and it'll automatically generate steps in there.
00:06:56.079 --> 00:07:09.439
And then the maintenance we do want a human in the loop because it is AI, so let's say it's 80 or 90 percent correct, and maybe in your facility you want to have things done a little bit different way to a higher standard or maybe extend an interval.
00:07:09.600 --> 00:07:10.560
All that's okay.
00:07:10.720 --> 00:07:19.040
The human is in the loop that's approving these, of course, yeah, and maintain control over your maintenance procedures, but talk about time savings.
00:07:19.279 --> 00:07:20.560
Wow, yeah, that's that's huge.
00:07:20.720 --> 00:07:21.199
That's huge.
00:07:21.279 --> 00:07:24.800
I mean, I think to be able to, and again, this is another problem in the industry, right?
00:07:24.879 --> 00:07:29.600
This is why I quite like these solutions because they are kind of solving frontline issues that we've got.
00:07:29.759 --> 00:07:35.199
When we do PM optimization as well, and we're looking at these things, we are looking through manuals and all the rest of it, but where is it going?
00:07:35.279 --> 00:07:37.439
How is it actually being generated within the system?
00:07:37.600 --> 00:07:44.240
And I think information and data, there's a lot of things that could probably do that, but how is centralizing the same system is the important part, really, isn't it?
00:07:44.319 --> 00:07:55.040
If you can manage that workflow and gradually start adding all of these manuals in, and also look what you're doing with your database, you're actually now forcing yourself to put all the information in one place rather than being on the shelf.
00:07:55.360 --> 00:07:56.480
You know, it's brilliant.
00:07:56.720 --> 00:08:02.800
Yeah, but not only PMs, if you have something that's not a PM and it's in the maintenance book, that's now in your procedure.
00:08:02.879 --> 00:08:03.360
Yeah, it's not.
00:08:03.439 --> 00:08:06.639
So let's say it's SOPs and just the way that you know just the way it's done.
00:08:06.800 --> 00:08:08.480
So you can get you can get everything in there.
00:08:08.720 --> 00:08:10.959
That's really, really powerful and really time-saving.
00:08:11.360 --> 00:08:11.839
Yeah, I agree.
00:08:11.920 --> 00:08:13.759
And I think that's where the industry needs to improve.
00:08:13.839 --> 00:08:15.920
I do feel like we don't have enough SOPs.
00:08:16.000 --> 00:08:19.839
There's not a lot of an alignment with say engineer A and engineer B doing the same jobs.
00:08:20.000 --> 00:08:23.759
How do you know and how can you measure that they're doing the same thing and it's consistent?
00:08:23.920 --> 00:08:25.199
Because that's what maintenance is, right?
00:08:25.279 --> 00:08:34.879
It's consistency and it's making sure that you can continue to do the same process no matter who it is, and you still get the same results, which can be difficult to do depending on who's doing this stuff, right?
00:08:35.039 --> 00:08:36.960
So let's go to our third feature.
00:08:37.039 --> 00:08:39.919
This is the feature you seem most excited about, you know.
00:08:40.000 --> 00:08:41.519
So I'm like firing up here.
00:08:41.919 --> 00:08:43.120
This is the the talk feature.
00:08:43.200 --> 00:08:46.720
So in natural language, you can use your voice to generate a work order.
00:08:46.799 --> 00:08:52.159
And so let's say I'm walking through the facility, I got my mobile phone out, I see something that uh needs to happen.
00:08:52.240 --> 00:08:57.600
I can pull up my phone and just talk into it and be like, hey, I'm walking through the facility at point ABC.
00:08:57.919 --> 00:09:04.080
I notice that this pump uh it's making
a noise, and uh this is what's happening.
00:09:04.240 --> 00:09:10.159
Whatever my natural language is, it will parse out what that is and put it into the exact fields of the work order.
00:09:10.399 --> 00:09:10.639
Wow.
00:09:10.799 --> 00:09:12.000
So it will okay.
00:09:12.080 --> 00:09:13.759
Just let me just get this uh this straight.
00:09:13.840 --> 00:09:15.039
Say I'm work order requests.
00:09:15.360 --> 00:09:15.759
Yeah, work order.
00:09:16.000 --> 00:09:18.159
So I'm walking around site, I see a pump leaking.
00:09:18.240 --> 00:09:20.879
Yeah, like, right, okay, I named the asset.
00:09:21.039 --> 00:09:24.399
This is where the asset is, here's the location, here's where it's leaking.
00:09:24.559 --> 00:09:31.039
It will transcribe that and it will put it in where it is with that asset within within the work order request.
00:09:31.200 --> 00:09:32.320
Within the work order request.
00:09:32.480 --> 00:09:33.919
Oh, okay, I see amazing.
00:09:34.399 --> 00:09:36.240
And so so what it is is it's a shortcut.
00:09:36.480 --> 00:09:45.279
People, you know, instead of pump broken or pump making noise, or instead of someone seeing it, saying I need to report that, getting back and completely forgetting.
00:09:45.360 --> 00:09:50.879
Because let's let's be honest, this I'll be honest with you, it within maintenance, this happens all the time.
00:09:51.039 --> 00:09:55.120
I don't really think that engineers want to not put this stuff in the system.
00:09:55.200 --> 00:09:58.799
That that's of course they don't, but what happens is complacency kicks in.
00:09:58.879 --> 00:10:01.679
And I think this is where technology can help the general engineer.
00:10:01.840 --> 00:10:07.039
If it's easier, you've got to make it so easy for the guys to do something.
00:10:07.360 --> 00:10:10.399
So when they do do it, it becomes more habitual.
00:10:10.639 --> 00:10:20.159
But like most CMS systems that we're dealing with nowadays, I know some have smart apps and you can even put it in, but to even be able to voice note in it's just so much easier.
00:10:20.320 --> 00:10:25.919
And I think that is quite revolutionary in the sense that the easier you make it, the more information you feel.
00:10:26.159 --> 00:10:31.919
And the more information you get, the better your maintenance is more, the more data you have, the more records you have.
00:10:32.000 --> 00:10:42.320
So what the desired intention is, is lower the barriers of entry for someone creating a work order request and then increasing the fidelity of uh what that work order request actually has.
00:10:42.399 --> 00:10:43.279
So you have more information.
00:10:43.840 --> 00:10:50.159
But that's what I think it is, because I think when you write down what you see in your brain, essentially to what you write is very different.
00:10:50.240 --> 00:10:50.879
Do you know what I mean?
00:10:50.960 --> 00:10:58.080
And how you explain things because I think some people, when they write things, struggle to explain what they think, if that makes sense.
00:10:58.320 --> 00:11:01.519
Because if we're saying it, I feel like you're gonna get more information there.
00:11:01.600 --> 00:11:09.519
And if you do that across all of your technicians, and say if you've got five or six technicians across the site, and or even operators, you know, operators are the guys uh next to the machine, right?
00:11:09.600 --> 00:11:11.440
They're the ones hearing it, feeding or whatever.
00:11:11.600 --> 00:11:15.200
Giving that feature to them guys is gonna significantly improve the whole process.
00:11:15.360 --> 00:11:16.399
So that's what we're hoping.
00:11:16.480 --> 00:11:24.080
So we've been tested uh ahead of launch with about or uh about 12 or so customers, and I think we're gonna see a lot is what was the feedback?
00:11:24.159 --> 00:11:24.879
Was the feedback good?
00:11:24.960 --> 00:11:26.960
Is that what you kind of feedback is good?
00:11:27.120 --> 00:11:30.000
I think what we need to see is how is it used in the wild?
00:11:30.320 --> 00:11:37.120
Probably had two dozen people, you know, play around with this, but we can extrapolate this from 20 text to 2,000 text.
00:11:37.440 --> 00:11:38.240
Yeah, how does that scale up?
00:11:38.399 --> 00:11:39.200
How does that scale?
00:11:39.279 --> 00:11:39.919
What are we finding?
00:11:40.000 --> 00:11:44.799
Is are we finding maybe the microphone isn't capturing in a noisy environment or we need to adjust things?
00:11:44.960 --> 00:11:46.159
But look, we can do that.
00:11:46.320 --> 00:11:48.799
And so that's one of the things that's really cool about software, right?
00:11:48.879 --> 00:11:51.679
Is you can iterate and you can make directions, improve it, yeah.
00:11:51.840 --> 00:11:56.159
And we can find out, and we don't have to like bring things back in, it just we can just push it out.
00:11:56.320 --> 00:11:58.240
And I think that's what you know this is about sometimes.
00:11:58.399 --> 00:12:11.200
These features don't seem like, oh my god, this is like rockets, but it's the implementation and the ability to be able to make sure that because like systems can be built to work, right, but they're only as good as the users and what we do to be able to implement them.
00:12:11.279 --> 00:12:12.000
Do you know what I mean?
00:12:12.080 --> 00:12:21.039
So making it easier to use, I think generally is going to improve overall output of it all, and it's gonna allow clients to be able to get on top where they keep their central information, really.
00:12:21.120 --> 00:12:21.759
Do you know what I mean?
00:12:21.840 --> 00:12:26.159
Because that is the brain box of their whole operation, really, is such an important part.
00:12:26.320 --> 00:12:30.320
And um, many sites we see don't really utilize it to the full potential.
00:12:30.399 --> 00:12:34.639
So you're missing out there on efficiencies and effectiveness through the maintenance practices.
00:12:34.720 --> 00:12:36.639
So, yeah, I I
love them personally.
00:12:36.720 --> 00:12:44.799
Like, I think I see a lot of value in them, and I'm hoping that you guys see your customers, and hopefully you get the feedback, and hopefully you get the value coming near it.
00:12:45.120 --> 00:12:52.080
Yeah, and it'll take this again, it takes a while for these things to happen and you know and go through, but there's definitely some long-term value there.
00:12:52.240 --> 00:12:53.919
You ready for our uh feature number four?
00:12:54.080 --> 00:12:54.879
Is this oh easy?
00:12:54.960 --> 00:12:57.279
I don't think I've heard this one, so this is gonna be doo-doo.
00:12:57.919 --> 00:12:59.679
Uh this is the learn feature.
00:12:59.840 --> 00:13:04.399
This is a derivative of of uh the AI assist, which is the uh talk to your data feature.
00:13:04.480 --> 00:13:14.399
So when we were testing this, this is one we hadn't planned, but it came up in testing, and this was like quite catalyzing, it's the easiest of the four to do, and people were most excited about it.
00:13:14.480 --> 00:13:16.240
And so you don't you can't predict these things.
00:13:16.320 --> 00:13:18.080
And I was just, you know, I'll tell you, this is real.
00:13:18.159 --> 00:13:28.879
I was on my way walking to this podcast, and literally one of my customers stopped me and they're like, they were talking about I have a plan in Japan, Germany, and the US, and the translations between these are really hard.
00:13:29.039 --> 00:13:41.919
And we designed a tool where when you have document data repositories, you can ask for information and it will scan through the manual, search for that, parse out what you're looking for, and then translate it into the language that you need.
00:13:42.080 --> 00:13:43.039
Wow, that's incredible.
00:13:43.440 --> 00:13:49.120
And so this is such a simple thing with the AI technology, but such the most powerful thing.
00:13:49.200 --> 00:13:55.039
And okay, like it's 90% correct or 95% correct, but for most applications, it's gonna work, yeah.
00:13:55.279 --> 00:13:59.279
It's gonna work, and it's gonna give you uh enough insight to know what you need.
00:13:59.360 --> 00:14:07.360
And so what we're seeing is, and and you probably realize this with your customers, is we're seeing more global rollouts to be made across countries and cultures.
00:14:07.519 --> 00:14:12.000
We're seeing a desire to standardize and have more digital transformation.
00:14:12.159 --> 00:14:16.639
And one of the key insights that we have is this is hard with language or cultural barriers.
00:14:17.039 --> 00:14:17.279
Yeah, yeah.
00:14:17.679 --> 00:14:21.840
And so this feature is designed to help address and alleviate some of those concerns.
00:14:22.399 --> 00:14:27.600
I can see that being really valuable even for some, maybe some of our customers as well, because we're doing a lot more work in Europe now.
00:14:27.679 --> 00:14:29.360
And in Europe, you know, it's a big place.
00:14:29.440 --> 00:14:37.919
I mean, often compared to the US, but you've got lots of countries within Europe, and you can travel across borders and there's different language barriers between them.
00:14:38.080 --> 00:14:38.799
Does that make sense?
00:14:38.879 --> 00:14:38.960
Yeah.
00:14:39.200 --> 00:14:46.399
But what we're trying to do as well as a function in some of these customers is start to standardise and align a lot of the SOPs, the standards, the practice.
00:14:46.480 --> 00:14:48.639
We need that aligned right across all of the plants.
00:14:48.720 --> 00:14:50.960
But what is difficult sometimes is the language barriers.
00:14:51.120 --> 00:14:59.120
So the principles are the same in terms of what we're trying to teach them in terms of reliability practice, but how do we get around the language barriers and stuff like that?
00:14:59.279 --> 00:15:16.720
Which is you know, this here seems like a great solution to some of that, and you know, some of them things of how do we make sure we can communicate in the same practice of reliability but across different countries, which could I could imagine we're starting to find it a bit challenging because we're now like, oh, okay, they do speak English, but they need these manuals in German.
00:15:16.799 --> 00:15:17.360
Do you know what I mean?
00:15:17.440 --> 00:15:22.639
So we're like our normal content doesn't like oh, we have to you know change a few rounds and all the rest of it.
00:15:22.720 --> 00:15:24.000
So, you know, I get it, I get it.
00:15:24.080 --> 00:15:25.519
I I see the value in that.
00:15:25.759 --> 00:15:30.559
And just for you, Will, I can give you a preview of some of the things that we're thinking about.
00:15:30.639 --> 00:15:37.840
These are not new features or uh anything on our roadmap, but there's things that we're thinking about that are really cool and exciting.
00:15:38.080 --> 00:15:38.799
You interested?
00:15:39.039 --> 00:15:40.080
Come on, give it to me.
00:15:40.159 --> 00:15:43.759
Let's let's so so think about this with uh work order history.
00:15:43.919 --> 00:15:46.480
Let's take your company and the reliability gang.
00:15:46.639 --> 00:15:48.080
You have how many employees now?
00:15:48.240 --> 00:15:49.440
Ten, ten guys work less.
00:15:49.759 --> 00:15:50.639
So let's flip this over.
00:15:50.799 --> 00:15:55.919
Let's say it was in a facility and you knew every work order every one of your people were working on.
00:15:56.080 --> 00:16:02.799
And so you can make assumptions saying, Oh, well, well, Crane ain't available today, and I need to have a vibration job, and it's really hard.
00:16:02.879 --> 00:16:05.279
It's a it's a uh technical job, yeah, yeah.
00:16:05.440 --> 00:16:09.440
It's a technical job, and like I have uh one of my other employees available.
00:16:09.600 --> 00:16:14.320
You could ask the AI potentially, hey, this person has done all these types of work orders.
00:16:14.399 --> 00:16:16.639
You could see every work order that employee's done.
00:16:16.799 --> 00:16:18.240
Do you think he could do this job?
00:16:18.639 --> 00:16:20.879
Okay, that's very okay, yeah, yeah.
00:16:21.200 --> 00:16:24.399
And it'll be like, hey, look, he probably doesn't have the right experience.
00:16:24.480 --> 00:16:26.720
You know, he may need to be able to, he may need some more.
00:16:26.799 --> 00:16:31.759
Oh, or absolutely, he's done all these, and we think he can do it based off this fact pattern.
00:16:31.919 --> 00:16:33.440
We've seen these people be successful.
00:16:33.519 --> 00:16:34.799
So trendy.
00:16:34.960 --> 00:16:37.360
So there's some competency things that we're looking at.
00:16:37.519 --> 00:16:45.519
And maybe, I don't know, I'm gonna say five years in the future, maybe a technician has a portable record where they now have all record of every job they've ever done.
00:16:45.600 --> 00:16:46.960
So now you have a different credential.
00:16:47.279 --> 00:16:49.600
I mean, the possibilities here are quite endless.
00:16:49.759 --> 00:16:50.399
Yeah, I can imagine.
00:16:50.559 --> 00:16:51.440
And super exciting.
00:16:51.519 --> 00:16:54.879
And I want to be clear this is this is something that we're thinking about.
00:16:55.039 --> 00:17:07.680
Yeah, we haven't quite figured out what the future looks like, but this is coming where we will know so much more information about asset types, maintenance professionals, and how the intersections are than we ever have in the past.
00:17:07.920 --> 00:17:15.519
You can ask questions of I got a vibration tech, how long will it take him to become a certified person in ultrasound based off of this experience?
00:17:15.680 --> 00:17:17.759
And you'll have a prediction of how fast he can work.
00:17:18.000 --> 00:17:18.559
That's pretty cool.
00:17:18.640 --> 00:17:19.359
That's pretty cool.
00:17:19.680 --> 00:17:23.279
What I love about that is as well, I think, again, businesses like ours is quite small.
00:17:23.359 --> 00:17:27.680
But if you were looking at big organizations that we deal with, competencies is a problem.
00:17:27.839 --> 00:17:34.160
Like you've got guys there that may be on the same level, but you've got to look at some of the jobs that are done in a plant.
00:17:34.319 --> 00:17:37.680
They can be so vast, you know, they're not they're not all the same thing, you know.
00:17:37.839 --> 00:17:57.839
When it comes down to what we're doing, vibration analysis, okay, there's a lot of things we do, but say, for example, you've got guys in the plant, and it's, you know, they need to be able to fix an electrical problem, and you've got electricians and you've got your electrical team, there's still abilities within that electrical team that you might have an engineer's not quite capable enough to do some of them jobs because of their experience, not just based on their qualification.
00:17:58.000 --> 00:18:00.720
So I think competencies and stuff like that, that that would be huge.
00:18:00.799 --> 00:18:02.480
That would
so there's a lot of interest here.
00:18:02.559 --> 00:18:05.279
You know, they might say, Yeah, you could learn how to do that job in a week.
00:18:05.440 --> 00:18:07.920
Jay, man, you're gonna you know, I might take me a year.
00:18:09.119 --> 00:18:10.480
This is real, you know.
00:18:10.640 --> 00:18:13.200
But um And the idea and the premise is very good.
00:18:13.279 --> 00:18:18.880
And this I think this is why I like speaking with you, Jay, because you're always thinking about how to solve the problems.
00:18:18.960 --> 00:18:19.599
Do you know what I mean?
00:18:19.680 --> 00:18:24.559
And and I think as more of a problem-solving kind of thought process, it's almost like a philosophy, isn't it?
00:18:24.640 --> 00:18:36.160
You know, we've got these systems, we know that they exist, but what really splits the margin, what really makes the difference is how do we approach the problems and how do we actually say on a ground level, how can I help you?
00:18:36.319 --> 00:18:42.160
You know, how can I help the technician there that's are fed up with old CMMS or fed up but doesn't use it or doesn't believe in it?
00:18:42.319 --> 00:18:44.559
How do we inspire them guys to get on board?
00:18:44.720 --> 00:18:53.359
And a lot of these things are are designed for that kind of front force workforce to work more effectively, and that's where the buyer needs to be.
00:18:53.440 --> 00:18:57.279
You know, these guys need to use it because if they don't, the whole system falls on itself.
00:18:57.839 --> 00:19:01.359
We talked a little bit about uh before the podcast started about the generational gap.
00:19:01.440 --> 00:19:08.880
I mean, like young people want to use technology, you know, they don't want to use like uh something that's with like complex transactional codes.
00:19:08.960 --> 00:19:10.799
They want to use something that that's easy.
00:19:10.880 --> 00:19:15.279
You know, I joke, you saw me tag you in a post about my 14-year-old daughter.
00:19:15.359 --> 00:19:19.839
You know, we're trying to get her get her excited to be a part of the reliability game.
00:19:20.000 --> 00:19:21.359
Oh, it's like brilliant great choice.
00:19:21.920 --> 00:19:24.960
Her usage of technology, it's like fantastic.
00:19:25.119 --> 00:19:29.759
She uses, she's learning in school the same program eMate uses uh to do their wireframes.
00:19:30.000 --> 00:19:30.480
It's crazy, right?
00:19:30.720 --> 00:19:37.519
And like you think of the this generation and and how they're using tech now, you think of what they can be doing in the next 10 years, 15 years.
00:19:38.480 --> 00:19:42.960
She will have an expectation if she's working in this industry that those tools are available.
00:19:43.279 --> 00:19:44.319
Yeah, it is just a norm for her.
00:19:45.279 --> 00:19:47.920
And so, like, if it doesn't have it, it's gonna be like, man, that stinks.
00:19:48.000 --> 00:19:54.720
So we gotta be really on the forefront of trying to do this and trying to make it
uh I I you know, we're only as good as customer adoption.
00:19:54.880 --> 00:19:55.119
Yeah.
00:19:55.279 --> 00:19:59.839
And so really being thoughtful, and I think these features kind of help us along that adoption curve.
00:20:00.000 --> 00:20:04.480
Yeah, and it kind of bridges the gap as well between the older generations because, you know, they have all the knowledge, right?
00:20:04.640 --> 00:20:08.720
And they've got all this experience, and we've got this new generation coming in that will adopt tech quite easy.
00:20:08.880 --> 00:20:17.359
And if we can use some of the things that you're doing here to almost bridge that gap a little bit, you know, you've got collaboration then, you've got the knowledge that it's potentially going to be lost very soon.
00:20:17.519 --> 00:20:24.799
Going into, you know, younger generation as well that are able to use the technology, and if you can marry the two together, I think that is a recipe for success.
00:20:24.960 --> 00:20:27.279
That's that leads me to my last question, Jay.
00:20:27.359 --> 00:20:27.440
Okay.
00:20:27.759 --> 00:20:29.039
Speaker, great podcast.
00:20:29.200 --> 00:20:30.960
This is kind of a bit of a closing thought.
00:20:31.119 --> 00:20:33.519
We know technology is moving fast, it's it's rapid.
00:20:33.839 --> 00:20:36.640
You know, you spoke about your daughter using all of these codes and programs.
00:20:36.720 --> 00:20:40.480
You've got kids programming code now and doing all of this crazy stuff.
00:20:40.720 --> 00:20:43.200
Technology's moving, and I don't think we can stop it.
00:20:43.440 --> 00:20:45.440
It is kind of on its own train.
00:20:45.599 --> 00:20:53.359
But the culture part of what we're trying to do and align with is very slow, and trying to get people to use some of these systems and know the whys is can be a little bit elongated.
00:20:53.440 --> 00:21:00.960
How do we speed up the process of really getting people to understand and align that technology gap to the culture gap that we're finding?
00:21:01.200 --> 00:21:03.920
Really difficult with some customers, some customers better than some.
00:21:04.240 --> 00:21:09.759
But you know, you've got customers wanting to put AI and everything, they haven't even really sort of their CMMS outwards or and all these things.
00:21:10.240 --> 00:21:11.200
So there's a couple things.
00:21:11.279 --> 00:21:12.480
This is a leadership question.
00:21:12.559 --> 00:21:12.720
Yeah.
00:21:12.880 --> 00:21:14.960
And there's a few things here I'm really hopeful on.
00:21:15.119 --> 00:21:23.680
One is information becomes more centralized, and IT systems like eMate become more deployed at senior levels in the organization.
00:21:23.839 --> 00:21:28.559
Like digital transformation officer, that title didn't really exist 15 years ago.
00:21:28.640 --> 00:21:31.680
Now that's a primary stakeholder here.
00:21:32.559 --> 00:21:42.160
So the conversations have become elevated, the awareness becomes elevated, the data becomes more consolidated and visible, the impact of not doing this becomes more visible.
00:21:42.319 --> 00:21:46.079
It gets more senior leader attention that drives a culture change.
00:21:46.160 --> 00:21:51.599
And if you look at this, if you look at the attendees just at our conference, you know, go back 15 years ago.
00:21:51.839 --> 00:21:56.000
Today we have directors and VPs of maintenance that attend, like that was not as common.
00:21:56.079 --> 00:22:08.240
That's why we started Thought Leadership Day is to have programming for both users of the system, but also directors and VPs that administer the system as well and think about what they're doing in their organization and decisions.
00:22:08.400 --> 00:22:11.680
Yeah, that's a fantastic trend that plays in this favor.
00:22:12.000 --> 00:22:18.640
I think also as organizations become more lean, you know, the leadership and the relationships become more important.
00:22:18.799 --> 00:22:20.720
Employees have a choice of where they work.
00:22:20.960 --> 00:22:21.759
Yeah, yeah, you're right.
00:22:21.839 --> 00:22:25.119
Yeah, and they're gonna want to choose somewhere and they're gonna want to choose, right?
00:22:25.200 --> 00:22:31.359
Yeah, they're gonna want to choose to be in a good culture, and so this will force companies to adapt.
00:22:31.519 --> 00:22:36.960
And so I think those two trends play very much in favor of some of those cultural shifts.
00:22:37.119 --> 00:22:37.839
No, that's a great idea.
00:22:38.079 --> 00:22:42.480
And having people like you in the industry also, that's a little bit exciting, starting new companies.
00:22:42.640 --> 00:22:43.759
I'm very hopeful for the future.
00:22:44.079 --> 00:22:44.720
Yeah, so am I.
00:22:44.799 --> 00:22:45.519
And you know what?
00:22:45.599 --> 00:22:49.920
I love that point that you've raised in terms of you know, is the company got a good culture?
00:22:50.000 --> 00:22:51.759
Because you need to attract the talent as well, right?
00:22:52.240 --> 00:23:01.920
You can't have a culture that doesn't look for the future, doesn't look for the visions, because people are not going to align with that now, and especially with the new generation, they want to see progress, so they want to see that that actually adding value to the progress.
00:23:02.000 --> 00:23:04.480
And if you're not adopting that culture, you have to be forced to.
00:23:04.559 --> 00:23:05.839
So, yeah, that's a really good point.
00:23:06.079 --> 00:23:08.640
But I just want to thank you for it's a pleasure as always.
00:23:09.039 --> 00:23:09.359
Honestly.
00:23:09.440 --> 00:23:16.000
Uh, it's been, I guess, I last time I saw you was at Main Tech, but I always like catch it up, but I always like seeing what's going on with the reliability gang.
00:23:16.160 --> 00:23:18.160
Well, again, always a pleasure, Jay.
00:23:18.240 --> 00:23:20.880
And you always bring a real good energy, a good vibe.
00:23:20.960 --> 00:23:22.799
And I just could interview you all day if we could.
00:23:22.880 --> 00:23:24.640
Like, I don't got enough time to have to keep going.
00:23:24.720 --> 00:23:29.920
But honestly, thank you so much for your time, and I really appreciate you coming on the Reliability Gang podcast.
00:23:30.079 --> 00:23:30.319
All right.
00:23:30.480 --> 00:23:30.720
Thank you.
00:23:30.880 --> 00:23:31.599
Take care, Jay.