WEBVTT
Language: en-US

1
00:00:25.389 --> 00:00:29.170
<v Speaker 1>Welcome to the trend detection podcast
powered by Siemens.

2
00:00:29.709 --> 00:00:30.569
<v Speaker 2>Hello everyone.

3
00:00:31.680 --> 00:00:36.840
<v Speaker 2>And thank you, Alex, thank you Simon, for
joining this conversation about ArA

4
00:00:36.840 --> 00:00:42.840
<v Speaker 2>Continental and the data-driven
manufacturing transformation and

5
00:00:42.840 --> 00:00:48.979
<v Speaker 2>how technology people and insights can
help organizations to

6
00:00:48.979 --> 00:00:50.439
<v Speaker 2>enhance operations.

7
00:00:51.279 --> 00:00:55.509
<v Speaker 2>But why don't we watch this clip before we
start this conversation?

8
00:00:56.319 --> 00:01:02.090
<v Speaker 3>Arca Continental is the 2nd largest
Coca-Cola bottling company in Latin America and

9
00:01:02.090 --> 00:01:04.110
<v Speaker 3>one of the most important in the world.

10
00:01:04.379 --> 00:01:08.089
<v Speaker 3>We operate in the US, Mexico, Ecuador,
Peru, and Argentina.

11
00:01:08.250 --> 00:01:13.150
<v Speaker 3>As you can imagine, having 45
manufacturing sites around these 5 different countries

12
00:01:13.290 --> 00:01:18.110
<v Speaker 3>involve having also different maturities
in terms of technology and data management.

13
00:01:18.330 --> 00:01:22.930
<v Speaker 3>There's a lot of people to be impacted in
terms of the implementation of digital

14
00:01:22.930 --> 00:01:24.250
<v Speaker 3>transformation use cases.

15
00:01:24.694 --> 00:01:30.235
<v Speaker 3>So understanding the impact we have on
humans that are still part of this loop, it,

16
00:01:30.415 --> 00:01:32.055
<v Speaker 3>it's pretty important.

17
00:01:32.214 --> 00:01:37.014
<v Speaker 3>So we try to have one excellent center in
terms of digital transformation in at

18
00:01:37.014 --> 00:01:42.055
<v Speaker 3>least one manufacturing site of each
country where we operate that allows more

19
00:01:42.055 --> 00:01:48.614
<v Speaker 3>people to be involved and have like a
local geographically located example, you

20
00:01:48.614 --> 00:01:52.754
<v Speaker 3>know, so you can just go and experience
what we mean with digital transformation.

21
00:01:53.214 --> 00:01:53.694
<v Speaker 2>Thank you.

22
00:01:54.800 --> 00:01:55.309
<v Speaker 2>Excellent.

23
00:01:55.489 --> 00:01:59.089
<v Speaker 2>Well, Alex, my first question is for you.

24
00:01:59.519 --> 00:02:04.809
<v Speaker 2>Do you remember when we first approached
ArA Continental, what were some of the

25
00:02:04.809 --> 00:02:07.709
<v Speaker 2>challenges that they were facing at that
time?

26
00:02:08.369 --> 00:02:09.350
<v Alex>Yes, absolutely.

27
00:02:09.649 --> 00:02:14.850
<v Alex>So it is actually we had a meeting with
ArA Continental when their journey started

28
00:02:14.850 --> 00:02:15.889
<v Alex>here in Hanover.

29
00:02:15.929 --> 00:02:20.929
<v Alex>It was a couple of years ago and they were
actually facing their challenges which

30
00:02:20.929 --> 00:02:23.610
<v Alex>are very similar to what a lot of
manufacturers see.

31
00:02:23.649 --> 00:02:28.750
<v Alex>It's the Traditional productivity
improvements were leveling out, so they had to

32
00:02:28.750 --> 00:02:33.940
<v Alex>actually use new technology to actually
get there to slope up again.

33
00:02:34.320 --> 00:02:38.559
<v Alex>Another topic was in some areas they were
concerned about that they were not

34
00:02:38.559 --> 00:02:43.000
<v Alex>generating the yield which they wanted to
have, so higher spread rates than it was

35
00:02:43.000 --> 00:02:44.740
<v Alex>actually desirable.

36
00:02:45.080 --> 00:02:49.759
<v Alex>And then a very interesting one is, is
very specifically, so when they of course are

37
00:02:49.759 --> 00:02:51.669
<v Alex>filling their products like Coke, etc.

38
00:02:52.300 --> 00:02:59.289
<v Alex>And they track very closely now the cost
per case and understand what is actually

39
00:02:59.289 --> 00:03:04.250
<v Alex>driving these numbers and that was also a
major challenge for them having this under

40
00:03:04.250 --> 00:03:08.669
<v Alex>control to match this with the rather
tight margins which they sometimes get there

41
00:03:08.929 --> 00:03:11.949
<v Alex>so that they can actually do this as a
profitable business.

42
00:03:12.750 --> 00:03:13.149
<v Speaker 2>Interesting.

43
00:03:14.000 --> 00:03:19.389
<v Speaker 2>So when those challenges were clear, do
you remember how did they make that

44
00:03:19.389 --> 00:03:19.779
<v Speaker 2>decision?

45
00:03:20.199 --> 00:03:24.119
<v Speaker 2>Where did they start instead of trying to
tackle everything at once?

46
00:03:24.360 --> 00:03:25.020
<v Alex>Yes, so.

47
00:03:25.869 --> 00:03:29.580
<v Alex>Very clearly they started with to get in
first basic transparency.

48
00:03:29.710 --> 00:03:34.190
<v Alex>Do they actually know where do they have
to go to make the changes to actually get

49
00:03:34.190 --> 00:03:35.520
<v Alex>also then the reward for they did.

50
00:03:35.589 --> 00:03:40.470
<v Alex>So what they did is the main use case for
them at the beginning was OEE for getting

51
00:03:40.470 --> 00:03:46.470
<v Alex>this transparency where is actually the
equipment which they have utilized to the

52
00:03:46.470 --> 00:03:51.110
<v Alex>best and where is there room for
improvement and in these cases what are actually

53
00:03:51.110 --> 00:03:53.860
<v Alex>the main loss drivers and then.

54
00:03:54.330 --> 00:03:58.300
<v Alex>On top of that, they already knew at that
point that they need to manage their

55
00:03:58.300 --> 00:04:03.160
<v Alex>energy costs more closely, and so they
introduced building on our energy manager

56
00:04:03.160 --> 00:04:07.179
<v Alex>solution, energy management system based
on ISO 50,0001.

57
00:04:07.470 --> 00:04:08.600
<v Alex>That's the starting point.

58
00:04:08.660 --> 00:04:11.410
<v Alex>And as they learn then where are the lost
drivers.

59
00:04:11.559 --> 00:04:17.309
<v Alex>For example, which failure modes cause
downtimes, what are the main reasons for

60
00:04:17.309 --> 00:04:19.549
<v Alex>scrapping parts of their production?

61
00:04:19.910 --> 00:04:24.700
<v Alex>That is then when they were able to go to
the next stage and then adopt topics like

62
00:04:24.700 --> 00:04:27.730
<v Alex>predictive quality or predictive
maintenance.

63
00:04:28.350 --> 00:04:28.670
<v Speaker 2>Right.

64
00:04:29.619 --> 00:04:32.000
<v Speaker 2>So now, Simon, my question is for you.

65
00:04:32.619 --> 00:04:39.220
<v Speaker 2>What role did predictive maintenance play
at Arca Continental to achieve their goals

66
00:04:39.220 --> 00:04:40.799
<v Speaker 2>for digital transformation?

67
00:04:41.709 --> 00:04:45.989
<v Speaker 5>Yeah, and, and predictive maintenance is,
is obviously is a big buzzword, and it's

68
00:04:45.989 --> 00:04:51.109
<v Speaker 5>also probably one of the ones that's the
hardest to adopt and make successful with a

69
00:04:51.109 --> 00:04:51.690
<v Speaker 5>customer.

70
00:04:52.269 --> 00:04:56.549
<v Speaker 5>And we always know there's, there's
certain key points we look at for a customer to

71
00:04:56.549 --> 00:05:02.250
<v Speaker 5>see, is it going to be successful, and the
key one for that is a cultural maturity.

72
00:05:03.029 --> 00:05:08.149
<v Speaker 5>Support from the shop floor to the, to the
top floor, and Archi Continental very

73
00:05:08.149 --> 00:05:09.940
<v Speaker 5>much had this in spades, right?

74
00:05:10.190 --> 00:05:13.950
<v Speaker 5>And we very much look for are they already
on a digital transformation journey,

75
00:05:14.230 --> 00:05:18.179
<v Speaker 5>because if they're not, and their first
entry point is predictive maintenance,

76
00:05:18.470 --> 00:05:22.510
<v Speaker 5>that's quite a tough ask, right, cause if
they are not even doing OEE transparency

77
00:05:22.510 --> 00:05:27.160
<v Speaker 5>yet, how are you gonna measure what
predictive maintenance is, is achieving, right?

78
00:05:27.549 --> 00:05:31.309
<v Speaker 5>So, once they had initial success with
transparency use case.

79
00:05:31.790 --> 00:05:36.750
<v Speaker 5>Then we started deploying Sensi predictive
maintenance, which is a machine and

80
00:05:36.750 --> 00:05:42.070
<v Speaker 5>vendor agnostic, highly scalable
predictive maintenance solution, which we deployed

81
00:05:42.070 --> 00:05:42.649
<v Speaker 5>with them.

82
00:05:42.989 --> 00:05:47.589
<v Speaker 5>And because they had that great sort of
strategic framework to deploy this and a lot

83
00:05:47.589 --> 00:05:52.649
<v Speaker 5>of buy-in across the organization, you can
actually get successfully quickly, and,

84
00:05:52.700 --> 00:05:54.589
<v Speaker 5>you know, within 6 days of going live.

85
00:05:55.160 --> 00:06:00.440
<v Speaker 5>They save 13 hours of downtime on a filler
labeler machine, right, and you can

86
00:06:00.440 --> 00:06:05.239
<v Speaker 5>imagine over 13 hours, that's a lot of
Coca-Cola, that's not being produced, right,

87
00:06:05.359 --> 00:06:10.130
<v Speaker 5>so, it's not always that quick, but with
Alca Continental, because they had that,

88
00:06:10.239 --> 00:06:14.799
<v Speaker 5>that right mindset and strategy across the
organization, it's been really successful

89
00:06:14.799 --> 00:06:16.799
<v Speaker 5>to help them along their digital journey.

90
00:06:17.799 --> 00:06:18.299
<v Speaker 2>Excellent.

91
00:06:18.880 --> 00:06:21.019
<v Speaker 2>So this question is for both of you.

92
00:06:21.720 --> 00:06:26.579
<v Speaker 2>So how does insights of and predictive
maintenance work together to achieve

93
00:06:27.399 --> 00:06:30.589
<v Speaker 2>operation transparency and predictive
insights?

94
00:06:30.760 --> 00:06:32.839
<v Speaker 5>Yeah, well, I, I, I can start, Alex.

95
00:06:33.119 --> 00:06:38.040
<v Speaker 5>Predictive maintenance never exists in
isolation, right, it's, it's always part of a

96
00:06:38.040 --> 00:06:42.299
<v Speaker 5>broader ecosystem of other products, other
maintenance workflows.

97
00:06:42.760 --> 00:06:49.079
<v Speaker 5>Enterprise workflows, and also often a
customer will start with a certain use case,

98
00:06:49.160 --> 00:06:54.579
<v Speaker 5>maybe transparency or quality, and then
move to like predictive maintenance.

99
00:06:54.880 --> 00:06:58.799
<v Speaker 5>And for us, Insights-Hub provides that
backbone, that's where we store all our data,

100
00:06:58.850 --> 00:07:04.100
<v Speaker 5>all our context, and we try to align
across that to give a single experience to the

101
00:07:04.100 --> 00:07:04.480
<v Speaker 5>user.

102
00:07:04.720 --> 00:07:08.170
<v Speaker 5>So, a bit like Microsoft Office, right,
you can start with Word.

103
00:07:08.679 --> 00:07:12.390
<v Speaker 5>That works well, then you move to
PowerPoint and you want the experience to be

104
00:07:12.390 --> 00:07:16.600
<v Speaker 5>similar, and you want the data to be kind
of interoperable and things like that.

105
00:07:16.709 --> 00:07:19.399
<v Speaker 5>So that's, that's what I see ins Shub as
as being.

106
00:07:20.760 --> 00:07:24.679
<v Alex>I think that's already a very good wrap up
and what comes on top of it is, of

107
00:07:24.679 --> 00:07:28.859
<v Alex>course, if you moved into more use cases,
you still have the same data foundation

108
00:07:28.859 --> 00:07:30.989
<v Alex>and that's an important piece for
consistency.

109
00:07:31.399 --> 00:07:36.609
<v Alex>Another topic is also if you do this
basically on the same platform set up, it's

110
00:07:36.609 --> 00:07:36.880
<v Alex>the.

111
00:07:37.524 --> 00:07:42.244
<v Alex>which you still have to build with CMMS on
the one side, MES on another side, kind

112
00:07:42.244 --> 00:07:46.885
<v Alex>of, you do this once and then it's
basically working similarly for the all the use

113
00:07:46.885 --> 00:07:52.165
<v Alex>cases, taking a lot of extra effort out as
you're expanding with adopting new use

114
00:07:52.165 --> 00:07:55.404
<v Alex>cases and addressing additional production
challenges.

115
00:07:55.765 --> 00:07:55.894
<v Alex>Well,

116
00:07:56.364 --> 00:08:00.704
<v Speaker 2>you kind of have been with Arca still in
the very beginning in this journey.

117
00:08:01.239 --> 00:08:07.089
<v Speaker 2>Do you remember what were some of the
early wins that the team made them feel like

118
00:08:07.089 --> 00:08:08.390
<v Speaker 2>they were on the right path?

119
00:08:09.089 --> 00:08:09.649
<v Alex>Exactly.

120
00:08:10.089 --> 00:08:14.720
<v Alex>So when they, when they started, as
mentioned, the focus was a lot on transparency,

121
00:08:14.769 --> 00:08:19.010
<v Alex>but that doesn't mean that it's just
information and then nothing tangible comes

122
00:08:19.010 --> 00:08:19.260
<v Alex>out.

123
00:08:19.359 --> 00:08:24.619
<v Alex>I mean, one of the elements was that The
cost per case could be managed more

124
00:08:24.619 --> 00:08:30.140
<v Alex>effectively and they could reduce the cost
position there, which of course directly

125
00:08:30.140 --> 00:08:32.250
<v Alex>turns into additional profitability.

126
00:08:32.609 --> 00:08:39.000
<v Alex>They were able to increase OEE by 3%
points and if you compare this basically to the

127
00:08:39.260 --> 00:08:43.679
<v Alex>large setup which we saw in the in the
early video, this is actually a significant

128
00:08:44.260 --> 00:08:44.650
<v Alex>additional.

129
00:08:44.710 --> 00:08:49.030
<v Alex>Output which you can then sell on the
market and then the last step is also that

130
00:08:49.030 --> 00:08:53.090
<v Alex>with more knowledge about what is actually
causing disruptions, they could also

131
00:08:53.630 --> 00:08:58.549
<v Alex>increase the stability of the processes
and then of course now with the adoption of

132
00:08:58.549 --> 00:09:04.309
<v Alex>the predictive use cases we are now
actually adding now towards this and uh yeah and

133
00:09:04.309 --> 00:09:09.469
<v Alex>it's, it's actually a really good journey
and uh we hope that ArA can actually keep

134
00:09:09.469 --> 00:09:10.109
<v Alex>this pace.

135
00:09:10.960 --> 00:09:11.640
<v Speaker 2>Excellent.

136
00:09:11.929 --> 00:09:18.210
<v Speaker 2>Well, Simon, one of my last questions
about people and the partnership between ARA

137
00:09:18.210 --> 00:09:19.679
<v Speaker 2>and Siemens.

138
00:09:19.969 --> 00:09:25.590
<v Speaker 2>How is the collaboration and what, how has
it been a factor of the success?

139
00:09:25.890 --> 00:09:30.090
<v Speaker 5>Yeah, and, and, and as, as I hinted
earlier, adopting predictive maintenance

140
00:09:30.090 --> 00:09:34.950
<v Speaker 5>requires a real cultural shift, and we've
been doing this now for over 10 years, and

141
00:09:34.950 --> 00:09:37.289
<v Speaker 5>we have stories that are positive and
negative.

142
00:09:37.960 --> 00:09:42.849
<v Speaker 5>And you know, normal maintenance workflow
is you're reacting to machines failing,

143
00:09:43.320 --> 00:09:47.229
<v Speaker 5>and you're extremely busy doing that, and
at times you'll probably get a quite a

144
00:09:47.229 --> 00:09:51.070
<v Speaker 5>rush with being able to fix the machine
quite quickly while the whole production

145
00:09:51.070 --> 00:09:51.789
<v Speaker 5>line is down.

146
00:09:52.140 --> 00:09:57.219
<v Speaker 5>So you're asking them to adopt a totally
different workflow, stop rushing around,

147
00:09:57.719 --> 00:10:02.419
<v Speaker 5>and use a system that can inform you how
to schedule your maintenance activities.

148
00:10:03.380 --> 00:10:08.200
<v Speaker 5>And to minimize that that crazy period of
reacting to things.

149
00:10:09.359 --> 00:10:11.010
<v Speaker 5>And doing that is tough.

150
00:10:11.130 --> 00:10:14.500
<v Speaker 5>So, you, you need the team to fully
support that.

151
00:10:14.890 --> 00:10:18.640
<v Speaker 5>You need from shop floor to top floor to
to support that.

152
00:10:18.969 --> 00:10:24.960
<v Speaker 5>And certainly for the first year, we work
intensively with our content, with our

153
00:10:24.960 --> 00:10:29.289
<v Speaker 5>customer success team to actually almost
be like the customer.

154
00:10:29.450 --> 00:10:34.369
<v Speaker 5>We're almost using a system like they use
it to help them adopt it, and when they

155
00:10:34.369 --> 00:10:38.830
<v Speaker 5>get success, to make sure it's promoted
and it spurs on further.

156
00:10:39.669 --> 00:10:44.830
<v Speaker 5>Further expansion and and success, and our
continental team has been very receptive

157
00:10:44.830 --> 00:10:49.030
<v Speaker 5>to that, you know, we work very closely in
in collaboration between our sort of

158
00:10:49.030 --> 00:10:51.710
<v Speaker 5>customer success team and and their
engineering team.

159
00:10:52.690 --> 00:10:53.299
<v Speaker 2>Thank you.

160
00:10:53.729 --> 00:10:58.090
<v Speaker 2>So looking ahead, what are the plans in
the roadmap for Insights-Hub and Sens I

161
00:10:58.090 --> 00:10:59.250
<v Speaker 2>predict maintenance?

162
00:10:59.929 --> 00:11:01.489
<v Alex>Maybe I start quickly so fast.

163
00:11:01.570 --> 00:11:03.289
<v Alex>It's actually there are 3 major building
blocks.

164
00:11:03.369 --> 00:11:07.770
<v Alex>Number 1 is, of course, we get a lot of
feedback from customers and that goes

165
00:11:07.770 --> 00:11:08.650
<v Alex>directly into product.

166
00:11:08.729 --> 00:11:12.039
<v Alex>That is always the most important thing,
getting the customer feedback in.

167
00:11:12.450 --> 00:11:14.469
<v Alex>Number 2 is contextualization.

168
00:11:14.770 --> 00:11:18.409
<v Alex>If you look around over here, there's a
lot of different elements going beyond the

169
00:11:18.409 --> 00:11:23.549
<v Alex>analytics which make up operational
software and Analytics only gives the full value

170
00:11:23.549 --> 00:11:27.429
<v Alex>if you actually get this contextual
information, no matter if it's manufacturing,

171
00:11:27.469 --> 00:11:32.909
<v Alex>execution, quality management in and you
actually augment the data with this to

172
00:11:32.909 --> 00:11:34.659
<v Alex>actually get the greater insights.

173
00:11:34.909 --> 00:11:38.590
<v Alex>And then the last one, it's of course if
you look to the innovation hub what we are

174
00:11:38.590 --> 00:11:44.150
<v Alex>doing there already, it's expanding on the
AI capabilities which we have with the

175
00:11:44.150 --> 00:11:46.229
<v Alex>production co-pilot with agentic AI.

176
00:11:46.969 --> 00:11:51.450
<v Speaker 5>Yeah, and, and, you know, the, the key
thing is to keep being best in class on, on

177
00:11:51.450 --> 00:11:55.559
<v Speaker 5>this, and I, I look at technology now, you
know, you have the sort of the first

178
00:11:55.559 --> 00:11:58.289
<v Speaker 5>generation stuff which is more condition
monitoring and at least from a predictive

179
00:11:58.289 --> 00:11:59.559
<v Speaker 5>maintenance perspective.

180
00:12:00.609 --> 00:12:04.429
<v Speaker 5>Second generation is sort of the first AI
wave, and now you've got the, the G AI

181
00:12:04.429 --> 00:12:08.250
<v Speaker 5>wave, and it's gonna be completely
transformative over the next few years and what

182
00:12:08.250 --> 00:12:12.409
<v Speaker 5>we can achieve and it'd be even more
prescriptive with what we give to our, our

183
00:12:12.409 --> 00:12:12.969
<v Speaker 5>customers.

184
00:12:14.260 --> 00:12:14.919
<v Speaker 2>Thank you.

185
00:12:15.380 --> 00:12:18.659
<v Speaker 2>Well, this has been a very interesting
conversation.

186
00:12:18.820 --> 00:12:23.309
<v Speaker 2>Thank you for sharing your perspective on
Arca Continental.

187
00:12:23.409 --> 00:12:29.260
<v Speaker 2>And if you wanna learn more about Insight
Hub or Sensite Predictive maintenance, you

188
00:12:29.260 --> 00:12:34.369
<v Speaker 2>can come and meet with our team, the
experts, and they would be very happy to, uh,

189
00:12:34.380 --> 00:12:36.280
<v Speaker 2>share with you, do a demonstration.

190
00:12:36.530 --> 00:12:41.119
<v Speaker 2>We are in the station 122 and 139.

191
00:12:42.320 --> 00:12:47.280
<v Speaker 1>Please like and subscribe on all major
podcast channels and find out more about

192
00:12:47.280 --> 00:12:50.659
<v Speaker 1>Sensei predictive maintenance at
Siemens.com.
