WEBVTT
Language: en-US

1
00:00:01.419 --> 00:00:06.400
<v Speaker 1>Welcome to the trend detection podcast
powered by Siemens, and now your host.

2
00:00:07.329 --> 00:00:10.789
<v Speaker 2>Just to get things straight, Pablo, you're
a product owner here at Siemens.

3
00:00:11.029 --> 00:00:15.760
<v Speaker 2>Anya, you are the head of business line
digital services, and Tobias, you are head

4
00:00:15.760 --> 00:00:18.020
<v Speaker 2>of maintenance and improvement.

5
00:00:18.399 --> 00:00:22.799
<v Speaker 2>And what we're gonna be doing in this
session is we're gonna be talking a lot about

6
00:00:22.799 --> 00:00:26.440
<v Speaker 2>one of our Siemens locations, and that is
in calm.

7
00:00:26.930 --> 00:00:29.739
<v Speaker 2>And um Tobias, maybe we can start with
you.

8
00:00:29.860 --> 00:00:34.000
<v Speaker 2>Maybe you can explain, maybe first of all,
where Calm actually is for our

9
00:00:34.000 --> 00:00:36.139
<v Speaker 2>international guests and what we actually
do there.

10
00:00:36.459 --> 00:00:42.569
<v Speaker 3>So, uh, our location in Calm is in the
east of Bavaria, um, and is a part of our

11
00:00:42.569 --> 00:00:45.490
<v Speaker 3>factory network within Siemens Electrical
Products.

12
00:00:46.430 --> 00:00:51.279
<v Speaker 3>And uh with a high degree of automation,
uh, we are producing several products of

13
00:00:51.279 --> 00:00:57.340
<v Speaker 3>our low voltage portfolio there, um, like
contractors, motor starter protectors,

14
00:00:57.419 --> 00:01:04.319
<v Speaker 3>overload relays, and so on, um, and round
about 470 employees are working

15
00:01:04.319 --> 00:01:10.160
<v Speaker 3>there, uh, spread across two production
halls and around about 16,000 square meters.

16
00:01:10.760 --> 00:01:14.180
<v Speaker 3>So it's, um, more or less very big
factory.

17
00:01:14.569 --> 00:01:16.809
<v Speaker 3>Uh, and belongs to our factory in Omberg.

18
00:01:17.040 --> 00:01:17.720
<v Speaker 2>OK, cool.

19
00:01:18.129 --> 00:01:24.419
<v Speaker 2>So, When we talk about maintenance then,
in this particular factory, what is a

20
00:01:24.419 --> 00:01:27.139
<v Speaker 2>challenge or some challenges that we are
facing there?

21
00:01:27.419 --> 00:01:30.019
<v Speaker 3>So when we talk about maintenance in our
factory.

22
00:01:30.720 --> 00:01:33.879
<v Speaker 3>And the maintenance of our manufacturing
equipment.

23
00:01:34.629 --> 00:01:39.440
<v Speaker 3>Um, and our major challenge, we have to
talk about unplanned downtimes for our

24
00:01:39.440 --> 00:01:41.239
<v Speaker 3>production machines, so I'll tell you why.

25
00:01:41.980 --> 00:01:48.250
<v Speaker 3>Um, first and foremost, unplanned
downtimes mean a loss of output, so you Don't get

26
00:01:48.250 --> 00:01:49.370
<v Speaker 3>the output anymore.

27
00:01:49.809 --> 00:01:54.290
<v Speaker 3>Uh, and secondly, and more or less a
consequence of the first point, you suffer a

28
00:01:54.290 --> 00:01:58.580
<v Speaker 3>loss of productivity and last but not
least, maintenance costs are increasing.

29
00:01:59.290 --> 00:02:03.650
<v Speaker 3>So I believe that many of our guests here
in front of the stage in the booth or

30
00:02:03.650 --> 00:02:08.350
<v Speaker 3>online on the live stream are familiar
with the consequences of unplanned downtimes.

31
00:02:08.809 --> 00:02:09.710
<v Speaker 3>Most obvious.

32
00:02:10.100 --> 00:02:14.820
<v Speaker 3>Um, the employees, mainly in the
production area, cannot do their work anymore when

33
00:02:14.820 --> 00:02:16.479
<v Speaker 3>it comes to unplanned downtimes.

34
00:02:16.820 --> 00:02:21.339
<v Speaker 3>So firefighting starts, internal
discussions arise regarding the lack of

35
00:02:21.339 --> 00:02:22.130
<v Speaker 3>productivity.

36
00:02:22.410 --> 00:02:24.279
<v Speaker 3>Countermeasures have to be derived.

37
00:02:24.820 --> 00:02:28.449
<v Speaker 3>So that's the internal view, but there's
an external view too.

38
00:02:28.899 --> 00:02:31.839
<v Speaker 3>Customers will be unhappy when they're not
getting their products anymore.

39
00:02:32.270 --> 00:02:37.970
<v Speaker 3>Uh, to the right time because of the
machine broke down, for example, so a loss of

40
00:02:38.059 --> 00:02:42.470
<v Speaker 3>image, a loss of trust may come up, uh, on
the external view.

41
00:02:42.949 --> 00:02:48.589
<v Speaker 3>So our conclusion was as follows unplanned
downtimes lead to 3 to 5 times higher

42
00:02:48.589 --> 00:02:50.979
<v Speaker 3>costs compared to planned downtimes.

43
00:02:51.750 --> 00:02:57.029
<v Speaker 3>And if you put yourself in that situation
I just described and imagine in addition.

44
00:02:57.470 --> 00:03:01.119
<v Speaker 3>Uh, you're facing a lack of transparency
on the health and the condition of your

45
00:03:01.119 --> 00:03:02.699
<v Speaker 3>assets in the production machine.

46
00:03:04.000 --> 00:03:07.550
<v Speaker 3>Your machines could break down at any
moment, but you have no idea when or how.

47
00:03:08.160 --> 00:03:12.520
<v Speaker 3>So we didn't feel comfortable with that
situation, and we decided to act.

48
00:03:12.720 --> 00:03:18.399
<v Speaker 2>OK, yeah, so a lot, a lot of consequences,
negative ones, um, so yeah, what did you

49
00:03:18.399 --> 00:03:18.789
<v Speaker 2>do?

50
00:03:19.000 --> 00:03:24.470
<v Speaker 3>So as I said, we didn't feel comfortable,
uh, with that situation, and we decided to

51
00:03:24.470 --> 00:03:26.740
<v Speaker 3>implement a digitalization approach.

52
00:03:27.419 --> 00:03:31.740
<v Speaker 3>Uh, that combines the real world on the
one hand and the digital world on the other

53
00:03:31.740 --> 00:03:32.059
<v Speaker 3>hand.

54
00:03:32.699 --> 00:03:33.660
<v Speaker 3>So what did we do?

55
00:03:33.910 --> 00:03:39.630
<v Speaker 3>Uh, we integrated smart hardware on the
one hand, so the real world, uh, to make use

56
00:03:39.630 --> 00:03:45.300
<v Speaker 3>of the data our machines produce, uh, and
we implemented an AI-driven analysis

57
00:03:45.300 --> 00:03:45.919
<v Speaker 3>approach.

58
00:03:46.500 --> 00:03:47.639
<v Speaker 3>On the other hand, so.

59
00:03:48.529 --> 00:03:53.779
<v Speaker 3>To play on the digital world, so, so that
we can predict failures and downtimes

60
00:03:53.779 --> 00:03:55.220
<v Speaker 3>before they really happen, OK.

61
00:03:56.089 --> 00:04:02.289
<v Speaker 2>Now, Pablo, yeah, obviously
digitalization, whenever we hear it, we think software

62
00:04:02.289 --> 00:04:05.289
<v Speaker 2>immediately, but there's also hardware
involved, right?

63
00:04:05.440 --> 00:04:05.940
<v Speaker 2>What can you tell

64
00:04:05.940 --> 00:04:10.490
<v Speaker 4>us, um, 11 of the things that you have to
think that is that digitalization is not

65
00:04:10.490 --> 00:04:16.329
<v Speaker 4>just about software, it's also migration
or changing, adapting our OT systems, our

66
00:04:16.329 --> 00:04:17.609
<v Speaker 4>automation systems.

67
00:04:18.410 --> 00:04:22.540
<v Speaker 4>You, you have to think that digitalization
starts in the shop floor.

68
00:04:22.750 --> 00:04:26.750
<v Speaker 4>The shop floor has all the information of
the real asset, the conveyor lanes, the

69
00:04:26.750 --> 00:04:32.709
<v Speaker 4>pumps, the mixers, the crushing machines,
all this information, these devices

70
00:04:32.709 --> 00:04:38.709
<v Speaker 4>provide you information and The idea is to
catch this information for you being used

71
00:04:38.709 --> 00:04:40.049
<v Speaker 4>in a higher level.

72
00:04:41.390 --> 00:04:45.149
<v Speaker 4>Without this information, it doesn't
matter how smart your software is.

73
00:04:45.359 --> 00:04:50.070
<v Speaker 4>The software is blind, and the idea behind
it is the same like if you drive a car.

74
00:04:50.149 --> 00:04:52.450
<v Speaker 4>Imagine that you would drive a car without
cockpits.

75
00:04:52.670 --> 00:04:54.989
<v Speaker 4>It doesn't matter how good are you for
driving.

76
00:04:55.029 --> 00:04:55.910
<v Speaker 4>You don't know the speed.

77
00:04:55.989 --> 00:05:00.149
<v Speaker 4>You don't know if it's missing oil, if it
is the revolution that the car is going or

78
00:05:00.149 --> 00:05:00.950
<v Speaker 4>the motor is going.

79
00:05:01.269 --> 00:05:04.230
<v Speaker 4>So all you need is all this information.

80
00:05:04.355 --> 00:05:10.994
<v Speaker 4>For systems and this is uh where where
they they start to to change

81
00:05:10.994 --> 00:05:17.424
<v Speaker 4>our OT systems to catch this information
and with the right hardware our

82
00:05:17.424 --> 00:05:22.864
<v Speaker 4>applications became storytellers of what's
happening on the real application.

83
00:05:23.589 --> 00:05:29.549
<v Speaker 4>And bridging this between the OT to the IT
level to flow this data up, OK?

84
00:05:30.429 --> 00:05:35.540
<v Speaker 2>Now, I mentioned in the intro that we're
gonna be talking about SIRIUS as well, so

85
00:05:35.540 --> 00:05:37.390
<v Speaker 2>our SIRIUS product family.

86
00:05:37.910 --> 00:05:43.269
<v Speaker 2>So, can you tell us which part of the
product family is actually involved in this

87
00:05:43.269 --> 00:05:44.850
<v Speaker 2>digitalization process?

88
00:05:45.269 --> 00:05:51.950
<v Speaker 4>Sure, um, in CDU for years, for, for
decades, SIRIUS was about controlling

89
00:05:51.950 --> 00:05:53.149
<v Speaker 4>and protecting, yeah?

90
00:05:53.739 --> 00:05:59.399
<v Speaker 4>Um, but it was part of our DNA, but The
world is changing.

91
00:05:59.570 --> 00:06:05.609
<v Speaker 4>The digitalization is making a tremendous
change on the industry, and this change is

92
00:06:05.609 --> 00:06:08.649
<v Speaker 4>generating also that we have to change our
portfolio.

93
00:06:08.890 --> 00:06:12.850
<v Speaker 4>Our portfolio is not anymore only about
control and protecting for sure.

94
00:06:12.929 --> 00:06:16.329
<v Speaker 4>We are still doing that, but it's about
also.

95
00:06:17.049 --> 00:06:22.019
<v Speaker 4>Gathering data, so the data flow, how this
data can help to a higher level.

96
00:06:22.559 --> 00:06:29.040
<v Speaker 4>So SIRIUS became a central part of the
digitalization, not maybe because of the

97
00:06:29.040 --> 00:06:35.709
<v Speaker 4>software side, but because of the
migration of the Or Tite and the shop floor

98
00:06:35.709 --> 00:06:37.850
<v Speaker 4>information that we can capture with our
portfolio.

99
00:06:37.989 --> 00:06:38.329
<v Speaker 2>OK.

100
00:06:38.589 --> 00:06:45.190
<v Speaker 2>Now you mentioned bringing data up, so, so
to the IT level, which, which part of the

101
00:06:45.190 --> 00:06:46.910
<v Speaker 2>SIRIUS family now actually does that?

102
00:06:47.470 --> 00:06:52.010
<v Speaker 4>Well, we have a, a complete portfolio like
I said before, uh, actually it's in the

103
00:06:52.010 --> 00:06:56.179
<v Speaker 4>screen, but we go from the standard
contractors and circuit breakers.

104
00:06:56.260 --> 00:07:00.339
<v Speaker 4>You can make them intelligent with a 3
year system intelligently module and connect

105
00:07:00.339 --> 00:07:04.160
<v Speaker 4>to better ET 200 speed as well as the
e-starter.

106
00:07:04.470 --> 00:07:09.190
<v Speaker 4>Eric Froli was some minutes ago here and
he showed a wonderful product.

107
00:07:09.230 --> 00:07:13.540
<v Speaker 4>They start a full electronic starter also
provided the same information like the 337

108
00:07:13.540 --> 00:07:18.750
<v Speaker 4>ILM soft starter, the well known SIMMO
code in the process industry, very well

109
00:07:18.750 --> 00:07:23.790
<v Speaker 4>known, and also we have full monitoring
relays, so it is not about only motors.

110
00:07:24.070 --> 00:07:27.790
<v Speaker 4>It doesn't matter which is the variable
that you want to monitor in your factory in

111
00:07:27.790 --> 00:07:28.329
<v Speaker 4>your application.

112
00:07:28.750 --> 00:07:30.350
<v Speaker 4>We have the full portfolio for

113
00:07:30.350 --> 00:07:30.670
<v Speaker 2>that.

114
00:07:31.339 --> 00:07:31.709
<v Speaker 2>OK.

115
00:07:32.420 --> 00:07:34.859
<v Speaker 2>So Anya, what would you say?

116
00:07:34.940 --> 00:07:37.540
<v Speaker 2>How does all this data then actually help
us?

117
00:07:37.989 --> 00:07:40.019
<v Speaker 2>I mean it's great to have it, but what do
you do with it?

118
00:07:40.309 --> 00:07:45.869
<v Speaker 5>Well, so once the data is collected, it's
being sent to either local or cloud

119
00:07:45.869 --> 00:07:52.269
<v Speaker 5>systems for actual analytics, and the
Siemens software turns the data into

120
00:07:52.269 --> 00:07:55.940
<v Speaker 5>actionable insights which help the
maintenance technicians.

121
00:07:56.269 --> 00:08:01.350
<v Speaker 5>So the maintenance technicians use this
information to optimize their maintenance

122
00:08:01.350 --> 00:08:02.059
<v Speaker 5>tasks.

123
00:08:02.260 --> 00:08:06.429
<v Speaker 2>OK, so which software is actually used
then for this task?

124
00:08:06.760 --> 00:08:11.679
<v Speaker 5>In this task we use sensor predictive
maintenance, which is an AI based cloud

125
00:08:11.679 --> 00:08:12.260
<v Speaker 5>solution.

126
00:08:12.720 --> 00:08:18.549
<v Speaker 5>It learns from historical and real-time
condition data to predict failures.

127
00:08:19.160 --> 00:08:21.750
<v Speaker 5>We apply AI here in two disciplines.

128
00:08:21.920 --> 00:08:28.640
<v Speaker 5>So first of all, the classic analytics
capabilities that, um, yeah, monitor a time

129
00:08:28.640 --> 00:08:34.750
<v Speaker 5>series and you can detect anomalies,
trends, threshold violations, patterns, things

130
00:08:34.750 --> 00:08:35.239
<v Speaker 5>like that.

131
00:08:36.080 --> 00:08:42.280
<v Speaker 5>Um, and then the generative AI takes it to
the next level by giving the numbers

132
00:08:42.280 --> 00:08:48.479
<v Speaker 5>meaning, textual meaning, really
describing what is going on, why is the case

133
00:08:48.479 --> 00:08:49.140
<v Speaker 5>raised.

134
00:08:49.559 --> 00:08:55.280
<v Speaker 5>It can suggest the reason and
explanations, a root cause, and even a recommendation

135
00:08:55.280 --> 00:08:56.179
<v Speaker 5>for the remedy.

136
00:08:56.570 --> 00:08:56.580
<v Speaker 5>Mhm.

137
00:08:57.010 --> 00:09:01.049
<v Speaker 2>So let's say I'm a user or a potential
user of this.

138
00:09:01.369 --> 00:09:04.520
<v Speaker 2>How can I now envision my interaction with
it?

139
00:09:04.650 --> 00:09:05.309
<v Speaker 2>How does it work?

140
00:09:05.770 --> 00:09:11.159
<v Speaker 5>So the user is typically in the
maintenance department and they can access the app

141
00:09:11.159 --> 00:09:16.169
<v Speaker 5>via a standard browser either on a PC or
on a tablet like this.

142
00:09:16.549 --> 00:09:20.890
<v Speaker 5>OK, so the user doesn't have to be close
to the machine to know about their

143
00:09:20.890 --> 00:09:22.250
<v Speaker 5>condition, and that's the charm.

144
00:09:22.690 --> 00:09:29.210
<v Speaker 5>All relevant assets, all onboarded assets
can be um checked out and the condition is

145
00:09:29.210 --> 00:09:35.969
<v Speaker 5>clear at all times and in the case you
hear um it is highlighted where are assets

146
00:09:35.969 --> 00:09:41.969
<v Speaker 5>that actually need attention, so the
maintenance technician can go into the details

147
00:09:41.969 --> 00:09:47.849
<v Speaker 5>of the case, check it out, see the
evidence, which kind of data shows that there's

148
00:09:47.849 --> 00:09:48.780
<v Speaker 5>something going on.

149
00:09:49.349 --> 00:09:55.210
<v Speaker 5>And it's even possible to open a chat
window to the co-pilot and chat, ask questions

150
00:09:55.309 --> 00:09:56.659
<v Speaker 5>like in a conversation.

151
00:09:57.239 --> 00:10:01.460
<v Speaker 5>And I'm inviting everyone here to check
out the co-pilot functions over here in our

152
00:10:01.460 --> 00:10:02.710
<v Speaker 5>industrial AI hub.

153
00:10:03.000 --> 00:10:08.760
<v Speaker 5>You can talk and find out what's the
problem and really get a step by step guidance

154
00:10:08.760 --> 00:10:11.599
<v Speaker 5>through the problem that, that there is
for the maintenance to solve.

155
00:10:11.710 --> 00:10:12.140
<v Speaker 5>OK.

156
00:10:12.440 --> 00:10:16.200
<v Speaker 2>And that, by the way, is why I and
Christine keep reminding you to go and check it

157
00:10:16.200 --> 00:10:16.640
<v Speaker 2>out, yeah?

158
00:10:16.760 --> 00:10:20.739
<v Speaker 2>This is exactly the reason we want you to
really experience it live.

159
00:10:22.289 --> 00:10:27.340
<v Speaker 2>Tobias, let's go a bit deeper then into
the calm factory use case.

160
00:10:27.580 --> 00:10:31.210
<v Speaker 2>So what exactly did you implement there
then?

161
00:10:31.500 --> 00:10:37.219
<v Speaker 3>So we applied the solution that Pablo and
Anya just presented to a highly automated

162
00:10:37.219 --> 00:10:37.340
<v Speaker 3>production.

163
00:10:37.534 --> 00:10:42.325
<v Speaker 3>Production line in our pre-production of
the motor starter protector 3RB 2 in calm

164
00:10:43.145 --> 00:10:49.534
<v Speaker 3>and uh the implementation uh took place
during ongoing operations, so like a

165
00:10:49.534 --> 00:10:52.554
<v Speaker 3>brownfield approach and was done in 3
steps.

166
00:10:53.099 --> 00:10:58.440
<v Speaker 3>Um, first of all, we upgraded our cabinets
by integrating the relevant, uh, serious

167
00:10:58.440 --> 00:11:02.840
<v Speaker 3>products, the smart hardware, to make use
of the data our machines produce.

168
00:11:03.419 --> 00:11:09.020
<v Speaker 3>Uh, secondly, we expanded our programming
standard and we integrated data

169
00:11:09.020 --> 00:11:15.619
<v Speaker 3>preprocessing on the PLC, uh, uh, like a
preprocessing routine, uh, to

170
00:11:15.619 --> 00:11:18.789
<v Speaker 3>secure the data transfer from the shop
floor, from the.

171
00:11:19.280 --> 00:11:24.520
<v Speaker 3>Uh, manufacturing line to the cloud and,
uh, finally we onboarded Sensi predictive

172
00:11:24.520 --> 00:11:30.039
<v Speaker 3>maintenance, the AI-driven solution that
Anya just presented, and now we are able to

173
00:11:30.039 --> 00:11:35.650
<v Speaker 3>gain insights into more than 90 connected
assets, um, in the production line.

174
00:11:36.080 --> 00:11:41.650
<v Speaker 3>Uh, especially the critical motor driven
components, um, that we try to have a look

175
00:11:41.650 --> 00:11:46.159
<v Speaker 3>on the health and the condition, how they
are working, and what stuff is there, uh,

176
00:11:46.210 --> 00:11:47.159
<v Speaker 3>with the components.

177
00:11:47.330 --> 00:11:52.130
<v Speaker 2>OK, Pablo, uh, Tobias just mentioned, the,
the SIRIUS product family again.

178
00:11:52.239 --> 00:11:55.369
<v Speaker 2>So can you tell us a bit more which
hardware was used then in Calm?

179
00:11:55.650 --> 00:11:55.809
<v Speaker 2>Well,

180
00:11:55.969 --> 00:11:57.989
<v Speaker 4>in CM in particular, we use the 3RS.

181
00:11:58.625 --> 00:11:59.875
<v Speaker 4>intelligent link module.

182
00:12:00.224 --> 00:12:04.895
<v Speaker 4>This is a device you can find directly
here on stand, but it's a device that goes

183
00:12:04.895 --> 00:12:07.344
<v Speaker 4>over the standard contact or standard
circuit breaker.

184
00:12:07.455 --> 00:12:12.625
<v Speaker 4>It connects with both and easily you can
start having not only control and

185
00:12:12.625 --> 00:12:17.864
<v Speaker 4>monitoring and protection of the motors,
but all the information, the data, that

186
00:12:17.864 --> 00:12:20.744
<v Speaker 4>real-time data that it needs for the
sensile level.

187
00:12:21.030 --> 00:12:27.309
<v Speaker 4>Um, with, with this, this hardware makes
very easy, the retrofitting of the machine

188
00:12:27.309 --> 00:12:29.500
<v Speaker 4>because you don't have to change even the
contractors.

189
00:12:29.549 --> 00:12:32.140
<v Speaker 4>You can just snap in on these devices.

190
00:12:32.429 --> 00:12:37.250
<v Speaker 4>And also we use the e-starter that was
presented also some minutes ago.

191
00:12:38.109 --> 00:12:42.830
<v Speaker 4>Also this starter was there and the beauty
of this is that both devices, also the

192
00:12:42.830 --> 00:12:46.469
<v Speaker 4>soft starter, the data structure of these
devices is exactly the same.

193
00:12:47.080 --> 00:12:52.719
<v Speaker 4>Therefore, if you use for one case the 3R
7 ILM and the next time you want to use

194
00:12:52.719 --> 00:12:57.150
<v Speaker 4>the starter, the data structure, how you
might handle that data is exactly the same.

195
00:12:57.320 --> 00:12:57.820
<v Speaker 2>OK.

196
00:12:58.359 --> 00:13:03.760
<v Speaker 2>Now, in order for this to work properly
for everyone and everyone to be able to work

197
00:13:03.760 --> 00:13:05.039
<v Speaker 2>efficiently with it.

198
00:13:05.539 --> 00:13:08.469
<v Speaker 2>It needs to be connected to the entire
system, right?

199
00:13:08.580 --> 00:13:09.700
<v Speaker 2>So how does that work?

200
00:13:10.020 --> 00:13:12.250
<v Speaker 4>Well, that's the beauty of our system.

201
00:13:12.500 --> 00:13:18.169
<v Speaker 4>Our system is fully integrated to cymatics
environment or to Tia portal environment.

202
00:13:18.500 --> 00:13:20.340
<v Speaker 4>So therefore the integration is quick.

203
00:13:20.900 --> 00:13:21.500
<v Speaker 4>Very quick.

204
00:13:21.659 --> 00:13:23.369
<v Speaker 4>You, you don't need extra software.

205
00:13:23.419 --> 00:13:27.000
<v Speaker 4>You just use the step 7 in the E-starter
or the 37 ILM.

206
00:13:27.690 --> 00:13:32.099
<v Speaker 4>You drag and drop and the communication,
the diagnostic, and everything is

207
00:13:32.099 --> 00:13:35.039
<v Speaker 4>automatically connected with our
ecosystem,

208
00:13:35.260 --> 00:13:35.599
<v Speaker 2>right?

209
00:13:35.859 --> 00:13:38.599
<v Speaker 2>And just back to the devices again
briefly.

210
00:13:38.859 --> 00:13:43.219
<v Speaker 2>So obviously they're, they're measuring a
lot of stuff to get the data, but what are

211
00:13:43.219 --> 00:13:45.539
<v Speaker 2>the values that they actually measure?

212
00:13:46.190 --> 00:13:50.690
<v Speaker 4>Well, our device measures the kick values
of the motors, right?

213
00:13:50.950 --> 00:13:56.549
<v Speaker 4>Currents, asymmetries, grounding currents,
starting times, voltage.

214
00:13:57.739 --> 00:14:04.460
<v Speaker 4>power factor, energy, all the, all the
recurrent, how many cycles you have used the

215
00:14:04.460 --> 00:14:09.409
<v Speaker 4>device, how many hours has been running
the motor or also the contractors or the the

216
00:14:09.429 --> 00:14:14.260
<v Speaker 4>starter, and with all this data you can
collect all the crucial information that you

217
00:14:14.260 --> 00:14:17.119
<v Speaker 4>need for the shop floor for the sens site
level.

218
00:14:17.520 --> 00:14:23.049
<v Speaker 2>OK, and, and Anya, we said before that the
data goes up, yeah, to the IT level.

219
00:14:23.250 --> 00:14:28.390
<v Speaker 2>So in this particular case then where does
the data go from, from Pablo's devices?

220
00:14:29.049 --> 00:14:34.289
<v Speaker 5>So the data goes from the shop floor to
the top floor we like to say, and our

221
00:14:34.289 --> 00:14:38.729
<v Speaker 5>industrial communication protocols make
sure that the transfer is reliable and

222
00:14:38.729 --> 00:14:39.309
<v Speaker 5>secure.

223
00:14:39.739 --> 00:14:45.500
<v Speaker 5>And we use typical industrial
communication protocols like ProfyNet, Ethernet IP or

224
00:14:45.500 --> 00:14:50.359
<v Speaker 5>Modbus TCP, and then when it gets to the
cloud, it's MQTT the typical way.

225
00:14:51.429 --> 00:14:58.169
<v Speaker 5>And we perform the required analytics to
turn the data into strategic information.

226
00:14:58.549 --> 00:14:59.549
<v Speaker 5>So what does that mean?

227
00:14:59.859 --> 00:15:02.909
<v Speaker 5>Data having motor temperature of 90
degrees.

228
00:15:03.109 --> 00:15:03.750
<v Speaker 5>Well, what is this?

229
00:15:03.830 --> 00:15:09.429
<v Speaker 5>It's data, but the context of it makes it
valuable information.

230
00:15:09.549 --> 00:15:12.289
<v Speaker 5>So if a motor is running slowly.

231
00:15:13.070 --> 00:15:20.020
<v Speaker 5>This kind of temperature is, is OK, but if
it's overheating and it's outside of the

232
00:15:20.020 --> 00:15:24.099
<v Speaker 5>range, this is the point where the
maintenance technicians need to be alerted, need

233
00:15:24.099 --> 00:15:29.000
<v Speaker 5>to be informed, and this is what, what's,
yeah, the anomaly detection here.

234
00:15:29.460 --> 00:15:35.340
<v Speaker 5>Find the context of the of the usage of
the motor with the actual condition data

235
00:15:35.340 --> 00:15:36.119
<v Speaker 5>like temperature.

236
00:15:36.859 --> 00:15:41.890
<v Speaker 5>And driving the attention to the asset
when it's necessary is ultimately the goal of

237
00:15:41.890 --> 00:15:43.340
<v Speaker 5>a predictive maintenance solution.

238
00:15:44.000 --> 00:15:49.789
<v Speaker 2>And implementing or setting up these
solutions, I mean, it sounds quite complex.

239
00:15:50.159 --> 00:15:53.760
<v Speaker 2>So was there anything in particular you
needed to take into consideration?

240
00:15:54.010 --> 00:15:54.919
<v Speaker 2>How was the setup?

241
00:15:55.119 --> 00:15:57.559
<v Speaker 5>Well, it's, it's a typical same way.

242
00:15:57.619 --> 00:16:01.960
<v Speaker 5>It always starts with the critical asset
that requires the monitoring.

243
00:16:02.400 --> 00:16:07.039
<v Speaker 5>So once this is defined with the customer
together, um, it's also necessary to

244
00:16:07.039 --> 00:16:11.799
<v Speaker 5>define the necessary KPIs to measure the
success, what needs to be improved or what

245
00:16:11.799 --> 00:16:12.929
<v Speaker 5>needs to be reduced.

246
00:16:13.590 --> 00:16:20.070
<v Speaker 5>This is the starting point to then
determine, well, these assets, which kind of

247
00:16:20.070 --> 00:16:24.520
<v Speaker 5>conditions do they have, which are the
condition indicators that help understand it,

248
00:16:25.109 --> 00:16:29.869
<v Speaker 5>and with this point you know which data
points you need and then the next step is to

249
00:16:29.869 --> 00:16:31.210
<v Speaker 5>figure out where to find them.

250
00:16:31.580 --> 00:16:36.479
<v Speaker 5>Either they're already available in the
PLC or sometimes additional sensors need to

251
00:16:36.479 --> 00:16:42.179
<v Speaker 5>be installed, and this then determines the
way the data needs to take end to end

252
00:16:42.179 --> 00:16:46.169
<v Speaker 5>ultimately reaching the cloud where the
analytics take place.

253
00:16:46.330 --> 00:16:46.679
<v Speaker 5>OK,

254
00:16:47.419 --> 00:16:49.119
<v Speaker 2>Tobias, I believe that this.

255
00:16:49.820 --> 00:16:55.780
<v Speaker 2>Is all still in its infancy, um, so, so
tell us, when did you actually start with

256
00:16:55.780 --> 00:16:58.690
<v Speaker 2>this and which results have you already
been seeing?

257
00:16:58.979 --> 00:17:04.380
<v Speaker 3>Well, the go live was 6 months ago and we
have already seen the first success cases

258
00:17:04.619 --> 00:17:06.160
<v Speaker 3>which have all one thing in common.

259
00:17:06.989 --> 00:17:12.438
<v Speaker 3>Um, by predicting failures, we were able
to maintain the critical assets before they

260
00:17:12.438 --> 00:17:13.178
<v Speaker 3>really broke down.

261
00:17:13.838 --> 00:17:15.619
<v Speaker 3>So let me tell you one example.

262
00:17:16.048 --> 00:17:20.838
<v Speaker 3>Um, in one example we saw anomalies, uh,
in torque and the current consumption of a

263
00:17:20.838 --> 00:17:26.298
<v Speaker 3>linear direct drive, which would have led
to a production downtime of several days

264
00:17:26.598 --> 00:17:31.279
<v Speaker 3>maybe, uh, and the corresponding financial
losses that I mentioned a few minutes ago

265
00:17:31.279 --> 00:17:34.438
<v Speaker 3>and just remember the, uh, all the
consequences.

266
00:17:34.829 --> 00:17:40.680
<v Speaker 3>Yeah, um, I, I told you a few minutes ago,
unhappy customers, internal discussions,

267
00:17:40.760 --> 00:17:44.859
<v Speaker 3>internal troubleshooting, and so on, all
the productivity discussions.

268
00:17:45.280 --> 00:17:50.500
<v Speaker 3>So our new approach by combining the real
and the digital world prevented all these

269
00:17:50.500 --> 00:17:57.040
<v Speaker 3>negative effects, uh, and consequences in
more, um, more or less, uh, 5 to 6

270
00:17:57.040 --> 00:17:58.099
<v Speaker 3>examples that we had.

271
00:17:58.560 --> 00:17:59.959
<v Speaker 3>Uh, in the last 6 months.

272
00:18:00.209 --> 00:18:05.630
<v Speaker 2>OK, now with that in mind, what would you
say are, are the key benefits then of

273
00:18:05.630 --> 00:18:09.699
<v Speaker 2>combining Siemens hardware and Siemens
software?

274
00:18:10.050 --> 00:18:14.069
<v Speaker 3>Well, in my opinion, there are 22 big
benefits.

275
00:18:14.660 --> 00:18:18.739
<v Speaker 3>So on the one hand, the transparency on
the health and the condition of the

276
00:18:18.739 --> 00:18:22.920
<v Speaker 3>different assets in the production
machines is much more higher than before.

277
00:18:23.260 --> 00:18:26.900
<v Speaker 3>Only by using the data the machine
produces every second.

278
00:18:27.069 --> 00:18:27.079
<v Speaker 3>OK.

279
00:18:27.500 --> 00:18:33.219
<v Speaker 3>And on the other hand, and that's the part
of, of the AI solution, making use of the

280
00:18:33.219 --> 00:18:39.930
<v Speaker 3>data leads to insights on the hourly, uh,
in a, in a minutely frequent, um,

281
00:18:40.099 --> 00:18:43.109
<v Speaker 3>insights on the, on the assets, on their
condition.

282
00:18:43.449 --> 00:18:48.329
<v Speaker 3>And predictive maintenance action actions
can be derived before the machine breaks

283
00:18:48.329 --> 00:18:48.709
<v Speaker 3>down.

284
00:18:49.130 --> 00:18:54.170
<v Speaker 3>So in combination we are now able to avoid
downtimes and drive maintenance

285
00:18:54.170 --> 00:18:59.729
<v Speaker 3>efficiency and all these benefits that I
told you, uh, were implemented through

286
00:18:59.729 --> 00:19:04.849
<v Speaker 3>reasonable changes to the existing
software and hardware environment in a brownfield

287
00:19:04.849 --> 00:19:05.130
<v Speaker 3>approach.

288
00:19:05.229 --> 00:19:05.670
<v Speaker 2>Yeah.

289
00:19:06.170 --> 00:19:09.329
<v Speaker 2>So you launched it 6 months ago.

290
00:19:10.280 --> 00:19:13.140
<v Speaker 2>What happens in the next 6 months and
beyond,

291
00:19:13.310 --> 00:19:18.579
<v Speaker 3>yeah, based on the positive experience we
made with our pilot project, uh, we are

292
00:19:18.579 --> 00:19:20.099
<v Speaker 3>now planning the next steps.

293
00:19:20.510 --> 00:19:25.069
<v Speaker 3>So the further rollout is prepared in our
factory in Ombeg and Calm, and we will

294
00:19:25.069 --> 00:19:26.829
<v Speaker 3>onboard the next use cases.

295
00:19:27.609 --> 00:19:33.000
<v Speaker 3>Um, but on the other hand, other locations
have recognized the benefits too and are

296
00:19:33.000 --> 00:19:34.239
<v Speaker 3>showing interest now.

297
00:19:34.689 --> 00:19:41.030
<v Speaker 3>So, um, the knowledge transfer is on the
agenda both internally to other production

298
00:19:41.030 --> 00:19:46.150
<v Speaker 3>units in our factory in Ombeg and Calm and
to the other Siemens locations, uh, which

299
00:19:46.150 --> 00:19:47.069
<v Speaker 3>are showing interest.

300
00:19:47.609 --> 00:19:52.719
<v Speaker 3>And finally, Uh, we will close the loop
towards new production machines, so we will

301
00:19:52.719 --> 00:19:58.430
<v Speaker 3>integrate both the hardware and the
software in the very beginning of the life cycle

302
00:19:58.430 --> 00:20:00.000
<v Speaker 3>of our manufacturing equipment,

303
00:20:00.199 --> 00:20:00.560
<v Speaker 2>OK.

304
00:20:01.469 --> 00:20:07.650
<v Speaker 2>Anya, could you maybe summarize some of
the key takeaways of this sort of

305
00:20:08.150 --> 00:20:11.550
<v Speaker 2>experience, if we can call it, in
particular for our customers?

306
00:20:11.869 --> 00:20:17.589
<v Speaker 5>Yeah, so we showed here that the Siemens
factory is actually using the products it

307
00:20:17.589 --> 00:20:22.989
<v Speaker 5>produces, and the Siemens products,
software and hardware together jointly proved

308
00:20:22.989 --> 00:20:24.790
<v Speaker 5>their value in in the setup.

309
00:20:25.739 --> 00:20:31.099
<v Speaker 5>And the good news is we're not just
keeping it to ourselves, we're actually enabling

310
00:20:31.099 --> 00:20:34.420
<v Speaker 5>you as our customers to use exactly this
technology.

311
00:20:35.020 --> 00:20:41.819
<v Speaker 5>So you may benefit just as much in saving
maintenance costs and avoiding unplanned

312
00:20:41.819 --> 00:20:43.319
<v Speaker 5>downtimes, right?

313
00:20:43.859 --> 00:20:48.939
<v Speaker 5>So, and it's not only software and
hardware we provide, we also support in services.

314
00:20:49.290 --> 00:20:55.689
<v Speaker 5>So our service experts guide you step by
step through through the setup of the

315
00:20:55.689 --> 00:20:58.380
<v Speaker 5>concept and then also implementing it.

316
00:20:58.849 --> 00:21:04.329
<v Speaker 5>So we have typically um standardized
blueprints of the typical scenarios that it's

317
00:21:04.329 --> 00:21:10.650
<v Speaker 5>very quick to give a first um overall
estimation how long that will take, how much

318
00:21:10.650 --> 00:21:17.449
<v Speaker 5>it will cost to set it up, and then also
enable it quickly to, to provide the value

319
00:21:17.449 --> 00:21:18.420
<v Speaker 5>to the customer.

320
00:21:19.719 --> 00:21:25.319
<v Speaker 5>So I'm inviting all of you to come by the
sensor predictive maintenance uh model,

321
00:21:25.560 --> 00:21:30.439
<v Speaker 5>have a chat with us about your specific uh
situation, about your requirements and

322
00:21:30.439 --> 00:21:35.959
<v Speaker 5>your operations and your production, and
we're looking forward to finding the proper

323
00:21:35.959 --> 00:21:36.780
<v Speaker 5>solution for you.

324
00:21:37.219 --> 00:21:38.619
<v Speaker 2>Yeah, I think we even have it up here.

325
00:21:38.719 --> 00:21:39.459
<v Speaker 2>Yeah, exactly.

326
00:21:39.739 --> 00:21:42.859
<v Speaker 2>So, Pablo, where else can we find more
info?

327
00:21:42.930 --> 00:21:43.099
<v Speaker 2>Are you,

328
00:21:43.180 --> 00:21:43.920
<v Speaker 4>are you everywhere?

329
00:21:43.979 --> 00:21:47.180
<v Speaker 4>So yeah, we actually took control of the
booth.

330
00:21:47.650 --> 00:21:50.880
<v Speaker 4>So you can find sensor plate maintenance
in the 85.

331
00:21:51.099 --> 00:21:53.819
<v Speaker 4>You can find electrification, so the
e-starter.

332
00:21:53.979 --> 00:21:59.510
<v Speaker 4>Also the SIMIMOC code and the 337
intelligent link module here directly on the

333
00:21:59.520 --> 00:22:04.609
<v Speaker 4>number 8 and in the middle where we crash
together you can see the complete solution

334
00:22:04.609 --> 00:22:09.229
<v Speaker 4>with SIRIUS and Sensi in the AI AI hub

335
00:22:10.010 --> 00:22:13.489
<v Speaker 2>exactly and the final question, Tobias.

336
00:22:14.949 --> 00:22:19.910
<v Speaker 2>I'm hoping everyone stays until the end of
SPS, so until Thursday, and if they've

337
00:22:19.910 --> 00:22:23.739
<v Speaker 2>got time on Friday, how far is it to get
to Cannes from here?

338
00:22:23.910 --> 00:22:25.060
<v Speaker 2>How, how long would you need?

339
00:22:25.189 --> 00:22:26.030
<v Speaker 2>Let's say driving.

340
00:22:26.219 --> 00:22:29.750
<v Speaker 3>Well, driving by car, I think, um, maybe 2

341
00:22:29.750 --> 00:22:30.130
<v Speaker 2>hours.

342
00:22:30.229 --> 00:22:30.619
<v Speaker 2>2 hours.

343
00:22:30.750 --> 00:22:31.790
<v Speaker 2>So that's doable, right?

344
00:22:31.910 --> 00:22:36.270
<v Speaker 2>So make sure to go and visit these guys in
Cannes and then also in Hamburg, and then

345
00:22:36.270 --> 00:22:39.410
<v Speaker 2>next time round we'll see where all your
other solutions are.

346
00:22:39.750 --> 00:22:41.390
<v Speaker 2>So thank you so much for being here today.

347
00:22:41.469 --> 00:22:43.890
<v Speaker 2>Can I have a big round of applause for our
guests, please?

348
00:22:45.030 --> 00:22:50.709
<v Speaker 2>Thank you so much for joining me here,
great talk and um enjoy the rest of SPS and

349
00:22:50.709 --> 00:22:51.239
<v Speaker 2>see you soon.

350
00:22:51.439 --> 00:22:52.540
<v Speaker 2>Thank you so much, bye bye.

351
00:22:54.530 --> 00:22:59.489
<v Speaker 1>Please like and subscribe on all major
podcast channels and find out more about

352
00:22:59.489 --> 00:23:02.869
<v Speaker 1>Sensei predictive maintenance at
Siemens.com.
