WEBVTT
Language: en-US

1
00:00:05.449 --> 00:00:11.390
<v Nick Leeder>So I, I think to start with, you know,
everybody loves to have the idea of scale,

2
00:00:11.729 --> 00:00:15.789
<v Nick Leeder>but it's about who we're dealing with and
who we're talking to often has a very big

3
00:00:15.789 --> 00:00:17.190
<v Nick Leeder>bearing in that conversation.

4
00:00:17.850 --> 00:00:21.010
<v Nick Leeder>So if you're speaking with the maintenance
technicians and teams that are actually

5
00:00:21.010 --> 00:00:26.569
<v Nick Leeder>doing the job, the boots on the ground,
their world is really related to their

6
00:00:26.569 --> 00:00:26.969
<v Nick Leeder>plant.

7
00:00:27.690 --> 00:00:33.569
<v Nick Leeder>And the context of scale for them is about
scaling the assets they are measuring and

8
00:00:33.569 --> 00:00:35.770
<v Nick Leeder>monitoring within that plant.

9
00:00:35.979 --> 00:00:37.569
<v Nick Leeder>So I'm trying to define what scale means.

10
00:00:38.299 --> 00:00:41.750
<v Nick Leeder>But you, for example, if I'm speaking to a
chief operating officer that's

11
00:00:41.750 --> 00:00:48.389
<v Nick Leeder>responsible for 5 plants or 20 plants,
scale to them means actually

12
00:00:48.389 --> 00:00:53.869
<v Nick Leeder>deploying the same solution across
multiple plants and increasing their visibility

13
00:00:53.869 --> 00:00:56.290
<v Nick Leeder>of the health and performance of those
plants.

14
00:00:59.299 --> 00:01:04.500
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens, and now your host, Nel

15
00:01:04.500 --> 00:01:05.019
<v Speaker 2>Sullivan.

16
00:01:09.720 --> 00:01:13.860
<v Niall Sullivan>Hello and welcome to the latest episode of
the trend detection podcast.

17
00:01:14.519 --> 00:01:18.279
<v Niall Sullivan>Um, I'm really pleased to be joined today,
um, by another, um, external guest, an

18
00:01:18.279 --> 00:01:23.870
<v Niall Sullivan>external expert, Nick Leader, who's
actually, um, an advisor and coach to a lot of

19
00:01:23.870 --> 00:01:25.360
<v Niall Sullivan>manufacturing businesses, and we've.

20
00:01:26.000 --> 00:01:30.319
<v Niall Sullivan>Um, has a lot of insights to share, you
know, uh, and particularly around the topic

21
00:01:30.319 --> 00:01:34.760
<v Niall Sullivan>today that we're talking about, which is
all about, um, why predictive maintenance

22
00:01:34.760 --> 00:01:36.089
<v Niall Sullivan>projects don't scale.

23
00:01:36.269 --> 00:01:41.120
<v Niall Sullivan>And anyone who listens to this podcast on
a regular basis will know, um, we, we've

24
00:01:41.120 --> 00:01:42.559
<v Niall Sullivan>covered this at lots of different angles
as well.

25
00:01:42.639 --> 00:01:43.720
<v Niall Sullivan>It's always a big challenge.

26
00:01:44.129 --> 00:01:47.879
<v Niall Sullivan>And I think from a customer's perspective,
it's sort of knowing where to start,

27
00:01:48.129 --> 00:01:51.860
<v Niall Sullivan>when's the right time to scale, what they
need to think about, um, and all those

28
00:01:51.860 --> 00:01:53.540
<v Niall Sullivan>things we're gonna talk about today.

29
00:01:53.730 --> 00:01:57.620
<v Niall Sullivan>But I guess before we dive into the topic,
I'll just like hand over to you, Nick,

30
00:01:57.669 --> 00:02:00.339
<v Niall Sullivan>just to sort of introduce yourself and
we'll go, go into it.

31
00:02:00.449 --> 00:02:01.319
<v Niall Sullivan>So over to you.

32
00:02:01.769 --> 00:02:05.540
<v Nick Leeder>Brilliant, well, look, thank you for the
opportunity today to, to speak with you

33
00:02:05.540 --> 00:02:06.199
<v Nick Leeder>around this topic.

34
00:02:06.300 --> 00:02:11.210
<v Nick Leeder>Um, you know, my background is really, uh,
30 odd years, which is really worrying

35
00:02:11.210 --> 00:02:13.559
<v Nick Leeder>actually when I start looking at the
amount of gray hairs on my head.

36
00:02:13.910 --> 00:02:20.309
<v Nick Leeder>Um, working in manufacturing businesses,
uh, exclusively on the, the transformation

37
00:02:20.309 --> 00:02:25.589
<v Nick Leeder>of operations in engineering and in
manufacturing, um, and I've done that across the

38
00:02:25.589 --> 00:02:32.470
<v Nick Leeder>world for big names like SKF and Dyson,
uh, and Phillips, uh, but also for

39
00:02:32.470 --> 00:02:38.369
<v Nick Leeder>mid-sized businesses as well that are
seeking to, to, uh, gain competitive advantage

40
00:02:38.369 --> 00:02:40.550
<v Nick Leeder>or improve operating efficiency, so.

41
00:02:41.020 --> 00:02:45.660
<v Nick Leeder>I spend my days brilliantly um and I
really enjoy it every week, getting out to

42
00:02:45.660 --> 00:02:49.820
<v Nick Leeder>manufacturing businesses and understanding
what they're doing and seeing how all

43
00:02:49.820 --> 00:02:54.419
<v Nick Leeder>these buzzwords we deal with on a daily
basis in the world of digital actually have

44
00:02:54.419 --> 00:02:56.460
<v Nick Leeder>something meaningful to their
organization.

45
00:02:57.869 --> 00:03:01.580
<v Niall Sullivan>Excellent, excellent, and I guess just to,
you know, before we go into sort of the,

46
00:03:01.740 --> 00:03:04.789
<v Niall Sullivan>you know, particularly about, you know,
the scaling of of predictive maintenance

47
00:03:04.789 --> 00:03:07.470
<v Niall Sullivan>projects, but, you know, talking, you
mentioned some big names there as well, but

48
00:03:07.470 --> 00:03:10.149
<v Niall Sullivan>what are some of the sort of the key
challenges that they're sort of facing at the

49
00:03:10.149 --> 00:03:13.300
<v Niall Sullivan>moment when you're having these
conversations, what are they coming to you to for

50
00:03:13.300 --> 00:03:14.369
<v Niall Sullivan>advice about?

51
00:03:15.130 --> 00:03:17.889
<v Nick Leeder>So I, I, I mean that's probably.

52
00:03:18.679 --> 00:03:23.889
<v Nick Leeder>The beauty of my job, it is very, very
varied, so, um, you know, ultimately, most

53
00:03:23.889 --> 00:03:28.529
<v Nick Leeder>people need to get stuff out the door on
time, at cost, at quality and do that

54
00:03:28.529 --> 00:03:32.539
<v Nick Leeder>safely as well, that, that, that last bit
often gets missed in that whole

55
00:03:32.539 --> 00:03:32.550
<v Nick Leeder>conversation.

56
00:03:33.410 --> 00:03:37.690
<v Nick Leeder>Um, so, you know, some of my topics are
generally around, you know, businesses

57
00:03:37.690 --> 00:03:40.690
<v Nick Leeder>sitting back and saying, look, we've got a
really aggressive growth plan over the

58
00:03:40.690 --> 00:03:42.500
<v Nick Leeder>next 2 to 5 years.

59
00:03:43.000 --> 00:03:43.800
<v Nick Leeder>How do we do that?

60
00:03:43.880 --> 00:03:45.289
<v Nick Leeder>Do we need to build a new factory?

61
00:03:45.360 --> 00:03:47.100
<v Nick Leeder>Can we improve, uh, performance?

62
00:03:47.360 --> 00:03:49.149
<v Nick Leeder>How does digital play in that?

63
00:03:49.440 --> 00:03:54.020
<v Nick Leeder>And digital doesn't have to be clever, you
know, I, I've got a current, um, uh,

64
00:03:54.149 --> 00:03:56.699
<v Nick Leeder>newsletter series called The Manufacturing
Mouse Trap.

65
00:03:57.000 --> 00:04:02.490
<v Nick Leeder>You know, there's, there's over 4400
patents for mouse traps in the US.

66
00:04:02.559 --> 00:04:03.699
<v Nick Leeder>I don't I mean if you don't know that.

67
00:04:04.360 --> 00:04:07.039
<v Nick Leeder>Only one works really well.

68
00:04:07.160 --> 00:04:10.919
<v Nick Leeder>I've seen some crazy ones with guns trying
to, you know, a mouse eating the cheese

69
00:04:10.919 --> 00:04:12.000
<v Nick Leeder>and a gun shooting them.

70
00:04:12.559 --> 00:04:18.730
<v Nick Leeder>But um in reality, it's a finding about
how digital gives them simple solutions to

71
00:04:18.730 --> 00:04:20.429
<v Nick Leeder>their operational problems today.

72
00:04:20.769 --> 00:04:25.529
<v Nick Leeder>Now that could be a new ERP or an MRP
system, and some of my customers have much

73
00:04:25.529 --> 00:04:29.890
<v Nick Leeder>more broader business challenges which
they help them take them on the next journey.

74
00:04:29.989 --> 00:04:34.850
<v Nick Leeder>It could be an implementation of a mess
system on a production shop floor, or it

75
00:04:34.850 --> 00:04:38.489
<v Nick Leeder>could be, you know, bringing it back to
the context of today's conversation.

76
00:04:39.140 --> 00:04:44.549
<v Nick Leeder>About how do you stop machines breaking on
the shop floor, you know, and that has

77
00:04:44.690 --> 00:04:49.929
<v Nick Leeder>that downtime and that frustration that
appears in the maintenance teams because

78
00:04:49.929 --> 00:04:54.690
<v Nick Leeder>they can't keep the kit running to the you
know, the operations director or the

79
00:04:54.690 --> 00:04:57.690
<v Nick Leeder>operations manager that's not getting the
product out the door when they need to

80
00:04:57.690 --> 00:04:59.570
<v Nick Leeder>because of lack of availability of
equipment.

81
00:05:00.010 --> 00:05:03.049
<v Nick Leeder>So it could be something about, well, how
do you implement a a condition-based

82
00:05:03.049 --> 00:05:07.250
<v Nick Leeder>monitoring or a predictive maintenance
solution that helps you get that visibility

83
00:05:07.250 --> 00:05:07.690
<v Nick Leeder>earlier.

84
00:05:08.049 --> 00:05:13.649
<v Nick Leeder>So it is, you know, absolutely a broad
spectrum of problems that manufacturers face

85
00:05:13.649 --> 00:05:14.649
<v Nick Leeder>on a daily basis.

86
00:05:15.440 --> 00:05:19.160
<v Nick Leeder>And sometimes just helping them think, see
the simple things away from all the noise

87
00:05:19.160 --> 00:05:23.820
<v Nick Leeder>we see in the press and the literature on
a daily basis of how we can actually get

88
00:05:24.200 --> 00:05:25.040
<v Nick Leeder>to value quickly.

89
00:05:26.769 --> 00:05:32.209
<v Niall Sullivan>Exactly, and, and today, today we're
talking about scale, um, and I I guess to

90
00:05:32.209 --> 00:05:36.529
<v Niall Sullivan>really start that conversation, and we, we
chatted just before, you know, we pressed

91
00:05:36.529 --> 00:05:40.850
<v Niall Sullivan>record a little bit about this, but, you
know, in terms of ambition and speaking

92
00:05:40.850 --> 00:05:42.769
<v Niall Sullivan>about predictive maintenance in
particular, is there.

93
00:05:43.290 --> 00:05:46.359
<v Niall Sullivan>You know, do you see there's an ambition
to sort of scale and make this sort of an

94
00:05:46.359 --> 00:05:50.579
<v Niall Sullivan>enterprise sort of deployment, or is it
sort of more reluctance in the market, you

95
00:05:50.579 --> 00:05:53.480
<v Niall Sullivan>know, more, you know, they're still a bit
unsure about the benefits predicting

96
00:05:53.480 --> 00:05:55.049
<v Niall Sullivan>maintenance and so want to start a bit
smaller.

97
00:05:55.089 --> 00:05:57.750
<v Niall Sullivan>What's your sort of feeling based on your
sort of experience?

98
00:05:58.250 --> 00:06:01.970
<v Nick Leeder>Uh, I, I mean, look, we, we all live in
the world of budgets for a start, so

99
00:06:01.970 --> 00:06:04.109
<v Nick Leeder>aspiration and budgets are two different
things.

100
00:06:04.570 --> 00:06:10.350
<v Nick Leeder>So I, I think to start with, you know,
everybody loves to have the idea of scale.

101
00:06:10.709 --> 00:06:14.869
<v Nick Leeder>But it's about who we're dealing with and
who we're talking to often has a very big

102
00:06:14.869 --> 00:06:16.170
<v Nick Leeder>bearing in that conversation.

103
00:06:16.920 --> 00:06:20.079
<v Nick Leeder>So if you're speaking with the maintenance
technicians and teams that are actually

104
00:06:20.079 --> 00:06:21.779
<v Nick Leeder>doing the job, the boots on the ground.

105
00:06:22.500 --> 00:06:26.109
<v Nick Leeder>Their world is really related to their
plant.

106
00:06:26.769 --> 00:06:32.649
<v Nick Leeder>And the context of scale for them is about
scaling the assets they are measuring and

107
00:06:32.649 --> 00:06:34.839
<v Nick Leeder>monitoring within that plant.

108
00:06:35.059 --> 00:06:36.649
<v Nick Leeder>So I'm trying to define what scale means.

109
00:06:37.329 --> 00:06:40.850
<v Nick Leeder>But you, for example, if I'm speaking to a
chief operating officer that's

110
00:06:40.850 --> 00:06:47.450
<v Nick Leeder>responsible for 5 plants or 20 plants,
scale to them means actually

111
00:06:47.450 --> 00:06:52.970
<v Nick Leeder>deploying the same solution across
multiple plants and increasing their visibility

112
00:06:52.970 --> 00:06:55.559
<v Nick Leeder>of the health and performance of those
plants.

113
00:06:56.010 --> 00:06:59.070
<v Nick Leeder>So scale to different people means
different things.

114
00:06:59.980 --> 00:07:06.079
<v Nick Leeder>But there are, I guess, a number of really
important things that are consistent,

115
00:07:06.500 --> 00:07:11.420
<v Nick Leeder>irrespective of whether you're talking
within your own plant in your facility or

116
00:07:11.420 --> 00:07:14.799
<v Nick Leeder>within um multiple plants and your
operations of the company.

117
00:07:15.299 --> 00:07:18.920
<v Nick Leeder>You know, the first one is, it's got to
make financial sense.

118
00:07:19.779 --> 00:07:24.410
<v Nick Leeder>You know, deploying stuff, I, I, I see,
you know, I get involved in questions around

119
00:07:24.410 --> 00:07:27.000
<v Nick Leeder>condition-based monitoring and predictive
maintenance quite a lot for companies.

120
00:07:28.059 --> 00:07:32.399
<v Nick Leeder>And the first tendency is to try and
measure everything.

121
00:07:33.369 --> 00:07:38.690
<v Nick Leeder>And actually starting with, well look,
what assets are actually the most critical

122
00:07:38.690 --> 00:07:42.329
<v Nick Leeder>assets that when they go down, your line
goes down, you can't produce.

123
00:07:43.429 --> 00:07:48.910
<v Nick Leeder>Or when they go down, you know, it has an
impact, but actually it's a very expensive

124
00:07:48.910 --> 00:07:52.709
<v Nick Leeder>piece of, you know, asset or equipment and
actually a long lead time item to get a

125
00:07:52.709 --> 00:07:55.269
<v Nick Leeder>replacement and you don't want to hold it
in stock because that drives your stock

126
00:07:55.269 --> 00:07:57.230
<v Nick Leeder>levels up and cost and in working Capital.

127
00:07:58.209 --> 00:08:01.250
<v Nick Leeder>So making sure that there's actually a
really clear benefit case of.

128
00:08:02.140 --> 00:08:06.190
<v Nick Leeder>Which assets do I really need to measure
that make the biggest difference?

129
00:08:07.040 --> 00:08:08.859
<v Nick Leeder>And then start saying, well, look.

130
00:08:09.649 --> 00:08:13.970
<v Nick Leeder>If uh if this goes down, the cost of
production and you know, and we can we all know

131
00:08:13.970 --> 00:08:18.570
<v Nick Leeder>the business case behind that, but one of
the things I spend a lot of time coaching

132
00:08:18.570 --> 00:08:22.720
<v Nick Leeder>both leaders and people who are trying to
get these projects off the ground and to

133
00:08:22.720 --> 00:08:23.250
<v Nick Leeder>scale.

134
00:08:24.589 --> 00:08:27.910
<v Nick Leeder>Is, you know, the mathematics of these
things you can demonstrate.

135
00:08:27.989 --> 00:08:28.709
<v Nick Leeder>I recently.

136
00:08:29.500 --> 00:08:33.340
<v Nick Leeder>Uh, read a paper and actually been
engaging with the author, uh, from Standard and

137
00:08:33.340 --> 00:08:40.280
<v Nick Leeder>Poorer, uh, S&amp;P on, uh, the financial
benefits of, um, uh, predictive

138
00:08:40.280 --> 00:08:43.320
<v Nick Leeder>maintenance, and it was built on a
hypothetical example.

139
00:08:43.859 --> 00:08:48.179
<v Nick Leeder>And their hypothetical example was 50% of
the machines in the, the factory need

140
00:08:48.179 --> 00:08:48.700
<v Nick Leeder>monitoring.

141
00:08:49.510 --> 00:08:52.960
<v Nick Leeder>But then the example was uh an OEM
manufacturer of pumps.

142
00:08:54.159 --> 00:09:00.719
<v Nick Leeder>Now I'm going, hold on, what, what
equipment is critical to you, you know, uh, you

143
00:09:00.719 --> 00:09:03.650
<v Nick Leeder>know, cos typically a lot of predictive
maintenance is based on rotating assets and

144
00:09:03.650 --> 00:09:06.809
<v Nick Leeder>equipment, yeah, your, your compressors,
your motors, your gearboxes.

145
00:09:07.640 --> 00:09:11.539
<v Nick Leeder>Um, you can do oil, temperature, humidity,
all these things come together, but

146
00:09:11.840 --> 00:09:14.880
<v Nick Leeder>really, do 50% of your machines need to be
measured?

147
00:09:15.159 --> 00:09:19.520
<v Nick Leeder>You know, and you know, the ROI ended up
being about 5 microseconds, you know, you

148
00:09:19.520 --> 00:09:20.140
<v Nick Leeder>turn it on.

149
00:09:20.479 --> 00:09:24.960
<v Nick Leeder>So let's be honest about it, let's be real
about it and actually bring the real case

150
00:09:24.960 --> 00:09:26.940
<v Nick Leeder>studies to the discussion.

151
00:09:27.080 --> 00:09:30.479
<v Nick Leeder>So not a theoretical, mathematical case,
but.

152
00:09:30.929 --> 00:09:36.650
<v Nick Leeder>You know what, last week we had compressor
number 4 on that line go down and we

153
00:09:36.650 --> 00:09:38.809
<v Nick Leeder>couldn't produce for uh.

154
00:09:39.530 --> 00:09:43.650
<v Nick Leeder>You know, 6 hours, so we lost 6 out of an
8 hour shift because of that.

155
00:09:45.169 --> 00:09:47.390
<v Nick Leeder>That costs you money, that's real.

156
00:09:48.260 --> 00:09:49.979
<v Nick Leeder>And the reason why it went down was X, Y,
and Z.

157
00:09:50.140 --> 00:09:53.700
<v Nick Leeder>Now if we had condition-based monitoring,
we would have known about this 2 weeks, 2

158
00:09:53.700 --> 00:09:54.400
<v Nick Leeder>weeks before.

159
00:09:55.059 --> 00:09:59.690
<v Nick Leeder>And we could have actually planned an
intervention in a planned downtime window or

160
00:09:59.690 --> 00:10:02.599
<v Nick Leeder>over the weekend that would have avoided
that.

161
00:10:03.049 --> 00:10:05.799
<v Nick Leeder>And you know what, that compressor, that's
an example last week.

162
00:10:05.979 --> 00:10:11.880
<v Nick Leeder>In the last year, we've had 14 of those
events on those same bits of equipment.

163
00:10:12.140 --> 00:10:14.179
<v Nick Leeder>Now I'm making these numbers off the top
of my head.

164
00:10:14.809 --> 00:10:18.289
<v Nick Leeder>But what you've done is taken an Excel
spreadsheet that gives you some very

165
00:10:18.289 --> 00:10:23.440
<v Nick Leeder>impressive numbers into something that is
real, that is pertinent to the people that

166
00:10:23.440 --> 00:10:28.570
<v Nick Leeder>want to do it, so that ROI becomes really
clear, not just in metrics and, you know,

167
00:10:28.609 --> 00:10:32.270
<v Nick Leeder>for the finance guys, but actually
examples of where it goes wrong.

168
00:10:32.570 --> 00:10:37.049
<v Nick Leeder>So that to me would be one, a great, a
great example of getting it over the line,

169
00:10:37.609 --> 00:10:37.929
<v Nick Leeder>um.

170
00:10:38.719 --> 00:10:42.010
<v Nick Leeder>I mean, there are a couple of other areas,
you know, we also live in the world of

171
00:10:42.010 --> 00:10:42.909
<v Nick Leeder>legacy equipment.

172
00:10:44.159 --> 00:10:48.750
<v Nick Leeder>Um, and, uh, please don't shoot me here,
but a lot of salespeople that go in around

173
00:10:48.750 --> 00:10:52.840
<v Nick Leeder>predictive maintenance kind of come into
this kind of view that, you know, you're

174
00:10:52.840 --> 00:10:56.880
<v Nick Leeder>working on a greenfield site and
everything's latest and the, the most shiniest

175
00:10:56.880 --> 00:10:58.830
<v Nick Leeder>equipment, you just plug things in and off
you go.

176
00:10:59.200 --> 00:11:04.520
<v Nick Leeder>That isn't the world that most
manufacturers live in, you know, and 85%, a study by

177
00:11:04.520 --> 00:11:10.909
<v Nick Leeder>IDC last year said that 85% of
manufacturers find that data silos and integration

178
00:11:10.909 --> 00:11:12.099
<v Nick Leeder>with legacy equipment.

179
00:11:12.840 --> 00:11:16.979
<v Nick Leeder>Are the major barriers to take
technologies like predictive maintenance forward.

180
00:11:18.070 --> 00:11:22.630
<v Nick Leeder>So, um, you know, understanding that this
stuff actually has to be retrofitted,

181
00:11:22.950 --> 00:11:28.070
<v Nick Leeder>finding companies that can do that with
you, both in terms of the technology, but

182
00:11:28.070 --> 00:11:32.549
<v Nick Leeder>understanding how to um sensorize the
equipment in the right places in the right

183
00:11:32.549 --> 00:11:35.070
<v Nick Leeder>ways have really big impacts.

184
00:11:36.229 --> 00:11:40.729
<v Nick Leeder>Um, Finally, I think, I think, well,
there's two other points actually, I'm probably

185
00:11:40.729 --> 00:11:43.960
<v Nick Leeder>taking a long time with this scaling
question, but these are the things where are,

186
00:11:44.210 --> 00:11:48.890
<v Nick Leeder>are really things that ignite the scale
question is, is also understanding the

187
00:11:48.890 --> 00:11:50.469
<v Nick Leeder>skills, so.

188
00:11:51.450 --> 00:11:55.380
<v Nick Leeder>If you speak to a lot of kind of uh we're
going into the world of buzzwords for a

189
00:11:55.380 --> 00:11:58.440
<v Nick Leeder>certain at the moment, you know,
predictive maintenance, and a lot of the focus of

190
00:11:58.440 --> 00:12:05.049
<v Nick Leeder>those conversations I hear are around kind
of AI skills, yeah, we need data

191
00:12:05.049 --> 00:12:06.750
<v Nick Leeder>scientists to do this stuff.

192
00:12:07.659 --> 00:12:11.510
<v Nick Leeder>Um, I disagree with that because if the
tools are doing the job properly.

193
00:12:12.219 --> 00:12:17.500
<v Nick Leeder>You don't need to be an AI expert, but
what you need is the skills to get the data,

194
00:12:17.619 --> 00:12:21.919
<v Nick Leeder>so the spectra analysis that you get off,
um, say, predictive maintenance.

195
00:12:22.539 --> 00:12:23.969
<v Nick Leeder>And how do you interpret that?

196
00:12:24.099 --> 00:12:28.280
<v Nick Leeder>How do you take that and say, you know,
you're classical CAP 2, CAT 3 vibration

197
00:12:28.280 --> 00:12:28.989
<v Nick Leeder>analysts.

198
00:12:29.500 --> 00:12:32.979
<v Nick Leeder>Being able to take that and go, you know
what, you've got a flat spot on one of the

199
00:12:32.979 --> 00:12:36.729
<v Nick Leeder>rolling elements or you've got an issue
with the lubrication regime or the shaft's

200
00:12:36.729 --> 00:12:37.940
<v Nick Leeder>gone out of alignment.

201
00:12:38.460 --> 00:12:41.940
<v Nick Leeder>So it's about the skills I think that
really make a difference are the people who

202
00:12:41.940 --> 00:12:46.820
<v Nick Leeder>can interpret the data and put them into
meaningful um outcomes and that's actually

203
00:12:46.820 --> 00:12:47.619
<v Nick Leeder>a rarity.

204
00:12:48.020 --> 00:12:52.380
<v Nick Leeder>So you know, the other reason is you don't
have people to really use the systems to

205
00:12:52.380 --> 00:12:56.929
<v Nick Leeder>the greatest advantage and that we'll see
if that has a knock-on effect on terms of

206
00:12:56.929 --> 00:12:57.919
<v Nick Leeder>the ROI question.

207
00:12:58.960 --> 00:13:03.159
<v Nick Leeder>Um, And if we're all honest as well, the
final one is just culture.

208
00:13:03.359 --> 00:13:09.760
<v Nick Leeder>Um, we have in the world of maintenance,
it has been a world of brake fix or planned

209
00:13:09.760 --> 00:13:10.280
<v Nick Leeder>maintenance.

210
00:13:10.400 --> 00:13:16.840
<v Nick Leeder>The vast majority of manufacturers are
still kind of fundamentally working in that

211
00:13:16.840 --> 00:13:17.340
<v Nick Leeder>world.

212
00:13:17.919 --> 00:13:21.840
<v Nick Leeder>And you know, for some businesses and some
sizes and complexity of processes, that

213
00:13:21.840 --> 00:13:22.739
<v Nick Leeder>actually is OK.

214
00:13:24.349 --> 00:13:28.469
<v Nick Leeder>But actually if you want to go predictive
maintenance around critical assets within

215
00:13:28.469 --> 00:13:32.830
<v Nick Leeder>your production facility and across your
production facilities, which we obviously

216
00:13:32.830 --> 00:13:33.570
<v Nick Leeder>talk about scale.

217
00:13:34.909 --> 00:13:40.260
<v Nick Leeder>Then you actually really need to start
changing the way of working, start saying,

218
00:13:40.590 --> 00:13:43.140
<v Nick Leeder>you know what, we're not gonna wait until
something breaks.

219
00:13:43.349 --> 00:13:48.580
<v Nick Leeder>We're gonna proactively get in there and
deal with it and the best window and the

220
00:13:48.580 --> 00:13:53.789
<v Nick Leeder>earliest window we have, uh, and that, you
know, from a, from a business point of

221
00:13:53.789 --> 00:13:58.510
<v Nick Leeder>view, improves obviously your availability
of assets, has a knock-on effect on OEE

222
00:13:58.510 --> 00:14:01.289
<v Nick Leeder>and and you know, and the product you can
get out the door.

223
00:14:02.070 --> 00:14:06.080
<v Nick Leeder>Um, but actually it has another really
important knock-on effect of that change of,

224
00:14:06.190 --> 00:14:09.299
<v Nick Leeder>uh, you know, that get people seeing the
benefit of getting in earlier.

225
00:14:09.909 --> 00:14:14.869
<v Nick Leeder>It also has, you know, maintenance teams
feel better because actually fewer things

226
00:14:14.869 --> 00:14:18.070
<v Nick Leeder>break because you're getting ahead of the
game, not reacting to the situation.

227
00:14:18.750 --> 00:14:24.190
<v Nick Leeder>Um, and all, you know, the stress levels
change and you know, it's a quite, it's a

228
00:14:24.190 --> 00:14:28.549
<v Nick Leeder>really nice, and I've seen this several
times when predictive maintenance works

229
00:14:28.549 --> 00:14:29.349
<v Nick Leeder>really well.

230
00:14:29.950 --> 00:14:34.349
<v Nick Leeder>The whole philosophy of the maintenance
team changes from the guys that are running

231
00:14:34.349 --> 00:14:38.179
<v Nick Leeder>around like headless chickens trying to
keep things up and running to the teams that

232
00:14:38.179 --> 00:14:42.909
<v Nick Leeder>are actually keeping and building and
improving, you know, and today stupid, you

233
00:14:42.909 --> 00:14:46.330
<v Nick Leeder>know, it's not stupid, but you know, there
is energy costs are going up again.

234
00:14:47.000 --> 00:14:50.820
<v Nick Leeder>You know, well maintained equipment uses
less energy.

235
00:14:51.359 --> 00:14:56.309
<v Nick Leeder>There's a financial benefit in the
business and you're increasing the life of those

236
00:14:56.309 --> 00:14:59.770
<v Nick Leeder>assets because you're maintaining them
well rather than waiting till they break.

237
00:15:00.289 --> 00:15:04.739
<v Nick Leeder>So that, you know, your Capital costs go
down and actually for many cases, and this

238
00:15:04.739 --> 00:15:08.510
<v Nick Leeder>is a real kind of hint in terms of the
business case, there's a massive impact in

239
00:15:08.510 --> 00:15:10.460
<v Nick Leeder>sustainability agenda there as well.

240
00:15:10.900 --> 00:15:10.909
<v Nick Leeder>Mhm.

241
00:15:12.890 --> 00:15:16.150
<v Niall Sullivan>Yeah, and it, and it's interesting you
talk about the broader use cases cos I think.

242
00:15:16.880 --> 00:15:20.969
<v Niall Sullivan>As a, as a market it's moved much more
beyond, you know, let's look at reducing

243
00:15:20.969 --> 00:15:23.969
<v Niall Sullivan>unplanned downtime, and that used to be
the only metric, and maybe it's still a key

244
00:15:23.969 --> 00:15:27.929
<v Niall Sullivan>metric, but even talking to colleagues on
this podcast, even things like health and

245
00:15:27.929 --> 00:15:31.809
<v Niall Sullivan>safety, you know, you know, and obviously
you can't put a price on that, clearly,

246
00:15:31.890 --> 00:15:35.570
<v Niall Sullivan>but even that's been talked about, you
know, with customers as like something

247
00:15:35.570 --> 00:15:38.409
<v Niall Sullivan>actually we, you know, it could, cos it
can help with that if you're proactive about

248
00:15:38.409 --> 00:15:39.890
<v Niall Sullivan>fixing things, it, you know, it's.

249
00:15:40.570 --> 00:15:44.929
<v Niall Sullivan>You can sort of save any sort of risky,
you know, repairs that may need to, may need

250
00:15:44.929 --> 00:15:45.390
<v Niall Sullivan>to happen.

251
00:15:46.150 --> 00:15:50.469
<v Nick Leeder>Well, I mean operating in a safe, in a
safe operating environment is obviously

252
00:15:50.469 --> 00:15:56.770
<v Nick Leeder>number one, you know, quality comes two
when it when compared to safety, um, and you

253
00:15:56.770 --> 00:16:00.330
<v Nick Leeder>know, so we can't argue that, but I think
one of the things that predictive

254
00:16:00.330 --> 00:16:05.890
<v Nick Leeder>maintenance does is it takes the pressure
off those moments of failure, when those

255
00:16:05.890 --> 00:16:06.770
<v Nick Leeder>moments of failure.

256
00:16:07.440 --> 00:16:11.239
<v Nick Leeder>People are rushing and often when people
are put under pressurized situations.

257
00:16:11.849 --> 00:16:16.409
<v Nick Leeder>It's, it's unfortunate mistakes get made
in those, and so it does change that

258
00:16:16.409 --> 00:16:17.989
<v Nick Leeder>dynamic quite significantly.

259
00:16:19.799 --> 00:16:22.359
<v Niall Sullivan>No, absolutely, and that, that makes a lot
of sense.

260
00:16:22.400 --> 00:16:23.940
<v Niall Sullivan>Well, I never really thought about it that
way.

261
00:16:24.479 --> 00:16:28.119
<v Niall Sullivan>Um, but some of the, what you were saying
before, and I know you apologize for, you

262
00:16:28.119 --> 00:16:32.000
<v Niall Sullivan>know, talking a lot, but A, we're on a
podcast, and B, the less I talk and the more

263
00:16:32.000 --> 00:16:36.679
<v Niall Sullivan>you talk, I think it's better for
everyone, but there was so much in there, I mean.

264
00:16:37.109 --> 00:16:40.520
<v Niall Sullivan>The, uh, the thing about culture, you
know, I wanna just start there because that's

265
00:16:40.520 --> 00:16:45.020
<v Niall Sullivan>something that often, we often talk about,
um, Vince Siemens, as well as such a key,

266
00:16:45.400 --> 00:16:49.590
<v Niall Sullivan>you know, key part of scalability, but you
also mentioned sort of a technical aspect

267
00:16:49.590 --> 00:16:50.080
<v Niall Sullivan>as well.

268
00:16:50.299 --> 00:16:53.599
<v Niall Sullivan>So, I think Nick, from your point of view,
how do you sort of bring those two very

269
00:16:53.599 --> 00:16:57.280
<v Niall Sullivan>opposing sides together and maybe you
could, we could even talk about some of the

270
00:16:57.280 --> 00:16:58.359
<v Niall Sullivan>stakeholders involved.

271
00:16:58.419 --> 00:17:03.260
<v Niall Sullivan>Cos there's very contrasting stakeholders
involved in, in a predictive maintenance

272
00:17:03.260 --> 00:17:06.599
<v Niall Sullivan>project, and how do, how does that all
stay aligned with different priorities?

273
00:17:06.900 --> 00:17:08.229
<v Niall Sullivan>It's a big question, I know.

274
00:17:08.579 --> 00:17:09.060
<v Nick Leeder>I'd love to.

275
00:17:09.180 --> 00:17:11.510
<v Nick Leeder>Yeah, I'm trying to, I'm trying to
mentally unpack that right now.

276
00:17:11.619 --> 00:17:13.380
<v Nick Leeder>Um, we could pack, we can

277
00:17:13.380 --> 00:17:14.930
<v Niall Sullivan>break it down a bit, we can break it down.

278
00:17:15.239 --> 00:17:15.520
<v Niall Sullivan>Let's,

279
00:17:15.579 --> 00:17:19.180
<v Nick Leeder>um, well, let's, let's start at the top,
shall we, because it's always easier to

280
00:17:19.180 --> 00:17:20.780
<v Nick Leeder>start at the top, um.

281
00:17:21.928 --> 00:17:27.548
<v Nick Leeder>I think a lot of executives view
predictive maintenance as a cost in the business.

282
00:17:28.270 --> 00:17:33.260
<v Nick Leeder>Uh, Rather than an investment and a cost
saving opportunity, um.

283
00:17:34.069 --> 00:17:40.709
<v Nick Leeder>So I, the, the first thing of cultural
change at the top is, is the ability to

284
00:17:40.709 --> 00:17:46.489
<v Nick Leeder>effectively connect how predictive
maintenance affects their KPIs in their world.

285
00:17:46.910 --> 00:17:48.550
<v Nick Leeder>And they're different to the maintenance
guys.

286
00:17:50.189 --> 00:17:54.660
<v Nick Leeder>So having that, you know, it's kind of
linked to the ROI question, but ROI's

287
00:17:54.660 --> 00:17:59.020
<v Nick Leeder>financially measured, but at the end of
the day is like we talked about safety a

288
00:17:59.020 --> 00:17:59.650
<v Nick Leeder>minute ago.

289
00:18:00.150 --> 00:18:05.089
<v Nick Leeder>So can you say to your operations
director, you know what, if we do this, it will

290
00:18:05.089 --> 00:18:06.689
<v Nick Leeder>improve the safety on the shop floor.

291
00:18:07.489 --> 00:18:12.079
<v Nick Leeder>That's something he and a clear why, again
back to that simple example that

292
00:18:12.079 --> 00:18:15.010
<v Nick Leeder>illustrates the point rather than the
metrics.

293
00:18:16.089 --> 00:18:21.329
<v Nick Leeder>Those things will stick in their head, and
that will start driving that leadership

294
00:18:21.329 --> 00:18:23.410
<v Nick Leeder>buy-in to do something different.

295
00:18:25.119 --> 00:18:30.880
<v Nick Leeder>So, let's, we, we talked about the top,
and then let's get down to the, the kind of

296
00:18:30.880 --> 00:18:34.000
<v Nick Leeder>the boots on the ground and actually the
people who do the job, so the maintenance

297
00:18:34.000 --> 00:18:35.239
<v Nick Leeder>engineers and the technicians.

298
00:18:35.989 --> 00:18:42.180
<v Nick Leeder>How does that change their world as well,
you know, and a part of that is, you know,

299
00:18:42.270 --> 00:18:47.130
<v Nick Leeder>I, I've covered some of that already, is
about changing their day.

300
00:18:47.469 --> 00:18:54.310
<v Nick Leeder>The day doesn't become a constant
firefighting, it, it, it's, it's about actually

301
00:18:54.310 --> 00:18:59.550
<v Nick Leeder>getting ahead of the game, keeping things
running smoothly, that pressure levels

302
00:18:59.550 --> 00:19:01.150
<v Nick Leeder>drop, um.

303
00:19:02.150 --> 00:19:07.130
<v Nick Leeder>You know, in reality there's a, there's
again PWC reporter did a report last year,

304
00:19:07.550 --> 00:19:10.949
<v Nick Leeder>um, and I'm reading off the screen because
quite often I can't memorize all these

305
00:19:10.949 --> 00:19:16.589
<v Nick Leeder>stats off the top of my head, but, uh,
about 25% of, only 25% of maintenance teams

306
00:19:16.589 --> 00:19:18.170
<v Nick Leeder>use data to make decisions.

307
00:19:19.209 --> 00:19:22.150
<v Nick Leeder>Wow, yeah, that's quite, that's really
quite low.

308
00:19:22.410 --> 00:19:28.369
<v Nick Leeder>Now that's a reflection on that kind of
planned or break fixed type approach,

309
00:19:28.530 --> 00:19:29.599
<v Nick Leeder>waiting until something breaks.

310
00:19:30.010 --> 00:19:34.930
<v Nick Leeder>Maybe the data is just nothing's running,
but um, when you look at that sort of,

311
00:19:35.050 --> 00:19:40.329
<v Nick Leeder>those sort of data points, it's that shift
from reactive to proactive.

312
00:19:41.219 --> 00:19:45.709
<v Nick Leeder>That has a profound effect from a cultural
buy-in, um, but it's, you know, it's not

313
00:19:45.709 --> 00:19:50.050
<v Nick Leeder>about the technology, it's about how it
changes the day for maintenance engineer,

314
00:19:51.150 --> 00:19:52.890
<v Nick Leeder>um, and also I think.

315
00:19:54.349 --> 00:19:57.449
<v Nick Leeder>I, I guess part of that is also about the
training you give them.

316
00:19:57.849 --> 00:20:02.829
<v Nick Leeder>um, I, I spend a lot of time talking about
workforce challenges in manufacturing uh

317
00:20:02.829 --> 00:20:06.989
<v Nick Leeder>as well, you know, that's one of my
passions and one of my passions is that I want

318
00:20:06.989 --> 00:20:11.989
<v Nick Leeder>to see this more from the people, um, the
frontline workers, the operators, and that

319
00:20:11.989 --> 00:20:15.910
<v Nick Leeder>perspective as opposed to the manufacturer
the management perspective of how skills

320
00:20:15.910 --> 00:20:16.430
<v Nick Leeder>are needed.

321
00:20:17.069 --> 00:20:22.079
<v Nick Leeder>Um, but actually, the training you give to
maintenance engineers and technicians

322
00:20:22.079 --> 00:20:25.329
<v Nick Leeder>that are then about how to use the tools.

323
00:20:26.329 --> 00:20:30.260
<v Nick Leeder>Helps them to actually understand, yeah,
OK, I get how that can be used.

324
00:20:30.650 --> 00:20:33.839
<v Nick Leeder>I don't have to do walk around listening,
you know, listening around, seeing what's

325
00:20:33.839 --> 00:20:37.930
<v Nick Leeder>rattling this week versus last week, they
know their assets, yeah, they know what's

326
00:20:37.930 --> 00:20:38.550
<v Nick Leeder>going on.

327
00:20:38.890 --> 00:20:43.170
<v Nick Leeder>But this is like a secret window, you
train them into this secret window of actually

328
00:20:43.170 --> 00:20:46.849
<v Nick Leeder>this is how it's performing, this is how
it's working, you can't hear this yet, but

329
00:20:46.849 --> 00:20:48.709
<v Nick Leeder>we're starting to see something change.

330
00:20:49.640 --> 00:20:56.069
<v Nick Leeder>And those skills are actually adding value
to them as an individual as well.

331
00:20:56.329 --> 00:20:57.349
<v Nick Leeder>You know, let's be honest.

332
00:20:57.810 --> 00:21:00.910
<v Nick Leeder>If they can use these tools, they're more
valuable in the marketplace.

333
00:21:01.329 --> 00:21:04.369
<v Nick Leeder>Um, so you're building, you're investing
in them.

334
00:21:05.719 --> 00:21:08.250
<v Nick Leeder>As well as investing in the technology,
um.

335
00:21:09.709 --> 00:21:11.349
<v Nick Leeder>And then there's the bum fight, isn't
there?

336
00:21:11.469 --> 00:21:14.709
<v Nick Leeder>Let's, let's be honest, there's always a
bum fight with these projects on cultural

337
00:21:14.709 --> 00:21:17.930
<v Nick Leeder>change between IT operations and
maintenance.

338
00:21:18.229 --> 00:21:18.589
<v Nick Leeder>Yeah.

339
00:21:19.069 --> 00:21:23.770
<v Nick Leeder>There's, and, um, there's always, well,
operations won't allow you to get on and try

340
00:21:23.770 --> 00:21:28.000
<v Nick Leeder>and implement this because they're
running, you know, 24 hour shifts 7 days a week,

341
00:21:28.109 --> 00:21:32.750
<v Nick Leeder>yeah, um, IT won't go there because
they'll go, well, that's not really our, you

342
00:21:32.750 --> 00:21:34.530
<v Nick Leeder>know, that's that, I want that to be our
project.

343
00:21:34.979 --> 00:21:38.569
<v Nick Leeder>And I want that connected in here, but
we've got all these huge barriers of security

344
00:21:38.569 --> 00:21:43.239
<v Nick Leeder>and technology to overcome, um, you know,
oh you can't connect that to our network

345
00:21:43.369 --> 00:21:47.300
<v Nick Leeder>conversation, um, to the maintenance teams
that just want something done to make

346
00:21:47.300 --> 00:21:48.199
<v Nick Leeder>their world better.

347
00:21:48.939 --> 00:21:54.939
<v Nick Leeder>So actually getting those people together
and say look, the objective is this, this

348
00:21:54.939 --> 00:21:55.579
<v Nick Leeder>is the goal.

349
00:21:56.520 --> 00:22:01.400
<v Nick Leeder>And we've gotta work together rather than
our traditional silos which we operate on.

350
00:22:02.489 --> 00:22:08.930
<v Nick Leeder>Um, it, it makes a massive difference in
terms of driving a success of a project to

351
00:22:08.930 --> 00:22:11.869
<v Nick Leeder>get these things over the line and start
seeing the benefits as well.

352
00:22:14.359 --> 00:22:19.689
<v Niall Sullivan>And And I guess, uh, I mean, quite, quite
obviously the key is to, you know, it's

353
00:22:19.689 --> 00:22:23.890
<v Niall Sullivan>collaboration, but any, and we, we know
ourselves that collaboration is key to the

354
00:22:23.890 --> 00:22:27.050
<v Niall Sullivan>success of these projects, but how do you
sort of foster collaboration between

355
00:22:27.050 --> 00:22:31.430
<v Niall Sullivan>those, you know, the different areas of a
business which have completely different

356
00:22:31.810 --> 00:22:34.130
<v Niall Sullivan>focuses, priorities, viewpoints on things?

357
00:22:34.209 --> 00:22:36.910
<v Niall Sullivan>How, how can you in reality bring, bring
people together?

358
00:22:37.930 --> 00:22:39.869
<v Nick Leeder>Well, I started off by talking about
leadership.

359
00:22:40.810 --> 00:22:44.920
<v Nick Leeder>I mean, the, the problem is that all
organizations have some degree of hierarchy,

360
00:22:44.989 --> 00:22:49.609
<v Nick Leeder>but ultimately the, the, the further up
the organization you go, the number of

361
00:22:49.609 --> 00:22:51.670
<v Nick Leeder>invested players becomes less and less.

362
00:22:52.589 --> 00:22:59.500
<v Nick Leeder>Um So actually having some level of
alignment at leadership, but

363
00:22:59.500 --> 00:23:01.060
<v Nick Leeder>buy in below them.

364
00:23:01.989 --> 00:23:06.229
<v Nick Leeder>You know, maybe you're a couple of levels
down in management, that's normally a

365
00:23:06.229 --> 00:23:12.670
<v Nick Leeder>really good place to start, so there is a
shared goal, a shared outcome that we need

366
00:23:12.670 --> 00:23:14.410
<v Nick Leeder>to get to as an organization.

367
00:23:14.869 --> 00:23:19.189
<v Nick Leeder>And if you agree and align on those shared
outcomes, then.

368
00:23:20.069 --> 00:23:24.709
<v Nick Leeder>That the, those barriers start diminishing
because we're all working towards a

369
00:23:24.709 --> 00:23:30.630
<v Nick Leeder>common goal, whereas IT want to just work
on security, you know, not introduce new

370
00:23:30.630 --> 00:23:34.530
<v Nick Leeder>systems into their business, you know,
those, those sort of things.

371
00:23:35.109 --> 00:23:41.699
<v Nick Leeder>But they also have a responsibility, not
to be a barrier, but also to enable the

372
00:23:41.699 --> 00:23:44.089
<v Nick Leeder>organization to operate efficiently as
well.

373
00:23:45.010 --> 00:23:47.369
<v Nick Leeder>So, you know, having those dialogues to
say look.

374
00:23:48.400 --> 00:23:51.579
<v Nick Leeder>This is the goal, this is the business
goal, here is the financial return.

375
00:23:53.040 --> 00:23:58.040
<v Nick Leeder>We need to work together to make that
happen, or do it in a way that those barriers

376
00:23:58.040 --> 00:23:58.910
<v Nick Leeder>disappear.

377
00:23:59.400 --> 00:24:05.520
<v Nick Leeder>I've seen a lot of uh predictive uh
maintenance solutions now that are not even

378
00:24:05.520 --> 00:24:07.719
<v Nick Leeder>touching the networks.

379
00:24:08.569 --> 00:24:12.000
<v Nick Leeder>So you're, you know, you're implementing
the sensors, the sensors are connected to

380
00:24:12.000 --> 00:24:16.439
<v Nick Leeder>gateways, those gateways are communicating
to a SAS platform, there is security

381
00:24:16.439 --> 00:24:17.280
<v Nick Leeder>across that chain.

382
00:24:18.189 --> 00:24:22.479
<v Nick Leeder>But they're not placing a risk, a
cybersecurity risk into the actual operations of

383
00:24:22.479 --> 00:24:23.020
<v Nick Leeder>the business.

384
00:24:23.979 --> 00:24:30.939
<v Nick Leeder>So there are ways of trying to skin this
cat, so to speak, that minimizes some of

385
00:24:30.939 --> 00:24:32.040
<v Nick Leeder>those barriers as well.

386
00:24:33.910 --> 00:24:38.270
<v Niall Sullivan>I get in terms of sort of other issues
that might cloud, I mean this is more about

387
00:24:38.270 --> 00:24:42.939
<v Niall Sullivan>the, the, the market in general, but is
there sort of misconceptions about what PDM

388
00:24:42.939 --> 00:24:47.020
<v Niall Sullivan>is, cos I guess even within an
organization, there might be different definitions

389
00:24:47.020 --> 00:24:49.839
<v Niall Sullivan>floating around, but in, and we know in
the market, there's some things that,

390
00:24:50.030 --> 00:24:52.750
<v Niall Sullivan>there's some products that say they,
they're predicting maintenance when they're

391
00:24:52.750 --> 00:24:54.790
<v Niall Sullivan>not, or they do AI when they don't.

392
00:24:55.050 --> 00:24:59.069
<v Niall Sullivan>Um, but it, and I guess this adds to this
internal confusion as well.

393
00:24:59.290 --> 00:25:00.619
<v Niall Sullivan>I'm, I'm gonna guess.

394
00:25:00.810 --> 00:25:00.930
<v Niall Sullivan>Well,

395
00:25:01.199 --> 00:25:05.410
<v Nick Leeder>I mean, you, you work for an organization
called Seedemans, and they have a PDM

396
00:25:05.410 --> 00:25:09.010
<v Nick Leeder>solution and a PDM solution, one being
product data management and one being

397
00:25:09.010 --> 00:25:09.760
<v Nick Leeder>predictive maintenance.

398
00:25:09.849 --> 00:25:13.810
<v Nick Leeder>So the, the world of acronyms is a, is a,
is a nightmare.

399
00:25:13.930 --> 00:25:18.689
<v Nick Leeder>Um, I, I spend a lot of time decoding
buzzwords to what do they really mean and

400
00:25:18.689 --> 00:25:20.290
<v Nick Leeder>acronyms to what do they really mean.

401
00:25:20.609 --> 00:25:22.410
<v Nick Leeder>And one of my favorite right now, by the
way, is agentic AI.

402
00:25:24.109 --> 00:25:26.229
<v Nick Leeder>Everybody's still like, that sounds cool,
what does that mean?

403
00:25:26.599 --> 00:25:33.319
<v Nick Leeder>Um, so I, I think the problem is there are
absolute themes and topics in

404
00:25:33.319 --> 00:25:35.420
<v Nick Leeder>the industry that get a lot of press and
noise.

405
00:25:36.239 --> 00:25:42.160
<v Nick Leeder>So AI, you mentioned it, yeah, is
absolutely one, you know, you can't go two days

406
00:25:42.160 --> 00:25:46.699
<v Nick Leeder>without a new report on the way that AI is
going to revolutionize industry and, and

407
00:25:47.400 --> 00:25:50.699
<v Nick Leeder>everything else around the world including
my coffee machine in my, in my kitchen,

408
00:25:51.359 --> 00:25:51.719
<v Nick Leeder>um.

409
00:25:53.260 --> 00:25:58.510
<v Nick Leeder>The reality is that very few solutions are
really truly AI centric.

410
00:25:59.239 --> 00:26:03.560
<v Nick Leeder>Um, one of the key things I think is about
data, first of all.

411
00:26:05.329 --> 00:26:10.089
<v Nick Leeder>In the world of predictive maintenance,
you kind of need to predict when something's

412
00:26:10.089 --> 00:26:10.890
<v Nick Leeder>going to fail.

413
00:26:11.819 --> 00:26:15.959
<v Nick Leeder>Now that requires knowing failure modes,
probabilities of failure modes.

414
00:26:16.569 --> 00:26:20.939
<v Nick Leeder>It requires understanding the condition of
the asset of where you are in that curve.

415
00:26:21.660 --> 00:26:27.020
<v Nick Leeder>And it requires having the right data in
the right context to apply that.

416
00:26:27.849 --> 00:26:31.829
<v Nick Leeder>And you know, we have to start with that
data quality.

417
00:26:31.930 --> 00:26:36.650
<v Nick Leeder>Have you got the, are you measuring the
right things at the right points and gaining

418
00:26:36.650 --> 00:26:40.599
<v Nick Leeder>that right data to make that analysis, to
predict something?

419
00:26:41.469 --> 00:26:47.709
<v Nick Leeder>Um, and you know, incorrect threshold
settings on sensors, you know, so your

420
00:26:47.709 --> 00:26:54.189
<v Nick Leeder>vibration, you know, your, um, RMS levels,
whatever, those things will have a

421
00:26:54.189 --> 00:26:59.270
<v Nick Leeder>profound effect on garbage in, garbage
out, you get, you know, and that actually is

422
00:26:59.270 --> 00:27:04.709
<v Nick Leeder>a killer, by the way, you do that wrong,
people's confidence level in the solutions

423
00:27:04.709 --> 00:27:05.550
<v Nick Leeder>you deploy.

424
00:27:06.109 --> 00:27:10.709
<v Nick Leeder>Kind of evaporate because it's just a
world of noise you're dealing with, it doesn't

425
00:27:10.709 --> 00:27:12.329
<v Nick Leeder>help the daily situation.

426
00:27:13.180 --> 00:27:18.780
<v Nick Leeder>So bringing that data um into something
that it becomes meaningful, setting

427
00:27:18.780 --> 00:27:24.130
<v Nick Leeder>thresholds for example that are really
showing the asset you're looking at and the

428
00:27:24.130 --> 00:27:30.010
<v Nick Leeder>operation it's performing and is that
really starting to go into a warning um alert

429
00:27:30.010 --> 00:27:31.119
<v Nick Leeder>or a warning status.

430
00:27:32.229 --> 00:27:36.329
<v Nick Leeder>Those, those things is where a lot of
predictive maintenance is today.

431
00:27:36.510 --> 00:27:40.989
<v Nick Leeder>There are a few solutions out there that
are now going into the prediction of that,

432
00:27:41.469 --> 00:27:46.310
<v Nick Leeder>but I think there's a, there's a risk
here, I think, well, actually maybe put it,

433
00:27:46.410 --> 00:27:50.130
<v Nick Leeder>let me put this in a different way, in a
more positive way I guess, is um.

434
00:27:51.010 --> 00:27:56.670
<v Nick Leeder>The prediction, I think stage one is
predicting what that failure mode is.

435
00:27:57.170 --> 00:28:00.680
<v Nick Leeder>So is it, as I mentioned at the beginning,
a a misalignment of a shaft, is it a

436
00:28:00.680 --> 00:28:03.270
<v Nick Leeder>mechanical failure somewhere, you know,
um.

437
00:28:04.420 --> 00:28:09.000
<v Nick Leeder>Is it, you know, you've got a problem with
the bearing, you know, um inner raceway

438
00:28:09.459 --> 00:28:10.500
<v Nick Leeder>issues or something else like that.

439
00:28:10.699 --> 00:28:16.160
<v Nick Leeder>Using the data, and there are quite, you
know, simple logical kind of fault

440
00:28:16.280 --> 00:28:21.180
<v Nick Leeder>connections where you've got multiple
failure states or multiple alert states would

441
00:28:21.180 --> 00:28:23.959
<v Nick Leeder>help you understand and predict what that
failure mode is.

442
00:28:26.099 --> 00:28:30.880
<v Nick Leeder>Then the next piece where it gets
cleverer, and I again this is where it gets harder

443
00:28:30.880 --> 00:28:34.979
<v Nick Leeder>because you get a lot more false positives
here, and what I mean by false positive

444
00:28:34.979 --> 00:28:35.260
<v Nick Leeder>is.

445
00:28:36.089 --> 00:28:39.489
<v Nick Leeder>Something isn't gonna fail, but you're
getting told it is gonna fail, and that's

446
00:28:39.489 --> 00:28:40.770
<v Nick Leeder>about training and time.

447
00:28:41.170 --> 00:28:46.000
<v Nick Leeder>So the next stage is about when, so you
know it's gonna fail, why it's gonna fail.

448
00:28:46.410 --> 00:28:48.369
<v Nick Leeder>The next question is when is it gonna
fail?

449
00:28:48.729 --> 00:28:54.689
<v Nick Leeder>And that's a lot harder because that, that
not only does you have to take the

450
00:28:54.689 --> 00:28:59.400
<v Nick Leeder>failure mode, you need to understand where
it is in that process of failure, and you

451
00:28:59.400 --> 00:29:02.209
<v Nick Leeder>need to predict events, well look we're
here.

452
00:29:02.800 --> 00:29:08.589
<v Nick Leeder>But it's got weeks left of run, week of
run time, and that's hugely um uh contingent

453
00:29:08.589 --> 00:29:12.050
<v Nick Leeder>on what are you gonna produce in the next
week, are you gonna run it 50% of the

454
00:29:12.050 --> 00:29:13.489
<v Nick Leeder>time, are you gonna run it 100% of the
time?

455
00:29:14.500 --> 00:29:19.099
<v Nick Leeder>So that kind of window, and actually if
we're honest, well that's all that's trying

456
00:29:19.099 --> 00:29:23.859
<v Nick Leeder>to do is uh understand how long you can
run it before it fails, so we're almost back

457
00:29:23.859 --> 00:29:27.439
<v Nick Leeder>into that brake fix reactive world there.

458
00:29:27.900 --> 00:29:33.180
<v Nick Leeder>So to me, all that cooler kind of cool
stuff that we talk about, it, it, it will get

459
00:29:33.180 --> 00:29:37.180
<v Nick Leeder>better over time and I'm absolutely
confident that this is the direction, but where

460
00:29:37.180 --> 00:29:39.619
<v Nick Leeder>we are right now, there is more false
positives.

461
00:29:40.319 --> 00:29:45.680
<v Nick Leeder>Um, and marketing, if I'm honest,
marketing noise in this space, than actually the

462
00:29:45.680 --> 00:29:46.670
<v Nick Leeder>practical application.

463
00:29:47.660 --> 00:29:53.260
<v Nick Leeder>And I think things like understanding the
failure mode and relying on the skills,

464
00:29:53.349 --> 00:29:57.469
<v Nick Leeder>the knowledge and the intelligence of the
maintenance teams that live and breathe

465
00:29:57.469 --> 00:30:01.349
<v Nick Leeder>those assets on a day to day basis is a
massive step forward.

466
00:30:02.130 --> 00:30:04.290
<v Nick Leeder>Anyway, cos if you can predict the failure
mode.

467
00:30:05.199 --> 00:30:10.920
<v Nick Leeder>You know, the people you have in your
business will probably know, OK, it's that

468
00:30:10.920 --> 00:30:13.560
<v Nick Leeder>machine and that's, and that's been
running like this, I reckon we've probably got

469
00:30:13.560 --> 00:30:18.910
<v Nick Leeder>another week, let's order that spare part
in now because I know the um the supplier

470
00:30:18.910 --> 00:30:22.540
<v Nick Leeder>of that motor will get us a new product,
you know, a new motor in in the next 3 days

471
00:30:22.540 --> 00:30:23.400
<v Nick Leeder>or something else like that.

472
00:30:25.540 --> 00:30:31.760
<v Niall Sullivan>That's, and I guess if we, if we apply
this to, to scaling as well, so in terms of.

473
00:30:32.859 --> 00:30:35.979
<v Niall Sullivan>And, and we're jumping ahead a little bit,
I guess, but in terms of the best

474
00:30:35.979 --> 00:30:39.479
<v Niall Sullivan>practices that drive success, I think
we've talked about a lot about, you know,

475
00:30:39.780 --> 00:30:43.569
<v Niall Sullivan>predictive maintenance, success and
cultural factors, technical factors.

476
00:30:43.619 --> 00:30:48.760
<v Niall Sullivan>But if we apply that to scaling, what,
what do organizations need to have in mind

477
00:30:49.099 --> 00:30:50.339
<v Niall Sullivan>when thinking about scaling?

478
00:30:51.520 --> 00:30:53.089
<v Nick Leeder>Um, so.

479
00:30:55.329 --> 00:31:01.290
<v Nick Leeder>I think the first, I think we need to
let's go back to my original point, scanned

480
00:31:01.290 --> 00:31:03.030
<v Nick Leeder>scaling in two dimensions.

481
00:31:04.449 --> 00:31:08.569
<v Nick Leeder>Dimensions within the plant, so the number
of assets you're monitoring versus the

482
00:31:08.569 --> 00:31:09.770
<v Nick Leeder>number of plants you're monitoring.

483
00:31:10.949 --> 00:31:13.469
<v Nick Leeder>And there'll be a break-even point on both
those axes.

484
00:31:14.189 --> 00:31:20.949
<v Nick Leeder>Um, and you know, when I see pilot, when I
see things or predictive maintenance, I

485
00:31:20.949 --> 00:31:23.089
<v Nick Leeder>use the word pilot, I shouldn't have done
so.

486
00:31:23.550 --> 00:31:29.569
<v Nick Leeder>When I see predictive maintenance projects
scale and be successful, is when they

487
00:31:29.569 --> 00:31:31.790
<v Nick Leeder>kind of start small.

488
00:31:33.010 --> 00:31:36.790
<v Nick Leeder>It's not, you know, you don't go for day
one, we, we're gonna measure everything.

489
00:31:37.569 --> 00:31:42.290
<v Nick Leeder>It's measuring those two or three critical
things that you've had either a lot of

490
00:31:42.290 --> 00:31:46.449
<v Nick Leeder>problems with that cause issues or are
known as the critical assets.

491
00:31:47.619 --> 00:31:49.089
<v Nick Leeder>Start with those.

492
00:31:49.949 --> 00:31:52.089
<v Nick Leeder>Uh, demonstrate the benefit.

493
00:31:53.050 --> 00:31:56.290
<v Nick Leeder>And then still don't have the aspiration
to measure everything, but then you can

494
00:31:56.290 --> 00:32:00.849
<v Nick Leeder>kind of progress on that access within
your plant or moving to the next, either the

495
00:32:00.849 --> 00:32:04.609
<v Nick Leeder>next line or perhaps the next set of
critical assets.

496
00:32:05.089 --> 00:32:09.410
<v Nick Leeder>And at some point you go, that's good, you
know, we're measuring really cheap motors

497
00:32:09.410 --> 00:32:13.349
<v Nick Leeder>on there that don't, you know, we don't
need to do that or they don't fail.

498
00:32:13.810 --> 00:32:16.050
<v Nick Leeder>So keep that and scale across that axis.

499
00:32:16.829 --> 00:32:22.829
<v Nick Leeder>That success story within that plant and
in those lines can then go, right, how do

500
00:32:22.829 --> 00:32:25.770
<v Nick Leeder>we replicate that across other plants and
facilities?

501
00:32:26.270 --> 00:32:29.949
<v Nick Leeder>And part of that is, are the product lines
the same, are the manufacturing processes

502
00:32:29.949 --> 00:32:31.589
<v Nick Leeder>the same, are the assets the same?

503
00:32:32.229 --> 00:32:35.750
<v Nick Leeder>Um, and then use that and say, well, look,
we're all using the same compressor,

504
00:32:35.949 --> 00:32:39.349
<v Nick Leeder>we're, we, we all have compressors in the
plants, we may use 3 different

505
00:32:39.349 --> 00:32:41.630
<v Nick Leeder>manufacturers of compressors in the plant.

506
00:32:41.989 --> 00:32:45.949
<v Nick Leeder>Um, but actually we can use this
technology and deploy these on all these because

507
00:32:45.949 --> 00:32:49.349
<v Nick Leeder>this, our technology is focused on
deploying our legacy equipment.

508
00:32:50.109 --> 00:32:56.030
<v Nick Leeder>And then you start getting that scale, and
then for the first time you start getting

509
00:32:56.030 --> 00:33:00.310
<v Nick Leeder>the overall health and performance of not
just your lines but your plants as well

510
00:33:00.310 --> 00:33:06.729
<v Nick Leeder>and then, you know, that ball starts, but
it all starts um with starting

511
00:33:07.030 --> 00:33:09.079
<v Nick Leeder>small, demonstrating it.

512
00:33:09.469 --> 00:33:12.719
<v Nick Leeder>And that, that is both from a financial
perspective.

513
00:33:13.400 --> 00:33:18.359
<v Nick Leeder>But also around that cultural change, cos
people don't believe this stuff works, you

514
00:33:18.359 --> 00:33:20.910
<v Nick Leeder>know, the amount of maintenance,
technicians and engineers going.

515
00:33:22.109 --> 00:33:25.790
<v Nick Leeder>Yeah, but it doesn't quite work out,
there's a great example, by the way, where I've

516
00:33:25.790 --> 00:33:26.369
<v Nick Leeder>got one.

517
00:33:26.910 --> 00:33:31.219
<v Nick Leeder>I had a company using condition-based
monitoring and it was quite new in its

518
00:33:31.219 --> 00:33:32.010
<v Nick Leeder>implementation.

519
00:33:32.750 --> 00:33:36.310
<v Nick Leeder>And um there was a a an air knife, so it's
basically a big fan.

520
00:33:37.040 --> 00:33:41.660
<v Nick Leeder>And the vibration of the spectra coming
off there was indicating a bearing failure,

521
00:33:42.119 --> 00:33:46.780
<v Nick Leeder>um, and actually what it was is it was
actually caused by dirt on the blades

522
00:33:47.079 --> 00:33:52.750
<v Nick Leeder>creating an imbalance, but the spectra
actually gave exactly the same replica, uh,

523
00:33:52.760 --> 00:33:53.290
<v Nick Leeder>replication.

524
00:33:53.359 --> 00:33:55.180
<v Nick Leeder>Now that was a really important learning.

525
00:33:55.719 --> 00:33:57.349
<v Nick Leeder>So important learning in twofold.

526
00:33:57.660 --> 00:34:03.479
<v Nick Leeder>One is everything you see on a screen
doesn't necessarily equal the real world in

527
00:34:03.479 --> 00:34:04.479
<v Nick Leeder>the production environment.

528
00:34:05.390 --> 00:34:11.070
<v Nick Leeder>But it actually was a great opportunity to
connect the uh skepticism.

529
00:34:11.800 --> 00:34:14.459
<v Nick Leeder>Of the maintenance teams and the reality
on the ground.

530
00:34:15.649 --> 00:34:21.090
<v Nick Leeder>Uh, with the data and then say, well,
look, even if it wasn't the bearing, it was in

531
00:34:21.090 --> 00:34:22.850
<v Nick Leeder>balance, you went and cleaned it.

532
00:34:24.209 --> 00:34:26.689
<v Nick Leeder>Cos that imbalance over time would create
a secondary issue.

533
00:34:27.169 --> 00:34:31.330
<v Nick Leeder>So actually, everybody everyone started
going, oh yeah, OK, so maybe it told me the

534
00:34:31.330 --> 00:34:36.040
<v Nick Leeder>wrong thing, but it told me something was
out of kilter, irrespective, and that

535
00:34:36.040 --> 00:34:36.739
<v Nick Leeder>helped me.

536
00:34:37.129 --> 00:34:40.290
<v Nick Leeder>And you go, you know, they could probably
go down the line, they'll hear something

537
00:34:40.290 --> 00:34:40.879
<v Nick Leeder>as well.

538
00:34:41.209 --> 00:34:44.409
<v Nick Leeder>Maybe they hear something and they go back
and then look at the the predictive

539
00:34:44.409 --> 00:34:48.770
<v Nick Leeder>maintenance system and actually saying,
well look, OK, it is trending, it hasn't hit

540
00:34:48.770 --> 00:34:49.729
<v Nick Leeder>the alert yet.

541
00:34:50.449 --> 00:34:54.659
<v Nick Leeder>But it is trending upwards, OK, so it's
corre gradual correlations of those, and the

542
00:34:54.659 --> 00:34:57.780
<v Nick Leeder>only way you can do that is to start small
and get some really good proof points.

543
00:34:58.209 --> 00:35:01.639
<v Nick Leeder>And I, I, I use this phrase a lot, Yodas.

544
00:35:02.219 --> 00:35:04.659
<v Nick Leeder>So, uh, we all love Star Wars.

545
00:35:04.719 --> 00:35:08.090
<v Nick Leeder>I mean, you know, behind me you've got
Muppets, so one day I will get a, a Yoda

546
00:35:08.090 --> 00:35:09.159
<v Nick Leeder>behind me, but um.

547
00:35:10.300 --> 00:35:14.540
<v Nick Leeder>What I, what I mean by Yodas, and this is
another thing about scaling and success

548
00:35:15.020 --> 00:35:15.399
<v Nick Leeder>is.

549
00:35:16.270 --> 00:35:19.719
<v Nick Leeder>Obviously you see a lot of very important
people walking around in suits at times

550
00:35:19.719 --> 00:35:21.679
<v Nick Leeder>talking about the huge benefits you get
from this.

551
00:35:22.590 --> 00:35:25.300
<v Nick Leeder>But they don't really change people's
opinions.

552
00:35:25.479 --> 00:35:32.479
<v Nick Leeder>Um, what Yoda, yeah, Yoda's the wise
engineer that's been around your business for

553
00:35:32.479 --> 00:35:36.879
<v Nick Leeder>many years, that everybody actually kind
of all the engineers go to and listen

554
00:35:36.879 --> 00:35:37.969
<v Nick Leeder>because when Yoda says.

555
00:35:38.949 --> 00:35:42.189
<v Nick Leeder>Something's wrong, everybody goes, yes it
is something wrong, everybody listens to

556
00:35:42.189 --> 00:35:46.270
<v Nick Leeder>them, their experience, their knowledge,
their wise, position, and if you can

557
00:35:46.270 --> 00:35:50.820
<v Nick Leeder>identify the Yodas in your operations that
says, you know what, predictive

558
00:35:50.820 --> 00:35:55.449
<v Nick Leeder>maintenance is the future, and this is why
I believe it's the way to work forward.

559
00:35:56.209 --> 00:35:59.929
<v Nick Leeder>Actually you get a lot of momentum cos you
get support behind you, Yoda.

560
00:36:00.800 --> 00:36:05.100
<v Nick Leeder>The, the challenge is Yodas are difficult
to convince, so you've got to be spot on

561
00:36:05.110 --> 00:36:06.229
<v Nick Leeder>on what you need to do.

562
00:36:06.679 --> 00:36:10.719
<v Nick Leeder>But actually, if you get your Yodas on
side, then that whole skating journey and

563
00:36:10.719 --> 00:36:12.860
<v Nick Leeder>bringing the rest of the organization
comes on.

564
00:36:13.360 --> 00:36:17.709
<v Nick Leeder>Um, and the other interesting thing is
whilst the engineers listen to Yoda, Yoda

565
00:36:17.709 --> 00:36:22.189
<v Nick Leeder>often carries a lot of respect back up
into the high Jedi council or, or let's call

566
00:36:22.189 --> 00:36:24.610
<v Nick Leeder>it the management team in your your
operations.

567
00:36:25.000 --> 00:36:29.399
<v Nick Leeder>So that, that has a two found or two
pronged approach of actually getting people

568
00:36:29.399 --> 00:36:30.280
<v Nick Leeder>buying upwards.

569
00:36:30.659 --> 00:36:33.120
<v Nick Leeder>And engagement and alignment downwards as
well.

570
00:36:36.080 --> 00:36:40.020
<v Niall Sullivan>But And you're right, and I'm sorry, I was
just thinking about through that as well,

571
00:36:40.120 --> 00:36:44.360
<v Niall Sullivan>so it's like horizontally and vertically
as well is is equally important, you're

572
00:36:44.360 --> 00:36:44.860
<v Niall Sullivan>saying.

573
00:36:45.439 --> 00:36:49.989
<v Nick Leeder>Yeah, absolutely, uh, yeah, because if you
don't, you can have all the managers

574
00:36:49.989 --> 00:36:53.389
<v Nick Leeder>saying this is the perfect solution, but
if nobody uses it, it never returns its

575
00:36:53.389 --> 00:36:58.860
<v Nick Leeder>value, so you kind of gotta get, gotta get
the people who do the day job on board

576
00:36:59.239 --> 00:37:03.209
<v Nick Leeder>and you know, as I've said, one of the
most successful things I've done in my career

577
00:37:03.620 --> 00:37:06.560
<v Nick Leeder>is generally identify quite quickly who
are the yodas.

578
00:37:07.110 --> 00:37:12.360
<v Nick Leeder>To get them on board um and actually
they're great to challenge you, they're great

579
00:37:12.360 --> 00:37:14.469
<v Nick Leeder>to challenge you and say is this the right
thing?

580
00:37:14.919 --> 00:37:18.679
<v Nick Leeder>Is there a different way of doing it, and
it really helps your own perspective in

581
00:37:18.679 --> 00:37:19.959
<v Nick Leeder>driving these projects forward as

582
00:37:19.959 --> 00:37:20.219
<v Niall Sullivan>well.

583
00:37:21.090 --> 00:37:22.810
<v Niall Sullivan>Yeah, and, and within Siemens as well.

584
00:37:22.919 --> 00:37:27.209
<v Niall Sullivan>So with our deployment to predictive
maintenance, we also, we have a similar, what

585
00:37:27.209 --> 00:37:28.610
<v Niall Sullivan>we call PDM champions.

586
00:37:28.770 --> 00:37:32.570
<v Niall Sullivan>So as we talk about a champion, someone
who's gonna really drive the project, be the

587
00:37:32.570 --> 00:37:37.280
<v Niall Sullivan>point of contact, be the link between, you
know, us as a vendor and, and them, and,

588
00:37:37.370 --> 00:37:38.770
<v Niall Sullivan>and working very closely with them.

589
00:37:38.889 --> 00:37:43.409
<v Niall Sullivan>And they're usually the big, you know, big
driver of using the platform of getting

590
00:37:43.409 --> 00:37:46.389
<v Niall Sullivan>buy-in, and for the scale aspect as well.

591
00:37:46.860 --> 00:37:49.030
<v Niall Sullivan>Yeah, so we see that as a very important
role.

592
00:37:49.500 --> 00:37:51.600
<v Nick Leeder>You say you say champion, I say Yoda.

593
00:37:53.300 --> 00:37:57.159
<v Niall Sullivan>Exactly, but it's just great, we're
talking about the very similar things as well,

594
00:37:57.459 --> 00:37:57.860
<v Niall Sullivan>um.

595
00:37:58.909 --> 00:38:04.090
<v Niall Sullivan>And I guess in terms of, um, I see we're
rapidly running out of time, so I want to,

596
00:38:04.110 --> 00:38:08.169
<v Niall Sullivan>um, well, I wanted to talk about the sort
of the business case angle as well.

597
00:38:08.270 --> 00:38:12.370
<v Niall Sullivan>So hopefully you've seen success, maybe
start online and like I say, starting small,

598
00:38:12.830 --> 00:38:14.169
<v Niall Sullivan>growing bigger and bigger and bigger, but.

599
00:38:14.590 --> 00:38:18.840
<v Niall Sullivan>Um, as you get sort of bigger deployments,
or maybe even not, but how do you sort of

600
00:38:18.840 --> 00:38:21.719
<v Niall Sullivan>approach sort of the resale investment and
building a business case between the

601
00:38:21.719 --> 00:38:23.760
<v Niall Sullivan>different stages of scaling, let's say.

602
00:38:24.000 --> 00:38:25.639
<v Niall Sullivan>So I'm sure it changes as you go.

603
00:38:25.879 --> 00:38:29.120
<v Nick Leeder>So, a, a point I've raised, but I'll keep
going back to it because I think it's so

604
00:38:29.120 --> 00:38:29.659
<v Nick Leeder>important.

605
00:38:30.040 --> 00:38:33.919
<v Nick Leeder>Uh, financial business cases and
spreadsheets are all well and good, but real world

606
00:38:33.919 --> 00:38:39.629
<v Nick Leeder>examples of where things fail, have caused
problems, and generally give everybody a

607
00:38:39.629 --> 00:38:40.500
<v Nick Leeder>real pain.

608
00:38:40.959 --> 00:38:44.219
<v Nick Leeder>Yeah, it's a real pain, something they've
experienced themselves.

609
00:38:44.810 --> 00:38:48.159
<v Nick Leeder>Not just in the KPIs they're measured by,
but all the problems they've had to deal

610
00:38:48.159 --> 00:38:51.360
<v Nick Leeder>with as a consequence of it, and that's
really good for leaderships, by the way.

611
00:38:52.159 --> 00:38:56.000
<v Nick Leeder>Um, that's the starting point for me in a
business case.

612
00:38:56.120 --> 00:38:59.479
<v Nick Leeder>You, you can build the spreadsheets up
and, you know, I've, the amount of business

613
00:38:59.479 --> 00:39:02.199
<v Nick Leeder>cases I've written over my year, over the
years I've been working.

614
00:39:02.639 --> 00:39:08.419
<v Nick Leeder>But actually it's, it's, I always see
those, the real world examples, those stories

615
00:39:09.149 --> 00:39:13.739
<v Nick Leeder>everybody relates to, so it brings it,
brings the financial case to life.

616
00:39:14.320 --> 00:39:19.879
<v Nick Leeder>Um, think about the secondary but also
tangible.

617
00:39:20.739 --> 00:39:21.840
<v Nick Leeder>Benefits as well.

618
00:39:22.729 --> 00:39:26.729
<v Nick Leeder>So unplanned downtime, you know, we, you
mentioned that, that's the traditional

619
00:39:26.729 --> 00:39:27.389
<v Nick Leeder>case, but.

620
00:39:28.179 --> 00:39:33.340
<v Nick Leeder>Actually, with predictive maintenance, um,
you know, maintenance costs go down.

621
00:39:34.050 --> 00:39:36.639
<v Nick Leeder>Yeah, about 2020 to 25%.

622
00:39:37.469 --> 00:39:43.389
<v Nick Leeder>Asset life can be extended by about 20%,
um, and that's some data out of the US

623
00:39:43.389 --> 00:39:46.629
<v Nick Leeder>actually, the Department of Energy, uh, a
couple of years ago had that.

624
00:39:47.500 --> 00:39:52.300
<v Nick Leeder>So, you know, you you're you're now
touching on not just uh the downtime question,

625
00:39:52.379 --> 00:39:56.860
<v Nick Leeder>but the kind of cause and effect and the
opportunities that you have that are quite

626
00:39:56.860 --> 00:40:01.179
<v Nick Leeder>tangible to measure cos you're not
replacing equipment so regularly, and that has a

627
00:40:01.179 --> 00:40:03.060
<v Nick Leeder>direct cost on the bottom line of
companies.

628
00:40:04.629 --> 00:40:09.659
<v Nick Leeder>And then the final area I think, and it
depends how far you go, but sustainability,

629
00:40:09.800 --> 00:40:14.770
<v Nick Leeder>uh, I mean it uses well maintained
equipment, is well known, it uses less energy.

630
00:40:15.280 --> 00:40:19.959
<v Nick Leeder>Can you have a well maintained versus it's
traditionally maintained machines, do

631
00:40:19.959 --> 00:40:21.719
<v Nick Leeder>energy monitoring it, see the difference
of it.

632
00:40:22.120 --> 00:40:27.120
<v Nick Leeder>That's, that's hard money, you know,
coming out of the business, um, and the ESG

633
00:40:27.120 --> 00:40:33.360
<v Nick Leeder>targets you have, uh, a great example, SKF
on, on their bearings, a remanufactured

634
00:40:33.360 --> 00:40:33.939
<v Nick Leeder>bearing.

635
00:40:34.379 --> 00:40:41.179
<v Nick Leeder>I think it uses 80%, 90% less energy and
has 80% of the carbon footprint of a new

636
00:40:41.179 --> 00:40:41.639
<v Nick Leeder>bearing.

637
00:40:42.360 --> 00:40:46.469
<v Nick Leeder>So, you know, running things to failure
basically means you've got the scrap of that

638
00:40:46.469 --> 00:40:47.030
<v Nick Leeder>equipment.

639
00:40:47.320 --> 00:40:50.120
<v Nick Leeder>You can then actually you don't run it to
failure, you take it out early, you

640
00:40:50.120 --> 00:40:50.939
<v Nick Leeder>maintain it.

641
00:40:51.659 --> 00:40:56.239
<v Nick Leeder>You, you're actually having a downstream
significant downstream impact in terms of

642
00:40:56.239 --> 00:40:56.899
<v Nick Leeder>sustainability.

643
00:40:58.540 --> 00:41:03.179
<v Nick Leeder>Uh, that one's a little bit more kind of,
I'll say on the edge, but it is real.

644
00:41:03.330 --> 00:41:08.260
<v Nick Leeder>It is real in terms of a, a, a business
case, so make it, you know, I can use the

645
00:41:08.260 --> 00:41:12.350
<v Nick Leeder>word real again, but make it real with
real success stories and examples of where

646
00:41:12.350 --> 00:41:17.949
<v Nick Leeder>people have seen the pain and how you
avoid the pain they've had, um, link it to

647
00:41:17.949 --> 00:41:23.189
<v Nick Leeder>direct real cost savings and not just
about platinum plan downtime, and then look at

648
00:41:23.189 --> 00:41:26.629
<v Nick Leeder>the other things that has like a yes, uh,
the sustainability angle as well.

649
00:41:28.739 --> 00:41:31.969
<v Niall Sullivan>Yeah, and it's, it's interesting, it does
link back to what we talked about that

650
00:41:32.310 --> 00:41:35.620
<v Niall Sullivan>when you're looking at building a business
case, it's not just about, you know, it's

651
00:41:35.620 --> 00:41:39.909
<v Niall Sullivan>looking, uh, of course, it's looking for
the, the problems you'll try and sell,

652
00:41:40.149 --> 00:41:44.949
<v Niall Sullivan>solve and maybe the critical assets you
need to, to manage, but, um, it's also

653
00:41:44.949 --> 00:41:49.389
<v Niall Sullivan>thinking beyond maybe just sort of
unplanned downtime and the vast potential of what

654
00:41:49.389 --> 00:41:50.750
<v Niall Sullivan>predicts maintenance can solve.

655
00:41:50.870 --> 00:41:54.429
<v Niall Sullivan>I mean, it's really the key and look at
other use cases, let's say.

656
00:41:55.320 --> 00:42:00.350
<v Nick Leeder>Yeah, um, you know I'm I'm sure the
finance director will get really excited because

657
00:42:00.350 --> 00:42:04.310
<v Nick Leeder>you can actually keep the machine running
2 years longer because of this rather than

658
00:42:04.310 --> 00:42:07.790
<v Nick Leeder>replace it, you know, and not having to
take the Capital investment they need.

659
00:42:08.149 --> 00:42:13.419
<v Nick Leeder>So I think there are some really strong
lines there that could be actually pursued.

660
00:42:13.790 --> 00:42:18.060
<v Nick Leeder>And it, it's very, very dependent on the
situation of the company and where that

661
00:42:18.060 --> 00:42:21.389
<v Nick Leeder>company is, where it is financially and
what their priorities are, and then you

662
00:42:21.389 --> 00:42:25.350
<v Nick Leeder>know, I think that, I didn't actually
mention that, but understanding those things

663
00:42:25.350 --> 00:42:26.489
<v Nick Leeder>before you write your business case.

664
00:42:27.159 --> 00:42:30.389
<v Nick Leeder>Are going to be also really critical, look
at your goals, your business goals over

665
00:42:30.389 --> 00:42:35.709
<v Nick Leeder>the next 3 to 5 years, also tie it into
those and without doing this, how much

666
00:42:35.709 --> 00:42:37.989
<v Nick Leeder>harder it is to achieve those goals.

667
00:42:39.770 --> 00:42:41.770
<v Niall Sullivan>Exactly, 100%, um.

668
00:42:42.739 --> 00:42:46.060
<v Niall Sullivan>And so yeah, so just to finish, I mean we
like to do this on, on the, on the

669
00:42:46.060 --> 00:42:50.820
<v Niall Sullivan>podcast, it's just, you know, if we're, if
we're gonna sort of finish here, um, lots

670
00:42:50.820 --> 00:42:55.139
<v Niall Sullivan>of great tips and information and a lot to
take in, but if, if Nick, just to sort of

671
00:42:55.139 --> 00:42:59.899
<v Niall Sullivan>summarize, maybe three key things for, um,
for companies, organizations to think

672
00:42:59.899 --> 00:43:03.699
<v Niall Sullivan>about if they want to get started with
predictor maintenance and want to scale and

673
00:43:03.699 --> 00:43:07.199
<v Niall Sullivan>build that business case to scale, what
should they be thinking about first of all?

674
00:43:08.219 --> 00:43:09.639
<v Nick Leeder>Um, so.

675
00:43:10.489 --> 00:43:13.590
<v Nick Leeder>I, I think the, the 3 things, the 3
takeaways would be.

676
00:43:14.469 --> 00:43:19.899
<v Nick Leeder>Be clear and make it real on why you need
to do it.

677
00:43:20.110 --> 00:43:24.350
<v Nick Leeder>It's not about the technology, it's about
the why for your business.

678
00:43:25.459 --> 00:43:29.780
<v Nick Leeder>So that'd be number one, that business
case is probably more richer when you think

679
00:43:29.780 --> 00:43:32.860
<v Nick Leeder>about it as why rather than the financial
just the financial return.

680
00:43:34.679 --> 00:43:39.909
<v Nick Leeder>Um, the, the second, uh, one will be start
small, really prove it.

681
00:43:40.129 --> 00:43:42.060
<v Nick Leeder>You don't have to measure everything.

682
00:43:42.399 --> 00:43:46.919
<v Nick Leeder>Measure those critical assets, show the
real impact, and then have a plan on how to

683
00:43:46.919 --> 00:43:51.090
<v Nick Leeder>scale it across your assets or across
similar assets in multiple plants.

684
00:43:53.010 --> 00:43:56.040
<v Nick Leeder>And then the final thing is people and
culture, yeah.

685
00:43:56.459 --> 00:44:01.699
<v Nick Leeder>This, again, it's technology, but you have
to show how people's lives get better on

686
00:44:01.699 --> 00:44:03.090
<v Nick Leeder>a day to day basis.

687
00:44:03.659 --> 00:44:08.620
<v Nick Leeder>So you could have the most successful
technical deployment of PDM in the world,

688
00:44:08.739 --> 00:44:09.959
<v Nick Leeder>predictive maintenance in the world.

689
00:44:10.290 --> 00:44:13.699
<v Nick Leeder>If nobody uses it, it delivers zero value.

690
00:44:14.370 --> 00:44:19.360
<v Nick Leeder>To show how it makes people's lives
better, improves their job.

691
00:44:20.270 --> 00:44:24.610
<v Nick Leeder>And that is a real to me, those three
things really make a recipe for success.

692
00:44:25.229 --> 00:44:30.669
<v Nick Leeder>Um, I, I guess maybe the 3.5 I could do is
to find the right partner that fits with

693
00:44:30.669 --> 00:44:34.939
<v Nick Leeder>your organization as well, but, um, that's
a 3.5, I'll just throw that in in the

694
00:44:34.939 --> 00:44:35.189
<v Nick Leeder>end.

695
00:44:35.770 --> 00:44:36.209
<v Niall Sullivan>Yeah.

696
00:44:36.409 --> 00:44:41.330
<v Niall Sullivan>And, and exactly, exactly, it's finding,
it's finding a, a partner or a vendor that,

697
00:44:41.409 --> 00:44:43.590
<v Niall Sullivan>you know, that works with you as well.

698
00:44:43.689 --> 00:44:48.570
<v Niall Sullivan>Um, I mean, yeah, we're talking, my, I'm
talking from a Siemens context, but we're

699
00:44:48.570 --> 00:44:51.530
<v Niall Sullivan>certainly about, it's not about, here's
the technology, off you go.

700
00:44:51.649 --> 00:44:55.370
<v Niall Sullivan>It's very much working together to work
with you to deliver success, cos obviously

701
00:44:55.370 --> 00:44:58.229
<v Niall Sullivan>it, you know, it benefits everyone, um,
for that to happen.

702
00:44:58.449 --> 00:44:59.010
<v Niall Sullivan>So that's the key.

703
00:44:59.050 --> 00:45:00.189
<v Niall Sullivan>You want a vendor who's really.

704
00:45:01.040 --> 00:45:05.040
<v Niall Sullivan>Working with you and not just supplying
you software as an example, it's

705
00:45:05.040 --> 00:45:09.000
<v Nick Leeder>having shared goals, and the shared goal,
the shared goal isn't a successful

706
00:45:09.000 --> 00:45:13.959
<v Nick Leeder>technical deployment, a shared goal is
actually improving the uptime, the

707
00:45:13.959 --> 00:45:18.750
<v Nick Leeder>availability, the safety of your
equipment, um, and actually making the maintenance

708
00:45:18.750 --> 00:45:21.379
<v Nick Leeder>engineers and technicians' jobs better on
a day to day basis.

709
00:45:23.060 --> 00:45:23.870
<v Niall Sullivan>Absolutely.

710
00:45:24.110 --> 00:45:30.510
<v Niall Sullivan>Um, so yeah, so really great takeaways
there as well, um, and a lot, um, for, I

711
00:45:30.510 --> 00:45:34.229
<v Niall Sullivan>guess people to think about, but if, um,
they wanted to continue the conversation

712
00:45:34.229 --> 00:45:37.709
<v Niall Sullivan>with you, Nick, where's the sort of best
place for people to, to find out about you

713
00:45:37.709 --> 00:45:40.149
<v Niall Sullivan>or keep up to date with what you're, what
you're doing?

714
00:45:40.919 --> 00:45:44.060
<v Nick Leeder>Um, great question, I hadn't actually
thought of an answer to that, but funny

715
00:45:44.060 --> 00:45:45.500
<v Nick Leeder>enough, I do have a website.

716
00:45:45.860 --> 00:45:49.729
<v Nick Leeder>So, um, number one, if you wanna see what
we do, uh, if you go to Nick Leeder,

717
00:45:49.820 --> 00:45:56.379
<v Nick Leeder>that's with two E's, so N I C K L E E D E
R dot com, you'll see what we do there and

718
00:45:56.379 --> 00:46:00.979
<v Nick Leeder>some good examples, uh, of about the
different states and how we take manufacturing

719
00:46:00.979 --> 00:46:02.840
<v Nick Leeder>businesses through that transformational
journey.

720
00:46:03.419 --> 00:46:06.320
<v Nick Leeder>Another one would be to go find Nick
Leeder and Co.

721
00:46:06.929 --> 00:46:12.290
<v Nick Leeder>On, uh, LinkedIn, we have a weekly Beyond
the Buzzwords newsletter where I, I talked

722
00:46:12.290 --> 00:46:14.770
<v Nick Leeder>about it at the beginning, you know, right
now we're talking about the manufacturing

723
00:46:14.770 --> 00:46:19.449
<v Nick Leeder>mousetrap, um, in the, you know, the next,
uh, pieces, next, next one's gonna be

724
00:46:19.449 --> 00:46:23.889
<v Nick Leeder>around the seven deadly sins of digital
transformation in manufacturing, so there's

725
00:46:23.889 --> 00:46:28.439
<v Nick Leeder>some great little kind of insights and
ideas that you can take away and think about

726
00:46:28.610 --> 00:46:30.129
<v Nick Leeder>in terms of your own organization.

727
00:46:31.350 --> 00:46:31.830
<v Niall Sullivan>Fantastic.

728
00:46:31.949 --> 00:46:35.229
<v Niall Sullivan>So what, what we'll do to make it a bit
easier for everyone as well, we'll just link

729
00:46:35.229 --> 00:46:39.189
<v Niall Sullivan>to, to those, um, yeah, to those places in
the sort of description as well, so you

730
00:46:39.189 --> 00:46:40.939
<v Niall Sullivan>can access those quite easily.

731
00:46:40.989 --> 00:46:44.030
<v Niall Sullivan>But, um, but no, thank you, Nick, for your
time today.

732
00:46:44.189 --> 00:46:47.570
<v Niall Sullivan>Um, really interesting to get, and again,
I say this a lot, like getting the

733
00:46:47.570 --> 00:46:50.590
<v Niall Sullivan>external perspective as well and bringing
that voice to the podcast.

734
00:46:50.709 --> 00:46:54.429
<v Niall Sullivan>I really appreciate, um, your time sort of
sharing your sort of knowledge and

735
00:46:54.429 --> 00:46:56.030
<v Niall Sullivan>expertise on this topic.

736
00:46:56.469 --> 00:47:00.350
<v Niall Sullivan>And I'd like to say that we'd hope you're
back on soon, cos I'd love to sort of

737
00:47:00.350 --> 00:47:03.550
<v Niall Sullivan>continue the conversation in other areas
as well, but, um, hopefully we haven't

738
00:47:03.550 --> 00:47:04.500
<v Niall Sullivan>scared you off.

739
00:47:05.370 --> 00:47:06.020
<v Niall Sullivan>No, not at all.

740
00:47:06.370 --> 00:47:07.290
<v Niall Sullivan>Thank you so much.

741
00:47:07.790 --> 00:47:10.939
<v Niall Sullivan>Thank you, everyone, and thank you,
everyone out there for listening to the podcast,

742
00:47:10.949 --> 00:47:12.449
<v Niall Sullivan>and we'll see you on the next episode.

743
00:47:14.500 --> 00:47:19.439
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

744
00:47:19.439 --> 00:47:23.040
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
