WEBVTT
Language: en-US

1
00:00:01.320 --> 00:00:06.199
<v Nick Leeder>I work at that difficult intersection
between technology and the processes that are

2
00:00:06.199 --> 00:00:10.779
<v Nick Leeder>used, and I sit on the process side more
than the technology, so I look at how

3
00:00:10.779 --> 00:00:15.470
<v Nick Leeder>technologies can be employed in
manufacturing processes to create more value,

4
00:00:15.880 --> 00:00:20.680
<v Nick Leeder>increase productivity, increase
profitability of margins, and I work all the way

5
00:00:20.680 --> 00:00:25.479
<v Nick Leeder>from companies in Formula One all the way
down through to smaller SMEs in the

6
00:00:25.479 --> 00:00:26.500
<v Nick Leeder>hydrogen sector.

7
00:00:27.139 --> 00:00:33.349
<v Nick Leeder>Um, and large multinationals, so my
interest is really at that intersection of

8
00:00:33.349 --> 00:00:37.990
<v Nick Leeder>how technology can add value to a
business, particularly in manufacturing.

9
00:00:39.689 --> 00:00:44.900
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens, and now your host, Nel

10
00:00:44.900 --> 00:00:45.450
<v Speaker 2>Sullivan.

11
00:00:47.650 --> 00:00:51.319
<v Speaker 3>Hello and welcome to the latest episode of
the Trend Section podcast.

12
00:00:51.939 --> 00:00:57.419
<v Speaker 3>Uh, really pleased to be joined once again
by, uh, Nick Leader, a, a regular on the

13
00:00:57.419 --> 00:00:57.700
<v Speaker 3>podcast.

14
00:00:57.779 --> 00:01:02.189
<v Speaker 3>I say not just a regular, but, um, I don't
know how, how many podcasts you've done

15
00:01:02.189 --> 00:01:02.490
<v Speaker 3>now, Nick.

16
00:01:02.540 --> 00:01:04.940
<v Speaker 3>I'm always trying to count with different
guests how many podcasts you've done.

17
00:01:05.139 --> 00:01:07.680
<v Nick Leeder>I must be either 3 or 4 now together.

18
00:01:08.540 --> 00:01:11.330
<v Speaker 3>Yeah, you're getting onto the leaderboard
that or the podium of, um,

19
00:01:13.650 --> 00:01:14.980
<v Nick Leeder>if there's a prize on there, yeah.

20
00:01:16.059 --> 00:01:16.220
<v Speaker 3>Exactly.

21
00:01:16.339 --> 00:01:19.860
<v Speaker 3>Maybe, maybe I should do that as, uh,
encouragement, but, uh, but no, really

22
00:01:19.860 --> 00:01:22.160
<v Speaker 3>fantastic to have you, um, back on again.

23
00:01:22.459 --> 00:01:26.220
<v Speaker 3>Um, and we'll talk about industrial AI, of
course, topic close to your heart, close

24
00:01:26.220 --> 00:01:30.980
<v Speaker 3>to our heart at Siemens as well, and it's
really to dive into your experiences about

25
00:01:30.980 --> 00:01:35.500
<v Speaker 3>why sort of industrial AI is a sort of a
broader term, why those projects sort of

26
00:01:35.500 --> 00:01:35.959
<v Speaker 3>fail.

27
00:01:36.319 --> 00:01:39.839
<v Speaker 3>What, what we could do about it, we're
gonna talk about, you know, you know, some of

28
00:01:39.839 --> 00:01:43.480
<v Speaker 3>the solutions to that, of course, for
people, anyone listening today can sort of

29
00:01:43.480 --> 00:01:47.790
<v Speaker 3>take away into their own day to day work,
but, um, but maybe Nick, cos it, it's

30
00:01:47.790 --> 00:01:51.019
<v Speaker 3>probably been a little while since you've
been on and for new listeners, uh, just a

31
00:01:51.019 --> 00:01:53.839
<v Speaker 3>little reminder of who you are, what you
do, etc.

32
00:01:55.019 --> 00:01:59.569
<v Nick Leeder>Sure, um, well what I do is a bit of a
nightmare to really explain, but ultimately,

33
00:01:59.940 --> 00:02:05.580
<v Nick Leeder>um, I, I, I work with a number of
different companies always around engineering and

34
00:02:05.580 --> 00:02:08.960
<v Nick Leeder>manufacturing of products and in the
processes themselves.

35
00:02:09.699 --> 00:02:15.820
<v Nick Leeder>And really what I do is I work at that
difficult intersection between technology and

36
00:02:15.820 --> 00:02:17.279
<v Nick Leeder>the processes that are used.

37
00:02:17.770 --> 00:02:21.490
<v Nick Leeder>And I sit on the process side more than
the technology, so I look at how

38
00:02:21.490 --> 00:02:26.119
<v Nick Leeder>technologies can be employed in
manufacturing processes to create more value,

39
00:02:26.520 --> 00:02:31.330
<v Nick Leeder>increase productivity, increase
profitability of margins, and I work all the way

40
00:02:31.330 --> 00:02:36.770
<v Nick Leeder>from companies in Formula One all the way
down to, to smaller SMEs in the hydrogen

41
00:02:36.770 --> 00:02:37.110
<v Nick Leeder>sector.

42
00:02:37.779 --> 00:02:43.979
<v Nick Leeder>Um, and to large multinationals, so my
interest is really at that intersection of

43
00:02:43.979 --> 00:02:48.660
<v Nick Leeder>how technology can add value to a
business, particularly in manufacturing.

44
00:02:50.220 --> 00:02:53.809
<v Speaker 3>Yeah, it's interesting that you said in
the sort of diversity of the businesses you,

45
00:02:53.899 --> 00:02:54.339
<v Speaker 3>you work with.

46
00:02:54.399 --> 00:02:57.300
<v Speaker 3>I mean, are there overlaps in the
conversation we're gonna have today when we talk

47
00:02:57.300 --> 00:03:01.000
<v Speaker 3>about industrial AI and the application of
AI and some of those other industries,

48
00:03:01.490 --> 00:03:04.130
<v Speaker 3>you know, what, what sort of similarities
and differences there,

49
00:03:05.190 --> 00:03:06.839
<v Nick Leeder>massively, I think, um.

50
00:03:08.330 --> 00:03:12.690
<v Nick Leeder>I mean, it, it, it, it frustrates
manufacturing companies that I work with going the

51
00:03:12.690 --> 00:03:17.110
<v Nick Leeder>business of manufacturing is actually the
same irrespective of whether you're making

52
00:03:17.110 --> 00:03:23.380
<v Nick Leeder>a one-off vehicle for a race or millions
of products or bearings every year, you

53
00:03:23.380 --> 00:03:28.080
<v Nick Leeder>know, look at my background in SKF Group,
yeah, and it's like the business of

54
00:03:28.080 --> 00:03:33.729
<v Nick Leeder>manufacturing is the same, the technology
has the same opportunity, but you need to

55
00:03:33.729 --> 00:03:36.649
<v Nick Leeder>employ the technologies and the use cases
that add the value, and that's where it

56
00:03:36.649 --> 00:03:37.070
<v Nick Leeder>differs.

57
00:03:38.000 --> 00:03:42.199
<v Nick Leeder>So, you know, I think the business is the
same, the focus is the same, they ask the

58
00:03:42.199 --> 00:03:46.520
<v Nick Leeder>same questions, but the solution is not
necessarily the same for all industries.

59
00:03:48.160 --> 00:03:53.699
<v Speaker 3>No, exactly, exactly, and I mean, so I
guess let's, let's start us off, I guess with

60
00:03:54.360 --> 00:03:59.479
<v Speaker 3>looking at why, you know, open it up, why
do industrial AI projects fail, you know,

61
00:03:59.800 --> 00:04:02.919
<v Speaker 3>and, and, and, and I guess we, a lot of
the time we talk about pilot phases because

62
00:04:02.919 --> 00:04:07.919
<v Speaker 3>a lot of these projects start off very
small to get started and do testing, but, uh,

63
00:04:07.960 --> 00:04:09.940
<v Speaker 3>maybe we could sort of mix those two
together.

64
00:04:11.119 --> 00:04:14.639
<v Nick Leeder>Well, I think it's worth taking a little
step back and saying we're in this, let's

65
00:04:14.639 --> 00:04:17.369
<v Nick Leeder>call it a halo moment for AI.

66
00:04:17.919 --> 00:04:22.359
<v Nick Leeder>Where if you're not mentioning AI in a
conversation with a client, you're all or in

67
00:04:22.359 --> 00:04:26.479
<v Nick Leeder>a manufacturing in a meeting now with
leaders, you're almost irrelevant, which is

68
00:04:26.479 --> 00:04:31.868
<v Nick Leeder>real absolute real shame because there are
many things we can do that don't require

69
00:04:31.868 --> 00:04:35.079
<v Nick Leeder>AI that increase productivity and I'm sure
we'll come onto some of those

70
00:04:35.079 --> 00:04:36.699
<v Nick Leeder>conversations today.

71
00:04:37.009 --> 00:04:43.398
<v Nick Leeder>Um, and also at the same time, there's a
lot of headline grabbing pieces of work

72
00:04:43.398 --> 00:04:44.058
<v Nick Leeder>that go out.

73
00:04:44.459 --> 00:04:49.899
<v Nick Leeder>That create this uh excitement around AI
and at the same time disillusionment.

74
00:04:50.739 --> 00:04:56.299
<v Nick Leeder>So you know, I, I can't, you know, I think
not a week goes by where Nvidia are not

75
00:04:56.299 --> 00:05:01.059
<v Nick Leeder>having another announcement of a
relationship that they're building around AI, um.

76
00:05:01.850 --> 00:05:04.649
<v Nick Leeder>You know, I think there's every company in
the world is currently now a partner of

77
00:05:04.649 --> 00:05:08.089
<v Nick Leeder>Nvidia, you know, so everybody's going,
we've gotta be part of this because

78
00:05:08.089 --> 00:05:08.920
<v Nick Leeder>everybody else is.

79
00:05:09.290 --> 00:05:11.549
<v Nick Leeder>So you've got that fear of missing out
moment.

80
00:05:12.329 --> 00:05:15.589
<v Nick Leeder>And I, I, I won't use acronyms, but we all
know what the acronym is there.

81
00:05:15.970 --> 00:05:22.220
<v Nick Leeder>But at the same time, you know, within
like days of that, uh, MIT put out a report

82
00:05:22.220 --> 00:05:27.170
<v Nick Leeder>that says 90% plus of AI AI projects are
failing.

83
00:05:27.850 --> 00:05:31.910
<v Nick Leeder>So you've kind of got this strange world
we're living in, it's, it's the perfect

84
00:05:31.910 --> 00:05:36.600
<v Nick Leeder>hype curve we're we're going through,
where you've got the excitement of the halo uh

85
00:05:37.720 --> 00:05:41.850
<v Nick Leeder>opportunity that comes from AI but at the
same time the reality is very, very

86
00:05:41.850 --> 00:05:42.670
<v Nick Leeder>different on the ground.

87
00:05:43.910 --> 00:05:50.260
<v Nick Leeder>And um I think that is probably one of the
root causes of why

88
00:05:50.480 --> 00:05:55.320
<v Nick Leeder>AI projects are not moving beyond pilot
pilot phases, because everybody's jumping in

89
00:05:55.320 --> 00:05:56.089
<v Nick Leeder>with 2 ft.

90
00:05:57.040 --> 00:06:00.549
<v Nick Leeder>They're jumping in 2 ft and going, well,
we've got to do an AI project, there's a

91
00:06:00.549 --> 00:06:01.799
<v Nick Leeder>relevance question there.

92
00:06:02.790 --> 00:06:07.049
<v Nick Leeder>Um, and then you go, OK, we're gonna do
this on this one thing.

93
00:06:08.739 --> 00:06:13.100
<v Nick Leeder>And that one thing, it may or may not
solve the problem, but the problem is that's

94
00:06:13.100 --> 00:06:15.059
<v Nick Leeder>not repeatable, it's not scalable.

95
00:06:15.299 --> 00:06:20.019
<v Nick Leeder>They've not stood back and said in this
process in this factory, we do it 50 times,

96
00:06:20.140 --> 00:06:25.779
<v Nick Leeder>we do it 20 times a day, or we may do, uh,
we may have 5 factories with the same

97
00:06:25.779 --> 00:06:28.119
<v Nick Leeder>process in there with pretty similar
setups.

98
00:06:29.029 --> 00:06:32.000
<v Nick Leeder>Um, what are the opportunities to use AI?

99
00:06:32.149 --> 00:06:35.429
<v Nick Leeder>Where will it create value, and then let's
focus in on that.

100
00:06:35.510 --> 00:06:40.609
<v Nick Leeder>They're jumping in almost kind of straight
into proving AI works.

101
00:06:41.109 --> 00:06:45.429
<v Nick Leeder>And I'm sure we're gonna go into, there
are I think some preconditions that we need

102
00:06:45.429 --> 00:06:47.790
<v Nick Leeder>to establish before AI becomes relevant.

103
00:06:48.750 --> 00:06:50.299
<v Nick Leeder>So, you know, um.

104
00:06:51.130 --> 00:06:57.549
<v Nick Leeder>A great example is Rockwell came out this
year, you know, 60%, nearly what, 56% of

105
00:06:57.970 --> 00:07:01.130
<v Nick Leeder>companies are piloting smart
manufacturing.

106
00:07:02.440 --> 00:07:04.630
<v Nick Leeder>But only 20% are using it at scale.

107
00:07:05.619 --> 00:07:11.459
<v Nick Leeder>So to show something's working and then to
prove it a scale are very, very different

108
00:07:11.459 --> 00:07:12.799
<v Nick Leeder>gigs, um.

109
00:07:13.880 --> 00:07:18.959
<v Nick Leeder>And the global Lighthouse Network, uh,
approach from the World Economic Forum, you

110
00:07:18.959 --> 00:07:22.149
<v Nick Leeder>know, they start, the people need to start
thinking and they're recommending,

111
00:07:22.160 --> 00:07:29.109
<v Nick Leeder>thinking of assets use case, use cases, so
things can be reused and not rebuilt

112
00:07:29.109 --> 00:07:29.869
<v Nick Leeder>every time.

113
00:07:30.119 --> 00:07:34.640
<v Nick Leeder>And again that's another flaw I think
we've got with AI is we're kind of going in,

114
00:07:34.799 --> 00:07:37.679
<v Nick Leeder>proving it, but then we go, OK, but it
won't work here, it won't do this because of

115
00:07:37.679 --> 00:07:38.320
<v Nick Leeder>X, Y and Z.

116
00:07:39.070 --> 00:07:44.209
<v Nick Leeder>And I think there are fundamental
preconditions that perhaps are being overlooked

117
00:07:44.269 --> 00:07:48.329
<v Nick Leeder>that are are probably why AI is not at
scale yet.

118
00:07:50.279 --> 00:07:54.450
<v Speaker 3>So is it a case of sort of going in and
thinking about this, this small problem

119
00:07:54.450 --> 00:07:58.329
<v Speaker 3>here, or is it being distracted by lots of
all the different use cases for AI I'm

120
00:07:58.329 --> 00:08:01.309
<v Speaker 3>thinking where to start first, or
spreading yourself too thin, I've got to do

121
00:08:01.869 --> 00:08:04.600
<v Speaker 3>everything at once, but end up spreading
yourself too thin.

122
00:08:05.170 --> 00:08:10.929
<v Nick Leeder>Well, we do see this problem of, uh,
motion versus progress, uh, illusion that

123
00:08:10.929 --> 00:08:11.709
<v Nick Leeder>happens a lot.

124
00:08:12.329 --> 00:08:15.970
<v Nick Leeder>So I, I've recently talked about this in a
couple of, uh, presentations I've given

125
00:08:16.369 --> 00:08:17.769
<v Nick Leeder>where, you know.

126
00:08:18.660 --> 00:08:22.839
<v Nick Leeder>There are the, the ability to spin up 50
projects is quite easy.

127
00:08:23.459 --> 00:08:27.519
<v Nick Leeder>To actually see progress against 50
projects is very hard.

128
00:08:28.059 --> 00:08:32.179
<v Nick Leeder>So what you've got right now is that
there's a lot of motion to do stuff, but

129
00:08:32.179 --> 00:08:33.250
<v Nick Leeder>progress is pretty hard.

130
00:08:33.500 --> 00:08:37.539
<v Nick Leeder>And then progress, if you're not making
progress, things get killed quite quickly.

131
00:08:38.338 --> 00:08:42.708
<v Nick Leeder>Or sometimes don't, which is actually
another problem, but, um, so there's illusion,

132
00:08:43.109 --> 00:08:47.508
<v Nick Leeder>disillusion there, um, that or illusion
that we're creating or if we're doing more

133
00:08:47.508 --> 00:08:51.318
<v Nick Leeder>things we're we're moving forward and
we're not actually doing that.

134
00:08:51.789 --> 00:08:56.059
<v Nick Leeder>I, I think also from a frontline workers'
point of view, you know, they're faced,

135
00:08:56.229 --> 00:09:01.309
<v Nick Leeder>you know, in the current environment
versus say 10 years ago, they're faced with 5

136
00:09:01.309 --> 00:09:04.348
<v Nick Leeder>times the amount of change that they've
had.

137
00:09:04.559 --> 00:09:07.328
<v Nick Leeder>So there's change fatigue in the people as
well.

138
00:09:08.289 --> 00:09:13.090
<v Nick Leeder>So you've kind of got this and at the same
time because of the AI hype, we're going,

139
00:09:13.169 --> 00:09:18.280
<v Nick Leeder>we've gotta do AI and that that varies
between very big programs with grand

140
00:09:18.280 --> 00:09:23.130
<v Nick Leeder>aspirations and grand statements up here
all the way down to well we're gonna use a

141
00:09:23.130 --> 00:09:27.369
<v Nick Leeder>little bit of AI agentic AI and some SOPs
down here.

142
00:09:28.179 --> 00:09:29.809
<v Nick Leeder>And so, and it's all disconnected.

143
00:09:30.140 --> 00:09:33.820
<v Nick Leeder>There's no, a lot of companies don't
actually have a fundamental strategy with the

144
00:09:33.820 --> 00:09:34.719
<v Nick Leeder>ripple down approach.

145
00:09:35.650 --> 00:09:40.890
<v Nick Leeder>And if we get into things like the ethics
of AIs, the security questions, you know,

146
00:09:41.369 --> 00:09:44.809
<v Nick Leeder>then it becomes more complicated, but
right now I think we're really at that

147
00:09:44.809 --> 00:09:46.700
<v Nick Leeder>experimental stage still.

148
00:09:47.289 --> 00:09:47.770
<v Nick Leeder>So.

149
00:09:48.280 --> 00:09:54.919
<v Nick Leeder>You know, that, that formal approach and
the way that we can scale is missing, that

150
00:09:54.919 --> 00:09:58.349
<v Nick Leeder>question's missing because we're
experimenting and that's good, we learn from

151
00:09:58.349 --> 00:10:02.479
<v Nick Leeder>experimentation, we're not necessarily
getting value and I think that's why you get

152
00:10:02.669 --> 00:10:08.159
<v Nick Leeder>97% of Egenic AI projects are not,
according to MIT, uh, uh, are not actually

153
00:10:08.159 --> 00:10:08.960
<v Nick Leeder>proving any value.

154
00:10:11.099 --> 00:10:14.419
<v Speaker 3>And I get, I mean, some of these, yeah,
some of those stats you're sort of reading

155
00:10:14.419 --> 00:10:17.460
<v Speaker 3>off there, Nick, are really quite stark,
aren't they, you know, especially when you

156
00:10:17.460 --> 00:10:20.619
<v Speaker 3>consider the, the, the hype around AI, I
know.

157
00:10:21.719 --> 00:10:24.880
<v Speaker 3>Because the way you'd think of it, you
know, it's just perfection and everything's

158
00:10:24.880 --> 00:10:28.280
<v Speaker 3>going perfectly, and it's, I guess it's a
part of the sort of social media thing as

159
00:10:28.280 --> 00:10:32.359
<v Speaker 3>well, isn't it, that, you know,
everything's talked about in such a positive light.

160
00:10:32.640 --> 00:10:37.080
<v Speaker 3>But I guess if we dig into sort of the
reasons behind it, to me, it seems like it's

161
00:10:37.080 --> 00:10:38.130
<v Speaker 3>more than just a.

162
00:10:38.590 --> 00:10:42.739
<v Speaker 3>Simple technology issue, you know, behind
this, and we're talking like people,

163
00:10:43.270 --> 00:10:46.450
<v Speaker 3>processes, culture, and what you said
before about, you know, that gap between

164
00:10:46.710 --> 00:10:49.270
<v Speaker 3>what's being set up here and what's being
said down here.

165
00:10:49.309 --> 00:10:53.190
<v Speaker 3>So, there's this big, let's say, vacuum of
information in the middle from what

166
00:10:53.190 --> 00:10:53.780
<v Speaker 3>you've described.

167
00:10:53.830 --> 00:10:54.989
<v Speaker 3>I thought that's quite interesting.

168
00:10:56.580 --> 00:10:58.599
<v Nick Leeder>Uh, I mean, look, let's start with a bold
statement, yeah?

169
00:10:59.520 --> 00:11:03.940
<v Nick Leeder>Automating an efficient, oh sorry,
automating a broken process.

170
00:11:04.830 --> 00:11:06.400
<v Nick Leeder>Just means you break things faster.

171
00:11:08.489 --> 00:11:11.080
<v Nick Leeder>So Let's take a step back.

172
00:11:11.390 --> 00:11:16.200
<v Nick Leeder>AI requires actually processes that work.

173
00:11:16.659 --> 00:11:18.719
<v Nick Leeder>If the processes don't work.

174
00:11:19.570 --> 00:11:22.549
<v Nick Leeder>Then you're automating something that's
fundamentally flawed.

175
00:11:22.969 --> 00:11:24.289
<v Nick Leeder>You're using capability.

176
00:11:24.650 --> 00:11:28.710
<v Nick Leeder>So I think the process debt within
companies.

177
00:11:29.729 --> 00:11:34.599
<v Nick Leeder>If you're trying to put AII over it,
ultimately becomes a tax later on because it

178
00:11:34.609 --> 00:11:39.650
<v Nick Leeder>fails because the process is broken and
it's not gonna fix, let's be honest, AI will

179
00:11:39.650 --> 00:11:41.169
<v Nick Leeder>not fix a broken process.

180
00:11:41.489 --> 00:11:45.070
<v Nick Leeder>That's people with process knowledge, the
data that you need.

181
00:11:45.609 --> 00:11:48.369
<v Nick Leeder>And actually that's another key component
is that.

182
00:11:50.520 --> 00:11:56.179
<v Nick Leeder>You need to think about is the data, what
data we need to make AI actually work or

183
00:11:56.179 --> 00:11:59.059
<v Nick Leeder>your use case of AI work.

184
00:11:59.950 --> 00:12:05.429
<v Nick Leeder>Um, And obviously the process is the
precursor to getting the right data points that

185
00:12:05.429 --> 00:12:06.090
<v Nick Leeder>you need.

186
00:12:07.159 --> 00:12:12.179
<v Nick Leeder>And again, I see that manufacturing does
not suffer from a lack of data.

187
00:12:13.270 --> 00:12:19.229
<v Nick Leeder>What it suffers from is relevance of that
data and context of that data.

188
00:12:20.159 --> 00:12:25.419
<v Nick Leeder>So actually pulling that together in a way
that says right, we have a good process,

189
00:12:26.119 --> 00:12:30.919
<v Nick Leeder>we have relevant data that we trust that's
providing context.

190
00:12:31.809 --> 00:12:37.809
<v Nick Leeder>Um, I think those two things, if you don't
have those, then your AI project is

191
00:12:37.809 --> 00:12:39.909
<v Nick Leeder>ultimately going to be at risk.

192
00:12:41.349 --> 00:12:45.450
<v Nick Leeder>Um, and actually just, uh, I'm actually
gonna make a quick call out on, um, SESM in

193
00:12:45.450 --> 00:12:46.559
<v Nick Leeder>the North America.

194
00:12:47.010 --> 00:12:53.049
<v Nick Leeder>They're doing the Smart manufacturing
interoperability, uh, program process or

195
00:12:53.049 --> 00:12:53.609
<v Nick Leeder>SMIPs.

196
00:12:54.820 --> 00:13:00.700
<v Nick Leeder>Um, and I, I, I, uh, this is really
interesting for me, um, interoperability

197
00:13:00.700 --> 00:13:01.489
<v Nick Leeder>platform, sorry.

198
00:13:01.780 --> 00:13:05.979
<v Nick Leeder>So SMIP is the Smart manufacturing
interoperability platform by Sesme.

199
00:13:07.039 --> 00:13:12.109
<v Nick Leeder>And It, it looks at a number of core
capabilities and this is actually the things,

200
00:13:12.469 --> 00:13:16.549
<v Nick Leeder>this is where you've got a world of
competition and different vendors and legacy

201
00:13:17.099 --> 00:13:17.200
<v Nick Leeder>applications.

202
00:13:17.280 --> 00:13:23.000
<v Nick Leeder>By the way, this stuff is really cool on a
greenfield site site where you build from

203
00:13:23.000 --> 00:13:27.710
<v Nick Leeder>scratch, but most of us work on brownfield
sites with a legacy equipment, legacy

204
00:13:27.710 --> 00:13:28.500
<v Nick Leeder>processes, so.

205
00:13:29.219 --> 00:13:34.570
<v Nick Leeder>The the SMMIP approach looks at
connectivity, yeah, how do you get the data from the

206
00:13:34.570 --> 00:13:41.419
<v Nick Leeder>different sources, legacy machines,
systems, old historians for example, um, how

207
00:13:41.419 --> 00:13:46.159
<v Nick Leeder>that data is ingested, so how, you know,
connectivity then acquiring that together,

208
00:13:46.539 --> 00:13:51.539
<v Nick Leeder>as I mentioned a minute ago, providing the
right context in a consistent way.

209
00:13:51.820 --> 00:13:55.239
<v Nick Leeder>That context gives you ultimately a
springboard for scale.

210
00:13:55.940 --> 00:14:00.659
<v Nick Leeder>Because a motor of a certain type in one
factory, if you can then connect it and say

211
00:14:00.659 --> 00:14:05.820
<v Nick Leeder>that's the same motor in a different
factory, you've got ultimately Uber context

212
00:14:05.820 --> 00:14:07.000
<v Nick Leeder>that provides around that.

213
00:14:07.419 --> 00:14:11.460
<v Nick Leeder>You know, security of that data, the
workflows that data goes through maybe even

214
00:14:11.460 --> 00:14:15.900
<v Nick Leeder>gets enriched and how it moves between
the, you know, some of the, the systems and

215
00:14:15.900 --> 00:14:17.320
<v Nick Leeder>the OT components you've got.

216
00:14:18.830 --> 00:14:24.320
<v Nick Leeder>And doing that in a neutral way so we
establish some standards that enable AI, you

217
00:14:24.320 --> 00:14:28.479
<v Nick Leeder>know, I had a wonderful conversation with
a company called Think IQ and Doug Lawson

218
00:14:28.479 --> 00:14:33.880
<v Nick Leeder>and Paul Turner, um, the other week and it
was actually last uh last Tuesday, uh, a

219
00:14:33.880 --> 00:14:39.080
<v Nick Leeder>presentation in London they were giving,
uh, at the Quorum principle event that was

220
00:14:39.080 --> 00:14:43.440
<v Nick Leeder>really going over a little light bulb
moment going, why is that not there in

221
00:14:43.440 --> 00:14:44.119
<v Nick Leeder>manufacturing?

222
00:14:44.590 --> 00:14:48.859
<v Nick Leeder>And the problem with standards like this
is standards are like toothbrushes, yeah.

223
00:14:49.520 --> 00:14:53.320
<v Nick Leeder>Everybody agrees we need one, but nobody
wants to use anybody else's.

224
00:14:53.799 --> 00:14:57.380
<v Nick Leeder>So, um, I'll let that sink in for a
moment.

225
00:14:59.400 --> 00:15:04.479
<v Nick Leeder>Um, you know, so I think something like
that Smith initiative by SsMe is really,

226
00:15:04.559 --> 00:15:06.570
<v Nick Leeder>really important for the data and context.

227
00:15:07.270 --> 00:15:12.719
<v Nick Leeder>But actually let's get the process right
now if you've got those preconditions and

228
00:15:12.719 --> 00:15:17.280
<v Nick Leeder>you've got a workforce that doesn't feel
threatened or, you know, cos there's an,

229
00:15:17.520 --> 00:15:21.469
<v Nick Leeder>you know, the other problem with this
bubble of AI is it's a link to workforce

230
00:15:21.469 --> 00:15:22.619
<v Nick Leeder>reduction as well.

231
00:15:23.869 --> 00:15:28.479
<v Nick Leeder>Um, that doesn't feel threatened, uh,
threatened by AI, but actually sees this as an

232
00:15:28.479 --> 00:15:32.080
<v Nick Leeder>opportunity to enhance their work, and
that's your job, by the way, if you're trying

233
00:15:32.080 --> 00:15:35.929
<v Nick Leeder>to do AI projects to position that
correctly with the frontline workers.

234
00:15:36.400 --> 00:15:39.750
<v Nick Leeder>I remember we've talked about this a
couple of times before about actually buying

235
00:15:39.750 --> 00:15:42.679
<v Nick Leeder>and making the value relevant to them and
not just the boardroom.

236
00:15:43.690 --> 00:15:48.359
<v Nick Leeder>That's, that is then the right environment
that you're creating for AI projects to

237
00:15:48.359 --> 00:15:49.219
<v Nick Leeder>be successful.

238
00:15:52.070 --> 00:15:56.760
<v Speaker 3>Yeah, and I think, I think as well, it
falls into this, again, everything you,

239
00:15:56.869 --> 00:15:58.619
<v Speaker 3>you've said is, is correct.

240
00:15:59.210 --> 00:16:03.840
<v Speaker 3>It, it just makes you think a lot of the,
the projects can sometimes just be sort of

241
00:16:03.840 --> 00:16:04.919
<v Speaker 3>like, you know, theater.

242
00:16:05.039 --> 00:16:08.150
<v Speaker 3>You know, it's, it's just, uh, something
to showcase that we're, we're in

243
00:16:08.169 --> 00:16:12.880
<v Speaker 3>innovative, we're doing AI, but like you
said, without some of the fundamentals, is

244
00:16:12.880 --> 00:16:15.799
<v Speaker 3>it, is it a case that some of the
fundamentals, you know, you mentioned connectors,

245
00:16:15.840 --> 00:16:17.919
<v Speaker 3>you mentioned data, like some of that's.

246
00:16:18.780 --> 00:16:22.869
<v Speaker 3>Maybe not forgotten, but sort of being put
in the shadow a little bit, not as cool

247
00:16:22.869 --> 00:16:25.869
<v Speaker 3>at the moment because AI is here, but
those are the things that you need to have in

248
00:16:25.869 --> 00:16:29.479
<v Speaker 3>place to actually, uh, apply AI on top of
it, that's what you're saying,

249
00:16:29.590 --> 00:16:30.010
<v Nick Leeder>right?

250
00:16:30.390 --> 00:16:35.580
<v Nick Leeder>Yeah, it's the, it's the boring things you
need to get right to make the exciting

251
00:16:35.580 --> 00:16:37.190
<v Nick Leeder>things work and get value from it.

252
00:16:38.119 --> 00:16:38.479
<v Nick Leeder>Yeah.

253
00:16:39.419 --> 00:16:45.419
<v Nick Leeder>Your, your, your car, you know, you get
attracted by all the kind of sat nav and all

254
00:16:45.419 --> 00:16:50.219
<v Nick Leeder>the, the funky stuff you get inside of it,
the self-driving features, the fact I was

255
00:16:50.219 --> 00:16:55.340
<v Nick Leeder>in one the other week, it's not mine by
the way, had a cup holder that was heated

256
00:16:55.340 --> 00:16:56.260
<v Nick Leeder>and cooled.

257
00:16:57.020 --> 00:17:00.679
<v Nick Leeder>I mean, my mind's exploding, what a great
cool feature that is.

258
00:17:01.179 --> 00:17:04.140
<v Nick Leeder>I can't find, I can't think of a use case
and by the way that's a great example of

259
00:17:04.140 --> 00:17:05.260
<v Nick Leeder>like AI kicking off.

260
00:17:05.579 --> 00:17:08.380
<v Nick Leeder>Why do you need a cup holder that chills
or heats something up?

261
00:17:09.260 --> 00:17:12.670
<v Nick Leeder>But if the engine doesn't work and you
don't put oil in the engine, I'm, I'm working

262
00:17:12.670 --> 00:17:16.829
<v Nick Leeder>on combustion, not electric, uh by the
way, in my example, but yeah, if you don't

263
00:17:16.829 --> 00:17:19.890
<v Nick Leeder>put the boring thing and maintain that
engine, the car doesn't go.

264
00:17:20.189 --> 00:17:25.109
<v Nick Leeder>So yes, you get a hot cup of coffee, but
you're still stuck with where you are, and

265
00:17:25.109 --> 00:17:28.189
<v Nick Leeder>primarily the main reason why you drive a
car is to go from A to B.

266
00:17:28.969 --> 00:17:32.449
<v Nick Leeder>So if you're stuck at A but with warm
coffee, it doesn't help where you need to get

267
00:17:32.449 --> 00:17:33.449
<v Nick Leeder>to, which is to get to B.

268
00:17:34.780 --> 00:17:38.619
<v Nick Leeder>So it's always been the case with
technology, and unfortunately I've been around too

269
00:17:38.619 --> 00:17:45.140
<v Nick Leeder>long now that we forget about the boring
foundation bits and we get attracted by the

270
00:17:45.140 --> 00:17:46.150
<v Nick Leeder>shiny hype.

271
00:17:47.500 --> 00:17:53.910
<v Nick Leeder>And where I am seeing AI have value is
where it's being

272
00:17:53.910 --> 00:18:00.430
<v Nick Leeder>deployed in scalable use cases where they
spend time and effort getting the process

273
00:18:00.430 --> 00:18:00.910
<v Nick Leeder>right.

274
00:18:01.920 --> 00:18:07.800
<v Nick Leeder>Getting the data right and then the use
cases are straightforward to actually

275
00:18:07.800 --> 00:18:10.180
<v Nick Leeder>implement and people have trust.

276
00:18:10.880 --> 00:18:14.670
<v Nick Leeder>People have trust in then what the
computer says.

277
00:18:15.000 --> 00:18:19.550
<v Nick Leeder>The computer says this and we know the
process is working, the data's right, and

278
00:18:19.550 --> 00:18:21.800
<v Nick Leeder>they're able to validate what the computer
is saying.

279
00:18:23.180 --> 00:18:27.260
<v Nick Leeder>Uh, that's where I'm seeing it, so things
like predictive maintenance is actually

280
00:18:27.260 --> 00:18:29.319
<v Nick Leeder>those sort of use cases are scalable.

281
00:18:30.089 --> 00:18:35.930
<v Nick Leeder>You can provide very simple context and it
makes the workforce's lives better.

282
00:18:36.010 --> 00:18:39.310
<v Nick Leeder>They make the operators' lives better
because the machine is running more smoothly.

283
00:18:39.969 --> 00:18:44.930
<v Nick Leeder>Maintenance moves out of kind of predict
uh preventative firefighting mode and into

284
00:18:44.930 --> 00:18:47.880
<v Nick Leeder>predictive modes, yeah, for the brake fix
world they live in.

285
00:18:48.170 --> 00:18:51.709
<v Nick Leeder>So their lives improve and things happen
then from there.

286
00:18:52.369 --> 00:18:55.810
<v Nick Leeder>Importantly, there's a tangible value case
to that as well, you know, unplanned

287
00:18:55.810 --> 00:18:57.290
<v Nick Leeder>downtime is very expensive.

288
00:18:58.140 --> 00:19:02.969
<v Nick Leeder>So it's that kind of compound effect and
the environment that that creates.

289
00:19:03.380 --> 00:19:06.439
<v Nick Leeder>So we move away from the theater and we
get to the practicals, um.

290
00:19:08.739 --> 00:19:09.430
<v Nick Leeder>Yeah.

291
00:19:09.849 --> 00:19:13.459
<v Speaker 3>So, I mean, uh, I mean, maybe let's, let's
go into that a little bit then, because a

292
00:19:13.459 --> 00:19:16.810
<v Speaker 3>key component of it, you know, everything
we, we've talked about, you know, what

293
00:19:16.810 --> 00:19:20.650
<v Speaker 3>type of projects to look, look at, look at
it at scale as well, which again in a

294
00:19:20.650 --> 00:19:24.170
<v Speaker 3>predictive maintenance world's important
because we know the value of predictive

295
00:19:24.170 --> 00:19:29.079
<v Speaker 3>maintenance in a Siemens or a Sensai world
is, you know, at scale, but.

296
00:19:30.209 --> 00:19:34.489
<v Speaker 3>What are sort of the measurements
companies can put in place, I guess, to, you know,

297
00:19:34.569 --> 00:19:37.569
<v Speaker 3>to see this, and then we can start with
predictive maintenance, but of course, maybe

298
00:19:37.569 --> 00:19:41.050
<v Speaker 3>there's other use cases we could talk
about as well, but what, what type of

299
00:19:41.050 --> 00:19:43.329
<v Speaker 3>measurement could they put in place for
these types of projects?

300
00:19:44.670 --> 00:19:48.869
<v Nick Leeder>Uh, first of all, let's call out, there
are 3 measurements you need to put in place

301
00:19:48.869 --> 00:19:49.630
<v Nick Leeder>for these things.

302
00:19:50.599 --> 00:19:54.939
<v Nick Leeder>Um, And the first one is a fundamental
disconnect in most manufacturing companies.

303
00:19:55.800 --> 00:20:01.920
<v Nick Leeder>Which is the operational metrics, so
things like defects, cycle times, unplanned

304
00:20:01.920 --> 00:20:05.000
<v Nick Leeder>downtime, um, those things.

305
00:20:06.380 --> 00:20:08.630
<v Nick Leeder>Safety, let's let's let's mention safety.

306
00:20:08.790 --> 00:20:10.589
<v Nick Leeder>I can't not mention safety, but.

307
00:20:11.880 --> 00:20:13.109
<v Nick Leeder>Those things are measured.

308
00:20:13.400 --> 00:20:17.760
<v Nick Leeder>They're often though measured in
percentages or other values.

309
00:20:17.839 --> 00:20:22.369
<v Nick Leeder>Now OEE is a classic there, yeah, it's
measured as a percentage which ultimately is

310
00:20:22.369 --> 00:20:24.140
<v Nick Leeder>quite meaningless as a statement.

311
00:20:24.640 --> 00:20:28.760
<v Nick Leeder>And people will shoot me down for that
maybe, but I think a percentage of nothing is

312
00:20:28.760 --> 00:20:30.520
<v Nick Leeder>still nothing, yeah, um.

313
00:20:32.109 --> 00:20:35.829
<v Nick Leeder>And actually there's a disconnect then,
first of all between the operational KPIs

314
00:20:35.829 --> 00:20:37.489
<v Nick Leeder>and the board level KPIs.

315
00:20:38.030 --> 00:20:42.709
<v Nick Leeder>You know, the, the harder metrics, you
know, the return on, uh, assets, the net

316
00:20:42.709 --> 00:20:47.729
<v Nick Leeder>assets, yeah, those sort of things, the
EBITD statements, the financials ultimately,

317
00:20:47.869 --> 00:20:54.550
<v Nick Leeder>which we look at what was and step one is
to get metrics agreed and understood

318
00:20:54.550 --> 00:20:59.810
<v Nick Leeder>operational, but actually then establish a
very strong metric connection between

319
00:20:59.810 --> 00:21:00.270
<v Nick Leeder>that.

320
00:21:01.000 --> 00:21:04.479
<v Nick Leeder>And the board level kind of financial
metrics the business is running.

321
00:21:04.890 --> 00:21:06.069
<v Nick Leeder>Why is that important?

322
00:21:06.699 --> 00:21:10.479
<v Nick Leeder>It strengthens the value case and the
investments.

323
00:21:10.770 --> 00:21:15.290
<v Nick Leeder>So you can prove something down here, but
actually show very, very, um, very

324
00:21:15.290 --> 00:21:19.099
<v Nick Leeder>directly how that's impacting key metrics
at the board level and the board care,

325
00:21:19.109 --> 00:21:20.810
<v Nick Leeder>people care about it.

326
00:21:21.290 --> 00:21:23.560
<v Nick Leeder>And that's a good practice irrespective of
AI.

327
00:21:25.329 --> 00:21:30.339
<v Nick Leeder>But I think the 3rd metric, and I
mentioned this earlier on, is the relevance to the

328
00:21:30.349 --> 00:21:32.310
<v Nick Leeder>person doing the job.

329
00:21:33.560 --> 00:21:37.310
<v Nick Leeder>So how do you prove that their life is
getting better?

330
00:21:37.660 --> 00:21:37.670
<v Nick Leeder>Mhm.

331
00:21:39.319 --> 00:21:43.010
<v Nick Leeder>You know, and we've talked about this, uh
I think I did it in the sense I kick off

332
00:21:43.010 --> 00:21:44.969
<v Nick Leeder>earlier on in the year, but you know.

333
00:21:46.280 --> 00:21:51.160
<v Nick Leeder>The cost of 1 second's downtime is, is a
meaningless figure, even if it's in

334
00:21:51.160 --> 00:21:54.819
<v Nick Leeder>hundreds of thousands, it doesn't really
mean anything.

335
00:21:56.510 --> 00:22:01.839
<v Nick Leeder>To an operator, so change the language,
make it relevant to them, you know, as I

336
00:22:01.839 --> 00:22:06.400
<v Nick Leeder>mentioned earlier on, prove that the
maintenance team because of what you're doing,

337
00:22:06.680 --> 00:22:11.040
<v Nick Leeder>is no longer having to go in at the
weekends and do stuff, they win their weekends

338
00:22:11.040 --> 00:22:11.540
<v Nick Leeder>back.

339
00:22:12.689 --> 00:22:18.130
<v Nick Leeder>Those sort of really simple things, those
metrics are connecting operational to

340
00:22:18.130 --> 00:22:19.810
<v Nick Leeder>board, operational to people.

341
00:22:21.020 --> 00:22:25.170
<v Nick Leeder>And you create that environment when
you're starting to measure the progress you're

342
00:22:25.170 --> 00:22:29.540
<v Nick Leeder>making, the impact you're having, it makes
it actually relevant to all the

343
00:22:29.540 --> 00:22:31.739
<v Nick Leeder>stakeholders, not just some of them.

344
00:22:33.359 --> 00:22:36.719
<v Speaker 3>So actually you talk about the ending, and
that's really interesting, if you want to

345
00:22:36.719 --> 00:22:40.550
<v Speaker 3>call it measurement, but it's actually
beyond measurement, it's almost, it's

346
00:22:41.000 --> 00:22:41.680
<v Speaker 3>humanizing.

347
00:22:41.839 --> 00:22:45.880
<v Speaker 3>It's, you know, it's creating a, you know,
personal stories beyond it, which can be,

348
00:22:45.959 --> 00:22:50.670
<v Speaker 3>I guess, which is important to share
internally as part of a, you know, as part of

349
00:22:50.670 --> 00:22:54.380
<v Speaker 3>an effort to, you know, scale up, um,
projects as well.

350
00:22:55.130 --> 00:22:59.689
<v Speaker 3>So I guess that's a really effective way
to get everyone bolted internally is share

351
00:22:59.689 --> 00:23:03.689
<v Speaker 3>some of these story, personal stories, not
just the downtime metrics or the improve

352
00:23:03.689 --> 00:23:07.890
<v Speaker 3>OEE or whatever it might be, but actually
this, this person, is that, is that

353
00:23:07.890 --> 00:23:10.869
<v Speaker 3>something you sort of encourage in your
conversations with clients as well as

354
00:23:10.869 --> 00:23:12.469
<v Speaker 3>sharing the personal stories?

355
00:23:12.819 --> 00:23:12.890
<v Speaker 3>Oh,

356
00:23:12.969 --> 00:23:14.650
<v Nick Leeder>you fell for it hook a sinker, didn't you?

357
00:23:14.839 --> 00:23:16.150
<v Nick Leeder>Um, absolutely.

358
00:23:17.250 --> 00:23:18.040
<v Speaker 3>There we go,

359
00:23:18.530 --> 00:23:23.530
<v Nick Leeder>there we go, um, but it is the personal
stories that make the difference, it makes.

360
00:23:24.199 --> 00:23:26.530
<v Nick Leeder>A technology change human.

361
00:23:27.670 --> 00:23:33.819
<v Nick Leeder>And I I, I think that's so important, we
are all humans, um, believe it or not, and

362
00:23:33.959 --> 00:23:39.630
<v Nick Leeder>actually it is those stories that inspire
us that make us actually want to do

363
00:23:39.630 --> 00:23:40.540
<v Nick Leeder>something different.

364
00:23:41.040 --> 00:23:46.880
<v Nick Leeder>So the adoption question is about
inspiring people through proof that it makes their

365
00:23:46.880 --> 00:23:47.920
<v Nick Leeder>life better.

366
00:23:48.829 --> 00:23:54.170
<v Nick Leeder>And that could be the CFO's life better
because he's seen the financial metrics move

367
00:23:54.390 --> 00:23:56.020
<v Nick Leeder>in the right way he needs to.

368
00:23:56.349 --> 00:24:01.229
<v Nick Leeder>It could be the operations director
because his unplanned unplanned downtime has

369
00:24:01.229 --> 00:24:02.689
<v Nick Leeder>dropped significantly.

370
00:24:03.069 --> 00:24:05.609
<v Nick Leeder>Or it could be the maintenance engineer
winning his weekend back.

371
00:24:06.560 --> 00:24:10.989
<v Nick Leeder>And I think um all those layers are human
stories.

372
00:24:11.959 --> 00:24:17.819
<v Nick Leeder>But we tend to get absorbed in the number,
not the, the impact it has.

373
00:24:18.959 --> 00:24:24.459
<v Nick Leeder>Um, and I think the other thing here is
the relevance of stories, uh, and, and, and

374
00:24:24.459 --> 00:24:25.319
<v Nick Leeder>who's telling them.

375
00:24:26.689 --> 00:24:30.750
<v Nick Leeder>So, um, I, I recently wrote an article on
LinkedIn about um.

376
00:24:32.000 --> 00:24:36.239
<v Nick Leeder>Are we developing sat, you know, are
people capable of only reading satnavs and um

377
00:24:36.239 --> 00:24:36.969
<v Nick Leeder>or map reading?

378
00:24:37.699 --> 00:24:44.560
<v Nick Leeder>And it was actually in context of AI but
it was inspired by, um, I think a video

379
00:24:44.560 --> 00:24:50.680
<v Nick Leeder>of uh a trucker, a relatively young
trucker that's driving um driving across Europe,

380
00:24:50.939 --> 00:24:53.839
<v Nick Leeder>uh, and their their satnav broke.

381
00:24:55.770 --> 00:25:00.530
<v Nick Leeder>And they are so reliant on the satnav, but
then then they had to try and use maps,

382
00:25:00.849 --> 00:25:03.069
<v Nick Leeder>even trying to map on routes they knew.

383
00:25:04.010 --> 00:25:06.689
<v Nick Leeder>And that really resonated with me, going.

384
00:25:07.589 --> 00:25:14.349
<v Nick Leeder>But this is the world we live in in AI
today where our dependence on AI I, I use AI

385
00:25:14.349 --> 00:25:17.390
<v Nick Leeder>a lot, I use chat GPT an awful lot.

386
00:25:18.219 --> 00:25:24.319
<v Nick Leeder>But I use it in a way that I'm still the
creative spark behind it and I use it to

387
00:25:25.000 --> 00:25:27.880
<v Nick Leeder>remove procrastination that I would
normally have or write an email.

388
00:25:28.300 --> 00:25:30.780
<v Nick Leeder>How many 15 ways you can write it, but I
asked chat GPT.

389
00:25:30.819 --> 00:25:33.839
<v Nick Leeder>I've got a version which I can edit and
I'm generally happy with.

390
00:25:35.380 --> 00:25:40.619
<v Nick Leeder>But actually we, we use this as a satnav,
we get guided by these tools and we don't

391
00:25:40.619 --> 00:25:41.300
<v Nick Leeder>think enough.

392
00:25:41.500 --> 00:25:45.540
<v Nick Leeder>We're map readers, they have to memorize a
map, they have to think about the route,

393
00:25:45.650 --> 00:25:47.520
<v Nick Leeder>they have to plan that route out.

394
00:25:48.260 --> 00:25:51.780
<v Nick Leeder>It's very, very different to go on from
here to here and let the computer say what

395
00:25:51.780 --> 00:25:54.859
<v Nick Leeder>it is, and you trust, you inherently trust
the satnav.

396
00:25:55.550 --> 00:25:59.400
<v Nick Leeder>And I think when I, when I actually look
at that and reflect on that in the world of

397
00:25:59.400 --> 00:26:02.920
<v Nick Leeder>AI, you know, I, I was in a, a meeting a
couple of weeks ago, where we're going,

398
00:26:03.000 --> 00:26:08.079
<v Nick Leeder>well, actually we need more kind of data
scientists in the manufacturing sector.

399
00:26:09.250 --> 00:26:11.430
<v Nick Leeder>And I'm like going, I don't think we do.

400
00:26:12.180 --> 00:26:18.790
<v Nick Leeder>I think we need more people that
understand the process that then can apply the data

401
00:26:18.790 --> 00:26:22.969
<v Nick Leeder>science, not having data scientists who
don't know the process.

402
00:26:23.469 --> 00:26:23.540
<v Nick Leeder>Mhm.

403
00:26:24.520 --> 00:26:29.160
<v Nick Leeder>And I think that is another massive
disconnect we have and you know potentially

404
00:26:29.160 --> 00:26:34.150
<v Nick Leeder>linked to AI and why projects don't scale
is we're not, we don't trust the people

405
00:26:34.150 --> 00:26:36.410
<v Nick Leeder>who know the process, who can read the
maps.

406
00:26:36.880 --> 00:26:40.959
<v Nick Leeder>We trust the people who can program the
satnavs and expect the satnav to be the most

407
00:26:40.959 --> 00:26:41.920
<v Nick Leeder>optimal route.

408
00:26:42.239 --> 00:26:46.160
<v Nick Leeder>You know, the ultimate example of this is
the London cabbie that has to go through

409
00:26:46.160 --> 00:26:46.930
<v Nick Leeder>the knowledge.

410
00:26:47.290 --> 00:26:51.780
<v Nick Leeder>That actually that they're they're
ultimately like your uh person that's been doing

411
00:26:51.780 --> 00:26:55.500
<v Nick Leeder>manufacturing in your site for 30 years
that knows everything inside out, that

412
00:26:55.500 --> 00:27:00.140
<v Nick Leeder>doesn't have to refer to an SOP it's all
in here, but they've got the knowledge,

413
00:27:00.219 --> 00:27:02.920
<v Nick Leeder>they know all the little back routes, the
the shortcuts to take.

414
00:27:03.839 --> 00:27:07.849
<v Speaker 3>So in a way, I guess with that, that
example, what you, in an ideal world, you bring

415
00:27:07.849 --> 00:27:12.349
<v Speaker 3>the knowledge of a taxi cab or anyone who
knows routes, even in their local area,

416
00:27:12.369 --> 00:27:15.689
<v Speaker 3>from like the back of their hand and
combine that with technology like Google Maps

417
00:27:15.689 --> 00:27:18.089
<v Speaker 3>and bring the two together, then you've
got almost the perfect.

418
00:27:18.569 --> 00:27:22.890
<v Speaker 3>Products and the perfect balance between
human and, well, machine if you want to

419
00:27:22.890 --> 00:27:27.790
<v Speaker 3>call it machine, but, but human and
software and software intelligence as well.

420
00:27:28.170 --> 00:27:28.250
<v Speaker 3>I

421
00:27:28.250 --> 00:27:32.079
<v Nick Leeder>think that's but we get you, exactly, and
I think that is the, that is almost the,

422
00:27:32.130 --> 00:27:37.839
<v Nick Leeder>the, the perfect combination, but we get
attracted by the Waze or the, the satnav,

423
00:27:37.969 --> 00:27:39.229
<v Nick Leeder>there are satnavs available.

424
00:27:39.880 --> 00:27:44.089
<v Nick Leeder>But um you we get attracted by the
technology, but what we don't think about is all

425
00:27:44.089 --> 00:27:47.010
<v Nick Leeder>the knowledge that has to be put behind it
and that's when I talked about, you know,

426
00:27:47.089 --> 00:27:51.329
<v Nick Leeder>earlier on about the process being wrong
or the data being wrong and getting those

427
00:27:51.329 --> 00:27:51.810
<v Nick Leeder>things right.

428
00:27:53.380 --> 00:27:55.099
<v Speaker 3>And it, it is interesting.

429
00:27:55.170 --> 00:27:58.500
<v Speaker 3>It is interesting because depending on the
context, so you, you're right, you

430
00:27:58.500 --> 00:28:03.689
<v Speaker 3>automatically trust some, um, technologies
without even thinking about it.

431
00:28:03.699 --> 00:28:09.060
<v Speaker 3>It's just part of everyday life, whereas
introducing it into an environment like a

432
00:28:09.060 --> 00:28:13.859
<v Speaker 3>factory floor, for example, requires a lot
more understanding, knowledge, you know,

433
00:28:14.099 --> 00:28:15.500
<v Speaker 3>culture change and things like this.

434
00:28:15.619 --> 00:28:17.979
<v Speaker 3>It, it's, and there's a big difference
there, isn't there?

435
00:28:18.020 --> 00:28:18.900
<v Speaker 3>I know, you know.

436
00:28:19.209 --> 00:28:22.199
<v Speaker 3>Yeah, yeah, it's completely different
circumstances, it could be personal life

437
00:28:22.199 --> 00:28:25.780
<v Speaker 3>versus non-personal life is one example,
but I do, yeah, that's quite a fascinating.

438
00:28:26.510 --> 00:28:31.150
<v Speaker 3>But you know, look at in terms of um
technology adoption, difference there.

439
00:28:31.869 --> 00:28:37.089
<v Nick Leeder>And ultimately so it's, it's a risk reward
moment, you know.

440
00:28:37.790 --> 00:28:41.310
<v Nick Leeder>I, I, I, when I got my new car a couple of
years ago, it's not a new car anymore,

441
00:28:41.390 --> 00:28:45.160
<v Nick Leeder>but when I got my car a couple of years
ago, the, the guy that sold me and I got an

442
00:28:45.160 --> 00:28:51.150
<v Nick Leeder>electric car, he said, don't use like
Apple Maps, use the inbuilt satnav.

443
00:28:51.949 --> 00:28:56.150
<v Nick Leeder>Because actually it communicates with the
car, it knows how much battery you've got

444
00:28:56.150 --> 00:29:00.790
<v Nick Leeder>left, it will reschedule the route, it
will schedule stops that you need to make to

445
00:29:00.790 --> 00:29:01.170
<v Nick Leeder>charge.

446
00:29:02.020 --> 00:29:05.609
<v Nick Leeder>It, it's clever, it's an integrated thing
and I, I just did it.

447
00:29:05.660 --> 00:29:09.380
<v Nick Leeder>I almost just, I actually just used it
without even questioning it.

448
00:29:11.420 --> 00:29:14.140
<v Nick Leeder>And then you go, OK, what's the worst that
can happen though?

449
00:29:14.300 --> 00:29:18.500
<v Nick Leeder>I'm 5 minutes late, you know, ultimately I
probably did an extra charge I didn't

450
00:29:18.500 --> 00:29:21.719
<v Nick Leeder>need to do, but Apple Maps might have got
me there with 3%.

451
00:29:22.099 --> 00:29:24.359
<v Nick Leeder>This one I always make sure I arrive with
10%.

452
00:29:25.369 --> 00:29:29.339
<v Nick Leeder>It it's kind of, OK, the risk is
relatively low.

453
00:29:31.540 --> 00:29:36.550
<v Nick Leeder>The trust in manufacturing is if we get it
wrong, you know, you might lose some

454
00:29:36.550 --> 00:29:41.069
<v Nick Leeder>money in a process, you know, you have to
do some scrap implant, you know, the scrap

455
00:29:41.069 --> 00:29:42.369
<v Nick Leeder>because the quality comes out wrong.

456
00:29:42.869 --> 00:29:45.770
<v Nick Leeder>Worst cases, people's lives may be at
risk.

457
00:29:46.589 --> 00:29:50.989
<v Nick Leeder>So actually the game is different and
therefore our trust levels have to be much

458
00:29:50.989 --> 00:29:51.410
<v Nick Leeder>higher.

459
00:29:51.709 --> 00:29:54.020
<v Nick Leeder>The proof points need to be much more
solid.

460
00:29:54.910 --> 00:29:58.150
<v Speaker 3>No, and that, yeah, and that's completely,
yeah, you completely summed it up there.

461
00:29:58.219 --> 00:30:02.270
<v Speaker 3>The worst you'll be with, say, Google Maps
again is you might be a little bit late

462
00:30:02.270 --> 00:30:06.310
<v Speaker 3>for whatever, you know, event you're,
you're you're attending or whatever, an

463
00:30:06.310 --> 00:30:08.890
<v Speaker 3>inconvenience in the grand scheme of
things.

464
00:30:08.989 --> 00:30:10.089
<v Speaker 3>That's really interesting.

465
00:30:10.430 --> 00:30:13.589
<v Speaker 3>Um, I guess this is the final, um,
question or thought.

466
00:30:13.630 --> 00:30:16.189
<v Speaker 3>I wanted to talk about sort of build
versus buy, because a lot of what we've been

467
00:30:16.189 --> 00:30:19.989
<v Speaker 3>talking about today, I think, is about
adopting various different AI technologies,

468
00:30:20.069 --> 00:30:20.310
<v Speaker 3>but.

469
00:30:21.420 --> 00:30:24.449
<v Speaker 3>You know, have you been hearing, you know,
a push around, you know, a lot of

470
00:30:24.449 --> 00:30:28.780
<v Speaker 3>building internally, I mean, we know
there's tools now that can, you know, spin up

471
00:30:28.780 --> 00:30:32.160
<v Speaker 3>products or early, early versions of
products very, very quickly.

472
00:30:32.459 --> 00:30:37.500
<v Speaker 3>But are you hearing more in that direction
in recent times, Nick, about building AI

473
00:30:37.500 --> 00:30:38.479
<v Speaker 3>products internally?

474
00:30:38.989 --> 00:30:39.140
<v Speaker 3>Uh,

475
00:30:39.180 --> 00:30:40.380
<v Nick Leeder>it depends who you speak to.

476
00:30:41.119 --> 00:30:42.719
<v Nick Leeder>I think is the ultimate answer.

477
00:30:42.800 --> 00:30:43.219
<v Nick Leeder>Exactly.

478
00:30:44.000 --> 00:30:48.800
<v Nick Leeder>So you, you speak to the IT guys, um, uh
sorry, the IT people, I shouldn't, I'm

479
00:30:48.800 --> 00:30:55.280
<v Nick Leeder>subconscious bias kicking out there, but
the IT people and what you find is that the

480
00:30:55.280 --> 00:30:57.599
<v Nick Leeder>build attraction is quite high, yeah?

481
00:30:58.359 --> 00:31:02.910
<v Nick Leeder>Um, Whereas if you speak to operations
management, they just wanna buy something

482
00:31:02.910 --> 00:31:03.630
<v Nick Leeder>that works.

483
00:31:04.729 --> 00:31:09.010
<v Nick Leeder>So that build versus buy is actually very
much driven by the personas, engineers are

484
00:31:09.010 --> 00:31:13.650
<v Nick Leeder>engineers, so inherently the build
question, the experimentation questions are very

485
00:31:13.650 --> 00:31:14.089
<v Nick Leeder>high.

486
00:31:15.170 --> 00:31:18.180
<v Nick Leeder>Uh, but you have to take into account the
cost.

487
00:31:19.380 --> 00:31:22.689
<v Nick Leeder>And what you're trying to prove, so all
the conversation we've had already in this

488
00:31:22.829 --> 00:31:26.489
<v Nick Leeder>here, if you start with all the negative
context and then try and do it yourself,

489
00:31:26.630 --> 00:31:29.209
<v Nick Leeder>the probability of successful outcome.

490
00:31:30.319 --> 00:31:34.959
<v Nick Leeder>Is, is low and then the question of
scalability makes that probability of successful

491
00:31:34.959 --> 00:31:36.739
<v Nick Leeder>outcome even lower.h.

492
00:31:38.140 --> 00:31:41.060
<v Nick Leeder>Point solutions that require some very
specialist knowledge, if you have that

493
00:31:41.060 --> 00:31:45.140
<v Nick Leeder>knowledge inside, it's fantastic, but
that's not a question of doubt that you open

494
00:31:45.140 --> 00:31:47.540
<v Nick Leeder>the whole Co up around scale.

495
00:31:48.599 --> 00:31:54.520
<v Nick Leeder>So commercial off the shelf solutions that
have proven solutions that know the

496
00:31:54.520 --> 00:31:56.719
<v Nick Leeder>conditions that it works in as well.

497
00:31:58.040 --> 00:32:03.280
<v Nick Leeder>That means your time to value is
significantly reduced by then trying to develop it

498
00:32:03.280 --> 00:32:03.709
<v Nick Leeder>yourself.

499
00:32:04.280 --> 00:32:06.790
<v Nick Leeder>But again, I put the use case flag on.

500
00:32:07.010 --> 00:32:10.280
<v Nick Leeder>If you've got very specialized processes.

501
00:32:11.189 --> 00:32:15.699
<v Nick Leeder>That require specialized inputs, then may
be the commercial off the shelf or Cots

502
00:32:15.699 --> 00:32:17.910
<v Nick Leeder>solutions might not be the right way
forward.

503
00:32:18.699 --> 00:32:24.500
<v Nick Leeder>Um, but what I am seeing I kind of is the
balancing act of a trend here of

504
00:32:24.500 --> 00:32:28.500
<v Nick Leeder>platforms, again, you know, we've gone
through this through IOT as well, yeah.

505
00:32:29.020 --> 00:32:33.699
<v Nick Leeder>We start off with, uh, ideas of what we
could do, we move to platforms, then we end

506
00:32:33.699 --> 00:32:35.780
<v Nick Leeder>up with solutions and then we go back to
platforms.

507
00:32:36.020 --> 00:32:37.900
<v Nick Leeder>There's a cycle that goes on here now.

508
00:32:39.189 --> 00:32:44.550
<v Nick Leeder>Uh, my prediction is AI is, is kind of
going solutions to plat it's on like platform

509
00:32:44.550 --> 00:32:45.229
<v Nick Leeder>move now.

510
00:32:45.750 --> 00:32:49.849
<v Nick Leeder>Maybe we'll go back to solutions again,
you know, let's trust the world of cyclic

511
00:32:50.140 --> 00:32:51.449
<v Nick Leeder>things that have happened before.

512
00:32:53.599 --> 00:32:55.479
<v Speaker 3>Interesting, interesting.

513
00:32:55.839 --> 00:32:59.560
<v Speaker 3>But I think, I think it ultimately comes
down to, again, because a lot of time, I

514
00:32:59.560 --> 00:33:02.550
<v Speaker 3>think, building internally, there's a lot
of internal expertise where we think,

515
00:33:02.599 --> 00:33:06.079
<v Speaker 3>well, we've got all this expertise,
whether skills or knowledge, we can build it

516
00:33:06.079 --> 00:33:09.839
<v Speaker 3>ourselves, but again, back to the point
before about bringing stuff together, you

517
00:33:09.839 --> 00:33:15.380
<v Speaker 3>know, you've got, you know, whatever
vendor, years of, years of experience, great,

518
00:33:15.520 --> 00:33:19.920
<v Speaker 3>um, great individuals who can really help
you in an external part, bring them

519
00:33:19.920 --> 00:33:22.359
<v Speaker 3>together with your fantastic internal
teams and create.

520
00:33:23.050 --> 00:33:26.449
<v Speaker 3>Not create something together, but create
a solution, a joint solution together

521
00:33:26.449 --> 00:33:29.030
<v Speaker 3>that's scalable and can make an impact.

522
00:33:29.130 --> 00:33:33.489
<v Speaker 3>So it's actually, again, you know, the
benefits of coming together with different,

523
00:33:33.530 --> 00:33:35.770
<v Speaker 3>and not just one vendor actually, it could
be multiple vendors, so we're talking

524
00:33:35.770 --> 00:33:41.209
<v Speaker 3>about a partner ecosystem as well, of
course, but yeah, so, I mean the benefits are

525
00:33:41.209 --> 00:33:41.650
<v Speaker 3>clear to that,

526
00:33:41.770 --> 00:33:42.130
<v Nick Leeder>right?

527
00:33:42.530 --> 00:33:46.849
<v Nick Leeder>Yeah, and, and just because you can
doesn't mean you should, you know, I, I could, I

528
00:33:46.849 --> 00:33:51.010
<v Nick Leeder>could build a kit car if I really wanted
to, um, but I go and buy one.

529
00:33:51.380 --> 00:33:53.800
<v Nick Leeder>Because it's actually a lot quicker to get
me from A to B.

530
00:33:54.140 --> 00:33:54.780
<v Nick Leeder>Yeah.

531
00:33:55.380 --> 00:33:59.520
<v Nick Leeder>So, but if I had to build a hill climbing
car.

532
00:34:00.410 --> 00:34:03.530
<v Nick Leeder>The likelihood is I wouldn't go out and
buy a commercial off the shelf vehicle and

533
00:34:03.530 --> 00:34:04.510
<v Nick Leeder>try and modify it.

534
00:34:04.930 --> 00:34:07.540
<v Nick Leeder>I'll probably build one specifically for
that purpose.

535
00:34:07.930 --> 00:34:10.689
<v Nick Leeder>So I think, you know, it's the tools to do
the job.

536
00:34:11.429 --> 00:34:14.270
<v Nick Leeder>Uh, is ultimately the question I'm, I, I'm
statement I'm making.

537
00:34:14.669 --> 00:34:18.429
<v Speaker 3>Yeah, ultimately it's what, what problem
you're trying to solve, and then you can

538
00:34:18.429 --> 00:34:23.169
<v Speaker 3>look at whether building or buying the
solution is, is applicable in that particular

539
00:34:23.169 --> 00:34:24.389
<v Speaker 3>circumstance, right?

540
00:34:24.590 --> 00:34:28.270
<v Nick Leeder>And I, I think timing, we're like I
mentioned right at the beginning of, uh, call,

541
00:34:28.340 --> 00:34:29.389
<v Nick Leeder>we're on a hype curve.

542
00:34:30.429 --> 00:34:35.489
<v Nick Leeder>So, 1.5, 2 years ago, the world of AI is
moving incredibly fast.

543
00:34:35.989 --> 00:34:41.909
<v Nick Leeder>There probably wasn't many solutions out
there that are, that were at scale that are

544
00:34:41.909 --> 00:34:42.429
<v Nick Leeder>proven.

545
00:34:42.750 --> 00:34:46.949
<v Nick Leeder>Now, still there's question marks around
those statements, but now there are

546
00:34:46.949 --> 00:34:51.909
<v Nick Leeder>probably a lot more, given the hype, a lot
more solutions you could look at from the

547
00:34:51.909 --> 00:34:56.469
<v Nick Leeder>big players that you can now assess, but
probably more platform centric than trying

548
00:34:56.469 --> 00:34:59.350
<v Nick Leeder>to do things from scratch, where 18
months, 2 years ago.

549
00:34:59.600 --> 00:35:01.239
<v Nick Leeder>It would the landscape look quite
different.

550
00:35:03.070 --> 00:35:04.719
<v Speaker 3>Absolutely, absolutely.

551
00:35:05.540 --> 00:35:08.610
<v Speaker 3>Um, and, in a way, it's a good, it's a
good point to end.

552
00:35:08.750 --> 00:35:11.909
<v Speaker 3>I mean, the, the only thing I'll, you
know, as we usually do on here, and what we've

553
00:35:11.909 --> 00:35:16.149
<v Speaker 3>done before, Nick, is sort of just end
with, uh, some takeaways for the audience as

554
00:35:16.149 --> 00:35:16.310
<v Speaker 3>well.

555
00:35:16.429 --> 00:35:19.489
<v Speaker 3>So, fingers starting an industrial AI
project.

556
00:35:20.320 --> 00:35:22.949
<v Speaker 3>Um, they wanna be able to get by
internally.

557
00:35:23.169 --> 00:35:25.570
<v Speaker 3>They obviously, you know, they're thinking
about scale as well, so they're not just

558
00:35:25.570 --> 00:35:29.030
<v Speaker 3>thinking about, um, you know, maybe the
short-term vision, but the long-term vision,

559
00:35:29.120 --> 00:35:34.149
<v Speaker 3>but what, what sort of three quick, um,
areas they should sort of consider before

560
00:35:34.489 --> 00:35:36.909
<v Speaker 3>launching into an industrial AI project.

561
00:35:37.790 --> 00:35:41.939
<v Nick Leeder>So if you're gonna launch into an indus
industrial AI project, which clearly wasn't

562
00:35:41.939 --> 00:35:46.510
<v Nick Leeder>very easy to say for me, first question I
would ask is why?

563
00:35:47.929 --> 00:35:49.760
<v Nick Leeder>Why is it an industrial AI project?

564
00:35:50.050 --> 00:35:54.409
<v Nick Leeder>Should it not be a process improvement
project that gathers the right data which you

565
00:35:54.409 --> 00:35:55.719
<v Nick Leeder>can then employ AI on?

566
00:35:55.850 --> 00:35:59.330
<v Nick Leeder>You might have got the question, you may
have got the answer before the question.

567
00:36:00.139 --> 00:36:01.540
<v Nick Leeder>So that's my first fundamental part.

568
00:36:01.739 --> 00:36:05.080
<v Nick Leeder>If you can explain why you're going to do
an industrial AI project.

569
00:36:05.989 --> 00:36:10.409
<v Nick Leeder>Then make sure that the the use case
you're solving is repeatable.

570
00:36:10.790 --> 00:36:14.790
<v Nick Leeder>You know, I've seen a lot of AI projects
that solve the use case once and the

571
00:36:14.790 --> 00:36:17.399
<v Nick Leeder>problem once, but the problem then doesn't
repeat itself.

572
00:36:17.909 --> 00:36:22.669
<v Nick Leeder>That doesn't get you to scale, so it's a
repeatable common problem and it applies to

573
00:36:22.669 --> 00:36:25.649
<v Nick Leeder>multiple lines, multiple factories you've
got in your network.

574
00:36:27.270 --> 00:36:31.780
<v Nick Leeder>And then make sure the measurements are
right, you can demonstrate value.

575
00:36:32.189 --> 00:36:36.070
<v Nick Leeder>You demonstrate value operationally,
demonstrate value at an exact level, but also

576
00:36:36.070 --> 00:36:38.560
<v Nick Leeder>make it relevant to the people you're
impacting.

577
00:36:40.120 --> 00:36:44.360
<v Nick Leeder>My final point is, and don't expect this
to be turned, you know, start on a Monday

578
00:36:44.360 --> 00:36:46.000
<v Nick Leeder>and by Friday you've got the answer.

579
00:36:46.439 --> 00:36:48.909
<v Nick Leeder>These things take time to get right.

580
00:36:49.639 --> 00:36:56.030
<v Nick Leeder>So set a realistic time frame to achieve
these things in and do it in a way that

581
00:36:56.030 --> 00:37:00.260
<v Nick Leeder>doesn't break the current processes but
enhances what you're doing as you're doing

582
00:37:00.260 --> 00:37:01.199
<v Nick Leeder>that step by step.

583
00:37:02.629 --> 00:37:04.110
<v Speaker 3>Oh, excellent, yeah, it's about.

584
00:37:05.129 --> 00:37:09.100
<v Speaker 3>Yeah, and don't try and use AI I guess to
fix, um, processes are already broken.

585
00:37:09.139 --> 00:37:11.649
<v Speaker 3>I'll, I just like that what you said
earlier on as well.

586
00:37:11.780 --> 00:37:14.500
<v Speaker 3>You know, AI is not gonna fix a bad
process, right, as well.

587
00:37:14.620 --> 00:37:17.199
<v Speaker 3>So it's, um, that's another thing to
consider.

588
00:37:17.899 --> 00:37:18.899
<v Speaker 3>Yeah, absolutely.

589
00:37:19.729 --> 00:37:20.439
<v Speaker 3>Fantastic.

590
00:37:20.860 --> 00:37:23.760
<v Speaker 3>But no, thank you, um, so much, Nick, for
your time today.

591
00:37:23.979 --> 00:37:25.699
<v Speaker 3>Very, very generous of your time today.

592
00:37:25.739 --> 00:37:29.600
<v Speaker 3>We've gone over a little bit, but, um,
it's been really great to have you on again,

593
00:37:29.699 --> 00:37:33.020
<v Speaker 3>and I guess, um, this, this episode will
go out in the new year.

594
00:37:33.139 --> 00:37:36.979
<v Speaker 3>We're talking sort of late December now,
but, um, happy Christmas and New Year to

595
00:37:36.979 --> 00:37:37.169
<v Speaker 3>you.

596
00:37:37.370 --> 00:37:37.500
<v Speaker 3>I,

597
00:37:37.620 --> 00:37:39.439
<v Nick Leeder>I should have put the Christmas tree in
the background.

598
00:37:42.260 --> 00:37:43.229
<v Nick Leeder>Exactly, have recorded it.

599
00:37:44.260 --> 00:37:44.590
<v Speaker 3>Exactly.

600
00:37:44.699 --> 00:37:47.580
<v Speaker 3>But no, it's been a pleasure having you on
again and, um, hopefully have you on

601
00:37:47.580 --> 00:37:48.600
<v Speaker 3>again in the future.

602
00:37:49.310 --> 00:37:49.949
<v Nick Leeder>Thank you for having me.

603
00:37:49.989 --> 00:37:53.310
<v Nick Leeder>I really enjoyed the conversation now and
I'm always happy to come along and have a

604
00:37:53.310 --> 00:37:53.969
<v Nick Leeder>chat with you.

605
00:37:54.389 --> 00:37:55.120
<v Speaker 3>Fantastic.

606
00:37:55.550 --> 00:37:58.820
<v Speaker 3>So yes, thank you to you, Nick, and thank
you to everyone out there for listening,

607
00:37:58.949 --> 00:38:01.409
<v Speaker 3>wherever you are, and we'll see you on the
next episode.

608
00:38:05.020 --> 00:38:09.979
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

609
00:38:09.979 --> 00:38:13.360
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
