WEBVTT
Language: en-US

1
00:00:01.200 --> 00:00:04.599
<v Jonathan>For our customers though, the benefits
that they receive really is the maintenance

2
00:00:04.599 --> 00:00:08.720
<v Jonathan>of uptime, you know, having that early
indication that there are signs of

3
00:00:08.720 --> 00:00:13.319
<v Jonathan>degradation so that uh with enough detail
that a maintenance team can go and start

4
00:00:13.319 --> 00:00:15.979
<v Jonathan>to repair and fix what is going wrong.

5
00:00:16.639 --> 00:00:19.280
<v Jonathan>But they also benefit from precise and
correct maintenance.

6
00:00:19.520 --> 00:00:24.389
<v Jonathan>So for the other 95% of their assets,
machines, their operations that are in

7
00:00:24.389 --> 00:00:28.379
<v Jonathan>perfectly good order, that you have a
centralized visibility of this.

8
00:00:28.799 --> 00:00:33.659
<v Jonathan>Um, it also helps and does touch on
sustainability because, uh, or has an impact on

9
00:00:33.659 --> 00:00:38.540
<v Jonathan>sustainability because there is less time
spent idling, less consumables used while

10
00:00:38.540 --> 00:00:42.360
<v Jonathan>performing maintenance, less emergency
transportation of spares.

11
00:00:42.819 --> 00:00:47.619
<v Jonathan>So really predictive maintenance in an
industry like food and beverage where it's

12
00:00:47.619 --> 00:00:50.639
<v Jonathan>high volumes, you know, you can sell as
much as you can produce.

13
00:00:52.590 --> 00:00:56.029
<v Speaker 2>Welcome to the trend detection podcast,
powered by Siemens.

14
00:00:58.340 --> 00:00:59.700
<v James>Hello and welcome everyone.

15
00:00:59.860 --> 00:01:03.959
<v James>Uh, I'm James, and I'll be your host for
today's webinar on predictive maintenance

16
00:01:03.959 --> 00:01:05.519
<v James>in the food and beverage industry.

17
00:01:05.980 --> 00:01:07.010
<v James>Well, thank you for joining us.

18
00:01:07.139 --> 00:01:11.180
<v James>Uh, we're really excited about today's
session because predictive maintenance is

19
00:01:11.180 --> 00:01:16.019
<v James>fast becoming a competitive advantage for
manufacturers, um, especially in an

20
00:01:16.019 --> 00:01:18.120
<v James>industry as fast moving as F&amp;B.

21
00:01:19.180 --> 00:01:23.980
<v James>So today we'll take a closer look at what
predictive maintenance is and how it

22
00:01:23.980 --> 00:01:25.860
<v James>differs from traditional monitoring.

23
00:01:26.250 --> 00:01:30.889
<v James>We'll look into how leading manufacturers
around the world are already seeing real

24
00:01:30.889 --> 00:01:32.589
<v James>value in predictive maintenance.

25
00:01:33.199 --> 00:01:36.900
<v James>And of course we'll see how this is being
applied within the Middle East market.

26
00:01:37.930 --> 00:01:42.330
<v James>Now if you have any questions, uh, please
use the Q&amp;A function that we have and we

27
00:01:42.330 --> 00:01:46.370
<v James>will ask our speakers your questions at
the end of the session.

28
00:01:46.760 --> 00:01:50.930
<v James>Now, talking about our experts, I'd like
to introduce you to Jonathan.

29
00:01:51.169 --> 00:01:55.150
<v James>He is the head of solution engineering for
Sensi Predictive maintenance.

30
00:01:55.410 --> 00:02:00.000
<v James>And we also have Rakesh, our other expert,
who is the digital enterprise services

31
00:02:00.000 --> 00:02:02.610
<v James>port portfolio manager here in the Middle
East.

32
00:02:03.410 --> 00:02:04.910
<v James>Thank you both for your time today.

33
00:02:05.129 --> 00:02:09.750
<v James>Uh, looking forward towards our
discussions, um, and perhaps maybe to kick off,

34
00:02:09.850 --> 00:02:13.690
<v James>Jonathan, if I could come to you and ask,
maybe if you could just give a quick

35
00:02:13.690 --> 00:02:18.729
<v James>introduction onto predictive maintenance,
um, especially in regards to the F&amp;B

36
00:02:18.729 --> 00:02:19.210
<v James>market.

37
00:02:19.809 --> 00:02:22.389
<v Jonathan>Absolutely and good afternoon to everyone
online.

38
00:02:23.089 --> 00:02:24.410
<v Jonathan>So predictive maintenance.

39
00:02:25.149 --> 00:02:29.550
<v Jonathan>Essentially, it's an evolution from
traditional condition monitoring, but instead of

40
00:02:29.550 --> 00:02:33.429
<v Jonathan>having a specialist go around the facility
taking manual measurements, then

41
00:02:33.429 --> 00:02:37.669
<v Jonathan>uploading them, uh, to the computer,
analyzing it and reporting back on it, you

42
00:02:37.669 --> 00:02:42.789
<v Jonathan>know, I think you could think of that
process like a vibration analyst, uh, going

43
00:02:42.789 --> 00:02:45.089
<v Jonathan>around and doing a manual process.

44
00:02:45.630 --> 00:02:47.070
<v Jonathan>This is now automated.

45
00:02:47.309 --> 00:02:51.570
<v Jonathan>So the process of data collection,
analysis and reporting is automated.

46
00:02:52.539 --> 00:02:55.320
<v Jonathan>Uh, using technology, uh, and, uh.

47
00:02:56.850 --> 00:03:02.410
<v Jonathan>Technology and systems and solutions like
Senseiie within Siemens, but like any good

48
00:03:02.410 --> 00:03:05.839
<v Jonathan>reliability engineer, the system continues
to learn.

49
00:03:06.009 --> 00:03:10.649
<v Jonathan>It learns about failure modes, failure
patterns, and starts to become very specific

50
00:03:10.649 --> 00:03:12.490
<v Jonathan>when it sees signs of degradation.

51
00:03:13.369 --> 00:03:18.419
<v Jonathan>But it's also not limited to rotating
equipment and doesn't just use one form or one

52
00:03:18.419 --> 00:03:20.460
<v Jonathan>stream of data like vibration.

53
00:03:20.899 --> 00:03:26.820
<v Jonathan>It incorporates a wide range of data
sources and data types to get a complete view

54
00:03:26.820 --> 00:03:31.979
<v Jonathan>of an asset's condition, signs of
degradation, um, and really start to highlight

55
00:03:31.979 --> 00:03:33.979
<v Jonathan>those important details when needed.

56
00:03:34.929 --> 00:03:38.330
<v Jonathan>For our customers though, the benefits
that they receive really is the maintenance

57
00:03:38.330 --> 00:03:42.410
<v Jonathan>of uptime, you know, having that early
indication that there are signs of

58
00:03:42.410 --> 00:03:47.050
<v Jonathan>degradation so that uh with enough detail
that a maintenance team can go and start

59
00:03:47.050 --> 00:03:49.630
<v Jonathan>to repair and fix what is going wrong.

60
00:03:50.339 --> 00:03:52.949
<v Jonathan>But they also benefit from precise and
correct maintenance.

61
00:03:53.270 --> 00:03:58.110
<v Jonathan>So for the other 95% of their assets,
machines, their operations that are in

62
00:03:58.110 --> 00:04:02.089
<v Jonathan>perfectly good order, that you have a
centralized visibility of this.

63
00:04:02.630 --> 00:04:07.389
<v Jonathan>Um, it also helps and does touch on
sustainability because, uh, or has an impact on

64
00:04:07.389 --> 00:04:12.270
<v Jonathan>sustainability because there is less time
spent idling, less consumables used while

65
00:04:12.270 --> 00:04:15.970
<v Jonathan>performing maintenance, less emergency
transportation of spares.

66
00:04:16.480 --> 00:04:21.329
<v Jonathan>So really predictive maintenance in an
industry like food and beverage where it's

67
00:04:21.329 --> 00:04:25.809
<v Jonathan>high volumes, you know, you can sell as
much as you can produce, that having the

68
00:04:25.809 --> 00:04:32.119
<v Jonathan>ability to Have a really good maintenance
strategy in place, backed by a centralized

69
00:04:32.119 --> 00:04:36.720
<v Jonathan>visibility, um, it means that you can
produce more and essentially make more.

70
00:04:38.459 --> 00:04:38.859
<v James>Right.

71
00:04:39.420 --> 00:04:40.500
<v James>Thank you for that overview there.

72
00:04:40.660 --> 00:04:44.500
<v James>Um, maybe Rakesh, you can give us a little
bit of insight of like what Jonathan

73
00:04:44.500 --> 00:04:47.140
<v James>says, but what the relevance is then for
the Middle East market.

74
00:04:47.980 --> 00:04:51.579
<v Rakesh>Yeah, thanks, James, and uh very good
afternoon to one and all.

75
00:04:52.279 --> 00:04:57.140
<v Rakesh>I mean, the Middle East region is very
special, yeah, I mean, It must address food

76
00:04:57.140 --> 00:05:02.100
<v Rakesh>security challenges, and this is resulting
from water scarcity, climate change, hot

77
00:05:02.100 --> 00:05:03.700
<v Rakesh>climate, and regional instability.

78
00:05:04.380 --> 00:05:09.829
<v Rakesh>And food and beverage plays a very
important role in uh the Middle East diversified

79
00:05:09.899 --> 00:05:10.920
<v Rakesh>industrial sector.

80
00:05:12.200 --> 00:05:15.880
<v Rakesh>Uh, the government of, uh, I mean, you can
see regional countries like, uh, the

81
00:05:15.880 --> 00:05:20.859
<v Rakesh>United Arab Emirates and Saudi Arabia
bringing initiatives such as, uh, the Smart

82
00:05:20.859 --> 00:05:25.760
<v Rakesh>manufacturing incentive program in, in Abu
Dhabi that incentivizes sectors such as

83
00:05:25.760 --> 00:05:29.200
<v Rakesh>food and Bev, uh, to embrace Industry 4.0.

84
00:05:29.760 --> 00:05:35.059
<v Rakesh>So in short, yes, it does play a very
important role in the food security aspect,

85
00:05:35.609 --> 00:05:36.660
<v Rakesh>uh, in the Middle East.

86
00:05:38.869 --> 00:05:39.190
<v James>Right.

87
00:05:39.429 --> 00:05:43.109
<v James>And then maybe while we're talking about
the region, could you go into some of the

88
00:05:43.109 --> 00:05:46.750
<v James>challenges, uh, in some of the traditional
maintenance approaches that you're

89
00:05:46.750 --> 00:05:47.089
<v James>seeing?

90
00:05:48.170 --> 00:05:51.880
<v Rakesh>Yeah, traditional maintenance procedures,
I mean, uh, they can be less efficient,

91
00:05:52.299 --> 00:05:57.200
<v Rakesh>uh, resulting in increased downtime,
higher repair costs, uh, greater reliance on

92
00:05:57.500 --> 00:06:02.459
<v Rakesh>manual processes, uh, and in the long run
this is, uh, I mean this is leading to

93
00:06:02.459 --> 00:06:05.339
<v Rakesh>compromised quality without any predictive
insights.

94
00:06:06.239 --> 00:06:11.089
<v Rakesh>And if you look at the food and beverage
factories in the Middle East, they suffer

95
00:06:11.089 --> 00:06:15.000
<v Rakesh>from one thing is the heavy reliance on
global OEMs.

96
00:06:15.290 --> 00:06:18.809
<v Rakesh>All of them are from Central Europe, East
Asia, etc.

97
00:06:19.089 --> 00:06:21.130
<v Rakesh>So there's a lack of documentation of
their plants.

98
00:06:21.839 --> 00:06:25.010
<v Rakesh>Uh, if you understand the dynamics of food
and death plants, they're built by

99
00:06:25.010 --> 00:06:30.850
<v Rakesh>multiple OEMs over a period of time, and
this brings in a lot of complexity with

100
00:06:30.850 --> 00:06:32.790
<v Rakesh>SOPs in operation and maintenance.

101
00:06:33.929 --> 00:06:38.410
<v Rakesh>And not to mention this, the region is
driven by expatriate population, so there's

102
00:06:38.410 --> 00:06:42.690
<v Rakesh>higher employee attrition rate in the
Middle East, and this can cripple

103
00:06:42.690 --> 00:06:45.329
<v Rakesh>productivity, erode institutional
knowledge.

104
00:06:45.690 --> 00:06:49.929
<v Rakesh>Uh, it could drain resources, and this is
prevalent due to the, the large landscape

105
00:06:49.929 --> 00:06:50.570
<v Rakesh>of end users.

106
00:06:50.649 --> 00:06:55.570
<v Rakesh>We're talking about 5000 F&amp;B end users
in the market with a revenue of more than a

107
00:06:55.570 --> 00:06:56.959
<v Rakesh>million dollars, yeah.

108
00:06:57.470 --> 00:07:00.739
<v Rakesh>So, these are regional specific
challenges, James and Jonathan.

109
00:07:00.829 --> 00:07:06.910
<v Rakesh>So uh I would really say that over a
period of time, uh, we need to look at regional

110
00:07:06.910 --> 00:07:11.709
<v Rakesh>specific challenges against global
challenges, and probably technologies like PDM

111
00:07:11.709 --> 00:07:12.769
<v Rakesh>can actually fill that gap.

112
00:07:14.279 --> 00:07:14.679
<v James>OK.

113
00:07:14.920 --> 00:07:19.679
<v James>Well, on that one, the segue to Jonathan,
like, so how can, how can like a PDM, you

114
00:07:19.679 --> 00:07:23.399
<v James>know, predictive maintenance enhance
operational efficiencies and, and

115
00:07:23.399 --> 00:07:24.260
<v James>consistencies?

116
00:07:25.570 --> 00:07:30.899
<v Jonathan>Yeah, uh, as I mentioned earlier, that
centralized visibility of your production, of

117
00:07:30.899 --> 00:07:33.839
<v Jonathan>your machines, your operations is
fantastic.

118
00:07:34.380 --> 00:07:39.459
<v Jonathan>Um, and Rakesh, you, you said that having
a reliance on multiple OEMs, a facility is

119
00:07:39.459 --> 00:07:45.480
<v Jonathan>created with a full stack of OEMs trying
to merge these things together.

120
00:07:45.820 --> 00:07:50.660
<v Jonathan>Um, quite often they don't talk to each
other, so you don't, they are siloed systems

121
00:07:50.660 --> 00:07:55.929
<v Jonathan>that you have to Somehow configure and
make work together, um, in a way, or you

122
00:07:55.929 --> 00:07:59.709
<v Jonathan>don't configure them and you don't have
that, uh, centralized visibility.

123
00:08:00.209 --> 00:08:05.410
<v Jonathan>But when you do start to incorporate that
one central point that can speak to all

124
00:08:05.410 --> 00:08:09.609
<v Jonathan>the OEMs where you can have the visibility
to all these operations, you are in

125
00:08:09.609 --> 00:08:10.029
<v Jonathan>control.

126
00:08:10.570 --> 00:08:17.309
<v Jonathan>You are, you have the The know-how now,
the, this visibility to plan in your

127
00:08:17.309 --> 00:08:20.989
<v Jonathan>maintenance correctly, to plan in your
production cycles, to have an understanding

128
00:08:20.989 --> 00:08:26.109
<v Jonathan>and better projections of when you're
making, what you're making, how you're making

129
00:08:26.109 --> 00:08:32.669
<v Jonathan>it, and a reliability of these operations
so that you know what you're making is of

130
00:08:32.669 --> 00:08:33.570
<v Jonathan>the highest quality.

131
00:08:34.510 --> 00:08:40.669
<v Jonathan>So really it is about gaining an
understanding from all areas using your OT uh

132
00:08:40.669 --> 00:08:46.229
<v Jonathan>information, your IT information, and also
the human element to bring it all into 11

133
00:08:46.229 --> 00:08:48.770
<v Jonathan>point, um, so that you're in better
control.

134
00:08:49.909 --> 00:08:51.280
<v James>OK, I mean, it makes sense.

135
00:08:51.469 --> 00:08:54.909
<v James>And then Rakesh, like maybe if you just
bring it down a level lower, how does this

136
00:08:54.909 --> 00:08:59.590
<v James>really like tie in with like the Siemens
portfolio, um, how can it help with like a

137
00:08:59.590 --> 00:09:01.239
<v James>customer's digitalization journey?

138
00:09:04.020 --> 00:09:10.330
<v Rakesh>I mean, in fact, Siemenstrial automation I
mean we we brought a sensitive cloud

139
00:09:10.960 --> 00:09:15.270
<v Rakesh>solution and you know I'm talking about uh
connectivity across levels.

140
00:09:15.309 --> 00:09:18.489
<v Rakesh>I'm talking about horizontal connectivity,
vertical connectivity.

141
00:09:18.919 --> 00:09:24.090
<v Rakesh>And being a player in that industry, we
provide that one-stop shop, uh, to provide

142
00:09:24.090 --> 00:09:28.770
<v Rakesh>an end to end uh turnkey solution for PDM
offerings.

143
00:09:30.880 --> 00:09:34.440
<v Rakesh>Charlie should say that uh we one of the
very few vendors in the world that offer

144
00:09:34.440 --> 00:09:39.679
<v Rakesh>this entire ecosystem uh from sensor to
cloud, and uh it plays a very important role

145
00:09:39.679 --> 00:09:45.820
<v Rakesh>in the bigger accelerator uh initiative of
Siemens, uh, bringing in an ecosystem of

146
00:09:46.159 --> 00:09:52.340
<v Rakesh>like-minded partners globally to actually
collaborate uh and uh communicate between

147
00:09:52.340 --> 00:09:54.460
<v Rakesh>our systems uh very efficiently.

148
00:09:55.789 --> 00:09:59.909
<v Jonathan>And I'll just add on to that, Rakesh,
Siemens also bring the, the specialists and

149
00:09:59.909 --> 00:10:04.830
<v Jonathan>the expertise in all of those layers and
in the industries, you know, it's not just

150
00:10:04.830 --> 00:10:09.710
<v Jonathan>about the, the technology that Siemens
provides, but it is the, the human elements

151
00:10:09.710 --> 00:10:11.929
<v Jonathan>as well backing the technology.

152
00:10:13.210 --> 00:10:13.409
<v Rakesh>Absolutely.

153
00:10:14.070 --> 00:10:17.549
<v Rakesh>I mean, we speak the OT language and uh
that differentiates from the IT landscape

154
00:10:17.549 --> 00:10:22.219
<v Rakesh>and we, we provide the bridge between the
OT and the IT world, and I think that's

155
00:10:22.219 --> 00:10:25.440
<v Rakesh>the perfect synergy for solutions like
PTM.

156
00:10:26.250 --> 00:10:26.969
<v James>Yeah, definitely.

157
00:10:27.169 --> 00:10:29.849
<v James>And Jonathan, I mean, you, you're working
with customers kind of all around the

158
00:10:29.849 --> 00:10:33.950
<v James>world, you know, do you have maybe any
examples that you can bring, you know, from,

159
00:10:34.169 --> 00:10:35.989
<v James>especially from the F&amp;B market?

160
00:10:37.299 --> 00:10:39.179
<v Jonathan>Yeah, absolutely, um.

161
00:10:40.419 --> 00:10:44.739
<v Jonathan>We've got a number of different types of
FMB customers that we're working with

162
00:10:44.739 --> 00:10:45.179
<v Jonathan>globally.

163
00:10:45.539 --> 00:10:49.450
<v Jonathan>Um, I think probably one of the, the most
interesting ones that are on my plate at

164
00:10:49.450 --> 00:10:53.299
<v Jonathan>the moment, that we have a customer that,
uh, deal with pet nutrition, essentially

165
00:10:53.299 --> 00:10:53.960
<v Jonathan>pet care.

166
00:10:54.690 --> 00:11:00.440
<v Jonathan>And they've gone for a global deployment,
so we're looking at many, many factories

167
00:11:00.440 --> 00:11:01.150
<v Jonathan>around the world.

168
00:11:03.239 --> 00:11:06.679
<v Jonathan>They have identified that in various
areas, they have different requirements.

169
00:11:06.919 --> 00:11:11.520
<v Jonathan>So in North America, for example, they
have a, a specific requirement for

170
00:11:11.520 --> 00:11:18.239
<v Jonathan>handholding, very much a, a managed
service, so that is, uh, full investigations,

171
00:11:18.320 --> 00:11:23.390
<v Jonathan>sensor selections, installations,
integrations with their existing systems.

172
00:11:23.820 --> 00:11:29.200
<v Jonathan>Um, that is training for personnel, that
is even, um, managed service of looking at

173
00:11:29.200 --> 00:11:32.750
<v Jonathan>the results, interpreting them, and, you
know, presenting that to the maintenance

174
00:11:32.750 --> 00:11:34.210
<v Jonathan>teams with recommendations.

175
00:11:35.090 --> 00:11:41.380
<v Jonathan>Uh, in other regions, if we look at Asia,
they are looking for not a necessarily a

176
00:11:41.380 --> 00:11:46.659
<v Jonathan>center-led deployment but looking to
really utilize their existing OT data and

177
00:11:46.659 --> 00:11:48.599
<v Jonathan>their, their existing investments.

178
00:11:49.309 --> 00:11:54.940
<v Jonathan>Um, and using or letting the technology
and our generative AI capabilities be the,

179
00:11:55.270 --> 00:11:57.969
<v Jonathan>that knowledge and recommendation basis
for them.

180
00:11:58.429 --> 00:12:03.700
<v Jonathan>You know, so that is a, a very interesting
way to see how we have to approach the,

181
00:12:04.190 --> 00:12:08.179
<v Jonathan>the initial setup with them differently in
different regions.

182
00:12:08.549 --> 00:12:10.719
<v Jonathan>However, the underlying technology is the
same.

183
00:12:10.989 --> 00:12:14.989
<v Jonathan>You know, the results, the, the, the
logic, the machine learning factor of it is

184
00:12:14.989 --> 00:12:15.669
<v Jonathan>exactly the same.

185
00:12:15.750 --> 00:12:17.530
<v Jonathan>It's just how we would implement that.

186
00:12:18.349 --> 00:12:23.059
<v Jonathan>But there are huge variants in the type of
machines we're looking at for this

187
00:12:23.059 --> 00:12:23.549
<v Jonathan>customer.

188
00:12:23.909 --> 00:12:28.590
<v Jonathan>You know, some are really focusing on
support assets, fans, compressors, you know,

189
00:12:28.710 --> 00:12:29.809
<v Jonathan>your utilities.

190
00:12:30.150 --> 00:12:34.349
<v Jonathan>Others are heavily focused on their main
production assets, your extruders,

191
00:12:34.469 --> 00:12:36.349
<v Jonathan>chocolate conches, and so on.

192
00:12:36.750 --> 00:12:40.030
<v Jonathan>Um, uh, oh yeah, those types of machines.

193
00:12:40.109 --> 00:12:43.890
<v Jonathan>So very varying approaches to
implementation.

194
00:12:44.739 --> 00:12:49.979
<v Jonathan>However, when we look at the, the value of
this, it really is around maintenance

195
00:12:49.979 --> 00:12:50.780
<v Jonathan>efficiency.

196
00:12:51.140 --> 00:12:55.539
<v Jonathan>So reducing your reactive, your unplanned
events, uh, making sure they have better

197
00:12:55.539 --> 00:13:01.820
<v Jonathan>visibility of their planned maintenance
approaches and really moving them into a, a

198
00:13:01.820 --> 00:13:03.260
<v Jonathan>more efficient way.

199
00:13:03.929 --> 00:13:07.609
<v Jonathan>If we look at some of the other successes
from some of our other food and beverage

200
00:13:07.609 --> 00:13:13.049
<v Jonathan>customers, there's um a dairy in Europe
that we went and investigated.

201
00:13:13.169 --> 00:13:14.989
<v Jonathan>Um, I was there on site personally.

202
00:13:15.630 --> 00:13:20.590
<v Jonathan>And what we found is that in their
existing infrastructure, they had very little

203
00:13:20.590 --> 00:13:21.020
<v Jonathan>control.

204
00:13:21.510 --> 00:13:23.909
<v Jonathan>Their systems were extremely siloed.

205
00:13:24.229 --> 00:13:28.229
<v Jonathan>They weren't sure whether or not we could
get access to the data which was there, so

206
00:13:28.229 --> 00:13:31.869
<v Jonathan>we had to plan for a, a hardware-led
deployment.

207
00:13:32.659 --> 00:13:37.580
<v Jonathan>Anyway, long story short is, we came in,
we made the recommendations, we helped to

208
00:13:37.580 --> 00:13:41.900
<v Jonathan>make sure that it was installed correctly,
um, that various sensors were put on the

209
00:13:41.900 --> 00:13:46.340
<v Jonathan>right components in the right way and data
was coming through, and they, they got a

210
00:13:46.340 --> 00:13:51.250
<v Jonathan>return of investment for their entire
investment including hardware with one, with

211
00:13:51.250 --> 00:13:51.719
<v Jonathan>one save.

212
00:13:52.059 --> 00:13:57.640
<v Jonathan>One notification, um, on a very critical
piece of equipment meant that they had a

213
00:13:57.640 --> 00:13:58.820
<v Jonathan>return on investment immediately.

214
00:13:59.200 --> 00:14:04.090
<v Jonathan>So a very short space of time, but it is
about targeting the value in an environment

215
00:14:04.559 --> 00:14:09.210
<v Jonathan>and uh we have a very structured process
which I I'll, I believe we'll get into it a

216
00:14:09.210 --> 00:14:10.030
<v Jonathan>little bit later.

217
00:14:10.890 --> 00:14:14.270
<v James>Yeah, I mean, you're talking about like,
again, we've talked about the efficiencies

218
00:14:14.369 --> 00:14:18.090
<v James>and so forth, but the other side of the
coin which a lot of our customers are asking

219
00:14:18.090 --> 00:14:22.929
<v James>about is around like quality control, um,
and, and like, for example, compliance,

220
00:14:23.010 --> 00:14:24.210
<v James>like these types of legal issues.

221
00:14:24.250 --> 00:14:27.890
<v James>I mean, where can like predictive
maintenance come in there to, to support?

222
00:14:28.020 --> 00:14:29.809
<v Jonathan>Yeah, absolutely.

223
00:14:29.929 --> 00:14:35.609
<v Jonathan>Well, with a better or a more reliable
plant or a more reliable line even, you're

224
00:14:35.609 --> 00:14:37.010
<v Jonathan>going to have better product quality.

225
00:14:37.679 --> 00:14:42.840
<v Jonathan>So if you know that your components are
running in a perfect condition or in a very

226
00:14:42.840 --> 00:14:49.260
<v Jonathan>good condition, that you aren't having
tolerance drifts, uh, that you have The

227
00:14:49.260 --> 00:14:52.020
<v Jonathan>components are running the way that they
should, you're going to have better

228
00:14:52.020 --> 00:14:52.380
<v Jonathan>quality.

229
00:14:52.500 --> 00:14:54.400
<v Jonathan>So some examples of this.

230
00:14:55.039 --> 00:14:59.219
<v Jonathan>is we have been monitoring for one of our
customers exit gauge.

231
00:14:59.429 --> 00:15:05.239
<v Jonathan>So product goes in through rollers to get
a desired width of product coming out

232
00:15:05.239 --> 00:15:10.239
<v Jonathan>before it goes into the cutting then
packaging process and by monitoring the exit

233
00:15:10.239 --> 00:15:16.000
<v Jonathan>gauge, a, a quality parameter, we've been
able to see where some of these rollers

234
00:15:16.000 --> 00:15:20.700
<v Jonathan>start to become deformed or the tolerance
of the, the rollers starts to move away.

235
00:15:21.309 --> 00:15:25.770
<v Jonathan>So it shows us, it gives us an indication
of mechanical degradation.

236
00:15:26.270 --> 00:15:31.169
<v Jonathan>However, by spotting that early, we can
then make sure that they aren't doing a run.

237
00:15:32.500 --> 00:15:32.780
<v Jonathan>Excuse me.

238
00:15:33.770 --> 00:15:35.989
<v Jonathan>There is a fire alarm test this morning.

239
00:15:36.820 --> 00:15:38.460
<v James>Well, at least we know it's live, yeah.

240
00:15:39.179 --> 00:15:39.729
<v Jonathan>Yes, absolutely.

241
00:15:41.179 --> 00:15:45.859
<v Jonathan>Um, yeah, so by monitoring this quality
parameter, we can make sure that we give

242
00:15:45.859 --> 00:15:49.659
<v Jonathan>them early indication that there is
something wrong from a mechanical degradation

243
00:15:49.659 --> 00:15:55.979
<v Jonathan>perspective, but also that they haven't
spent 2 days or 2 weeks even producing and

244
00:15:55.979 --> 00:16:00.840
<v Jonathan>packaging and then starting to distribute
uh products which have got a bad quality

245
00:16:01.260 --> 00:16:01.619
<v Jonathan>behind them.

246
00:16:02.520 --> 00:16:08.859
<v Jonathan>Also, if you look at various things now
looking at mechanical uh parameters such as

247
00:16:09.440 --> 00:16:13.119
<v Jonathan>if you look at a sealer bar, a sealer bar
is essentially an element.

248
00:16:13.440 --> 00:16:17.239
<v Jonathan>If that sealer bar is not running
correctly or is not operating correctly, let's say

249
00:16:17.239 --> 00:16:21.820
<v Jonathan>it doesn't have a uniform, um, heating
profile across the bar.

250
00:16:22.520 --> 00:16:27.919
<v Jonathan>When that goes to seal your package, that
could then um leave spaces open on one of

251
00:16:27.919 --> 00:16:28.549
<v Jonathan>the sides.

252
00:16:29.070 --> 00:16:34.010
<v Jonathan>So that has a huge product quality and
then can, uh, product quality impact.

253
00:16:34.809 --> 00:16:40.049
<v Jonathan>Which probably won't get picked up or may
not get picked up immediately, um, and

254
00:16:40.049 --> 00:16:45.070
<v Jonathan>therefore you have recalls because
packages aren't sealed, you know, um, food

255
00:16:45.070 --> 00:16:49.210
<v Jonathan>products are now exposed to whatever
elements they have been and there is a problem

256
00:16:49.210 --> 00:16:49.869
<v Jonathan>with that.

257
00:16:50.450 --> 00:16:55.369
<v Jonathan>So again, just recap that, by having
better reliability, you make sure that your

258
00:16:55.369 --> 00:17:00.890
<v Jonathan>standards and processes are followed
better and that you have less potential for

259
00:17:00.890 --> 00:17:01.609
<v Jonathan>issues later on.

260
00:17:03.770 --> 00:17:04.250
<v James>It makes sense.

261
00:17:04.369 --> 00:17:06.050
<v James>I mean, OK, this is, this is all good.

262
00:17:06.170 --> 00:17:10.449
<v James>I think there'll be some people in the
audience who perhaps haven't, uh, deployed

263
00:17:10.449 --> 00:17:13.770
<v James>predictive maintenance yet, you know,
like, so where would you, for these people,

264
00:17:13.849 --> 00:17:15.209
<v James>where would you, what would you recommend?

265
00:17:15.270 --> 00:17:19.010
<v James>Like what are the first steps and like the
best practices to get started when it

266
00:17:19.010 --> 00:17:23.380
<v James>comes to, uh, your first, your first
introduction to predict.

267
00:17:25.170 --> 00:17:30.530
<v Jonathan>I always say that any one of our customers
needs to start with the problem

268
00:17:30.530 --> 00:17:33.250
<v Jonathan>definition, defining what it is they're
trying to solve.

269
00:17:33.729 --> 00:17:37.810
<v Jonathan>If they're just wanting to implement
technology for the sake of it, that's probably

270
00:17:37.810 --> 00:17:39.270
<v Jonathan>not the right driver.

271
00:17:39.810 --> 00:17:45.489
<v Jonathan>But if you can or if you identify in your
environment that you have maintenance

272
00:17:45.489 --> 00:17:50.119
<v Jonathan>inefficiencies, That your teams are
overworked, um, that they are having to

273
00:17:50.119 --> 00:17:55.910
<v Jonathan>firefight the entire time, that the cost
of downtime and this lack of reliability is

274
00:17:55.910 --> 00:18:02.199
<v Jonathan>huge, that you have potentials for
increasing your OEE, um, and your output, then

275
00:18:02.199 --> 00:18:04.359
<v Jonathan>that is a good place to say, yes, I want
to start.

276
00:18:04.790 --> 00:18:06.099
<v Jonathan>So you have a problem definition.

277
00:18:07.079 --> 00:18:12.130
<v Jonathan>And then for us, our structured
methodology, I say it's quite simple, it's quite

278
00:18:12.130 --> 00:18:15.010
<v Jonathan>simple for us, but we guide our customers
through this.

279
00:18:15.609 --> 00:18:19.550
<v Jonathan>So for us, we, uh, we have 5 phases in
every single project.

280
00:18:19.770 --> 00:18:22.869
<v Jonathan>These are scope, design, deploy, operate,
and refine.

281
00:18:23.329 --> 00:18:26.150
<v Jonathan>And within each of these phases, there are
4 steps.

282
00:18:26.530 --> 00:18:29.790
<v Jonathan>But again, as I said, we manage the
process with our customers.

283
00:18:30.329 --> 00:18:32.390
<v Jonathan>So if I just uh describe them briefly.

284
00:18:33.119 --> 00:18:36.810
<v Jonathan>Scope phase is really information
gathering within the sales cycle.

285
00:18:37.209 --> 00:18:41.229
<v Jonathan>We make sure that there is the correct
problem definition, that we are looking at

286
00:18:42.209 --> 00:18:46.709
<v Jonathan>solving problems and really giving or
generating value in a customer's environment.

287
00:18:47.329 --> 00:18:51.839
<v Jonathan>Then we would assess the assets, where
this value is gonna come from, the data,

288
00:18:51.930 --> 00:18:56.989
<v Jonathan>infrastructure, who's gonna be involved in
the project so that Um, we get a project

289
00:18:56.989 --> 00:19:01.910
<v Jonathan>team together and they are aware of their
inputs, their requirements, and we define

290
00:19:01.910 --> 00:19:04.589
<v Jonathan>the success criteria, all within the sales
cycle.

291
00:19:05.359 --> 00:19:09.459
<v Jonathan>Then once the project starts, we go into
the design phase, which is an in-depth look

292
00:19:09.459 --> 00:19:12.500
<v Jonathan>or getting into the nitty-gritty of the
project.

293
00:19:12.750 --> 00:19:17.520
<v Jonathan>You know, operational interdependency
between machines, um, you know, what are the

294
00:19:17.520 --> 00:19:21.640
<v Jonathan>actual communication protocols between
various infrastructure or architecture

295
00:19:21.640 --> 00:19:22.280
<v Jonathan>systems.

296
00:19:23.170 --> 00:19:23.969
<v Jonathan>And so on.

297
00:19:24.290 --> 00:19:26.760
<v Jonathan>Then deploying is about making the data
move.

298
00:19:27.050 --> 00:19:30.969
<v Jonathan>So if there is need for additional
hardware that that gets installed, that systems

299
00:19:30.969 --> 00:19:36.010
<v Jonathan>are integrated, as um data is streaming
into the application, assets are on boarded,

300
00:19:36.199 --> 00:19:41.650
<v Jonathan>users are on boarded and then trained,
which typically takes about 1 to 2 hours.

301
00:19:41.810 --> 00:19:46.410
<v Jonathan>It's very, very It's an intuitive system
and it doesn't require that much training,

302
00:19:46.609 --> 00:19:47.349
<v Jonathan>thankfully.

303
00:19:48.010 --> 00:19:52.319
<v Jonathan>The operate phase runs through a best
practice approach on using the application,

304
00:19:52.609 --> 00:19:57.969
<v Jonathan>monitoring notifications, adding in work
events, doing daily, weekly, monthly

305
00:19:57.969 --> 00:20:02.209
<v Jonathan>reviews, and then in the refined phase,
it's about making it as good as it can

306
00:20:02.209 --> 00:20:04.020
<v Jonathan>possibly be in that environment.

307
00:20:04.770 --> 00:20:09.449
<v Jonathan>So we assess the need for additional data
if necessary or potentially higher

308
00:20:09.449 --> 00:20:10.510
<v Jonathan>processing of data.

309
00:20:11.010 --> 00:20:15.170
<v Jonathan>We look at who's using it and the adoption
factor, you know, it doesn't matter how

310
00:20:15.170 --> 00:20:19.770
<v Jonathan>good your system is, if it's not being
used, it's a, it's not a good thing.

311
00:20:19.869 --> 00:20:23.050
<v Jonathan>So we look at who's using the application
and making sure that we are getting the

312
00:20:23.050 --> 00:20:24.380
<v Jonathan>adoption from the users.

313
00:20:25.079 --> 00:20:28.290
<v Jonathan>Um, we also look at the success that's
been achieved.

314
00:20:28.530 --> 00:20:34.089
<v Jonathan>And we have a process of documenting these
success because what we find is in any

315
00:20:34.089 --> 00:20:35.949
<v Jonathan>project, you'll have your project team.

316
00:20:36.859 --> 00:20:42.180
<v Jonathan>And, uh, the project team may know exactly
what's happening, but they need to be the

317
00:20:42.180 --> 00:20:48.420
<v Jonathan>internal, um, uh, success distribution
channel.

318
00:20:48.859 --> 00:20:52.699
<v Jonathan>They need to make sure that they are
distributing the wins internally so that they

319
00:20:52.699 --> 00:20:57.339
<v Jonathan>can get wider buy-in and they can look at
scaling the project, um, and having it

320
00:20:57.339 --> 00:20:58.780
<v Jonathan>successful throughout an entire plant.

321
00:20:59.459 --> 00:21:04.890
<v Jonathan>So by following that process, we cover
from initial investigations all the way

322
00:21:04.890 --> 00:21:08.939
<v Jonathan>through to success and then that feeds
back into the scale.

323
00:21:09.260 --> 00:21:13.579
<v Jonathan>So we'll do that in for the rest of the
plants or for a new plant, you know, we

324
00:21:13.579 --> 00:21:17.020
<v Jonathan>start the process again until we're
looking at a global deployment.

325
00:21:18.839 --> 00:21:21.449
<v James>I mean, yeah, you, you've laid, I think
you've summarized it very well there.

326
00:21:21.500 --> 00:21:25.680
<v James>You've laid it out, seems very clear, but
like Rakesh, for someone who's going to be

327
00:21:25.680 --> 00:21:30.130
<v James>doing this for the first time, you know,
it could probably be quite daunting,

328
00:21:30.209 --> 00:21:30.859
<v James>overwhelming.

329
00:21:31.170 --> 00:21:33.910
<v James>What kind of support is on offer to, to
help the customer?

330
00:21:35.030 --> 00:21:39.670
<v Rakesh>Oh, yes, I mean, uh, being in the I mean,
Siemens in the Middle East is pretty close

331
00:21:39.670 --> 00:21:44.310
<v Rakesh>to the customers and, uh, in a solution
like PDM there's a lot of handholding that's

332
00:21:44.310 --> 00:21:49.469
<v Rakesh>needed during the initial phase, you know,
especially design deployment and so

333
00:21:49.469 --> 00:21:53.550
<v Rakesh>Siemens right from the beginning, right
from the consultancy phase, the design and

334
00:21:53.550 --> 00:21:58.030
<v Rakesh>deployment phase, the life cycle support
phase plays a very important role in, in

335
00:21:58.030 --> 00:22:01.589
<v Rakesh>actually guiding the customer, uh, towards
this PDM journey.

336
00:22:02.689 --> 00:22:06.849
<v Rakesh>Of course, not to mention there are a lot
of challenges that come up with, uh, with

337
00:22:06.849 --> 00:22:08.930
<v Rakesh>solutions that are adopted on the cloud.

338
00:22:08.979 --> 00:22:13.939
<v Rakesh>I mean, for example, data governance and
cyber security so we do have a team of

339
00:22:13.939 --> 00:22:18.290
<v Rakesh>network specialists, uh, cyber security uh
specialists that actually also guide the

340
00:22:18.290 --> 00:22:22.939
<v Rakesh>customer towards his compliance
requirements in terms of his network integrity

341
00:22:22.939 --> 00:22:28.180
<v Rakesh>requirements, uh, because, uh, I mean it
plays a very important role in the success

342
00:22:28.180 --> 00:22:29.239
<v Rakesh>of such projects.

343
00:22:30.040 --> 00:22:30.050
<v Jonathan>Yeah.

344
00:22:30.890 --> 00:22:35.680
<v Jonathan>And just, just to add on to that, Rakesh,
um, as you know, I've done, uh, quite a

345
00:22:35.680 --> 00:22:38.859
<v Jonathan>bit of training with the engineers in the
Middle East from Siemens.

346
00:22:39.199 --> 00:22:44.640
<v Jonathan>Uh, we in fact have some engineers who are
preparing for a site assessment, you

347
00:22:44.640 --> 00:22:49.239
<v Jonathan>know, the in-depth investigations with uh
food and beverage customer, uh, starting

348
00:22:49.239 --> 00:22:50.959
<v Jonathan>with, uh, a factory in Dubai.

349
00:22:51.369 --> 00:22:56.819
<v Jonathan>So there is local support and local
expertise ready to, to guide you through the

350
00:22:56.819 --> 00:22:59.839
<v Jonathan>process and guide you through to success
available now.

351
00:23:01.579 --> 00:23:05.459
<v Rakesh>And we're doing this from some of our key
regions and key countries in the region

352
00:23:05.459 --> 00:23:07.979
<v Rakesh>such as UAE, Saudi Arabia, Egypt.

353
00:23:08.060 --> 00:23:12.760
<v Rakesh>So we're trying to really base our
expertise across the regions to get them as close

354
00:23:12.760 --> 00:23:15.819
<v Rakesh>as possible uh to respective end users in
the Middle East region.

355
00:23:17.119 --> 00:23:17.130
<v James>Right.

356
00:23:18.040 --> 00:23:19.920
<v James>I mean, look, you, it's a very compelling
argument.

357
00:23:20.079 --> 00:23:23.880
<v James>It seems that you've got the process there
to like to, to help people on their 1st,

358
00:23:24.000 --> 00:23:27.300
<v James>1st time like installing or deploying
predictive maintenance.

359
00:23:28.079 --> 00:23:31.829
<v James>But you know, Rakesh, you, you're talking
to customers, there must be like certain

360
00:23:31.829 --> 00:23:35.680
<v James>objections or obstacles or perhaps some
barriers that are stopping them from

361
00:23:35.680 --> 00:23:36.189
<v James>adopting it.

362
00:23:36.280 --> 00:23:39.310
<v James>What, what, what are these like main, main
challenges that you're seeing?

363
00:23:40.400 --> 00:23:45.239
<v Rakesh>I think if you look at the Middle East in
specific, um, all the Middle Eastern

364
00:23:45.239 --> 00:23:49.119
<v Rakesh>countries, at least the major ones, adopt
very stringent data privacy laws, yeah.

365
00:23:49.920 --> 00:23:54.530
<v Rakesh>So it makes compliance more challenging,
uh, and not to mention cloud adoption in

366
00:23:54.530 --> 00:23:57.689
<v Rakesh>the Middle East is is has been slower than
the rest of the world.

367
00:23:57.810 --> 00:24:02.369
<v Rakesh>Yeah, I'm talking about the West, and, uh,
but nevertheless, the situation is fast

368
00:24:02.369 --> 00:24:07.209
<v Rakesh>changing, you know, governments are
ambitious, uh, the ambitions are to diversify

369
00:24:07.209 --> 00:24:12.010
<v Rakesh>and digitalize their manufacturing sector,
the economies, and there's a growing

370
00:24:12.010 --> 00:24:14.469
<v Rakesh>awareness of, uh, cloud benefits.

371
00:24:15.729 --> 00:24:20.430
<v Rakesh>Now, this has accelerated the introduction
of policies for cybersecurity, for data

372
00:24:20.430 --> 00:24:22.040
<v Rakesh>governance, for data protection.

373
00:24:22.449 --> 00:24:26.369
<v Rakesh>Uh, there are very cloud specific policies
in the region, yeah, and regulations in

374
00:24:26.369 --> 00:24:26.689
<v Rakesh>the region.

375
00:24:26.770 --> 00:24:29.329
<v Rakesh>So this has helped regulate the entire
sector.

376
00:24:30.209 --> 00:24:33.119
<v Rakesh>Uh, not to mention the cloud, the cost of
cloud adoption.

377
00:24:33.739 --> 00:24:37.099
<v Rakesh>It wasn't the case in 2019 when we had the
first data center in Bahrain.

378
00:24:37.770 --> 00:24:39.280
<v Rakesh>Uh, things are much different today.

379
00:24:39.739 --> 00:24:44.900
<v Rakesh>Uh, increasing number of international
cloud service providers like AWS, Azure are

380
00:24:44.900 --> 00:24:48.699
<v Rakesh>in the region, and this has brought the
cost of cloud adoption much lower than what

381
00:24:48.699 --> 00:24:49.900
<v Rakesh>it was 5 years back.

382
00:24:50.300 --> 00:24:55.380
<v Rakesh>So it's made it more affordable, more
easier for our customers, uh, to adopt cloud

383
00:24:55.380 --> 00:24:58.000
<v Rakesh>for cloud adoption than it was 5 years
back.

384
00:24:58.609 --> 00:25:03.050
<v Rakesh>And uh not to mention, I mean we've
overcome challenges in PDM adoption like limited

385
00:25:03.050 --> 00:25:08.060
<v Rakesh>local expertise, the infrastructure, so
these teething challenges have been overcome

386
00:25:08.569 --> 00:25:13.209
<v Rakesh>and uh I think it's all a matter of time,
the training, uh, solutions, cultural

387
00:25:13.209 --> 00:25:15.930
<v Rakesh>alignment we can actually bring this
together with customers.

388
00:25:15.949 --> 00:25:21.930
<v Rakesh>So it's much better than what we were in
2020 and uh see a huge exponential growth

389
00:25:21.930 --> 00:25:23.530
<v Rakesh>in the sector in the coming years.

390
00:25:24.569 --> 00:25:25.469
<v James>Great, great.

391
00:25:25.849 --> 00:25:29.250
<v James>And, and Jonathan, like from, you know,
obviously, you know, we're talking about

392
00:25:29.250 --> 00:25:29.930
<v James>Sensai.

393
00:25:30.369 --> 00:25:34.770
<v James>So if you, if we're going to talk to our
customers, how would you say that that what

394
00:25:34.770 --> 00:25:39.560
<v James>Sens I can offer is, is a level above what
is out, what else is out there in the

395
00:25:39.560 --> 00:25:39.910
<v James>market?

396
00:25:42.770 --> 00:25:48.689
<v Jonathan>I guess there Well, there's many factors,
um, but I'm gonna split them into 21 is

397
00:25:48.689 --> 00:25:53.719
<v Jonathan>Sensai, the technology, the actual
application, and then the second factor is

398
00:25:53.719 --> 00:25:56.770
<v Jonathan>Siemens, what do we offer which is
different and above.

399
00:25:57.329 --> 00:26:02.109
<v Jonathan>So starting off with Sensai the
application, really it is an automated platform.

400
00:26:02.689 --> 00:26:09.599
<v Jonathan>So, The learning process, the
understanding, the recommendations are all automated.

401
00:26:10.060 --> 00:26:15.420
<v Jonathan>We have our Sensi co-pilot, which is
essentially a virtual reliability engineer,

402
00:26:15.900 --> 00:26:20.420
<v Jonathan>which uh large language models inside of
our environment, we're continuing to feed

403
00:26:20.420 --> 00:26:24.010
<v Jonathan>that with additional information around
condition monitoring, reliability and

404
00:26:24.010 --> 00:26:25.170
<v Jonathan>maintenance practices.

405
00:26:25.579 --> 00:26:30.500
<v Jonathan>So it's gonna, it's much better than just
your, your standard standard large

406
00:26:30.500 --> 00:26:31.280
<v Jonathan>language model.

407
00:26:31.900 --> 00:26:37.560
<v Jonathan>The customer can also then add in expert
knowledge in the form of documentation.

408
00:26:38.050 --> 00:26:41.900
<v Jonathan>So user manuals, maintenance manuals,
spare parts lists, which can all be

409
00:26:41.900 --> 00:26:46.969
<v Jonathan>interrogated and made the information made
available at any request in the

410
00:26:46.969 --> 00:26:47.180
<v Jonathan>application.

411
00:26:48.500 --> 00:26:54.589
<v Jonathan>Our application is not limited to only
rotating equipment, we aren't specialists in

412
00:26:54.589 --> 00:27:00.020
<v Jonathan>one form of data management like vibration
analysis for example, but really we, uh,

413
00:27:00.069 --> 00:27:04.430
<v Jonathan>the application for a single asset can
take in currents, torque, vibration,

414
00:27:04.550 --> 00:27:09.790
<v Jonathan>temperature, speed, flow, cycle time, and
a full range of other information to make

415
00:27:09.790 --> 00:27:14.969
<v Jonathan>informed decisions around, uh, degradation
and give you that those recommendations.

416
00:27:15.339 --> 00:27:20.630
<v Jonathan>So really, world-class, world-leading
predictive maintenance technology.

417
00:27:21.670 --> 00:27:26.829
<v Jonathan>Then from a Siemen's perspective, well, as
Rakesh said earlier, we can do the full

418
00:27:26.829 --> 00:27:27.349
<v Jonathan>stack.

419
00:27:27.790 --> 00:27:34.369
<v Jonathan>You know, our availability from sensors,
hardware, infrastructure, um,

420
00:27:34.430 --> 00:27:40.349
<v Jonathan>expertise, specialists who can come in and
guide you through means that we can do as

421
00:27:40.349 --> 00:27:42.489
<v Jonathan>little or as much as is necessary.

422
00:27:43.339 --> 00:27:48.140
<v Jonathan>So for customers who want to take full
control of their journey, well, you are

423
00:27:48.140 --> 00:27:51.040
<v Jonathan>guided by the specialists, you are guided
by us.

424
00:27:51.500 --> 00:27:55.739
<v Jonathan>For customers that don't have the time or
maybe even um don't have the, the skill

425
00:27:55.739 --> 00:27:56.680
<v Jonathan>sets on site.

426
00:27:57.459 --> 00:28:00.780
<v Jonathan>Don't worry about it, we can come and fill
those gaps 100%.

427
00:28:01.270 --> 00:28:06.510
<v Jonathan>So from start to finish, from top to
bottom, we cover the entire picture and as I

428
00:28:06.510 --> 00:28:09.349
<v Jonathan>said, it's not limited, it is very much
open, so.

429
00:28:10.280 --> 00:28:13.180
<v Jonathan>In my mind, those are the differentiators.

430
00:28:15.369 --> 00:28:19.079
<v Rakesh>Another one from a regional perspective
is, um, you know, we're a very multilingual

431
00:28:19.640 --> 00:28:20.170
<v Rakesh>region, yeah.

432
00:28:20.760 --> 00:28:24.880
<v Rakesh>So you go to a typical F&amp;B plant, you
will have, uh, operators speaking different

433
00:28:24.880 --> 00:28:27.780
<v Rakesh>languages, different cultures, not to
mention, and, uh.

434
00:28:28.310 --> 00:28:33.790
<v Rakesh>Integrating gen AI features like the
co-pilot in in our PDM solution has made it

435
00:28:33.790 --> 00:28:37.300
<v Rakesh>much more easier, you know, the, the
prompts and they could speak in any language,

436
00:28:37.310 --> 00:28:39.170
<v Rakesh>they could be prompted in any language.

437
00:28:39.630 --> 00:28:45.510
<v Rakesh>So, uh, that has made a complete paradigm
shift in terms of, uh, user experience on

438
00:28:45.510 --> 00:28:47.959
<v Rakesh>PDM platforms, especially in a region like
the Middle East.

439
00:28:48.750 --> 00:28:52.170
<v Jonathan>And Rakesh, on the multilingual factor and
the copilot.

440
00:28:54.140 --> 00:28:59.410
<v Jonathan>I was speaking with a customer a few
months ago and their OEM manuals were all in,

441
00:28:59.420 --> 00:29:05.060
<v Jonathan>um, uh, Mandarin, Chinese, and no one on
site could speak them, so no one knew what

442
00:29:05.060 --> 00:29:06.500
<v Jonathan>was inside of the manual.

443
00:29:07.099 --> 00:29:11.939
<v Jonathan>Whereas you're having a technology, you,
uh, the Sensai copilot, for example, it

444
00:29:11.939 --> 00:29:16.939
<v Jonathan>doesn't matter what language that, that
manual is in, we can put it in and then the

445
00:29:16.939 --> 00:29:19.920
<v Jonathan>user can interrogate that manual from any
language.

446
00:29:20.410 --> 00:29:24.660
<v Jonathan>You know, whether, yeah, whatever language
you speak and whatever language the

447
00:29:24.660 --> 00:29:27.699
<v Jonathan>manual is in, well, we converge them into,
yeah.

448
00:29:29.250 --> 00:29:30.709
<v Jonathan>easy to use platform.

449
00:29:33.319 --> 00:29:33.430
<v Jonathan>OK.

450
00:29:35.119 --> 00:29:35.640
<v James>Fantastic.

451
00:29:35.719 --> 00:29:38.839
<v James>Now, we are, I'm afraid, are coming to the
end of our time.

452
00:29:38.959 --> 00:29:42.880
<v James>So just before we close on the actual, um,
on the presentation or the discussion,

453
00:29:43.280 --> 00:29:44.920
<v James>maybe Rakesh, you can just start.

454
00:29:45.040 --> 00:29:48.589
<v James>How do you see, foresee the future of, uh,
predictive maintenance, uh, in the

455
00:29:48.589 --> 00:29:48.939
<v James>region?

456
00:29:50.579 --> 00:29:55.339
<v Rakesh>I think, um, predictive maintenance is
playing and will play a very important role

457
00:29:55.339 --> 00:29:58.579
<v Rakesh>in asset management in food and beverage
industries.

458
00:29:58.979 --> 00:30:02.770
<v Rakesh>I mean, uh, it's worth mentioning again
that, uh, food and beverage industry, uh,

459
00:30:02.780 --> 00:30:07.579
<v Rakesh>the F&amp;B manufacturing plays a very
critical role in the Middle East due to the

460
00:30:07.579 --> 00:30:11.459
<v Rakesh>factors I've already mentioned in terms of
food security, in terms of water

461
00:30:11.459 --> 00:30:17.219
<v Rakesh>scarcity, uh, I think up time and, uh,
productivity of these plants, it ends up

462
00:30:17.219 --> 00:30:20.050
<v Rakesh>being one of the most critical
infrastructure sectors in the UAE.

463
00:30:20.689 --> 00:30:27.310
<v Rakesh>So there's more and more pressure on uh
F&amp;B manufacturers uh to maintain uh up time

464
00:30:27.689 --> 00:30:30.489
<v Rakesh>and at the same time very strict quality
and safety standards.

465
00:30:30.569 --> 00:30:35.869
<v Rakesh>So, uh, altogether, uh, PDM will play a
very integral role in this and thanks to AI

466
00:30:36.010 --> 00:30:39.989
<v Rakesh>I think adopting PDM is much easier today
than it was in the past.

467
00:30:41.829 --> 00:30:45.329
<v James>And Jonathan, anything from your point of
view where you think, uh, the future of

468
00:30:45.869 --> 00:30:47.050
<v James>predictive maintenance lies?

469
00:30:49.170 --> 00:30:53.530
<v Jonathan>If we look at the rate of change in
technology these days, the rate of change just

470
00:30:53.530 --> 00:30:54.569
<v Jonathan>keeps on accelerating.

471
00:30:55.530 --> 00:30:58.660
<v Jonathan>Um, so it's only gonna get better.

472
00:30:59.219 --> 00:31:02.459
<v Jonathan>So there is definitely a future and it's,
it's a very bright future.

473
00:31:02.599 --> 00:31:06.400
<v Jonathan>However, what we have available today is
phenomenal.

474
00:31:06.819 --> 00:31:11.290
<v Jonathan>And you know, what I, I keep saying to our
customers, you know, why are you waiting?

475
00:31:11.579 --> 00:31:16.719
<v Jonathan>Why, why are we spending 68 months trying
to convince you where for 6 or 8 months,

476
00:31:16.739 --> 00:31:17.839
<v Jonathan>you could have been getting value.

477
00:31:18.329 --> 00:31:22.089
<v Jonathan>You could have been um having better
production, you could have been making these

478
00:31:22.089 --> 00:31:26.050
<v Jonathan>savings, you could have better maintenance
practices and efficiency.

479
00:31:26.569 --> 00:31:29.050
<v Jonathan>So why are you discussing this for six or
eight months?

480
00:31:29.170 --> 00:31:31.109
<v Jonathan>Let's get it in and start driving value.

481
00:31:31.609 --> 00:31:36.530
<v Jonathan>So it's not about the future of predictive
maintenance, it's about your future using

482
00:31:36.530 --> 00:31:37.540
<v Jonathan>predictive maintenance.

483
00:31:37.849 --> 00:31:39.430
<v Jonathan>Let's get that future happening now.

484
00:31:40.890 --> 00:31:42.260
<v James>Sounds good, sounds good.

485
00:31:42.660 --> 00:31:46.140
<v James>Well, unfortunately, we have come to the
end in terms of the, the discussion, but we

486
00:31:46.140 --> 00:31:47.869
<v James>have had a few questions come through.

487
00:31:47.979 --> 00:31:50.660
<v James>So if you've got time, we'll just go
through a couple of these questions.

488
00:31:50.819 --> 00:31:56.660
<v James>Um, so the first one is around How do we
determine if our plant is ready to move

489
00:31:56.660 --> 00:32:00.280
<v James>from condition monitoring to predictive
maintenance?

490
00:32:01.060 --> 00:32:02.359
<v James>How do you know when to make that shift?

491
00:32:03.910 --> 00:32:07.489
<v Jonathan>Um, well, I would say get in touch.

492
00:32:08.109 --> 00:32:13.270
<v Jonathan>Let us help and guide you because as I
mentioned earlier, there is no barrier, at

493
00:32:13.270 --> 00:32:16.449
<v Jonathan>least not anymore, to when you can start
predictive maintenance.

494
00:32:16.709 --> 00:32:19.910
<v Jonathan>If you don't have a suitable
infrastructure, we can help you with that.

495
00:32:20.229 --> 00:32:25.589
<v Jonathan>If it's the skill sets on site or um a
requirement for learning, we can assist with

496
00:32:25.589 --> 00:32:25.989
<v Jonathan>that.

497
00:32:26.430 --> 00:32:30.280
<v Jonathan>Uh, really it is about, do you have the
defined problem statement?

498
00:32:30.359 --> 00:32:31.790
<v Jonathan>What is it that you're trying to solve?

499
00:32:32.209 --> 00:32:35.390
<v Jonathan>And are you ready for a journey because it
is a journey.

500
00:32:35.400 --> 00:32:39.979
<v Jonathan>It does take time and effort to implement,
but the benefits are huge.

501
00:32:40.640 --> 00:32:46.400
<v Jonathan>So we can definitely guide you, um,
locally to, uh, predictive maintenance from

502
00:32:46.400 --> 00:32:47.760
<v Jonathan>whatever starting point you're at.

503
00:32:49.609 --> 00:32:50.160
<v James>OK.

504
00:32:50.459 --> 00:32:54.010
<v James>Rakesh, anything, have you got anything to
add from a local point of view of like

505
00:32:54.010 --> 00:32:57.810
<v James>maybe some of the barriers when, um,
customers are asking about, you know, we do

506
00:32:57.810 --> 00:33:00.670
<v James>our, we do our own monitoring, we don't
need the predictive maintenance.

507
00:33:01.150 --> 00:33:05.069
<v Rakesh>Yeah, uh, to be frank, I just resonate
what, uh, Jonathan said, and in fact, we've

508
00:33:05.069 --> 00:33:09.750
<v Rakesh>actually successfully started the journey
with quite a few customers, and, uh, it's

509
00:33:09.750 --> 00:33:14.219
<v Rakesh>been so positive so far, and, um, we can,
we can guide them through, we can bring in

510
00:33:14.219 --> 00:33:19.250
<v Rakesh>our expertise, our, uh, the best
practices, uh, in the industry and help them, uh,

511
00:33:19.260 --> 00:33:20.069
<v Rakesh>reach their goals.

512
00:33:20.849 --> 00:33:21.520
<v James>Right, right.

513
00:33:22.130 --> 00:33:26.569
<v James>Now we've had two similar questions, um,
so I'll just kind of combine them, and, but

514
00:33:26.569 --> 00:33:32.569
<v James>it is about some of, since I really like
large scale manufacturers, you know, or can

515
00:33:32.569 --> 00:33:37.369
<v James>it be applied to much smaller, smaller
entities as well who might have more, more

516
00:33:37.369 --> 00:33:38.670
<v James>limited resources.

517
00:33:38.849 --> 00:33:39.170
<v Jonathan>Yeah.

518
00:33:41.119 --> 00:33:43.520
<v Jonathan>There are a range of starting points.

519
00:33:43.800 --> 00:33:50.479
<v Jonathan>So, you know, historically our focus has
been on much larger, um, companies,

520
00:33:50.560 --> 00:33:54.400
<v Jonathan>facilities, uh, where there is that, that
option for scale.

521
00:33:54.520 --> 00:34:00.079
<v Jonathan>However, working with our regional
colleagues, we have found multiple different

522
00:34:00.079 --> 00:34:05.660
<v Jonathan>options, packages, whether it's a An
initial deployment or um a starter pack or

523
00:34:05.660 --> 00:34:09.820
<v Jonathan>whatever it may be that can help smaller
companies still get the benefit of

524
00:34:09.820 --> 00:34:13.959
<v Jonathan>predictive maintenance even though they
don't have massive facilities and thousands

525
00:34:13.959 --> 00:34:14.729
<v Jonathan>of employees.

526
00:34:15.260 --> 00:34:21.219
<v Jonathan>So yes, we do have options available and
we can work with you to structure that

527
00:34:21.219 --> 00:34:24.560
<v Jonathan>offering so that it's uh best suited for
your environment.

528
00:34:25.139 --> 00:34:25.560
<v James>OK.

529
00:34:26.320 --> 00:34:30.280
<v James>And this question kind of, I suppose
you've already mentioned earlier, Jonathan,

530
00:34:30.350 --> 00:34:35.520
<v James>like one of the your case examples about
the ROI like you know, um, that one of

531
00:34:35.520 --> 00:34:38.959
<v James>your, one of your customers did see an
almost like an immediate ROI.

532
00:34:39.898 --> 00:34:43.178
<v James>Is that common, is that, is that the usual
timeline or what or what is the usual

533
00:34:43.178 --> 00:34:46.259
<v James>timeline, would you say, would you
recommend to a customer, you're gonna see your

534
00:34:46.259 --> 00:34:48.888
<v James>ROI within this type of timeframe?

535
00:34:49.339 --> 00:34:50.678
<v Jonathan>Yeah, um.

536
00:34:52.159 --> 00:34:54.520
<v Jonathan>That is how long is a piece of string
question, right?

537
00:34:54.600 --> 00:34:55.959
<v Jonathan>You can never be certain.

538
00:34:56.080 --> 00:34:58.760
<v Jonathan>However, We target the value.

539
00:34:59.010 --> 00:35:02.449
<v Jonathan>So as part of our initial investigations,
we're going to look for the areas that

540
00:35:02.449 --> 00:35:07.090
<v Jonathan>have the highest maintenance activity, the
least amount of reliability, and that's

541
00:35:07.090 --> 00:35:08.810
<v Jonathan>where we will start our initial
deployment.

542
00:35:09.370 --> 00:35:14.229
<v Jonathan>So the chances of seeing something
interesting, the chances of getting that ROI are

543
00:35:14.850 --> 00:35:17.840
<v Jonathan>increased because we're targeting those
areas that will bring that.

544
00:35:18.889 --> 00:35:24.030
<v Jonathan>Um, so we try and set it up so that we are
going to bring value in that ROI.

545
00:35:24.770 --> 00:35:27.189
<v Jonathan>How quickly or what is the typical
timeline?

546
00:35:28.159 --> 00:35:32.060
<v Jonathan>There have been many cases where that ROI
has happened within weeks.

547
00:35:32.790 --> 00:35:37.280
<v Jonathan>For weeks from, uh, on boarding, from it
being ready, you now have a full ROI.

548
00:35:38.239 --> 00:35:40.909
<v Jonathan>Um, in other cases, it is months.

549
00:35:41.080 --> 00:35:44.000
<v Jonathan>It could take, you know, anywhere between
6 to 8 months.

550
00:35:44.780 --> 00:35:46.159
<v Jonathan>It really does depend.

551
00:35:47.379 --> 00:35:51.419
<v Jonathan>If we're monitoring, let's say 100 assets,
what are the chances that one of them is

552
00:35:51.419 --> 00:35:52.600
<v Jonathan>going to degrade and fail?

553
00:35:53.790 --> 00:35:55.229
<v Jonathan>Could be high, could be low.

554
00:35:55.459 --> 00:35:58.709
<v Jonathan>We could choose the most unreliable thing
and nothing happens for six months.

555
00:35:59.530 --> 00:36:03.810
<v Jonathan>It is really hard to say, but our process
is to try and target those areas that are

556
00:36:03.810 --> 00:36:04.909
<v Jonathan>gonna drive value.

557
00:36:05.250 --> 00:36:10.260
<v Jonathan>We have a way of projecting what the ROI
would be within the 1st 12 months.

558
00:36:10.649 --> 00:36:16.530
<v Jonathan>So our aim is to, to make sure that we hit
that ROI a few times over within the 1st

559
00:36:16.530 --> 00:36:17.389
<v Jonathan>12 months.

560
00:36:17.850 --> 00:36:20.149
<v Jonathan>Um, so that's, that's how we go about it.

561
00:36:21.280 --> 00:36:25.159
<v James>OK, and if I'm just sticking with the,
with time frames here as well, what is the

562
00:36:25.159 --> 00:36:29.280
<v James>time frame generally, would you say for
like onboarding and implementation to you

563
00:36:29.280 --> 00:36:33.899
<v James>would say like, uh, uh, your predicted
maintenance is actually fully up and running.

564
00:36:34.439 --> 00:36:40.159
<v Jonathan>Again, it really does depend on the
readiness, the maturity of the environment when

565
00:36:40.159 --> 00:36:41.260
<v Jonathan>we get in there.

566
00:36:41.679 --> 00:36:44.840
<v Jonathan>Uh, things like system integration does
take time.

567
00:36:45.389 --> 00:36:50.550
<v Jonathan>Uh, factors like is the customer driving
the activity or is Siemens driving the

568
00:36:50.550 --> 00:36:55.169
<v Jonathan>activity, you know, those do have um,
different times attached to them.

569
00:36:55.909 --> 00:37:02.179
<v Jonathan>Typically though, we would expect to have
data onboarded within the 1st 3 months.

570
00:37:02.709 --> 00:37:08.389
<v Jonathan>So we want to get the implementation
integration sorted so that by the 3 month

571
00:37:08.389 --> 00:37:10.719
<v Jonathan>period, the application is ready to use.

572
00:37:11.419 --> 00:37:16.659
<v Jonathan>We have done it much sooner than that
previously where everything was in place and

573
00:37:16.659 --> 00:37:21.500
<v Jonathan>we have had projects that were delayed
because of, let's say there were factors like

574
00:37:21.500 --> 00:37:26.300
<v Jonathan>system integration which was, you know,
um, harder to overcome than the customer

575
00:37:26.300 --> 00:37:26.719
<v Jonathan>thought.

576
00:37:27.260 --> 00:37:31.979
<v Jonathan>But your, your, your aim is 3 months, 3
months from the moment we start the project

577
00:37:31.979 --> 00:37:33.860
<v Jonathan>to having full use of the application.

578
00:37:34.989 --> 00:37:36.629
<v James>OK, that's good, that's good.

579
00:37:36.909 --> 00:37:40.550
<v James>And then we've got one question that's
just coming through actually onto the chat is

580
00:37:40.550 --> 00:37:45.350
<v James>actually, do you have a model or maybe,
uh, yeah, a model that can be used to show

581
00:37:45.350 --> 00:37:48.419
<v James>the benefits and something that you could
probably share with the, with the wider

582
00:37:48.419 --> 00:37:48.889
<v James>audience.

583
00:37:50.600 --> 00:37:53.629
<v Jonathan>Um, a model, I'm not too sure.

584
00:37:54.000 --> 00:37:56.179
<v James>Maybe like a case study or something,
maybe.

585
00:37:58.090 --> 00:38:01.590
<v Jonathan>Well, we have defined benefits.

586
00:38:02.209 --> 00:38:03.729
<v Jonathan>Well, absolutely.

587
00:38:04.090 --> 00:38:08.350
<v Jonathan>We have in the application, um, a way of
recording the benefits.

588
00:38:08.689 --> 00:38:14.290
<v Jonathan>So this is, um, recording of maintenance
activities, notification activities,

589
00:38:14.489 --> 00:38:20.209
<v Jonathan>specific KPIs, downtime avoided, spare
parts saved, labor saved that we can start to

590
00:38:20.209 --> 00:38:22.070
<v Jonathan>record the benefits in the application.

591
00:38:23.000 --> 00:38:29.520
<v Jonathan>We have a series of templates and, um,
calculation, uh, calculations that we can do

592
00:38:29.520 --> 00:38:33.179
<v Jonathan>to project what the benefit will be or
your return of investment will be.

593
00:38:33.909 --> 00:38:38.139
<v Jonathan>Um, yeah, I'm not too sure that's the, the
word model which is throwing me out,

594
00:38:39.530 --> 00:38:45.389
<v Jonathan>yeah, yeah, but, um, if you would like to
know more, please get in touch and we can

595
00:38:45.389 --> 00:38:48.449
<v Jonathan>discuss this and show you everything, um,
yeah, one on one.

596
00:38:49.020 --> 00:38:52.709
<v James>We can have a bit more detailed
conversation, right, OK.

597
00:38:53.090 --> 00:38:56.620
<v James>Um, I think those are most of the
questions that have come through now.

598
00:38:56.850 --> 00:39:00.050
<v James>Um, gentlemen, thank you very much.

599
00:39:00.409 --> 00:39:01.610
<v James>Really appreciate your time.

600
00:39:01.810 --> 00:39:05.050
<v James>The only other question that's probably
come through, which I can answer is yes,

601
00:39:05.169 --> 00:39:07.830
<v James>after this session, the recording will be
available.

602
00:39:08.169 --> 00:39:09.570
<v James>It will be sent to your email.

603
00:39:10.209 --> 00:39:11.639
<v James>So we can close on that now.

604
00:39:11.889 --> 00:39:16.639
<v James>Um, of course, as Jonathan said, please
feel free to get in touch if you do have any

605
00:39:16.639 --> 00:39:17.629
<v James>specific questions.

606
00:39:18.010 --> 00:39:22.010
<v James>Um, and then in the meantime, so thank you
for our speakers, Jonathan to Rakesh.

607
00:39:22.379 --> 00:39:26.590
<v James>Thank you to our audience, thank you for
your questions, and we'll be in touch again

608
00:39:26.840 --> 00:39:28.870
<v James>for our next session on Sensei.

609
00:39:29.780 --> 00:39:30.689
<v James>Thank you very much.

610
00:39:32.270 --> 00:39:37.229
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

611
00:39:37.229 --> 00:39:40.750
<v Speaker 2>Sensi predictive maintenance at
Siemens.com.
