WEBVTT
Language: en-US

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

2
00:00:05.159 --> 00:00:06.780
<v Speaker 1>And now your host.

3
00:00:09.220 --> 00:00:13.739
<v Speaker 2>I am your host Senia, and in today's
episode, we are going to explore how the

4
00:00:13.739 --> 00:00:18.260
<v Speaker 2>automotive industry is navigating its most
pressing challenges, from production

5
00:00:18.260 --> 00:00:22.860
<v Speaker 2>complexity and labor shortages to
unplanned downtime and sustainability demands.

6
00:00:23.100 --> 00:00:27.510
<v Speaker 2>And joining us today is Mikhail
Schafferman, sales vertical manager for Vertical

7
00:00:27.510 --> 00:00:29.360
<v Speaker 2>automotive at Siemens.

8
00:00:29.899 --> 00:00:32.139
<v Speaker 2>Mikhail, it's really great to have you
here today.

9
00:00:32.340 --> 00:00:35.220
<v Speaker 2>Can you start by telling us a bit about
your old Siemens?

10
00:00:36.639 --> 00:00:37.799
<v Mikhail Shaferman>Absolutely, Cenia.

11
00:00:38.000 --> 00:00:39.020
<v Mikhail Shaferman>Thank you for having me.

12
00:00:40.020 --> 00:00:44.500
<v Mikhail Shaferman>My focus is working closely with our
automotive customers to make sure their

13
00:00:44.500 --> 00:00:47.680
<v Mikhail Shaferman>production lines keep running day in and
day out.

14
00:00:48.259 --> 00:00:53.459
<v Mikhail Shaferman>In practice, that means helping them
harness advanced digital technologies like IoT

15
00:00:53.459 --> 00:00:58.419
<v Mikhail Shaferman>and edge computing to spot potential
issues long before they cause a problem.

16
00:00:59.349 --> 00:01:03.630
<v Mikhail Shaferman>Over the years I've seen just how
transformative even small changes can be.

17
00:01:03.990 --> 00:01:08.589
<v Mikhail Shaferman>A single new sensor or let's say analytic
tool can radically improve up time and

18
00:01:08.589 --> 00:01:13.250
<v Mikhail Shaferman>efficiency, and I'm truly excited to share
some of this real world experience today.

19
00:01:14.400 --> 00:01:19.029
<v Speaker 2>That is really great to hear, and I think
those real world examples will be very

20
00:01:19.029 --> 00:01:20.620
<v Speaker 2>valuable for our listeners.

21
00:01:21.160 --> 00:01:23.330
<v Speaker 2>So perhaps let's start abroad.

22
00:01:23.839 --> 00:01:28.440
<v Speaker 2>What do you see as the biggest operational
pressures facing automotive manufacturers

23
00:01:28.440 --> 00:01:28.699
<v Speaker 2>today?

24
00:01:30.349 --> 00:01:33.489
<v Mikhail Shaferman>Unplanned downtime is still the single
biggest pain point.

25
00:01:34.300 --> 00:01:38.980
<v Mikhail Shaferman>And it's not just an operational concern,
it's a business level risk.

26
00:01:40.019 --> 00:01:44.589
<v Speaker 2>So you're saying it's not just a factory
floor issue and it's really something that

27
00:01:44.589 --> 00:01:45.849
<v Speaker 2>impacts the entire business.

28
00:01:47.349 --> 00:01:53.050
<v Mikhail Shaferman>Exactly what's really striking is how it
intersects with other challenges these

29
00:01:53.050 --> 00:01:53.419
<v Mikhail Shaferman>days.

30
00:01:54.629 --> 00:01:59.470
<v Mikhail Shaferman>Automakers are asked to do more with less
managing, you know, high production

31
00:01:59.470 --> 00:02:05.069
<v Mikhail Shaferman>targets despite labor shortages, volatile
supply chains, and the constant pressure

32
00:02:05.069 --> 00:02:06.150
<v Mikhail Shaferman>to keep costs down.

33
00:02:07.000 --> 00:02:12.919
<v Mikhail Shaferman>And in the in that environment, every
minute of stoppage can feel like a crisis, not

34
00:02:12.919 --> 00:02:15.800
<v Mikhail Shaferman>just for the plant, but for the whole
supply chain.

35
00:02:17.869 --> 00:02:24.199
<v Mikhail Shaferman>Industry research puts the average cost of
an hour of downtime at over €20,000

36
00:02:24.830 --> 00:02:28.910
<v Mikhail Shaferman>sometimes much more than you factor in
logistics and penalties.

37
00:02:30.160 --> 00:02:35.360
<v Mikhail Shaferman>That's why maintenance has moved from the
back room to the boardroom, and it's now

38
00:02:35.360 --> 00:02:38.440
<v Mikhail Shaferman>absolutely crucial for performance and
competitiveness.

39
00:02:40.059 --> 00:02:44.070
<v Speaker 2>Right, and I think that's exactly where
predictive approaches come into play.

40
00:02:44.460 --> 00:02:49.050
<v Speaker 2>And as more manufacturers go digital,
yeah, predictive maintenance enters the

41
00:02:49.050 --> 00:02:49.440
<v Speaker 2>conversation.

42
00:02:49.740 --> 00:02:53.639
<v Speaker 2>But maybe let's discuss where exactly does
it fit.

43
00:02:53.860 --> 00:02:57.059
<v Speaker 2>Is it just a maintenance tool or a broader
business level?

44
00:02:58.940 --> 00:03:05.259
<v Mikhail Shaferman>It's a great question, and the answer is
that predictive maintenance is so much more

45
00:03:05.259 --> 00:03:06.160
<v Mikhail Shaferman>than just a tool.

46
00:03:06.419 --> 00:03:09.029
<v Mikhail Shaferman>It's a really strategic lever for
business.

47
00:03:09.619 --> 00:03:14.179
<v Mikhail Shaferman>And of course the first goal is to catch
and even predict failures before, you know,

48
00:03:14.259 --> 00:03:17.460
<v Mikhail Shaferman>they happen, so you avoid unexpected
downtime.

49
00:03:18.779 --> 00:03:22.360
<v Speaker 2>And beyond avoiding breakdowns, what's the
bigger picture benefit?

50
00:03:23.929 --> 00:03:29.809
<v Mikhail Shaferman>The real power of predictive maintenance
is how it links technical availability,

51
00:03:30.080 --> 00:03:34.660
<v Mikhail Shaferman>which simply means machines are ready and
working when you need them, with broader

52
00:03:34.660 --> 00:03:35.720
<v Mikhail Shaferman>business KPIs.

53
00:03:36.460 --> 00:03:42.839
<v Mikhail Shaferman>For example, we've seen companies cut
unplanned downtime by up to 50%, which has

54
00:03:43.110 --> 00:03:48.940
<v Mikhail Shaferman>line effects across quality, delivery
times, and ultimately customer satisfaction.

55
00:03:49.880 --> 00:03:53.960
<v Mikhail Shaferman>It's less about fixing what's broken and
more about creating.

56
00:03:54.759 --> 00:04:00.880
<v Mikhail Shaferman>A stable and high performance environment
where teams can focus on making great

57
00:04:00.880 --> 00:04:03.119
<v Mikhail Shaferman>vehicles rather than putting out fires.

58
00:04:04.259 --> 00:04:06.520
<v Speaker 2>Right, that makes a lot of sense actually.

59
00:04:07.100 --> 00:04:11.300
<v Speaker 2>But before we even get to prediction, I
think there is one fundamental step before

60
00:04:11.300 --> 00:04:13.089
<v Speaker 2>that, the data itself.

61
00:04:13.460 --> 00:04:17.640
<v Speaker 2>So how big of a hurdle is connectivity in
automotive plants?

62
00:04:19.220 --> 00:04:24.619
<v Mikhail Shaferman>Connectivity is absolutely the foundation,
and honestly it's often underestimated.

63
00:04:25.529 --> 00:04:29.929
<v Mikhail Shaferman>You know, many automotive plants,
especially ones with decades of history, rely on

64
00:04:29.929 --> 00:04:34.890
<v Mikhail Shaferman>brownfield equipment, machines, and
controllers that predate today's connected

65
00:04:34.890 --> 00:04:35.850
<v Mikhail Shaferman>factory models.

66
00:04:37.089 --> 00:04:41.730
<v Speaker 2>So now you're saying that just pulling
reliable data out of those older systems is

67
00:04:41.730 --> 00:04:42.670
<v Speaker 2>already a challenge.

68
00:04:43.929 --> 00:04:44.480
<v Mikhail Shaferman>Exactly.

69
00:04:44.859 --> 00:04:50.429
<v Mikhail Shaferman>The first real hurdle is simply getting
secure, reliable data out of those machines.

70
00:04:50.809 --> 00:04:54.730
<v Mikhail Shaferman>And at Siemens we work side by side with
customers to bridge this gap.

71
00:04:56.040 --> 00:05:01.339
<v Mikhail Shaferman>Using industrial age devices, secure
gateways, and of course standardized protocols

72
00:05:01.339 --> 00:05:03.720
<v Mikhail Shaferman>to ensure safe and seamless data
collection.

73
00:05:04.440 --> 00:05:10.059
<v Mikhail Shaferman>And once the data pipeline is established,
we are able to feed predictive platform

74
00:05:10.059 --> 00:05:15.579
<v Mikhail Shaferman>like Sensai, transforming a house of raw
machine data into valuable, actionable

75
00:05:15.720 --> 00:05:16.239
<v Mikhail Shaferman>insights.

76
00:05:17.130 --> 00:05:20.950
<v Mikhail Shaferman>And I would add this isn't a purely
technical step.

77
00:05:21.350 --> 00:05:25.549
<v Mikhail Shaferman>The conversation about data ownership and
cybersecurity is just as important.

78
00:05:27.320 --> 00:05:28.730
<v Speaker 2>All right, let's summarize it.

79
00:05:28.929 --> 00:05:32.029
<v Speaker 2>Connectivity is step 0 and predictive is
step 1.

80
00:05:32.290 --> 00:05:38.329
<v Speaker 2>And once both of that are in place, what
makes Sensi predictive maintenance

81
00:05:38.329 --> 00:05:40.350
<v Speaker 2>particularly suited for the automotive
industry?

82
00:05:42.339 --> 00:05:47.079
<v Mikhail Shaferman>You know, since I was purpose built with
the realities of automotive in mind.

83
00:05:48.049 --> 00:05:54.190
<v Mikhail Shaferman>First, it's cloud native and scales easily
from a few critical machines up to

84
00:05:54.929 --> 00:05:55.609
<v Mikhail Shaferman>entire fleets.

85
00:05:56.339 --> 00:05:59.040
<v Mikhail Shaferman>Covers several plants, and that's unique.

86
00:05:59.720 --> 00:06:04.910
<v Mikhail Shaferman>You know, is that it doesn't require users
to manually set up thousands of rules.

87
00:06:05.269 --> 00:06:10.299
<v Mikhail Shaferman>Instead, it leverages machine learning to
understand each asset's normal behavior

88
00:06:10.480 --> 00:06:13.239
<v Mikhail Shaferman>and automatically identifies anomalies.

89
00:06:14.109 --> 00:06:19.799
<v Mikhail Shaferman>This is a huge benefit for multi-shift,
high volume environment where, you know,

90
00:06:20.029 --> 00:06:25.589
<v Mikhail Shaferman>where just isn't time or often the
in-house expertise for endless programming.

91
00:06:26.799 --> 00:06:31.890
<v Mikhail Shaferman>And there it's a conveyor on line one or a
robotic arm in final assembly.

92
00:06:32.119 --> 00:06:37.880
<v Mikhail Shaferman>Sensii integrates right alongside existing
automation, so manufacturers gets the

93
00:06:37.880 --> 00:06:40.119
<v Mikhail Shaferman>benefits of predictive insights without
disruption.

94
00:06:42.100 --> 00:06:47.049
<v Speaker 2>Yeah, and I think that is really important
because ripping out old systems isn't

95
00:06:47.049 --> 00:06:48.059
<v Speaker 2>usually an option, right?

96
00:06:48.839 --> 00:06:53.269
<v Speaker 2>But let's say what happens if teams don't
feel ready internally?

97
00:06:53.649 --> 00:06:57.809
<v Speaker 2>What about plants that don't have data
scientists or condition mentoring experts?

98
00:06:59.589 --> 00:07:05.209
<v Mikhail Shaferman>That's a fantastic point, and quite
honestly, it's a challenge that comes up along

99
00:07:07.779 --> 00:07:11.989
<v Mikhail Shaferman>That's a fantastic point, and quite
honestly, it's a challenge that comes up all the

100
00:07:11.989 --> 00:07:12.329
<v Mikhail Shaferman>time.

101
00:07:13.130 --> 00:07:18.010
<v Mikhail Shaferman>You know, not every plant has a team of
data scientists or condition monitoring

102
00:07:18.010 --> 00:07:18.649
<v Mikhail Shaferman>specialists.

103
00:07:19.250 --> 00:07:20.489
<v Mikhail Shaferman>And that's perfectly OK.

104
00:07:21.649 --> 00:07:26.279
<v Mikhail Shaferman>Our data enhanced service contracts are
really designed with those customers in

105
00:07:26.279 --> 00:07:26.890
<v Mikhail Shaferman>mind.

106
00:07:27.250 --> 00:07:32.890
<v Mikhail Shaferman>With this approach, you don't just get
access to powerful analytic software, you get

107
00:07:32.890 --> 00:07:35.489
<v Mikhail Shaferman>a team of Siemens experts who partner with
you.

108
00:07:36.510 --> 00:07:42.049
<v Mikhail Shaferman>And they, these experts, handle the data
analysis, flag early signs of failure,

109
00:07:42.859 --> 00:07:47.630
<v Mikhail Shaferman>recommend concrete steps, and sometimes
could even support implementation.

110
00:07:48.609 --> 00:07:53.359
<v Mikhail Shaferman>For resource rich plants, this as a
service partnership means you still get the

111
00:07:53.359 --> 00:07:58.250
<v Mikhail Shaferman>predictive insights and proactive support
without needing to build out a whole new

112
00:07:58.250 --> 00:07:59.209
<v Mikhail Shaferman>department internally.

113
00:08:01.029 --> 00:08:05.269
<v Speaker 2>Yeah, and that's definitely a major win
for manufacturers who are already resource

114
00:08:05.269 --> 00:08:06.010
<v Speaker 2>stretched.

115
00:08:06.510 --> 00:08:11.220
<v Speaker 2>And now that more companies are scaling
digital efforts, how well does predictive

116
00:08:11.220 --> 00:08:15.350
<v Speaker 2>maintenance scale across plants, regions,
or even globally?

117
00:08:17.380 --> 00:08:22.160
<v Mikhail Shaferman>You know, scalability is one of the real
game changers in digital maintenance.

118
00:08:23.549 --> 00:08:28.350
<v Speaker 2>Meaning once you have solved it in one
plan, you can actually reuse this model

119
00:08:28.350 --> 00:08:29.029
<v Speaker 2>elsewhere.

120
00:08:29.829 --> 00:08:31.179
<v Mikhail Shaferman>Yes, exactly.

121
00:08:31.589 --> 00:08:37.390
<v Mikhail Shaferman>Once you have developed a predictive model
for, say, a specific type of fan or

122
00:08:37.390 --> 00:08:43.270
<v Mikhail Shaferman>robot, you can replicate it across
identical assets at other locations, accelerating

123
00:08:43.270 --> 00:08:48.929
<v Mikhail Shaferman>rollout dramatically and even better by
aggregating health data across an entire

124
00:08:48.929 --> 00:08:53.030
<v Mikhail Shaferman>fleet, which could mean thousands of
machines in different countries.

125
00:08:54.140 --> 00:08:58.640
<v Mikhail Shaferman>Automotive decision makers can benchmark
performance and spot risks from a single

126
00:08:58.640 --> 00:08:59.919
<v Mikhail Shaferman>centralized dashboard.

127
00:09:00.780 --> 00:09:05.840
<v Mikhail Shaferman>Imagine being able to prioritize
maintenance not just plant by plant but globally,

128
00:09:06.140 --> 00:09:10.549
<v Mikhail Shaferman>aligning efforts to maximize up time and
efficiency across all plants.

129
00:09:10.929 --> 00:09:13.179
<v Mikhail Shaferman>That's the power of scalable, predictive
maintenance.

130
00:09:14.989 --> 00:09:19.309
<v Speaker 2>And they think that leads now perfectly
into existing systems.

131
00:09:19.710 --> 00:09:22.909
<v Speaker 2>How does this complement things like clean
or TPM?

132
00:09:24.590 --> 00:09:30.590
<v Mikhail Shaferman>Absolutely, it's really about amplifying
what approaches like Lean and TPM already

133
00:09:30.590 --> 00:09:31.090
<v Mikhail Shaferman>do well.

134
00:09:32.099 --> 00:09:37.770
<v Mikhail Shaferman>Predictive maintenance, hence teams
real-time data-driven insights, making TPM

135
00:09:37.770 --> 00:09:40.179
<v Mikhail Shaferman>activities much more targeted and
efficient.

136
00:09:41.580 --> 00:09:48.460
<v Mikhail Shaferman>Instead of relying solely on periodic
checks or even intuition, maintenance

137
00:09:48.460 --> 00:09:50.820
<v Mikhail Shaferman>teams know exactly where to focus.

138
00:09:51.820 --> 00:09:57.059
<v Mikhail Shaferman>And if a component starts showing abnormal
vibration, for example, they can

139
00:09:57.059 --> 00:09:59.059
<v Mikhail Shaferman>proactively interfere before failure.

140
00:09:59.989 --> 00:10:04.630
<v Mikhail Shaferman>And this is not only boost technical
availability, ensuring machines are up and

141
00:10:04.630 --> 00:10:09.630
<v Mikhail Shaferman>running, but also frees up valuable time
and resources by directing energy where

142
00:10:09.630 --> 00:10:10.909
<v Mikhail Shaferman>it's actually needed.

143
00:10:13.200 --> 00:10:18.080
<v Speaker 2>And the closer we get to final assembly or
just in time delivery, the most I can

144
00:10:18.080 --> 00:10:18.400
<v Speaker 2>ever.

145
00:10:19.570 --> 00:10:19.919
<v Speaker 2>Oh, sorry.

146
00:10:20.820 --> 00:10:25.419
<v Speaker 2>And the closer we get to final assembly or
just in time delivery, the more every

147
00:10:25.419 --> 00:10:26.469
<v Speaker 2>second matters, right?

148
00:10:27.409 --> 00:10:30.059
<v Speaker 2>So how does predictive maintenance support
those processes?

149
00:10:31.840 --> 00:10:32.489
<v Mikhail Shaferman>Absolutely.

150
00:10:32.789 --> 00:10:39.070
<v Mikhail Shaferman>Nowhere is timing more critical than in
final assembly and just in time delivery.

151
00:10:39.429 --> 00:10:44.349
<v Mikhail Shaferman>In those areas, even a 3-minute delay can
throw off the entire flow, potentially

152
00:10:44.349 --> 00:10:47.789
<v Mikhail Shaferman>leading to missed shipments or costly
rework.

153
00:10:48.599 --> 00:10:52.679
<v Mikhail Shaferman>And predictive maintenance empowers teams
to anticipate issues.

154
00:10:53.489 --> 00:10:58.580
<v Mikhail Shaferman>They conveyor motor trending toward
failure, so repairs can be scheduled during

155
00:10:58.580 --> 00:11:01.039
<v Mikhail Shaferman>plant breaks rather than disrupting the
line.

156
00:11:02.460 --> 00:11:04.650
<v Speaker 2>Can you perhaps share a real world
example?

157
00:11:05.659 --> 00:11:06.369
<v Mikhail Shaferman>Yeah, sure.

158
00:11:07.179 --> 00:11:12.919
<v Mikhail Shaferman>In a recent case, we worked with a
customer to identify and correct a bearing issue

159
00:11:12.919 --> 00:11:14.419
<v Mikhail Shaferman>during an overnight window.

160
00:11:15.210 --> 00:11:19.090
<v Mikhail Shaferman>Preventing what would have been a full
morning's lost production.

161
00:11:19.900 --> 00:11:26.299
<v Mikhail Shaferman>And that's the kind of precision and
reliability just in time operations demand, and

162
00:11:26.299 --> 00:11:28.780
<v Mikhail Shaferman>it's where predictive maintenance really
shine.

163
00:11:30.799 --> 00:11:32.820
<v Speaker 2>Yeah, that's definitely a critical point.

164
00:11:33.280 --> 00:11:37.960
<v Speaker 2>And of course, as we know, companies also
need to justify the investment, right?

165
00:11:38.440 --> 00:11:41.000
<v Speaker 2>So is it ROI or risk-based?

166
00:11:42.609 --> 00:11:44.909
<v Mikhail Shaferman>This is the heart of the business case.

167
00:11:45.210 --> 00:11:51.890
<v Mikhail Shaferman>The financial ROI is clear lower downtime,
less crap, better asset utilization,

168
00:11:52.250 --> 00:11:56.010
<v Mikhail Shaferman>and very often, you know, reduced overtime
and rush orders.

169
00:11:57.219 --> 00:11:59.580
<v Speaker 2>But then there's also the risk angle,
right?

170
00:12:01.140 --> 00:12:01.840
<v Mikhail Shaferman>Correct.

171
00:12:02.380 --> 00:12:07.260
<v Mikhail Shaferman>By catching problems before they cascade,
you actually avoid last minute

172
00:12:07.260 --> 00:12:12.719
<v Mikhail Shaferman>firefighting that can lead to missed
targets or worse reputational damage.

173
00:12:13.469 --> 00:12:16.429
<v Mikhail Shaferman>What's more, you know, teams become more
confident.

174
00:12:16.559 --> 00:12:21.429
<v Mikhail Shaferman>They know the data has their backs, which
allows them to focus on continuous

175
00:12:21.429 --> 00:12:23.909
<v Mikhail Shaferman>improvement rather than just holding the
line.

176
00:12:25.729 --> 00:12:27.619
<v Speaker 2>Yeah, I think that makes total sense.

177
00:12:28.159 --> 00:12:31.940
<v Speaker 2>So Mikhail, let's perhaps close out by
looking to the future.

178
00:12:32.400 --> 00:12:36.500
<v Speaker 2>Where is predictive maintenance headed in
the next 3 to 5 years in automotive?

179
00:12:38.520 --> 00:12:43.359
<v Mikhail Shaferman>Looking ahead, we are already seeing the
next evolution fully integrated,

180
00:12:43.500 --> 00:12:45.299
<v Mikhail Shaferman>semi-autonomous maintenance.

181
00:12:46.630 --> 00:12:52.780
<v Mikhail Shaferman>Where predictive systems will soon not
just create alerts, but automatically

182
00:12:52.780 --> 00:12:58.510
<v Mikhail Shaferman>generate work orders, order the
replacement parts, and even slot maintenance into

183
00:12:58.510 --> 00:12:59.409
<v Mikhail Shaferman>production schedules.

184
00:13:00.210 --> 00:13:05.570
<v Mikhail Shaferman>For instance, if a key machine starts
drifting from its performance baseline, the

185
00:13:05.570 --> 00:13:10.280
<v Mikhail Shaferman>system can kick off a maintenance request,
check spare parts inventory, and

186
00:13:10.409 --> 00:13:14.010
<v Mikhail Shaferman>coordinate with operators without waiting
for manual intervention.

187
00:13:14.880 --> 00:13:20.340
<v Mikhail Shaferman>This level of integration means
maintenance becomes both proactive and seamless,

188
00:13:20.719 --> 00:13:24.400
<v Mikhail Shaferman>truly driving digital transformation in
automotive.

189
00:13:26.309 --> 00:13:28.530
<v Speaker 2>Wow, that was packed with insights.

190
00:13:28.739 --> 00:13:32.780
<v Speaker 2>Thank you very much, Mikhail, for walking
us through both the strategy and the

191
00:13:32.780 --> 00:13:35.159
<v Speaker 2>practical side of predictive maintenance
in automotive.

192
00:13:36.700 --> 00:13:38.099
<v Mikhail Shaferman>Sure, thanks for having me.

193
00:13:38.340 --> 00:13:42.700
<v Mikhail Shaferman>Always a pleasure to share how digital
services are delivering real results.

194
00:13:43.960 --> 00:13:48.239
<v Speaker 2>And to our listeners, thank you for
joining us on the trend detection podcast.

195
00:13:48.679 --> 00:13:53.559
<v Speaker 2>Be sure to check our SiMmens website for
more stories, insights, and tools to help

196
00:13:53.559 --> 00:13:54.979
<v Speaker 2>you on your digital journey.

197
00:13:55.479 --> 00:13:57.820
<v Speaker 2>Thanks for tuning in and we'll see you
next time.

198
00:14:01.059 --> 00:14:06.020
<v Speaker 1>Please like and subscribe on all major
podcast channels and find out more about

199
00:14:06.020 --> 00:14:09.539
<v Speaker 1>Sensei predictive maintenance at
Siemens.com.
