WEBVTT
Language: en-US

1
00:00:02.029 --> 00:00:05.610
<v Speaker 1>Welcome to the trend detection podcast
powered by Siemens.

2
00:00:05.789 --> 00:00:07.750
<v Speaker 1>And now your host, Nel Sullivan.

3
00:00:10.590 --> 00:00:15.300
<v Speaker 2>And so I'm going to see a hand over to our
first speaker, Nick Leader, um, who's

4
00:00:15.300 --> 00:00:19.409
<v Speaker 2>gonna talk about what can we do
differently to scale predictive maintenance.

5
00:00:19.870 --> 00:00:22.729
<v Speaker 2>So Nick's, um, an award winning coach and
advisor.

6
00:00:22.829 --> 00:00:25.610
<v Speaker 2>Um, I've interviewed him many times on our
podcast.

7
00:00:26.389 --> 00:00:30.469
<v Speaker 2>um, and one thing is for sure, you say
beyond the buzzwords, Nick isn't a fan of

8
00:00:30.469 --> 00:00:33.909
<v Speaker 2>buzzwords, so there'll be lots of
actionable insights here for you.

9
00:00:34.869 --> 00:00:38.590
<v Speaker 2>So without further ado, I'm gonna hand
over to Nick um to take it away, so over to

10
00:00:38.590 --> 00:00:39.029
<v Speaker 2>you, Nick.

11
00:00:40.119 --> 00:00:45.450
<v Nick Leeder>Thanks Noel, and, and thank you everybody
for the opportunity to uh speak with you

12
00:00:45.459 --> 00:00:48.810
<v Nick Leeder>today about scaling predictive
maintenance.

13
00:00:48.930 --> 00:00:53.509
<v Nick Leeder>Um, now just if you could give me two
seconds, I'm gonna have a, a, a quick go at

14
00:00:53.509 --> 00:00:57.110
<v Nick Leeder>sharing and hopefully that all works for
everybody.

15
00:00:57.650 --> 00:01:04.489
<v Nick Leeder>So, um, I think when we start using, uh,
the phrase scaling, we have to actually put

16
00:01:04.489 --> 00:01:09.529
<v Nick Leeder>that into context, because scaling means
different things to different people.

17
00:01:10.230 --> 00:01:14.040
<v Nick Leeder>Um, So what do we mean by scale?

18
00:01:14.360 --> 00:01:19.040
<v Nick Leeder>So we've all got our assets, our critical
assets in our facilities, and they've got

19
00:01:19.319 --> 00:01:23.879
<v Nick Leeder>some level of sensors on them, so it's
picking up the vibration, the noise, and we,

20
00:01:23.959 --> 00:01:28.760
<v Nick Leeder>we, we're using predictive maintenance to
understand whether something's gonna break

21
00:01:28.760 --> 00:01:29.500
<v Nick Leeder>or not.

22
00:01:30.080 --> 00:01:36.910
<v Nick Leeder>But as we take that, we also start looking
at that asset sits within a

23
00:01:36.910 --> 00:01:39.959
<v Nick Leeder>larger facility, and in that facility.

24
00:01:40.680 --> 00:01:45.330
<v Nick Leeder>There are many of those assets, and that's
actually the first level of scaling for

25
00:01:45.330 --> 00:01:47.230
<v Nick Leeder>many companies and many businesses.

26
00:01:47.720 --> 00:01:53.970
<v Nick Leeder>It is kind of understanding really what,
you know, where can we use this technology

27
00:01:53.970 --> 00:01:55.089
<v Nick Leeder>else within the plant.

28
00:01:55.989 --> 00:02:02.190
<v Nick Leeder>And for many people, that's as far as
scaling goes, and it depends often on the

29
00:02:02.190 --> 00:02:05.389
<v Nick Leeder>responsibility of the individual and what
they're trying to do.

30
00:02:06.000 --> 00:02:10.000
<v Nick Leeder>And as I'm gonna go through today, I'm
gonna say the challenges here are no

31
00:02:10.000 --> 00:02:16.399
<v Nick Leeder>deference to the next level of scaling
because that factory also might sit within a

32
00:02:16.399 --> 00:02:19.059
<v Nick Leeder>network of factories across your business.

33
00:02:19.869 --> 00:02:26.199
<v Nick Leeder>And again, that is scaling again, but in a
different context for different people.

34
00:02:26.669 --> 00:02:31.070
<v Nick Leeder>So when we think about scaling, we don't
just think about scaling within the

35
00:02:31.070 --> 00:02:34.550
<v Nick Leeder>factory, we think about scaling across all
our factories.

36
00:02:35.149 --> 00:02:39.149
<v Nick Leeder>And again, back to that point, the
challenges, whether we're talking about one

37
00:02:39.149 --> 00:02:42.190
<v Nick Leeder>factory or many factories, are often the
same.

38
00:02:44.360 --> 00:02:46.259
<v Nick Leeder>So scaling's easy, right?

39
00:02:46.639 --> 00:02:49.899
<v Nick Leeder>I mean, it can't be that hard, it's just
putting more sensors on a machine.

40
00:02:52.229 --> 00:02:55.850
<v Nick Leeder>Now, it, it, the, the reality is it's not
quite that easy.

41
00:02:56.259 --> 00:03:02.389
<v Nick Leeder>And the reason being is, as you grow from
just doing one or two machines into many

42
00:03:02.389 --> 00:03:07.429
<v Nick Leeder>machines all across many machines across
many factories, the challenges are no

43
00:03:07.429 --> 00:03:11.410
<v Nick Leeder>longer linked really to the technology
itself.

44
00:03:12.059 --> 00:03:15.850
<v Nick Leeder>The challenges start to become around the
people.

45
00:03:17.279 --> 00:03:20.100
<v Nick Leeder>So what gets in the way of scaling?

46
00:03:20.559 --> 00:03:23.660
<v Nick Leeder>Well, as you unders you know, as I started
to talk about a second ago.

47
00:03:24.839 --> 00:03:28.300
<v Nick Leeder>The first thing that starts to get in the
way are the behaviors.

48
00:03:29.369 --> 00:03:35.889
<v Nick Leeder>People are, and rightly so, proud about
the way they do things and how they, you

49
00:03:35.889 --> 00:03:39.089
<v Nick Leeder>know, particularly maintenance engineers,
they know their assets.

50
00:03:39.570 --> 00:03:44.470
<v Nick Leeder>They can often walk up to uh a machine and
understand if it's gonna break or not,

51
00:03:44.850 --> 00:03:46.880
<v Nick Leeder>just by listening to the sound.

52
00:03:47.330 --> 00:03:51.610
<v Nick Leeder>So there's a lot of knowledge, but there's
a lot of behaviors in there.

53
00:03:52.880 --> 00:03:58.020
<v Nick Leeder>Those silos, you know, we have in the
business, you know, the maintenance teams, the

54
00:03:58.020 --> 00:04:01.490
<v Nick Leeder>operations teams, sometimes there's IT
teams involved.

55
00:04:01.869 --> 00:04:07.789
<v Nick Leeder>And that complexity actually means that
many times that businesses run in silos

56
00:04:07.789 --> 00:04:13.339
<v Nick Leeder>across their organization, and that means
that communication between those teams,

57
00:04:13.470 --> 00:04:17.309
<v Nick Leeder>working, collaboration, is a barrier that
we have to overcome.

58
00:04:18.170 --> 00:04:22.450
<v Nick Leeder>And skepticism, as I mentioned like the
behaviors of we've always done it this way,

59
00:04:22.820 --> 00:04:28.339
<v Nick Leeder>there's a skepticism, particularly with
very experienced and knowledgeable people

60
00:04:28.339 --> 00:04:34.059
<v Nick Leeder>about what can predictive maintenance
actually teach them, and we need to kind of

61
00:04:34.059 --> 00:04:35.260
<v Nick Leeder>understand that to address it.

62
00:04:36.640 --> 00:04:42.119
<v Nick Leeder>And then think the last one, but it's
certainly not the least one, our priorities.

63
00:04:43.290 --> 00:04:48.850
<v Nick Leeder>Now, often, you know, when I talk to
companies about starting their transformation

64
00:04:48.850 --> 00:04:53.690
<v Nick Leeder>journeys in the business, perhaps looking
at predictive maintenance as one of those

65
00:04:53.690 --> 00:04:55.049
<v Nick Leeder>first steps.

66
00:04:55.799 --> 00:04:59.739
<v Nick Leeder>There's always the question of, yeah,
that's great, but I don't have the time or

67
00:05:00.000 --> 00:05:04.519
<v Nick Leeder>there's no budget to do this with, and I'm
sure everybody on the call gets and sees

68
00:05:04.519 --> 00:05:06.779
<v Nick Leeder>that and hears that on a regular basis.

69
00:05:07.279 --> 00:05:11.200
<v Nick Leeder>So the barriers are quite significant, and
that, you know, and when you start

70
00:05:11.200 --> 00:05:15.600
<v Nick Leeder>thinking about the 3 things, or these 4
things, sorry, I mentioned a moment ago, we

71
00:05:15.600 --> 00:05:20.359
<v Nick Leeder>go back to that scaling question because
they exist within a factory or a plant.

72
00:05:21.209 --> 00:05:25.410
<v Nick Leeder>But they also exist across all the plants
within your business, so we have to

73
00:05:25.410 --> 00:05:26.170
<v Nick Leeder>overcome them.

74
00:05:28.019 --> 00:05:29.559
<v Nick Leeder>The other thing is money.

75
00:05:29.899 --> 00:05:33.420
<v Nick Leeder>Do we actually understand what the cost of
downtime is?

76
00:05:34.290 --> 00:05:39.769
<v Nick Leeder>Well, the problem here is that to try and
get people to change, we have to attribute

77
00:05:39.769 --> 00:05:42.079
<v Nick Leeder>it to a problem we're trying to solve.

78
00:05:42.329 --> 00:05:48.049
<v Nick Leeder>Downtime is often measured, but the cost
of that downtime is very rarely understood.

79
00:05:48.130 --> 00:05:52.809
<v Nick Leeder>Only, you know, 80% of teams lack
visibility into the cost of downtime in the

80
00:05:52.809 --> 00:05:53.049
<v Nick Leeder>business.

81
00:05:53.130 --> 00:05:55.589
<v Nick Leeder>This was done very recently by Aberdeen
Research.

82
00:05:56.089 --> 00:05:58.459
<v Nick Leeder>That proves that actually the pain.

83
00:05:58.989 --> 00:06:05.119
<v Nick Leeder>The financial pain a company is feeling
from not having predictive maintenance, not

84
00:06:05.119 --> 00:06:08.739
<v Nick Leeder>having the visibility of the downtime they
have today.

85
00:06:09.829 --> 00:06:13.170
<v Nick Leeder>Is significant, and they're not in that
position to start addressing it.

86
00:06:14.850 --> 00:06:17.390
<v Nick Leeder>So we have to start the change journey.

87
00:06:18.380 --> 00:06:21.940
<v Nick Leeder>And that's that change journey, the
people, this is not again, not technology, this

88
00:06:21.940 --> 00:06:22.600
<v Nick Leeder>is people.

89
00:06:23.260 --> 00:06:27.299
<v Nick Leeder>We have to start demonstrating the value
to the people that actually matter.

90
00:06:28.049 --> 00:06:33.269
<v Nick Leeder>And we need to look at making that really
relevant to the people within your

91
00:06:33.269 --> 00:06:37.690
<v Nick Leeder>organization that are going to use
predictive maintenance, and that's not

92
00:06:37.690 --> 00:06:39.700
<v Nick Leeder>necessarily, by the way, the managers.

93
00:06:41.440 --> 00:06:46.920
<v Nick Leeder>So what we often hear is, yes, but if we
do predictive maintenance, what's that,

94
00:06:47.000 --> 00:06:47.769
<v Nick Leeder>what's the value of it?

95
00:06:47.839 --> 00:06:51.059
<v Nick Leeder>What we say often is, well, it helps us
reduce downtime.

96
00:06:51.559 --> 00:06:56.320
<v Nick Leeder>It helps us save money, you know, either
that's, you know, not having pumps and you

97
00:06:56.320 --> 00:07:00.959
<v Nick Leeder>know, fans on the shelf ready to be
swapped over when something goes wrong, or it's

98
00:07:00.959 --> 00:07:05.140
<v Nick Leeder>just the cost of not being able to run the
line because one of the machines is down.

99
00:07:08.220 --> 00:07:14.059
<v Nick Leeder>But what we need to start also
understanding is what the person on the other end is

100
00:07:14.059 --> 00:07:16.059
<v Nick Leeder>receiving, what they're hearing.

101
00:07:16.820 --> 00:07:22.500
<v Nick Leeder>And that other person, you know, yes, of
course, downtime, money is important, but

102
00:07:22.500 --> 00:07:26.720
<v Nick Leeder>we have to make it relevant, and make it
matter for them as well.

103
00:07:27.709 --> 00:07:32.739
<v Nick Leeder>So we have to start talking about it,
well, look, if we do this, you get back your

104
00:07:32.739 --> 00:07:33.209
<v Nick Leeder>weekend.

105
00:07:33.549 --> 00:07:38.019
<v Nick Leeder>You know, you're not coming in on a an
extra shift to try and get something fixed or

106
00:07:38.269 --> 00:07:43.209
<v Nick Leeder>working on sociable hours, it's actually
giving you back control.

107
00:07:44.600 --> 00:07:49.279
<v Nick Leeder>So that's a, you know, an important start
to think about the value isn't always in

108
00:07:49.279 --> 00:07:53.399
<v Nick Leeder>time and money, but it also can actually
apply to the person.

109
00:07:54.250 --> 00:07:58.049
<v Nick Leeder>That they're set, you know, and on a
personal level to the individuals that it

110
00:07:58.049 --> 00:07:58.700
<v Nick Leeder>impacts.

111
00:07:59.790 --> 00:08:01.890
<v Nick Leeder>And then we start that winning them over
journey.

112
00:08:02.000 --> 00:08:06.230
<v Nick Leeder>So if we can start talking about value,
not just in terms of what I mentioned a

113
00:08:06.230 --> 00:08:11.820
<v Nick Leeder>second ago, but making it personal to
them, then we start winning them over because

114
00:08:11.829 --> 00:08:13.769
<v Nick Leeder>we have that financial outcome.

115
00:08:14.309 --> 00:08:17.869
<v Nick Leeder>That's the first, you know, any business
scale will always scale predictor

116
00:08:17.869 --> 00:08:20.019
<v Nick Leeder>maintenance on a business case.

117
00:08:20.470 --> 00:08:23.869
<v Nick Leeder>So the outcome is we're making staff more
productive.

118
00:08:24.690 --> 00:08:28.359
<v Nick Leeder>We're stopping the downtimes, and planned
downtimes by 20%, whatever.

119
00:08:29.859 --> 00:08:33.390
<v Nick Leeder>But then we also connect that to the
emotional things, yeah, that emotional things

120
00:08:33.390 --> 00:08:36.640
<v Nick Leeder>is like, like I said a minute ago, it's
not just about.

121
00:08:37.380 --> 00:08:42.590
<v Nick Leeder>Understanding whether they can get their
time back, but also the feel-good factors

122
00:08:42.590 --> 00:08:43.219
<v Nick Leeder>as well.

123
00:08:43.510 --> 00:08:46.630
<v Nick Leeder>They fix issues before they become a
problem.

124
00:08:46.900 --> 00:08:52.099
<v Nick Leeder>You know, in maintenance, it is a world of
constant firefighting if you don't have

125
00:08:52.099 --> 00:08:53.250
<v Nick Leeder>predictive maintenance.

126
00:08:53.669 --> 00:08:57.950
<v Nick Leeder>And at some point that does become quite a
demoralizing environment to be in.

127
00:08:58.390 --> 00:09:03.650
<v Nick Leeder>So little things like proactively fixing
problems really taps into the emotion.

128
00:09:04.150 --> 00:09:07.169
<v Nick Leeder>And when you get the outcome and the
emotion together.

129
00:09:07.570 --> 00:09:11.200
<v Nick Leeder>You really start to get the buy-in of
people.

130
00:09:11.659 --> 00:09:14.020
<v Nick Leeder>And if you start getting the buy-in of
people.

131
00:09:15.229 --> 00:09:18.140
<v Nick Leeder>Then you really start that change journey
to scale.

132
00:09:19.659 --> 00:09:22.440
<v Nick Leeder>So let's go back to this question of
value.

133
00:09:23.390 --> 00:09:27.880
<v Nick Leeder>Um, I'm gonna see, I'm, I'm probably gonna
fail quite miserably here.

134
00:09:28.799 --> 00:09:34.250
<v Nick Leeder>Um, I'm gonna talk about, uh, downtime
here, one second of downtime.

135
00:09:34.489 --> 00:09:38.250
<v Nick Leeder>Now this is coming from Siemens' own
research here, uh, and the recent report

136
00:09:38.250 --> 00:09:38.849
<v Nick Leeder>they've released.

137
00:09:40.159 --> 00:09:44.080
<v Nick Leeder>How much does 1 2nd of downtime cost?

138
00:09:46.239 --> 00:09:48.900
<v Nick Leeder>Um, feel free to put it in the chat if
anybody's got an idea.

139
00:09:51.270 --> 00:09:57.690
<v Nick Leeder>OK, I'm gonna keep going So 1 2nd of
downtime is equivalent to 2 Big Macs.

140
00:09:58.520 --> 00:10:05.309
<v Nick Leeder>Now that doesn't sound very much, but one
second for an average small business is,

141
00:10:05.320 --> 00:10:08.429
<v Nick Leeder>uh, around about $13.

142
00:10:08.520 --> 00:10:12.960
<v Nick Leeder>It's a, it's about well a in a Big Mac,
I'm making some generalizations here, it's

143
00:10:12.960 --> 00:10:16.979
<v Nick Leeder>about $5 50s, yeah, but it's about $13 for
one second.

144
00:10:19.729 --> 00:10:23.239
<v Nick Leeder>But that scales significantly.

145
00:10:23.659 --> 00:10:28.099
<v Nick Leeder>So we're deep into the Big Mac index
because a Big Mac is ubiquitous, you can, it's

146
00:10:28.099 --> 00:10:30.780
<v Nick Leeder>not a dollar, you can spend it anywhere in
the world.

147
00:10:31.140 --> 00:10:37.059
<v Nick Leeder>But for some larger automotive plants,
that runs into the thousands of dollars in an

148
00:10:37.059 --> 00:10:38.869
<v Nick Leeder>hour, in seconds, sorry.

149
00:10:39.539 --> 00:10:45.140
<v Nick Leeder>That's 116 Big Macs for 1 2nd of downtime.

150
00:10:46.960 --> 00:10:49.469
<v Nick Leeder>Now, why am I using this, because.

151
00:10:50.219 --> 00:10:55.460
<v Nick Leeder>Actually, everybody knows what a Big Mac
is, everybody knows the worth of it.

152
00:10:55.700 --> 00:11:01.130
<v Nick Leeder>In fact, even The Economist uses the Big
Mac index to look at the variable um rates

153
00:11:01.130 --> 00:11:02.840
<v Nick Leeder>across different countries and the
inflation, but.

154
00:11:04.219 --> 00:11:09.669
<v Nick Leeder>Actually, everybody understands this, this
is something to get, and this is a 2nd in

155
00:11:09.669 --> 00:11:13.309
<v Nick Leeder>an automotive plant, just let's just
absorb that for 1 2nd, yeah?

156
00:11:13.669 --> 00:11:15.710
<v Nick Leeder>Yeah, no pun intended, by the way.

157
00:11:16.440 --> 00:11:22.030
<v Nick Leeder>That's 116 Big Macs in 1 2nd for an
automotive plant.

158
00:11:22.289 --> 00:11:23.380
<v Nick Leeder>1 2nd of downtime.

159
00:11:25.010 --> 00:11:28.010
<v Nick Leeder>That's more than, more than I've probably
eaten in my entire lifetime.

160
00:11:28.409 --> 00:11:32.409
<v Nick Leeder>So it probably, you know, we're starting
to make some of these values more

161
00:11:32.409 --> 00:11:37.049
<v Nick Leeder>relatable, but, you know, going back to
answering that 80% problem, here are some

162
00:11:37.049 --> 00:11:41.530
<v Nick Leeder>real test points that can start helping on
that economic and value proposition.

163
00:11:43.599 --> 00:11:49.429
<v Nick Leeder>So we need to start that journey and tell
the story, you can tell the story using

164
00:11:49.429 --> 00:11:54.010
<v Nick Leeder>Big Macs, um, but we have to take those
small wins.

165
00:11:54.690 --> 00:11:58.520
<v Nick Leeder>And build that narrative up so they become
big momentum in it.

166
00:11:58.940 --> 00:12:03.700
<v Nick Leeder>Now that story isn't just we did
predictive maintenance and we saved X number of

167
00:12:03.700 --> 00:12:04.359
<v Nick Leeder>hours.

168
00:12:04.890 --> 00:12:08.969
<v Nick Leeder>This story has to tell you the journey
that you've gone on.

169
00:12:09.179 --> 00:12:14.580
<v Nick Leeder>You know, the challenges of trying to
understand which assets to sensorize and put

170
00:12:14.580 --> 00:12:16.500
<v Nick Leeder>the sensors on to measure the prediction.

171
00:12:16.859 --> 00:12:22.989
<v Nick Leeder>Um, of, you know, uh, of, of, of
vibration, yeah, to understand actually how we went

172
00:12:22.989 --> 00:12:26.030
<v Nick Leeder>through understanding the first results,
were they results accurate?

173
00:12:26.099 --> 00:12:30.150
<v Nick Leeder>Did we have to refine the thresholds and
parameters that gave us the alerts?

174
00:12:30.200 --> 00:12:34.409
<v Nick Leeder>Did we get too many alerts, and it became
confusing.

175
00:12:34.989 --> 00:12:39.710
<v Nick Leeder>Tell the story and the journey you went
through and tell that story so it shows you

176
00:12:39.710 --> 00:12:43.450
<v Nick Leeder>how you overcame the challenges
yourselves.

177
00:12:45.169 --> 00:12:50.640
<v Nick Leeder>And don't just keep that story to
yourself, start looking at how you can share that

178
00:12:50.969 --> 00:12:51.929
<v Nick Leeder>within your organization.

179
00:12:52.770 --> 00:12:57.059
<v Nick Leeder>Now are there ways of um sharing that on
bulletin boards?

180
00:12:57.169 --> 00:12:59.760
<v Nick Leeder>I don't know many companies have them
physically.

181
00:13:00.049 --> 00:13:04.250
<v Nick Leeder>You know, I, I've seen some great examples
of going around uh factories where every

182
00:13:04.250 --> 00:13:08.520
<v Nick Leeder>time they avoid a downtime event, they put
a win on the board, they have the asset,

183
00:13:08.760 --> 00:13:14.049
<v Nick Leeder>they show what that asset is, they show
the amount of time it's been saved, what

184
00:13:14.049 --> 00:13:14.849
<v Nick Leeder>they did.

185
00:13:15.239 --> 00:13:19.559
<v Nick Leeder>What the information, what the signals
that actually told them it was going to fail,

186
00:13:19.960 --> 00:13:25.799
<v Nick Leeder>and actually what, who was involved in
stopping it, so it's not just recognizing the

187
00:13:25.799 --> 00:13:30.520
<v Nick Leeder>success and doing it on the board, it
talks about the people that were involved in

188
00:13:30.520 --> 00:13:31.320
<v Nick Leeder>it as well.

189
00:13:32.380 --> 00:13:36.500
<v Nick Leeder>So think about that success, and that
success is on the shop floor, communicate on

190
00:13:36.500 --> 00:13:40.700
<v Nick Leeder>the shop floor, but also look at ways that
you can actually elevate that upwards in

191
00:13:40.700 --> 00:13:46.859
<v Nick Leeder>the organization, because that continuous
momentum of success stories and and what

192
00:13:46.859 --> 00:13:52.179
<v Nick Leeder>you have will build more momentum and
awareness at leadership level.

193
00:13:53.460 --> 00:13:57.109
<v Nick Leeder>And I think the final one is recognize the
champions.

194
00:13:58.169 --> 00:14:03.330
<v Nick Leeder>Um, I, I, I, the little story behind this
is I've been, I've recently spent a day

195
00:14:03.330 --> 00:14:07.570
<v Nick Leeder>with a psychologist, um, and not on a
personal level, but actually on a, on a

196
00:14:07.570 --> 00:14:14.210
<v Nick Leeder>professional level, understanding how
they, they are training, um, Team GB,

197
00:14:14.599 --> 00:14:17.929
<v Nick Leeder>uh, Olympians actually on performance.

198
00:14:18.969 --> 00:14:25.570
<v Nick Leeder>And part of that was that for a long time
they were struggling to

199
00:14:25.570 --> 00:14:31.929
<v Nick Leeder>convince the people in um Team GB to to
follow their methodology, to spend time with

200
00:14:31.929 --> 00:14:32.229
<v Nick Leeder>them.

201
00:14:33.429 --> 00:14:36.929
<v Nick Leeder>And that flipped when one of them won
gold.

202
00:14:38.190 --> 00:14:43.229
<v Nick Leeder>And they, that person was saying the thing
that made the difference was spending

203
00:14:43.229 --> 00:14:44.549
<v Nick Leeder>time with this psychologist.

204
00:14:46.539 --> 00:14:51.640
<v Nick Leeder>That's, at that point in time, that
psychologist no longer had to try and sell

205
00:14:51.640 --> 00:14:51.919
<v Nick Leeder>themselves.

206
00:14:52.539 --> 00:14:54.979
<v Nick Leeder>That other person was selling it for them.

207
00:14:56.520 --> 00:15:01.710
<v Nick Leeder>That champion Was actually the advocate in
their business, talking about how great

208
00:15:01.710 --> 00:15:02.299
<v Nick Leeder>it was.

209
00:15:03.099 --> 00:15:09.169
<v Nick Leeder>So who would be your champions, how would
you recognize them within your business?

210
00:15:12.599 --> 00:15:15.169
<v Nick Leeder>And often I see.

211
00:15:16.059 --> 00:15:20.659
<v Nick Leeder>Predictive maintenance projects coming and
being driven like a project.

212
00:15:21.400 --> 00:15:24.760
<v Nick Leeder>It is a project, so it starts here and it
finishes here and then we're done.

213
00:15:25.950 --> 00:15:28.169
<v Nick Leeder>But it isn't, it's a continuous journey.

214
00:15:28.549 --> 00:15:32.409
<v Nick Leeder>And it's a journey that's really starts
taking a new mindset.

215
00:15:32.590 --> 00:15:33.409
<v Nick Leeder>If done well.

216
00:15:34.219 --> 00:15:38.580
<v Nick Leeder>That scaling factor, it creates a new
mindset within the organization, and I mean

217
00:15:38.580 --> 00:15:42.400
<v Nick Leeder>that could be, as I said, go back, let's
go back to that scale question.

218
00:15:42.940 --> 00:15:47.659
<v Nick Leeder>That could be just the teams on your, on
the shop floor in your plant, or it could,

219
00:15:47.700 --> 00:15:52.580
<v Nick Leeder>and it could be just the maintenance team,
for example, or it could be different

220
00:15:52.580 --> 00:15:55.219
<v Nick Leeder>plants working together and working in a
different way.

221
00:15:55.919 --> 00:16:01.080
<v Nick Leeder>But the things I see very differently,
that shift, it starts driving a level of

222
00:16:01.080 --> 00:16:03.179
<v Nick Leeder>curiosity within the business.

223
00:16:04.599 --> 00:16:09.080
<v Nick Leeder>They start looking at this and going,
actually there there's something there that I

224
00:16:09.080 --> 00:16:10.460
<v Nick Leeder>didn't know existed.

225
00:16:10.599 --> 00:16:14.479
<v Nick Leeder>I'm now starting to see why things might
be failing.

226
00:16:16.260 --> 00:16:22.809
<v Nick Leeder>It actually starts bringing forward the
visibility of those problems within the

227
00:16:22.809 --> 00:16:23.179
<v Nick Leeder>organization.

228
00:16:23.460 --> 00:16:27.010
<v Nick Leeder>And actually that visibility can happen on
many different levels.

229
00:16:27.299 --> 00:16:31.530
<v Nick Leeder>It can happen at the expert level, the
VA's, the VA twos, the VA threes, with a

230
00:16:31.530 --> 00:16:35.859
<v Nick Leeder>detailed spectral analysis of actually
understanding what the potential failures

231
00:16:35.859 --> 00:16:36.380
<v Nick Leeder>are.

232
00:16:37.239 --> 00:16:41.700
<v Nick Leeder>That visibility can then be used at an
operational level, so the maintenance person

233
00:16:42.000 --> 00:16:46.840
<v Nick Leeder>can actually see well what's the health of
my assets, and I don't have to go hunting

234
00:16:46.840 --> 00:16:49.400
<v Nick Leeder>around, it's on there on a single page in
a single place.

235
00:16:50.760 --> 00:16:55.719
<v Nick Leeder>But it will also elevate that same
information up to management level, so the

236
00:16:55.719 --> 00:16:59.929
<v Nick Leeder>management gets an overall visibility of
what the health of the plant is or what the

237
00:16:59.929 --> 00:17:02.020
<v Nick Leeder>health of all the critical assets are.

238
00:17:02.400 --> 00:17:07.439
<v Nick Leeder>So that visibility and that curiosity
really starts driving the next thing, which is

239
00:17:07.439 --> 00:17:09.520
<v Nick Leeder>then starting to take ownership.

240
00:17:10.318 --> 00:17:13.749
<v Nick Leeder>You actually create and allow people and
empower people.

241
00:17:14.798 --> 00:17:20.788
<v Nick Leeder>To act to make sure that they feel
responsible and accountable for ensuring the

242
00:17:20.788 --> 00:17:22.869
<v Nick Leeder>performance of the facility and
production.

243
00:17:24.069 --> 00:17:29.430
<v Nick Leeder>And that ownership, when those 3 things
start happening together, curiosity, the

244
00:17:29.430 --> 00:17:34.339
<v Nick Leeder>visibility and the ownership, you really
know that you're on that journey of

245
00:17:34.339 --> 00:17:38.949
<v Nick Leeder>continuous improvement within, driven by
predictive maintenance, and that journey of

246
00:17:38.949 --> 00:17:43.550
<v Nick Leeder>scaling is healthy and is ready to start,
if not already started.

247
00:17:46.800 --> 00:17:52.229
<v Nick Leeder>So the things that really drive that from
a pilot, cause some of those things really

248
00:17:52.229 --> 00:17:57.750
<v Nick Leeder>exist even in a pilot stage, and then look
at scale and performance of four key

249
00:17:57.750 --> 00:18:01.949
<v Nick Leeder>things, and these are the four things I've
seen repeatedly um when I've worked with

250
00:18:01.949 --> 00:18:03.189
<v Nick Leeder>predictive maintenance in my career.

251
00:18:04.750 --> 00:18:07.290
<v Nick Leeder>First thing is a standard level of
standardization.

252
00:18:08.530 --> 00:18:12.040
<v Nick Leeder>How you go about using predictive
maintenance, you should be using the same

253
00:18:12.040 --> 00:18:16.910
<v Nick Leeder>processes, the same approaches, but also
the same technology because that allows you

254
00:18:17.770 --> 00:18:20.209
<v Nick Leeder>to get that visibility I mentioned earlier
on.

255
00:18:22.209 --> 00:18:25.900
<v Nick Leeder>You have to think about how maintenance
and predictive maintenance actually is

256
00:18:25.900 --> 00:18:30.540
<v Nick Leeder>connected in the broader processes within
the business.

257
00:18:31.300 --> 00:18:33.680
<v Nick Leeder>So you have to connect those processes
together.

258
00:18:34.810 --> 00:18:38.819
<v Nick Leeder>You have to think about how it works, not
just in maintenance, but how it works

259
00:18:38.819 --> 00:18:42.900
<v Nick Leeder>perhaps with procurement and planning and
the other teams and making sure that the

260
00:18:42.900 --> 00:18:47.209
<v Nick Leeder>scheduling and more dynamic scheduling you
can now do because you can now predict

261
00:18:47.209 --> 00:18:48.959
<v Nick Leeder>when things can fail.

262
00:18:49.219 --> 00:18:53.900
<v Nick Leeder>How do those things work together, so it's
not just a maintenance play, it's a

263
00:18:53.900 --> 00:18:56.780
<v Nick Leeder>connected play within production and
manufacturing.

264
00:18:58.680 --> 00:19:03.589
<v Nick Leeder>The next thing I've seen which is a real
man shift change is, is also a learning

265
00:19:03.589 --> 00:19:04.099
<v Nick Leeder>loops.

266
00:19:05.459 --> 00:19:10.339
<v Nick Leeder>Um, I would love to say everything in my
career I've got right first time.

267
00:19:11.369 --> 00:19:16.270
<v Nick Leeder>Um, alas, that hasn't happened, and this,
this presentation may be testament to one

268
00:19:16.270 --> 00:19:17.199
<v Nick Leeder>of those occasions.

269
00:19:17.569 --> 00:19:23.150
<v Nick Leeder>But one of the things here is that
learning loops are really, really critical.

270
00:19:23.449 --> 00:19:27.930
<v Nick Leeder>When something doesn't go right, so
perhaps you had a failure on the shop floor

271
00:19:27.930 --> 00:19:29.280
<v Nick Leeder>using predictive maintenance.

272
00:19:30.000 --> 00:19:33.180
<v Nick Leeder>Did somebody not actually pay attention to
the alert?

273
00:19:34.140 --> 00:19:35.890
<v Nick Leeder>Were the thresholds set wrong?

274
00:19:37.010 --> 00:19:38.290
<v Nick Leeder>Was there something different?

275
00:19:38.540 --> 00:19:41.020
<v Nick Leeder>Were you producing something different
that caused it to fail?

276
00:19:42.829 --> 00:19:44.939
<v Nick Leeder>So take that, take that learning.

277
00:19:45.750 --> 00:19:49.189
<v Nick Leeder>Get feedback on it and then fix it.

278
00:19:50.329 --> 00:19:54.459
<v Nick Leeder>Because that will make you better, and
that again, we talk about continuous

279
00:19:54.459 --> 00:19:55.260
<v Nick Leeder>improvement in this world.

280
00:19:56.890 --> 00:20:00.760
<v Nick Leeder>And then start bringing everybody into
that process.

281
00:20:00.979 --> 00:20:05.689
<v Nick Leeder>So on your line walks, on your uh uh that
you do, make sure that predictive

282
00:20:05.689 --> 00:20:11.329
<v Nick Leeder>maintenance, that asset health becomes
absolutely visible, get everybody involved in

283
00:20:11.329 --> 00:20:15.060
<v Nick Leeder>this, from the operators, from the
maintenance teams, all the way through also to

284
00:20:15.060 --> 00:20:16.239
<v Nick Leeder>the management teams.

285
00:20:16.619 --> 00:20:20.839
<v Nick Leeder>So everybody can build that into their
daily routines, and it then becomes

286
00:20:21.770 --> 00:20:26.469
<v Nick Leeder>institutionalized, if that's the right
word to use, in how everybody works together.

287
00:20:30.359 --> 00:20:32.000
<v Nick Leeder>So how do you start?

288
00:20:32.119 --> 00:20:33.819
<v Nick Leeder>I'm gonna throw the challenge back here.

289
00:20:34.280 --> 00:20:37.569
<v Nick Leeder>You need to become a change maker, you
want things to scale.

290
00:20:38.579 --> 00:20:40.369
<v Nick Leeder>You've gotta take the first steps
yourself.

291
00:20:41.449 --> 00:20:45.010
<v Nick Leeder>So are you on this call asking the right
questions?

292
00:20:46.089 --> 00:20:48.890
<v Nick Leeder>So what can you try differently?

293
00:20:49.819 --> 00:20:53.739
<v Nick Leeder>And using some of the things I've talked
about today, have you thought about, OK, if

294
00:20:53.739 --> 00:20:57.819
<v Nick Leeder>I thought about this and I thought about
things in a different way, how could I do

295
00:20:57.819 --> 00:21:02.979
<v Nick Leeder>this differently, how could I use this to
start scaling within what I'm doing within

296
00:21:02.979 --> 00:21:03.500
<v Nick Leeder>my plant.

297
00:21:04.209 --> 00:21:05.760
<v Nick Leeder>Perhaps even to other plants.

298
00:21:06.770 --> 00:21:08.630
<v Nick Leeder>What will be the story that you will tell?

299
00:21:09.589 --> 00:21:13.900
<v Nick Leeder>Next, What's the journey that journey,
it's not just about we did this and this is

300
00:21:13.900 --> 00:21:14.530
<v Nick Leeder>the outcome.

301
00:21:15.010 --> 00:21:18.500
<v Nick Leeder>How can you talk about this, how can you
make your champ find your champions?

302
00:21:19.920 --> 00:21:24.239
<v Nick Leeder>And what will the first step you will take
from the back of this presentation?

303
00:21:27.420 --> 00:21:28.719
<v Nick Leeder>So evolving scaling.

304
00:21:29.500 --> 00:21:34.410
<v Nick Leeder>It's hard, yeah, it's much, much harder
than starting the projects off.

305
00:21:35.660 --> 00:21:40.420
<v Nick Leeder>So We talked about it a second ago, but
you need to communicate that why.

306
00:21:41.650 --> 00:21:47.209
<v Nick Leeder>That why isn't just about the time and the
money, it's about making it personal to

307
00:21:47.209 --> 00:21:50.380
<v Nick Leeder>the people that it impacts in predictive
maintenance.

308
00:21:50.729 --> 00:21:55.770
<v Nick Leeder>So make that why about actually winning
the time, getting control back of their

309
00:21:55.770 --> 00:22:01.280
<v Nick Leeder>time, being proactive and fixing things
rather than just constantly firefighting.

310
00:22:01.770 --> 00:22:04.469
<v Nick Leeder>These are such an emotional connections.

311
00:22:04.920 --> 00:22:09.689
<v Nick Leeder>That combined with the financial benefits
of predictive maintenance, really get you

312
00:22:09.689 --> 00:22:11.630
<v Nick Leeder>to scale within the business.

313
00:22:12.920 --> 00:22:16.290
<v Nick Leeder>I talked about this a lot and I'm gonna
keep going on about it, hanging on about it.

314
00:22:16.770 --> 00:22:18.750
<v Nick Leeder>Celebrate success.

315
00:22:19.410 --> 00:22:25.910
<v Nick Leeder>Make sure that wins are recognized, wins
are publicized, and the people

316
00:22:25.910 --> 00:22:29.989
<v Nick Leeder>involved in those wins are recognized
through it as well.

317
00:22:31.750 --> 00:22:35.329
<v Nick Leeder>And that helps this point here, which is
about building the culture.

318
00:22:35.719 --> 00:22:41.640
<v Nick Leeder>When we talked about being curious,
getting the visibility but not being afraid of

319
00:22:41.640 --> 00:22:46.359
<v Nick Leeder>it, also recognizing that you don't get
everything right first time and actually

320
00:22:46.359 --> 00:22:51.880
<v Nick Leeder>showing how you're improving things,
that's the culture that will allow you to scale

321
00:22:51.880 --> 00:22:53.800
<v Nick Leeder>predictive maintenance within your
facility.

322
00:22:54.839 --> 00:23:00.489
<v Nick Leeder>And that allows you to take pilots of
predictive maintenance or very small deploy um

323
00:23:01.390 --> 00:23:06.239
<v Nick Leeder>deployments of predictive maintenance and
drive them to scale within your plant or

324
00:23:06.239 --> 00:23:07.560
<v Nick Leeder>even further afield.

325
00:23:09.489 --> 00:23:12.550
<v Nick Leeder>Thank you very much, I'm open to any uh
questions now.

326
00:23:19.939 --> 00:23:20.540
<v Speaker 2>Thank you, Nick.

327
00:23:20.739 --> 00:23:23.109
<v Speaker 2>That was really good, really interesting,
um.

328
00:23:24.050 --> 00:23:27.890
<v Speaker 2>So we, we have a couple of questions in
the chat, but I thought I'd start cos I've,

329
00:23:27.959 --> 00:23:31.349
<v Speaker 2>I've written down a couple of questions
myself, um, just to get us started.

330
00:23:31.979 --> 00:23:37.060
<v Speaker 2>Um, in terms of your, your background, so
we went straight into the, you know, nuts

331
00:23:37.060 --> 00:23:39.660
<v Speaker 2>and bolts of the present, so, but I think
we would be really interested to hear

332
00:23:39.660 --> 00:23:43.020
<v Speaker 2>what, what your background, what your
personal experiences are working on these

333
00:23:43.020 --> 00:23:46.119
<v Speaker 2>projects and advising all, you know,
various organizations on that.

334
00:23:46.260 --> 00:23:48.760
<v Speaker 2>Is there anything you can draw on your own
personal insight?

335
00:23:48.939 --> 00:23:54.260
<v Nick Leeder>So, look, I, I, I've spent 30 years,
almost 30 years, you, you, you probably can

336
00:23:54.260 --> 00:23:57.099
<v Nick Leeder>tell by the slightly thinning top and gray
hair, but.

337
00:23:57.459 --> 00:24:02.260
<v Nick Leeder>Um, I've always worked at the intersection
of technology and business, but on the

338
00:24:02.260 --> 00:24:05.119
<v Nick Leeder>business side of things in engineering and
manufacturing.

339
00:24:05.540 --> 00:24:11.010
<v Nick Leeder>So in my career I've run production
production lines, I've moved, uh, production and

340
00:24:11.010 --> 00:24:16.739
<v Nick Leeder>out uh offshored production, and I've
worked for companies such as, um, SKF and

341
00:24:16.739 --> 00:24:21.780
<v Nick Leeder>Dyson, where I've owned these
transformations at corporate level, you know, at SKF

342
00:24:21.780 --> 00:24:26.020
<v Nick Leeder>there's 113 factories across 44 different
countries.

343
00:24:26.589 --> 00:24:33.349
<v Nick Leeder>Um, so I, I've been really at the
forefront of getting manufacturing

344
00:24:33.349 --> 00:24:38.030
<v Nick Leeder>businesses to do something different, to
use technology but to scale it.

345
00:24:38.750 --> 00:24:44.229
<v Nick Leeder>So that experience coupled with, I've
worked uh as a consultant, and I still do work

346
00:24:44.229 --> 00:24:48.989
<v Nick Leeder>independently as a consultant, um, and I,
I've, I've worked for techno other

347
00:24:48.989 --> 00:24:50.849
<v Nick Leeder>technology companies in this space.

348
00:24:51.229 --> 00:24:55.290
<v Nick Leeder>I've really got a detailed understanding
of the manufacturing operating environment

349
00:24:55.599 --> 00:24:58.689
<v Nick Leeder>as well as predict things like predictive
maintenance.

350
00:24:59.030 --> 00:25:04.160
<v Nick Leeder>Um, and it drives me crazy in my, in what
I do today when I just hear so many

351
00:25:04.160 --> 00:25:06.189
<v Nick Leeder>industry 4 buzzwords that are flying
around.

352
00:25:06.550 --> 00:25:10.060
<v Nick Leeder>I'm sure everybody's got hold of Industry
5 now as well because they couldn't

353
00:25:10.060 --> 00:25:12.969
<v Nick Leeder>implement Industry 4, so we've moved on a
digit already.

354
00:25:13.510 --> 00:25:18.250
<v Nick Leeder>Um, you know, we're all in the, um, AI,
um, golden age right now.

355
00:25:18.670 --> 00:25:23.729
<v Nick Leeder>So, you know, all these buzzwords,
actually, it's always about, can you make things

356
00:25:24.030 --> 00:25:24.630
<v Nick Leeder>safely.

357
00:25:25.560 --> 00:25:31.319
<v Nick Leeder>On time, to quantity and profitably, and
things like predictive maintenance really

358
00:25:31.319 --> 00:25:32.520
<v Nick Leeder>have a profound effect.

359
00:25:32.920 --> 00:25:39.339
<v Nick Leeder>So what in the work I do now, I work with
manufacturers across the world, from some

360
00:25:39.339 --> 00:25:45.020
<v Nick Leeder>very, very big multinational businesses to
actually some less than kind of 50 person

361
00:25:45.400 --> 00:25:49.839
<v Nick Leeder>manufacturing startups, where I help them
understand what technology can actually

362
00:25:49.839 --> 00:25:51.300
<v Nick Leeder>bring to their organization.

363
00:25:51.790 --> 00:25:57.310
<v Nick Leeder>The value and help guide them and coach
them, I call it co-pilot them, to get them

364
00:25:57.310 --> 00:26:02.270
<v Nick Leeder>to value, not to technology deployment,
but to value, and that's a very different

365
00:26:02.670 --> 00:26:06.270
<v Nick Leeder>piece and that's why scaling for something
like predictive maintenance is really

366
00:26:06.270 --> 00:26:06.630
<v Nick Leeder>important.

367
00:26:08.170 --> 00:26:09.469
<v Speaker 2>Excellent, excellent.

368
00:26:09.969 --> 00:26:14.969
<v Speaker 2>Um, and if we, if we go into the chats,
there's a question here about, um, Siemens's

369
00:26:14.969 --> 00:26:18.209
<v Speaker 2>approach to predictive maintenance, and I
don't think, um, we need to go

370
00:26:18.209 --> 00:26:21.359
<v Speaker 2>specifically into that, but maybe we could
have a slightly different angle on it.

371
00:26:21.410 --> 00:26:24.650
<v Speaker 2>So you, you mentioned you talked to, you
know, large multinationals and, you know,

372
00:26:24.849 --> 00:26:25.839
<v Speaker 2>smaller customers.

373
00:26:25.910 --> 00:26:30.160
<v Speaker 2>What, where does the approach to
predictive maintenance differ from your

374
00:26:30.160 --> 00:26:30.829
<v Speaker 2>perspective?

375
00:26:31.949 --> 00:26:37.520
<v Nick Leeder>Um, Well, traditionally, you know,
maintenance is a, the lowest level is brake fix,

376
00:26:37.599 --> 00:26:41.400
<v Nick Leeder>yeah, we keep running it until something
breaks and then we repair it or we swap it.

377
00:26:42.199 --> 00:26:44.760
<v Nick Leeder>Then companies have evolved to planned
maintenance.

378
00:26:44.839 --> 00:26:48.829
<v Nick Leeder>The problem with planned maintenance is
you're probably over maintaining or under

379
00:26:48.829 --> 00:26:50.439
<v Nick Leeder>maintaining on that basis.

380
00:26:51.140 --> 00:26:55.199
<v Nick Leeder>And companies realize that that that
evolution of the maintenance journey is kind of

381
00:26:55.300 --> 00:27:00.219
<v Nick Leeder>inefficient, and that's driven them to
say, well, look, how can we be more efficient

382
00:27:00.219 --> 00:27:01.140
<v Nick Leeder>with maintenance?

383
00:27:01.420 --> 00:27:05.520
<v Nick Leeder>It's a cost, quite often it's actually
seen as a cost to the business, not a benefit

384
00:27:06.180 --> 00:27:06.920
<v Nick Leeder>to the business.

385
00:27:07.300 --> 00:27:11.020
<v Nick Leeder>And I see a lot of companies start that
journey of, well, let's do a couple of

386
00:27:11.020 --> 00:27:15.040
<v Nick Leeder>machines, let's put it on and let's bleed
it, that's skepticism I talked about

387
00:27:15.540 --> 00:27:16.140
<v Nick Leeder>earlier on.

388
00:27:16.890 --> 00:27:21.329
<v Nick Leeder>Um, so a lot of companies start that
journey off by going, well, look, we'll choose

389
00:27:21.329 --> 00:27:21.900
<v Nick Leeder>a platform.

390
00:27:22.650 --> 00:27:26.239
<v Nick Leeder>Um, we're here today with Siemens, that's
one of the many platforms out there.

391
00:27:26.660 --> 00:27:31.079
<v Nick Leeder>Uh, and we'll, we'll start measuring and
we'll start understanding, and does it help

392
00:27:31.079 --> 00:27:32.380
<v Nick Leeder>me stop things breaking?

393
00:27:33.359 --> 00:27:36.959
<v Nick Leeder>The problem is it always feels a little
bit like an insurance policy, isn't it?

394
00:27:37.530 --> 00:27:43.369
<v Nick Leeder>Because you stop something breaking, it
didn't break, therefore you didn't really

395
00:27:43.369 --> 00:27:46.189
<v Nick Leeder>have a cost, you avoided a cost, and
that's an insurance.

396
00:27:47.270 --> 00:27:52.910
<v Nick Leeder>Um, and I think that's where actually
understanding that time, you know, 80% of

397
00:27:52.910 --> 00:27:55.989
<v Nick Leeder>companies don't actually understand the
cost of downtime, so the true cost of

398
00:27:55.989 --> 00:27:56.589
<v Nick Leeder>downtime.

399
00:27:57.069 --> 00:28:02.000
<v Nick Leeder>Uh, and, and the cost of downtime, you
know, it, it's interesting, I, I, I, I, I was

400
00:28:02.030 --> 00:28:07.369
<v Nick Leeder>doing something the other week and it's
like, I know 11 facility, um, saved

401
00:28:07.449 --> 00:28:09.969
<v Nick Leeder>2700 hours.

402
00:28:11.030 --> 00:28:17.969
<v Nick Leeder>The downtime 2700 hours, that equated to
11.4 million of

403
00:28:17.969 --> 00:28:22.400
<v Nick Leeder>benefit to the business, because the
downtime itself wasn't really the cost, and

404
00:28:22.400 --> 00:28:25.030
<v Nick Leeder>this is why the Burger's is quite
important.

405
00:28:25.449 --> 00:28:29.630
<v Nick Leeder>The downtime wasn't the cost of um OK, we
had to put a new pump on.

406
00:28:29.890 --> 00:28:31.329
<v Nick Leeder>That's the cost in maintenance, yeah?

407
00:28:32.579 --> 00:28:34.959
<v Nick Leeder>Yeah, it's the maintenance cost of how
much labor was involved.

408
00:28:35.579 --> 00:28:40.339
<v Nick Leeder>The real cost is actually you couldn't
produce anything in that time.

409
00:28:41.020 --> 00:28:44.339
<v Nick Leeder>Therefore you had product, and if you're
working in a capacity constrained

410
00:28:44.339 --> 00:28:48.260
<v Nick Leeder>environment, you couldn't produce product
you needed to sell, perhaps you, you

411
00:28:48.260 --> 00:28:51.599
<v Nick Leeder>failed on OTIP, there's a, a downstream
effect of this.

412
00:28:52.380 --> 00:28:55.579
<v Nick Leeder>So it's understanding that, you know, that
connection I talked about as well.

413
00:28:55.939 --> 00:28:59.920
<v Nick Leeder>Understanding the true cost is what starts
that process off.

414
00:29:02.300 --> 00:29:02.869
<v Speaker 2>Excellent.

415
00:29:03.069 --> 00:29:07.910
<v Speaker 2>Um, and actually related to that, um, and
by the way, we've got about 5 minutes left

416
00:29:07.910 --> 00:29:11.069
<v Speaker 2>for questions as well, so if anyone's got
any questions now, please put them in the

417
00:29:11.069 --> 00:29:13.670
<v Speaker 2>chat and we'll, um, we can prioritize
them.

418
00:29:14.189 --> 00:29:18.910
<v Speaker 2>Um, we, we actually have a question about,
um, what would you do during or before a

419
00:29:18.910 --> 00:29:22.150
<v Speaker 2>pilot in order to be ready to scale
efficiently, efficiently, sorry.

420
00:29:22.349 --> 00:29:26.890
<v Speaker 2>So, what, how do you lay the groundwork
for scaling, I guess is one way to put it.

421
00:29:27.469 --> 00:29:27.849
<v Nick Leeder>Well.

422
00:29:29.300 --> 00:29:35.709
<v Nick Leeder>Why pilot, let's look at why pilots fail,
and then we'll turn the question around

423
00:29:35.709 --> 00:29:36.060
<v Nick Leeder>perhaps.

424
00:29:36.869 --> 00:29:40.599
<v Nick Leeder>Um, I, I've worked, uh, as I said, I, I've
worked in the technology space in

425
00:29:40.599 --> 00:29:44.489
<v Nick Leeder>manufacturing and engineering, I've seen
pilots, and we, we all hear this phrase

426
00:29:44.489 --> 00:29:45.859
<v Nick Leeder>called pilot purgatory.

427
00:29:46.729 --> 00:29:50.020
<v Nick Leeder>Which is, we've got Pillot, we prove value
but we never scale it.

428
00:29:50.290 --> 00:29:52.890
<v Nick Leeder>And the, the question you have to ask is
why?

429
00:29:53.819 --> 00:29:58.099
<v Nick Leeder>Now, obviously we've got the
organizational barriers I talked about as well.

430
00:29:58.219 --> 00:30:02.500
<v Nick Leeder>These are often some of the biggest
challenges which drive you, but that's, that's

431
00:30:02.500 --> 00:30:05.660
<v Nick Leeder>kind of, you get really into that during
the pilot.

432
00:30:06.920 --> 00:30:13.020
<v Nick Leeder>The problem I often see is you start the
pilot on something that won't scale itself.

433
00:30:14.050 --> 00:30:19.729
<v Nick Leeder>So, you know Rather than choosing that
same compressor or the same fan or the same

434
00:30:19.729 --> 00:30:23.260
<v Nick Leeder>pump, which you have 30 of in your
facility, and you've standardized across your

435
00:30:23.260 --> 00:30:28.109
<v Nick Leeder>other 10 facilities, they'll choose
something that they know is easy.

436
00:30:29.420 --> 00:30:33.300
<v Nick Leeder>But it's actually a use case that doesn't
exist anywhere else, it's, or maybe only

437
00:30:33.300 --> 00:30:34.560
<v Nick Leeder>exists one or two times.

438
00:30:35.140 --> 00:30:40.619
<v Nick Leeder>So one of the first things that I, I would
look at is, what, what are the assets

439
00:30:40.619 --> 00:30:45.680
<v Nick Leeder>that are worth sensorizing, that's, and
we'll come on to that in a second actually.

440
00:30:46.099 --> 00:30:50.209
<v Nick Leeder>Um, and which, and how often do we use
them, how many of them are there?

441
00:30:50.579 --> 00:30:54.219
<v Nick Leeder>Because that is the route to scale, you
set your path to scathing from the

442
00:30:54.219 --> 00:30:54.459
<v Nick Leeder>beginning.

443
00:30:55.729 --> 00:30:59.609
<v Nick Leeder>And then the other thing is, and then I'll
come on to that is now is, which is what

444
00:30:59.609 --> 00:31:02.869
<v Nick Leeder>assets are important, you know, what are
your critical assets?

445
00:31:03.329 --> 00:31:07.489
<v Nick Leeder>I often also hear that people look at the
bottlenecks in the, in the production line

446
00:31:07.489 --> 00:31:09.089
<v Nick Leeder>and use that as the basis.

447
00:31:09.530 --> 00:31:14.170
<v Nick Leeder>And it isn't, it could be that one fan
that isn't actually on the production line

448
00:31:14.170 --> 00:31:17.119
<v Nick Leeder>but maybe uh connected to your hedgeVAC
systems.

449
00:31:17.489 --> 00:31:19.589
<v Nick Leeder>But if that goes down, you have to stop
production.

450
00:31:19.849 --> 00:31:23.930
<v Nick Leeder>It's not a critical process step, it's a
supporting thing.

451
00:31:24.800 --> 00:31:31.619
<v Nick Leeder>So what are those critical assets that are
essential for you to keep running,

452
00:31:32.079 --> 00:31:38.260
<v Nick Leeder>and if they go down, it's either really
costly or time, you know, costly to replace

453
00:31:38.260 --> 00:31:42.520
<v Nick Leeder>or timely to replace, either it's a long
lead time to replace it, or you have to

454
00:31:42.520 --> 00:31:45.439
<v Nick Leeder>keep it a spare part on the shelf, so.

455
00:31:46.650 --> 00:31:50.479
<v Nick Leeder>Looking at those variables, there's a cost
element, there's a criticality element,

456
00:31:50.859 --> 00:31:53.060
<v Nick Leeder>but there's also a, a, a volume element.

457
00:31:54.709 --> 00:32:01.469
<v Nick Leeder>And then I would also get your, your
supplier involved early on in that

458
00:32:01.469 --> 00:32:03.170
<v Nick Leeder>change management journey as well.

459
00:32:04.170 --> 00:32:07.650
<v Nick Leeder>So, you know, in this, let's let's keep
the context in terms of Siemens, you know,

460
00:32:07.770 --> 00:32:12.569
<v Nick Leeder>if you're doing Siemens here, get them
involved in that journey, help them to start

461
00:32:12.569 --> 00:32:17.930
<v Nick Leeder>winning over the hearts and minds of
people, because they can show you the teams

462
00:32:17.930 --> 00:32:21.170
<v Nick Leeder>that get involved, the maintenance teams,
what this would look like, what would be

463
00:32:21.170 --> 00:32:24.339
<v Nick Leeder>the benefits before you've actually
deployed it.

464
00:32:24.650 --> 00:32:29.869
<v Nick Leeder>So you start that change journey and you
start addressing, you start understanding.

465
00:32:30.300 --> 00:32:34.750
<v Nick Leeder>Some of the skepticisms and some of those
barriers before you start the pilot.

466
00:32:37.469 --> 00:32:38.589
<v Speaker 2>Fantastic, thank you, Nick.

467
00:32:38.699 --> 00:32:43.670
<v Speaker 2>Um, I think we have, we have one time for
one more question that's just, um, that's

468
00:32:43.670 --> 00:32:44.729
<v Speaker 2>just popped in.

469
00:32:45.229 --> 00:32:48.829
<v Speaker 2>um, I might have to make it very quick cos
we are running short time, so in your

470
00:32:48.829 --> 00:32:53.069
<v Speaker 2>experience, in your experience, why do
maintenance and operation leaders rarely

471
00:32:53.069 --> 00:32:57.069
<v Speaker 2>quantify the opportunity cost of downtime
in financial terms?

472
00:32:58.079 --> 00:33:02.099
<v Speaker 2>Um, yeah, and who should actually own that
responsibility in an organization.

473
00:33:03.250 --> 00:33:08.010
<v Nick Leeder>So there's there's two things, I, I, I
think first of all, actually there's one

474
00:33:08.010 --> 00:33:08.209
<v Nick Leeder>thing.

475
00:33:09.000 --> 00:33:13.359
<v Nick Leeder>Their KPIs, which is could be OEE could be
unplanned downtime.

476
00:33:14.150 --> 00:33:18.099
<v Nick Leeder>That's their measure, they're typically
measured on a a a value and hours or

477
00:33:18.099 --> 00:33:19.729
<v Nick Leeder>percentage on those sort of things, yeah?

478
00:33:20.670 --> 00:33:27.030
<v Nick Leeder>That KPI very rarely, that's an
operational KPI that very rarely gets translated

479
00:33:27.030 --> 00:33:30.540
<v Nick Leeder>into financial KPIs at board level, at CFO
level.

480
00:33:31.079 --> 00:33:37.130
<v Nick Leeder>So what I see a lot is a disconnect
between operational KPIs which are 100% valid,

481
00:33:37.479 --> 00:33:42.520
<v Nick Leeder>but a true connection to the financial
implication, um, further upstream.

482
00:33:42.800 --> 00:33:46.630
<v Nick Leeder>And that's a disconnect often that's
happening between financial KPIs and

483
00:33:46.630 --> 00:33:47.459
<v Nick Leeder>operational KPIs.

484
00:33:47.599 --> 00:33:48.079
<v Nick Leeder>There you go.

485
00:33:48.900 --> 00:33:52.920
<v Speaker 2>Fantastic, I'm right, right on cue as
well, Nick, so that's fantastic.

486
00:33:53.380 --> 00:33:55.979
<v Speaker 2>Um, but yeah, thank you so much for your
presentation, Nick.

487
00:33:56.170 --> 00:33:57.780
<v Speaker 2>All of your contact details are on the
screen.

488
00:33:57.859 --> 00:34:01.500
<v Speaker 2>I think we're gonna share some links in
the chat as well, and we'll do that in a

489
00:34:01.500 --> 00:34:01.839
<v Speaker 2>second.

490
00:34:03.550 --> 00:34:08.510
<v Speaker 1>Please like and subscribe on all major
podcast channels and find out more about

491
00:34:08.510 --> 00:34:12.030
<v Speaker 1>Sensei predictive maintenance at
Siemens.com.
