WEBVTT
Language: en-US

1
00:00:01.110 --> 00:00:04.650
<v Jonathan Bonner>But it's also monitoring machines,
equipment 24/7.

2
00:00:04.980 --> 00:00:10.430
<v Jonathan Bonner>So continuously gathering data,
information about The condition of the machine.

3
00:00:10.970 --> 00:00:14.689
<v Jonathan Bonner>But what we're finding or or what has been
a problem within heavy industry is that

4
00:00:15.170 --> 00:00:18.049
<v Jonathan Bonner>without visibility of these machines'
condition.

5
00:00:19.200 --> 00:00:20.600
<v Jonathan Bonner>They are running to failure.

6
00:00:21.040 --> 00:00:25.159
<v Jonathan Bonner>Now, a human being wouldn't run a race in
a desert without water, without support,

7
00:00:25.329 --> 00:00:27.840
<v Jonathan Bonner>without medical advice or check-ins.

8
00:00:28.079 --> 00:00:32.000
<v Jonathan Bonner>And this is actually, if we use that
analogy, what maintenance teams and heavy

9
00:00:32.000 --> 00:00:34.819
<v Jonathan Bonner>industries have been doing, running to
failure.

10
00:00:35.479 --> 00:00:39.880
<v Jonathan Bonner>But with predictive maintenance, it gives
them insight into the condition, into the

11
00:00:39.880 --> 00:00:45.119
<v Jonathan Bonner>signs of degradation so that A specialist
like a doctor can tell you when to slow

12
00:00:45.119 --> 00:00:50.180
<v Jonathan Bonner>down, when to hydrate, when to rest and
recover, or for maintenance in this case.

13
00:00:51.150 --> 00:00:56.349
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens, and now your host, Nel

14
00:00:56.349 --> 00:00:56.869
<v Speaker 2>Sullivan.

15
00:00:59.139 --> 00:01:02.970
<v Speaker 3>Hello and welcome to the latest episode of
the trend detection podcast.

16
00:01:03.630 --> 00:01:05.980
<v Speaker 3>Um, we're in a new location today.

17
00:01:06.069 --> 00:01:07.949
<v Speaker 3>I'm really excited in the studio today.

18
00:01:08.389 --> 00:01:11.510
<v Speaker 3>Joined by my colleague, Jonathan Bonner,
who's been on many times onto the podcast.

19
00:01:11.629 --> 00:01:12.419
<v Speaker 3>Welcome back, John.

20
00:01:12.629 --> 00:01:13.669
<v Speaker 3>Thank you for having me.

21
00:01:14.150 --> 00:01:14.660
<v Speaker 3>Awesome.

22
00:01:14.750 --> 00:01:20.860
<v Speaker 3>Um, today we're talking about heavy
industry, um, and, and real world winds with

23
00:01:20.860 --> 00:01:22.569
<v Speaker 3>predicting maintenance in the heavy
industry.

24
00:01:22.910 --> 00:01:25.489
<v Speaker 3>But I guess before we start, heavy
industry is quite a broad term.

25
00:01:26.180 --> 00:01:29.790
<v Speaker 3>Could mean a lot of things to, to lots of
different people, so when, when I'm saying

26
00:01:29.790 --> 00:01:31.669
<v Speaker 3>heavy industry, John, what, what does that
mean to you?

27
00:01:31.750 --> 00:01:35.830
<v Speaker 3>What, what sort of, um, let's say
subverticals are we're talking about here?

28
00:01:36.309 --> 00:01:37.569
<v Jonathan Bonner>When you think of heavy industry.

29
00:01:38.120 --> 00:01:39.389
<v Jonathan Bonner>You can think of it in two ways.

30
00:01:39.680 --> 00:01:44.839
<v Jonathan Bonner>Either the machinery used in this process,
manufacturing are heavy, big, extremely

31
00:01:44.839 --> 00:01:50.839
<v Jonathan Bonner>large, the size of warehouses, um, tall
buildings, or what they're producing is

32
00:01:50.839 --> 00:01:52.099
<v Jonathan Bonner>heavy, big and large.

33
00:01:52.269 --> 00:01:56.819
<v Jonathan Bonner>So typically, heavy industry contains
heavy stuff, makes heavy stuff.

34
00:01:57.319 --> 00:02:00.680
<v Jonathan Bonner>However, when you look at the
subverticals, you're thinking of metals, mining,

35
00:02:00.790 --> 00:02:03.919
<v Jonathan Bonner>cement, those type of uh manufacturing
environments.

36
00:02:05.370 --> 00:02:09.229
<v Speaker 3>And in terms of, I mean, I think we know
across all industries actually predictive

37
00:02:09.229 --> 00:02:14.529
<v Speaker 3>maintenance is becoming a strategic
priority, but why specifically in, um, heavy

38
00:02:14.529 --> 00:02:16.190
<v Speaker 3>industry is it becoming so important?

39
00:02:17.169 --> 00:02:18.970
<v Jonathan Bonner>Well, if you think about predictive
maintenance.

40
00:02:19.740 --> 00:02:23.460
<v Jonathan Bonner>It's a decision support tool designed for
maintenance personnel.

41
00:02:24.289 --> 00:02:28.539
<v Jonathan Bonner>But it automates the function of a
condition monitoring engineer on site.

42
00:02:28.800 --> 00:02:31.899
<v Jonathan Bonner>So the data collection, analysis and
reporting are now automated.

43
00:02:32.839 --> 00:02:36.910
<v Jonathan Bonner>But like any good condition monitoring
engineer, it continues to learn about failure

44
00:02:36.910 --> 00:02:41.440
<v Jonathan Bonner>modes, failure patterns, and can be quite
precise in what it's recommending for

45
00:02:41.440 --> 00:02:43.320
<v Jonathan Bonner>maintenance actions and corrective
actions.

46
00:02:44.070 --> 00:02:47.649
<v Jonathan Bonner>But it's also monitoring machines,
equipment 24/7.

47
00:02:47.949 --> 00:02:53.350
<v Jonathan Bonner>So continuously gathering data,
information about The condition of a machine.

48
00:02:53.929 --> 00:02:57.589
<v Jonathan Bonner>But what we're finding or or what has been
a problem within heavy industry is that

49
00:02:58.130 --> 00:03:00.970
<v Jonathan Bonner>without visibility of these machines'
condition.

50
00:03:02.160 --> 00:03:03.509
<v Jonathan Bonner>They are running to failure.

51
00:03:04.000 --> 00:03:08.119
<v Jonathan Bonner>Now, a human being wouldn't run a race in
a desert without water, without support,

52
00:03:08.289 --> 00:03:10.750
<v Jonathan Bonner>without medical advice or check-ins.

53
00:03:11.039 --> 00:03:14.949
<v Jonathan Bonner>And this is actually, if we use that
analogy, what maintenance teams and heavy

54
00:03:14.949 --> 00:03:17.559
<v Jonathan Bonner>industries have been doing, running to
failure.

55
00:03:18.399 --> 00:03:22.850
<v Jonathan Bonner>But with predictive maintenance, it gives
them insight into the condition, into the

56
00:03:22.850 --> 00:03:28.100
<v Jonathan Bonner>signs of degradation, so that A specialist
like a doctor can tell you when to slow

57
00:03:28.100 --> 00:03:33.210
<v Jonathan Bonner>down, when to hydrate, when to rest and
recover or perform maintenance in this case.

58
00:03:33.630 --> 00:03:37.910
<v Jonathan Bonner>So really extremely important in all
industries, but specifically in heavy industry.

59
00:03:38.779 --> 00:03:42.500
<v Speaker 3>So why is running into failure so common
in, in heavy industry?

60
00:03:42.580 --> 00:03:47.259
<v Speaker 3>What's, you know, sort of brought that
mindset on, if it is a mindset thing or a

61
00:03:47.259 --> 00:03:47.919
<v Speaker 3>cultural thing.

62
00:03:48.419 --> 00:03:50.410
<v Jonathan Bonner>I, I wouldn't say it's a mindset or a
cultural thing.

63
00:03:50.460 --> 00:03:57.220
<v Jonathan Bonner>I think it's got to do with availability,
availability of time, resources, skills,

64
00:03:57.660 --> 00:04:00.660
<v Jonathan Bonner>knowledge about what's happening or
visibility of what's happening.

65
00:04:01.100 --> 00:04:02.059
<v Jonathan Bonner>Quite often.

66
00:04:02.720 --> 00:04:07.160
<v Jonathan Bonner>Environments such as heavy industry, your
metals and mining have been set up with

67
00:04:07.160 --> 00:04:09.270
<v Jonathan Bonner>visibility on the process.

68
00:04:09.639 --> 00:04:12.860
<v Jonathan Bonner>What product is coming out, at what rate
and at what quality.

69
00:04:13.279 --> 00:04:18.679
<v Jonathan Bonner>But very little thought has gone into The
maintenance or understanding the condition

70
00:04:18.679 --> 00:04:19.559
<v Jonathan Bonner>of these machines.

71
00:04:20.320 --> 00:04:25.820
<v Jonathan Bonner>So, you'll find that often data is there,
the ability to have visibility is there.

72
00:04:26.720 --> 00:04:30.269
<v Jonathan Bonner>However, it's just not catered for in the
initial designs or the initial operations,

73
00:04:31.489 --> 00:04:37.769
<v Jonathan Bonner>and now after 2030 years of running,
they've done it in a reactive way, day in, day

74
00:04:37.769 --> 00:04:43.489
<v Jonathan Bonner>out for decades, and they haven't had a
reason to change, whereas technology

75
00:04:43.489 --> 00:04:45.269
<v Jonathan Bonner>nowadays enables this change.

76
00:04:45.589 --> 00:04:49.630
<v Speaker 3>And you mentioned about data before, and
there's obviously, you know, again across

77
00:04:49.630 --> 00:04:52.589
<v Speaker 3>all industries, but in heavy industry as
well, there's, you know, data is being

78
00:04:52.589 --> 00:04:56.549
<v Speaker 3>collected, but are you saying maybe it's
not being utilized in, in the right way at

79
00:04:56.549 --> 00:04:59.950
<v Speaker 3>the moment, it's not being explored, the
insights aren't being gathered from that

80
00:04:59.950 --> 00:05:00.429
<v Speaker 3>data.

81
00:05:00.829 --> 00:05:01.890
<v Jonathan Bonner>Absolutely, so.

82
00:05:02.809 --> 00:05:07.540
<v Jonathan Bonner>At the moment, what we see is it's a lot
of the data that exists on a site is geared

83
00:05:07.540 --> 00:05:10.380
<v Jonathan Bonner>for process control or understanding of
production.

84
00:05:11.359 --> 00:05:14.149
<v Jonathan Bonner>Perfect, that has huge amounts of
benefits, and that's great.

85
00:05:14.829 --> 00:05:19.660
<v Jonathan Bonner>But what you need, especially for
predictive maintenance, is condition data.

86
00:05:20.160 --> 00:05:24.239
<v Jonathan Bonner>So condition monitoring data such as
pressure, currents, torque, vibration,

87
00:05:24.390 --> 00:05:29.920
<v Jonathan Bonner>temperature, speed, flow, cycle time,
whatever is relevant to identify the normal

88
00:05:29.920 --> 00:05:30.799
<v Jonathan Bonner>condition of an asset.

89
00:05:31.239 --> 00:05:36.799
<v Jonathan Bonner>Now, some of those are available within
PLCs, drives, inverters from a customer's

90
00:05:36.799 --> 00:05:38.500
<v Jonathan Bonner>environment existing already.

91
00:05:39.299 --> 00:05:44.619
<v Jonathan Bonner>But a lot of them haven't been mapped in,
so there is no record or historian of this

92
00:05:44.619 --> 00:05:50.420
<v Jonathan Bonner>data, and there's no analytics being
employed on this data to gain further insight.

93
00:05:51.170 --> 00:05:53.000
<v Jonathan Bonner>But that's where predictive maintenance
comes in.

94
00:05:53.079 --> 00:05:58.279
<v Jonathan Bonner>It's about using your existing data along
with additional data that can either be

95
00:05:58.279 --> 00:06:04.040
<v Jonathan Bonner>mapped through your OT environment or
supplemented with additional sensors so that

96
00:06:04.040 --> 00:06:08.399
<v Jonathan Bonner>you can get a centralized visibility of an
entire plant's production, the signs of

97
00:06:08.399 --> 00:06:13.029
<v Jonathan Bonner>degradation with then recommendations on
what maintenance should be done, when it

98
00:06:13.029 --> 00:06:15.880
<v Jonathan Bonner>should be done, um, and even who should be
doing it.

99
00:06:16.739 --> 00:06:17.779
<v Speaker 3>No, exactly, exactly.

100
00:06:17.859 --> 00:06:21.940
<v Speaker 3>And I, I guess to your point as well,
because we do like to say, you know, use

101
00:06:21.940 --> 00:06:23.000
<v Speaker 3>existing data where possible.

102
00:06:23.019 --> 00:06:26.859
<v Speaker 3>When there is a requirement to, you know,
add additional sensors and bring in other

103
00:06:26.859 --> 00:06:27.679
<v Speaker 3>types of data.

104
00:06:27.859 --> 00:06:31.239
<v Speaker 3>I mean, I can only imagine in a heavy
industry environment that's quite challenging.

105
00:06:31.540 --> 00:06:34.880
<v Speaker 3>Um, well, I mean, it's a question for you,
Joel, actually, is about, you know, is it

106
00:06:34.880 --> 00:06:38.940
<v Speaker 3>challenging to collect data in such a sort
of a rough, you know, potentially rough

107
00:06:38.940 --> 00:06:39.399
<v Speaker 3>environment.

108
00:06:40.500 --> 00:06:40.529
<v Jonathan Bonner>Actually, no.

109
00:06:40.660 --> 00:06:41.619
<v Jonathan Bonner>Actually, no, yeah.

110
00:06:46.779 --> 00:06:50.029
<v Jonathan Bonner>No, but although it hasn't been mapped
through, the data exists.

111
00:06:50.380 --> 00:06:55.320
<v Jonathan Bonner>The systems are in place already that are
gathering the data, which are controlling,

112
00:06:55.980 --> 00:06:58.540
<v Jonathan Bonner>uh, the machines and that have these forms
of data in it.

113
00:06:58.619 --> 00:07:00.079
<v Jonathan Bonner>So the data we find exists.

114
00:07:00.850 --> 00:07:01.480
<v Jonathan Bonner>It's there.

115
00:07:02.329 --> 00:07:04.359
<v Jonathan Bonner>It's really about how to access it.

116
00:07:04.730 --> 00:07:09.850
<v Jonathan Bonner>And some of the challenges we're finding
with that is really around how a company

117
00:07:09.850 --> 00:07:12.510
<v Jonathan Bonner>has grown or let's take a steel plant, for
example.

118
00:07:13.440 --> 00:07:16.760
<v Jonathan Bonner>A steel a steel factory could have many
different plants inside of it.

119
00:07:17.089 --> 00:07:18.440
<v Jonathan Bonner>They could be different ages.

120
00:07:18.600 --> 00:07:23.119
<v Jonathan Bonner>They could have different OEMs, uh,
responsible, um, different controllers,

121
00:07:23.209 --> 00:07:25.010
<v Jonathan Bonner>different communication pathways.

122
00:07:25.720 --> 00:07:30.559
<v Jonathan Bonner>So really, getting access to the data can
be a bit of a challenge, and has been a

123
00:07:30.559 --> 00:07:30.980
<v Jonathan Bonner>challenge.

124
00:07:31.829 --> 00:07:36.579
<v Jonathan Bonner>But we do live in an age where gateways
and getting access to the relevant data is

125
00:07:36.579 --> 00:07:38.149
<v Jonathan Bonner>actually relatively easy.

126
00:07:38.630 --> 00:07:44.070
<v Jonathan Bonner>There are single devices that can speak to
a range of OEMs, can gather the relevant

127
00:07:44.070 --> 00:07:49.190
<v Jonathan Bonner>data, can do the data processing that is
required, and can push it to the cloud in a

128
00:07:49.190 --> 00:07:55.609
<v Jonathan Bonner>very secure way, um, practically
risk-free, um, for a small adjustment, huge amounts

129
00:07:55.609 --> 00:07:56.209
<v Jonathan Bonner>of value.

130
00:07:56.670 --> 00:07:59.899
<v Jonathan Bonner>And in heavy industry, the data that is
existing already.

131
00:07:59.989 --> 00:08:00.690
<v Jonathan Bonner>It's there.

132
00:08:01.190 --> 00:08:06.470
<v Jonathan Bonner>Um, And what we're finding is the addition
of, uh, additional sensors and hardware

133
00:08:06.890 --> 00:08:10.600
<v Jonathan Bonner>is actually not as much as customers
would, would think to get started.

134
00:08:11.049 --> 00:08:16.309
<v Jonathan Bonner>So we can drive a lot of value from
existing data, existing infrastructure, um, that

135
00:08:16.329 --> 00:08:16.989
<v Jonathan Bonner>is already there.

136
00:08:17.670 --> 00:08:21.369
<v Speaker 3>Yeah, I guess it, is it one of those
things where some, sometimes there's a, you

137
00:08:21.369 --> 00:08:25.630
<v Speaker 3>know, underestimating the value within
existing data already, and maybe the other

138
00:08:25.630 --> 00:08:27.799
<v Speaker 3>way around as well is like overestimating
the value in that.

139
00:08:27.899 --> 00:08:32.349
<v Speaker 3>Is that something that you often come
across those are very contrasting scenarios.

140
00:08:33.260 --> 00:08:38.539
<v Jonathan Bonner>I think, uh, the scenario that we come
across the most is overestimating the data

141
00:08:38.539 --> 00:08:40.080
<v Jonathan Bonner>that that that that is available.

142
00:08:40.619 --> 00:08:41.000
<v Jonathan Bonner>Um.

143
00:08:41.890 --> 00:08:45.739
<v Jonathan Bonner>Yeah, quite often in in our
investigations, the customer will say, yeah, we've got

144
00:08:45.739 --> 00:08:48.690
<v Jonathan Bonner>plenty of data, loads of data, no problem
there.

145
00:08:48.820 --> 00:08:53.979
<v Jonathan Bonner>And then when we come down to actually
investigating what they have, as far as time

146
00:08:53.979 --> 00:08:59.820
<v Jonathan Bonner>series data, continuous measurements of a,
a parameter, like currents, like torque,

147
00:08:59.929 --> 00:09:00.520
<v Jonathan Bonner>and so on.

148
00:09:01.729 --> 00:09:03.700
<v Jonathan Bonner>That that isn't necessarily in place.

149
00:09:04.049 --> 00:09:08.809
<v Jonathan Bonner>Again, they'll have a lot of process
related data, not necessarily conditioned data.

150
00:09:09.780 --> 00:09:16.179
<v Jonathan Bonner>However There is an underestimation of how
much value can be derived from what is

151
00:09:16.179 --> 00:09:17.200
<v Jonathan Bonner>existing on site.

152
00:09:17.780 --> 00:09:21.780
<v Jonathan Bonner>So when we really do start to investigate
it and we look at the possibilities for

153
00:09:21.780 --> 00:09:27.770
<v Jonathan Bonner>additional data mapping, for adding in a
data gateway that can speak to OEMs or

154
00:09:27.770 --> 00:09:33.260
<v Jonathan Bonner>controllers and make the data useful,
really, we have a lot of value and a lot of

155
00:09:33.260 --> 00:09:35.479
<v Jonathan Bonner>benefit from that existing data already.

156
00:09:36.099 --> 00:09:39.059
<v Jonathan Bonner>So part of my role within Siemens and
Sensei.

157
00:09:39.830 --> 00:09:41.900
<v Jonathan Bonner>is to assist with those investigations.

158
00:09:42.309 --> 00:09:47.450
<v Jonathan Bonner>To help identify what data exists, where
does it exist, how do we get access to it,

159
00:09:47.799 --> 00:09:52.270
<v Jonathan Bonner>and how can we process it and get it
pushed to the cloud, so that we can use it.

160
00:09:53.260 --> 00:09:56.500
<v Speaker 3>Well, I guess another angle on this as
well, because we talked a lot about data and

161
00:09:56.500 --> 00:10:00.090
<v Speaker 3>collection of data, but the other side of
it is the human element, the, the

162
00:10:00.090 --> 00:10:03.729
<v Speaker 3>knowledge that's often locked in people's
heads or in manuals and things like that.

163
00:10:03.739 --> 00:10:07.609
<v Speaker 3>And so how, you know, in the heavy
industry, how do, how can they extract that sort

164
00:10:07.609 --> 00:10:11.799
<v Speaker 3>of information out and utilize it in a
sort of a predictive maintenance deployment.

165
00:10:12.880 --> 00:10:16.210
<v Jonathan Bonner>I guess that expert knowledge comes in a
range of forms.

166
00:10:17.190 --> 00:10:22.940
<v Jonathan Bonner>The first format which is actually being
extremely useful for us now is expert

167
00:10:22.940 --> 00:10:23.830
<v Jonathan Bonner>documentation.

168
00:10:24.190 --> 00:10:30.469
<v Jonathan Bonner>OEM manuals, maintenance manuals, decision
trees based off of experience over many

169
00:10:30.469 --> 00:10:31.090
<v Jonathan Bonner>years.

170
00:10:31.590 --> 00:10:38.460
<v Jonathan Bonner>Written documentation on uh machines, what
to do next, Pro, uh, problem shooting and

171
00:10:38.460 --> 00:10:38.780
<v Jonathan Bonner>so on.

172
00:10:38.950 --> 00:10:39.950
<v Jonathan Bonner>Troublesshooting rather.

173
00:10:41.119 --> 00:10:45.690
<v Jonathan Bonner>So we can load that into the application
and that can be used and referenced

174
00:10:45.690 --> 00:10:48.169
<v Jonathan Bonner>directly using our Sensi maintenance
copilot.

175
00:10:49.140 --> 00:10:53.979
<v Jonathan Bonner>But the other form of knowledge and
experience that we want to capture or at least

176
00:10:53.979 --> 00:10:58.260
<v Jonathan Bonner>feed into the application is the human
knowledge, the stuff that is inside of their

177
00:10:58.260 --> 00:10:58.739
<v Jonathan Bonner>brains.

178
00:10:59.099 --> 00:11:02.760
<v Jonathan Bonner>The stuff that has taken decades and
decades to, to learn.

179
00:11:03.440 --> 00:11:08.690
<v Jonathan Bonner>And that comes in the form, or at least
for us, in maintenance, uh, events

180
00:11:08.690 --> 00:11:08.989
<v Jonathan Bonner>information.

181
00:11:09.479 --> 00:11:13.590
<v Jonathan Bonner>Tracking what was done, what the problem
was, what their, their process of fault

182
00:11:13.590 --> 00:11:18.280
<v Jonathan Bonner>finding showed, um, who was involved, you
know, tracking.

183
00:11:18.929 --> 00:11:22.690
<v Jonathan Bonner>And making markers of their knowledge
inside of the application.

184
00:11:23.210 --> 00:11:28.039
<v Jonathan Bonner>So using documented knowledge and the
person's actual actions and feedback of their

185
00:11:28.039 --> 00:11:34.000
<v Jonathan Bonner>actions to unify that so that it can be
made ref or so that it can be referenced

186
00:11:34.000 --> 00:11:35.049
<v Jonathan Bonner>ongoing in the future.

187
00:11:36.030 --> 00:11:39.880
<v Speaker 3>And I wonder, in just the technology
context, we know how valuable, you know,

188
00:11:40.000 --> 00:11:42.599
<v Speaker 3>knowledge of people who know the machines
like the back of their hands have worked

189
00:11:42.599 --> 00:11:46.559
<v Speaker 3>in the industry for a long time, but when
it comes to a technology deployment, is it

190
00:11:46.559 --> 00:11:50.440
<v Speaker 3>sometimes forgotten that actually your
knowledge is just as important to this as,

191
00:11:50.719 --> 00:11:53.919
<v Speaker 3>you know, the data we collect from
machines or how well the technology works, if

192
00:11:53.919 --> 00:11:54.580
<v Speaker 3>that makes sense.

193
00:11:54.880 --> 00:11:55.000
<v Speaker 3>Yeah,

194
00:11:55.119 --> 00:11:59.280
<v Jonathan Bonner>so the specialists on site who can help,
uh, give us access to the data, can help us

195
00:11:59.280 --> 00:12:00.090
<v Jonathan Bonner>process the data.

196
00:12:00.520 --> 00:12:01.190
<v Jonathan Bonner>Having that.

197
00:12:01.979 --> 00:12:06.229
<v Jonathan Bonner>Specialist knowledge and input from the
very early stages means that when we run

198
00:12:06.229 --> 00:12:11.549
<v Jonathan Bonner>into the initial deployment, the, the
start of the project, that everything has been

199
00:12:11.549 --> 00:12:16.750
<v Jonathan Bonner>considered well, that we've had a smooth
implementation, that the onboarding process

200
00:12:16.750 --> 00:12:21.869
<v Jonathan Bonner>has gone well, and the results that we're
getting are really good because we've

201
00:12:21.869 --> 00:12:25.830
<v Jonathan Bonner>taken everything which is important, which
can only be found out from the

202
00:12:25.830 --> 00:12:30.190
<v Jonathan Bonner>specialists on site, the, the people who
have the knowledge and know-how and

203
00:12:30.190 --> 00:12:30.669
<v Jonathan Bonner>experience.

204
00:12:31.369 --> 00:12:33.729
<v Jonathan Bonner>They bring into a project is just
phenomenal.

205
00:12:34.840 --> 00:12:38.159
<v Speaker 3>And I guess that, that leads to a, you
know, a more general point about, you know,

206
00:12:38.320 --> 00:12:44.390
<v Speaker 3>workforce engagement in the projects and
the change management required, um, for a

207
00:12:44.390 --> 00:12:47.719
<v Speaker 3>successful rollout because we know you
were just saying then about, you know, you

208
00:12:47.719 --> 00:12:51.559
<v Speaker 3>need people engaged in the project in
order for it to work, or, you know, people

209
00:12:51.559 --> 00:12:54.710
<v Speaker 3>engaging with the app and, and looking at
cases and things like that, but maybe you

210
00:12:54.710 --> 00:12:57.440
<v Speaker 3>could talk a little bit, Jon, about the,
um, the change management piece.

211
00:12:57.520 --> 00:13:01.000
<v Speaker 3>What, what mindset needs to sort of change
within an organization.

212
00:13:01.359 --> 00:13:03.159
<v Jonathan Bonner>Absolutely, without people.

213
00:13:04.039 --> 00:13:07.080
<v Jonathan Bonner>Adopting the solution without them using
it, it's useless.

214
00:13:07.330 --> 00:13:11.369
<v Jonathan Bonner>Doesn't matter how good the functionality
is, doesn't matter how impressive the

215
00:13:11.369 --> 00:13:12.179
<v Jonathan Bonner>features are.

216
00:13:12.630 --> 00:13:14.750
<v Jonathan Bonner>Without people using it, it is useless.

217
00:13:15.289 --> 00:13:18.239
<v Jonathan Bonner>So, we have a number of ways of addressing
this.

218
00:13:18.489 --> 00:13:21.409
<v Jonathan Bonner>The first is to get the right people in
the room at the right time.

219
00:13:22.130 --> 00:13:22.909
<v Jonathan Bonner>Early on.

220
00:13:23.450 --> 00:13:26.849
<v Jonathan Bonner>So when we start a project, there's
typically 5 key characters that we look to

221
00:13:26.849 --> 00:13:27.469
<v Jonathan Bonner>involve.

222
00:13:27.969 --> 00:13:31.809
<v Jonathan Bonner>Project sponsor, someone who at a high
level can enforce change.

223
00:13:32.010 --> 00:13:34.919
<v Jonathan Bonner>They can get you the budget and the, the
PO that you need.

224
00:13:35.250 --> 00:13:40.349
<v Jonathan Bonner>They can get replacements for anyone who
goes off sick in the project, high level

225
00:13:41.090 --> 00:13:42.919
<v Jonathan Bonner>change, project sponsor.

226
00:13:43.520 --> 00:13:47.599
<v Jonathan Bonner>Then we're looking for maintenance
representation, because ideally, maintenance

227
00:13:47.599 --> 00:13:49.760
<v Jonathan Bonner>personnel are our desired end user.

228
00:13:50.080 --> 00:13:54.559
<v Jonathan Bonner>So we want them involved as early as
possible, so that it's their solution, not

229
00:13:54.559 --> 00:13:58.080
<v Jonathan Bonner>something that management has done and now
expects them to use.

230
00:13:59.010 --> 00:14:01.950
<v Jonathan Bonner>We're looking for a PDM champion.

231
00:14:02.330 --> 00:14:06.950
<v Jonathan Bonner>Someone who is gonna be responsible for
day to day progress and moving the project

232
00:14:06.950 --> 00:14:07.349
<v Jonathan Bonner>along.

233
00:14:07.969 --> 00:14:13.679
<v Jonathan Bonner>We look for controls or controls and
drives engineers, um, OT staff, people who can

234
00:14:13.679 --> 00:14:18.440
<v Jonathan Bonner>help us with the OT environment, and then
IT essentially because we need the data to

235
00:14:18.440 --> 00:14:22.030
<v Jonathan Bonner>move from the OT environment and come into
the IT space in the cloud.

236
00:14:22.570 --> 00:14:26.609
<v Jonathan Bonner>So having the right people in the room at
the right time is absolutely key.

237
00:14:27.239 --> 00:14:29.929
<v Jonathan Bonner>But you also need to get them on board.

238
00:14:30.239 --> 00:14:34.400
<v Jonathan Bonner>You need to make sure that their concerns
are addressed, that they are completely

239
00:14:34.400 --> 00:14:39.000
<v Jonathan Bonner>satisfied and happy, and that they become,
every one of those people actually become

240
00:14:39.000 --> 00:14:40.000
<v Jonathan Bonner>your PDM champion.

241
00:14:40.929 --> 00:14:46.380
<v Jonathan Bonner>Because they can progress it along during
the initial stages, but also act as your

242
00:14:46.380 --> 00:14:48.239
<v Jonathan Bonner>champion throughout their business.

243
00:14:48.299 --> 00:14:52.820
<v Jonathan Bonner>They can take the results and distribute
it internally, um, and get other people

244
00:14:52.820 --> 00:14:55.799
<v Jonathan Bonner>excited so that it's more widely used and
more widely adopted.

245
00:14:56.219 --> 00:15:01.940
<v Jonathan Bonner>And really what we want by that is to have
other departments, other plants, other

246
00:15:01.940 --> 00:15:06.539
<v Jonathan Bonner>factories and other locations, begging to
have the solution implemented because of

247
00:15:06.539 --> 00:15:08.700
<v Jonathan Bonner>the good stuff that they're hearing from
SIITA.

248
00:15:09.690 --> 00:15:12.609
<v Speaker 3>And you mentioned that, you know, about
scale as well, because, of course,

249
00:15:12.719 --> 00:15:17.150
<v Speaker 3>predicting maintenance across a line,
across a few machines is one thing, but across

250
00:15:17.369 --> 00:15:21.250
<v Speaker 3>the real, uh, value and return on
investment, as we know, comes from scale across

251
00:15:21.250 --> 00:15:21.840
<v Speaker 3>multiple plants.

252
00:15:21.849 --> 00:15:25.969
<v Speaker 3>But what are sort of the challenges,
again, thinking about heavy industry, you know,

253
00:15:26.090 --> 00:15:27.719
<v Speaker 3>probably very remote environments.

254
00:15:27.929 --> 00:15:32.010
<v Speaker 3>How, how, how tricky is it to, you know,
scale predictive maintenance across those

255
00:15:32.010 --> 00:15:32.539
<v Speaker 3>environments?

256
00:15:35.299 --> 00:15:37.590
<v Jonathan Bonner>Scale is not actually that much of a
problem.

257
00:15:38.250 --> 00:15:41.419
<v Jonathan Bonner>The machines are there, typically the
infrastructure is there.

258
00:15:41.729 --> 00:15:45.489
<v Jonathan Bonner>There's some small adjustments, even for
remote plants, you can get connectivity, so

259
00:15:45.489 --> 00:15:47.150
<v Jonathan Bonner>we can still get access to the data.

260
00:15:47.570 --> 00:15:50.309
<v Jonathan Bonner>So, the ability to scale is not the
problem.

261
00:15:50.609 --> 00:15:56.049
<v Jonathan Bonner>It's about targeting the use case, the
value, the business outcomes that drive

262
00:15:56.049 --> 00:15:56.750
<v Jonathan Bonner>scale.

263
00:15:57.679 --> 00:16:01.169
<v Jonathan Bonner>Because you're working with the project
team, they know the ins and outs of the

264
00:16:01.169 --> 00:16:03.409
<v Jonathan Bonner>solution you're proposing, they're all
happy with it.

265
00:16:03.739 --> 00:16:09.200
<v Jonathan Bonner>But they all need to go and present these
results or, you know, the possibilities to

266
00:16:09.460 --> 00:16:10.179
<v Jonathan Bonner>a higher team.

267
00:16:11.000 --> 00:16:15.349
<v Jonathan Bonner>Um, and once you're running the project,
they need to advocate for it and, you know,

268
00:16:15.929 --> 00:16:21.530
<v Jonathan Bonner>push those results again to the higher
team to get further buy-in, to get a further

269
00:16:21.530 --> 00:16:23.190
<v Jonathan Bonner>financial support to scale.

270
00:16:23.690 --> 00:16:29.179
<v Jonathan Bonner>So I would say one of the biggest
challenges is really Starting a project that is

271
00:16:29.619 --> 00:16:34.280
<v Jonathan Bonner>going to drive business value, that's
going to drive return on investment, and then

272
00:16:34.280 --> 00:16:41.109
<v Jonathan Bonner>making sure that you are Targeting
everyone's concerns, their desired outcomes, so

273
00:16:41.109 --> 00:16:44.669
<v Jonathan Bonner>that you're running the project
successfully, that you're constantly checking on

274
00:16:44.669 --> 00:16:48.590
<v Jonathan Bonner>milestones, making sure you're hitting the
success criteria at the right milestones,

275
00:16:48.950 --> 00:16:52.909
<v Jonathan Bonner>so that when you do come towards the end
of the project, as I said, people are dying

276
00:16:52.909 --> 00:16:53.510
<v Jonathan Bonner>for a

277
00:16:53.510 --> 00:16:58.590
<v Jonathan Bonner>scaled operation, not just, that was nice,
but uh we'll try again in a few years.

278
00:16:59.200 --> 00:17:02.669
<v Speaker 3>And so, and it, it's all got me thinking
about um who leads these projects, and

279
00:17:02.669 --> 00:17:03.489
<v Speaker 3>maybe it's not.

280
00:17:03.909 --> 00:17:07.589
<v Speaker 3>You know, probably differs organization to
organization, but from your experience

281
00:17:07.589 --> 00:17:11.859
<v Speaker 3>in, in heavy industries, is it, you know,
do you find these are sort of IT led

282
00:17:11.859 --> 00:17:16.189
<v Speaker 3>initiatives or more on the sort of the
maintenance engineering side, or it, is it

283
00:17:16.189 --> 00:17:19.790
<v Speaker 3>really, you know, both coming together and
meeting in the middle somehow?

284
00:17:19.949 --> 00:17:21.329
<v Jonathan Bonner>Absolute mixed bag.

285
00:17:21.680 --> 00:17:28.069
<v Jonathan Bonner>Um, we, within heavy industries, we've
engaged with maintenance teams, uh,

286
00:17:28.150 --> 00:17:30.430
<v Jonathan Bonner>digitization teams, uh.

287
00:17:30.900 --> 00:17:33.839
<v Jonathan Bonner>IT teams, a full range of.

288
00:17:35.219 --> 00:17:38.630
<v Jonathan Bonner>Teams, I guess, but a full range of them
who are interested in predictive

289
00:17:38.630 --> 00:17:39.349
<v Jonathan Bonner>maintenance.

290
00:17:39.670 --> 00:17:45.650
<v Jonathan Bonner>But all of them have different reasons for
investigating predictive maintenance.

291
00:17:46.270 --> 00:17:49.270
<v Jonathan Bonner>So maintenance team, looking for a
maintenance efficiency.

292
00:17:49.510 --> 00:17:50.030
<v Jonathan Bonner>Fantastic.

293
00:17:50.109 --> 00:17:51.750
<v Jonathan Bonner>That's what predictive maintenance is
about.

294
00:17:52.109 --> 00:17:54.469
<v Jonathan Bonner>Um, digitization teams.

295
00:17:56.829 --> 00:18:01.650
<v Jonathan Bonner>Yeah, sometimes digitalization teams can
come about because Uh, they were at a, a

296
00:18:01.650 --> 00:18:02.670
<v Jonathan Bonner>show, an event.

297
00:18:02.890 --> 00:18:04.209
<v Jonathan Bonner>They saw something really cool.

298
00:18:04.310 --> 00:18:07.290
<v Jonathan Bonner>Now they wanna investigate and, see if we
can make change.

299
00:18:07.849 --> 00:18:10.560
<v Jonathan Bonner>Other digitization teams have a very clear
use case.

300
00:18:10.770 --> 00:18:11.250
<v Jonathan Bonner>Fantastic.

301
00:18:11.319 --> 00:18:13.270
<v Jonathan Bonner>We like the ones with a very clear use
case.

302
00:18:13.810 --> 00:18:20.810
<v Jonathan Bonner>Um, IT teams are typically more cautious
of the digitization in a sense

303
00:18:20.810 --> 00:18:27.530
<v Jonathan Bonner>that If you look at the, the risks in
integrating OT and IT or the perceived

304
00:18:27.530 --> 00:18:28.270
<v Jonathan Bonner>risks rather.

305
00:18:29.349 --> 00:18:31.579
<v Jonathan Bonner>Um, uh, that is quite high.

306
00:18:31.760 --> 00:18:34.760
<v Jonathan Bonner>And what happens if it fails is also quite
bad.

307
00:18:35.089 --> 00:18:37.400
<v Jonathan Bonner>The, the risk of failure is, is extremely
high.

308
00:18:37.550 --> 00:18:41.109
<v Jonathan Bonner>No one wants to start something with that
amount of risk.

309
00:18:41.849 --> 00:18:44.069
<v Jonathan Bonner>So, IT teams can be a little bit tricky.

310
00:18:44.689 --> 00:18:48.489
<v Jonathan Bonner>However, when we start to really engage
with them, speak their language, identify

311
00:18:48.489 --> 00:18:54.369
<v Jonathan Bonner>what is important to them, um, and what
risks they feel, we can then start to

312
00:18:54.369 --> 00:18:57.349
<v Jonathan Bonner>mitigate those and make them a lot more
comfortable with, with the project.

313
00:18:58.119 --> 00:19:00.819
<v Jonathan Bonner>But typically we're wanting to, to work
with.

314
00:19:01.969 --> 00:19:06.959
<v Jonathan Bonner>Maintenance, digitization, those type of
characters because typically speaking,

315
00:19:07.209 --> 00:19:11.189
<v Jonathan Bonner>their objectives align with what the
deliverables are with predictive maintenance.

316
00:19:11.729 --> 00:19:15.130
<v Speaker 3>Yeah, it's interesting cos you mentioned
objectives and outcomes and that, that's of

317
00:19:15.130 --> 00:19:19.489
<v Speaker 3>course, why we're here is to deliver the,
the outcomes and overcome the challenges

318
00:19:19.489 --> 00:19:24.430
<v Speaker 3>customers are facing, um, and I know we
could talk about unplanned downtime and

319
00:19:24.640 --> 00:19:26.969
<v Speaker 3>reducing maintenance costs would be more,
more efficient.

320
00:19:27.310 --> 00:19:30.709
<v Speaker 3>Well, I guess one, which I think's
probably particularly interesting, well,

321
00:19:30.829 --> 00:19:33.949
<v Speaker 3>particularly important, important in any
industry, but in every industry

322
00:19:33.949 --> 00:19:36.949
<v Speaker 3>particularly is, is safety and workforce
safety.

323
00:19:37.099 --> 00:19:40.339
<v Speaker 3>And I remember speaking to your, actually,
a guy on your team, Tom, a colleague of

324
00:19:40.339 --> 00:19:44.469
<v Speaker 3>ours, he was saying he, he spoke to a
customer who, um, who actually brought that to

325
00:19:44.469 --> 00:19:46.430
<v Speaker 3>his attention, you know, when they're
talking about, oh, you know, what, you know,

326
00:19:46.469 --> 00:19:47.390
<v Speaker 3>what challenges are you facing?

327
00:19:47.510 --> 00:19:48.069
<v Speaker 3>Is it downtime?

328
00:19:48.109 --> 00:19:51.270
<v Speaker 3>Is it, and then he was like, no, safety,
which we all know is the number one

329
00:19:51.270 --> 00:19:51.770
<v Speaker 3>priority.

330
00:19:52.319 --> 00:19:55.599
<v Speaker 3>But again maybe you could talk about, you
know, predictive maintenance, you know,

331
00:19:55.719 --> 00:19:59.790
<v Speaker 3>role in that, which can play such an
important role in that side of things.

332
00:20:02.709 --> 00:20:03.319
<v Jonathan Bonner>Absolutely.

333
00:20:04.140 --> 00:20:08.819
<v Jonathan Bonner>So, if I just run through some of the
benefits of predictive maintenance, reduction

334
00:20:08.819 --> 00:20:11.770
<v Jonathan Bonner>of unplanned downtime, right, that's the,
the obvious one.

335
00:20:12.140 --> 00:20:14.290
<v Jonathan Bonner>But also precise and correct maintenance.

336
00:20:14.459 --> 00:20:20.760
<v Jonathan Bonner>So really knowing that For the 95% of your
operations that are in perfect health,

337
00:20:20.890 --> 00:20:22.160
<v Jonathan Bonner>that they are in perfect health.

338
00:20:22.410 --> 00:20:23.050
<v Jonathan Bonner>Don't touch them.

339
00:20:23.800 --> 00:20:27.640
<v Jonathan Bonner>And that then drives the rest of the
benefits or a full range of them, one of them

340
00:20:27.640 --> 00:20:28.420
<v Jonathan Bonner>being safety.

341
00:20:28.959 --> 00:20:33.630
<v Jonathan Bonner>Because the less you have to touch a
machine, the less risk and more cost there is.

342
00:20:34.160 --> 00:20:39.270
<v Jonathan Bonner>So, you don't have to send people out to
go and do inspections because you have the

343
00:20:39.270 --> 00:20:40.380
<v Jonathan Bonner>visibility of it.

344
00:20:40.760 --> 00:20:44.239
<v Jonathan Bonner>Um, you don't need to do plan maintenance
or you can reduce your plan, plan

345
00:20:44.239 --> 00:20:48.219
<v Jonathan Bonner>maintenance rather, because you have
visibility of an assets condition.

346
00:20:48.780 --> 00:20:52.180
<v Jonathan Bonner>You can have better planning time, you can
make sure that you have the right spares,

347
00:20:52.250 --> 00:20:54.209
<v Jonathan Bonner>the right people, when production allows.

348
00:20:54.579 --> 00:20:56.810
<v Jonathan Bonner>You can make better informed decisions.

349
00:20:57.260 --> 00:20:59.680
<v Jonathan Bonner>So, huge impact on safety in that sense.

350
00:21:00.449 --> 00:21:02.949
<v Jonathan Bonner>Also having a more reliable.

351
00:21:04.439 --> 00:21:10.880
<v Jonathan Bonner>Operation, more reliable machinery, um, is
going to have a safe, uh, is going to

352
00:21:10.880 --> 00:21:17.300
<v Jonathan Bonner>give you a safer environment because now
you're not having Rather, the risk of

353
00:21:17.300 --> 00:21:20.569
<v Jonathan Bonner>something going wrong is a lot less
because you know what the condition is.

354
00:21:20.819 --> 00:21:26.680
<v Jonathan Bonner>You're not running to failure, where
failure could mean massive parts, snap, break,

355
00:21:27.619 --> 00:21:31.920
<v Jonathan Bonner>essentially explode because of pressures,
um, and temperatures and so on.

356
00:21:32.260 --> 00:21:36.780
<v Jonathan Bonner>You've been able to understand the
condition, do small little changes so that your

357
00:21:36.780 --> 00:21:39.140
<v Jonathan Bonner>machines are a lot more reliable and
therefore more safe.

358
00:21:40.329 --> 00:21:42.819
<v Speaker 3>Yeah, so it's as I said it, cos it's
unexpected as well.

359
00:21:42.859 --> 00:21:45.739
<v Speaker 3>You could have someone just standing next
to a machine and all of a sudden, if you

360
00:21:45.739 --> 00:21:48.180
<v Speaker 3>know what's happening with that machine,
you're monitoring that machine, and you,

361
00:21:48.420 --> 00:21:52.900
<v Speaker 3>and you know that machines are flagged to
you that potentially, you know, need some

362
00:21:52.900 --> 00:21:54.810
<v Speaker 3>attention, then you can plan that much
better.

363
00:21:55.180 --> 00:21:56.239
<v Jonathan Bonner>Yeah, absolutely.

364
00:21:56.540 --> 00:22:00.040
<v Jonathan Bonner>And with heavy industries, you don't get
many chances at safety.

365
00:22:00.859 --> 00:22:05.959
<v Jonathan Bonner>No, because, as I said, big machinery, big
products, um.

366
00:22:06.510 --> 00:22:10.780
<v Jonathan Bonner>When something goes wrong, it goes wrong
in a spectacular, spectacular way.

367
00:22:11.160 --> 00:22:16.479
<v Jonathan Bonner>Um, I've been privileged enough to work in
a, a wide range of factories and

368
00:22:16.479 --> 00:22:18.020
<v Jonathan Bonner>industries all over the world.

369
00:22:18.520 --> 00:22:22.079
<v Jonathan Bonner>And I've only seen it go wrong a few
times, but when it happens, it's extremely

370
00:22:22.079 --> 00:22:24.339
<v Jonathan Bonner>scary and extremely dangerous.

371
00:22:25.089 --> 00:22:29.890
<v Jonathan Bonner>Um, if you look at in certain areas, let's
say that have a, an ATex requirement, so

372
00:22:29.890 --> 00:22:32.150
<v Jonathan Bonner>they are hazardous for explosions.

373
00:22:33.010 --> 00:22:36.670
<v Jonathan Bonner>When something goes wrong, it goes wrong
very, very badly.

374
00:22:36.969 --> 00:22:42.760
<v Jonathan Bonner>Um, environments, even an environment that
just has dust, powders, sugars in the air

375
00:22:43.290 --> 00:22:47.729
<v Jonathan Bonner>can cause massive explosion risks and when
it does go up, it goes up in a huge,

376
00:22:47.849 --> 00:22:51.069
<v Jonathan Bonner>huge, huge, um, ball of fire, really.

377
00:22:51.500 --> 00:22:56.660
<v Jonathan Bonner>And anyone who's sitting or standing or
around that anywhere close is in massive

378
00:22:56.660 --> 00:22:59.689
<v Jonathan Bonner>risk of, you know, fatal injury because of
that.

379
00:23:00.020 --> 00:23:01.260
<v Jonathan Bonner>And that's just one example.

380
00:23:01.380 --> 00:23:05.459
<v Jonathan Bonner>In a heavy industry environment, there are
millions, millions of things that could

381
00:23:05.459 --> 00:23:09.780
<v Jonathan Bonner>go wrong and millions of things that could
be fatally damaging, really.

382
00:23:10.589 --> 00:23:14.479
<v Speaker 3>No, exactly, and, and I really liked how
you sort of articulated how, you know,

383
00:23:14.709 --> 00:23:17.609
<v Speaker 3>throughout all the outcomes we usually
talk about, they actually lead to, you know,

384
00:23:18.189 --> 00:23:22.390
<v Speaker 3>being, you know, of a safe working
environment for maintenance people, which, it was

385
00:23:22.390 --> 00:23:22.949
<v Speaker 3>fantastic.

386
00:23:23.150 --> 00:23:27.430
<v Speaker 3>So I just want to shift gears and talk a
little bit about return on investment, and

387
00:23:27.430 --> 00:23:31.109
<v Speaker 3>within heavy industry, and I know, you
know, knowing our customers, we've, we've

388
00:23:31.109 --> 00:23:32.390
<v Speaker 3>seen lots of successes.

389
00:23:32.430 --> 00:23:35.010
<v Speaker 3>We could maybe talk through some of that
as well.

390
00:23:35.390 --> 00:23:39.310
<v Speaker 3>Um, you know, how quickly, you know,
organizations should expect to see a return on

391
00:23:39.310 --> 00:23:40.969
<v Speaker 3>investment, maybe in heavy industry as
well.

392
00:23:41.349 --> 00:23:44.829
<v Speaker 3>Um, and of course, we've got a very
successful, well, many successful customers, but

393
00:23:44.829 --> 00:23:48.030
<v Speaker 3>Blue Scope Steel is one that sticks in my
mind because I've spoken to them quite a

394
00:23:48.030 --> 00:23:51.530
<v Speaker 3>lot, quite a few podcast episodes, but,
um, to look out for.

395
00:23:51.949 --> 00:23:56.650
<v Speaker 3>Um, and we might even link to them in the,
in, in the, um, show notes as well.

396
00:23:57.109 --> 00:23:58.979
<v Speaker 3>But yeah, so we start on investment.

397
00:23:59.430 --> 00:24:01.910
<v Speaker 3>What, what does that look like from a
heavy industry point of view?

398
00:24:02.430 --> 00:24:06.800
<v Jonathan Bonner>Well, for us to calculate return on
investment or even project what a return on

399
00:24:06.800 --> 00:24:09.109
<v Jonathan Bonner>investment can be, there's a number of
factors we look at.

400
00:24:09.339 --> 00:24:11.890
<v Jonathan Bonner>The first is the cost of downtime.

401
00:24:12.270 --> 00:24:16.270
<v Jonathan Bonner>So this could be production loss, again,
heavy industry, big products.

402
00:24:16.979 --> 00:24:20.819
<v Jonathan Bonner>That could be tens of thousands, hundreds
of thousands, millions an hour.

403
00:24:21.300 --> 00:24:24.849
<v Jonathan Bonner>So an hour loss of production could cost
you quite a lot.

404
00:24:25.459 --> 00:24:29.400
<v Jonathan Bonner>Then there is the breakdown cost, the
actual machinery which has failed.

405
00:24:29.780 --> 00:24:32.380
<v Jonathan Bonner>You know, is it a simple component
replacement?

406
00:24:32.540 --> 00:24:34.079
<v Jonathan Bonner>Do you have to replace the whole thing?

407
00:24:34.579 --> 00:24:40.020
<v Jonathan Bonner>Is it a specialized machine that you need
to get shipped in, um, or that has a 12

408
00:24:40.020 --> 00:24:41.209
<v Jonathan Bonner>month lead time?

409
00:24:41.699 --> 00:24:45.660
<v Jonathan Bonner>All with costs, uh, all with costs
involved or associated with those.

410
00:24:46.319 --> 00:24:50.560
<v Jonathan Bonner>There's also planned maintenance
efficiency, so a reduction in your scheduled

411
00:24:50.560 --> 00:24:51.800
<v Jonathan Bonner>calendar events.

412
00:24:52.359 --> 00:24:57.719
<v Jonathan Bonner>And then there's a reduction in spares
used during various maintenance types.

413
00:24:58.709 --> 00:25:02.540
<v Jonathan Bonner>So that's how we look at driving value and
return on investment.

414
00:25:02.949 --> 00:25:07.469
<v Jonathan Bonner>But with heavy industry, because, again,
heavy machines, heavy products, just saving

415
00:25:07.469 --> 00:25:08.150
<v Jonathan Bonner>one event.

416
00:25:09.030 --> 00:25:11.930
<v Jonathan Bonner>can have huge impact and definitely ROI.

417
00:25:12.709 --> 00:25:19.569
<v Jonathan Bonner>So, One of the fastest ROIs that I
remember looking at from team in SETA is,

418
00:25:19.859 --> 00:25:24.739
<v Jonathan Bonner>uh, uh, it happened over 2 weeks after the
deployment.

419
00:25:24.780 --> 00:25:27.969
<v Jonathan Bonner>So within 2 weeks they had a return on
investment from one event.

420
00:25:28.420 --> 00:25:32.140
<v Jonathan Bonner>So it just so happened it took 2 weeks
before something interesting happened and we

421
00:25:32.140 --> 00:25:34.839
<v Jonathan Bonner>were able to notify and get resolved.

422
00:25:35.260 --> 00:25:37.989
<v Jonathan Bonner>But it was one event that saved millions
of euros.

423
00:25:38.900 --> 00:25:44.060
<v Jonathan Bonner>Heavy industry, one event could be life
changing, essentially when you, when you

424
00:25:44.060 --> 00:25:45.800
<v Jonathan Bonner>start to look at return on investments.

425
00:25:46.339 --> 00:25:51.160
<v Jonathan Bonner>But typically when we're calculating the
potential, we're trying to project what

426
00:25:51.160 --> 00:25:52.359
<v Jonathan Bonner>return on investment can be.

427
00:25:52.819 --> 00:25:56.819
<v Jonathan Bonner>We're looking to, to have that anywhere
between 6 and 8 months.

428
00:25:57.660 --> 00:25:59.290
<v Jonathan Bonner>Um, maximum 12 months.

429
00:25:59.790 --> 00:26:02.209
<v Jonathan Bonner>And the way that we do that is to target
the value.

430
00:26:02.589 --> 00:26:07.219
<v Jonathan Bonner>So, yes, in, in certain circumstances,
that is looking at the critical equipment,

431
00:26:07.550 --> 00:26:11.770
<v Jonathan Bonner>you know, the ones that if something were
to go down, it would have huge financial

432
00:26:11.770 --> 00:26:12.500
<v Jonathan Bonner>uh impact.

433
00:26:12.869 --> 00:26:14.180
<v Jonathan Bonner>We would want to monitor those.

434
00:26:14.630 --> 00:26:19.369
<v Jonathan Bonner>But also the ones that are having, uh,
impact, uh, because of lack of reliability.

435
00:26:19.750 --> 00:26:22.989
<v Jonathan Bonner>The ones that are causing you unplanned
downtime events that are stopping

436
00:26:22.989 --> 00:26:27.920
<v Jonathan Bonner>production, that are halting your You
know, your process of making stuff that makes

437
00:26:27.920 --> 00:26:28.859
<v Jonathan Bonner>your company money.

438
00:26:29.430 --> 00:26:34.359
<v Jonathan Bonner>So that's how we would do it, but
typically we would expect it to be months to

439
00:26:34.359 --> 00:26:40.500
<v Jonathan Bonner>achieve ROI, um, and I believe With some
of our heavier clients.

440
00:26:41.300 --> 00:26:45.890
<v Jonathan Bonner>Within the first year, you're looking at
about a 10 times ROI typically speaking.

441
00:26:46.869 --> 00:26:50.670
<v Speaker 3>Yeah, it's amazing, you know, it's like I
said, I mean, we haven't talked about it

442
00:26:50.670 --> 00:26:55.099
<v Speaker 3>too much, but in terms of even like
production stopping, you know, if you're not, if

443
00:26:55.099 --> 00:26:59.069
<v Speaker 3>you're not making, um, material, then
you're not making money, right, and that's,

444
00:26:59.189 --> 00:27:01.670
<v Speaker 3>that's such key aspects of it, yeah,
keeping things

445
00:27:01.670 --> 00:27:02.069
<v Jonathan Bonner>running.

446
00:27:02.550 --> 00:27:07.250
<v Jonathan Bonner>Absolutely, and also if you look at the,
the metals environment, if you have a stop

447
00:27:07.469 --> 00:27:11.270
<v Jonathan Bonner>at some point in the, in the production,
uh, or processing of it.

448
00:27:12.199 --> 00:27:17.339
<v Jonathan Bonner>You could have scrap, scrap that needs to
be reworked or actually just scrap.

449
00:27:17.670 --> 00:27:22.599
<v Jonathan Bonner>Um, and in certain circumstances, I
remember a customer of ours, we gave them a

450
00:27:22.599 --> 00:27:27.989
<v Jonathan Bonner>notification which allowed them to do a
simple adjustment on rollers, just got metal

451
00:27:27.989 --> 00:27:28.719
<v Jonathan Bonner>running through it.

452
00:27:28.989 --> 00:27:34.719
<v Jonathan Bonner>They did a simple adjustment and they
saved, I believe it was 20 kilometers of sheet

453
00:27:34.719 --> 00:27:35.189
<v Jonathan Bonner>metal.

454
00:27:35.800 --> 00:27:36.739
<v Jonathan Bonner>One notification.

455
00:27:37.479 --> 00:27:37.839
<v Jonathan Bonner>Yeah.

456
00:27:38.349 --> 00:27:42.209
<v Jonathan Bonner>So there's lots of factors where value can
be derived with predictive maintenance,

457
00:27:42.469 --> 00:27:47.150
<v Jonathan Bonner>but unplanned downtime or reducing that,
reducing planned maintenance, reducing your

458
00:27:47.150 --> 00:27:53.780
<v Jonathan Bonner>scrap and rework, and reducing spares all
go to drive a, a, a tidy profit, well,

459
00:27:54.150 --> 00:27:55.109
<v Jonathan Bonner>return on investment anyway.

460
00:27:56.099 --> 00:27:59.339
<v Speaker 3>And I think again something you referred
to earlier is about capturing these

461
00:27:59.339 --> 00:28:02.589
<v Speaker 3>successes as well and sharing them
internally because there's nothing more, you

462
00:28:02.589 --> 00:28:06.050
<v Speaker 3>know, I, you know, look, well this is just
saved, how much money this has saved, I

463
00:28:06.050 --> 00:28:09.510
<v Speaker 3>mean, for everyone loves a good, you know,
a good win story, right?

464
00:28:09.689 --> 00:28:10.219
<v Speaker 3>Yeah, so

465
00:28:10.670 --> 00:28:14.780
<v Jonathan Bonner>yeah, and that's why we have the ability
to capture those metrics in the

466
00:28:14.780 --> 00:28:14.910
<v Jonathan Bonner>application.

467
00:28:15.609 --> 00:28:21.040
<v Jonathan Bonner>You know, carbon saved, downtime avoided,
uh, scrap rework saved, machine parts

468
00:28:21.040 --> 00:28:21.640
<v Jonathan Bonner>saved, and so on.

469
00:28:21.689 --> 00:28:22.770
<v Jonathan Bonner>We can capture all of those.

470
00:28:23.550 --> 00:28:29.050
<v Jonathan Bonner>But with our customer success department,
we also go through a hefty process of

471
00:28:29.550 --> 00:28:33.349
<v Jonathan Bonner>capturing the wins, um, taking the
maintenance events that have been added in,

472
00:28:33.510 --> 00:28:38.510
<v Jonathan Bonner>speaking to the people who have captured
these, um, creating slides, creating

473
00:28:38.510 --> 00:28:43.750
<v Jonathan Bonner>material, creating these, uh, playbooks so
that we, the customer themselves can use

474
00:28:43.750 --> 00:28:46.910
<v Jonathan Bonner>this internally to say, hey, you know this
project we've been running?

475
00:28:46.979 --> 00:28:48.060
<v Jonathan Bonner>Well, look at how good it's been.

476
00:28:48.189 --> 00:28:50.920
<v Jonathan Bonner>Look at all of these in-depth successes.

477
00:28:51.329 --> 00:28:56.020
<v Jonathan Bonner>That have absolutely saved us money, time,
and, you know, made us a lot more

478
00:28:56.020 --> 00:28:56.420
<v Jonathan Bonner>efficient.

479
00:28:57.589 --> 00:29:02.550
<v Speaker 3>Yeah, it's, yeah, and it, of course, it's
a key part of and it's also a key part of

480
00:29:02.550 --> 00:29:06.229
<v Speaker 3>that, you know, scale process because you
could go to each site and say, well, look

481
00:29:06.229 --> 00:29:07.589
<v Speaker 3>at the successes we've had over here.

482
00:29:07.949 --> 00:29:10.319
<v Speaker 3>That old fear of missing out type concept,
right?

483
00:29:10.520 --> 00:29:11.310
<v Jonathan Bonner>Absolutely.

484
00:29:11.670 --> 00:29:14.589
<v Jonathan Bonner>We, we try not to play sites against each
other.

485
00:29:15.150 --> 00:29:17.494
<v Jonathan Bonner>It does work in our Advantage every now
and then.

486
00:29:17.744 --> 00:29:18.775
<v Jonathan Bonner>Healthy competition.

487
00:29:19.025 --> 00:29:22.305
<v Speaker 3>Well, it is a, well, it's like, yeah, I, I
completely understand that because

488
00:29:22.305 --> 00:29:25.425
<v Speaker 3>everyone wants to see, oh, you're seeing
success, maybe we could see the same

489
00:29:25.425 --> 00:29:27.905
<v Speaker 3>success and it just builds that momentum
internally.

490
00:29:27.944 --> 00:29:31.505
<v Speaker 3>I mean, maybe we could talk about that
actually, in terms of momentum behind the

491
00:29:31.505 --> 00:29:31.744
<v Speaker 3>project.

492
00:29:31.905 --> 00:29:33.984
<v Speaker 3>I mean, I guess that's important as well.

493
00:29:34.104 --> 00:29:37.185
<v Speaker 3>Keep the winds coming through, keep the
engagement coming through, and it's sort of

494
00:29:37.185 --> 00:29:41.305
<v Speaker 3>a self-fulfilling process if it keep, you
know, the momentum's there, the winds are

495
00:29:41.305 --> 00:29:45.025
<v Speaker 3>there, it's only going to grow, build
momentum, scale, etc.

496
00:29:45.479 --> 00:29:46.930
<v Jonathan Bonner>Yeah, absolutely.

497
00:29:47.079 --> 00:29:49.699
<v Jonathan Bonner>And that's why we make sure we have the
right people.

498
00:29:49.920 --> 00:29:54.180
<v Jonathan Bonner>We make sure that we're targeting value
and that we're capturing the success because

499
00:29:54.319 --> 00:29:56.180
<v Jonathan Bonner>you need to keep the momentum going.

500
00:29:56.599 --> 00:30:02.880
<v Jonathan Bonner>You know, uh, any digitization project,
specifically PDM, it doesn't just happen

501
00:30:02.880 --> 00:30:03.469
<v Jonathan Bonner>overnight.

502
00:30:03.719 --> 00:30:06.439
<v Jonathan Bonner>It's not like you install some sensors and
boom, it's done.

503
00:30:06.839 --> 00:30:08.680
<v Jonathan Bonner>It is a full process.

504
00:30:08.790 --> 00:30:13.239
<v Jonathan Bonner>It can take weeks and months to
investigate, implement, you know, uh, get data

505
00:30:13.239 --> 00:30:16.780
<v Jonathan Bonner>integrations together, get people trained,
using it.

506
00:30:17.000 --> 00:30:18.739
<v Jonathan Bonner>It's a very iterative.

507
00:30:19.780 --> 00:30:24.130
<v Jonathan Bonner>Process of getting the customer involved,
engaged, getting it set up, getting and

508
00:30:24.130 --> 00:30:29.349
<v Jonathan Bonner>using it, and then driving success, you
know, at least just trying to get the users

509
00:30:29.349 --> 00:30:30.449
<v Jonathan Bonner>to capture the success.

510
00:30:31.130 --> 00:30:34.369
<v Jonathan Bonner>Um, but we do that continuously.

511
00:30:34.449 --> 00:30:38.680
<v Jonathan Bonner>We're there to support our customers
continuously because of that momentum.

512
00:30:38.969 --> 00:30:43.290
<v Jonathan Bonner>We don't want anyone to get frustrated or,
you know, disheartened because it's

513
00:30:43.290 --> 00:30:47.689
<v Jonathan Bonner>taking longer than they expected and, um,
you know, they, they, they just want to

514
00:30:47.689 --> 00:30:48.469
<v Jonathan Bonner>give it up now.

515
00:30:48.969 --> 00:30:52.849
<v Jonathan Bonner>We want to keep that momentum going, and
yes, there are hurdles, but hurdles aren't

516
00:30:52.849 --> 00:30:53.300
<v Jonathan Bonner>a problem.

517
00:30:53.410 --> 00:30:57.489
<v Jonathan Bonner>You can jump straight over them and keep
the momentum going as long as you're there

518
00:30:57.489 --> 00:30:59.650
<v Jonathan Bonner>to support the customer, and that's what
we do.

519
00:31:01.160 --> 00:31:05.439
<v Speaker 3>And I guess, because we hadn't touched
upon sort of AI and, and, well, Gen AI

520
00:31:05.439 --> 00:31:09.189
<v Speaker 3>obviously and co-pilots are a huge topic
at the moment, but how are they sort of

521
00:31:09.189 --> 00:31:15.079
<v Speaker 3>helping with adoption within, um, within
heavy industries and, and unders you know,

522
00:31:15.319 --> 00:31:18.319
<v Speaker 3>and again, uh, the point I was originally
gonna make actually is, you know, when

523
00:31:18.319 --> 00:31:22.670
<v Speaker 3>people hear AI they think, oh, turn it on,
it's magic, and off it goes, kind of

524
00:31:22.670 --> 00:31:22.719
<v Speaker 3>thing.

525
00:31:22.790 --> 00:31:25.319
<v Speaker 3>So we could talk a little bit about that,
but I'm more interested in sort of how

526
00:31:25.319 --> 00:31:29.239
<v Speaker 3>that's helping people to understand these
technologies and, and use them in.

527
00:31:29.579 --> 00:31:31.400
<v Speaker 3>The, you know, the right way to get
results.

528
00:31:32.109 --> 00:31:34.540
<v Jonathan Bonner>Uh, to be honest, it's been, it's been
absolutely amazing.

529
00:31:35.339 --> 00:31:41.380
<v Jonathan Bonner>First of all, it's making the information
which really you should have had, or you

530
00:31:41.380 --> 00:31:46.099
<v Jonathan Bonner>required some sort of condition
monitoring, data analytics experience for.

531
00:31:46.420 --> 00:31:50.699
<v Jonathan Bonner>It's making that information accessible to
everyone because now you don't need to

532
00:31:50.699 --> 00:31:54.900
<v Jonathan Bonner>understand measures, what the measures
mean, what the patterns mean, that there is a

533
00:31:54.900 --> 00:31:55.380
<v Jonathan Bonner>pattern.

534
00:31:55.829 --> 00:31:59.910
<v Jonathan Bonner>Uh, this information is being presented to
you in your natural language.

535
00:32:01.520 --> 00:32:06.920
<v Jonathan Bonner>With the Sensai co-pilot, it's also then
making recommendations based off of the

536
00:32:06.920 --> 00:32:08.280
<v Jonathan Bonner>measure, what the measure is doing.

537
00:32:08.339 --> 00:32:13.719
<v Jonathan Bonner>It has a condition monitoring,
reliability, maintenance knowledge inherently uh

538
00:32:13.869 --> 00:32:14.869
<v Jonathan Bonner>embedded within it.

539
00:32:15.160 --> 00:32:19.400
<v Jonathan Bonner>So it's understanding the data from a
condition monitoring perspective, can make

540
00:32:19.400 --> 00:32:25.560
<v Jonathan Bonner>recommendations, and then still use all of
your historic events, maintenance events,

541
00:32:25.760 --> 00:32:28.839
<v Jonathan Bonner>notes, uh, feedbacks, case closures.

542
00:32:29.180 --> 00:32:32.959
<v Jonathan Bonner>And can bring that past experience into
the present case.

543
00:32:33.750 --> 00:32:39.069
<v Jonathan Bonner>So it is acting like a reliability or
condition monitoring engineer who knows this

544
00:32:39.069 --> 00:32:41.209
<v Jonathan Bonner>machine from the moment it was on boarded.

545
00:32:41.630 --> 00:32:47.030
<v Jonathan Bonner>Every bit of data, every pattern, every
maintenance event, and can make or bring

546
00:32:47.030 --> 00:32:51.609
<v Jonathan Bonner>that information to the user as it relates
to what is happening now.

547
00:32:52.550 --> 00:32:57.939
<v Jonathan Bonner>But With our co-pilot, we can then add in
that expert knowledge, the documentation I

548
00:32:57.939 --> 00:32:58.959
<v Jonathan Bonner>was talking about earlier.

549
00:32:59.339 --> 00:33:04.739
<v Jonathan Bonner>So you can upload these and pretty much
instantly have reference or have access to

550
00:33:04.739 --> 00:33:05.540
<v Jonathan Bonner>this information.

551
00:33:06.239 --> 00:33:07.489
<v Jonathan Bonner>Um, just by asking.

552
00:33:07.839 --> 00:33:11.589
<v Jonathan Bonner>So with a few prompts, you have access to
the user manual, the maintenance manuals,

553
00:33:11.920 --> 00:33:13.219
<v Jonathan Bonner>the spare parts lists.

554
00:33:13.520 --> 00:33:17.319
<v Jonathan Bonner>So if you want to find out what the, the
code is for a drive and bearing, just ask

555
00:33:17.319 --> 00:33:18.079
<v Jonathan Bonner>it, it's there.

556
00:33:18.359 --> 00:33:22.079
<v Jonathan Bonner>And it can reference this information and
make it available to everyone.

557
00:33:22.989 --> 00:33:27.560
<v Jonathan Bonner>And because it works in every language, it
helps global organizations to

558
00:33:27.560 --> 00:33:28.079
<v Jonathan Bonner>collaborate.

559
00:33:28.680 --> 00:33:31.500
<v Jonathan Bonner>It doesn't matter what language the the
manual is in.

560
00:33:31.760 --> 00:33:32.880
<v Jonathan Bonner>Is it in Cantonese?

561
00:33:32.969 --> 00:33:33.719
<v Jonathan Bonner>Is it in German?

562
00:33:33.939 --> 00:33:34.670
<v Jonathan Bonner>It doesn't matter.

563
00:33:35.000 --> 00:33:37.920
<v Jonathan Bonner>You can speak to it and reference it in
your natural language.

564
00:33:38.319 --> 00:33:39.140
<v Jonathan Bonner>Fantastic.

565
00:33:39.560 --> 00:33:44.319
<v Jonathan Bonner>Um, but it also makes maintenance teams
around the world or gives them the ability

566
00:33:44.319 --> 00:33:49.520
<v Jonathan Bonner>to collaborate because again, you can
speak your natural language and the co-pilot

567
00:33:49.520 --> 00:33:53.989
<v Jonathan Bonner>is continuously learning from all of these
events, from the knowledge, from the

568
00:33:53.989 --> 00:33:56.920
<v Jonathan Bonner>conversations, from the users and the
experts you have on site.

569
00:33:57.420 --> 00:34:02.180
<v Jonathan Bonner>It is learning from them, and when you
have a global organization set up, it is then

570
00:34:02.180 --> 00:34:03.650
<v Jonathan Bonner>benefiting everyone.

571
00:34:05.030 --> 00:34:08.439
<v Speaker 3>And I guess we could also, because we're
taking, I mean, the product's, you know,

572
00:34:08.489 --> 00:34:11.439
<v Speaker 3>yeah, well, it's come a long way over the
past, you know, 4 years I've been with

573
00:34:11.439 --> 00:34:15.719
<v Speaker 3>Sens I now Siemens, but, you know, in the
past sort of 12 to 18 months, it's, it's

574
00:34:15.719 --> 00:34:18.679
<v Speaker 3>really accelerated, and particularly, it's
interesting you mentioned the

575
00:34:18.679 --> 00:34:21.919
<v Speaker 3>collaboration piece as well, because not
only is the co-pilot enabling that, we've

576
00:34:21.919 --> 00:34:24.500
<v Speaker 3>also got things like app mentions coming
into the.

577
00:34:24.780 --> 00:34:27.620
<v Speaker 3>The app now where you can just bring
someone into the loop, you can upload a picture

578
00:34:27.620 --> 00:34:31.300
<v Speaker 3>and say, oh, look at this, I saw this, and
you can say that to your mate, your

579
00:34:31.300 --> 00:34:33.679
<v Speaker 3>colleague all the way on the other side of
the world.

580
00:34:34.020 --> 00:34:36.300
<v Speaker 3>So connecting these, these colleagues
together.

581
00:34:36.500 --> 00:34:36.939
<v Speaker 3>Absolutely,

582
00:34:37.060 --> 00:34:39.340
<v Jonathan Bonner>yeah, it's becoming a lot more about
collaboration.

583
00:34:40.570 --> 00:34:44.310
<v Jonathan Bonner>You know, uh, a few years ago, it was
about machine learning.

584
00:34:44.449 --> 00:34:45.560
<v Jonathan Bonner>What is the machine doing?

585
00:34:45.659 --> 00:34:49.959
<v Jonathan Bonner>Understanding the data, the condition
monitoring part of it, let's say, or the

586
00:34:49.959 --> 00:34:51.030
<v Jonathan Bonner>automation of that at least.

587
00:34:51.870 --> 00:34:56.689
<v Jonathan Bonner>But now with the co-pilots, without in at
in at mentions.

588
00:34:57.629 --> 00:34:58.830
<v Jonathan Bonner>It is about collaboration.

589
00:34:58.949 --> 00:35:01.810
<v Jonathan Bonner>It's about learning from a lot more than
time series data.

590
00:35:02.350 --> 00:35:05.070
<v Jonathan Bonner>It's taking in many more inputs.

591
00:35:05.939 --> 00:35:10.590
<v Jonathan Bonner>As I've said, your, uh, documentation,
maintenance event information, human

592
00:35:10.590 --> 00:35:14.000
<v Jonathan Bonner>feedback, um, conversations that you're
having.

593
00:35:14.110 --> 00:35:19.110
<v Jonathan Bonner>So now, me and you working on the same
problem, even if we are, um, continents

594
00:35:19.110 --> 00:35:25.989
<v Jonathan Bonner>apart, we can collaborate on this and it's
all being there, stored and being used in

595
00:35:25.989 --> 00:35:28.530
<v Jonathan Bonner>the future when it's relevant and
necessary.

596
00:35:29.169 --> 00:35:33.350
<v Speaker 3>Um, not only store, but again it can be
raised again in future, so people leave

597
00:35:33.350 --> 00:35:35.280
<v Speaker 3>organizations or, you know, move to
different roles.

598
00:35:35.530 --> 00:35:36.850
<v Speaker 3>The knowledge is still there.

599
00:35:37.199 --> 00:35:41.129
<v Speaker 3>All it takes is someone to ask the
question again, oh yeah, we had this previous

600
00:35:41.129 --> 00:35:41.530
<v Speaker 3>case.

601
00:35:41.860 --> 00:35:43.780
<v Speaker 3>And then comparing to previous cases.

602
00:35:43.899 --> 00:35:48.580
<v Jonathan Bonner>Yeah, uh, honestly, every environment that
I've been in, every single one, they've

603
00:35:48.580 --> 00:35:49.979
<v Jonathan Bonner>all had that Dave.

604
00:35:50.179 --> 00:35:54.179
<v Jonathan Bonner>Dave's been there for 30 years, he knows
the machines, he can walk around and hear

605
00:35:54.179 --> 00:35:58.020
<v Jonathan Bonner>when something's off, he can put his, you
know, screwdriver to the ear and listen

606
00:35:58.020 --> 00:36:02.659
<v Jonathan Bonner>and go, yeah, OK, this is a a variant
going or we need to grease this or whatever it

607
00:36:02.659 --> 00:36:03.199
<v Jonathan Bonner>may be.

608
00:36:03.860 --> 00:36:09.229
<v Jonathan Bonner>But when Dave leaves, you know,
retirement, sickness, new job, whatever the reason.

609
00:36:09.850 --> 00:36:14.770
<v Jonathan Bonner>That knowledge is lost, you know, that
proper in-depth experience and expertise is

610
00:36:14.770 --> 00:36:14.989
<v Jonathan Bonner>lost.

611
00:36:15.989 --> 00:36:21.280
<v Jonathan Bonner>Um, and We don't have as much of an inflow
of apprentices and up and coming

612
00:36:21.280 --> 00:36:26.100
<v Jonathan Bonner>maintainers, uh, engineers as we should
really, and this is a global factor.

613
00:36:26.699 --> 00:36:32.570
<v Jonathan Bonner>So, If you have the Daves of the world,
the real experience, decades and decades of

614
00:36:32.570 --> 00:36:38.409
<v Jonathan Bonner>expert knowledge leaving and not enough
people filling in that gap coming in, it

615
00:36:38.409 --> 00:36:41.449
<v Jonathan Bonner>does leave a hole, a hole that needs to be
filled.

616
00:36:41.770 --> 00:36:47.449
<v Jonathan Bonner>And with the, the co-pilots, with the Gen
AI functionality, it's retaining that

617
00:36:47.449 --> 00:36:50.850
<v Jonathan Bonner>expert knowledge forever, making it
referenced forever.

618
00:36:52.340 --> 00:36:56.100
<v Speaker 3>And I guess, yeah, so as we come to sort
of, you know, the final question, and

619
00:36:56.100 --> 00:36:59.159
<v Speaker 3>usually this, well, there's usually two
things actually, it's maybe like the final,

620
00:36:59.179 --> 00:37:03.100
<v Speaker 3>final question, the final question before
the final question, but, um, so we usually

621
00:37:03.100 --> 00:37:05.840
<v Speaker 3>finish by sort of a summary of key
takeaways and things, but.

622
00:37:06.169 --> 00:37:10.850
<v Speaker 3>And the other question we, we also ask
quite commonly is, so, what, what's next for

623
00:37:10.850 --> 00:37:14.570
<v Speaker 3>predictive maintenance and what's next,
obviously in the context of heavy industry,

624
00:37:14.729 --> 00:37:17.070
<v Speaker 3>but maybe we're talking about that more
collaboration.

625
00:37:17.169 --> 00:37:19.520
<v Speaker 3>I don't want to put words into your mouth,
but that seems like the way we're going,

626
00:37:19.570 --> 00:37:25.000
<v Speaker 3>predictive maintenance is a team game, but
not just your team here in this, on this

627
00:37:25.000 --> 00:37:26.649
<v Speaker 3>site, but a global team.

628
00:37:26.810 --> 00:37:27.060
<v Speaker 3>Yeah.

629
00:37:27.770 --> 00:37:29.270
<v Speaker 3>But maybe you've got other thoughts as
well.

630
00:37:29.689 --> 00:37:31.709
<v Jonathan Bonner>What, what's next for predictive
maintenance?

631
00:37:33.280 --> 00:37:38.000
<v Jonathan Bonner>I definitely see a change in our
activities.

632
00:37:38.949 --> 00:37:40.330
<v Jonathan Bonner>Meaning more of them.

633
00:37:40.709 --> 00:37:45.510
<v Jonathan Bonner>There are, there is definitely a driver
from all industries, but very much heavy

634
00:37:45.510 --> 00:37:50.629
<v Jonathan Bonner>industry as well, a driver to get these
system solutions in place so people can

635
00:37:50.629 --> 00:37:52.550
<v Jonathan Bonner>start benefiting from it.

636
00:37:53.189 --> 00:37:58.610
<v Jonathan Bonner>But it's also in conjunction with other
initiatives, OEE energy management.

637
00:37:59.250 --> 00:38:00.239
<v Jonathan Bonner>Digital twin.

638
00:38:00.510 --> 00:38:05.760
<v Jonathan Bonner>So I'm seeing a lot more cross-portfolio
collaboration so that what customers are

639
00:38:05.760 --> 00:38:10.350
<v Jonathan Bonner>receiving is not just one thing,
predictive maintenance, which on its own is

640
00:38:10.350 --> 00:38:17.159
<v Jonathan Bonner>fantastic, but rather a wholesale change
backed by data, backed by information which

641
00:38:17.159 --> 00:38:21.580
<v Jonathan Bonner>exists so that they can make better
decisions, that they can save money because

642
00:38:21.760 --> 00:38:23.149
<v Jonathan Bonner>budgets are tight all around.

643
00:38:23.520 --> 00:38:27.320
<v Jonathan Bonner>So if you can target value from multiple
avenues.

644
00:38:28.040 --> 00:38:32.280
<v Jonathan Bonner>Essentially using one data stream, really,
and that's what we're, what we're doing

645
00:38:32.280 --> 00:38:32.830
<v Jonathan Bonner>nowadays.

646
00:38:33.080 --> 00:38:35.649
<v Jonathan Bonner>Um, it has massive benefits and value on
site.

647
00:38:35.800 --> 00:38:40.030
<v Jonathan Bonner>So that's where I see it's, it's around
further adoption, but collaboration with

648
00:38:40.030 --> 00:38:45.000
<v Jonathan Bonner>other systems like OEE Energy management,
digital twin, and so on.

649
00:38:45.949 --> 00:38:49.270
<v Speaker 3>Yeah, and I guess you've, you've also sort
of summarized the last question I was

650
00:38:49.270 --> 00:38:53.110
<v Speaker 3>gonna ask in terms of, you know, next
steps that, you know, if, if there were, you

651
00:38:53.110 --> 00:38:56.149
<v Speaker 3>know, people within these industries are
thinking, yeah, actually this really does

652
00:38:56.149 --> 00:38:56.979
<v Speaker 3>resonate with me.

653
00:38:57.189 --> 00:39:00.389
<v Speaker 3>Predictor maintenance sounds like a great
use case, and probably no doubt it's

654
00:39:00.389 --> 00:39:03.629
<v Speaker 3>already on their radar already, they
probably know about predictor maintenance, what

655
00:39:03.629 --> 00:39:07.629
<v Speaker 3>it, what it can do, but if they really
wanted to get started with it tomorrow, John,

656
00:39:07.709 --> 00:39:11.469
<v Speaker 3>what, what would your, what should they be
thinking about to get in that mindset?

657
00:39:12.879 --> 00:39:14.580
<v Jonathan Bonner>Think about the use case.

658
00:39:14.870 --> 00:39:17.219
<v Jonathan Bonner>Think about what is it that I'm wanting to
achieve.

659
00:39:18.459 --> 00:39:23.739
<v Jonathan Bonner>If you have a downtime problem or you're
spending far too much time, money, effort,

660
00:39:24.100 --> 00:39:25.739
<v Jonathan Bonner>resource on planned maintenance.

661
00:39:26.580 --> 00:39:30.320
<v Jonathan Bonner>Then predictive maintenance is a good
avenue to, to look at.

662
00:39:30.860 --> 00:39:36.959
<v Jonathan Bonner>If you are having or if you have extremely
high bills, um, uh, due

663
00:39:36.959 --> 00:39:40.550
<v Jonathan Bonner>to energy, then maybe energy management is
the thing to go.

664
00:39:40.800 --> 00:39:42.399
<v Jonathan Bonner>So, essentially, look at the use case.

665
00:39:42.479 --> 00:39:44.459
<v Jonathan Bonner>Look at what you are trying to achieve.

666
00:39:45.719 --> 00:39:51.280
<v Jonathan Bonner>Look at where you can derive or drive
value, and then the solution will follow.

667
00:39:52.290 --> 00:39:56.419
<v Speaker 3>Yeah, don't just think about, you know, I
wanna install this or implement this um

668
00:39:56.719 --> 00:39:57.229
<v Speaker 3>new AI.

669
00:39:57.540 --> 00:40:00.399
<v Speaker 3>It's all, it sounds really cool and that
kind of thing.

670
00:40:00.639 --> 00:40:03.639
<v Speaker 3>You gotta think about the value it's gonna
bring to the to your business or

671
00:40:03.639 --> 00:40:03.659
<v Speaker 3>organization.

672
00:40:03.909 --> 00:40:04.340
<v Speaker 3>Absolutely.

673
00:40:04.909 --> 00:40:08.100
<v Jonathan Bonner>Now there are ways to get started which
don't require wholesale change.

674
00:40:09.129 --> 00:40:14.290
<v Jonathan Bonner>We, for example, have removed the, the
co-pilot's dependency on time series data.

675
00:40:14.770 --> 00:40:19.290
<v Jonathan Bonner>So now we have a maintenance co-pilot
essential package which works off of your

676
00:40:19.290 --> 00:40:24.139
<v Jonathan Bonner>data, your, sorry, your maintenance
manuals, your user manuals, spare parts lists,

677
00:40:24.250 --> 00:40:30.050
<v Jonathan Bonner>your expert documentation, and human
feedback, the conversations, the questions,

678
00:40:30.110 --> 00:40:31.409
<v Jonathan Bonner>it's learning from those.

679
00:40:31.770 --> 00:40:35.629
<v Jonathan Bonner>So there are ways to get started, which
don't require wholesale change.

680
00:40:36.350 --> 00:40:40.389
<v Jonathan Bonner>But my tip, my bit of advice is always
look at what is going to drive business

681
00:40:40.389 --> 00:40:43.909
<v Jonathan Bonner>value, what problems are you having,
what's gonna drive the value, and then the

682
00:40:43.909 --> 00:40:45.129
<v Jonathan Bonner>solution can come after that.

683
00:40:45.669 --> 00:40:45.939
<v Jonathan Bonner>Yeah,

684
00:40:46.189 --> 00:40:48.370
<v Speaker 3>always comes back to business value, of
course.

685
00:40:48.790 --> 00:40:52.870
<v Speaker 3>But um, but no, for today, thank you
Jonathan for joining us and sharing your

686
00:40:52.870 --> 00:40:53.489
<v Speaker 3>expertise.

687
00:40:53.830 --> 00:40:55.100
<v Speaker 3>Um, it's been great to chat again.

688
00:40:55.310 --> 00:40:56.810
<v Speaker 3>Hope to come back on again soon.

689
00:40:57.149 --> 00:40:57.610
<v Speaker 3>Thank you.

690
00:40:58.070 --> 00:41:01.989
<v Speaker 3>And thank you everyone for listening and
watching wherever you are, and we'll see

691
00:41:01.989 --> 00:41:02.989
<v Speaker 3>you on the next episode.

692
00:41:05.500 --> 00:41:10.459
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

693
00:41:10.459 --> 00:41:13.939
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
