WEBVTT
Language: en-US

1
00:00:01.879 --> 00:00:07.090
<v Speaker 1>Welcome to the trend detection podcast
powered by Siemens, and now your host Nel

2
00:00:07.090 --> 00:00:07.639
<v Speaker 1>Sullivan.

3
00:00:09.189 --> 00:00:13.210
<v Speaker 2>Hello and welcome to the latest episode of
the Trend detection podcast.

4
00:00:13.630 --> 00:00:17.290
<v Speaker 2>Um, I'm really pleased to be joined by a
very familiar face on the podcast, Tom.

5
00:00:17.469 --> 00:00:17.969
<v Speaker 2>Welcome back.

6
00:00:18.069 --> 00:00:19.250
<v Speaker 2>But we're actually in person.

7
00:00:19.469 --> 00:00:24.170
<v Speaker 2>You've probably heard us quite a few times
talking about many fantastic, um,

8
00:00:24.190 --> 00:00:29.020
<v Speaker 2>subjects online, but we're actually in
person, so it's a pleasure to do this in

9
00:00:29.020 --> 00:00:29.420
<v Speaker 2>person to be here.

10
00:00:29.670 --> 00:00:30.770
<v Speaker 2>No, fantastic.

11
00:00:31.110 --> 00:00:34.430
<v Speaker 2>Um, and I think towards the end of our
last podcast we did, we sort of, or maybe it

12
00:00:34.430 --> 00:00:36.250
<v Speaker 2>was after we stopped recording, but we.

13
00:00:36.950 --> 00:00:40.590
<v Speaker 2>Came up with this idea cos your career is,
has been so interesting and you've seen

14
00:00:40.590 --> 00:00:44.029
<v Speaker 2>sort of both sides of the, the table, both
sides of the table, both sides of the

15
00:00:44.029 --> 00:00:48.790
<v Speaker 2>coin in terms of, you know, working on a
shop floor to now working at Siemens and

16
00:00:48.790 --> 00:00:53.990
<v Speaker 2>with the um deploying Sensai with our
customers, so we sort of wanted to talk about

17
00:00:53.990 --> 00:00:57.630
<v Speaker 2>that journey today but I guess maybe the
best way to sort of open the conversation

18
00:00:57.630 --> 00:01:00.930
<v Speaker 2>is, um, people might be familiar with you
already listening, but.

19
00:01:01.459 --> 00:01:05.610
<v Speaker 2>Just give us a brief overview of your
career so far, where you started from, and

20
00:01:05.610 --> 00:01:07.279
<v Speaker 2>that'll just open it up to wherever yeah,
with

21
00:01:07.279 --> 00:01:08.550
<v Tom Jacques>pleasure.

22
00:01:08.849 --> 00:01:13.089
<v Tom Jacques>Um, so, yeah, hi, my name's Tom, as you
know very well, and we've done these things

23
00:01:13.089 --> 00:01:18.480
<v Tom Jacques>a few times, I think when it comes to my
career, I mean, I could start when I was 3

24
00:01:18.480 --> 00:01:19.129
<v Tom Jacques>or 4.

25
00:01:19.860 --> 00:01:23.459
<v Tom Jacques>Sounds bizarre, but that comes from a, a,
a history of agricultural maintenance.

26
00:01:23.660 --> 00:01:28.540
<v Tom Jacques>So my dad's got his own business, um,
which is very heavily focused on maintaining

27
00:01:28.540 --> 00:01:32.500
<v Tom Jacques>machines, maintaining assets in automotive
space, anything to do with agriculture.

28
00:01:32.900 --> 00:01:36.059
<v Tom Jacques>So, you've gotta think, as a 3 year old,
that's where I first started to see things

29
00:01:36.059 --> 00:01:40.580
<v Tom Jacques>like bearings and sprockets and chains,
and that's then had a big impact on, on the

30
00:01:40.580 --> 00:01:41.839
<v Tom Jacques>direction my career's gone in.

31
00:01:42.500 --> 00:01:47.419
<v Tom Jacques>Now it, it could have continued down that
route of maintenance or of, of mechanical

32
00:01:47.419 --> 00:01:47.870
<v Tom Jacques>processes.

33
00:01:48.279 --> 00:01:51.730
<v Tom Jacques>But actually I ended up doing an
apprenticeship, uh, with Siemens in, in Germany,

34
00:01:51.930 --> 00:01:56.150
<v Tom Jacques>uh, and that was really focused on
automation, so Control and automation,

35
00:01:56.290 --> 00:02:00.209
<v Tom Jacques>Mechatronics was the degree, and that's
taken me down the route of digitalization,

36
00:02:00.370 --> 00:02:03.930
<v Tom Jacques>what you can do with sensors, what you can
do with PLCs and control systems, and

37
00:02:03.930 --> 00:02:06.050
<v Tom Jacques>now, of course, what we can do with
Artificial Intelligence.

38
00:02:06.169 --> 00:02:10.050
<v Tom Jacques>So, you, you literally just combine those,
those two things that I really enjoy

39
00:02:10.050 --> 00:02:13.550
<v Tom Jacques>doing, um, and that's my career, so I'm
very fortunate.

40
00:02:14.070 --> 00:02:17.110
<v Speaker 2>And I think you're right to start with
that as well, like because I, even I didn't

41
00:02:17.110 --> 00:02:20.970
<v Speaker 2>know that, so it started all the way, all
the way back, way, way back when.

42
00:02:21.389 --> 00:02:25.740
<v Speaker 2>And I guess I mean if we take it from that
point, from the point of childhood and

43
00:02:25.740 --> 00:02:29.419
<v Speaker 2>having an interest in that to where you
sort of started to work on shop floors and

44
00:02:29.419 --> 00:02:32.039
<v Speaker 2>stuff, how, how did you sort of, what was
the transition to that?

45
00:02:32.270 --> 00:02:32.550
<v Tom Jacques>How did that?

46
00:02:32.580 --> 00:02:36.350
<v Tom Jacques>Um, really the transition came from, you
remember at school you have to do work

47
00:02:36.350 --> 00:02:36.979
<v Tom Jacques>placements.

48
00:02:37.309 --> 00:02:42.309
<v Tom Jacques>So my first work placement was when I was
maybe sort of 1516 years old if I remember

49
00:02:42.309 --> 00:02:42.699
<v Tom Jacques>rightly.

50
00:02:43.179 --> 00:02:48.380
<v Tom Jacques>And that was doing control and automation,
uh, on lots of machinery in a small, um,

51
00:02:48.779 --> 00:02:52.619
<v Tom Jacques>effectively OEM manufacturer where they
made custom projects for different

52
00:02:52.619 --> 00:02:57.339
<v Tom Jacques>customers, and some of it was, was defense
customers, some of it was, you know,

53
00:02:57.419 --> 00:02:58.300
<v Tom Jacques>other machinery.

54
00:02:58.699 --> 00:03:02.380
<v Tom Jacques>Uh, one of the famous things they created
was a, a small, uh, machine that could put

55
00:03:02.380 --> 00:03:03.960
<v Tom Jacques>the springs into the barrel of a lock.

56
00:03:04.139 --> 00:03:08.740
<v Tom Jacques>That was all patented technology, really
clever stuff, and, and that's kind of where

57
00:03:08.740 --> 00:03:12.520
<v Tom Jacques>I first saw, you know, wiring systems,
PLCs linked together.

58
00:03:13.199 --> 00:03:16.639
<v Tom Jacques>And obviously, I came back from this
experience bouncing off the walls just thinking

59
00:03:16.639 --> 00:03:20.800
<v Tom Jacques>this is, this is what I wanna do, this is
really, um, it makes me passionate about

60
00:03:20.800 --> 00:03:21.300
<v Tom Jacques>engineering.

61
00:03:21.759 --> 00:03:26.800
<v Tom Jacques>It also makes me wanna see where I can
take this in my career, so let's, let's, you

62
00:03:26.800 --> 00:03:30.550
<v Tom Jacques>know, in many ways I've, I've been
fortunate that it's continuously gone in this

63
00:03:30.550 --> 00:03:32.160
<v Tom Jacques>direction, not straight down the middle.

64
00:03:32.679 --> 00:03:35.960
<v Tom Jacques>Sometimes it's gone off in a, in a control
and automation direction with electronics

65
00:03:35.960 --> 00:03:40.160
<v Tom Jacques>and so on, and equally it's gone off in
the hydraulics and lubrication direction,

66
00:03:41.119 --> 00:03:42.580
<v Tom Jacques>uh, we can, we can go into that.

67
00:03:43.520 --> 00:03:46.850
<v Speaker 2>Yeah, um, I guess how have all these sort
of, again, we could go into maybe more,

68
00:03:46.970 --> 00:03:51.169
<v Speaker 2>more of the specifics, but how to going
all these different directions and having

69
00:03:51.169 --> 00:03:55.009
<v Speaker 2>experiences in this, in these different
areas, how has that sort of shaped what you

70
00:03:55.009 --> 00:03:56.460
<v Speaker 2>do today at Siemens?

71
00:03:56.529 --> 00:03:57.350
<v Tom Jacques>That's a great question.

72
00:03:57.449 --> 00:04:01.309
<v Tom Jacques>So what that's allowed me to do is see
things from lots of different perspectives.

73
00:04:01.729 --> 00:04:05.169
<v Tom Jacques>If I walk into a customer, I can
understand pretty well the kind of problems that

74
00:04:05.169 --> 00:04:09.289
<v Tom Jacques>they're gonna face, um, as a solutions
engineer, pre-sales engineer, that's really

75
00:04:09.289 --> 00:04:11.050
<v Tom Jacques>what we need to be able to do very well,
so.

76
00:04:11.529 --> 00:04:15.250
<v Tom Jacques>That's been able to understand which
assets are critical, what does downtime mean in

77
00:04:15.250 --> 00:04:18.170
<v Tom Jacques>a certain facility, so you have to have a
good understanding of, you know,

78
00:04:18.250 --> 00:04:22.950
<v Tom Jacques>mechanical degradation, how does, how does
a, a, a bearing fail, why would it fail,

79
00:04:23.410 --> 00:04:27.130
<v Tom Jacques>um, is it due to the, the, the oil that
you use, the lubrication system, the pump

80
00:04:27.130 --> 00:04:28.700
<v Tom Jacques>that supplies that lubrication oil?

81
00:04:28.890 --> 00:04:32.649
<v Tom Jacques>There's lots and lots of different failure
modes in the facility, and then you start

82
00:04:32.649 --> 00:04:35.869
<v Tom Jacques>to look at entire production lines, so
there's loads and loads of different assets.

83
00:04:36.399 --> 00:04:39.269
<v Tom Jacques>You start to look at, you know, entirely
different processes.

84
00:04:39.540 --> 00:04:43.929
<v Tom Jacques>Famously, we're agnostic at Sensei, so
that's everything from a steel mill, a paper

85
00:04:43.929 --> 00:04:47.359
<v Tom Jacques>mill, um, a food and beverage facility, a
pharmaceutical process.

86
00:04:47.519 --> 00:04:49.910
<v Tom Jacques>So, I've seen lots and lots of different
machines.

87
00:04:50.029 --> 00:04:53.920
<v Tom Jacques>I've seen how they fail, and then
crucially, you know how to, how to offer solutions

88
00:04:53.920 --> 00:04:57.399
<v Tom Jacques>and offer suggestions to, to fix those
things, which we have done now very

89
00:04:57.399 --> 00:04:57.899
<v Tom Jacques>successfully.

90
00:04:58.589 --> 00:05:00.070
<v Speaker 2>Yeah, I guess that was the question I was
gonna ask.

91
00:05:00.109 --> 00:05:02.869
<v Speaker 2>What sort of, maybe you answered it a
little bit there about how, you know, what

92
00:05:02.869 --> 00:05:04.390
<v Speaker 2>sparked the interest in predictive
maintenance.

93
00:05:04.489 --> 00:05:08.429
<v Speaker 2>When did you first come across it maybe as
a, as a concept in your own sort of day

94
00:05:08.429 --> 00:05:08.970
<v Speaker 2>to day?

95
00:05:09.470 --> 00:05:14.100
<v Tom Jacques>I think, I think predictive maintenance
for me really became, uh, my main topic of

96
00:05:14.100 --> 00:05:17.429
<v Tom Jacques>focus being the head of an Industry 4
development division, um.

97
00:05:17.940 --> 00:05:22.190
<v Tom Jacques>This is for another German um equipment
manufacturer and parts supplier and, and

98
00:05:22.190 --> 00:05:27.149
<v Tom Jacques>really there what I was able to do was,
was lead a team, lead the division of, you

99
00:05:27.149 --> 00:05:28.190
<v Tom Jacques>know, what are we trying to achieve?

100
00:05:28.390 --> 00:05:32.510
<v Tom Jacques>We're trying to digitalize hydraulic
lubrication systems and that's where I first

101
00:05:32.510 --> 00:05:36.429
<v Tom Jacques>saw, you know, with things like Tribology
and what you can do by, by analyzing a

102
00:05:36.429 --> 00:05:36.869
<v Tom Jacques>fluid.

103
00:05:37.929 --> 00:05:41.769
<v Tom Jacques>How that impacts the way the machine's
gonna degrade from that point onwards, so

104
00:05:41.769 --> 00:05:45.170
<v Tom Jacques>it's not in a failing state at the moment,
but it's going to get into a failing

105
00:05:45.170 --> 00:05:48.890
<v Tom Jacques>state pretty quickly, so you need to be
able to anticipate, um, and there's a lot of

106
00:05:48.890 --> 00:05:52.450
<v Tom Jacques>money to be made as well in, in if, if you
can anticipate when that's, when that

107
00:05:52.450 --> 00:05:53.529
<v Tom Jacques>failure's gonna take place.

108
00:05:54.329 --> 00:06:01.290
<v Tom Jacques>So my, my sort of focus there, I think was
probably the best word to use, is how do

109
00:06:01.290 --> 00:06:01.959
<v Tom Jacques>we do this?

110
00:06:02.209 --> 00:06:05.970
<v Tom Jacques>Which sensors should we use, which, which
equipment do we need to make that happen,

111
00:06:06.049 --> 00:06:07.089
<v Tom Jacques>you know, most effectively.

112
00:06:07.809 --> 00:06:11.410
<v Tom Jacques>And as I've then gone into it, you start
to realize that time-based maintenance is

113
00:06:11.410 --> 00:06:12.769
<v Tom Jacques>a, is a certain element of it.

114
00:06:13.559 --> 00:06:17.769
<v Tom Jacques>But really with predictive maintenance,
you can remove standard time-based intervals

115
00:06:18.000 --> 00:06:21.750
<v Tom Jacques>and convert it entirely to a, an
intelligent software that's just looking at the

116
00:06:21.750 --> 00:06:26.350
<v Tom Jacques>health of a system, um, you know, exactly,
I often say this as, as like an

117
00:06:26.350 --> 00:06:30.109
<v Tom Jacques>individual patient in a hospital or in a
surgery, is effectively how you should look

118
00:06:30.109 --> 00:06:35.109
<v Tom Jacques>at every machine, so we see this with a,
with a filling line, let's say, every piece

119
00:06:35.109 --> 00:06:39.730
<v Tom Jacques>of equipment there has its own, its own
ailments, it's own, it's own history.

120
00:06:40.390 --> 00:06:44.070
<v Tom Jacques>If you can document that in a piece of
software, you've got some clever AI that can

121
00:06:44.070 --> 00:06:49.070
<v Tom Jacques>monitor it, suddenly you can anticipate
pretty accurately as well, when is it gonna

122
00:06:49.070 --> 00:06:52.630
<v Tom Jacques>fail, how is it gonna fail, what do we
need to do to, to anticipate that and to

123
00:06:52.630 --> 00:06:56.029
<v Tom Jacques>mitigate that downtime or over-maintenance
that we might be doing.

124
00:06:56.230 --> 00:07:01.470
<v Tom Jacques>Um, so it's, it's a real, it's a real
fascination from my perspective to see how you

125
00:07:01.470 --> 00:07:05.320
<v Tom Jacques>can solve mechanical problems with a piece
of, a piece of software.

126
00:07:06.140 --> 00:07:10.190
<v Speaker 2>And, and the fact you've seen sort of both
sides, does that, that must make it easy

127
00:07:10.190 --> 00:07:13.190
<v Speaker 2>when you're speaking to customers today
that you're, you know, you're not just, you

128
00:07:13.190 --> 00:07:16.989
<v Speaker 2>know, I've only worked in software and I
know this and that, you've actually seen

129
00:07:16.989 --> 00:07:20.250
<v Speaker 2>what they've seen, experienced what
they've experienced, that must help greatly,

130
00:07:20.309 --> 00:07:20.470
<v Speaker 2>right?

131
00:07:20.589 --> 00:07:25.290
<v Tom Jacques>I think it really helps to do, to do with,
um, respect from a certain degree because

132
00:07:25.390 --> 00:07:29.549
<v Tom Jacques>if the customer can understand that I
understand their problem, I've surprised a few

133
00:07:29.549 --> 00:07:33.630
<v Tom Jacques>customers as well in the past, um, because
I think typically solutions engineers

134
00:07:33.630 --> 00:07:34.790
<v Tom Jacques>have to have been through the mill.

135
00:07:35.209 --> 00:07:38.980
<v Tom Jacques>Ironically, steel mill, paper mill, you
name it, but you end up having to have seen

136
00:07:38.980 --> 00:07:42.019
<v Tom Jacques>lots and lots of different things, and
I've been fortunate enough to have seen

137
00:07:42.019 --> 00:07:48.690
<v Tom Jacques>loads, um, at the age of 30, so, um, and
also what I've seen very often as well is,

138
00:07:48.820 --> 00:07:53.660
<v Tom Jacques>is how intelligent, and I really mean
this, the, the standard maintenance engineer

139
00:07:53.660 --> 00:07:54.260
<v Tom Jacques>is becoming.

140
00:07:54.630 --> 00:07:58.899
<v Tom Jacques>It's no longer someone who just uses
spanners and, and certain mechanical tools to

141
00:07:58.899 --> 00:07:59.339
<v Tom Jacques>fix things.

142
00:07:59.380 --> 00:08:03.220
<v Tom Jacques>They know how to diagnose problems, they
know how to interact with software and, and

143
00:08:03.220 --> 00:08:07.140
<v Tom Jacques>maybe do some controls and automation
stuff on the side to interrogate a failure

144
00:08:07.140 --> 00:08:08.660
<v Tom Jacques>code on a PLC or something like that.

145
00:08:08.779 --> 00:08:12.579
<v Tom Jacques>So, we're starting to see a little bit of
a shift in industry, um, which, which

146
00:08:12.579 --> 00:08:13.980
<v Tom Jacques>aligns well to my skill set.

147
00:08:14.540 --> 00:08:18.140
<v Speaker 2>And, and actually that, that, that leads
very nicely onto this, this question about

148
00:08:18.140 --> 00:08:22.559
<v Speaker 2>may, cos on the face of it, working on the
shop floor and working now as a solution

149
00:08:22.559 --> 00:08:26.019
<v Speaker 2>engineer at Siemens are completely
different things, but by the sound of it, they're

150
00:08:26.019 --> 00:08:28.140
<v Speaker 2>getting closer and closer together.

151
00:08:28.380 --> 00:08:28.500
<v Speaker 2>They

152
00:08:28.500 --> 00:08:32.780
<v Tom Jacques>are, they are, they're getting a, they're
getting much closer, um, because of how

153
00:08:32.780 --> 00:08:34.119
<v Tom Jacques>intelligent the software's getting.

154
00:08:34.260 --> 00:08:38.099
<v Tom Jacques>So for many, many years we've had the
ability to do condition monitoring, so

155
00:08:38.099 --> 00:08:42.280
<v Tom Jacques>condition-based maintenance where you, you
can just effectively see in a software

156
00:08:42.739 --> 00:08:43.200
<v Tom Jacques>if.

157
00:08:43.710 --> 00:08:49.239
<v Tom Jacques>Temperature equals 80 degrees, um, then we
send an alert, and that's that's been

158
00:08:49.239 --> 00:08:53.710
<v Tom Jacques>possible for many, many years, you know,
decades, but now with the, with the, um,

159
00:08:53.719 --> 00:08:58.510
<v Tom Jacques>the dawn of Artificial intelligence and
how intelligent it's now getting, we end up

160
00:08:58.510 --> 00:09:04.229
<v Tom Jacques>in a situation where, The software can
anticipate based on live telemetry,

161
00:09:04.349 --> 00:09:09.429
<v Tom Jacques>historical, um, you know, data from that
machine, looking at the PDF documents, any

162
00:09:09.429 --> 00:09:13.510
<v Tom Jacques>other um document that we've got, a a
manual, uh, a user spec sheet,

163
00:09:13.669 --> 00:09:17.510
<v Tom Jacques>anything like that, it can now read it and
look down through the document, see what

164
00:09:17.510 --> 00:09:20.900
<v Tom Jacques>you, what oil do you need, what problem
is, is there to be fixed, exactly the steps

165
00:09:20.900 --> 00:09:23.710
<v Tom Jacques>you should take to change a filter or to
change a bearing.

166
00:09:24.469 --> 00:09:26.799
<v Tom Jacques>And that's really fascinating from my
side, because.

167
00:09:27.929 --> 00:09:33.130
<v Tom Jacques>You know, we're gonna, we're gonna see
this, this get much, much closer, and we'll

168
00:09:33.130 --> 00:09:38.159
<v Tom Jacques>end up, I'm sure in about 5 or 10 years
where we, we can't even imagine maintenance

169
00:09:38.460 --> 00:09:41.619
<v Tom Jacques>without having this intelligent software
bolted onto the side of it.

170
00:09:43.109 --> 00:09:48.190
<v Speaker 2>And I guess to that point, do you, would
you say that PDM or predictive maintenance,

171
00:09:48.390 --> 00:09:52.070
<v Speaker 2>give it its full title, is, is becoming
more accessible now compared to when you,

172
00:09:52.179 --> 00:09:55.150
<v Speaker 2>you know, first start to, you know,
working on the shop floor, for example, it's

173
00:09:55.150 --> 00:09:59.190
<v Speaker 2>more accessible to maintenance engineers
and, and organizations as a whole.

174
00:09:59.289 --> 00:10:00.270
<v Tom Jacques>It is, yeah, it is.

175
00:10:00.349 --> 00:10:03.750
<v Tom Jacques>That's a great question because, because
what you need to try and do is understand

176
00:10:03.750 --> 00:10:09.030
<v Tom Jacques>how do we build the algorithm, you know,
in, in a classic example of, um, monitoring

177
00:10:09.030 --> 00:10:09.669
<v Tom Jacques>turbines.

178
00:10:10.659 --> 00:10:14.260
<v Tom Jacques>You know, you've got quite a few PhD
Engineers to put together a mathematic model of

179
00:10:14.260 --> 00:10:16.179
<v Tom Jacques>what that turbine is gonna do next.

180
00:10:16.700 --> 00:10:21.419
<v Tom Jacques>That asset is worth multi-millions,
downtime is effectively unavoidable, you need it

181
00:10:21.419 --> 00:10:22.679
<v Tom Jacques>to do its job.

182
00:10:24.130 --> 00:10:27.809
<v Tom Jacques>How do you then translate that across to a
smaller asset which has less of an impact

183
00:10:27.809 --> 00:10:29.650
<v Tom Jacques>but equally still a big impact?

184
00:10:30.049 --> 00:10:35.849
<v Tom Jacques>Now Sense I does that with, with
effectively an agnostic solution, um, building a, a

185
00:10:35.849 --> 00:10:39.450
<v Tom Jacques>tool that can learn baseline of an asset
in 2 to 5 days, normal operation.

186
00:10:40.359 --> 00:10:44.200
<v Tom Jacques>Now when I first learned that, it made me
wanna be part of the team because that's a

187
00:10:44.200 --> 00:10:48.239
<v Tom Jacques>breakthrough in this sector, uh, and being
able to do that on any asset, be that a,

188
00:10:48.320 --> 00:10:52.510
<v Tom Jacques>a, a critical conveyor or, or a filling
line or, or any other asset that you see in

189
00:10:52.510 --> 00:10:52.859
<v Tom Jacques>the industry.

190
00:10:53.700 --> 00:10:57.510
<v Tom Jacques>To understand and be able to build a
mathematic model, um, obviously there's a lot

191
00:10:57.510 --> 00:11:01.989
<v Tom Jacques>more to it with, with patented technology
in the background, how do we, how do we,

192
00:11:02.309 --> 00:11:06.109
<v Tom Jacques>you know, understand what the fingerprint
is of that asset?

193
00:11:06.969 --> 00:11:12.090
<v Tom Jacques>And then map that across an entire factory
of rotating, non-rotating assets, you

194
00:11:12.090 --> 00:11:15.489
<v Tom Jacques>know, HVAC on the roof and something else,
so utilities are also included.

195
00:11:16.390 --> 00:11:18.409
<v Tom Jacques>It's amazing, it really is incredible.

196
00:11:19.500 --> 00:11:24.109
<v Speaker 2>And how have you, how do you find
translating that, you know, cos, you know, you

197
00:11:24.109 --> 00:11:28.349
<v Speaker 2>know, maybe someone like me maybe, you
know, joined Sensi a few years ago and was

198
00:11:28.349 --> 00:11:32.140
<v Speaker 2>like, oh this is very technical anomaly
detection and all these buzzwords and stuff,

199
00:11:32.210 --> 00:11:35.219
<v Speaker 2>but you, you, you must find a way to,
well, I mean that's your job really is to

200
00:11:35.219 --> 00:11:38.510
<v Speaker 2>translate that into tangible results.

201
00:11:38.619 --> 00:11:41.869
<v Tom Jacques>I think in terms of translating it, what
we, what we often see is a customer who

202
00:11:41.869 --> 00:11:45.390
<v Tom Jacques>knows the problem and then they've got
sensors and data and all the rest of it to,

203
00:11:45.510 --> 00:11:47.030
<v Tom Jacques>to try and anticipate what's going wrong.

204
00:11:47.150 --> 00:11:48.770
<v Tom Jacques>So they say, well, we've got all the data.

205
00:11:49.450 --> 00:11:53.070
<v Tom Jacques>We've, we've built all this stuff
together, we've linked the SCAA into a Historian,

206
00:11:53.650 --> 00:11:57.289
<v Tom Jacques>but we, we now don't know what to do with
that data, we don't know what's next, we

207
00:11:57.289 --> 00:12:00.869
<v Tom Jacques>don't know how to, how do we get some sort
of tangible insight from that?

208
00:12:01.750 --> 00:12:05.909
<v Tom Jacques>The answer is you need a software that's
got the capability to, to do something very

209
00:12:05.909 --> 00:12:08.140
<v Tom Jacques>useful with that software, and that's what
Sensei is.

210
00:12:08.309 --> 00:12:12.429
<v Tom Jacques>So, this is one of the reasons we're
winning big contracts because we're effectively

211
00:12:12.429 --> 00:12:15.710
<v Tom Jacques>the only product, uh, product on the
market that can do that.

212
00:12:16.489 --> 00:12:21.770
<v Tom Jacques>And it's very hard, um, we could go into
the specifics of, of how the software

213
00:12:21.770 --> 00:12:25.549
<v Tom Jacques>works, but I'll leave James to, to do
that, you know, very well, our head of

214
00:12:25.549 --> 00:12:26.330
<v Tom Jacques>Research and Development.

215
00:12:27.320 --> 00:12:30.619
<v Tom Jacques>And there's, there's other podcasts that
he covers it really, really well, so I

216
00:12:30.619 --> 00:12:34.929
<v Tom Jacques>won't try and paraphrase it, but
effectively if you can monitor all those different

217
00:12:34.929 --> 00:12:41.369
<v Tom Jacques>machines, it gives the customer like this,
this hope I guess that we can now do

218
00:12:41.369 --> 00:12:44.890
<v Tom Jacques>something with what they've worked so hard
to put into place, um.

219
00:12:45.690 --> 00:12:51.070
<v Tom Jacques>So to come back to what we talked about
earlier, um, you know, why does this job

220
00:12:51.210 --> 00:12:53.590
<v Tom Jacques>make so much, uh, you know, why is it so
enjoyable?

221
00:12:54.250 --> 00:12:57.590
<v Tom Jacques>It's because you, you're working to solve
customers' problems.

222
00:12:58.479 --> 00:13:02.460
<v Tom Jacques>And that feels really good, it feels good
to help a customer who, who'd done

223
00:13:02.460 --> 00:13:06.469
<v Tom Jacques>everything they possibly could, except for
that last piece that we then fill in the

224
00:13:06.469 --> 00:13:09.700
<v Tom Jacques>blanks and we, we sort of complete the
puzzle, um.

225
00:13:11.599 --> 00:13:15.859
<v Tom Jacques>And I, I think when it comes to what do we
see most, so when, when a customer really

226
00:13:16.119 --> 00:13:16.900
<v Tom Jacques>has a problem.

227
00:13:17.669 --> 00:13:20.130
<v Tom Jacques>You know, is it because they're over
maintaining the, the asset?

228
00:13:20.229 --> 00:13:24.070
<v Tom Jacques>Is it because they're, they keep reacting
to downtime, they don't understand why it

229
00:13:24.070 --> 00:13:24.809
<v Tom Jacques>keeps happening?

230
00:13:25.309 --> 00:13:28.710
<v Tom Jacques>It might be because they're on a
shoestring budget and they don't have the resources

231
00:13:28.710 --> 00:13:29.510
<v Tom Jacques>that they actually need.

232
00:13:30.330 --> 00:13:34.369
<v Tom Jacques>So in many ways we're, we're kind of,
we're not solving one problem, we're helping

233
00:13:34.369 --> 00:13:38.619
<v Tom Jacques>them solve a whole host of different
things, um, included within that of course is

234
00:13:38.619 --> 00:13:40.770
<v Tom Jacques>also safety, we've done an entire topic of
this.

235
00:13:41.280 --> 00:13:41.809
<v Tom Jacques>Yeah we um.

236
00:13:42.760 --> 00:13:47.729
<v Tom Jacques>And it's, it's then a case of are the
assets in a, in a sustainable, um, operation,

237
00:13:47.830 --> 00:13:51.909
<v Tom Jacques>like if something's about to critically
fail, is someone's life at risk?

238
00:13:52.690 --> 00:13:55.729
<v Tom Jacques>So suddenly, you know, you can put a price
to downtime, you can put a price to lots

239
00:13:55.729 --> 00:14:00.090
<v Tom Jacques>of other things, but then, but then
there's even more important things to dis to

240
00:14:00.090 --> 00:14:02.909
<v Tom Jacques>discuss, you know, you could lose a leg if
a, if a machine goes wrong.

241
00:14:03.409 --> 00:14:06.849
<v Tom Jacques>Um, I've seen some of the things that go
wrong in hydraulics, for example, um.

242
00:14:07.580 --> 00:14:10.809
<v Tom Jacques>And then you have to just make sure those
assets are healthy, uh, and that's what

243
00:14:10.809 --> 00:14:11.309
<v Tom Jacques>we're doing.

244
00:14:12.210 --> 00:14:15.299
<v Speaker 2>And I, I guess another sort of angle to
it, because, of course, there's people who

245
00:14:15.299 --> 00:14:19.099
<v Speaker 2>know they've got a problem, they need
software or an approach like predicting

246
00:14:19.099 --> 00:14:24.020
<v Speaker 2>maintenance to solve that, but you must
come across, um, you know, different

247
00:14:24.020 --> 00:14:25.780
<v Speaker 2>organizations that maybe take a different
view.

248
00:14:25.849 --> 00:14:28.820
<v Speaker 2>They've got their own traditional
practices, and they're like, you know, why should

249
00:14:28.820 --> 00:14:29.659
<v Speaker 2>we change?

250
00:14:29.700 --> 00:14:31.159
<v Speaker 2>And, you know, coming from that angle.

251
00:14:31.419 --> 00:14:36.460
<v Speaker 2>And I'd imagine your your past experience
can again, can help see it from the other

252
00:14:36.460 --> 00:14:37.799
<v Speaker 2>side again, and

253
00:14:38.059 --> 00:14:40.440
<v Tom Jacques>that's a good, that's a, that's a great
question, because if you think.

254
00:14:40.719 --> 00:14:43.039
<v Tom Jacques>You know, we've done everything we can,
um.

255
00:14:43.770 --> 00:14:47.250
<v Tom Jacques>The one thing you don't wanna do is offend
anybody and say, well, wait, what you've

256
00:14:47.250 --> 00:14:50.929
<v Tom Jacques>got here, it's not good enough or
whatever, it's like what you've got here, you've

257
00:14:50.929 --> 00:14:52.630
<v Tom Jacques>done as, as well with that as you can.

258
00:14:53.169 --> 00:14:55.780
<v Tom Jacques>What we can do now is we can help you get
to the next level.

259
00:14:55.969 --> 00:14:57.169
<v Tom Jacques>Um, that's what Sensi's doing.

260
00:14:57.250 --> 00:15:00.000
<v Tom Jacques>We're doing that with, you know, big
multinational corporations.

261
00:15:00.320 --> 00:15:01.869
<v Tom Jacques>Equally, we're doing that with smaller
companies.

262
00:15:02.090 --> 00:15:05.940
<v Tom Jacques>We, we've got some good examples now in,
in pharmaceutical space that are smaller,

263
00:15:06.049 --> 00:15:07.530
<v Tom Jacques>but the downtime impact is massive.

264
00:15:07.679 --> 00:15:10.309
<v Tom Jacques>You know, you lose a batch, you lose 2
million pounds worth of product.

265
00:15:11.109 --> 00:15:16.239
<v Tom Jacques>If you can start to anticipate when a a
compressor is about to break or a cooler or

266
00:15:16.239 --> 00:15:17.239
<v Tom Jacques>any kind of other system.

267
00:15:18.159 --> 00:15:22.479
<v Tom Jacques>And you really can see that as well, so if
you can start to see in the data, um.

268
00:15:23.219 --> 00:15:26.130
<v Tom Jacques>You know, you start to get an upward trend
or some sort of step change in the data.

269
00:15:27.750 --> 00:15:31.469
<v Tom Jacques>You and I could look at that with our own
eyes and see something within it, but

270
00:15:31.469 --> 00:15:36.869
<v Tom Jacques>since I can do so much more with the same
piece of information, plus what it says in

271
00:15:36.869 --> 00:15:40.270
<v Tom Jacques>the user spec sheet, plus what it says,
you know, in the last case closure that was,

272
00:15:40.340 --> 00:15:40.940
<v Tom Jacques>that was had.

273
00:15:41.849 --> 00:15:47.119
<v Tom Jacques>What exactly is, is this going to look
like as a failure and, and what do we need to

274
00:15:47.119 --> 00:15:48.309
<v Tom Jacques>do next to, to solve it?

275
00:15:48.359 --> 00:15:53.659
<v Tom Jacques>So let's get onto that later on, but
where, where does Sens I add value?

276
00:15:53.950 --> 00:15:57.559
<v Tom Jacques>For me, it's 10% of it is anticipating
what's gonna happen next.

277
00:15:58.119 --> 00:16:02.219
<v Tom Jacques>90% of it now, especially with co-pilot,
is how do we then fix that?

278
00:16:02.859 --> 00:16:06.340
<v Tom Jacques>So understanding that, you know, you can
see the problem sooner, but then being able

279
00:16:06.340 --> 00:16:10.460
<v Tom Jacques>to solve it much faster is amazing because
you can, you can get the spare parts into

280
00:16:10.460 --> 00:16:14.940
<v Tom Jacques>stock, you can anticipate what maintenance
is, is needed to be scheduled, um.

281
00:16:15.789 --> 00:16:19.549
<v Tom Jacques>And I've maybe far more than answered your
question, but it's,

282
00:16:19.739 --> 00:16:23.320
<v Speaker 2>well, I mean, I mean just to, uh, you
know, you definitely have, I'll just maybe we

283
00:16:23.320 --> 00:16:27.510
<v Speaker 2>could draw more on some of the objections
to some of that, cos even, you know, even

284
00:16:27.510 --> 00:16:30.419
<v Speaker 2>if you present it as like, you know, this
is your solution, there's still gonna be.

285
00:16:31.150 --> 00:16:35.950
<v Speaker 2>You know, skeptics, let's say, in terms
of, you know, you know, how it can be

286
00:16:35.950 --> 00:16:38.789
<v Speaker 2>deployed, what sort of return on
investment it can provide and that kind of thing.

287
00:16:38.909 --> 00:16:41.229
<v Speaker 2>So how do you sort of use your perspective
to.

288
00:16:41.840 --> 00:16:45.950
<v Speaker 2>No, to shape theirs, and, you know,
without, you know, like, to your point, without

289
00:16:45.950 --> 00:16:47.549
<v Speaker 2>saying everything you're doing is

290
00:16:48.030 --> 00:16:48.669
<v Tom Jacques>a waste of time.

291
00:16:48.789 --> 00:16:48.830
<v Tom Jacques>Yeah,

292
00:16:48.919 --> 00:16:49.710
<v Speaker 2>yeah, exactly, it's, well,

293
00:16:49.750 --> 00:16:50.859
<v Tom Jacques>you, you're exactly right.

294
00:16:51.109 --> 00:16:55.510
<v Tom Jacques>What you need to do first of all, what we
typically try and do is understand what is

295
00:16:55.510 --> 00:16:56.289
<v Tom Jacques>currently going wrong.

296
00:16:57.030 --> 00:17:00.109
<v Tom Jacques>Do we already have an understanding of
what are the exact costs of downtime?

297
00:17:00.150 --> 00:17:03.349
<v Tom Jacques>If you lose production for an hour or for
a day, what does that actually do to

298
00:17:03.349 --> 00:17:04.869
<v Tom Jacques>impact, um, your process?

299
00:17:05.390 --> 00:17:08.510
<v Tom Jacques>More often than not, we talk about it as a
maintenance problem, but what it actually

300
00:17:08.510 --> 00:17:10.170
<v Tom Jacques>is, is a, is a production problem.

301
00:17:10.659 --> 00:17:13.348
<v Tom Jacques>So you've got the production staff
standing around saying, right guys, we need to

302
00:17:13.348 --> 00:17:17.788
<v Tom Jacques>make sure this machine is capable, maybe a
press in a car plant, we need to make

303
00:17:17.788 --> 00:17:22.068
<v Tom Jacques>sure that that can output panels for, you
know, doors, all the rest of it.

304
00:17:23.369 --> 00:17:27.318
<v Tom Jacques>And what you then have to try and do is
make sure you're, you're fulfilling the KPIs

305
00:17:27.318 --> 00:17:28.749
<v Tom Jacques>of different people across the business.

306
00:17:29.168 --> 00:17:32.448
<v Tom Jacques>You know, someone in the Health and Safety
Department wants healthy, safe machinery,

307
00:17:32.649 --> 00:17:37.009
<v Tom Jacques>someone in production wants to maintain
the output, you know, maybe even 24/7 steady

308
00:17:37.009 --> 00:17:40.448
<v Tom Jacques>state operation, making chocolate or
making, uh, potato chips or whatever it is.

309
00:17:41.839 --> 00:17:45.319
<v Tom Jacques>Then the real thing falls down to
maintenance, so you're trying to help them with a

310
00:17:45.319 --> 00:17:50.800
<v Tom Jacques>headache of maintaining asset
availability, and we can do that incredibly well.

311
00:17:51.599 --> 00:17:53.599
<v Tom Jacques>At the top line, who pays for the project?

312
00:17:53.770 --> 00:17:58.800
<v Tom Jacques>So some companies, some industries will
have the purse strings will be controlled by

313
00:17:58.800 --> 00:18:03.609
<v Tom Jacques>maintenance engineers, not very often, but
you get this kind of new role of

314
00:18:03.609 --> 00:18:08.329
<v Tom Jacques>maintenance reliability engineers, maybe a
digitalization IOT team who can start to

315
00:18:08.329 --> 00:18:12.170
<v Tom Jacques>have more of an impact and, and have like
an upward drive through the business and

316
00:18:12.170 --> 00:18:16.209
<v Tom Jacques>say, right, explaining to the management,
the reason we need this software is

317
00:18:16.209 --> 00:18:17.250
<v Tom Jacques>because it does X, Y, and Z.

318
00:18:17.530 --> 00:18:20.770
<v Tom Jacques>It will change our process, it will change
our, our efficiencies and so on.

319
00:18:21.270 --> 00:18:25.189
<v Tom Jacques>And when you can start to explain that in
the KPIs that the management understand

320
00:18:25.579 --> 00:18:28.869
<v Tom Jacques>that it's gonna save money, it's gonna
save time, you can allocate resource more

321
00:18:28.869 --> 00:18:33.229
<v Tom Jacques>effectively, that's where, that's where
the business case starts, starts to stack

322
00:18:33.229 --> 00:18:33.449
<v Tom Jacques>up.

323
00:18:33.869 --> 00:18:39.349
<v Tom Jacques>Um, and I think just to that point,
sometimes you need to say, right, we've got

324
00:18:39.349 --> 00:18:42.670
<v Tom Jacques>loads of sensors, we've got loads of data
in the machinery, but what can we actually

325
00:18:42.670 --> 00:18:42.849
<v Tom Jacques>use?

326
00:18:42.910 --> 00:18:44.949
<v Tom Jacques>What can we leverage from that to make
sense of it?

327
00:18:45.640 --> 00:18:50.680
<v Tom Jacques>And Sometimes a step that can come before
predictive maintenance is connectivity.

328
00:18:50.890 --> 00:18:54.310
<v Tom Jacques>So we're, we're obviously being part of
Siemens now, this is, this is huge.

329
00:18:54.930 --> 00:18:59.250
<v Tom Jacques>You've got the ability to add edge boxes,
to add other protocols in the middle, uh,

330
00:18:59.329 --> 00:19:02.329
<v Tom Jacques>you know, brownfield connectivity is
fantastic for this because you can take

331
00:19:02.329 --> 00:19:07.770
<v Tom Jacques>different, um, different data, different
data types from different machines that all

332
00:19:07.770 --> 00:19:09.270
<v Tom Jacques>effectively speak different languages.

333
00:19:09.689 --> 00:19:13.349
<v Tom Jacques>You can now add a uniformity to that, pull
it into one central location.

334
00:19:13.910 --> 00:19:18.380
<v Tom Jacques>And then fire all of that information
effectively in a uniform state to Sensei.

335
00:19:18.790 --> 00:19:22.180
<v Tom Jacques>You can do the same with Edge, InsightSub,
you can, you can pull all that

336
00:19:22.180 --> 00:19:22.869
<v Tom Jacques>information to cloud.

337
00:19:23.699 --> 00:19:26.140
<v Tom Jacques>And then Sensei does the magic in the
cloud.

338
00:19:27.290 --> 00:19:29.969
<v Tom Jacques>I think what we need to see more of are.

339
00:19:30.829 --> 00:19:36.260
<v Tom Jacques>I think companies Who allow the smarter,
you know, the maintenance teams in the

340
00:19:36.260 --> 00:19:36.719
<v Tom Jacques>middle.

341
00:19:37.410 --> 00:19:41.770
<v Tom Jacques>To, they know the problem, they're trying
to tell you that they've found this

342
00:19:41.770 --> 00:19:45.359
<v Tom Jacques>fantastic solution um and we, I'm speaking
from experience here.

343
00:19:46.189 --> 00:19:50.829
<v Tom Jacques>And, and then we kind of need to, maybe we
need to do better to explain the business

344
00:19:50.829 --> 00:19:56.010
<v Tom Jacques>case of this is how it's gonna impact, um,
you know, downtime, over maintenance,

345
00:19:56.390 --> 00:19:59.310
<v Tom Jacques>overstock and spares that we may not, we
don't need those.

346
00:19:59.469 --> 00:20:00.890
<v Tom Jacques>You see that a lot in the shipping
industry.

347
00:20:01.550 --> 00:20:05.109
<v Tom Jacques>Um, where you have to carry those spares
with you all around the world, and if you,

348
00:20:05.189 --> 00:20:10.189
<v Tom Jacques>if you only knew that that asset is
perfectly fine, you don't need to, you know, do

349
00:20:10.189 --> 00:20:10.739
<v Tom Jacques>anything with it.

350
00:20:10.939 --> 00:20:14.349
<v Tom Jacques>It's a risk that you could take, but it's
a calculated risk now based on intelligent

351
00:20:14.349 --> 00:20:16.170
<v Tom Jacques>software that you, that you learn to
trust.

352
00:20:16.709 --> 00:20:21.300
<v Tom Jacques>Um, and just a small anecdote on that,
we've got a great example with, um,

353
00:20:21.310 --> 00:20:25.380
<v Tom Jacques>Automotive robots, where there used to be
lots of, um, oil samples taken on the

354
00:20:25.380 --> 00:20:26.510
<v Tom Jacques>joints and.

355
00:20:27.170 --> 00:20:31.250
<v Tom Jacques>Effectively what we, what we managed to do
was turn that into a, a process where you

356
00:20:31.250 --> 00:20:36.170
<v Tom Jacques>only react to Sensei, so that customer was
then able to change your process of doing

357
00:20:36.170 --> 00:20:38.530
<v Tom Jacques>something like 800 samples.

358
00:20:39.349 --> 00:20:43.469
<v Tom Jacques>And now only doing, you know, only opening
the joint of the robot when Sensi tells

359
00:20:43.469 --> 00:20:48.250
<v Tom Jacques>them to, tells them that there's a certain
um deviation and an axis on whichever

360
00:20:48.250 --> 00:20:49.930
<v Tom Jacques>servo motor you're talking about.

361
00:20:50.469 --> 00:20:54.469
<v Tom Jacques>And that really changes the process and
it, it, it allows customers for the first

362
00:20:54.469 --> 00:21:00.469
<v Tom Jacques>time I think to say wow, this is how the
software has completely changed our

363
00:21:00.469 --> 00:21:00.859
<v Tom Jacques>process.

364
00:21:01.349 --> 00:21:04.430
<v Tom Jacques>Here we've, we've now got this resource we
can allocate elsewhere.

365
00:21:04.790 --> 00:21:08.420
<v Tom Jacques>This work now doesn't need doing at all,
we've overmaintained that machine for

366
00:21:08.420 --> 00:21:08.750
<v Tom Jacques>years.

367
00:21:09.229 --> 00:21:14.520
<v Tom Jacques>Um, I think the next step, we can go into
where AI is gonna go next, but I think the

368
00:21:14.520 --> 00:21:19.800
<v Tom Jacques>next step is really let's make as much use
as we can from data, so from mainly what

369
00:21:19.800 --> 00:21:21.359
<v Tom Jacques>I'm talking about are things like
documentation.

370
00:21:22.280 --> 00:21:26.449
<v Tom Jacques>If we've got Copilot pulling the
information from a, from a spec sheet, from a user

371
00:21:26.449 --> 00:21:30.849
<v Tom Jacques>manual, it knows now what to do next, and
that's what accelerates you from, we know

372
00:21:30.849 --> 00:21:31.719
<v Tom Jacques>what the problem is.

373
00:21:32.050 --> 00:21:33.609
<v Tom Jacques>Now, now, now what do we need to do to fix
it?

374
00:21:33.729 --> 00:21:35.930
<v Tom Jacques>You know, what's the next step to fix that
as fast as we can.

375
00:21:36.699 --> 00:21:40.500
<v Speaker 2>No, and I guess before we sort of talk
about the future, it might be quite cool to

376
00:21:40.859 --> 00:21:45.579
<v Speaker 2>like imagine, could you have imagined
having a tool like Sensai back when you sort

377
00:21:45.579 --> 00:21:49.520
<v Speaker 2>of started to, to assist you on the shop
floor or similar tools, it doesn't

378
00:21:49.520 --> 00:21:52.380
<v Tom Jacques>have to be, it was destined to happen,
right, so the idea of having a smart

379
00:21:52.380 --> 00:21:56.020
<v Tom Jacques>intelligent software, it's, it's been in
the making for many, many years.

380
00:21:56.099 --> 00:22:00.339
<v Tom Jacques>You can start to see AI's been in
existence for, you know, decades.

381
00:22:00.849 --> 00:22:04.569
<v Tom Jacques>Unbeknownst to lots of people, people who
have, have heard of like the latest craze

382
00:22:04.569 --> 00:22:06.569
<v Tom Jacques>of, you know, ChachiBT and all the rest of
it.

383
00:22:07.270 --> 00:22:12.189
<v Tom Jacques>And, and now it's kind of, you start to
find really useful applications for this.

384
00:22:12.709 --> 00:22:13.680
<v Tom Jacques>This is not a new thing, right?

385
00:22:13.790 --> 00:22:18.310
<v Tom Jacques>Sensi's been doing this for 10 years, and,
and you can see how that, that has

386
00:22:18.310 --> 00:22:23.310
<v Tom Jacques>accelerated us to effectively ahead of the
market because we've seen what we need to

387
00:22:23.310 --> 00:22:28.510
<v Tom Jacques>do to make that work, not on pumps and
motors or chillers or a specific asset type,

388
00:22:28.650 --> 00:22:30.849
<v Tom Jacques>a HHVAC or whatever, on, on everything.

389
00:22:31.189 --> 00:22:35.109
<v Tom Jacques>And the model that Sensi started out with
to do this agnostically across many

390
00:22:35.109 --> 00:22:35.930
<v Tom Jacques>different machines.

391
00:22:36.819 --> 00:22:40.920
<v Tom Jacques>You know, when you look back and you say,
right, who knows how to fix this machine?

392
00:22:42.089 --> 00:22:47.020
<v Tom Jacques>So often the answer is, it's a, it's a guy
called Steve, he's 70 years old, he's

393
00:22:47.020 --> 00:22:50.979
<v Tom Jacques>worked here since he did his
apprenticeship, and, and that's the kind of the bolt

394
00:22:50.979 --> 00:22:54.800
<v Tom Jacques>tapper or, or the, the guy that knows
exactly when the machine sounds different or

395
00:22:54.810 --> 00:22:55.290
<v Tom Jacques>or things like that.

396
00:22:55.300 --> 00:22:56.819
<v Tom Jacques>You hear about that a lot in maintenance.

397
00:22:58.319 --> 00:23:01.420
<v Tom Jacques>And to to digitalize that person's
knowledge.

398
00:23:02.489 --> 00:23:05.239
<v Tom Jacques>Maybe that sounded a little bit out of
reach for a lot of people for a long time,

399
00:23:05.319 --> 00:23:05.560
<v Tom Jacques>but.

400
00:23:06.339 --> 00:23:10.670
<v Tom Jacques>But now I kind of would argue it is
possible and all of the knowledge that let's say

401
00:23:10.670 --> 00:23:13.609
<v Tom Jacques>fictitious Steve has, he can now put that
into a software.

402
00:23:14.150 --> 00:23:17.369
<v Tom Jacques>So Steve can now explain, you know, this
is what I've done to fix the machine.

403
00:23:17.829 --> 00:23:22.260
<v Tom Jacques>I heard this strange harmonic coming from
this part of the, the shaft or the bearing

404
00:23:22.260 --> 00:23:26.069
<v Tom Jacques>or whatever it was, and I know from years
of experience that that means this and

405
00:23:26.069 --> 00:23:26.709
<v Tom Jacques>this and this.

406
00:23:27.310 --> 00:23:30.930
<v Tom Jacques>um, maybe we need to realign something or
there's a, there's something, you know,

407
00:23:31.310 --> 00:23:31.989
<v Tom Jacques>out of square.

408
00:23:33.089 --> 00:23:38.560
<v Tom Jacques>From, from that perspective, being able to
digitalize his knowledge, we are now with

409
00:23:38.560 --> 00:23:43.609
<v Tom Jacques>a piece of software, turning what was
inherently an experience based um skill, being

410
00:23:43.609 --> 00:23:47.449
<v Tom Jacques>able to anticipate failure and and tell
what's wrong with, with a piece of

411
00:23:47.449 --> 00:23:50.770
<v Tom Jacques>equipment, and you're not gonna find that
in a manual, you're not gonna understand

412
00:23:50.770 --> 00:23:53.589
<v Tom Jacques>that, in some cases those assets are
completely unique.

413
00:23:54.040 --> 00:23:56.930
<v Tom Jacques>They've had different things added to them
or they've been changed over the years,

414
00:23:57.010 --> 00:24:01.170
<v Tom Jacques>so it's a completely unique machine, like
a completely unique patient in a hospital,

415
00:24:01.520 --> 00:24:02.650
<v Tom Jacques>you that that comes up often.

416
00:24:04.910 --> 00:24:09.150
<v Tom Jacques>I think now with, with co-pilot and having
the software that's really intelligent,

417
00:24:09.229 --> 00:24:14.390
<v Tom Jacques>the next step is making as much use as we
possibly can out of, out of the context

418
00:24:14.390 --> 00:24:19.099
<v Tom Jacques>of, of that machine, you know, what's, um,
what's the maintenance been like on that

419
00:24:19.099 --> 00:24:20.599
<v Tom Jacques>motor compared to this one?

420
00:24:21.109 --> 00:24:22.310
<v Tom Jacques>How much of an impact has that had?

421
00:24:22.349 --> 00:24:23.869
<v Tom Jacques>You can start to learn that in the
software.

422
00:24:24.150 --> 00:24:27.050
<v Tom Jacques>You know, this motor's about bolted to a
concrete, uh, pedestal.

423
00:24:27.140 --> 00:24:29.209
<v Tom Jacques>This one's on a, on a steel gantry on the
wall.

424
00:24:30.380 --> 00:24:33.089
<v Tom Jacques>They're gonna have different harmonic
signatures, the way they're mounted will be

425
00:24:33.089 --> 00:24:37.180
<v Tom Jacques>different, the way we can, we can change,
um, you know, the way we can also change

426
00:24:37.180 --> 00:24:39.369
<v Tom Jacques>the future factory designs and so on.

427
00:24:39.660 --> 00:24:43.219
<v Tom Jacques>There's lots of softwares across Siemens
where you can simulate the process and with

428
00:24:43.219 --> 00:24:46.819
<v Tom Jacques>the support of Sensor, we can start to
pull that straight back in and say, right,

429
00:24:46.900 --> 00:24:51.130
<v Tom Jacques>now how can we, how can we design better,
you know, production lines.

430
00:24:51.300 --> 00:24:55.140
<v Tom Jacques>We've seen that the way this was, it
always used to go out of misalignment.

431
00:24:55.699 --> 00:25:00.900
<v Tom Jacques>Now because of all the maintenance data
we've got, we can see how to, how to build a

432
00:25:00.900 --> 00:25:05.459
<v Tom Jacques>highly maintainable system that's gonna,
you know, last longer, break down, you

433
00:25:05.459 --> 00:25:08.000
<v Tom Jacques>know, less often and so forth.

434
00:25:08.739 --> 00:25:10.119
<v Tom Jacques>So, yeah, in answer to your question.

435
00:25:11.099 --> 00:25:14.479
<v Tom Jacques>It was, it was destined to happen, to have
a, a smart piece of software.

436
00:25:15.020 --> 00:25:19.180
<v Speaker 2>I guess the, the digitalization aspect, I
guess originally was probably just, yeah,

437
00:25:19.339 --> 00:25:22.819
<v Speaker 2>you know, saving all this knowledge in the
cloud, you know, in like PDFs and

438
00:25:22.819 --> 00:25:27.140
<v Speaker 2>documents and stuff like that, but maybe,
well, the next step is clearly the, you

439
00:25:27.140 --> 00:25:30.849
<v Speaker 2>know, you can upload those to the cloud
and get answers quickly from them amongst

440
00:25:30.849 --> 00:25:33.380
<v Speaker 2>other things and capture the knowledge
like you were, you were talking about then as

441
00:25:33.380 --> 00:25:33.420
<v Speaker 2>well.

442
00:25:33.619 --> 00:25:33.810
<v Speaker 2>That's, that's

443
00:25:33.810 --> 00:25:33.890
<v Tom Jacques>a

444
00:25:33.890 --> 00:25:34.050
<v Speaker 2>good

445
00:25:34.050 --> 00:25:36.160
<v Tom Jacques>point because you say, well, all the
data's available.

446
00:25:36.780 --> 00:25:40.520
<v Tom Jacques>So, OK, off you go then, go and read
through 400 pages of a PDF document.

447
00:25:41.209 --> 00:25:45.380
<v Tom Jacques>And even though it's all there and it's
all possible, it's amazing now, exactly to

448
00:25:45.380 --> 00:25:49.439
<v Tom Jacques>what you're saying about how simple the
the software can make that process.

449
00:25:49.699 --> 00:25:51.989
<v Tom Jacques>Um, I think that's the direction we're
gonna carry on going in.

450
00:25:53.469 --> 00:25:56.430
<v Speaker 2>No, I don't think, yeah, cause I, I was
just looking at the question here cause we

451
00:25:56.430 --> 00:25:58.790
<v Speaker 2>weren't gonna talk about it in the next 5
to 10 years, but I think you've actually

452
00:25:58.790 --> 00:26:00.630
<v Speaker 2>sort of summarized it quite well in, in
those answers.

453
00:26:00.709 --> 00:26:02.260
<v Speaker 2>Is there anything else you'd add to that
at all?

454
00:26:02.459 --> 00:26:04.040
<v Speaker 2>Where are we getting into the crystal
ball?

455
00:26:04.390 --> 00:26:05.530
<v Tom Jacques>Where are we gonna be in 5 years?

456
00:26:06.030 --> 00:26:09.930
<v Tom Jacques>I think, I think the next couple of steps
will be, we have vision.

457
00:26:10.229 --> 00:26:14.290
<v Tom Jacques>I think one of the most interesting things
you start to look at is humanoid robots.

458
00:26:14.989 --> 00:26:18.869
<v Tom Jacques>That's a little bit of a, of a fictitious
scenario at the moment, cos we're not

459
00:26:18.869 --> 00:26:19.530
<v Tom Jacques>quite there yet.

460
00:26:20.260 --> 00:26:23.550
<v Tom Jacques>But let's imagine, let's, let's really go
down that, that, that train of thought.

461
00:26:23.859 --> 00:26:28.719
<v Tom Jacques>If you've got a machine, which is a
humanoid robot, it stands doing maintenance,

462
00:26:28.890 --> 00:26:32.140
<v Tom Jacques>it's, it's got a spanner in its hand and
it's fixing a certain, let's say it's, it's

463
00:26:32.140 --> 00:26:33.859
<v Tom Jacques>repositioning the motor on the, on the
ground.

464
00:26:35.719 --> 00:26:40.719
<v Tom Jacques>For me this is at least, I would say, to
be reliably talking about this kind of

465
00:26:40.719 --> 00:26:42.140
<v Tom Jacques>application, maybe 15 years away.

466
00:26:42.640 --> 00:26:46.430
<v Tom Jacques>But just imagine if you could take the,
the force that was required to tighten that

467
00:26:46.430 --> 00:26:50.199
<v Tom Jacques>spanner, you've got all the vision systems
from the, from the optics of the robot.

468
00:26:50.640 --> 00:26:55.270
<v Tom Jacques>This is an incredible resource in terms of
understanding context of where the asset

469
00:26:55.270 --> 00:27:00.310
<v Tom Jacques>sits in a real life environment, and I
think the sooner that happens, you know,

470
00:27:00.560 --> 00:27:03.119
<v Tom Jacques>sometimes it, it becomes a bit of a
dystopian future, but.

471
00:27:03.839 --> 00:27:06.650
<v Tom Jacques>But we're probably gonna end up in that,
in that area when you look at the

472
00:27:06.650 --> 00:27:09.729
<v Tom Jacques>direction, you know, if you just
extrapolate this out where, where we're going.

473
00:27:10.660 --> 00:27:14.729
<v Tom Jacques>And I think in terms of maintaining
machinery, that's an amazing resource to, to

474
00:27:14.729 --> 00:27:18.489
<v Tom Jacques>have that extra data, you know, the
machine, the torque that was used from the

475
00:27:18.489 --> 00:27:22.680
<v Tom Jacques>server on the elbow of that robot to
tighten, to tighten a certain bolt.

476
00:27:23.170 --> 00:27:27.650
<v Tom Jacques>You can save that into a, into a CMMS
software and, and say, yeah, you know, that's

477
00:27:27.650 --> 00:27:29.390
<v Tom Jacques>exactly what it should have been tightened
to.

478
00:27:29.930 --> 00:27:34.119
<v Tom Jacques>When you did the visual inspection, you
can have small video clips, you can have um

479
00:27:34.250 --> 00:27:36.790
<v Tom Jacques>vision AI systems that, that look at
what's taken place.

480
00:27:37.599 --> 00:27:42.489
<v Tom Jacques>Um, In the near term, in the near term, we
need to start seeing more and more of a,

481
00:27:42.599 --> 00:27:48.130
<v Tom Jacques>a use of, of copilot, more of an
understanding of if you, if you feed all of this

482
00:27:48.130 --> 00:27:51.829
<v Tom Jacques>information into the software, it gets
infinitely smarter, right, so if you've only

483
00:27:51.829 --> 00:27:57.479
<v Tom Jacques>got the ability to, you know, see, let's
say torque, pressure, temperature, and flow

484
00:27:57.479 --> 00:28:02.160
<v Tom Jacques>on a system, if you then have, I'm not
talking about vision, if you, if you just

485
00:28:02.160 --> 00:28:05.849
<v Tom Jacques>have the ability to fill in what the
maintenance teams have done, upload the right

486
00:28:05.849 --> 00:28:06.969
<v Tom Jacques>PDF documentation.

487
00:28:07.489 --> 00:28:10.939
<v Tom Jacques>It starts to very quickly build a, build
a, you know, very broad picture of what's

488
00:28:10.939 --> 00:28:16.219
<v Tom Jacques>going on, um, and you've got that same
asset maybe being maintained in another 10

489
00:28:16.219 --> 00:28:16.839
<v Tom Jacques>factories.

490
00:28:17.380 --> 00:28:20.339
<v Tom Jacques>You set those up as a group or a fleet,
suddenly they're all learning from each

491
00:28:20.339 --> 00:28:20.699
<v Tom Jacques>other.

492
00:28:20.939 --> 00:28:23.839
<v Tom Jacques>We've, we've been doing this for years,
but that's exactly what Senssight's for.

493
00:28:24.260 --> 00:28:28.750
<v Tom Jacques>So you have this like enormously scalable
maintenance knowledge.

494
00:28:29.380 --> 00:28:33.140
<v Tom Jacques>Um, which I and it is kept within your
account, so anything that's learned on a, on

495
00:28:33.140 --> 00:28:38.660
<v Tom Jacques>a machine is unique to a facility, unique
to the tenant of Sensoriye, and, and how

496
00:28:38.660 --> 00:28:43.219
<v Tom Jacques>do we then, you know, how do we monitor
that in a, in a, in a better way in the

497
00:28:43.219 --> 00:28:43.739
<v Tom Jacques>future.

498
00:28:44.339 --> 00:28:49.640
<v Tom Jacques>So sensors will get better, um, the
methodology that we can use for connecting data.

499
00:28:50.420 --> 00:28:54.050
<v Tom Jacques>So from, I love Loroan, I love any sensor
that's really simple.

500
00:28:54.140 --> 00:28:58.339
<v Tom Jacques>We remove any, any data cables, I think,
you know, we need them in some, in some

501
00:28:58.339 --> 00:28:58.880
<v Tom Jacques>areas.

502
00:28:59.349 --> 00:29:01.910
<v Tom Jacques>Particularly maybe in an an ateex area or
something, but.

503
00:29:02.560 --> 00:29:05.930
<v Tom Jacques>If you just have something that's got
batteries, it's got its own method to connect

504
00:29:05.930 --> 00:29:09.030
<v Tom Jacques>to cloud, you can pre-parameterize it and
just go and screw something to a motor.

505
00:29:09.890 --> 00:29:14.010
<v Tom Jacques>That is, that has to be the direction for
the, for the near term future because you

506
00:29:14.010 --> 00:29:18.199
<v Tom Jacques>remove the complexities of install, that's
got cost implications, it's got, it's got

507
00:29:18.199 --> 00:29:20.400
<v Tom Jacques>loads of other benefits to just having
something simple.

508
00:29:20.650 --> 00:29:21.750
<v Tom Jacques>And the technology's there.

509
00:29:22.729 --> 00:29:26.689
<v Tom Jacques>With something particularly like Lorovan,
you've got a signal, um, uh, uh, you know,

510
00:29:26.839 --> 00:29:31.719
<v Tom Jacques>capability to send a signal through 10 m
of concrete in the basement of a steel mill

511
00:29:31.979 --> 00:29:37.849
<v Tom Jacques>and collect it as well as the data from
another, you know, 50, 50 motors, all using

512
00:29:37.849 --> 00:29:38.630
<v Tom Jacques>one gateway.

513
00:29:39.800 --> 00:29:44.359
<v Tom Jacques>That's incredible, and to do that without
wires, very quickly set things up and

514
00:29:44.359 --> 00:29:45.339
<v Tom Jacques>parameterize everything.

515
00:29:46.219 --> 00:29:48.250
<v Tom Jacques>That's where I think in the near term
we're gonna be at.

516
00:29:49.369 --> 00:29:50.560
<v Speaker 2>Fantastic, fantastic.

517
00:29:50.699 --> 00:29:55.410
<v Speaker 2>So I guess to sort of close things off a
little bit, there's just one question, and

518
00:29:55.410 --> 00:30:00.819
<v Speaker 2>it's really for someone who is maybe
thinking of following a similar career path to

519
00:30:00.819 --> 00:30:04.859
<v Speaker 2>you, Tom, so maybe working on the shop
floor and wants to make that transition to

520
00:30:05.180 --> 00:30:08.739
<v Speaker 2>whether it's solution engineering or more,
you know, working on the software side.

521
00:30:09.140 --> 00:30:12.760
<v Speaker 2>Um, do you have any advice or any sort of
tips and things for them to think about?

522
00:30:12.869 --> 00:30:16.880
<v Tom Jacques>I do have advice, yeah, I think that's,
that's a lovely question, um.

523
00:30:17.910 --> 00:30:19.750
<v Tom Jacques>My advice would try and be to.

524
00:30:20.380 --> 00:30:24.859
<v Tom Jacques>You know, we've got a lot of specialists
who are very good in a certain domain or

525
00:30:24.859 --> 00:30:28.660
<v Tom Jacques>very good at a specific thing, those
people are always gonna be very needed, but in

526
00:30:28.660 --> 00:30:31.199
<v Tom Jacques>the role that I've got, I've effectively
become.

527
00:30:32.410 --> 00:30:36.150
<v Tom Jacques>I'll say an expert, but I don't like using
that term, an expert generalist.

528
00:30:36.849 --> 00:30:41.170
<v Tom Jacques>So I know lots about lots of different
things, and I'm not an expert at any one of

529
00:30:41.170 --> 00:30:41.290
<v Tom Jacques>them.

530
00:30:41.369 --> 00:30:44.920
<v Tom Jacques>I'm not the best, I'm not the best
programmer for sure, I'm not the best maintenance

531
00:30:44.920 --> 00:30:49.420
<v Tom Jacques>engineer, but what I can do is sit between
these different divisions and also sit in

532
00:30:49.420 --> 00:30:52.910
<v Tom Jacques>a room with customers, and I can
understand the perspective of the maintenance

533
00:30:52.910 --> 00:30:55.819
<v Tom Jacques>engineer, equally, I can understand the,
the production engineer.

534
00:30:56.420 --> 00:30:59.770
<v Tom Jacques>And I can also see the guy watching over
their shoulder, the guy, the guy kind of

535
00:30:59.780 --> 00:31:02.020
<v Tom Jacques>facilitating all this, he's he's gonna
have to pay for the solution at the end of

536
00:31:02.020 --> 00:31:06.449
<v Tom Jacques>the day is to understand what is he
looking to get out of this.

537
00:31:06.979 --> 00:31:11.619
<v Tom Jacques>So you have to be able to understand the
commercial side of things, understand, you

538
00:31:11.619 --> 00:31:14.300
<v Tom Jacques>know, how are we're gonna use technology
to link stuff together.

539
00:31:15.140 --> 00:31:18.739
<v Tom Jacques>If you're looking at a bearing or a motor
or a gearbox or a belt and sprocket

540
00:31:18.739 --> 00:31:20.560
<v Tom Jacques>system, how is that gonna fail?

541
00:31:21.339 --> 00:31:23.739
<v Tom Jacques>So first of all, if you don't know that,
you don't know what sensors you need, you

542
00:31:23.739 --> 00:31:27.219
<v Tom Jacques>don't know what connectivity you need, and
I think we need more people who

543
00:31:27.219 --> 00:31:28.680
<v Tom Jacques>understand the sort of broader spectrum.

544
00:31:28.859 --> 00:31:32.699
<v Tom Jacques>Um, the world is lacking maintenance
engineers, uh, I think we're seeing that more

545
00:31:32.699 --> 00:31:33.060
<v Tom Jacques>and more.

546
00:31:33.219 --> 00:31:35.579
<v Tom Jacques>We go to customers, uh, they outsource
that.

547
00:31:35.979 --> 00:31:38.119
<v Tom Jacques>That is gonna be, you know, more and more
the case.

548
00:31:39.010 --> 00:31:43.130
<v Tom Jacques>And so we need to make sure we've got
people who understand a broad spectrum of lots

549
00:31:43.130 --> 00:31:43.650
<v Tom Jacques>of things.

550
00:31:44.359 --> 00:31:47.839
<v Tom Jacques>And that's kind of where we've ended up
already in this industry, right, so you've,

551
00:31:47.920 --> 00:31:51.000
<v Tom Jacques>you've got a few maintenance engineers and
when they need someone to come and look

552
00:31:51.000 --> 00:31:54.150
<v Tom Jacques>at the compressor, they, you know, they
can speak to the compressor expert and he

553
00:31:54.150 --> 00:31:55.060
<v Tom Jacques>can come and solve it.

554
00:31:55.640 --> 00:32:00.520
<v Tom Jacques>um, but more often now you start to say,
well, what systems do we need to digitalize

555
00:32:00.520 --> 00:32:03.300
<v Tom Jacques>that and pull that data into, into a cloud
software.

556
00:32:04.319 --> 00:32:07.280
<v Tom Jacques>And I think Really, what advice would I
give?

557
00:32:08.579 --> 00:32:13.310
<v Tom Jacques>Always try and just learn something, so
every week I'm learning something different

558
00:32:13.310 --> 00:32:18.010
<v Tom Jacques>about a new sensor or a new, a new way of
integrating these different things, um,

559
00:32:18.109 --> 00:32:21.630
<v Tom Jacques>even sometimes a new part of Siemens that,
you know, there's a, there's a sensor

560
00:32:21.630 --> 00:32:26.030
<v Tom Jacques>that I've just discovered a few weeks ago,
um, the, the Mag 8000, this sort of

561
00:32:26.030 --> 00:32:28.599
<v Tom Jacques>clever little thing that sits on, on, on
pipes.

562
00:32:29.189 --> 00:32:33.280
<v Tom Jacques>We can use that, we can start to leverage
that as well, um, because it gives us an

563
00:32:33.280 --> 00:32:35.989
<v Tom Jacques>insight, it's got batteries, it's got, um.

564
00:32:36.229 --> 00:32:39.670
<v Tom Jacques>It fits well into the portfolio and
there's so many different parts of Siemens where

565
00:32:39.670 --> 00:32:40.780
<v Tom Jacques>you start to say, right.

566
00:32:42.380 --> 00:32:47.380
<v Tom Jacques>Have I upskilled myself in, in IOT, have I
upskilled myself in Edge and maybe how

567
00:32:47.380 --> 00:32:50.119
<v Tom Jacques>does an S7 protocol work and all this kind
of stuff.

568
00:32:50.739 --> 00:32:55.130
<v Tom Jacques>More, more often than not, you need to
know who to contact, I think it's very

569
00:32:55.130 --> 00:32:59.819
<v Tom Jacques>helpful, so try and make sure you've got,
um, you know, know who your experts are as

570
00:32:59.819 --> 00:33:00.239
<v Tom Jacques>well.

571
00:33:00.739 --> 00:33:04.219
<v Tom Jacques>So there's things that I will just go to
certain people for and say right, we're,

572
00:33:04.300 --> 00:33:05.449
<v Tom Jacques>we're looking at this today.

573
00:33:05.959 --> 00:33:07.550
<v Tom Jacques>What do we need to do, you know, how do we
fix it?

574
00:33:07.599 --> 00:33:09.739
<v Tom Jacques>We've got, uh, Axel in our, in our team.

575
00:33:10.199 --> 00:33:12.520
<v Tom Jacques>He's an expert at vibration and analytics.

576
00:33:12.640 --> 00:33:17.650
<v Tom Jacques>He's come from the CMS 1200, um, SM 1281
team from years and years and years of

577
00:33:17.650 --> 00:33:17.920
<v Tom Jacques>experience.

578
00:33:18.000 --> 00:33:22.430
<v Tom Jacques>So if ever we need support on, you know,
how do we monitor this, I've got my own

579
00:33:22.430 --> 00:33:26.560
<v Tom Jacques>knowledge, but I also, I'm not afraid to
admit that I need his support and it's

580
00:33:26.560 --> 00:33:29.920
<v Tom Jacques>great to have him, um, there to help us,
um.

581
00:33:31.010 --> 00:33:32.010
<v Tom Jacques>Yeah, that's my advice.

582
00:33:32.560 --> 00:33:36.280
<v Speaker 2>I think, and, and to your point, that
last, I really like that last bit about, you

583
00:33:36.280 --> 00:33:39.680
<v Speaker 2>know, you, you, you know, you can gather,
just keep learning, keep thinking.

584
00:33:39.760 --> 00:33:41.310
<v Speaker 2>I'm, I'm like a lifelong learner.

585
00:33:41.319 --> 00:33:44.599
<v Speaker 2>I'm always listening and learning and try
and pick things up, but I also know the

586
00:33:44.599 --> 00:33:48.079
<v Speaker 2>point where you can say, well, actually, I
know this much, but it'd be great to

587
00:33:48.079 --> 00:33:49.000
<v Speaker 2>bring this person in.

588
00:33:49.420 --> 00:33:51.310
<v Speaker 2>As well, that's really nice, nice way to
put it, I

589
00:33:51.310 --> 00:33:51.530
<v Tom Jacques>think.

590
00:33:51.709 --> 00:33:53.329
<v Tom Jacques>I think you do it as well already in the
marketing team.

591
00:33:53.709 --> 00:33:57.589
<v Tom Jacques>I think it's, I think it's fantastic to
see how, how things like this have evolved

592
00:33:57.869 --> 00:34:01.459
<v Tom Jacques>and how we, how we've gone from, you know,
podcasts online, now we do things in

593
00:34:01.459 --> 00:34:02.349
<v Tom Jacques>video format.

594
00:34:02.630 --> 00:34:06.589
<v Tom Jacques>It's really helpful to sort of share the
knowledge, and it's nice to get the

595
00:34:06.589 --> 00:34:09.790
<v Tom Jacques>platform to, to sit with you and talk
about it and, and talk about how we can help

596
00:34:09.790 --> 00:34:10.870
<v Tom Jacques>and, and drive this forward.

597
00:34:11.030 --> 00:34:12.590
<v Speaker 2>Fantastic, and that's what it's all about.

598
00:34:12.750 --> 00:34:16.149
<v Speaker 2>And what a lovely way to end on a lovely
positive note, but, um, no, thank you so

599
00:34:16.149 --> 00:34:21.310
<v Speaker 2>much, Tom, for talking through your, Your
career and your experience, um, and

600
00:34:21.310 --> 00:34:22.510
<v Speaker 2>hopefully you'll be back on again soon.

601
00:34:22.550 --> 00:34:26.469
<v Speaker 2>This won't be the last time, always,
always it'll be on very soon, um, but I thank

602
00:34:26.469 --> 00:34:31.629
<v Speaker 2>you and thank you everyone for listening
and watching and we'll see you on the next

603
00:34:31.629 --> 00:34:31.929
<v Speaker 2>episode.

604
00:34:34.000 --> 00:34:38.959
<v Speaker 1>Please like and subscribe on all major
podcast channels and find out more about

605
00:34:38.959 --> 00:34:42.340
<v Speaker 1>Sensei predictive maintenance at
Siemens.com.
