WEBVTT
Language: en-US

1
00:00:01.450 --> 00:00:06.130
<v Tom Jacques>I'll tell you, if you're overwhelmed by
where to begin with digital transformation,

2
00:00:06.570 --> 00:00:09.720
<v Tom Jacques>start where failure costs the most, and
that's your machines.

3
00:00:09.850 --> 00:00:13.220
<v Tom Jacques>and predictive maintenance is the lowest
hanging fruit with the highest return of

4
00:00:13.220 --> 00:00:13.789
<v Tom Jacques>investment.

5
00:00:14.949 --> 00:00:20.129
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens, and now your host Nel

6
00:00:20.129 --> 00:00:20.649
<v Speaker 2>Sullivan.

7
00:00:23.319 --> 00:00:27.549
<v Niall Sullivan>Hello everyone and welcome to the latest
episode of the Trends section podcast.

8
00:00:28.129 --> 00:00:33.290
<v Niall Sullivan>Um, today I'm joined once again by my, um,
colleague, esteemed colleague Tom.

9
00:00:33.450 --> 00:00:35.709
<v Niall Sullivan>Welcome back to the podcast, thanks for
coming back.

10
00:00:36.270 --> 00:00:37.549
<v Tom Jacques>Hi, thanks for having me.

11
00:00:38.229 --> 00:00:42.310
<v Niall Sullivan>Um, um, I know we'd usually do, um,
introductions and things like that, but I think

12
00:00:42.310 --> 00:00:45.720
<v Niall Sullivan>we could dive straight into the topic
today because people know you by now, Tom.

13
00:00:45.840 --> 00:00:47.020
<v Niall Sullivan>I mean, you're our.

14
00:00:47.360 --> 00:00:48.150
<v Tom Jacques>I'm happy to do that

15
00:00:48.150 --> 00:00:51.709
<v Niall Sullivan>you're engineer for Sentai within Siemens,
right, unless you wanna add to that in

16
00:00:51.709 --> 00:00:52.259
<v Niall Sullivan>any way.

17
00:00:53.159 --> 00:00:57.159
<v Tom Jacques>Mainly, mainly I'm solutions engineering,
so anything where you think there might be

18
00:00:57.159 --> 00:01:00.939
<v Tom Jacques>a requirement, um, reach out to me, reach
out to the rest of the team.

19
00:01:01.080 --> 00:01:02.360
<v Tom Jacques>Um, I'm always here.

20
00:01:02.400 --> 00:01:05.019
<v Tom Jacques>If there's any questions or anything,
always feel free.

21
00:01:05.760 --> 00:01:06.269
<v Niall Sullivan>That's awesome.

22
00:01:06.349 --> 00:01:09.680
<v Niall Sullivan>Hopefully I didn't undersell you there
either, cos, you know, your role is very,

23
00:01:09.800 --> 00:01:12.839
<v Niall Sullivan>very broad and a lot involved, and that's
why we invite you on the podcast,

24
00:01:12.949 --> 00:01:17.279
<v Niall Sullivan>obviously share those, um, thoughts and,
and especially the conversations you have

25
00:01:17.279 --> 00:01:18.830
<v Niall Sullivan>with customers and potential customers.

26
00:01:20.160 --> 00:01:24.000
<v Niall Sullivan>But I mean, so today's topic, um, we're
talking about predictive maintenance and how

27
00:01:24.000 --> 00:01:26.319
<v Niall Sullivan>it can enable digital transformation.

28
00:01:26.739 --> 00:01:30.330
<v Niall Sullivan>Um, and as we know, digital transformation
is such a broad topic.

29
00:01:30.459 --> 00:01:34.220
<v Niall Sullivan>Um, and to us, predicting maintenance is a
core focus, but in, in a lot of ways,

30
00:01:34.230 --> 00:01:38.220
<v Niall Sullivan>it's a tiny dot on the map of a bigger
project, or maybe it isn't.

31
00:01:38.389 --> 00:01:39.709
<v Niall Sullivan>I mean, that's what we're talking about
today, right?

32
00:01:39.790 --> 00:01:43.930
<v Niall Sullivan>So, Let's, I mean, let's get, let's get
started and straight into it.

33
00:01:43.970 --> 00:01:48.709
<v Niall Sullivan>I guess if we start with the big picture
first and sort of expand a little bit.

34
00:01:49.209 --> 00:01:53.559
<v Niall Sullivan>So, Tom, how would you define digital
transformation in the context of industrial

35
00:01:53.559 --> 00:01:56.150
<v Niall Sullivan>operations, first of all, just to lay the,
the groundwork for this.

36
00:01:57.540 --> 00:01:58.800
<v Tom Jacques>Uh, that's a good question.

37
00:01:58.940 --> 00:02:04.059
<v Tom Jacques>So I'll start by saying it really comes
down to changing, so digital transformation

38
00:02:04.059 --> 00:02:08.369
<v Tom Jacques>means shifting from find and fix to
predict and prevent effectively.

39
00:02:08.820 --> 00:02:12.520
<v Tom Jacques>So it's about connecting assets, unlocking
data, making sure that you can do

40
00:02:12.520 --> 00:02:17.220
<v Tom Jacques>something with that, with a main objective
to do things like reducing downtime, you

41
00:02:17.220 --> 00:02:20.660
<v Tom Jacques>know, improve efficiency, make sure that
the factories is a little bit more

42
00:02:20.660 --> 00:02:24.300
<v Tom Jacques>resilient to things, so you're not just
reacting to problems as they arise, you can

43
00:02:24.300 --> 00:02:27.000
<v Tom Jacques>foresee some of that stuff coming before
it comes.

44
00:02:27.440 --> 00:02:31.490
<v Tom Jacques>And crucially as well, making sure you
don't do too much, so a big element of this

45
00:02:31.710 --> 00:02:35.919
<v Tom Jacques>is definitely, you know, how can we
prevent lots of over maintenance.

46
00:02:36.190 --> 00:02:39.289
<v Tom Jacques>Um, that's the fundamental aspect of
predictive maintenance.

47
00:02:39.779 --> 00:02:43.630
<v Tom Jacques>Digital transformation goes then much more
broad and it becomes, you know, what can

48
00:02:43.630 --> 00:02:48.229
<v Tom Jacques>we have a digital twin version of, um, how
can we start to drive this across other

49
00:02:48.229 --> 00:02:49.250
<v Tom Jacques>areas of the business?

50
00:02:49.610 --> 00:02:53.460
<v Tom Jacques>And it, it really starts to become now
making sure that these different softwares

51
00:02:53.460 --> 00:02:55.619
<v Tom Jacques>and different solutions integrate with
each other.

52
00:02:55.820 --> 00:02:59.059
<v Tom Jacques>That, that's a big headache for companies
at the moment where, where these different

53
00:02:59.059 --> 00:03:01.860
<v Tom Jacques>tools don't link, um, as well as they
could.

54
00:03:03.789 --> 00:03:07.270
<v Niall Sullivan>And do you think sometimes, because I
guess when anyone hears the term digital

55
00:03:07.270 --> 00:03:09.830
<v Niall Sullivan>transformation, it can almost be a bit
overwhelming because like I said, there's so

56
00:03:09.830 --> 00:03:12.649
<v Niall Sullivan>many different tools, strategies, places
to get started.

57
00:03:13.270 --> 00:03:16.509
<v Niall Sullivan>I mean, do you, do you find that from
customers that sometimes it's a bit like

58
00:03:16.509 --> 00:03:18.130
<v Niall Sullivan>overwhelming to start with?

59
00:03:19.029 --> 00:03:23.389
<v Tom Jacques>Um, I think it can be, I think it can seem
overwhelming, but really when you start

60
00:03:23.389 --> 00:03:26.979
<v Tom Jacques>with predictive maintenance, you start by
not just, you know, you're not just fixing

61
00:03:26.979 --> 00:03:29.470
<v Tom Jacques>the machines, you're building trust across
different departments.

62
00:03:30.029 --> 00:03:34.429
<v Tom Jacques>So it can seem daunting, but it becomes
then, you know, how do the finance team and

63
00:03:34.429 --> 00:03:37.630
<v Tom Jacques>the operations team and the maintenance
team have this common goal?

64
00:03:37.669 --> 00:03:40.589
<v Tom Jacques>What's the, what's the common impact that
you're trying to, trying to look at?

65
00:03:41.139 --> 00:03:43.419
<v Tom Jacques>And that, that impact comes from
everything.

66
00:03:43.500 --> 00:03:47.740
<v Tom Jacques>I talk about predictive maintenance
because it's my specialty, but it's the same for

67
00:03:47.740 --> 00:03:49.619
<v Tom Jacques>all different areas of a, of a process.

68
00:03:51.979 --> 00:03:55.820
<v Niall Sullivan>And, yeah, I guess if we, if we focus on
the mains, well, that's what, you know,

69
00:03:55.940 --> 00:04:00.169
<v Niall Sullivan>focusing on the maintenance side, and I
guess, I mean, different organizations,

70
00:04:00.179 --> 00:04:05.419
<v Niall Sullivan>we're in different, um, stages of their
journey, but if we think about, um, the

71
00:04:05.419 --> 00:04:09.500
<v Niall Sullivan>challenges organizations face, even just
digitalizing their maintenance strategy,

72
00:04:09.580 --> 00:04:11.210
<v Niall Sullivan>maybe we could talk about that first of
all.

73
00:04:11.300 --> 00:04:12.960
<v Niall Sullivan>What are the, what are those challenges?

74
00:04:13.940 --> 00:04:18.019
<v Tom Jacques>One of the main ones is trying to unlock
the data that's there, so many, many

75
00:04:18.019 --> 00:04:22.579
<v Tom Jacques>machines sit within most of these
facilities or mines, quarries, steel processing

76
00:04:22.579 --> 00:04:26.579
<v Tom Jacques>plants, whatever it could be, and what you
end up with are lots of machines that

77
00:04:26.579 --> 00:04:30.980
<v Tom Jacques>work effectively siloed and maybe there's
tags and little pieces of information that

78
00:04:30.980 --> 00:04:34.600
<v Tom Jacques>say, yep, my part of the process is, is
complete, move on to the next step.

79
00:04:35.299 --> 00:04:36.790
<v Tom Jacques>But there's lots more information within
that.

80
00:04:37.429 --> 00:04:40.589
<v Tom Jacques>There's things like harmonic frequencies,
there's pressures, there's flows, and all

81
00:04:40.589 --> 00:04:42.630
<v Tom Jacques>of this stuff changes over time.

82
00:04:42.829 --> 00:04:44.779
<v Tom Jacques>Also, the process changes over time.

83
00:04:44.910 --> 00:04:48.809
<v Tom Jacques>Maybe you start to manufacture a different
product on the same pieces of equipment

84
00:04:48.899 --> 00:04:52.809
<v Tom Jacques>and, and some of that machine will be
brand new and some of it will be legacy.

85
00:04:53.269 --> 00:04:56.790
<v Tom Jacques>And again, you have to figure out the best
methods of making it all really work

86
00:04:56.790 --> 00:04:58.390
<v Tom Jacques>together, um, harmoniously.

87
00:04:58.950 --> 00:05:03.910
<v Tom Jacques>And that's, that's the difficult part of
all of this and also having of course

88
00:05:03.910 --> 00:05:07.510
<v Tom Jacques>different PLCs from different vendors,
making sure all of these things can

89
00:05:07.510 --> 00:05:11.750
<v Tom Jacques>communicate with each other so that you as
a business can do what you do best,

90
00:05:11.989 --> 00:05:14.570
<v Tom Jacques>making chocolate, making steel, whatever
it might be.

91
00:05:15.070 --> 00:05:19.109
<v Tom Jacques>And that for me is really one of the
biggest challenges, making sure that all of

92
00:05:19.109 --> 00:05:22.670
<v Tom Jacques>these different solutions work together,
um, and that is daunting.

93
00:05:22.750 --> 00:05:24.290
<v Tom Jacques>I think that is a, is a daunting thing.

94
00:05:25.540 --> 00:05:29.570
<v Niall Sullivan>Yeah, I, I guess that's particularly, um,
the case, you know, when you talk about,

95
00:05:29.679 --> 00:05:33.880
<v Niall Sullivan>um, I mean, a word we use often, you know,
about scale and across the enterprise, as

96
00:05:33.880 --> 00:05:37.470
<v Niall Sullivan>soon as you get, you know, to a deploy
digital transformation, I guess, across

97
00:05:38.049 --> 00:05:40.170
<v Niall Sullivan>multiple sites, that's where the
complexities start.

98
00:05:40.329 --> 00:05:43.170
<v Niall Sullivan>Like you said, with different systems,
different approaches, different culture,

99
00:05:43.190 --> 00:05:44.269
<v Niall Sullivan>maybe as well.

100
00:05:44.570 --> 00:05:48.029
<v Tom Jacques>That can be part of it, yeah, so if you've
always been in a, in a reactive mode,

101
00:05:48.440 --> 00:05:52.720
<v Tom Jacques>changing, I, again, I will link straight
back to predictive maintenance, it becomes

102
00:05:52.720 --> 00:05:54.910
<v Tom Jacques>a cultural shift to change your approach.

103
00:05:57.649 --> 00:06:02.119
<v Niall Sullivan>And I guess, um, yeah, so let's, I guess,
illustrate some of, some of these points,

104
00:06:02.130 --> 00:06:07.269
<v Niall Sullivan>um, we've discussed so far in terms of
sort of real life, you know, or real world,

105
00:06:07.450 --> 00:06:11.609
<v Niall Sullivan>um, examples where predictive maintenance
has enabled this broader digital

106
00:06:11.609 --> 00:06:12.350
<v Niall Sullivan>transformation.

107
00:06:12.480 --> 00:06:14.369
<v Niall Sullivan>Is there anything you can share, Tom, on
that side?

108
00:06:15.570 --> 00:06:20.359
<v Tom Jacques>There is, the, the, the main one I would
go to to start with would be a global

109
00:06:20.359 --> 00:06:24.320
<v Tom Jacques>automotive plant that Sens and I worked
with, um, looked at digitalizing the

110
00:06:24.320 --> 00:06:29.109
<v Tom Jacques>workflow but kept facing, um, you know,
they kept facing costly unplanned downtime,

111
00:06:29.649 --> 00:06:31.339
<v Tom Jacques>um, on a single stamping press.

112
00:06:31.489 --> 00:06:35.170
<v Tom Jacques>And just by implementing predictive
maintenance on that one asset, they saved over

113
00:06:35.170 --> 00:06:41.010
<v Tom Jacques>£200,000 and effectively that was good
return on investment came very quickly.

114
00:06:41.130 --> 00:06:43.059
<v Tom Jacques>So that's a good example of where we've
done this.

115
00:06:43.640 --> 00:06:47.410
<v Tom Jacques>And a global food and beverage customer,
just thinking of a second, um.

116
00:06:48.149 --> 00:06:51.529
<v Tom Jacques>With large plants around the world, they
weren't really sure where to begin.

117
00:06:51.950 --> 00:06:56.350
<v Tom Jacques>um, when we talk about digital
transformation uh with an example where predictive

118
00:06:56.350 --> 00:07:02.549
<v Tom Jacques>maintenance it really benefits you, I'll
tell you, if you're overwhelmed by where to

119
00:07:02.549 --> 00:07:06.950
<v Tom Jacques>begin with digital transformation, start
where failure costs the most, and that's

120
00:07:06.950 --> 00:07:07.630
<v Tom Jacques>your machines.

121
00:07:07.829 --> 00:07:11.179
<v Tom Jacques>And predictive maintenance is the lowest
hanging fruit with the highest return of

122
00:07:11.179 --> 00:07:11.670
<v Tom Jacques>investment.

123
00:07:12.390 --> 00:07:18.109
<v Tom Jacques>And since I worked to centralize existing
sensor data and mapped that data across um

124
00:07:18.109 --> 00:07:22.869
<v Tom Jacques>into a digital twin of the factory to
begin with, locations of where the motors are,

125
00:07:22.910 --> 00:07:25.649
<v Tom Jacques>the pumps, the conveyors, ventilation
systems and so on.

126
00:07:26.329 --> 00:07:31.269
<v Tom Jacques>Um, and effectively what we did then was
we gave them visibility as soon as we could

127
00:07:31.269 --> 00:07:35.130
<v Tom Jacques>and gave them a digital fingerprint of all
of those assets and understood very

128
00:07:35.130 --> 00:07:39.130
<v Tom Jacques>quickly what, what was healthy behavior
and what was unhealthy behavior based on

129
00:07:39.130 --> 00:07:41.070
<v Tom Jacques>those metrics that we started to create.

130
00:07:41.170 --> 00:07:46.119
<v Tom Jacques>So, you know, 2 to 5 days normal operation
since I build you a fingerprint of

131
00:07:46.130 --> 00:07:48.109
<v Tom Jacques>normal, of normal healthy operation.

132
00:07:48.809 --> 00:07:52.130
<v Tom Jacques>And equally it could be in a, in a failed
state already, so.

133
00:07:52.869 --> 00:07:56.250
<v Tom Jacques>That's a question we get asked often, so
I'm caveating myself while I say it.

134
00:07:56.589 --> 00:08:00.829
<v Tom Jacques>Um, a machine could be on boarded in a
failed state, and again, every case closure

135
00:08:00.829 --> 00:08:04.029
<v Tom Jacques>gives you the chance to fill that back in
and say, yeah, the machine was already

136
00:08:04.029 --> 00:08:07.290
<v Tom Jacques>failed, uh, you know, the bearings were
80% collapsed.

137
00:08:07.820 --> 00:08:11.579
<v Tom Jacques>Pretty much that last little grinder and
that increased torque, we replaced it,

138
00:08:11.779 --> 00:08:13.269
<v Tom Jacques>that's why you've seen different results.

139
00:08:13.700 --> 00:08:16.820
<v Tom Jacques>But effectively this has helped them to
streamline what they do.

140
00:08:16.980 --> 00:08:21.579
<v Tom Jacques>Uh, maintenance is now much more optimized
and, and really it focuses on how much

141
00:08:21.579 --> 00:08:22.429
<v Tom Jacques>maintenance they do.

142
00:08:22.619 --> 00:08:26.140
<v Tom Jacques>So that's something that we've really
helped them with, uh, and that's just, you

143
00:08:26.140 --> 00:08:29.480
<v Tom Jacques>know, two of good, two of many examples
that I could give to you.

144
00:08:30.549 --> 00:08:36.039
<v Niall Sullivan>Yeah, and I say 22 examples that, um, are
very different, different verticals,

145
00:08:36.109 --> 00:08:37.200
<v Niall Sullivan>right, with different approaches.

146
00:08:37.400 --> 00:08:40.640
<v Niall Sullivan>I mean, is there, when we talk about sort
of digital transformation or predict

147
00:08:40.640 --> 00:08:44.640
<v Niall Sullivan>maintenance as an enabler for that, you
know, what sort of the differences, I mean,

148
00:08:44.799 --> 00:08:47.789
<v Niall Sullivan>compared, you know, automotive versus food
and beverage, if you want to put the two

149
00:08:47.789 --> 00:08:48.450
<v Niall Sullivan>up against each other.

150
00:08:48.510 --> 00:08:54.539
<v Niall Sullivan>Is there, Differences, differences in
approaches or, or mindset or

151
00:08:55.080 --> 00:09:00.049
<v Tom Jacques>there is, there is, so if you've got a, a
process that runs start to finish nonstop,

152
00:09:00.239 --> 00:09:03.640
<v Tom Jacques>so if, if you think of something like
paper manufacturing, that's something that you

153
00:09:03.640 --> 00:09:07.549
<v Tom Jacques>can't really stop it, it needs to
continuously run, which means when you get the

154
00:09:07.549 --> 00:09:12.400
<v Tom Jacques>chance to, to stop the machines, typically
you'll you'll really strip things down,

155
00:09:12.530 --> 00:09:16.119
<v Tom Jacques>you'll change bearings that aren't
perhaps, you know, completely collapsed, but you

156
00:09:16.119 --> 00:09:18.960
<v Tom Jacques>wanna make sure they make it through the
next window of operation.

157
00:09:19.419 --> 00:09:20.679
<v Tom Jacques>And that could be months long.

158
00:09:21.719 --> 00:09:25.580
<v Tom Jacques>Equally, if you've got a process where it
stops and starts, that's where you might

159
00:09:25.580 --> 00:09:30.940
<v Tom Jacques>not need to do so much over maintenance,
but reacting to stoppages, all these small

160
00:09:30.940 --> 00:09:35.599
<v Tom Jacques>little downtime events, conveyors that
stop, bearings that um collapse and all the

161
00:09:35.599 --> 00:09:40.820
<v Tom Jacques>rest of it, they will start to impact you,
you know, collectively over time.

162
00:09:40.989 --> 00:09:43.260
<v Tom Jacques>So in food and beverage, that's a good
example.

163
00:09:43.960 --> 00:09:47.640
<v Tom Jacques>Um, in steel, that's a good example, you,
you wanna make sure that downtime is

164
00:09:47.640 --> 00:09:51.979
<v Tom Jacques>avoided, and I've, I'm picking a few key
ones that everybody knows, but there are,

165
00:09:52.000 --> 00:09:56.070
<v Tom Jacques>of course, hundreds, thousands of
different processes, um, and things being

166
00:09:56.070 --> 00:09:58.659
<v Tom Jacques>manufactured, you know, tens of thousands
of different things.

167
00:09:59.729 --> 00:10:04.530
<v Tom Jacques>What I would say is when we start to look
at this, it comes down to what's the

168
00:10:04.530 --> 00:10:09.010
<v Tom Jacques>operation and, and what's the value of the
product that's being manufactured or

169
00:10:09.010 --> 00:10:09.489
<v Tom Jacques>processed.

170
00:10:10.150 --> 00:10:14.119
<v Tom Jacques>And that is really what, what starts to
impact, um, you know, how much can we spend

171
00:10:14.119 --> 00:10:17.270
<v Tom Jacques>on the project as an initial outlay,
what's the return of investment.

172
00:10:17.559 --> 00:10:21.159
<v Tom Jacques>That will change depending on, um, you
know, the business impact that we have.

173
00:10:21.320 --> 00:10:25.000
<v Tom Jacques>So the, if something's more valuable, if
you start making medicine or you're, you're

174
00:10:25.000 --> 00:10:30.080
<v Tom Jacques>making, um, vaccines or vials of things or
even tablets, this stuff is very

175
00:10:30.080 --> 00:10:30.570
<v Tom Jacques>valuable.

176
00:10:30.690 --> 00:10:34.739
<v Tom Jacques>So an hour of downtime here is enormous
compared to.

177
00:10:35.119 --> 00:10:39.929
<v Tom Jacques>You know, making uh potato chips or
something smaller uh and, and less, so we have

178
00:10:39.929 --> 00:10:44.450
<v Tom Jacques>to factor that in and we, we do factor
that in when we do projects, um, to make sure

179
00:10:44.450 --> 00:10:46.070
<v Tom Jacques>it aligns to the, to the industry.

180
00:10:48.309 --> 00:10:52.419
<v Niall Sullivan>No, yeah, it's really interesting, and the
thing is, it's an important point to, um,

181
00:10:52.710 --> 00:10:56.309
<v Niall Sullivan>to look at these nuances, because I guess
when you're, when you're talking to these

182
00:10:56.309 --> 00:10:57.450
<v Niall Sullivan>different customers and different.

183
00:10:58.159 --> 00:11:02.150
<v Niall Sullivan>Verticals, it becomes clear which use
cases are maybe more appropriate to one over

184
00:11:02.150 --> 00:11:03.099
<v Niall Sullivan>the other, right?

185
00:11:04.239 --> 00:11:08.520
<v Tom Jacques>Yeah, exactly, and it's also
understanding, you know, you might get a very forward

186
00:11:08.520 --> 00:11:12.880
<v Tom Jacques>thinking company, um, the sector is then
irrelevant, it's a company that are trying

187
00:11:12.880 --> 00:11:16.960
<v Tom Jacques>to move forward, uh, and maybe take the
risk of, of deploying something that they're

188
00:11:16.960 --> 00:11:21.760
<v Tom Jacques>not sure of, um, and also we get customers
who are a little bit risk averse and.

189
00:11:22.229 --> 00:11:26.469
<v Tom Jacques>They need a little bit more uh of an
understanding first before they effectively

190
00:11:26.469 --> 00:11:30.150
<v Tom Jacques>dive in at the deep end, you know, this is
tried and tested, we can, we can show

191
00:11:30.150 --> 00:11:35.590
<v Tom Jacques>that, but it's, it sometimes it really
requires that um handholding and we've got an

192
00:11:35.590 --> 00:11:36.950
<v Tom Jacques>approach for, for everybody.

193
00:11:38.590 --> 00:11:42.239
<v Niall Sullivan>And I, I guess another, well, I mean, key
to maybe predictive maintenance as well,

194
00:11:42.320 --> 00:11:46.549
<v Niall Sullivan>but certainly to digital transformation, a
great deal of collaboration, you know,

195
00:11:46.679 --> 00:11:49.940
<v Niall Sullivan>involved across many different, um,
departments.

196
00:11:50.200 --> 00:11:53.400
<v Niall Sullivan>But I guess if we focus on the predictive
maintenance aspect, how does sort of, how

197
00:11:53.400 --> 00:11:57.599
<v Niall Sullivan>does implementing predictive maintenance
sort of bring, bring the data, the systems

198
00:11:57.599 --> 00:12:00.989
<v Niall Sullivan>and the people together so they can sort
of collaborate together and achieve those

199
00:12:00.989 --> 00:12:03.099
<v Niall Sullivan>outcomes, some, some of which you've
mentioned already.

200
00:12:04.380 --> 00:12:08.789
<v Tom Jacques>Um, I would say when you start with
predictive maintenance, you're not just fixing

201
00:12:08.789 --> 00:12:12.210
<v Tom Jacques>the machines, you're, you're building that
trust across the different departments.

202
00:12:12.469 --> 00:12:16.869
<v Tom Jacques>So if it's robot reliability teams,
operations, finance, they will all see an

203
00:12:16.869 --> 00:12:17.409
<v Tom Jacques>impact.

204
00:12:17.869 --> 00:12:22.750
<v Tom Jacques>Um, and that alignment I think is quite
rare across a business to also have teams of

205
00:12:22.750 --> 00:12:26.309
<v Tom Jacques>people that start a project and they
really sit right down at the bottom of the

206
00:12:26.309 --> 00:12:30.270
<v Tom Jacques>business, um, you know, at the crux of
things, making sure the machines do what they

207
00:12:30.270 --> 00:12:32.000
<v Tom Jacques>should do, all the way through to the CEO.

208
00:12:32.650 --> 00:12:36.590
<v Tom Jacques>And predictive maintenance, sometimes
that's why it's complicated because all these

209
00:12:36.590 --> 00:12:40.950
<v Tom Jacques>teams suddenly realize they've never had
to work this closely together before.

210
00:12:41.530 --> 00:12:45.570
<v Tom Jacques>Um, but equally then you start to see the
results as a team, you start to achieve

211
00:12:45.570 --> 00:12:50.219
<v Tom Jacques>something, you start to have a direct
impact, um, you know, return on investment

212
00:12:50.219 --> 00:12:50.640
<v Tom Jacques>impact.

213
00:12:50.929 --> 00:12:55.330
<v Tom Jacques>It makes people's lives simpler if you've,
you know, you're not, not running around

214
00:12:55.330 --> 00:12:58.530
<v Tom Jacques>chasing after yourself so much, you can
preempt things, you can.

215
00:12:58.919 --> 00:13:02.679
<v Tom Jacques>Order spares and, and, and parts into
stock so they can be changed at the right

216
00:13:02.679 --> 00:13:03.179
<v Tom Jacques>time.

217
00:13:03.719 --> 00:13:08.359
<v Tom Jacques>That will have an impact on the process,
the product, so you can make more, you can,

218
00:13:08.440 --> 00:13:09.919
<v Tom Jacques>you can do more with less.

219
00:13:10.280 --> 00:13:13.799
<v Tom Jacques>And of course, right the way through the
business, that has, uh, knock-on effects,

220
00:13:13.880 --> 00:13:16.080
<v Tom Jacques>positive knock-on effects all the way to
the top.

221
00:13:17.919 --> 00:13:21.080
<v Niall Sullivan>And actually, I wanted to pick out
something you said sort of earlier in your, in

222
00:13:21.080 --> 00:13:21.719
<v Niall Sullivan>your answer.

223
00:13:21.799 --> 00:13:25.440
<v Niall Sullivan>You said about, you know, departments, you
know, coming together that potentially

224
00:13:25.440 --> 00:13:26.760
<v Niall Sullivan>haven't worked together before.

225
00:13:26.880 --> 00:13:31.239
<v Niall Sullivan>Is that something you, you see quite
often, that, um, oh well, A, that, you know,

226
00:13:31.320 --> 00:13:35.400
<v Niall Sullivan>that's the case, and B, that predictive
maintenance helps to bring these teams

227
00:13:35.400 --> 00:13:35.900
<v Niall Sullivan>together.

228
00:13:36.739 --> 00:13:38.500
<v Tom Jacques>Yes, that is exactly what we see.

229
00:13:38.580 --> 00:13:44.539
<v Tom Jacques>We see companies where it's a new thing,
digital transformation, um, in its nature

230
00:13:44.539 --> 00:13:45.880
<v Tom Jacques>is fairly new.

231
00:13:46.340 --> 00:13:51.299
<v Tom Jacques>Um, in some organizations, it's already
set up to, to work well, uh, maybe whatever

232
00:13:51.299 --> 00:13:54.039
<v Tom Jacques>it is they manufacture, there's lots of
links across the business.

233
00:13:54.419 --> 00:13:55.679
<v Tom Jacques>But what we also see.

234
00:13:56.169 --> 00:13:59.929
<v Tom Jacques>Are the ones where they, where they don't,
and, and predictive maintenance gets them

235
00:13:59.929 --> 00:14:00.859
<v Tom Jacques>all in the same room.

236
00:14:01.059 --> 00:14:04.289
<v Tom Jacques>It makes you start to look at things and
say, right, do we have the right equipment?

237
00:14:04.409 --> 00:14:07.390
<v Tom Jacques>Do we have the right process to deal with
something when it goes wrong?

238
00:14:07.739 --> 00:14:09.159
<v Tom Jacques>If it goes wrong, what do we do?

239
00:14:09.700 --> 00:14:13.859
<v Tom Jacques>In some cases, like we, like we're saying
now, if it's reactive, you, you can use

240
00:14:13.859 --> 00:14:16.419
<v Tom Jacques>predictive maintenance to flip that whole
process.

241
00:14:16.500 --> 00:14:20.380
<v Tom Jacques>So actually predictive maintenance is a
fantastic place to start in a digital

242
00:14:20.380 --> 00:14:21.419
<v Tom Jacques>transformation journey.

243
00:14:21.859 --> 00:14:25.450
<v Tom Jacques>Uh, because of how many different impacts
it has, and it pays for itself

244
00:14:25.789 --> 00:14:26.289
<v Tom Jacques>immediately.

245
00:14:26.500 --> 00:14:31.190
<v Tom Jacques>Um, immediately, could be, depending on
the process, a few months, um, a, a few

246
00:14:31.190 --> 00:14:31.650
<v Tom Jacques>years.

247
00:14:32.419 --> 00:14:38.030
<v Tom Jacques>But it It depends as well on how much
stuff you've already got in place, so if you

248
00:14:38.030 --> 00:14:43.510
<v Tom Jacques>don't have an existing, you know, network
system of, of DCS and SCADA where data can

249
00:14:43.510 --> 00:14:46.849
<v Tom Jacques>be collected into one central location,
saved in a historian.

250
00:14:47.539 --> 00:14:51.799
<v Tom Jacques>And then sent somewhere, you need to start
actually implementing that first.

251
00:14:51.900 --> 00:14:56.260
<v Tom Jacques>That's one of the things you need to put
in place before you go any further, so that

252
00:14:56.270 --> 00:15:01.340
<v Tom Jacques>that data can be made available, made
useful, um, and I guess what it helps you to

253
00:15:01.340 --> 00:15:05.539
<v Tom Jacques>do is understand what, what gaps have you
got in the organization, um, pretty

254
00:15:05.539 --> 00:15:05.880
<v Tom Jacques>quickly.

255
00:15:05.979 --> 00:15:09.099
<v Tom Jacques>I think that's what predictive maintenance
is good for, that's one of the reasons.

256
00:15:09.830 --> 00:15:13.890
<v Tom Jacques>I like starting projects with predictive
maintenance, um, with an industrial edge

257
00:15:13.890 --> 00:15:16.869
<v Tom Jacques>solution in place, with the Brownfield
Connect solution in place, and some other

258
00:15:16.869 --> 00:15:17.710
<v Tom Jacques>products from Siemens.

259
00:15:18.429 --> 00:15:20.270
<v Tom Jacques>Um, fit harmoniously into this.

260
00:15:22.010 --> 00:15:25.849
<v Niall Sullivan>So, I, I guess when there, there is, let's
say nothing in place or very little in

261
00:15:25.849 --> 00:15:30.270
<v Niall Sullivan>place, I guess it's about building out a
sort of a roadmap, you know, uh, and being,

262
00:15:30.409 --> 00:15:34.210
<v Niall Sullivan>I guess, realistic on timelines and what
can be achieved and, and when, but maybe

263
00:15:34.210 --> 00:15:37.690
<v Niall Sullivan>you could talk a little bit about that
process, Tom, for sort of mapping out, you

264
00:15:37.690 --> 00:15:42.049
<v Niall Sullivan>know, if we give an example of, um, an
organization with very little, um, data

265
00:15:42.049 --> 00:15:42.809
<v Niall Sullivan>collection, etc.

266
00:15:43.000 --> 00:15:43.909
<v Niall Sullivan>in place already.

267
00:15:44.760 --> 00:15:49.039
<v Tom Jacques>So the essential part is really um to have
an element of standardization to start

268
00:15:49.039 --> 00:15:51.640
<v Tom Jacques>with, just across the process, so your DCS
and SCADA network.

269
00:15:52.679 --> 00:15:56.840
<v Tom Jacques>And then as far as I'm concerned, that's
the main standard that we need to pull data

270
00:15:56.840 --> 00:15:58.580
<v Tom Jacques>uniformly into one place.

271
00:15:59.080 --> 00:16:02.830
<v Tom Jacques>And often I think that's the part of our
projects that we, we really look to deploy

272
00:16:02.830 --> 00:16:03.919
<v Tom Jacques>a simple Siemens solution.

273
00:16:04.000 --> 00:16:08.140
<v Tom Jacques>I just mentioned it, so something like
Edge, something like Insight Hub, other

274
00:16:08.400 --> 00:16:10.919
<v Tom Jacques>products from Siemens that are really,
really useful to do this.

275
00:16:11.469 --> 00:16:16.119
<v Tom Jacques>Um, and also from there, it starts to give
you the ability to monitor things like

276
00:16:16.119 --> 00:16:21.200
<v Tom Jacques>energy consumption, look at areas of
wastage, look at OEE, um, calculations, using

277
00:16:21.200 --> 00:16:22.719
<v Tom Jacques>effectively the same information.

278
00:16:22.960 --> 00:16:27.159
<v Tom Jacques>So digital transformation is, is doing the
most you can with what you've already

279
00:16:27.159 --> 00:16:27.580
<v Tom Jacques>got.

280
00:16:28.119 --> 00:16:31.919
<v Tom Jacques>Um, and if you've, if you've already got
some sensors, what data can we pull from?

281
00:16:32.080 --> 00:16:33.489
<v Tom Jacques>Do you already have historians?

282
00:16:33.960 --> 00:16:36.950
<v Tom Jacques>This is part of the scope project that we
start every project with.

283
00:16:37.159 --> 00:16:40.700
<v Tom Jacques>So we understand, first of all, what are
the limitations, what are the.

284
00:16:41.119 --> 00:16:45.609
<v Tom Jacques>Uh, constraints that we already work with
and as much as possible, build a solution

285
00:16:45.609 --> 00:16:52.530
<v Tom Jacques>that fits in, um, without huge Capital
expenditure of, um, you know, sensors and

286
00:16:52.530 --> 00:16:54.179
<v Tom Jacques>additional edge boxes and everything else.

287
00:16:54.289 --> 00:16:56.750
<v Tom Jacques>As much as possible, we'll use what's
already there.

288
00:16:57.090 --> 00:17:01.729
<v Tom Jacques>But equally, if you're looking to
transform, we can put a transformation layer in

289
00:17:01.729 --> 00:17:04.270
<v Tom Jacques>place, um, to benefit you for the future.

290
00:17:04.410 --> 00:17:06.430
<v Tom Jacques>That's also got cybersecurity involved.

291
00:17:06.910 --> 00:17:08.050
<v Tom Jacques>Uh, and all the rest of it.

292
00:17:08.219 --> 00:17:13.150
<v Tom Jacques>And this is then positioning you very well
for long-term digital growth, digital

293
00:17:13.150 --> 00:17:18.550
<v Tom Jacques>transformation, adding new things, adding
different, um, you know, different PLCs

294
00:17:18.550 --> 00:17:20.250
<v Tom Jacques>from different vendors, different sensors.

295
00:17:20.390 --> 00:17:24.739
<v Tom Jacques>You know, we, we use different sensors
where we need to, um, maybe for a better IP

296
00:17:24.739 --> 00:17:27.810
<v Tom Jacques>rating or for a, a higher heat tolerance
or something like that.

297
00:17:28.568 --> 00:17:33.769
<v Tom Jacques>And because Sensi is designed as a, uh, an
agnostic solution for any industry, any

298
00:17:33.769 --> 00:17:37.698
<v Tom Jacques>space, and also Brownfield Connect is
specifically designed for things like this.

299
00:17:37.938 --> 00:17:40.879
<v Tom Jacques>So for linking, uh, different types of
data together.

300
00:17:41.770 --> 00:17:46.329
<v Tom Jacques>We end up with a solution which is based
on a few foundational technologies but

301
00:17:46.329 --> 00:17:49.290
<v Tom Jacques>gives you an essential, um, you know.

302
00:17:50.689 --> 00:17:54.810
<v Tom Jacques>Process to build on for the future and
that's, that's, you know, we're, we're

303
00:17:54.810 --> 00:17:59.170
<v Tom Jacques>involved, um, in many different projects
and, and the Siemens Accelerator Project is

304
00:17:59.170 --> 00:18:00.469
<v Tom Jacques>designed kind of with this in mind.

305
00:18:00.560 --> 00:18:06.219
<v Tom Jacques>So the, the accelerator portfolio in its
entirety is how can we remove paper-based

306
00:18:06.219 --> 00:18:10.609
<v Tom Jacques>processes and do as much as we can with
the data that's there and then simulate

307
00:18:10.609 --> 00:18:12.310
<v Tom Jacques>things and digital twin things.

308
00:18:12.849 --> 00:18:17.229
<v Tom Jacques>Uh, this is the direction we will move in,
uh, lots of companies now look towards

309
00:18:17.229 --> 00:18:17.449
<v Tom Jacques>this.

310
00:18:17.489 --> 00:18:18.869
<v Tom Jacques>I think if, if you look at growth.

311
00:18:19.650 --> 00:18:24.859
<v Tom Jacques>Um, I realize this is a very long answer
to your question, but it's, it's, it's a

312
00:18:24.859 --> 00:18:30.280
<v Tom Jacques>really good question, and it, it does
include loads and loads of different elements.

313
00:18:30.579 --> 00:18:35.300
<v Tom Jacques>Um, in terms of what's essential to start
a project, a base layer, some sort of

314
00:18:35.300 --> 00:18:38.420
<v Tom Jacques>standardization across DCS and SCAA
networks.

315
00:18:38.810 --> 00:18:43.099
<v Tom Jacques>And then we look forward from there and we
make sure we build that in a scalable

316
00:18:43.099 --> 00:18:43.339
<v Tom Jacques>way.

317
00:18:43.459 --> 00:18:45.380
<v Tom Jacques>So things like virtual Edge from Siemens.

318
00:18:45.500 --> 00:18:50.729
<v Tom Jacques>Again, that's very scalable in the way
it's been designed, um, for this exact

319
00:18:50.729 --> 00:18:51.040
<v Tom Jacques>purpose.

320
00:18:52.680 --> 00:18:54.199
<v Niall Sullivan>No, long answers are good, Toms.

321
00:18:54.209 --> 00:18:57.670
<v Niall Sullivan>It means I'm talking less, which I think
is the most benefit to an audience.

322
00:18:57.680 --> 00:19:00.599
<v Niall Sullivan>If you're doing more of the talking than
me, that's, that's exactly what we want,

323
00:19:00.719 --> 00:19:00.890
<v Niall Sullivan>right?

324
00:19:00.949 --> 00:19:01.099
<v Niall Sullivan>Yeah, yeah.

325
00:19:03.219 --> 00:19:06.420
<v Niall Sullivan>But I, I was gonna mention, because it,
yeah, it's really interesting about these

326
00:19:06.420 --> 00:19:09.939
<v Niall Sullivan>projects, and I guess what they generate
more than anything as well is a lot of

327
00:19:09.939 --> 00:19:12.939
<v Niall Sullivan>excitement, or you'd hope so, you know,
everyone's really, you know, we want to

328
00:19:12.939 --> 00:19:14.290
<v Niall Sullivan>achieve this, we want to achieve that.

329
00:19:14.619 --> 00:19:18.619
<v Niall Sullivan>Is it, is it quite hard to sort of manage
expectations, both, you know, not, not

330
00:19:18.619 --> 00:19:22.290
<v Niall Sullivan>just in terms of, we're going to get this
return on investment in 3 months' time,

331
00:19:22.540 --> 00:19:24.260
<v Niall Sullivan>but also in terms of timelines for things.

332
00:19:24.329 --> 00:19:28.199
<v Niall Sullivan>Oh, we want it rolled out like now or in 2
months' time and.

333
00:19:28.650 --> 00:19:29.599
<v Niall Sullivan>You know, this kind of thing.

334
00:19:29.689 --> 00:19:33.160
<v Niall Sullivan>I mean, excitement's good, but is it also
quite tricky with, you know, because we

335
00:19:33.160 --> 00:19:37.250
<v Niall Sullivan>know sometimes extra data's required or
extra considerations, and that's what the

336
00:19:37.250 --> 00:19:41.689
<v Niall Sullivan>scope workshop's for, of course, but yeah,
is it hard, sorry, my question's really

337
00:19:41.689 --> 00:19:46.369
<v Niall Sullivan>long now, but is, is it hard to basically
is what I'm asking.

338
00:19:47.050 --> 00:19:51.849
<v Tom Jacques>Um, the hardest thing I think with all of
it is you're gonna perhaps get different

339
00:19:51.849 --> 00:19:53.270
<v Tom Jacques>solutions from different companies.

340
00:19:53.680 --> 00:19:57.739
<v Tom Jacques>And whose job is it then within all of
that to make sure it it can be integrated

341
00:19:58.119 --> 00:20:00.959
<v Tom Jacques>seamlessly, so making sure that you can.

342
00:20:01.709 --> 00:20:04.790
<v Tom Jacques>You can automate a process and standardize
and all the rest of it, but what you need

343
00:20:04.790 --> 00:20:07.790
<v Tom Jacques>to try and do is, it, it is that, it's to
standardize the process.

344
00:20:07.949 --> 00:20:12.270
<v Tom Jacques>So does this predictive maintenance
solution work with your CMMS solution, work with

345
00:20:12.270 --> 00:20:17.030
<v Tom Jacques>your EIP system, um, you need to make sure
if you're gonna digitalize, you don't end

346
00:20:17.030 --> 00:20:22.560
<v Tom Jacques>up with siloed solutions, um, in some
cases, maybe one of them's got a, a chat

347
00:20:22.560 --> 00:20:25.209
<v Tom Jacques>functionality, the other one's got a chat
functionality and you start to.

348
00:20:25.819 --> 00:20:29.810
<v Tom Jacques>Create a little bit of chaos and it's,
it's minimize that as much as you can as soon

349
00:20:29.810 --> 00:20:34.630
<v Tom Jacques>as you can, um, and I think when it comes
to answering your question, it, it's

350
00:20:35.050 --> 00:20:39.849
<v Tom Jacques>making sure there's a some team or at
least uh uh someone who's who's got a good

351
00:20:39.849 --> 00:20:44.260
<v Tom Jacques>understanding of what's happening and when
you absorb a new solution, make sure it's

352
00:20:44.260 --> 00:20:48.170
<v Tom Jacques>running on, you know, it's got an API
architecture that's gonna work cross

353
00:20:48.170 --> 00:20:50.449
<v Tom Jacques>functionally across different things, um.

354
00:20:50.949 --> 00:20:55.430
<v Tom Jacques>Make sure if you've got sensors, they they
communicate with standard methods so they

355
00:20:55.430 --> 00:21:00.329
<v Tom Jacques>can send data, um, on a standard protocol
that can be collected and sent to cloud

356
00:21:00.329 --> 00:21:06.949
<v Tom Jacques>via MQTT or whatever format it is in
standard ways that are, um, you know, allow

357
00:21:06.949 --> 00:21:08.430
<v Tom Jacques>that flexibility for the future.

358
00:21:09.910 --> 00:21:13.550
<v Niall Sullivan>And I, I guess, you know, in relation to
that, I know one of the questions on our

359
00:21:13.550 --> 00:21:17.140
<v Niall Sullivan>list was about IT and OT and sort of
bridging those two together.

360
00:21:17.410 --> 00:21:20.319
<v Niall Sullivan>Does that form part of what you were
saying then there as well?

361
00:21:20.780 --> 00:21:22.170
<v Niall Sullivan>Sort of if it helps with that.

362
00:21:22.550 --> 00:21:28.469
<v Tom Jacques>It does, yeah, and I think every business
wants to be data driven, um, but most are

363
00:21:28.469 --> 00:21:30.849
<v Tom Jacques>still flying blind to a certain degree.

364
00:21:31.310 --> 00:21:35.390
<v Tom Jacques>Um, and you need to find the best way of
linking your field level, you know, the

365
00:21:35.390 --> 00:21:38.489
<v Tom Jacques>operational technology up through the IT
technology.

366
00:21:39.130 --> 00:21:42.560
<v Tom Jacques>As far as I'm concerned, predictive
maintenance is the best way of doing that

367
00:21:42.569 --> 00:21:46.599
<v Tom Jacques>because you start having machines that
break down inherently based on mechanical

368
00:21:46.599 --> 00:21:49.209
<v Tom Jacques>systems, bearings, sprockets, chains,
motors.

369
00:21:49.609 --> 00:21:53.209
<v Tom Jacques>These things are all gonna break down, but
these are the fundamental backbone to how

370
00:21:53.209 --> 00:21:58.890
<v Tom Jacques>an organization makes things, you know,
crushes stone in a quarry, um, you know,

371
00:21:59.050 --> 00:22:01.810
<v Tom Jacques>pulls iron ore out of the ground or
whatever it is or if it's making chocolate

372
00:22:01.810 --> 00:22:05.229
<v Tom Jacques>again, right the way across the, the
different processes that we're looking at.

373
00:22:05.989 --> 00:22:10.810
<v Tom Jacques>It's then how do you get the data out, how
do you push that securely to cloud, um,

374
00:22:11.550 --> 00:22:14.589
<v Tom Jacques>making sure data is encrypted and all the
rest of it, making sure you've got

375
00:22:14.589 --> 00:22:19.410
<v Tom Jacques>controllers and uh and different devices
throughout your network that do certain

376
00:22:19.709 --> 00:22:21.369
<v Tom Jacques>jobs and there's standards for everything.

377
00:22:22.030 --> 00:22:23.160
<v Tom Jacques>um, Siemens.

378
00:22:23.839 --> 00:22:29.270
<v Tom Jacques>I think I'm happily would say are leading
the way in industry, um, biggest player

379
00:22:29.640 --> 00:22:33.520
<v Tom Jacques>globally in many, many different sectors
of this, and we're very good at

380
00:22:33.520 --> 00:22:36.640
<v Tom Jacques>understanding how the OT and IT can
connect together with diff different hardware

381
00:22:36.640 --> 00:22:37.900
<v Tom Jacques>and software solutions.

382
00:22:38.439 --> 00:22:42.199
<v Tom Jacques>So again, if you, if you were to come to
me and ask questions, I can answer certain

383
00:22:42.199 --> 00:22:44.540
<v Tom Jacques>elements of it and I've got colleagues
that can answer the rest.

384
00:22:45.290 --> 00:22:49.209
<v Tom Jacques>Um, equally across the whole of Siemens,
there's teams that could even consult on

385
00:22:49.209 --> 00:22:52.930
<v Tom Jacques>this, um, help you understand what you've
got, what you need, where are you're

386
00:22:52.930 --> 00:22:55.089
<v Tom Jacques>trying to, to, to head long term.

387
00:22:55.869 --> 00:23:01.439
<v Tom Jacques>Um, The difficult thing is Noel, when you
start to ask where does PDM fit in digital

388
00:23:01.439 --> 00:23:06.900
<v Tom Jacques>transformation, it is such a massive
topic, um and it covers so many things.

389
00:23:07.619 --> 00:23:11.640
<v Tom Jacques>That you have to understand um you know,
what are you, what's the end goal?

390
00:23:11.680 --> 00:23:15.619
<v Tom Jacques>I think first of all focus on what are you
trying to achieve and I would say almost

391
00:23:15.619 --> 00:23:19.859
<v Tom Jacques>always the goal is to do more with less,
to increase profit margins and all the rest

392
00:23:19.859 --> 00:23:23.260
<v Tom Jacques>of it, and that's why I think predictive
maintenance is one of the best places you

393
00:23:23.260 --> 00:23:23.900
<v Tom Jacques>can start.

394
00:23:25.150 --> 00:23:26.709
<v Niall Sullivan>No, absolutely, absolutely.

395
00:23:26.829 --> 00:23:29.829
<v Niall Sullivan>And I, and I think another really, you
know, another plus point, and let's say for

396
00:23:29.829 --> 00:23:33.469
<v Niall Sullivan>predictive maintenance as well is because
it can impact, you know, other business

397
00:23:33.469 --> 00:23:33.790
<v Niall Sullivan>functions.

398
00:23:33.829 --> 00:23:36.469
<v Niall Sullivan>And you talked, I think we talked about it
a little bit earlier on, but, you know,

399
00:23:36.540 --> 00:23:40.280
<v Niall Sullivan>there's examples like production planning
or quality assurance or supply chain

400
00:23:40.280 --> 00:23:40.729
<v Niall Sullivan>management.

401
00:23:41.349 --> 00:23:44.989
<v Niall Sullivan>Um, so maybe you could talk about that as
well, and then it's more of a, what I'd

402
00:23:44.989 --> 00:23:48.060
<v Niall Sullivan>call, not a side benefit, but uh, an
additional benefit, right?

403
00:23:48.079 --> 00:23:50.640
<v Niall Sullivan>It shouldn't, it's not the core focus, but
if it could impact.

404
00:23:51.079 --> 00:23:54.880
<v Niall Sullivan>Other parts of the business, then surely
that, that's, that's what digital

405
00:23:54.880 --> 00:23:56.510
<v Niall Sullivan>transformations are all about, right?

406
00:23:56.520 --> 00:23:59.949
<v Niall Sullivan>You don't want it just to be isolated on
one particular area of an organization

407
00:23:59.949 --> 00:24:01.020
<v Tom Jacques>that's exactly it.

408
00:24:01.199 --> 00:24:05.359
<v Tom Jacques>And if you just take a machine, for
example, that's got a trending failure, so

409
00:24:05.359 --> 00:24:08.479
<v Tom Jacques>something that starts to collapse long
term, maybe you don't see that until it

410
00:24:08.479 --> 00:24:12.689
<v Tom Jacques>breaks, but when you add something like
predictive maintenance, you can see how that

411
00:24:12.689 --> 00:24:16.760
<v Tom Jacques>maybe slows production, cos you can see
how it starts to break and then you can, you

412
00:24:16.760 --> 00:24:18.140
<v Tom Jacques>can do something.

413
00:24:18.510 --> 00:24:21.550
<v Tom Jacques>In a planned maintenance where you know
it's maybe the night shift and you're doing

414
00:24:21.550 --> 00:24:25.670
<v Tom Jacques>something at half speed or whatever it is,
but if you know when something's gonna

415
00:24:25.670 --> 00:24:29.819
<v Tom Jacques>break or you can anticipate things going
wrong, you can see across a fleet of

416
00:24:29.819 --> 00:24:32.010
<v Tom Jacques>different assets that one of them is an
outlier.

417
00:24:32.589 --> 00:24:36.939
<v Tom Jacques>That's where you can start to impact
production, which, and you don't need to be a

418
00:24:36.939 --> 00:24:40.430
<v Tom Jacques>rocket scientist, has a direct impact on
the bottom line of the business because you

419
00:24:40.430 --> 00:24:43.430
<v Tom Jacques>now know that there's a, a certain flag
within that.

420
00:24:44.170 --> 00:24:48.010
<v Tom Jacques>There's a recurring pattern or something's
going wrong, you can, you can improve the

421
00:24:48.010 --> 00:24:51.569
<v Tom Jacques>procurement process, you could, you could
get those spares into stock earlier

422
00:24:51.569 --> 00:24:53.719
<v Tom Jacques>because you know that that part is already
failing.

423
00:24:54.050 --> 00:24:58.329
<v Tom Jacques>You don't need to rely on uh long lead
times of that component or, or maybe you've

424
00:24:58.329 --> 00:25:02.969
<v Tom Jacques>seen in the past that that particular um
unique component has to be custom made or

425
00:25:02.969 --> 00:25:03.869
<v Tom Jacques>whatever it might be.

426
00:25:05.150 --> 00:25:11.209
<v Tom Jacques>This is uh it, it, it blew my mind when I
could first see what Sensei is capable of,

427
00:25:11.219 --> 00:25:15.540
<v Tom Jacques>learning baselines so quickly and, and
starting to trend things and see where

428
00:25:15.540 --> 00:25:19.119
<v Tom Jacques>something's going wrong, look at step
changes and anomalous spikes in the data.

429
00:25:20.689 --> 00:25:25.369
<v Tom Jacques>This all allows you to have smarter
decisions across the whole business and that is

430
00:25:25.369 --> 00:25:29.689
<v Tom Jacques>the fundamental part of this because it
allows you to do structured planning for the

431
00:25:29.689 --> 00:25:33.930
<v Tom Jacques>future um and that's one thing it's all
across industry that you need more of, it's

432
00:25:33.930 --> 00:25:39.709
<v Tom Jacques>more time to think and react, um, react
not to the machines going wrong but react to

433
00:25:40.089 --> 00:25:43.469
<v Tom Jacques>different alerts, different preemptive
information that's coming through to you.

434
00:25:43.930 --> 00:25:45.849
<v Tom Jacques>Uh it could even be that there's a traffic
jam.

435
00:25:46.329 --> 00:25:51.810
<v Tom Jacques>On XYZ motorway and that now causes you to
have, um, you know, a whole shipment of

436
00:25:51.810 --> 00:25:55.560
<v Tom Jacques>parts is, is delayed and you need those as
raw material to do something else.

437
00:25:55.900 --> 00:25:59.380
<v Tom Jacques>So if you could GPS track the trucks, for
example, which is what the likes of Amazon

438
00:25:59.380 --> 00:26:04.099
<v Tom Jacques>do, you can anticipate that there's
something changed and you can change your

439
00:26:04.099 --> 00:26:05.180
<v Tom Jacques>planning accordingly.

440
00:26:05.420 --> 00:26:09.890
<v Tom Jacques>Um, and that's, you know, that's a huge
benefit, um, to anybody who's trying to run

441
00:26:09.890 --> 00:26:10.500
<v Tom Jacques>a process.

442
00:26:11.250 --> 00:26:15.189
<v Niall Sullivan>So what you mentioned there, Tom, is some
really, um, really great examples.

443
00:26:15.250 --> 00:26:19.439
<v Niall Sullivan>I, I sort of, the way I imagine it is like
little treasure chests that as you're

444
00:26:19.439 --> 00:26:23.170
<v Niall Sullivan>sort of rolling out predictor maintenance
in an organization and maybe you start to

445
00:26:23.170 --> 00:26:26.369
<v Niall Sullivan>scale, it's like, oh, there's another
little benefit here, or another little benefit

446
00:26:26.369 --> 00:26:27.810
<v Niall Sullivan>here, maybe not so little, actually.

447
00:26:27.930 --> 00:26:29.199
<v Niall Sullivan>Maybe I'm underselling it there.

448
00:26:29.410 --> 00:26:33.930
<v Niall Sullivan>But it's that kind of thing, you discover
all these maybe unexpected benefits along

449
00:26:33.930 --> 00:26:36.569
<v Niall Sullivan>the way, you know, because like you say,
you, in the scope workshop, you're

450
00:26:36.569 --> 00:26:40.310
<v Niall Sullivan>planning, you know, what, what on
investment potentially, what assets to focus on.

451
00:26:40.589 --> 00:26:44.189
<v Niall Sullivan>Um, you know, what do we want to achieve,
but then there must be like unexpected

452
00:26:44.189 --> 00:26:47.439
<v Niall Sullivan>stuff like that that just keep popping up
and surprise people, right?

453
00:26:48.640 --> 00:26:52.119
<v Tom Jacques>Exactly, and this is the reason we've got
companies that have scaled to having, you

454
00:26:52.119 --> 00:26:56.040
<v Tom Jacques>know, tens of thousands of assets online
with Sensei, because it, because it does

455
00:26:56.040 --> 00:26:56.459
<v Tom Jacques>that.

456
00:26:56.959 --> 00:27:00.560
<v Tom Jacques>And then because it learns baseline so
quickly, you can then do that at scale.

457
00:27:01.150 --> 00:27:05.430
<v Tom Jacques>And when those assets learn baseline, you
set them up, you link the sensors, you,

458
00:27:05.510 --> 00:27:08.910
<v Tom Jacques>you parameterize it, so you, you set
things like off-state filtering, so you know

459
00:27:08.910 --> 00:27:11.949
<v Tom Jacques>when the machine is running and when it's
not, when it should learn things and when

460
00:27:11.949 --> 00:27:12.569
<v Tom Jacques>not to.

461
00:27:13.310 --> 00:27:16.810
<v Tom Jacques>From there, you can then just leave those
things to sort of self regulate.

462
00:27:17.390 --> 00:27:22.270
<v Tom Jacques>You've got uh AI functionality that's
gonna monitor things, look for things, then

463
00:27:22.270 --> 00:27:25.770
<v Tom Jacques>when a case is, is raised, it will show
you what's going wrong.

464
00:27:25.949 --> 00:27:29.930
<v Tom Jacques>It will pull things from the PDF
documents, from the user manuals and so on.

465
00:27:30.510 --> 00:27:34.270
<v Tom Jacques>And that's really powerful because then
all of this different information is coming

466
00:27:34.270 --> 00:27:35.869
<v Tom Jacques>to you from, from different sources.

467
00:27:36.030 --> 00:27:40.430
<v Tom Jacques>So, again, you've got things like, uh,
your PDF manual, the, the, the user spec

468
00:27:40.430 --> 00:27:41.810
<v Tom Jacques>documents, whatever it might be.

469
00:27:42.430 --> 00:27:46.630
<v Tom Jacques>The data's been pulled from this
simultaneously, it's also been pulled from what the

470
00:27:46.630 --> 00:27:50.219
<v Tom Jacques>users have, have written down in the past
as they've closed the case.

471
00:27:50.349 --> 00:27:54.510
<v Tom Jacques>You know, we've cleared the cowlings on
the motor to help it cool down and other

472
00:27:54.510 --> 00:27:54.890
<v Tom Jacques>things.

473
00:27:55.020 --> 00:27:58.790
<v Tom Jacques>And all of this stuff, including, of
course, the live telemetry is pulled into one

474
00:27:58.790 --> 00:27:59.489
<v Tom Jacques>central location.

475
00:28:00.369 --> 00:28:04.530
<v Tom Jacques>So already with one SAS solution, one
software, you're, you're doing absolutely

476
00:28:04.530 --> 00:28:06.489
<v Tom Jacques>loads with information that you've already
got.

477
00:28:06.979 --> 00:28:09.670
<v Tom Jacques>Then you've got other, um, solutions
across the business.

478
00:28:09.729 --> 00:28:13.530
<v Tom Jacques>You've got how that integrates with the
CMMS solution that you've already got in, in

479
00:28:13.530 --> 00:28:16.550
<v Tom Jacques>place and how all of this stuff links
through the business.

480
00:28:16.619 --> 00:28:21.349
<v Tom Jacques>This is what Industry 4 is, and this has
been talked about for at least a decade.

481
00:28:21.689 --> 00:28:25.650
<v Tom Jacques>Um, I think the coin, the, the, the phrase
was first coined in Germany, uh, at

482
00:28:25.650 --> 00:28:29.250
<v Tom Jacques>least, I'd say 10 or 15 years ago, maybe
longer, um.

483
00:28:29.829 --> 00:28:34.969
<v Tom Jacques>But what that now starts, what now starts
to happen is this is becoming a reality.

484
00:28:35.270 --> 00:28:39.619
<v Tom Jacques>um, you know, I remember someone saying to
me the once the, the long term, uh,

485
00:28:39.630 --> 00:28:44.300
<v Tom Jacques>future of industry is that you know
something's going wrong, the system will, um,

486
00:28:44.310 --> 00:28:45.420
<v Tom Jacques>self detect a problem.

487
00:28:45.619 --> 00:28:48.140
<v Tom Jacques>It will then reorder those parts
autonomously.

488
00:28:48.550 --> 00:28:52.050
<v Tom Jacques>They will get, you know, they would get
ordered, that would arrive.

489
00:28:52.310 --> 00:28:56.290
<v Tom Jacques>A small, um, you know, AGV would go off
and collect the component.

490
00:28:56.660 --> 00:29:00.130
<v Tom Jacques>It would also collect the tools that you
need and park next to the machine that's

491
00:29:00.130 --> 00:29:04.380
<v Tom Jacques>broken down and just put on an alert, like
a a beacon to say, you know, workers

492
00:29:04.380 --> 00:29:05.959
<v Tom Jacques>should come over and fix this machine.

493
00:29:06.859 --> 00:29:10.900
<v Tom Jacques>Um, if you add the next step, you've got
the likes of, you know, humanoid robots

494
00:29:10.900 --> 00:29:16.540
<v Tom Jacques>that may in the not too, uh, distant
future, start coming and doing those repairs

495
00:29:16.540 --> 00:29:20.219
<v Tom Jacques>for you, but again, this, this is where
Industry 4 is gonna be layered and layered

496
00:29:20.219 --> 00:29:21.469
<v Tom Jacques>and layered on top of itself.

497
00:29:21.650 --> 00:29:26.339
<v Tom Jacques>Um, and predictive maintenance, I really
do believe is, is the core fundamental

498
00:29:26.339 --> 00:29:26.819
<v Tom Jacques>element to that.

499
00:29:26.900 --> 00:29:30.140
<v Tom Jacques>So you, you can anticipate what is
happening with your machinery.

500
00:29:30.959 --> 00:29:35.979
<v Niall Sullivan>Yeah, and it, and soon we'll be talking
about industry 5.0, no doubt, or maybe,

501
00:29:36.890 --> 00:29:37.650
<v Niall Sullivan>maybe we'll skip ahead,

502
00:29:37.760 --> 00:29:42.030
<v Tom Jacques>but let, let's get industry 4 nailed
first, I think is, is where I currently sit.

503
00:29:42.449 --> 00:29:47.369
<v Niall Sullivan>Yeah, I think that's a fair, um, a fair
point actually, but, um, but yeah, so I

504
00:29:47.369 --> 00:29:51.439
<v Niall Sullivan>guess, um, as we come towards the end, I
just wanted to sort of round up and sort of

505
00:29:51.439 --> 00:29:54.750
<v Niall Sullivan>finish, um, with one final question, and
it's around.

506
00:29:55.209 --> 00:29:59.219
<v Niall Sullivan>I guess that some of the misconceptions
sort of leaders might have around predictive

507
00:29:59.219 --> 00:30:01.609
<v Niall Sullivan>maintenance, where it fits in digital
transformation.

508
00:30:01.729 --> 00:30:04.550
<v Niall Sullivan>I mean, is there anything you sort of, you
can sort of comment on that side, Tom?

509
00:30:05.010 --> 00:30:08.010
<v Tom Jacques>The main, the main one, and I've heard it
plenty of times, is that we need to

510
00:30:08.010 --> 00:30:10.800
<v Tom Jacques>digitalize everything before we start
predictive maintenance.

511
00:30:10.969 --> 00:30:14.849
<v Tom Jacques>You know, we're not ready for predictive
maintenance, um, you know, we've still got

512
00:30:14.849 --> 00:30:16.849
<v Tom Jacques>this and this and this other thing to do.

513
00:30:17.500 --> 00:30:21.290
<v Tom Jacques>Now some of those other solutions might
help with communication across the business

514
00:30:21.290 --> 00:30:25.030
<v Tom Jacques>or something else, which is equally
important, but one of the best places to start,

515
00:30:25.089 --> 00:30:30.550
<v Tom Jacques>it is PDM and it's often the entry point
to digital, I think.

516
00:30:31.010 --> 00:30:35.849
<v Tom Jacques>Um, it's, you know, it's that
misconception that it's just a tool for the

517
00:30:35.849 --> 00:30:39.410
<v Tom Jacques>maintenance team, but we've already spoken
about just in this podcast and in others

518
00:30:39.410 --> 00:30:42.770
<v Tom Jacques>in the past, um, and we're talking about
this every week with customers.

519
00:30:43.349 --> 00:30:47.979
<v Tom Jacques>That it has enormous impacts across the
entire organizations and it has financial

520
00:30:47.979 --> 00:30:54.550
<v Tom Jacques>impact, all positive, um because it's
saving you money through um all the advantages

521
00:30:54.550 --> 00:30:55.209
<v Tom Jacques>it gives you.

522
00:30:56.349 --> 00:31:01.989
<v Tom Jacques>So sometimes I, I kind of think how has
that become a misconception, um, and I think

523
00:31:01.989 --> 00:31:06.209
<v Tom Jacques>often it comes down to not fully
understanding what you're trying to achieve.

524
00:31:06.390 --> 00:31:10.619
<v Tom Jacques>So first of all, it's, it's aiming for,
you know, what exactly is it we're going to

525
00:31:10.619 --> 00:31:10.979
<v Tom Jacques>achieve?

526
00:31:11.550 --> 00:31:16.030
<v Tom Jacques>What's the best, uh, uh, most effective
way of doing that for the long term, not

527
00:31:16.030 --> 00:31:20.670
<v Tom Jacques>just a solution that benefits us for the
next two years until we find out it doesn't

528
00:31:20.670 --> 00:31:21.609
<v Tom Jacques>integrate with anything.

529
00:31:22.069 --> 00:31:23.089
<v Tom Jacques>Is it an open platform?

530
00:31:23.430 --> 00:31:27.489
<v Tom Jacques>Does it integrate across, you know, does
it help the rest of the organization?

531
00:31:27.829 --> 00:31:29.010
<v Tom Jacques>will it do that long term?

532
00:31:29.900 --> 00:31:32.839
<v Tom Jacques>Um, I think that answers your question
pretty well.

533
00:31:33.260 --> 00:31:34.420
<v Niall Sullivan>It does, it does.

534
00:31:34.619 --> 00:31:38.380
<v Niall Sullivan>And what I'd usually do at this point is
say that was the final question and ask

535
00:31:38.380 --> 00:31:41.180
<v Niall Sullivan>another question to, to, you know, to
contradict myself.

536
00:31:41.260 --> 00:31:44.939
<v Niall Sullivan>But I think actually you've summarized it
very well, Tom, and, um, and not just

537
00:31:44.939 --> 00:31:47.560
<v Niall Sullivan>that, that answer actually, but for,
throughout today.

538
00:31:47.689 --> 00:31:51.219
<v Niall Sullivan>I think it's probably, well, hopefully
it's opened up the eyes to a lot of people

539
00:31:51.219 --> 00:31:55.579
<v Niall Sullivan>that predictive maintenance can be that
enabler for digital transformation.

540
00:31:56.140 --> 00:32:00.099
<v Tom Jacques>It can, and I, I think you can see that
we're having a lot of these conversations

541
00:32:00.099 --> 00:32:04.089
<v Tom Jacques>quite often, and it's not the first time
that, you know, obviously you're asking me

542
00:32:04.089 --> 00:32:08.239
<v Tom Jacques>these questions today, but these are
things that come up, um, at least once a month

543
00:32:08.300 --> 00:32:12.459
<v Tom Jacques>with different, uh, organizations that we
either see in person or that we speak to

544
00:32:12.459 --> 00:32:12.640
<v Tom Jacques>online.

545
00:32:13.459 --> 00:32:16.010
<v Tom Jacques>Um, and it is changing, it is definitely
changing.

546
00:32:16.060 --> 00:32:20.969
<v Tom Jacques>We're starting to see a, a bigger, um,
bigger groups of people who understand more

547
00:32:20.969 --> 00:32:21.520
<v Tom Jacques>of this.

548
00:32:21.859 --> 00:32:24.300
<v Tom Jacques>Um, I'm learning about this every week.

549
00:32:24.420 --> 00:32:28.030
<v Tom Jacques>I'm also speaking to different colleagues
across Siemens, and we're building a very

550
00:32:28.030 --> 00:32:31.719
<v Tom Jacques>good picture of, you know, how the
different divisions can work well together.

551
00:32:32.099 --> 00:32:35.699
<v Tom Jacques>Accelerator and Roland Bush has got the
right idea with all of this, of how we make

552
00:32:35.699 --> 00:32:39.719
<v Tom Jacques>all of these different products work
together seamlessly is the key.

553
00:32:40.739 --> 00:32:41.020
<v Niall Sullivan>Exactly.

554
00:32:41.140 --> 00:32:42.420
<v Niall Sullivan>And what a nice way to.

555
00:32:42.719 --> 00:32:46.560
<v Niall Sullivan>To end the episode today, so, um, no thank
you, Tom, once again for sharing your

556
00:32:46.560 --> 00:32:50.800
<v Niall Sullivan>insights, um, of course we'll invite you
back, um, for future episodes too if you're

557
00:32:50.800 --> 00:32:51.400
<v Niall Sullivan>open to it.

558
00:32:51.599 --> 00:32:53.500
<v Tom Jacques>It's always a pleasure, it's always a
pleasure.

559
00:32:54.000 --> 00:32:57.760
<v Niall Sullivan>Fantastic, fantastic, but yeah, so thank
you for your time today, um, and thank you

560
00:32:57.760 --> 00:33:01.400
<v Niall Sullivan>everyone out there for listening, wherever
you are, and we'll see you on the next

561
00:33:01.400 --> 00:33:01.520
<v Niall Sullivan>episode.

562
00:33:01.640 --> 00:33:02.780
<v Niall Sullivan>Thank you very much.

563
00:33:03.319 --> 00:33:04.140
<v Tom Jacques>Cheers.

564
00:33:07.619 --> 00:33:12.579
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

565
00:33:12.579 --> 00:33:15.959
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
