WEBVTT
Language: en-US

1
00:00:02.230 --> 00:00:03.640
<v Tom Jacques>It's really important to see the assets.

2
00:00:03.680 --> 00:00:07.480
<v Tom Jacques>It's also really important to meet the
team and learn a little bit more about the

3
00:00:07.480 --> 00:00:07.920
<v Tom Jacques>culture.

4
00:00:08.210 --> 00:00:10.119
<v Tom Jacques>So, is, is this a proactive team?

5
00:00:10.279 --> 00:00:13.140
<v Tom Jacques>Is this a team who really just runs things
to failure?

6
00:00:13.600 --> 00:00:16.059
<v Tom Jacques>Because that, again, has an impact on the
business objective.

7
00:00:18.440 --> 00:00:19.149
<v Tom Jacques>Welcome to the

8
00:00:19.149 --> 00:00:24.219
<v Speaker 2>trend detection podcast powered by
Siemens, and now your host Nel Sullivan.

9
00:00:27.010 --> 00:00:30.629
<v Speaker 3>Hello and welcome to the latest episode of
the Trends section podcast.

10
00:00:31.049 --> 00:00:34.490
<v Speaker 3>I'm really pleased to be joined once again
by my colleague Tom, um, he's fast

11
00:00:34.490 --> 00:00:37.270
<v Speaker 3>becoming one of our most regular guests,
so welcome back, Tom.

12
00:00:37.889 --> 00:00:38.159
<v Speaker 3>Hello Noel.

13
00:00:40.090 --> 00:00:46.130
<v Speaker 3>Good to see you and hear you again, um,
and today we're talking about, um, a

14
00:00:46.130 --> 00:00:50.139
<v Speaker 3>slightly different topic I guess cos we
talk about a lot about predict mountains, of

15
00:00:50.139 --> 00:00:53.380
<v Speaker 3>course, and the details of the project,
but we, we don't often talk about how, you

16
00:00:53.380 --> 00:00:56.979
<v Speaker 3>know, the start of a project and actually
getting a predict mountains project up and

17
00:00:56.979 --> 00:00:57.340
<v Speaker 3>running.

18
00:00:57.959 --> 00:01:00.139
<v Speaker 3>Um, so yeah, so that's what we're gonna
cover today.

19
00:01:00.950 --> 00:01:04.589
<v Speaker 3>Um, but maybe Tom, just for those who
maybe haven't, um, listened to you on the

20
00:01:04.589 --> 00:01:06.970
<v Speaker 3>podcast before, maybe just a quick intro
from your side.

21
00:01:07.110 --> 00:01:07.540
<v Speaker 3>That'd be great.

22
00:01:07.650 --> 00:01:08.150
<v Speaker 3>Absolutely,

23
00:01:08.269 --> 00:01:08.470
<v Tom Jacques>yeah.

24
00:01:08.589 --> 00:01:09.389
<v Tom Jacques>So my name's Tom.

25
00:01:09.510 --> 00:01:13.330
<v Tom Jacques>Um, my job is solutions engineering for
Sensei Predictive maintenance within

26
00:01:13.330 --> 00:01:13.930
<v Tom Jacques>Siemens.

27
00:01:14.069 --> 00:01:18.709
<v Tom Jacques>Um, the real role is to try and understand
customer problems, um, mainly with a

28
00:01:18.709 --> 00:01:23.510
<v Tom Jacques>focus on, you know, anything to do with
downtime avoidance, um, prevention of

29
00:01:23.510 --> 00:01:23.830
<v Tom Jacques>certain.

30
00:01:24.110 --> 00:01:28.720
<v Tom Jacques>Um, mechanical component failures and so
on, and really bring this forward to a full

31
00:01:28.720 --> 00:01:32.559
<v Tom Jacques>scale project, um, and really understand
how we can help customers.

32
00:01:32.739 --> 00:01:33.559
<v Tom Jacques>That, that's what I'm here for.

33
00:01:35.209 --> 00:01:38.830
<v Speaker 3>Fantastic, so the the perfect person to
interview on this topic then.

34
00:01:39.129 --> 00:01:39.480
<v Speaker 3>OK.

35
00:01:40.510 --> 00:01:45.639
<v Speaker 3>Um, so let's just start first of all by,
um, taking sort of a broader look at

36
00:01:45.639 --> 00:01:45.919
<v Speaker 3>things.

37
00:01:46.040 --> 00:01:49.440
<v Speaker 3>So, um, we know that predictive
maintenance, and you'll know cause there's been so

38
00:01:49.440 --> 00:01:52.080
<v Speaker 3>many customers about the predictive
maintenance topic.

39
00:01:52.160 --> 00:01:53.660
<v Speaker 3>It's getting so much traction.

40
00:01:54.120 --> 00:01:56.669
<v Speaker 3>I mean, from your point of view, Tom,
what, you know, why, why predictive

41
00:01:56.669 --> 00:01:57.440
<v Speaker 3>maintenance in particular?

42
00:01:57.519 --> 00:01:59.580
<v Speaker 3>Why is that so in demand at the moment?

43
00:02:00.519 --> 00:02:01.360
<v Tom Jacques>This is a great question.

44
00:02:01.480 --> 00:02:01.599
<v Tom Jacques>Yes.

45
00:02:01.720 --> 00:02:05.559
<v Tom Jacques>So, at the moment, we're kind of in a new
phase, I would call it, of, of

46
00:02:05.559 --> 00:02:08.919
<v Tom Jacques>digitalization, where things like sensors
start to become cheaper.

47
00:02:09.059 --> 00:02:14.440
<v Tom Jacques>The ability to monitor a fully mechanical
system or even an electromechanical system

48
00:02:14.440 --> 00:02:15.529
<v Tom Jacques>is getting easier.

49
00:02:16.190 --> 00:02:20.520
<v Tom Jacques>And also the monitoring process, the likes
of Sensor now coming to the forefront

50
00:02:20.520 --> 00:02:22.779
<v Tom Jacques>with AI and lots of other features.

51
00:02:23.080 --> 00:02:28.839
<v Tom Jacques>It's, it's becoming cost effective and
simply enough, you know, as a plug and play

52
00:02:28.839 --> 00:02:29.139
<v Tom Jacques>solution.

53
00:02:29.869 --> 00:02:35.149
<v Tom Jacques>Um, for want of a better word at this
stage, to, to make it work, to pull data from

54
00:02:35.149 --> 00:02:39.839
<v Tom Jacques>a, from a system, understand how to
improve maintenance, make it work for you.

55
00:02:39.990 --> 00:02:44.020
<v Tom Jacques>Um, and I think just, yeah, that rise of,
of scalability, that rise of

56
00:02:44.020 --> 00:02:49.009
<v Tom Jacques>affordability, um, with the intelligence
in the background to make smart decisions.

57
00:02:49.369 --> 00:02:53.600
<v Tom Jacques>It's really now a reality and it, you
know, we've got customers who've been doing

58
00:02:53.600 --> 00:02:58.500
<v Tom Jacques>this for 5, 10 years, but we've got lots
of customers recently really coming to the

59
00:02:58.500 --> 00:03:00.460
<v Tom Jacques>forefront asking us how we can help them.

60
00:03:01.889 --> 00:03:06.649
<v Speaker 3>And, and do you see a shift in sort of
mindset away from thinking of predictive

61
00:03:06.649 --> 00:03:10.889
<v Speaker 3>maintenance initiative as like a cost on a
spreadsheet to an actual investment, like

62
00:03:10.889 --> 00:03:14.270
<v Speaker 3>you say, to save money and increase
productivity, for example.

63
00:03:15.580 --> 00:03:16.610
<v Tom Jacques>It definitely is.

64
00:03:16.820 --> 00:03:21.699
<v Tom Jacques>So you see it as an outgoing, of course,
it costs something to install the system to

65
00:03:21.699 --> 00:03:25.300
<v Tom Jacques>get it up and running, to connect all the
different components, set sensitivities of

66
00:03:25.300 --> 00:03:26.380
<v Tom Jacques>sensors and so on.

67
00:03:26.899 --> 00:03:31.139
<v Tom Jacques>And also to pull some context in so we can
understand what the motors, the pumps,

68
00:03:31.220 --> 00:03:35.860
<v Tom Jacques>the gearboxes, also non-rotating assets,
so things like hydraulic systems or

69
00:03:35.860 --> 00:03:38.039
<v Tom Jacques>coolers, understand what they're doing.

70
00:03:39.850 --> 00:03:42.869
<v Tom Jacques>Really, what you need to look at is how
does that have a business impact.

71
00:03:43.130 --> 00:03:45.199
<v Tom Jacques>So where does downtime cost you money?

72
00:03:45.389 --> 00:03:49.729
<v Tom Jacques>Where does over maintenance cost you
money, and sometimes companies don't have an

73
00:03:49.729 --> 00:03:51.039
<v Tom Jacques>oversight of those things.

74
00:03:51.410 --> 00:03:53.089
<v Tom Jacques>Um, so it just looks like an outgoing.

75
00:03:53.369 --> 00:03:58.130
<v Tom Jacques>and also part of my role is to help
understand how that's not the case and, and, and

76
00:03:58.130 --> 00:04:01.389
<v Tom Jacques>really how predictive maintenance can have
a really positive impact.

77
00:04:03.250 --> 00:04:08.889
<v Speaker 3>So actually, I guess that leads on uh
nicely to, you know, this question about, you

78
00:04:08.889 --> 00:04:12.210
<v Speaker 3>know, if predictive maintenance is
actually right for an organization, because I

79
00:04:12.210 --> 00:04:13.779
<v Speaker 3>guess there's many factors to consider.

80
00:04:13.889 --> 00:04:16.630
<v Speaker 3>So, you know, what are those factors, Tom,
from your point of view?

81
00:04:17.410 --> 00:04:19.320
<v Tom Jacques>I think start with a business problem.

82
00:04:19.570 --> 00:04:24.040
<v Tom Jacques>So, not really the technology, really
identify high impact areas.

83
00:04:24.649 --> 00:04:29.970
<v Tom Jacques>So, look to assess major losses when they
fail, look to see how leadership buy in

84
00:04:29.970 --> 00:04:34.010
<v Tom Jacques>and stakeholders are going to look at
this, how the IT team looks at, you know,

85
00:04:34.049 --> 00:04:35.489
<v Tom Jacques>cybersecurity topics.

86
00:04:35.890 --> 00:04:37.890
<v Tom Jacques>Can we allow data to flow to the cloud?

87
00:04:38.369 --> 00:04:40.850
<v Tom Jacques>You know, we're seeing more and more
customers allowing that to be the case.

88
00:04:41.089 --> 00:04:42.890
<v Tom Jacques>So we see a positive approach to this.

89
00:04:42.970 --> 00:04:48.290
<v Tom Jacques>We see a You know, an open mindedness
towards digitalization, digital transformation

90
00:04:48.290 --> 00:04:49.750
<v Tom Jacques>definitely taking place.

91
00:04:50.510 --> 00:04:52.570
<v Tom Jacques>Um, and then just how do we access the
data?

92
00:04:52.799 --> 00:04:56.570
<v Tom Jacques>So, you know, some of the key factors are,
have we got the data?

93
00:04:56.730 --> 00:04:58.480
<v Tom Jacques>Have we got the sensors that we're going
to need?

94
00:04:58.570 --> 00:05:02.269
<v Tom Jacques>And if you don't, if the customers that we
speak to don't have that, that's a part

95
00:05:02.269 --> 00:05:03.989
<v Tom Jacques>of the scope work that I do.

96
00:05:04.630 --> 00:05:08.649
<v Tom Jacques>Um, so we can try and build a process, get
customers to that stage of, you know,

97
00:05:08.790 --> 00:05:11.709
<v Tom Jacques>connectivity, pull that data into one
central location.

98
00:05:12.470 --> 00:05:16.690
<v Tom Jacques>And, and of course, we get loads of
customers that don't have these things in place.

99
00:05:17.670 --> 00:05:21.029
<v Tom Jacques>And because there's suddenly a
requirement, which there wasn't before, to

100
00:05:21.029 --> 00:05:25.420
<v Tom Jacques>centralized data, pull it together in some
form, you know, that's all part of the

101
00:05:25.420 --> 00:05:25.739
<v Tom Jacques>project.

102
00:05:26.109 --> 00:05:30.670
<v Tom Jacques>So we talk about, you know, why is it hard
to start a project or how to start a

103
00:05:30.670 --> 00:05:31.170
<v Tom Jacques>project?

104
00:05:31.869 --> 00:05:33.269
<v Tom Jacques>You know, that's what I'm here for.

105
00:05:33.390 --> 00:05:34.970
<v Tom Jacques>That's also what my team is here for.

106
00:05:35.109 --> 00:05:36.170
<v Tom Jacques>So we all work together.

107
00:05:36.790 --> 00:05:41.149
<v Tom Jacques>Um, to make sense of it, what's the
objective and what are the building blocks we've

108
00:05:41.149 --> 00:05:45.410
<v Tom Jacques>currently got and what are the things that
we currently, we currently lack.

109
00:05:45.760 --> 00:05:49.959
<v Tom Jacques>So that method to cloud that we might not
have in place, or, or, you know, the, the

110
00:05:49.959 --> 00:05:53.220
<v Tom Jacques>person who's going to react to those
alerts from Sensi, for example.

111
00:05:55.100 --> 00:06:00.299
<v Speaker 3>And I guess, uh, another thing that you
and, and colleagues have to consider as well

112
00:06:00.299 --> 00:06:04.380
<v Speaker 3>is you, you must face a lot of
misconceptions from customers.

113
00:06:04.700 --> 00:06:08.459
<v Speaker 3>And it, and, you know, in a way, you can't
blame people because, you know, I know

114
00:06:08.459 --> 00:06:11.929
<v Speaker 3>coming from a marketing perspective, the,
the amount of tools and products out there

115
00:06:11.929 --> 00:06:14.769
<v Speaker 3>saying they do this or that, some doing
PDM and not doing it.

116
00:06:15.019 --> 00:06:17.059
<v Speaker 3>And, you know, it's a very confusing
market out there.

117
00:06:17.140 --> 00:06:20.959
<v Speaker 3>So I guess that leads to a lot of, you
know, misunderstandings and misconceptions.

118
00:06:22.559 --> 00:06:23.769
<v Tom Jacques>I think you're right, Nolan.

119
00:06:23.799 --> 00:06:24.369
<v Tom Jacques>We've seen it.

120
00:06:24.450 --> 00:06:28.040
<v Tom Jacques>I know you've seen this as well, where we
get the wrong sort of requests.

121
00:06:28.170 --> 00:06:33.649
<v Tom Jacques>It ends up becoming a condition monitoring
topic, and PDM for a start is, is much

122
00:06:33.649 --> 00:06:34.290
<v Tom Jacques>broader than that.

123
00:06:34.369 --> 00:06:38.769
<v Tom Jacques>It's about really intelligent, um, you
know, smart decision making.

124
00:06:38.890 --> 00:06:42.609
<v Tom Jacques>So the system's able to not only detect
that you've crossed over a certain

125
00:06:42.609 --> 00:06:47.489
<v Tom Jacques>threshold, but also tell you more or less
what's going wrong on a broad level with a

126
00:06:47.489 --> 00:06:50.510
<v Tom Jacques>good understanding of the application and
the context of the asset.

127
00:06:50.940 --> 00:06:55.179
<v Tom Jacques>Um, with its own general intelligence,
plus the knowledge of, you know, PDF

128
00:06:55.179 --> 00:06:58.989
<v Tom Jacques>documents and so on, and give you decision
making.

129
00:06:59.109 --> 00:07:03.910
<v Tom Jacques>So I think some of the misconceptions are,
it's basically what we saw 10 years ago.

130
00:07:04.029 --> 00:07:08.429
<v Tom Jacques>We can add some sensors, we can see when
we cross the threshold, but it's so much

131
00:07:08.429 --> 00:07:09.070
<v Tom Jacques>more than that.

132
00:07:09.179 --> 00:07:12.920
<v Tom Jacques>And it's very easy when you look at the,
you know, the overlevel, the, the, the

133
00:07:12.920 --> 00:07:14.660
<v Tom Jacques>over, uh, you know, the interface of
Sensi.

134
00:07:15.480 --> 00:07:18.000
<v Tom Jacques>Um, you know, I've seen something like
this 10 years ago.

135
00:07:18.200 --> 00:07:21.260
<v Tom Jacques>I heard that from a customer, at Hanover
Messa not long ago.

136
00:07:22.160 --> 00:07:25.119
<v Tom Jacques>And you have to try and explain that in
the background, there's a lot more

137
00:07:25.119 --> 00:07:29.470
<v Tom Jacques>intelligence than there was in the past,
the ability to determine baseline of an

138
00:07:29.470 --> 00:07:31.899
<v Tom Jacques>asset very, very quickly without models.

139
00:07:32.660 --> 00:07:37.790
<v Tom Jacques>Um, and I think when it comes to
misconceptions, it can be, OK, we just plug it in

140
00:07:37.790 --> 00:07:39.519
<v Tom Jacques>and it all just works is another one.

141
00:07:40.899 --> 00:07:44.579
<v Tom Jacques>And I would still say it's plug and play
with a little bit of context and

142
00:07:44.579 --> 00:07:48.660
<v Tom Jacques>understanding of, you know, which sensors
do we need, which context data do we need,

143
00:07:49.140 --> 00:07:54.500
<v Tom Jacques>so that we have that understanding of this
particular motor or this particular hoist

144
00:07:54.500 --> 00:07:57.820
<v Tom Jacques>or cooling system, and we can build that
into the software.

145
00:07:57.920 --> 00:08:01.739
<v Tom Jacques>So as soon as that's in place, which is,
I'd still call it plug and play with a

146
00:08:01.739 --> 00:08:06.220
<v Tom Jacques>little bit of an extra piece of delivery
work, then you get the full-fledged

147
00:08:06.220 --> 00:08:08.130
<v Tom Jacques>predictive maintenance, um.

148
00:08:08.670 --> 00:08:11.970
<v Tom Jacques>And I think people often think it's
expensive and it's not going to pay for itself

149
00:08:11.970 --> 00:08:13.320
<v Tom Jacques>and what's the value?

150
00:08:13.709 --> 00:08:17.109
<v Tom Jacques>And, and a big part of it has to be that
business understanding, what's the

151
00:08:17.109 --> 00:08:22.029
<v Tom Jacques>objective we're trying to solve and see
perhaps case studies from past, you know,

152
00:08:22.190 --> 00:08:26.230
<v Tom Jacques>how we've done this with previous
customers, um, and really the the proof is in the

153
00:08:26.230 --> 00:08:26.510
<v Tom Jacques>pudding.

154
00:08:26.630 --> 00:08:27.450
<v Tom Jacques>We've done this before.

155
00:08:29.570 --> 00:08:34.010
<v Speaker 3>And, and actually to, to your latter
point, you know, focusing on, because a lot of

156
00:08:34.010 --> 00:08:37.150
<v Speaker 3>those points around, you know, it's, it's
too expensive and.

157
00:08:37.549 --> 00:08:39.950
<v Speaker 3>You know, when will I see a return on
investments, actually, a lot of the time it's

158
00:08:39.950 --> 00:08:44.520
<v Speaker 3>focusing on, um, the technology aspects of
it and not the business outcomes, which

159
00:08:44.520 --> 00:08:45.799
<v Speaker 3>you mentioned before, right?

160
00:08:45.960 --> 00:08:49.359
<v Speaker 3>So that's part, probably going, oh, you
know, do I need this technology rather than

161
00:08:49.359 --> 00:08:51.669
<v Speaker 3>saying, what business problem am I trying
to solve?

162
00:08:51.840 --> 00:08:53.400
<v Speaker 3>I guess that could be a way to look at it.

163
00:08:53.590 --> 00:08:56.719
<v Tom Jacques>It can be one of the first areas that
we've looked to address, because if the

164
00:08:56.719 --> 00:09:00.840
<v Tom Jacques>business objective is wrong or somehow
it's, it's not going to miss, it's not going

165
00:09:00.840 --> 00:09:05.070
<v Tom Jacques>to align, we can't achieve this certain
component, but we can achieve these other

166
00:09:05.070 --> 00:09:06.520
<v Tom Jacques>areas that you haven't considered.

167
00:09:06.869 --> 00:09:10.940
<v Tom Jacques>It's making sure we get on the same page
as quickly as possible, um, as to what's

168
00:09:10.940 --> 00:09:13.479
<v Tom Jacques>achievable, where the big wins are going
to come from.

169
00:09:13.650 --> 00:09:15.599
<v Tom Jacques>Um, yeah, no, it's exactly to your point.

170
00:09:16.210 --> 00:09:19.840
<v Tom Jacques>It's really important to get the business
objective, um, in place when we start.

171
00:09:21.239 --> 00:09:24.690
<v Speaker 3>And I, I guess to another point you made
about, you know, you know, often being

172
00:09:24.690 --> 00:09:26.229
<v Speaker 3>compared to condition monitoring.

173
00:09:26.369 --> 00:09:30.130
<v Speaker 3>Is there a reason why condition monitoring
is often confused with predictive

174
00:09:30.130 --> 00:09:30.830
<v Speaker 3>maintenance?

175
00:09:31.590 --> 00:09:32.590
<v Speaker 3>Um, I'd say

176
00:09:32.590 --> 00:09:32.789
<v Tom Jacques>so.

177
00:09:32.909 --> 00:09:36.789
<v Tom Jacques>The reason, the reason is, and because
it's been doing, you know, it's been taking

178
00:09:36.789 --> 00:09:41.820
<v Tom Jacques>place for, I'd say at least, you know, 10,
maybe even 20 years at the scale it is at

179
00:09:41.820 --> 00:09:45.570
<v Tom Jacques>the moment, where you have maybe some IOT
sensors, you bolt them on.

180
00:09:46.030 --> 00:09:49.469
<v Tom Jacques>There's certain thresholds, maybe there's
some, some basic level intelligence in

181
00:09:49.469 --> 00:09:49.809
<v Tom Jacques>there.

182
00:09:50.229 --> 00:09:52.070
<v Tom Jacques>Um, that to me is condition monitoring.

183
00:09:52.349 --> 00:09:54.869
<v Tom Jacques>You're monitoring that sort of condition
of the asset.

184
00:09:55.489 --> 00:10:00.869
<v Tom Jacques>Predictive maintenance then becomes, you
know, how do we then make sense of that

185
00:10:00.869 --> 00:10:01.030
<v Tom Jacques>information?

186
00:10:01.159 --> 00:10:06.840
<v Tom Jacques>The software within Sensei is able to
really enhance that and give you, you know,

187
00:10:06.979 --> 00:10:10.739
<v Tom Jacques>digital support, give you AI driven
decision making.

188
00:10:11.159 --> 00:10:15.099
<v Tom Jacques>And sometimes it sounds too good to be
true, but the more you feed into the software

189
00:10:15.099 --> 00:10:18.520
<v Tom Jacques>in terms of how you fix problems, how
you've solved things, the work that you've

190
00:10:18.520 --> 00:10:24.750
<v Tom Jacques>done to grease a bearing or do certain
work is saved and used as future decision

191
00:10:24.760 --> 00:10:25.099
<v Tom Jacques>support.

192
00:10:25.510 --> 00:10:29.770
<v Tom Jacques>And that's a really fundamental difference
to, you know, to how predictive

193
00:10:29.770 --> 00:10:30.890
<v Tom Jacques>maintenance works.

194
00:10:31.229 --> 00:10:31.530
<v Tom Jacques>Um.

195
00:10:32.580 --> 00:10:35.950
<v Tom Jacques>Long term, I think we'll see more and more
customers start to understand that.

196
00:10:36.690 --> 00:10:41.840
<v Tom Jacques>The the transition I've already seen it
things like the exhibitions we go to, it's

197
00:10:41.849 --> 00:10:43.960
<v Tom Jacques>quite significant, especially in the last
12 months.

198
00:10:44.090 --> 00:10:48.130
<v Tom Jacques>The impact it seems to have had great job
from the marketing team.

199
00:10:48.169 --> 00:10:51.239
<v Tom Jacques>I definitely would say that where we've
got more customers.

200
00:10:51.739 --> 00:10:56.500
<v Tom Jacques>Understanding what, what we are, what we
can do, and what we bring to the table, um,

201
00:10:56.859 --> 00:11:01.619
<v Tom Jacques>in a way that, you know, far outclasses
the typical condition monitoring as it was,

202
00:11:01.890 --> 00:11:03.320
<v Tom Jacques>you know, all those years ago.

203
00:11:05.789 --> 00:11:08.969
<v Speaker 3>Yeah, well, thank you for the compliment,
first of all, Tom, but, um, no problem.

204
00:11:09.950 --> 00:11:14.469
<v Speaker 3>Yeah, but I think, I think also the
market, you know, the, the, the market's ever

205
00:11:14.469 --> 00:11:15.619
<v Speaker 3>changing as well.

206
00:11:15.789 --> 00:11:20.070
<v Speaker 3>Uh, but yeah, there, there certainly is
that, um, sort of confusion in the market.

207
00:11:20.150 --> 00:11:25.210
<v Speaker 3>I mean, I, I've spoken to, um, a few, um,
industry analysts recently, and again,

208
00:11:25.429 --> 00:11:29.609
<v Speaker 3>that, that's the, the common, you know,
when end users approach them, it's always

209
00:11:29.609 --> 00:11:32.890
<v Speaker 3>about, you know, what's the differentiator
between X product and X product.

210
00:11:33.150 --> 00:11:33.570
<v Speaker 3>And I think.

211
00:11:34.479 --> 00:11:38.159
<v Speaker 3>Yeah, and I think that's, and it leads
back to that point about, you know, is

212
00:11:38.159 --> 00:11:40.859
<v Speaker 3>predictive maintenance the right fit for
your organization, but if you don't

213
00:11:41.640 --> 00:11:44.669
<v Speaker 3>understand what predictive maintenance is
because of all this confusion, then it's

214
00:11:44.669 --> 00:11:47.739
<v Speaker 3>difficult to get started, right, if that
makes sense.

215
00:11:48.559 --> 00:11:51.960
<v Tom Jacques>It does make sense, and it's good to see
that analysts in the industry are seeing

216
00:11:51.960 --> 00:11:52.539
<v Tom Jacques>the same.

217
00:11:52.840 --> 00:11:57.119
<v Tom Jacques>Um, and I think just to, just to really
reiterate it, in the last 12 months, it's

218
00:11:57.119 --> 00:11:58.080
<v Tom Jacques>really significant.

219
00:11:58.530 --> 00:12:01.760
<v Tom Jacques>Um, how many people now know what it is,
they see what it can do.

220
00:12:01.890 --> 00:12:05.010
<v Tom Jacques>I think the, you know, the fact that AI
has become a really big buzzword in

221
00:12:05.010 --> 00:12:07.150
<v Tom Jacques>different circles, it's in the news quite
a lot.

222
00:12:07.799 --> 00:12:11.250
<v Tom Jacques>Um, it gives you more of an understanding
of what's actually achievable in an

223
00:12:11.250 --> 00:12:13.669
<v Tom Jacques>industrial space and maintenance.

224
00:12:13.690 --> 00:12:17.090
<v Tom Jacques>It's always going to be there until we
remove friction from the process, we're

225
00:12:17.090 --> 00:12:20.960
<v Tom Jacques>always going to have degrading belts,
rockets, chains, bearings, you name it.

226
00:12:21.330 --> 00:12:25.030
<v Tom Jacques>All of these things will always need to be
maintained, and it's really important

227
00:12:25.409 --> 00:12:28.150
<v Tom Jacques>that your process there to, to do that
maintenance.

228
00:12:28.909 --> 00:12:34.239
<v Tom Jacques>I would say nowadays, especially in, in
2025, is digitally driven rather than coming

229
00:12:34.239 --> 00:12:38.719
<v Tom Jacques>from an old catalog or from an old PDF
document that's got a structured process and

230
00:12:38.719 --> 00:12:43.059
<v Tom Jacques>every six months we do this and this
maintenance in a preventative way.

231
00:12:43.599 --> 00:12:49.119
<v Tom Jacques>We really now move towards, you know, AI
driven decision making, which is forward

232
00:12:49.119 --> 00:12:49.400
<v Tom Jacques>thinking.

233
00:12:49.469 --> 00:12:50.799
<v Tom Jacques>It's based on the past.

234
00:12:50.869 --> 00:12:54.780
<v Tom Jacques>Decisions are then extremely intelligent
compared to the past.

235
00:12:56.690 --> 00:13:00.559
<v Tom Jacques>Yeah, I, I know we're gonna come on to
these topics, but this is, this is how I see

236
00:13:00.559 --> 00:13:01.559
<v Tom Jacques>it, massively.

237
00:13:01.880 --> 00:13:03.520
<v Speaker 3>No, no, exactly, exactly.

238
00:13:03.880 --> 00:13:07.489
<v Speaker 3>And if we, I guess we pull it back to, you
know, the start of a predicting

239
00:13:07.489 --> 00:13:12.320
<v Speaker 3>maintenance, um, project, but with all
this in mind, we've discussed so far, which I

240
00:13:12.320 --> 00:13:16.840
<v Speaker 3>think feeds into this question, but what
does sort of an ideal roadmap look like for

241
00:13:16.840 --> 00:13:17.840
<v Speaker 3>a PDM project?

242
00:13:17.960 --> 00:13:21.940
<v Speaker 3>I know there's some context around it, you
know, diff customers are all different,

243
00:13:22.059 --> 00:13:22.280
<v Speaker 3>right?

244
00:13:22.440 --> 00:13:25.140
<v Speaker 3>But if, uh, let's say a typical roadmap
might look like.

245
00:13:26.179 --> 00:13:26.780
<v Tom Jacques>Simple.

246
00:13:27.130 --> 00:13:31.640
<v Tom Jacques>It is to start small, prove the value, and
then scale, and sensesize scales really,

247
00:13:31.690 --> 00:13:32.390
<v Tom Jacques>really well.

248
00:13:32.770 --> 00:13:36.210
<v Tom Jacques>It scales because it's got no models in
the background, so it works, you know, it

249
00:13:36.210 --> 00:13:39.599
<v Tom Jacques>learns baseline of any asset that we've
never seen before very quickly.

250
00:13:40.049 --> 00:13:44.289
<v Tom Jacques>But the key to it is to start small and
see that value for yourselves, and small to

251
00:13:44.289 --> 00:13:46.250
<v Tom Jacques>us typically is 50 assets.

252
00:13:46.690 --> 00:13:51.590
<v Tom Jacques>The reason that's small is because we, um,
you know, we look for a process that's

253
00:13:52.090 --> 00:13:55.669
<v Tom Jacques>enough data, enough machines, looking at
enough things that could go wrong.

254
00:13:56.150 --> 00:14:00.809
<v Tom Jacques>Um, typically in a factory or any
environments maintenance, there's lots of things

255
00:14:01.349 --> 00:14:02.630
<v Tom Jacques>already being well maintained.

256
00:14:03.229 --> 00:14:06.409
<v Tom Jacques>There's, you know, good quality machinery,
which doesn't typically fail.

257
00:14:07.229 --> 00:14:10.710
<v Tom Jacques>But when it does, it can be catastrophic
or you're having to really over maintain

258
00:14:10.710 --> 00:14:11.210
<v Tom Jacques>stuff.

259
00:14:11.710 --> 00:14:16.270
<v Tom Jacques>So, if we look at 50 things, it allows us
to really show value on at least, you

260
00:14:16.270 --> 00:14:19.250
<v Tom Jacques>know, 234 of those across the 12 month
period.

261
00:14:19.909 --> 00:14:23.690
<v Tom Jacques>And then you see the value that gives us
the ability to prove value.

262
00:14:24.409 --> 00:14:26.229
<v Tom Jacques>Um, and I guess really that's my job.

263
00:14:26.349 --> 00:14:29.849
<v Tom Jacques>So we have to make sure we scope the right
assets, we look at the right parameters,

264
00:14:30.510 --> 00:14:32.200
<v Tom Jacques>what sensors, what connectivity do we
need?

265
00:14:32.630 --> 00:14:35.989
<v Tom Jacques>And we've got a whole team of people
within Siemens that support this, that support

266
00:14:35.989 --> 00:14:38.150
<v Tom Jacques>this across, you know, any region of the
world.

267
00:14:38.270 --> 00:14:40.109
<v Tom Jacques>We can, we can make sure this happens.

268
00:14:40.349 --> 00:14:43.580
<v Tom Jacques>Um, also with partners that are well
engaged with our customers.

269
00:14:44.299 --> 00:14:49.869
<v Tom Jacques>It allows us to really build a
relationship and prove that first step, and then, um,

270
00:14:49.940 --> 00:14:54.469
<v Tom Jacques>you know, really, you know, build
confidence, I think is the key with that small

271
00:14:54.469 --> 00:14:56.770
<v Tom Jacques>scale start and then scale it from there.

272
00:14:57.830 --> 00:15:01.669
<v Speaker 3>Yeah, and it, it's, it's really
interesting because you use that, the, the phrase

273
00:15:01.669 --> 00:15:06.669
<v Speaker 3>sort of small, you know, start small,
which small could mean also, you know, in some

274
00:15:06.669 --> 00:15:10.250
<v Speaker 3>eyes, let's start with this one really
important machine we have here.

275
00:15:10.530 --> 00:15:14.429
<v Speaker 3>So what, why is that not sort of a good
starting point for predicting maintenance

276
00:15:14.429 --> 00:15:14.929
<v Speaker 3>necessarily?

277
00:15:15.549 --> 00:15:16.429
<v Tom Jacques>That's a good topic.

278
00:15:16.590 --> 00:15:16.869
<v Tom Jacques>No.

279
00:15:17.179 --> 00:15:21.869
<v Tom Jacques>Um, sometimes it becomes the machine is,
you know, worth €3 million or 3 million

280
00:15:21.869 --> 00:15:22.030
<v Tom Jacques>pounds.

281
00:15:22.109 --> 00:15:26.130
<v Tom Jacques>You think, well, actually, this is
something that we should monitor.

282
00:15:26.760 --> 00:15:28.570
<v Tom Jacques>But maybe there's a, there's a whip
storage.

283
00:15:28.650 --> 00:15:31.750
<v Tom Jacques>There's a, there's a back and forth in the
maintenance process where that machine is

284
00:15:31.750 --> 00:15:33.130
<v Tom Jacques>only switched on 2 days a week.

285
00:15:33.369 --> 00:15:37.330
<v Tom Jacques>You throw a few things through it, it does
what it's supposed to do, stamping or

286
00:15:37.330 --> 00:15:39.109
<v Tom Jacques>pressing or something that's on a larger
scale.

287
00:15:40.010 --> 00:15:44.409
<v Tom Jacques>And actually, if you were to stop it for a
few days and run it back up again on a

288
00:15:44.409 --> 00:15:47.229
<v Tom Jacques>couple of other shifts, it doesn't really
impact the process.

289
00:15:47.609 --> 00:15:51.630
<v Tom Jacques>So you have these big gaps to do
maintenance that don't affect the process.

290
00:15:52.289 --> 00:15:55.869
<v Tom Jacques>Whereas somewhere else, you could have a
small conveyor that's only €200.

291
00:15:56.130 --> 00:15:59.549
<v Tom Jacques>It's really crucial and it's a big
bottleneck in the process.

292
00:15:59.849 --> 00:16:04.890
<v Tom Jacques>And actually, if that thing stops, you
lose hours of production time or, you know,

293
00:16:05.409 --> 00:16:09.109
<v Tom Jacques>depending on the criticality and depending
on the output of what the product is.

294
00:16:09.940 --> 00:16:15.369
<v Tom Jacques>The impact could be huge, even though the
asset we choose to monitor is fairly

295
00:16:15.369 --> 00:16:18.979
<v Tom Jacques>insignificant or fairly, um, you know,
cost-effective.

296
00:16:19.049 --> 00:16:21.239
<v Tom Jacques>It's, it's cheaper compared to the rest.

297
00:16:22.039 --> 00:16:24.039
<v Tom Jacques>So again, this comes back down to business
objective.

298
00:16:24.239 --> 00:16:28.000
<v Tom Jacques>Do we look to extend the lifespan of the,
you know, the 1 million pounds CNC

299
00:16:28.000 --> 00:16:32.919
<v Tom Jacques>machine, um, or likewise, make sure we
don't have a stoppage and a downtime on a, on

300
00:16:32.919 --> 00:16:36.260
<v Tom Jacques>a, um, you know, a smaller, less
significant asset.

301
00:16:37.049 --> 00:16:41.219
<v Speaker 3>So, so I guess what we're saying is a
really important part of this is asset

302
00:16:41.219 --> 00:16:45.719
<v Speaker 3>selection is looking at business outcomes,
looking at the right assets, you know,

303
00:16:45.880 --> 00:16:50.559
<v Speaker 3>for, you know, to meet, you know, you
know, to, to meet those, um, business

304
00:16:50.559 --> 00:16:51.809
<v Speaker 3>objectives, I guess that,

305
00:16:51.840 --> 00:16:56.960
<v Tom Jacques>that's the, yeah, absolutely, and it can
make or break a make or break a project

306
00:16:56.960 --> 00:17:01.659
<v Tom Jacques>because if you, if you select the wrong
assets, and that business impact isn't seen

307
00:17:02.080 --> 00:17:03.500
<v Tom Jacques>for obviously whatever reason.

308
00:17:04.250 --> 00:17:07.890
<v Tom Jacques>Like sometimes we see this, we see where a
customer wants to monitor the biggest,

309
00:17:07.930 --> 00:17:11.810
<v Tom Jacques>most expensive assets, and that's the
asset they would typically do lots of over

310
00:17:11.810 --> 00:17:14.109
<v Tom Jacques>maintenance on, even if Sun size is in
place.

311
00:17:14.530 --> 00:17:16.729
<v Tom Jacques>And so after 12 months, it never broke
down.

312
00:17:16.810 --> 00:17:21.599
<v Tom Jacques>It never was given the chance to fail or
to get close to degrading for Sunite to

313
00:17:21.599 --> 00:17:22.229
<v Tom Jacques>show the impact.

314
00:17:22.530 --> 00:17:23.709
<v Tom Jacques>So, yeah, no, absolutely.

315
00:17:24.130 --> 00:17:25.630
<v Tom Jacques>Asset selection is really, really
important.

316
00:17:26.310 --> 00:17:31.310
<v Speaker 3>And I guess maybe just, you know, for the
audience, um, information like how, how do

317
00:17:31.310 --> 00:17:35.410
<v Speaker 3>you go about working with the customer to
select the right assets for, for a project

318
00:17:35.510 --> 00:17:36.689
<v Speaker 3>on a typical project?

319
00:17:37.189 --> 00:17:42.819
<v Tom Jacques>What it comes down to is we understand
each other, so we have interaction between

320
00:17:42.819 --> 00:17:45.510
<v Tom Jacques>each other to understand, you know, how
can we help?

321
00:17:45.790 --> 00:17:46.640
<v Tom Jacques>what are the problems?

322
00:17:48.800 --> 00:17:49.209
<v Tom Jacques>Um, this could be online.

323
00:17:49.670 --> 00:17:53.510
<v Tom Jacques>And then it leads perhaps to an onsite
meeting and somewhere within this, it leads

324
00:17:53.510 --> 00:17:57.630
<v Tom Jacques>to a scope workshop, which is what we term
as the chance to come and have a look at

325
00:17:57.630 --> 00:18:01.869
<v Tom Jacques>the machines, do a walk around that could
be around the mine, it could be around a

326
00:18:01.869 --> 00:18:05.239
<v Tom Jacques>steel factory, it could be around a
chocolate factory or anything.

327
00:18:05.270 --> 00:18:09.140
<v Tom Jacques>It could be around literally any kind of
processes that we're looking at, you know,

328
00:18:09.189 --> 00:18:10.630
<v Tom Jacques>it goes without saying since size.

329
00:18:10.949 --> 00:18:13.369
<v Tom Jacques>It's a completely system and industry
agnostic.

330
00:18:14.109 --> 00:18:15.369
<v Tom Jacques>So, we look at anything.

331
00:18:15.719 --> 00:18:19.199
<v Tom Jacques>And the team, you know, the solutions
engineering team have got lots of knowledge,

332
00:18:19.359 --> 00:18:23.359
<v Tom Jacques>lots of understanding of how mechanical
systems fail, what to look out for, what

333
00:18:23.359 --> 00:18:27.839
<v Tom Jacques>questions to ask, what kind of data to
look for, and make recommendations as well,

334
00:18:27.959 --> 00:18:32.599
<v Tom Jacques>you know, if we need additional vibration
sensing or some other monitoring or we

335
00:18:32.599 --> 00:18:34.619
<v Tom Jacques>need some context from the PLC system.

336
00:18:35.239 --> 00:18:38.790
<v Tom Jacques>This all leads towards, you know, correct
selection of assets.

337
00:18:39.560 --> 00:18:42.290
<v Tom Jacques>And once we do that, we continue to work
together.

338
00:18:42.599 --> 00:18:44.530
<v Tom Jacques>Uh, it, it becomes a real collaboration.

339
00:18:44.689 --> 00:18:46.359
<v Tom Jacques>It's not like, here's a box of stuff.

340
00:18:46.369 --> 00:18:47.589
<v Tom Jacques>Now, off you go and plug it in.

341
00:18:47.969 --> 00:18:49.859
<v Tom Jacques>It's an ongoing continuation.

342
00:18:50.400 --> 00:18:54.729
<v Tom Jacques>Even when, you know, the, the alerts would
raise from a, from a newly onboarded

343
00:18:54.729 --> 00:18:55.349
<v Tom Jacques>asset.

344
00:18:55.849 --> 00:18:59.770
<v Tom Jacques>We work together with customers to make
sure that's set correctly, to make sure

345
00:18:59.770 --> 00:19:04.209
<v Tom Jacques>that, you know, as the weeks and months go
on, Nuisance alerts don't happen, but

346
00:19:04.209 --> 00:19:08.329
<v Tom Jacques>also things don't get missed, so we
increase, decrease sensitivities of things.

347
00:19:08.410 --> 00:19:12.359
<v Tom Jacques>We can add additional logic if we need to
through things like derived measures.

348
00:19:13.270 --> 00:19:17.859
<v Tom Jacques>This is really important because it, it,
it means we lead to long-term success and

349
00:19:17.859 --> 00:19:22.010
<v Tom Jacques>there's a relationship between, between us
and the customers, um, also where

350
00:19:22.010 --> 00:19:23.290
<v Tom Jacques>partners are involved as well.

351
00:19:25.040 --> 00:19:27.849
<v Speaker 3>And, and just to pick up on a point
because you mentioned about sort of sensor

352
00:19:27.849 --> 00:19:31.479
<v Speaker 3>selection and actually being on site,
maybe even touching the asset or seeing the

353
00:19:31.479 --> 00:19:35.770
<v Speaker 3>asset in person, but how important is that
sort of physical visit to site, Tom, from

354
00:19:35.770 --> 00:19:36.910
<v Speaker 3>your perspective?

355
00:19:37.390 --> 00:19:38.420
<v Tom Jacques>Yeah, it's really important, yeah.

356
00:19:39.650 --> 00:19:41.130
<v Tom Jacques>It's really important to see the assets.

357
00:19:41.209 --> 00:19:45.000
<v Tom Jacques>It's also really important to meet the
team and learn a little bit more about the

358
00:19:45.000 --> 00:19:45.489
<v Tom Jacques>culture.

359
00:19:45.729 --> 00:19:47.650
<v Tom Jacques>So is, is this a proactive team?

360
00:19:47.810 --> 00:19:50.670
<v Tom Jacques>Is this a team who really just runs things
to failure?

361
00:19:51.130 --> 00:19:53.630
<v Tom Jacques>Because that, again, has an impact on the
business objective.

362
00:19:53.930 --> 00:19:56.469
<v Tom Jacques>Um, is this thing working in a clean
environment?

363
00:19:56.729 --> 00:20:00.930
<v Tom Jacques>Can we look to also, um, you know,
strategically improve the way something is, is

364
00:20:00.930 --> 00:20:01.719
<v Tom Jacques>looked after?

365
00:20:02.010 --> 00:20:05.489
<v Tom Jacques>Um, is it being jet washed to keep it
clean, but actually the, the, you know,

366
00:20:05.569 --> 00:20:06.109
<v Tom Jacques>incorrect.

367
00:20:06.609 --> 00:20:09.439
<v Tom Jacques>Um, IP ratings or housings are not in
place.

368
00:20:09.520 --> 00:20:13.550
<v Tom Jacques>There's other things we can do to make
suggestions and bring improvements.

369
00:20:14.219 --> 00:20:19.400
<v Tom Jacques>Um, and to be clear, that's also, um, you
know, that's done as a, most often as a

370
00:20:19.400 --> 00:20:20.300
<v Tom Jacques>gesture of goodwill.

371
00:20:20.439 --> 00:20:26.390
<v Tom Jacques>So we try to do this in cases where, um,
you know, where we can support customers

372
00:20:26.390 --> 00:20:30.760
<v Tom Jacques>and show that we're there to help, um,
bring our knowledge to the table, we start a

373
00:20:30.760 --> 00:20:32.770
<v Tom Jacques>project together and, and long term.

374
00:20:33.229 --> 00:20:36.430
<v Tom Jacques>You know, hopefully customers choose to
scale with Sensei.

375
00:20:38.959 --> 00:20:43.400
<v Speaker 3>No, absolutely, and, and scale is clearly
the, you know, the pathway that we're

376
00:20:43.400 --> 00:20:45.630
<v Speaker 3>looking to be on that journey with the
customer.

377
00:20:46.160 --> 00:20:50.130
<v Speaker 3>But I guess thinking about, um, you know,
what could possibly, what possible

378
00:20:50.130 --> 00:20:53.920
<v Speaker 3>challenges there are and roadblocks that
could derail some of these projects before

379
00:20:53.920 --> 00:20:58.520
<v Speaker 3>they, in some cases before they even
really get going, but could you sort of explain

380
00:20:58.520 --> 00:21:02.160
<v Speaker 3>some of the, you know, the ones that you
come across most of all, Tom?

381
00:21:03.089 --> 00:21:08.270
<v Tom Jacques>One of the biggest ones is the team are
really keen to start something, and we try

382
00:21:08.270 --> 00:21:11.719
<v Tom Jacques>and escalate this through the business and
we start to hit roadblocks, whether it's

383
00:21:11.719 --> 00:21:15.439
<v Tom Jacques>to do with cloud, um, which is starting to
really disperse now.

384
00:21:15.510 --> 00:21:19.260
<v Tom Jacques>We're not seeing that such, such, um, you
know, so often these days.

385
00:21:20.000 --> 00:21:24.339
<v Tom Jacques>But one of the things is making sure that
upper-level CEOs and high-level management

386
00:21:24.339 --> 00:21:28.719
<v Tom Jacques>are on the same page that this could all
be explained, um, the business impact can

387
00:21:28.719 --> 00:21:30.329
<v Tom Jacques>be explained, the return of investment.

388
00:21:30.619 --> 00:21:36.260
<v Tom Jacques>And can be fully understood rather than
just, Hey, boss, we've got this, this big

389
00:21:36.260 --> 00:21:38.010
<v Tom Jacques>new solution to monitor all of our assets.

390
00:21:38.349 --> 00:21:39.599
<v Tom Jacques>Can we sign it off, please?

391
00:21:40.290 --> 00:21:44.579
<v Tom Jacques>If that is not explained properly and it's
not described as to how this will have a

392
00:21:44.579 --> 00:21:47.219
<v Tom Jacques>business impact, that's a roadblock.

393
00:21:47.300 --> 00:21:48.310
<v Tom Jacques>That's a big roadblock.

394
00:21:49.099 --> 00:21:52.780
<v Tom Jacques>Also, where we start to see there's some
sensors in place, but they might not be

395
00:21:52.780 --> 00:21:53.760
<v Tom Jacques>high enough quality.

396
00:21:54.020 --> 00:22:00.099
<v Tom Jacques>Again, that's a roadblock and making sure
the assets are You know, not being too

397
00:22:00.099 --> 00:22:00.630
<v Tom Jacques>maintained.

398
00:22:00.709 --> 00:22:03.869
<v Tom Jacques>We, we want to make sure that the things
we're looking at are going to get a chance

399
00:22:03.869 --> 00:22:07.900
<v Tom Jacques>to degrade, and since I get a chance to
show the power of, you know, predictive

400
00:22:07.900 --> 00:22:13.709
<v Tom Jacques>maintenance, AI based decision making, um,
And I think culturally, we need to just

401
00:22:13.709 --> 00:22:18.469
<v Tom Jacques>make sure that the kind of customer that
installs this has a vested interest to, you

402
00:22:18.469 --> 00:22:22.709
<v Tom Jacques>know, to follow up on the alerts raised by
Sense I and, and sometimes we find

403
00:22:22.709 --> 00:22:26.329
<v Tom Jacques>customers who don't really understand it
and as soon as the alerts start to come.

404
00:22:26.819 --> 00:22:30.380
<v Tom Jacques>And they see the benefits of interacting
with the algorithm and, and filling in what

405
00:22:30.380 --> 00:22:33.469
<v Tom Jacques>they did to fix problems and, and remedy
the situation.

406
00:22:33.979 --> 00:22:38.380
<v Tom Jacques>That's where the buy-in starts to come
from in a way that I personally have never

407
00:22:38.380 --> 00:22:41.819
<v Tom Jacques>seen in condition monitoring, but I see it
now massively in the predictive

408
00:22:41.819 --> 00:22:42.699
<v Tom Jacques>maintenance space.

409
00:22:43.839 --> 00:22:48.250
<v Speaker 3>And of course, it, it's that thing that
if, you know, if, if, um, like Sensai's

410
00:22:48.250 --> 00:22:51.280
<v Speaker 3>raising alerts, but no one's taking action
on them, and it's sort of a

411
00:22:51.280 --> 00:22:55.199
<v Speaker 3>self-fulfilling prophecy, I guess it's
the, the right way I'd say it won't be

412
00:22:55.199 --> 00:23:00.160
<v Speaker 3>successful if you're not taking the
actions that Sensai's, you know, pointing out to

413
00:23:00.160 --> 00:23:00.939
<v Speaker 3>people, right?

414
00:23:01.560 --> 00:23:02.300
<v Tom Jacques>Absolutely.

415
00:23:02.439 --> 00:23:06.979
<v Tom Jacques>And even, even with that, now, we get the
case where alerts will get closed.

416
00:23:07.040 --> 00:23:10.359
<v Tom Jacques>It seems like the, the system's, you know,
it's just, it's been a little bit of a

417
00:23:10.359 --> 00:23:10.829
<v Tom Jacques>nuisance.

418
00:23:10.880 --> 00:23:13.619
<v Tom Jacques>It's alerting you to a, a motor that's got
some issues.

419
00:23:14.079 --> 00:23:18.439
<v Tom Jacques>The alert gets closed, 2 weeks later, the
motor fails, and then you realize

420
00:23:18.439 --> 00:23:22.680
<v Tom Jacques>culturally, ah, we need to pay attention
to these alerts because it has actually had

421
00:23:22.680 --> 00:23:25.800
<v Tom Jacques>a direct impact on our maintenance, on our
operations.

422
00:23:26.310 --> 00:23:30.900
<v Tom Jacques>Um, and that's something that you learn,
you know, these things start to really, uh,

423
00:23:30.920 --> 00:23:33.229
<v Tom Jacques>progress as you start to work with the
software.

424
00:23:33.280 --> 00:23:37.199
<v Tom Jacques>So you also can't do this as a, as a demo
off to the side in a, in an innovation

425
00:23:37.199 --> 00:23:37.579
<v Tom Jacques>room.

426
00:23:38.040 --> 00:23:42.349
<v Tom Jacques>It has to, you know, we see the most
success where, where it's part of a, a fully

427
00:23:42.349 --> 00:23:45.819
<v Tom Jacques>active process that's, you know, driving
business outcomes.

428
00:23:47.040 --> 00:23:50.219
<v Speaker 3>And it was, it was interesting actually,
on a recent podcast, I interviewed our

429
00:23:50.599 --> 00:23:52.540
<v Speaker 3>colleague Jordan in the delivery team.

430
00:23:53.359 --> 00:23:55.689
<v Speaker 3>Um, and, and he was, he was saying.

431
00:23:56.640 --> 00:23:59.430
<v Speaker 3>You know, one of the challenges he had
talking to customers is that they were

432
00:23:59.430 --> 00:24:03.640
<v Speaker 3>actually sometimes, in some cases too
afraid to sort of point out that, oh, the

433
00:24:03.640 --> 00:24:07.800
<v Speaker 3>system missed something or, you know,
didn't do something quite correctly, you know,

434
00:24:07.880 --> 00:24:10.640
<v Speaker 3>thinking, oh, you know, we don't want to
criticize the system too much.

435
00:24:10.719 --> 00:24:14.239
<v Speaker 3>But he was saying, no, no, we need that
kind of feedback so we can, you know, make

436
00:24:14.239 --> 00:24:15.349
<v Speaker 3>tweaks and improve it.

437
00:24:15.680 --> 00:24:18.920
<v Speaker 3>So it's just in, so that's another part of
it, that someone is paying attention to

438
00:24:18.920 --> 00:24:19.859
<v Speaker 3>it, but they're actually too.

439
00:24:20.709 --> 00:24:23.459
<v Speaker 3>You know, reluctant to provide that
feedback in some cases.

440
00:24:23.619 --> 00:24:24.089
<v Speaker 3>It's another ways.

441
00:24:24.189 --> 00:24:24.310
<v Speaker 3>Well,

442
00:24:24.550 --> 00:24:25.069
<v Tom Jacques>well said.

443
00:24:25.239 --> 00:24:31.339
<v Tom Jacques>Yeah, and Jordan's expert in delivery
along with other members of the delivery team,

444
00:24:31.550 --> 00:24:35.530
<v Tom Jacques>and these are the type of things that we
see and we can work together.

445
00:24:35.630 --> 00:24:38.010
<v Tom Jacques>So that's a really ongoing process to make
sure.

446
00:24:38.400 --> 00:24:41.920
<v Tom Jacques>You know, customers understand the
benefit, like you say, of, of giving the

447
00:24:41.920 --> 00:24:46.380
<v Tom Jacques>feedback, making sure it's a, it's a
collaboration between the maintenance engineers

448
00:24:46.520 --> 00:24:50.920
<v Tom Jacques>and the software itself, um, and it is
self-learning in that sense, it continues to

449
00:24:50.920 --> 00:24:53.680
<v Tom Jacques>get better based on what you fill it, uh,
fill it in with.

450
00:24:53.880 --> 00:24:56.459
<v Tom Jacques>So the more you put in, the more you get
back out of it.

451
00:24:57.520 --> 00:24:58.640
<v Speaker 3>Exactly, exactly.

452
00:24:59.300 --> 00:25:03.729
<v Speaker 3>Um, so I know, I know we're very short on
time because you've got to, we're, we're

453
00:25:03.729 --> 00:25:07.540
<v Speaker 3>back to back here, as well, I guess a lot
of the people listening will understand as

454
00:25:07.540 --> 00:25:07.890
<v Speaker 3>well.

455
00:25:08.180 --> 00:25:11.560
<v Speaker 3>So I'll just ask one more question, Tom,
before you, before you depart.

456
00:25:11.660 --> 00:25:14.790
<v Speaker 3>Um, and it's really just to summarize what
we've talked about today.

457
00:25:14.900 --> 00:25:18.859
<v Speaker 3>So someone looking to start a predictive
maintenance project, don't quite know, uh,

458
00:25:18.979 --> 00:25:21.939
<v Speaker 3>where to start or what to think about,
what are the three things they need to think

459
00:25:21.939 --> 00:25:22.380
<v Speaker 3>about?

460
00:25:23.540 --> 00:25:26.479
<v Tom Jacques>The first one is what do you want to start
to achieve?

461
00:25:26.619 --> 00:25:29.959
<v Tom Jacques>I think the first point is, why would you
install predictive maintenance?

462
00:25:30.579 --> 00:25:33.699
<v Tom Jacques>The second one is, are you keen to have us
just to come and have a look?

463
00:25:34.020 --> 00:25:34.589
<v Tom Jacques>We'll help you.

464
00:25:34.699 --> 00:25:39.060
<v Tom Jacques>We're happy to try and have a look at
things and effectively address some of the key

465
00:25:39.060 --> 00:25:39.520
<v Tom Jacques>issues.

466
00:25:39.699 --> 00:25:44.459
<v Tom Jacques>Um, and then the third one is, you know,
how do you think long term that's going to

467
00:25:44.459 --> 00:25:45.219
<v Tom Jacques>impact the business?

468
00:25:45.380 --> 00:25:45.739
<v Tom Jacques>So.

469
00:25:46.229 --> 00:25:48.359
<v Tom Jacques>It can't really be done as a short term
thing.

470
00:25:48.420 --> 00:25:52.949
<v Tom Jacques>This needs to be done as a, I would always
say a 12 month pilot, 2 year pilot if

471
00:25:52.949 --> 00:25:58.630
<v Tom Jacques>possible, and really see how we can
extrapolate that and see benefit and value, um.

472
00:25:59.270 --> 00:26:03.140
<v Tom Jacques>You know, where I've seen the most success
is where we've got proactive customers,

473
00:26:03.390 --> 00:26:08.150
<v Tom Jacques>proactive IOT departments, digitalization,
digital transformation teams, um, that

474
00:26:08.150 --> 00:26:13.670
<v Tom Jacques>are fully integrated with the maintenance
department, and it becomes like a, a

475
00:26:13.670 --> 00:26:17.050
<v Tom Jacques>cross-business collaboration to make, to
make things better.

476
00:26:17.670 --> 00:26:22.209
<v Tom Jacques>Um, You know, there's loads of companies I
can think of off the top of my head that

477
00:26:22.209 --> 00:26:23.630
<v Tom Jacques>where where this has been the case.

478
00:26:24.310 --> 00:26:27.750
<v Tom Jacques>And loads of case studies and other things
that we've got to share.

479
00:26:27.869 --> 00:26:32.510
<v Tom Jacques>I mean, I'll point them in your direction
after this, but this is really where,

480
00:26:32.579 --> 00:26:33.209
<v Tom Jacques>where we have to.

481
00:26:33.390 --> 00:26:35.329
<v Tom Jacques>We have to show, you know, we've done this
before.

482
00:26:36.229 --> 00:26:39.430
<v Tom Jacques>We've seen customers where they don't
integrate and they don't, you know, engage

483
00:26:39.430 --> 00:26:41.930
<v Tom Jacques>properly or they don't understand what's
needed.

484
00:26:42.790 --> 00:26:44.229
<v Tom Jacques>We're here to answer those questions.

485
00:26:44.349 --> 00:26:47.489
<v Tom Jacques>We're here to make sure those, those
teething problems can be solved.

486
00:26:47.959 --> 00:26:51.229
<v Tom Jacques>Um, and I would say we see lots and lots
of success.

487
00:26:51.310 --> 00:26:56.069
<v Tom Jacques>We've got customers scaling to 15,000,
20,000 assets across many, many countries

488
00:26:56.069 --> 00:26:56.770
<v Tom Jacques>around the world.

489
00:26:57.520 --> 00:27:02.630
<v Tom Jacques>Um, I'd like to get more customers who,
who have the same mindset, um, but it's

490
00:27:02.630 --> 00:27:06.069
<v Tom Jacques>already impressive in the last 12 months,
especially to see how that mindset is

491
00:27:06.069 --> 00:27:06.489
<v Tom Jacques>changing.

492
00:27:07.640 --> 00:27:11.040
<v Speaker 3>Absolutely, and what a nice positive way
to finish as well, Tom, so.

493
00:27:11.729 --> 00:27:15.969
<v Speaker 3>Yeah, so that's all we've got time for
today, but thank you so much, um, for taking

494
00:27:15.969 --> 00:27:18.089
<v Speaker 3>part and sharing your insights, Tom, as
usual.

495
00:27:18.250 --> 00:27:19.119
<v Speaker 3>Really, really good.

496
00:27:19.369 --> 00:27:23.130
<v Speaker 3>Um, and yeah, thank you everyone out there
for listening and we'll see you on the

497
00:27:23.130 --> 00:27:23.729
<v Speaker 3>next episode.

498
00:27:23.959 --> 00:27:24.949
<v Speaker 3>Thank you very much.

499
00:27:25.530 --> 00:27:26.489
<v Tom Jacques>Cheers, Noel, cheers.

500
00:27:30.069 --> 00:27:35.030
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

501
00:27:35.030 --> 00:27:38.550
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
