WEBVTT
Language: en-US

1
00:00:05.550 --> 00:00:06.510
<v Speaker 1>Good afternoon, everyone.

2
00:00:06.590 --> 00:00:12.109
<v Speaker 1>Welcome to today's session on maximize
drivetrain longevity and performance with

3
00:00:12.109 --> 00:00:13.189
<v Speaker 1>predictive maintenance.

4
00:00:13.500 --> 00:00:17.899
<v Speaker 1>The presentation will be delivered by
Rafael Larcher and moderated by Laura Timova.

5
00:00:18.340 --> 00:00:19.629
<v Speaker 1>We'll get going shortly.

6
00:00:19.909 --> 00:00:23.579
<v Speaker 1>Before we start though, I'd like to cover
some basic housekeeping items.

7
00:00:23.989 --> 00:00:28.709
<v Speaker 1>This presentation is being recorded and
will be made available via a link in the

8
00:00:28.709 --> 00:00:31.950
<v Speaker 1>follow-up email that you'll receive after
the session.

9
00:00:32.349 --> 00:00:34.759
<v Speaker 1>The session will run around 45 minutes.

10
00:00:35.040 --> 00:00:37.919
<v Speaker 1>It will only be better with your active
participation.

11
00:00:38.319 --> 00:00:43.330
<v Speaker 1>So please submit questions that you may
have throughout the presentation in the Q&amp;A

12
00:00:43.330 --> 00:00:47.139
<v Speaker 1>box that you'll see in the upper
right-hand corner of your viewing screen.

13
00:00:47.720 --> 00:00:52.040
<v Speaker 1>We're gonna be monitoring the question box
at all times and we'll get to them at the

14
00:00:52.040 --> 00:00:52.959
<v Speaker 1>end of the session.

15
00:00:53.779 --> 00:00:58.450
<v Speaker 1>And finally, a reminder that you will be
in listen-only mode during the entire

16
00:00:58.450 --> 00:00:59.419
<v Speaker 1>presentation.

17
00:00:59.939 --> 00:01:04.690
<v Speaker 1>So, without further ado, I will go, I will
pass it on to our presenter today, Rafael

18
00:01:04.690 --> 00:01:05.180
<v Speaker 1>Larcher.

19
00:01:06.440 --> 00:01:07.620
<v Rafael Larcher>Hey, I appreciate it.

20
00:01:09.029 --> 00:01:09.870
<v Rafael Larcher>Welcome everybody.

21
00:01:10.370 --> 00:01:13.150
<v Rafael Larcher>Thank you for taking the time off your
busy schedules.

22
00:01:13.769 --> 00:01:18.980
<v Rafael Larcher>Um, You see my name on the screen, my
contact email in case you need to reach out

23
00:01:18.980 --> 00:01:23.110
<v Rafael Larcher>after the presentation, but uh let's jump
right on.

24
00:01:23.230 --> 00:01:30.019
<v Rafael Larcher>So, you know, it seems a common theme for
many companies where they think predictive

25
00:01:30.019 --> 00:01:36.669
<v Rafael Larcher>maintenance is too complex or expensive to
implement, but today I like to challenge

26
00:01:36.669 --> 00:01:37.180
<v Rafael Larcher>that notion.

27
00:01:37.269 --> 00:01:43.180
<v Rafael Larcher>So whether you're a small company or a
large enterprise, Even a basic approach can

28
00:01:43.180 --> 00:01:46.199
<v Rafael Larcher>yield significant return on investment.

29
00:01:46.819 --> 00:01:52.139
<v Rafael Larcher>So let's jump right on, let's do a live
demo, and talk about how predictive

30
00:01:52.139 --> 00:01:57.980
<v Rafael Larcher>maintenance can keep your plant running
smoothly while maximizing your drivechain up

31
00:01:57.980 --> 00:01:58.339
<v Rafael Larcher>time.

32
00:01:59.150 --> 00:02:03.029
<v Rafael Larcher>Like Disa mentioned, if you guys have
questions, please, uh, just put it on on the

33
00:02:03.029 --> 00:02:03.620
<v Rafael Larcher>chat.

34
00:02:04.029 --> 00:02:08.389
<v Rafael Larcher>We're gonna try to tackle them throughout
the presentation and at the end of it as

35
00:02:08.389 --> 00:02:08.770
<v Rafael Larcher>well.

36
00:02:10.169 --> 00:02:17.080
<v Rafael Larcher>So, Let's look at some figures from the
IEA World Energy Report a

37
00:02:17.080 --> 00:02:17.880
<v Rafael Larcher>few years back.

38
00:02:18.039 --> 00:02:24.759
<v Rafael Larcher>So they said the industrial sector
accounts for over 1/3 of the

39
00:02:24.759 --> 00:02:26.919
<v Rafael Larcher>entire world's electrical energy
consumption.

40
00:02:27.910 --> 00:02:34.830
<v Rafael Larcher>And about 70% of that energy is
represented by billions of electrical

41
00:02:34.830 --> 00:02:37.389
<v Rafael Larcher>drivetrain installed worldwide.

42
00:02:39.369 --> 00:02:45.690
<v Rafael Larcher>When you look at Drive train, we're not
only talking about the motors up top, but

43
00:02:46.270 --> 00:02:51.630
<v Rafael Larcher>the whole connected payload, the
gearboxes, and the couplings, and then of course,

44
00:02:51.869 --> 00:02:56.460
<v Rafael Larcher>the application itself, whether they are
pumps, fans, compressors, any other type of

45
00:02:56.460 --> 00:03:00.250
<v Rafael Larcher>application, and not to forget the VFDs as
well.

46
00:03:01.539 --> 00:03:07.860
<v Rafael Larcher>We can keep a set of eyes 24/7 on the
condition and performance of these components

47
00:03:07.860 --> 00:03:12.839
<v Rafael Larcher>with our sensor modules and our AI-based
software solutions.

48
00:03:14.750 --> 00:03:16.729
<v Rafael Larcher>Going back to the report figures.

49
00:03:18.119 --> 00:03:24.940
<v Rafael Larcher>They say about half up to up to 50% of
that energy in industrial operations

50
00:03:25.240 --> 00:03:26.360
<v Rafael Larcher>simply wasted.

51
00:03:28.919 --> 00:03:32.100
<v Rafael Larcher>Funny how they categorize those wastes.

52
00:03:32.199 --> 00:03:37.279
<v Rafael Larcher>So they put into three different buckets,
and we can briefly talk about them over

53
00:03:37.279 --> 00:03:37.570
<v Rafael Larcher>here.

54
00:03:37.960 --> 00:03:39.320
<v Rafael Larcher>First one on the left.

55
00:03:40.649 --> 00:03:44.750
<v Rafael Larcher>Is waste as a result of products being
dimensioned incorrectly.

56
00:03:45.759 --> 00:03:50.199
<v Rafael Larcher>If they were undersized and then installed
to the equipment, there's not, not much

57
00:03:50.199 --> 00:03:54.479
<v Rafael Larcher>we can do, right, but replace them with
the proper components, but at that time,

58
00:03:54.520 --> 00:03:59.610
<v Rafael Larcher>it's a waste of material, waste of energy
to produce new products, um, and also a

59
00:03:59.610 --> 00:04:03.639
<v Rafael Larcher>waste of the actual workforce time to
replace them, if you think about it.

60
00:04:04.080 --> 00:04:09.360
<v Rafael Larcher>More often than not though, engineers tend
to actually oversize the drivetrain

61
00:04:09.360 --> 00:04:10.080
<v Rafael Larcher>equipment.

62
00:04:10.639 --> 00:04:16.279
<v Rafael Larcher>And as a result of that, those products
may or may not be operating at their optimum

63
00:04:16.279 --> 00:04:22.420
<v Rafael Larcher>efficient conditions, leading to the
second waste buck bucket um of that report,

64
00:04:22.519 --> 00:04:26.890
<v Rafael Larcher>which is the middle of the slide when they
are operated inefficiently.

65
00:04:28.100 --> 00:04:32.980
<v Rafael Larcher>As a consequence to that, potentially
leading to faulty or low quality products and

66
00:04:32.980 --> 00:04:37.739
<v Rafael Larcher>processes, which again, it's a waste of
resources, material, energy, and the actual

67
00:04:37.739 --> 00:04:39.519
<v Rafael Larcher>workforce to work on them.

68
00:04:40.399 --> 00:04:43.500
<v Rafael Larcher>Here's also where the lack of a
maintenance strategy.

69
00:04:44.660 --> 00:04:49.230
<v Rafael Larcher>Could accelerate wear and tear on these
devices, leading them to the 3rd waste

70
00:04:49.230 --> 00:04:49.890
<v Rafael Larcher>bucket.

71
00:04:50.679 --> 00:04:55.809
<v Rafael Larcher>On the right of this slide when products
fail unexpectedly, incurring then in

72
00:04:55.809 --> 00:05:01.470
<v Rafael Larcher>unplanned downtimes, and here again, waste
of the workforce and waste of resources.

73
00:05:02.290 --> 00:05:05.540
<v Rafael Larcher>When we talk about predictive maintenance
for your drive train.

74
00:05:06.600 --> 00:05:11.480
<v Rafael Larcher>We are aiming to reduce those two buckets,
right, so you can maximize again the

75
00:05:11.480 --> 00:05:15.820
<v Rafael Larcher>production while minimizing any
operational expenditure.

76
00:05:16.750 --> 00:05:20.549
<v Rafael Larcher>We do have solutions for when products are
dimensioned incorrectly for simulation

77
00:05:20.549 --> 00:05:23.910
<v Rafael Larcher>and validation, but we're not gonna be
covering on today's presentation.

78
00:05:23.950 --> 00:05:28.470
<v Rafael Larcher>We're gonna be focusing on when the
products are deployed into the shop floor.

79
00:05:30.640 --> 00:05:34.459
<v Rafael Larcher>So, how about we start with uh a poll
question here.

80
00:05:34.630 --> 00:05:41.459
<v Rafael Larcher>Um, I'd like to gauge the audience status
or strategy when it comes to maintenance

81
00:05:41.559 --> 00:05:45.480
<v Rafael Larcher>or maintaining their drivetrain equipment,
and again, I'm talking about the VFDs,

82
00:05:45.540 --> 00:05:47.690
<v Rafael Larcher>the motors, couplings, gearboxes.

83
00:05:48.119 --> 00:05:49.720
<v Rafael Larcher>As well as the connected load.

84
00:05:49.880 --> 00:05:54.739
<v Rafael Larcher>So, curious to hear where the audience is
in that regard.

85
00:05:55.279 --> 00:05:59.079
<v Rafael Larcher>So if you please could select uh the
different options that we have on the pole, I

86
00:05:59.079 --> 00:06:00.899
<v Rafael Larcher>think Laura has that on the screen.

87
00:06:02.019 --> 00:06:08.859
<v Laura>Yeah, so, uh, if everyone can just, um,
answer the question, Rafael, do you want me

88
00:06:08.859 --> 00:06:09.739
<v Laura>to read it out?

89
00:06:10.690 --> 00:06:13.140
<v Rafael Larcher>Um, you can read it out, Laura, please.

90
00:06:13.260 --> 00:06:13.809
<v Rafael Larcher>Thank you.

91
00:06:14.239 --> 00:06:18.500
<v Laura>Um, what's your maintenance strategy for
the installed drive chain equipment?

92
00:06:19.149 --> 00:06:24.980
<v Laura>Um, includes VFDs, motors, couplings,
gearboxes, and connected equipment, and then

93
00:06:24.980 --> 00:06:30.779
<v Laura>either reactive maintenance, preventative,
or fixed interval maintenance, predictive

94
00:06:30.779 --> 00:06:33.359
<v Laura>maintenance, or prescriptive maintenance.

95
00:06:34.709 --> 00:06:35.309
<v Rafael Larcher>Thank you, Laura.

96
00:06:35.429 --> 00:06:40.220
<v Rafael Larcher>While the audience is answering that, uh,
really quickly, let's talk about the

97
00:06:40.220 --> 00:06:41.450
<v Rafael Larcher>differences between them, right?

98
00:06:41.579 --> 00:06:46.589
<v Rafael Larcher>So if we look at a chart where we plot the
cost and risk of failure versus the

99
00:06:46.589 --> 00:06:51.809
<v Rafael Larcher>equipment health and performance, Over
time, that performance and the risk of

100
00:06:51.809 --> 00:06:56.450
<v Rafael Larcher>failure degrades quickly once the
equipment starts to fail, and if you're doing

101
00:06:56.450 --> 00:06:58.130
<v Rafael Larcher>nothing, you're being reactive.

102
00:06:58.250 --> 00:07:00.489
<v Rafael Larcher>You don't basically don't have time to
react.

103
00:07:00.690 --> 00:07:03.890
<v Rafael Larcher>You're doing the repairs after damage is
done, that's costly.

104
00:07:05.410 --> 00:07:09.609
<v Rafael Larcher>Some folks, I would say most of the
companies out there is just doing a fixed time

105
00:07:09.609 --> 00:07:14.950
<v Rafael Larcher>intervals, a preventive maintenance
schedule where products may or may not be in a,

106
00:07:15.679 --> 00:07:19.470
<v Rafael Larcher>Um, accelerated wear and tear condition
when the maintenance team is deployed.

107
00:07:20.429 --> 00:07:21.700
<v Rafael Larcher>Where we want to lead.

108
00:07:22.609 --> 00:07:27.010
<v Rafael Larcher>The customers and companies too are
predictive and prescriptive maintenance, right?

109
00:07:27.089 --> 00:07:32.760
<v Rafael Larcher>Those are the leading strategies um where
sensor modules paired with AI-based

110
00:07:33.130 --> 00:07:38.890
<v Rafael Larcher>software keep that 24/7 set of eyes and
notify you a set of, ahead of time, I should

111
00:07:38.890 --> 00:07:40.790
<v Rafael Larcher>say, when issues start to develop.

112
00:07:41.369 --> 00:07:45.769
<v Rafael Larcher>The main goal here is, of course, to give
you time to schedule your maintenance

113
00:07:45.769 --> 00:07:49.459
<v Rafael Larcher>checks, as well as to procure the spare
parts as needed.

114
00:07:50.829 --> 00:07:55.339
<v Rafael Larcher>Few have achieved prescriptive and
predictive maintenance, I should say, at a

115
00:07:55.339 --> 00:08:01.260
<v Rafael Larcher>reasonable scale, where regenerative AI
models are the catalyst behind the scenes,

116
00:08:01.339 --> 00:08:01.540
<v Rafael Larcher>right?

117
00:08:01.700 --> 00:08:07.820
<v Rafael Larcher>These AI agents not only predict future
issues, but they can also guide their users

118
00:08:07.820 --> 00:08:10.730
<v Rafael Larcher>through them, how to fix them and interact
with other software.

119
00:08:11.019 --> 00:08:13.920
<v Rafael Larcher>They can generate tickets to issue to your
maintenance department.

120
00:08:14.450 --> 00:08:20.200
<v Rafael Larcher>They can send a uh a spare part purchase
order to your procurement team, so the

121
00:08:20.200 --> 00:08:22.390
<v Rafael Larcher>systems not start talking to each other.

122
00:08:24.779 --> 00:08:29.459
<v Rafael Larcher>Laura, if we could go back to the poll
results and see uh where the audience is as

123
00:08:29.459 --> 00:08:31.239
<v Rafael Larcher>far as their maintenance strategy.

124
00:08:32.200 --> 00:08:32.400
<v Rafael Larcher>Yeah,

125
00:08:32.559 --> 00:08:38.719
<v Laura>so we have most of them fall under
preventative fixed interval maintenance and then

126
00:08:38.719 --> 00:08:41.239
<v Laura>about the other half in the predictive
maintenance.

127
00:08:41.400 --> 00:08:48.000
<v Laura>So more on the side we want, but still has
a big shift of where we can be.

128
00:08:49.080 --> 00:08:53.320
<v Rafael Larcher>That is interesting, as kind of a reality
as we see out there.

129
00:08:53.460 --> 00:08:57.130
<v Rafael Larcher>Most of the folks out there are just doing
a fixed interval strategy.

130
00:08:57.890 --> 00:09:02.609
<v Rafael Larcher>Uh, glad to see about 1/3, over 1/3 of the
audience is already doing predictive

131
00:09:02.609 --> 00:09:04.119
<v Rafael Larcher>maintenance, that's encouraging.

132
00:09:04.650 --> 00:09:10.489
<v Rafael Larcher>Um, of course, ideally trying to move the
reactive team, um, and somewhat of the

133
00:09:10.489 --> 00:09:16.780
<v Rafael Larcher>preventive team to the, um, Predictive or
and ideally to the prescriptive scenarios

134
00:09:16.780 --> 00:09:20.830
<v Rafael Larcher>as well, but um Thanks folks for, for
sharing where you are.

135
00:09:20.909 --> 00:09:26.090
<v Rafael Larcher>Um, luckily, You're gonna see value after
this uh presentation, so we can start

136
00:09:26.090 --> 00:09:30.090
<v Rafael Larcher>moving you guys towards the preventive and
prescriptive.

137
00:09:32.460 --> 00:09:33.599
<v Rafael Larcher>All right, let's uh.

138
00:09:35.119 --> 00:09:40.280
<v Rafael Larcher>Move forward here, so with those poll
results in mind, folks, I'd like to throw a

139
00:09:40.280 --> 00:09:40.859
<v Rafael Larcher>question here.

140
00:09:41.039 --> 00:09:42.219
<v Rafael Larcher>I'm gonna read it out loud.

141
00:09:43.080 --> 00:09:49.900
<v Rafael Larcher>Is a return on investment of one year or
less an attractive investment to implement

142
00:09:50.000 --> 00:09:54.679
<v Rafael Larcher>cloud-based predictive maintenance
strategies to your installed drivetrain

143
00:09:54.679 --> 00:09:55.299
<v Rafael Larcher>equipment?

144
00:09:58.169 --> 00:10:03.169
<v Rafael Larcher>Or better yet, which of your customers are
currently asking for these solutions

145
00:10:03.169 --> 00:10:03.809
<v Rafael Larcher>right now?

146
00:10:05.650 --> 00:10:10.809
<v Rafael Larcher>In a couple of minutes, I'll give you 3
customer examples who have indeed achieved

147
00:10:10.809 --> 00:10:14.169
<v Rafael Larcher>ROIs in less than 1 year with our latest
solutions.

148
00:10:14.969 --> 00:10:18.159
<v Rafael Larcher>But, you know, here's why they achieved
that.

149
00:10:18.690 --> 00:10:21.460
<v Rafael Larcher>So I'm going from left to right on this
slide.

150
00:10:21.869 --> 00:10:26.510
<v Rafael Larcher>First one, of course, optimization of
energy consumption and the CO2 emissions.

151
00:10:27.010 --> 00:10:29.650
<v Rafael Larcher>Uh, we've seen the reduction by up to 10%.

152
00:10:29.969 --> 00:10:35.169
<v Rafael Larcher>Huge savings if you think about these
devices are running for 1020, 30+ years,

153
00:10:35.250 --> 00:10:35.609
<v Rafael Larcher>right?

154
00:10:36.130 --> 00:10:37.799
<v Rafael Larcher>Big, big savings potential there.

155
00:10:38.700 --> 00:10:44.919
<v Rafael Larcher>Uh, if we look at early identification of
motor failures, um, therefore, of course,

156
00:10:44.979 --> 00:10:49.739
<v Rafael Larcher>prolonging their lifetime and reducing the
overall maintenance costs, that's a big

157
00:10:49.739 --> 00:10:54.700
<v Rafael Larcher>chunk of savings too, and we've seen up to
about a 30% savings on those different

158
00:10:54.700 --> 00:10:55.960
<v Rafael Larcher>buckets as well.

159
00:10:56.619 --> 00:11:02.299
<v Rafael Larcher>And then detection of inefficiencies on
the drivetrain, also increasing the plant

160
00:11:02.299 --> 00:11:05.320
<v Rafael Larcher>productivity with some interesting figures
there as well.

161
00:11:06.010 --> 00:11:09.369
<v Rafael Larcher>These are coming from, from Siemens
factories, these are coming from our customers

162
00:11:09.369 --> 00:11:11.640
<v Rafael Larcher>using um our solutions.

163
00:11:12.210 --> 00:11:17.530
<v Rafael Larcher>So, big savings and we are, they are
achieving, you know, ROIs within a year or

164
00:11:17.530 --> 00:11:20.729
<v Rafael Larcher>less, very attractive um return on
investment.

165
00:11:22.739 --> 00:11:28.070
<v Rafael Larcher>So Exactly which conditions can we monitor
with, with our sensors?

166
00:11:30.010 --> 00:11:34.849
<v Rafael Larcher>These are uh one of our latest
introductions in the market, but if you think about

167
00:11:34.849 --> 00:11:39.409
<v Rafael Larcher>some of the most common motor failures,
you know, bearings, kind of number one to

168
00:11:39.409 --> 00:11:43.030
<v Rafael Larcher>come to mind, so we can keep an eye on the
bearing, wear and tears.

169
00:11:43.849 --> 00:11:49.419
<v Rafael Larcher>Um, how the balance or the lack of in, in
the motor, if the shaft, it starts to

170
00:11:49.419 --> 00:11:54.210
<v Rafael Larcher>misalign with the coupling with the
connected application, what type of resonant

171
00:11:54.210 --> 00:11:57.780
<v Rafael Larcher>points are developed that you want to skip
those frequencies or those speeds.

172
00:11:58.500 --> 00:12:03.000
<v Rafael Larcher>Uh, you know, motor temperatures, of
course, energy efficiency and some other.

173
00:12:03.799 --> 00:12:07.770
<v Rafael Larcher>Variables as well, but you, you can have
an idea of the mechanical conditions that

174
00:12:07.770 --> 00:12:12.210
<v Rafael Larcher>we can keep an eye and monitor the
condition of these, these assets.

175
00:12:13.099 --> 00:12:18.729
<v Rafael Larcher>And when I say drive train, those same
elements, those same analysis and conditions

176
00:12:18.909 --> 00:12:22.750
<v Rafael Larcher>could apply to the, connect to the
application as well, whether they are fans,

177
00:12:22.830 --> 00:12:29.630
<v Rafael Larcher>compressors, um, I have an example here
for, for a pump, where by adding the

178
00:12:29.630 --> 00:12:35.270
<v Rafael Larcher>sensor to the actual pump, because these
devices have now acoustic sensors, they can

179
00:12:35.270 --> 00:12:41.210
<v Rafael Larcher>actually listen to the pump and start
detecting clogging, cavitation, and other um

180
00:12:41.210 --> 00:12:42.750
<v Rafael Larcher>ultrasound related.

181
00:12:43.239 --> 00:12:48.479
<v Rafael Larcher>Um, developments or anomalies, and then
again alert the users beforehand that they

182
00:12:48.479 --> 00:12:50.780
<v Rafael Larcher>need to do some sort of maintenance to
their equipment.

183
00:12:54.460 --> 00:12:59.780
<v Rafael Larcher>So, I promise I'll give you guys 3
examples of customers who achieved that ROI um

184
00:13:01.010 --> 00:13:01.520
<v Rafael Larcher>within a year.

185
00:13:01.650 --> 00:13:07.210
<v Rafael Larcher>Of course, everything we do, we also
validate within our own facilities, uh, our own

186
00:13:07.210 --> 00:13:07.609
<v Rafael Larcher>factories.

187
00:13:07.679 --> 00:13:14.250
<v Rafael Larcher>In this case, we deploy them to some of
HVACs and pumps and compressors in our, some

188
00:13:14.250 --> 00:13:18.570
<v Rafael Larcher>of our factories in Europe, and we did got
ROIs in less than a year with reduction

189
00:13:18.570 --> 00:13:20.849
<v Rafael Larcher>of maintenance service checks.

190
00:13:21.210 --> 00:13:24.500
<v Rafael Larcher>And we were able to actually avoid a
failure within the first year.

191
00:13:26.869 --> 00:13:32.429
<v Rafael Larcher>Now the customer, um, water and
wastewater, Scottish Water up in Scotland, they

192
00:13:32.429 --> 00:13:37.710
<v Rafael Larcher>started small with a proof of concept to
make sure the solution would achieve the

193
00:13:37.710 --> 00:13:42.650
<v Rafael Larcher>results they were aiming to, and they
quickly observed that and then scaled

194
00:13:42.960 --> 00:13:47.989
<v Rafael Larcher>throughout the dozens of facilities
throughout um uh Scotland, and you see some of

195
00:13:47.989 --> 00:13:50.409
<v Rafael Larcher>the figures that they're able to achieve
there as well.

196
00:13:52.349 --> 00:13:58.469
<v Rafael Larcher>Third customer that was actually uh a
partnership with Grunt Forces pumps, and that

197
00:13:58.469 --> 00:14:04.010
<v Rafael Larcher>was for a food and beverage company,
Danish Crown, where this was all about

198
00:14:04.130 --> 00:14:10.289
<v Rafael Larcher>maximizing the up time and the asset
transparency, where they wanted to

199
00:14:10.909 --> 00:14:17.070
<v Rafael Larcher>work together with the pump, OEM
Groundfalls in this case, to keep remote monitoring

200
00:14:17.070 --> 00:14:21.690
<v Rafael Larcher>of their devices so they could fine-tune
the application and then Um,

201
00:14:21.929 --> 00:14:26.330
<v Rafael Larcher>deploy maintenance checks before any
issues, um, arise.

202
00:14:27.429 --> 00:14:29.229
<v Rafael Larcher>Good, good examples of the solutions.

203
00:14:29.309 --> 00:14:34.849
<v Rafael Larcher>Uh, these are all available as public
references, YouTube videos, so you can um

204
00:14:34.849 --> 00:14:39.950
<v Rafael Larcher>check what were, what the challenges were
and how they overcame those with these

205
00:14:39.950 --> 00:14:40.650
<v Rafael Larcher>solutions.

206
00:14:45.210 --> 00:14:47.880
<v Rafael Larcher>How did those customers achieve those
results?

207
00:14:48.049 --> 00:14:54.059
<v Rafael Larcher>Of course, they needed some sort of
connectivity to gather the, the drivetrain data

208
00:14:54.500 --> 00:14:55.830
<v Rafael Larcher>and send it to the cloud.

209
00:14:56.770 --> 00:15:03.049
<v Rafael Larcher>Um, for that, they used our connection
module, CM for short, CMIOT

210
00:15:03.630 --> 00:15:10.369
<v Rafael Larcher>paired with our cloud-based analytics app
called DriveTrain Analyzer, in this case,

211
00:15:10.409 --> 00:15:11.030
<v Rafael Larcher>cloud.

212
00:15:12.289 --> 00:15:17.880
<v Rafael Larcher>The hardware itself, it's a plug and play
wireless device that you attach to the

213
00:15:17.880 --> 00:15:23.250
<v Rafael Larcher>motor, and on board to the cloud via any
Wi Fi connection.

214
00:15:24.799 --> 00:15:29.440
<v Rafael Larcher>So really quickly here, some of the
highlights of this device, you see a nice

215
00:15:29.440 --> 00:15:35.280
<v Rafael Larcher>picture of this device connected to a
motor, but, you know, powerful signal sensing,

216
00:15:35.359 --> 00:15:39.239
<v Rafael Larcher>we can measure vibration on all the three
different axes for the motor or the

217
00:15:39.239 --> 00:15:44.960
<v Rafael Larcher>connected load, uh, motor temperature,
magnetic field, so we can calculate speed and

218
00:15:44.960 --> 00:15:50.039
<v Rafael Larcher>torque for things like speed, um, energy
calculations or detection of different

219
00:15:50.039 --> 00:15:51.150
<v Rafael Larcher>operating points.

220
00:15:52.070 --> 00:15:57.020
<v Rafael Larcher>As I mentioned, also an acoustic and
ultrasound sensor, so we can listen to the

221
00:15:57.020 --> 00:16:01.010
<v Rafael Larcher>application uh for specific anomalies
being developed.

222
00:16:01.890 --> 00:16:03.530
<v Rafael Larcher>Flexible power options.

223
00:16:05.479 --> 00:16:11.679
<v Rafael Larcher>24 volts wired, and or uh battery
operated, we have a long lasting and fuel

224
00:16:11.679 --> 00:16:14.219
<v Rafael Larcher>replaceable battery, can last up to 4
years.

225
00:16:16.919 --> 00:16:22.039
<v Rafael Larcher>Always thinking about safe and secure data
transfers, uh, for cybersecurity, of

226
00:16:22.039 --> 00:16:22.530
<v Rafael Larcher>course.

227
00:16:22.799 --> 00:16:28.919
<v Rafael Larcher>This is aligned with the highest security
standards, um, up to the WPA 3 enterprise

228
00:16:28.919 --> 00:16:31.640
<v Rafael Larcher>protocols, dual-band Wi Fi.

229
00:16:32.700 --> 00:16:35.669
<v Rafael Larcher>And we also offer MQTT protocol.

230
00:16:36.440 --> 00:16:42.760
<v Rafael Larcher>All that means customers don't necessarily
have to use our tools, our analytics tool

231
00:16:42.760 --> 00:16:43.630
<v Rafael Larcher>up in the cloud.

232
00:16:44.039 --> 00:16:49.320
<v Rafael Larcher>They can localize and just send the raw
data from the sensors to their own analytic

233
00:16:49.320 --> 00:16:55.000
<v Rafael Larcher>apps, and then do their own analysis
locally without the need to use any of our

234
00:16:55.000 --> 00:16:56.530
<v Rafael Larcher>cloud-based solutions.

235
00:16:57.119 --> 00:16:59.419
<v Rafael Larcher>And of course, you know, rugged design.

236
00:17:00.239 --> 00:17:06.829
<v Rafael Larcher>Uh, with IP 66 protection and ATTA
certification for, for hazardous operations,

237
00:17:06.910 --> 00:17:09.619
<v Rafael Larcher>either zone 2 or zone 22.

238
00:17:14.029 --> 00:17:18.328
<v Rafael Larcher>As I mentioned, once the device is on
boarded to the cloud via any.

239
00:17:19.409 --> 00:17:23.499
<v Rafael Larcher>Wi Fi router doesn't have to be a Siemens
router, could be any Wi Fi router.

240
00:17:24.098 --> 00:17:30.359
<v Rafael Larcher>Then the Drivetrain analyzer app leverages
the sensor data, and with, with its

241
00:17:30.359 --> 00:17:35.218
<v Rafael Larcher>pre-trained AI models, start generating
all the analytics and the monitoring

242
00:17:35.218 --> 00:17:35.958
<v Rafael Larcher>functions.

243
00:17:37.739 --> 00:17:42.689
<v Rafael Larcher>Uh, there are 3 main use cases for this
app, fleet management, so you have that

244
00:17:42.689 --> 00:17:47.619
<v Rafael Larcher>transparency, that holistic view of your
assets throughout the world, if you have

245
00:17:47.619 --> 00:17:51.479
<v Rafael Larcher>different plants, predictive maintenance,
obviously, that's what we've been talking

246
00:17:51.780 --> 00:17:54.459
<v Rafael Larcher>today, and energy efficiency as well.

247
00:17:55.709 --> 00:17:59.189
<v Rafael Larcher>We're introducing our operations copilot.

248
00:17:59.270 --> 00:18:05.199
<v Rafael Larcher>It's still in beta testing, uh, where
users can actually have a conversation, a

249
00:18:05.400 --> 00:18:08.430
<v Rafael Larcher>conversational interface, I should say,
and talk to their data.

250
00:18:08.510 --> 00:18:14.109
<v Rafael Larcher>We like to say that and get in plain
English, what's going on, how to fix them, and

251
00:18:14.109 --> 00:18:14.709
<v Rafael Larcher>things like that.

252
00:18:14.859 --> 00:18:20.949
<v Rafael Larcher>So I'll do a live demo in a few minutes,
but first, let's watch a quick video where

253
00:18:20.949 --> 00:18:24.770
<v Rafael Larcher>we show these uh use cases in action.

254
00:18:29.869 --> 00:18:34.750
<v Speaker 4>Once your CMIOT sensor is connected to the
cloud, Drivetrain Analyzer cloud uses

255
00:18:34.750 --> 00:18:37.530
<v Speaker 4>advanced AI to give you insights into your
equipment.

256
00:18:37.790 --> 00:18:42.099
<v Speaker 4>For instance, it continuously monitors
motor health, tracking bearing conditions,

257
00:18:42.229 --> 00:18:45.300
<v Speaker 4>detecting unbalance, and checking for
misalignment.

258
00:18:45.670 --> 00:18:49.949
<v Speaker 4>All this is shown in a simple traffic
light system, so you easily know when there's

259
00:18:49.949 --> 00:18:50.689
<v Speaker 4>an issue.

260
00:18:51.699 --> 00:18:54.890
<v Speaker 4>Ever wondered if your pumps are operating
efficiently?

261
00:18:55.209 --> 00:19:00.030
<v Speaker 4>Our system can detect clogging, monitor
power loss, and evaluate pump efficiency,

262
00:19:00.449 --> 00:19:02.709
<v Speaker 4>all visualized in customizable charts.

263
00:19:03.050 --> 00:19:04.239
<v Speaker 4>But we don't stop there.

264
00:19:04.410 --> 00:19:08.479
<v Speaker 4>Our platform also identifies resonance
points that could damage your machinery, and

265
00:19:08.479 --> 00:19:12.890
<v Speaker 4>if your motor is driven by a frequency
converter, we can detect all operating points

266
00:19:12.890 --> 00:19:14.530
<v Speaker 4>that your motor is operating in.

267
00:19:15.880 --> 00:19:17.949
<v Speaker 4>Now let's talk about vibration monitoring.

268
00:19:18.160 --> 00:19:20.819
<v Speaker 4>Depending on your needs, you can choose
from several options.

269
00:19:21.199 --> 00:19:25.239
<v Speaker 4>And if you're not sure which one to pick,
simply activate intelligent vibration

270
00:19:25.239 --> 00:19:26.839
<v Speaker 4>monitoring with a single click.

271
00:19:27.239 --> 00:19:31.099
<v Speaker 4>The AI will take care of the rest,
checking for any problems related to your motor.

272
00:19:31.199 --> 00:19:34.640
<v Speaker 4>All alarms are logged and you'll receive
email notifications to keep your

273
00:19:34.640 --> 00:19:35.939
<v Speaker 4>maintenance team informed.

274
00:19:37.160 --> 00:19:40.290
<v Speaker 4>Drivetrain analyzer cloud also helps you
save energy.

275
00:19:40.640 --> 00:19:45.199
<v Speaker 4>You can monitor energy consumption, CO2
emissions, and even the costs.

276
00:19:45.520 --> 00:19:49.560
<v Speaker 4>If an inefficient motor is detected, the
system will automatically recommend a more

277
00:19:49.560 --> 00:19:50.900
<v Speaker 4>efficient alternative.

278
00:19:51.560 --> 00:19:55.670
<v Speaker 4>This is just a glimpse of what drivetrain
analyzer cloud can do for your operations.

279
00:19:55.920 --> 00:19:59.729
<v Speaker 4>Imagine the time, money, and headaches
you'll save with this level of insight.

280
00:20:00.119 --> 00:20:03.219
<v Speaker 4>Ready to take your drivetrain to the next
level of efficiency?

281
00:20:04.060 --> 00:20:04.069
<v Speaker 4>OK

282
00:20:10.750 --> 00:20:11.239
<v Rafael Larcher>All righty.

283
00:20:11.339 --> 00:20:12.650
<v Rafael Larcher>Pretty cool video, folks.

284
00:20:12.869 --> 00:20:17.729
<v Rafael Larcher>Um, As I mentioned before, if you have any
questions, you know, feel free to put

285
00:20:17.729 --> 00:20:18.449
<v Rafael Larcher>them on the chat.

286
00:20:18.589 --> 00:20:24.400
<v Rafael Larcher>We're going to address them in a few
minutes, but I know the video was maybe a

287
00:20:24.400 --> 00:20:29.000
<v Rafael Larcher>little difficult to see, but as I
mentioned, I'll do a live demo and show that live

288
00:20:29.000 --> 00:20:29.589
<v Rafael Larcher>in a second.

289
00:20:30.680 --> 00:20:33.609
<v Rafael Larcher>Before we do that, though, how about we do
a 2nd poll?

290
00:20:34.699 --> 00:20:41.500
<v Rafael Larcher>And get the audience uh responses where
about how they are currently monitoring

291
00:20:41.500 --> 00:20:43.920
<v Rafael Larcher>the performance of their drive train
equipment.

292
00:20:44.459 --> 00:20:48.060
<v Rafael Larcher>So Laura, if you could help me out here
reading the, the question out loud, I

293
00:20:48.060 --> 00:20:48.260
<v Rafael Larcher>appreciate it.

294
00:20:48.329 --> 00:20:48.420
<v Rafael Larcher>Yeah,

295
00:20:48.469 --> 00:20:52.819
<v Laura>of course, yeah, we'd love to know how
you're currently monitoring your performance

296
00:20:52.819 --> 00:20:54.260
<v Laura>of your drive train equipment.

297
00:20:54.739 --> 00:20:58.400
<v Laura>So, do you either have in-house certified
technicians?

298
00:20:58.930 --> 00:21:02.000
<v Laura>Does your OEM or distributor provide that
service?

299
00:21:02.699 --> 00:21:06.660
<v Laura>Is it outsourced through a third-party
company, or are you just not doing anything

300
00:21:06.660 --> 00:21:08.839
<v Laura>right now and reacting to the issues?

301
00:21:09.819 --> 00:21:10.319
<v Rafael Larcher>Perfect.

302
00:21:10.459 --> 00:21:11.239
<v Rafael Larcher>Thank you, Laura.

303
00:21:11.540 --> 00:21:16.739
<v Rafael Larcher>Again, while the audience thinks about
where they are today and provide us the

304
00:21:16.739 --> 00:21:21.510
<v Rafael Larcher>answers, let me Change screens and bring.

305
00:21:23.280 --> 00:21:28.209
<v Rafael Larcher>Mm Drive train analyzer cloud to the
screen.

306
00:21:29.199 --> 00:21:30.239
<v Rafael Larcher>Maximize that.

307
00:21:30.349 --> 00:21:31.859
<v Rafael Larcher>How about we do a full screen?

308
00:21:34.339 --> 00:21:37.280
<v Rafael Larcher>I think I see that on my other screen, so.

309
00:21:38.630 --> 00:21:42.459
<v Rafael Larcher>As you guys saw in the video, um,
cloud-based tool.

310
00:21:43.550 --> 00:21:48.780
<v Rafael Larcher>The home function, of course, gives you
that fleet uh fleet management view with

311
00:21:48.780 --> 00:21:52.469
<v Rafael Larcher>different dashboards, so if you have
plants throughout the world, you, you see where

312
00:21:52.469 --> 00:21:59.189
<v Rafael Larcher>they are in the map, um, the health of
your, your fleet, how the different

313
00:21:59.189 --> 00:22:01.560
<v Rafael Larcher>plants, the drive trains or the assets
are.

314
00:22:02.119 --> 00:22:07.979
<v Rafael Larcher>Behaving, if you have any anomalies going
on with, with your motors, what are your

315
00:22:07.979 --> 00:22:12.819
<v Rafael Larcher>main um issues that you need to address,
so you have a quick management type

316
00:22:12.819 --> 00:22:19.380
<v Rafael Larcher>dashboard, both for, again, the health of
the equipment as well as how the energy

317
00:22:19.380 --> 00:22:22.140
<v Rafael Larcher>consumption, the energy efficiency looks
like.

318
00:22:23.280 --> 00:22:25.420
<v Rafael Larcher>I must say this is a demo.

319
00:22:26.229 --> 00:22:30.400
<v Rafael Larcher>Tenant that we have to show the
capabilities and functionalities of these tools, so

320
00:22:30.400 --> 00:22:36.400
<v Rafael Larcher>we have valid assets at our factories, but
we also have some trade shows, um.

321
00:22:37.420 --> 00:22:41.780
<v Rafael Larcher>Sensors that we onboarded to this tool
that you're going to see that we use around,

322
00:22:41.859 --> 00:22:46.459
<v Rafael Larcher>like, for instance, this very first one,
it's a mixing cell pump that we use on our

323
00:22:46.459 --> 00:22:47.280
<v Rafael Larcher>trade show equipment.

324
00:22:47.380 --> 00:22:53.099
<v Rafael Larcher>Yes, very inefficient because it's not a
real production, it doesn't run all the

325
00:22:53.099 --> 00:22:58.760
<v Rafael Larcher>time, but you get the point, and it does
show uh that, that, the tool works.

326
00:22:59.780 --> 00:23:04.739
<v Rafael Larcher>OK, that will be what you see on the main
screen, you see different menus over on

327
00:23:04.739 --> 00:23:10.619
<v Rafael Larcher>the left side for the hierarchy, the
different assets, again, a, a map, and I like

328
00:23:10.619 --> 00:23:13.819
<v Rafael Larcher>the global logbook for the maintenance
team.

329
00:23:14.219 --> 00:23:19.500
<v Rafael Larcher>This is where they would most likely jump
to, to see the major anomalies happening

330
00:23:19.500 --> 00:23:20.400
<v Rafael Larcher>at the facility.

331
00:23:21.989 --> 00:23:27.869
<v Rafael Larcher>So, we could filter based on the severity,
based on the, the, the plants, the, the

332
00:23:27.869 --> 00:23:34.410
<v Rafael Larcher>class of the assets, and we can also see
uh what's going on.

333
00:23:34.949 --> 00:23:41.150
<v Rafael Larcher>If we have service tickets being issued,
we can enter comments, fix.

334
00:23:42.069 --> 00:23:45.189
<v Rafael Larcher>Have a service action um sent to the
maintenance team.

335
00:23:45.270 --> 00:23:51.670
<v Rafael Larcher>You can see how the tool works uh with
your, your maintenance personnel

336
00:23:51.949 --> 00:23:57.290
<v Rafael Larcher>and The magnifying glass would jump
straight to the cause.

337
00:23:58.199 --> 00:24:02.089
<v Rafael Larcher>Of the issue in this case, let's see, we
had a temperature warning threshold.

338
00:24:02.719 --> 00:24:07.459
<v Rafael Larcher>So if we look at the magnifying glass, it
would take us straight to that asset.

339
00:24:08.329 --> 00:24:10.989
<v Rafael Larcher>And show us the violation, what happened.

340
00:24:11.489 --> 00:24:18.390
<v Rafael Larcher>You could plot with different signals and
correlate with other issues that may lead,

341
00:24:18.589 --> 00:24:21.349
<v Rafael Larcher>led to this uh anomaly.

342
00:24:22.829 --> 00:24:25.849
<v Rafael Larcher>But you, you get the point of what the
tool provides to you.

343
00:24:26.510 --> 00:24:33.270
<v Rafael Larcher>So right now, we are at a particular
Siemens factory, and that particular motor went

344
00:24:33.270 --> 00:24:37.430
<v Rafael Larcher>beyond the threshold, and of course you
would have knowledge about their application

345
00:24:37.430 --> 00:24:41.180
<v Rafael Larcher>to understand what happened in here.

346
00:24:41.459 --> 00:24:46.109
<v Rafael Larcher>If not, you could ask the co-pilot to try
to correlate and pinpoint different

347
00:24:46.109 --> 00:24:46.530
<v Rafael Larcher>issues.

348
00:24:46.869 --> 00:24:48.170
<v Rafael Larcher>I'll show that in a second.

349
00:24:49.250 --> 00:24:53.589
<v Rafael Larcher>Uh, let's look at another Siemens factory,
this, uh, Nuremberg factory.

350
00:24:55.670 --> 00:24:57.339
<v Rafael Larcher>Perhaps we look at this.

351
00:24:58.280 --> 00:25:00.459
<v Rafael Larcher>Water pump #3.

352
00:25:01.939 --> 00:25:06.900
<v Rafael Larcher>KPIs that will be the again, the main
dashboard for for these motor.

353
00:25:07.739 --> 00:25:11.619
<v Rafael Larcher>In this particular case, I'm looking at
the energy consumption.

354
00:25:13.900 --> 00:25:19.819
<v Rafael Larcher>2 has a nice feature, you see the um
alternative motor details, so it

355
00:25:20.300 --> 00:25:26.660
<v Rafael Larcher>looks at its database, Siemens motor
database, and it tries to compare and look if

356
00:25:26.660 --> 00:25:32.729
<v Rafael Larcher>a, a more efficient motor would Perhaps
give you better results that you could

357
00:25:32.729 --> 00:25:36.170
<v Rafael Larcher>consider changing or upgrading for a more
efficient motor.

358
00:25:36.479 --> 00:25:41.890
<v Rafael Larcher>In this particular case, the tool did
dettech a better, more efficient motor, but

359
00:25:41.890 --> 00:25:47.130
<v Rafael Larcher>it's still doing the savings calculation,
and in, you know, a few weeks' time, you

360
00:25:47.130 --> 00:25:51.670
<v Rafael Larcher>would start spilling out what will be the
savings, what will be the ROI if you

361
00:25:51.670 --> 00:25:57.010
<v Rafael Larcher>decide to perhaps consider a more
efficient motor for this particular asset.

362
00:25:58.640 --> 00:25:59.000
<v Rafael Larcher>What else?

363
00:25:59.079 --> 00:26:05.199
<v Rafael Larcher>Um, of course, logbook, you see the
different issues for, for this motor, uh, you

364
00:26:05.199 --> 00:26:09.939
<v Rafael Larcher>can change the time frame, uh, let's do it
last year, and then it would trigger

365
00:26:10.270 --> 00:26:12.109
<v Rafael Larcher>other functions.

366
00:26:12.479 --> 00:26:15.979
<v Rafael Larcher>Most of them have been cleared, have been
addressed by the service team.

367
00:26:16.979 --> 00:26:19.979
<v Rafael Larcher>When it comes to the actual monitoring.

368
00:26:20.979 --> 00:26:26.020
<v Rafael Larcher>Um, Vibration signals, we're talking about
vibration analysis, predictive

369
00:26:26.020 --> 00:26:32.359
<v Rafael Larcher>maintenance, so you could, the tool
automatically identifies resonant points, in

370
00:26:32.359 --> 00:26:34.780
<v Rafael Larcher>this case, there are none, which, which is
good.

371
00:26:35.339 --> 00:26:38.260
<v Rafael Larcher>So this will be speeds or frequencies you
would like to avoid.

372
00:26:39.140 --> 00:26:44.819
<v Rafael Larcher>An operating point to again automatically
identifies what's the speed of that motor,

373
00:26:44.900 --> 00:26:49.359
<v Rafael Larcher>so it runs 100% in that range, that,
that's good, it's easy to do the analysis.

374
00:26:50.880 --> 00:26:56.989
<v Rafael Larcher>When it comes to the mechanical aspects of
the motor, bearings, what unbalance,

375
00:26:57.209 --> 00:27:02.680
<v Rafael Larcher>shaft misalignment, they all look to be in
decent states, no aggravation, no

376
00:27:02.680 --> 00:27:04.030
<v Rafael Larcher>anomalies being developed.

377
00:27:05.189 --> 00:27:07.819
<v Rafael Larcher>You can also see the traffic light up top
as well.

378
00:27:08.239 --> 00:27:12.489
<v Rafael Larcher>And again, it's telling us that we have a
warning, we saw that was the temperature

379
00:27:12.959 --> 00:27:17.800
<v Rafael Larcher>threshold that was exceeded, but it tells
that the unit is connected and the battery

380
00:27:17.800 --> 00:27:19.420
<v Rafael Larcher>it's at 70%.

381
00:27:20.359 --> 00:27:27.079
<v Rafael Larcher>Um, alarm settings, you can do your own
signal, uh, thresholds or, or

382
00:27:27.079 --> 00:27:31.030
<v Rafael Larcher>evaluations for, for torque, power,
temperature, speed.

383
00:27:31.329 --> 00:27:35.089
<v Rafael Larcher>In this particular case, we're looking for
the vibration signals.

384
00:27:35.959 --> 00:27:39.500
<v Rafael Larcher>You can accept the automatic values from
the tool.

385
00:27:39.680 --> 00:27:44.199
<v Rafael Larcher>These are based on standards, so the tool
automatically knows the the motor

386
00:27:44.199 --> 00:27:49.219
<v Rafael Larcher>characteristics, the motor power, speeds,
and infer threshold levels.

387
00:27:49.640 --> 00:27:51.939
<v Rafael Larcher>You can select that and apply.

388
00:27:52.160 --> 00:27:57.800
<v Rafael Larcher>It would define those values automatically
for you, or you can enter your own if you

389
00:27:57.800 --> 00:28:01.219
<v Rafael Larcher>have that knowledge yourself about that
particular asset.

390
00:28:02.339 --> 00:28:07.020
<v Rafael Larcher>Alternatively, we can do what we call the
intelligent monitoring, and I think that

391
00:28:07.020 --> 00:28:08.400
<v Rafael Larcher>was shown on the video.

392
00:28:09.329 --> 00:28:16.050
<v Rafael Larcher>Where you can feed the tool with a set of,
let's say a good data set, and

393
00:28:16.050 --> 00:28:22.209
<v Rafael Larcher>you will learn what a good data set looks
for for this motor, or you can flag for

394
00:28:22.209 --> 00:28:28.810
<v Rafael Larcher>automatic vibration monitoring, where
again the AI agents, the vaccines would be

395
00:28:28.810 --> 00:28:34.369
<v Rafael Larcher>looking for anomalies, correlate different
signals, and then spill out potential

396
00:28:34.369 --> 00:28:37.869
<v Rafael Larcher>issues, potential developments that you,
you need to take an action on.

397
00:28:38.849 --> 00:28:45.709
<v Rafael Larcher>Uh, obviously, you can send email
notifications, so the maintenance personnel would

398
00:28:45.709 --> 00:28:51.329
<v Rafael Larcher>input their emails and then subscribe to
receive those alerts, and then take actions

399
00:28:51.329 --> 00:28:52.630
<v Rafael Larcher>upon them as well.

400
00:28:54.959 --> 00:28:58.089
<v Rafael Larcher>This is just a snapshot of the tool folks.

401
00:28:58.170 --> 00:29:03.420
<v Rafael Larcher>Uh, what I would like to show now, as I
mentioned, um, the operations copilot, it's

402
00:29:03.680 --> 00:29:07.459
<v Rafael Larcher>recently been developed and you can see
it's still under a beta testing.

403
00:29:08.369 --> 00:29:10.229
<v Rafael Larcher>Just for the sake of time, I, I.

404
00:29:11.000 --> 00:29:15.089
<v Rafael Larcher>Provided 3 questions or 3 requests to the
agent here.

405
00:29:15.410 --> 00:29:19.810
<v Rafael Larcher>What are my top 3 critical issues at this
particular factory that we're looking for?

406
00:29:19.969 --> 00:29:21.449
<v Rafael Larcher>Siems Nuremberg factory.

407
00:29:22.089 --> 00:29:27.729
<v Rafael Larcher>So yes, he came and listed the 3 major
issues, uh, based on the criteria, of course,

408
00:29:27.810 --> 00:29:29.849
<v Rafael Larcher>that the agent was programmed for.

409
00:29:30.489 --> 00:29:35.650
<v Rafael Larcher>Then I asked for my very first one, give
me more details about the most critical

410
00:29:35.650 --> 00:29:35.979
<v Rafael Larcher>issue.

411
00:29:36.719 --> 00:29:42.000
<v Rafael Larcher>And then he gave me a very nice plain
English summary of what's going on.

412
00:29:42.439 --> 00:29:49.020
<v Rafael Larcher>Uh, you, we see frequency of the issue,
the severity, duration and intensity,

413
00:29:49.560 --> 00:29:53.060
<v Rafael Larcher>some patterns being recognized, potential
impact.

414
00:29:53.400 --> 00:29:59.359
<v Rafael Larcher>So you see the value of what co-pilot can
bring to the table now, by lowering the

415
00:29:59.359 --> 00:30:03.880
<v Rafael Larcher>level of knowledge required from whoever
is interacting to the tool to better

416
00:30:03.880 --> 00:30:05.180
<v Rafael Larcher>understand what's happening here.

417
00:30:06.589 --> 00:30:12.380
<v Rafael Larcher>Then a third question, I said, how do I
address and fix these issues for pump #2,

418
00:30:12.469 --> 00:30:13.709
<v Rafael Larcher>this particular asset?

419
00:30:14.109 --> 00:30:19.369
<v Rafael Larcher>Again, gave me a very thorough answer with
some immediate actions.

420
00:30:20.130 --> 00:30:26.109
<v Rafael Larcher>Inspections, doing evaluations, doing an
electrical check, operational assessment.

421
00:30:26.989 --> 00:30:28.369
<v Rafael Larcher>Optimization.

422
00:30:29.209 --> 00:30:30.130
<v Rafael Larcher>What else?

423
00:30:30.449 --> 00:30:30.859
<v Rafael Larcher>Um.

424
00:30:31.930 --> 00:30:36.069
<v Rafael Larcher>See kind of a long term solution,
documentation and training.

425
00:30:36.170 --> 00:30:40.069
<v Rafael Larcher>So again, You see the value of the tool,
um.

426
00:30:41.130 --> 00:30:45.290
<v Rafael Larcher>In the near future, you will start talking
with other software elements too, so you

427
00:30:45.290 --> 00:30:52.209
<v Rafael Larcher>can translate and export this information
to other system and trigger service

428
00:30:52.209 --> 00:30:57.790
<v Rafael Larcher>tickets, maintenance tickets with this
intel that the two already gave to you.

429
00:31:01.219 --> 00:31:04.930
<v Rafael Larcher>You see on my cheat sheet, if I forgot to
mention something.

430
00:31:13.589 --> 00:31:15.469
<v Rafael Larcher>That's pretty much it.

431
00:31:19.010 --> 00:31:22.770
<v Rafael Larcher>For the sake of time, let's just go back
to the uh the presentation.

432
00:31:23.510 --> 00:31:30.479
<v Rafael Larcher>And Laura,

433
00:31:30.520 --> 00:31:34.239
<v Rafael Larcher>if you could please put the, uh, the poll
results on the screen.

434
00:31:34.420 --> 00:31:41.099
<v Rafael Larcher>Uh, I'm very curious to see where the
audience um is handling their Their

435
00:31:41.099 --> 00:31:43.410
<v Rafael Larcher>performance on the drivetrain assets, so.

436
00:31:45.130 --> 00:31:51.890
<v Rafael Larcher>OK, about 1/3 have in-house technicians
and experts, that's, that's good.

437
00:31:52.989 --> 00:31:57.750
<v Rafael Larcher>Um, the vast majority, actually, it's not
doing anything right now, just reacting to

438
00:31:57.750 --> 00:31:59.989
<v Rafael Larcher>the issues that's um.

439
00:32:01.329 --> 00:32:03.239
<v Rafael Larcher>Not what we would like to see, obviously,
and hopefully.

440
00:32:04.089 --> 00:32:06.650
<v Rafael Larcher>We can help you guys turning the table on
that.

441
00:32:07.459 --> 00:32:13.660
<v Rafael Larcher>Um, 14% having OEMs and distributors doing
that for them, yes, it's kind of growing

442
00:32:13.660 --> 00:32:18.920
<v Rafael Larcher>as, as we see those guys are adding such
digital services to their portfolio.

443
00:32:20.160 --> 00:32:24.469
<v Rafael Larcher>Uh, and it's outsourced, outsourced
through third-party companies, less than 10%,

444
00:32:24.569 --> 00:32:30.199
<v Rafael Larcher>so, Interesting to see that the majority
actually is not doing anything right now,

445
00:32:30.410 --> 00:32:35.060
<v Rafael Larcher>um, but about 1/3 have that knowledge,
have that intel in-house.

446
00:32:37.430 --> 00:32:39.180
<v Rafael Larcher>Thank you again, folks for sharing that.

447
00:32:39.439 --> 00:32:43.290
<v Rafael Larcher>Um, So how about we just bring it home?

448
00:32:43.790 --> 00:32:47.170
<v Rafael Larcher>Um, again, the solution I've been talking
today.

449
00:32:47.790 --> 00:32:51.150
<v Rafael Larcher>It's solely focused on the drive train,
right?

450
00:32:51.500 --> 00:32:57.069
<v Rafael Larcher>If you're looking to implement maintenance
strategies beyond your drive train, let's

451
00:32:57.069 --> 00:33:03.229
<v Rafael Larcher>say you have a, a robot arm or, or, you
know, you wanna monitor different process

452
00:33:03.229 --> 00:33:08.130
<v Rafael Larcher>variables, or if you want to do
performance on an entire line, entire shop floor,

453
00:33:08.589 --> 00:33:12.089
<v Rafael Larcher>then we offer different tools, platforms.

454
00:33:13.030 --> 00:33:16.069
<v Rafael Larcher>Sense I would be your answer in this case.

455
00:33:16.819 --> 00:33:21.979
<v Rafael Larcher>Sensi, if you heard about it, that, that
is a very comprehensive and product

456
00:33:21.979 --> 00:33:27.180
<v Rafael Larcher>agnostic solution, and that's for any and
all assets in your shop floor.

457
00:33:29.650 --> 00:33:34.369
<v Rafael Larcher>Sensi is not the focus technology for
today's webinar, but again, I wanted to make

458
00:33:34.369 --> 00:33:39.449
<v Rafael Larcher>sure you are aware of Siemens uh different
hardware and software solutions when it

459
00:33:39.449 --> 00:33:45.489
<v Rafael Larcher>comes to predictive and prescriptive
maintenance, including generative AI and the

460
00:33:45.489 --> 00:33:50.770
<v Rafael Larcher>co-pilot that I just showed to you guys
for a more holistic, a more conversational

461
00:33:50.770 --> 00:33:55.150
<v Rafael Larcher>approach, showing the potential issues and
how to address them.

462
00:33:55.729 --> 00:34:01.089
<v Rafael Larcher>But again, if you're looking beyond your
drivetrain, Um, analytics, predictive

463
00:34:01.089 --> 00:34:05.989
<v Rafael Larcher>maintenance, one of Siemens solutions that
I would encourage you guys to learn more

464
00:34:06.130 --> 00:34:10.330
<v Rafael Larcher>would be the Sensii, uh, predictive
maintenance cloud-based platform.

465
00:34:10.459 --> 00:34:16.790
<v Rafael Larcher>Again, agnostic, any and all asset at your
machine or the entire shop floor.

466
00:34:19.620 --> 00:34:23.310
<v Rafael Larcher>So just bringing it home before we uh open
up for, for question folks.

467
00:34:25.059 --> 00:34:30.208
<v Rafael Larcher>Just kind of summarizing everything that
I, I spoke here today, uh, showing the, the

468
00:34:30.208 --> 00:34:32.378
<v Rafael Larcher>value of such digital services, right?

469
00:34:32.448 --> 00:34:37.718
<v Rafael Larcher>So if you are a plant operator, if you're
an end user, of course, by deploying, by

470
00:34:37.718 --> 00:34:42.489
<v Rafael Larcher>applying these solutions, you can extend
the lifetime of your assets, increase the

471
00:34:42.489 --> 00:34:47.368
<v Rafael Larcher>productivity, reduce the maintenance
efforts, make, make them more efficiently in

472
00:34:47.368 --> 00:34:52.319
<v Rafael Larcher>your facilities, and um save with energy,
reduce energy consumption, which is a

473
00:34:52.319 --> 00:34:54.448
<v Rafael Larcher>major cost savings right there.

474
00:34:55.540 --> 00:35:00.620
<v Rafael Larcher>If you are an OEM or if you are a machine
builder, um, you know, perhaps you can

475
00:35:00.620 --> 00:35:03.659
<v Rafael Larcher>consider expanding your portfolio with
such digital services.

476
00:35:03.739 --> 00:35:09.100
<v Rafael Larcher>You can enhance the analytics of your
machine by providing such services to your

477
00:35:09.100 --> 00:35:09.780
<v Rafael Larcher>customers, right?

478
00:35:09.899 --> 00:35:15.209
<v Rafael Larcher>And you can offer that serviceability, uh
remote, I should say serviceability in

479
00:35:15.209 --> 00:35:17.840
<v Rafael Larcher>addition to your hardware to your
machines.

480
00:35:18.419 --> 00:35:23.290
<v Rafael Larcher>And then likewise, if you are a service
provider, if you are a distributor, You may

481
00:35:23.709 --> 00:35:27.300
<v Rafael Larcher>think about adding such digital services
to your portfolio as well.

482
00:35:27.709 --> 00:35:33.459
<v Rafael Larcher>Partner with your customers, have them
grant access to their data, so you can keep

483
00:35:33.459 --> 00:35:38.189
<v Rafael Larcher>an eye on their assets and notify them in
advance of an anomaly of a deterioration

484
00:35:38.550 --> 00:35:43.669
<v Rafael Larcher>and help them through the, the maintenance
uh schedule and procuring the spare parts

485
00:35:43.669 --> 00:35:43.909
<v Rafael Larcher>too.

486
00:35:47.780 --> 00:35:52.969
<v Rafael Larcher>Looking at time, I think we have about
maybe 10 minutes for, for questions, Laura.

487
00:35:53.040 --> 00:35:57.219
<v Rafael Larcher>Um, I haven't been looking at the chat, so
if you could help me out here, I would

488
00:35:57.219 --> 00:35:58.340
<v Rafael Larcher>greatly appreciate it.

489
00:35:59.239 --> 00:35:59.800
<v Laura>Of course.

490
00:36:00.000 --> 00:36:02.320
<v Laura>Great presentation, very informative.

491
00:36:02.679 --> 00:36:05.959
<v Laura>Um, I hope everyone gains some insight on
that.

492
00:36:06.280 --> 00:36:10.959
<v Laura>And before we get to the questions, just
want everyone to know, um, that you'll see

493
00:36:10.959 --> 00:36:13.899
<v Laura>a poll on the right-hand side of your
screen.

494
00:36:14.280 --> 00:36:18.590
<v Laura>And so please answer that if you want us
to contact you with some more information

495
00:36:18.919 --> 00:36:20.209
<v Laura>after this webinar.

496
00:36:20.679 --> 00:36:23.570
<v Laura>So, again, on your upper right screen.

497
00:36:23.959 --> 00:36:25.760
<v Laura>But let's get into the questions.

498
00:36:25.909 --> 00:36:32.429
<v Laura>So, a lot of these are about the
connection module, and if it is connected to

499
00:36:32.429 --> 00:36:35.020
<v Laura>Industrial edge is our first question.

500
00:36:36.229 --> 00:36:40.830
<v Rafael Larcher>This particular solution is not connected
to edge, we are.

501
00:36:41.699 --> 00:36:46.159
<v Rafael Larcher>Making that happen in, in maybe a year or
so time frame.

502
00:36:46.739 --> 00:36:53.149
<v Rafael Larcher>Today's cloud-on, but as I mentioned, it
does have MQTT communication capability,

503
00:36:53.540 --> 00:36:59.120
<v Rafael Larcher>so you can get the raw data and do your
own analytics if you would like to do that.

504
00:37:01.540 --> 00:37:02.050
<v Laura>Awesome.

505
00:37:02.179 --> 00:37:07.739
<v Laura>And then the next question is if this can
be installed on other manufacturers'

506
00:37:07.739 --> 00:37:08.560
<v Laura>motors.

507
00:37:10.010 --> 00:37:15.370
<v Rafael Larcher>Most likely, this product is motor
agnostic or we, as we say, asset agnostic, so it

508
00:37:15.370 --> 00:37:19.800
<v Rafael Larcher>can be any motor, it can be induction
motor, it could be per permanent magnet motor,

509
00:37:19.850 --> 00:37:21.310
<v Rafael Larcher>it doesn't have to be Siemens only.

510
00:37:22.909 --> 00:37:23.310
<v Laura>Awesome.

511
00:37:23.429 --> 00:37:28.419
<v Laura>And then a couple more questions about the
module itself is if there's, the

512
00:37:28.419 --> 00:37:31.159
<v Laura>batteries for it are standard off the
shelf.

513
00:37:32.669 --> 00:37:39.260
<v Rafael Larcher>These are not the standard AA, they are
the A A size, but these are the LTC, uh,

514
00:37:39.270 --> 00:37:44.070
<v Rafael Larcher>rechargeable batteries, um, if you know
what I, what I mean, where it's a, it's a

515
00:37:44.070 --> 00:37:47.949
<v Rafael Larcher>little higher in voltage, but you can
recharge them and they, they last longer.

516
00:37:48.070 --> 00:37:51.870
<v Rafael Larcher>So as I mentioned, these are supposed to
last for about 4 years.

517
00:37:52.149 --> 00:37:55.550
<v Rafael Larcher>The good thing is that they are also fuel
replaceable, the actual sensor, you can

518
00:37:55.550 --> 00:37:59.570
<v Rafael Larcher>open the sensor and replace the batteries
after they've been installed.

519
00:38:01.479 --> 00:38:02.010
<v Laura>Awesome.

520
00:38:02.209 --> 00:38:07.879
<v Laura>Um, and then this is a specific use case
if this module can be used in a freezer at

521
00:38:07.879 --> 00:38:09.870
<v Laura>-20 °F.

522
00:38:14.300 --> 00:38:15.879
<v Rafael Larcher>They got me with that one, Laura.

523
00:38:15.939 --> 00:38:20.879
<v Rafael Larcher>I did, I don't recall the actual
temperature range top of my head.

524
00:38:21.139 --> 00:38:24.879
<v Rafael Larcher>I would have to look at some
documentation, but that's, that's a good one, perhaps.

525
00:38:25.800 --> 00:38:27.399
<v Rafael Larcher>You guys have my contact information.

526
00:38:27.479 --> 00:38:32.280
<v Rafael Larcher>If uh you can follow up with me, I'll be
uh providing that answer back to the person

527
00:38:32.280 --> 00:38:33.000
<v Rafael Larcher>who asked that question.

528
00:38:33.110 --> 00:38:33.520
<v Rafael Larcher>Thank you.

529
00:38:34.540 --> 00:38:41.139
<v Laura>Yeah, and then also, is the app able to
send the signal to automatically shut down

530
00:38:41.139 --> 00:38:44.560
<v Laura>the equipment if the alarm is on, for
example.

531
00:38:45.300 --> 00:38:52.080
<v Rafael Larcher>No, keep in mind this is a predictive
maintenance tool, so it's not a real-time

532
00:38:52.540 --> 00:38:58.979
<v Rafael Larcher>monitoring device, and when we talk about
cloud connectivity, The vast majority of

533
00:38:58.979 --> 00:39:00.540
<v Rafael Larcher>the communication is just one way.

534
00:39:00.620 --> 00:39:02.449
<v Rafael Larcher>It's just from the device to the cloud.

535
00:39:02.580 --> 00:39:06.580
<v Rafael Larcher>The only change that we send to the device
is for firmware update.

536
00:39:07.370 --> 00:39:11.649
<v Rafael Larcher>Um, and different time measurement
intervals, but there's no way for the tool to

537
00:39:11.649 --> 00:39:15.010
<v Rafael Larcher>actually interface with the motor or with
the drive whatsoever.

538
00:39:15.209 --> 00:39:17.389
<v Rafael Larcher>That will have to be done outside the
platform.

539
00:39:19.560 --> 00:39:19.850
<v Laura>OK.

540
00:39:20.050 --> 00:39:25.310
<v Laura>And then last one is how is the hardware
and sensor mounted to the motor?

541
00:39:27.830 --> 00:39:29.209
<v Rafael Larcher>You can either.

542
00:39:30.360 --> 00:39:35.360
<v Rafael Larcher>Glue or actually screw the, the metal
bracket to, to the motor, uh we recommend, of

543
00:39:35.360 --> 00:39:40.139
<v Rafael Larcher>course, gluing to the motor so you don't
void the warranty, but the device comes

544
00:39:40.139 --> 00:39:44.439
<v Rafael Larcher>with a metal bracket and you just glue the
metal bracket to the motor and then screw

545
00:39:44.439 --> 00:39:45.500
<v Rafael Larcher>the sensor to it.

546
00:39:45.879 --> 00:39:50.340
<v Rafael Larcher>It's at the shaft height, 1/3 towards the
front of the motor, it's straightforward,

547
00:39:50.479 --> 00:39:52.239
<v Rafael Larcher>it's in the manner, but that's how you do
it.

548
00:39:53.719 --> 00:39:55.780
<v Laura>And then one more just came in.

549
00:39:56.239 --> 00:40:00.100
<v Laura>What is the update time on the CM?

550
00:40:03.010 --> 00:40:06.360
<v Rafael Larcher>I guess the question would be, OK, I think
I got the question.

551
00:40:06.689 --> 00:40:10.570
<v Rafael Larcher>So there are two time frame if you think
about it.

552
00:40:10.649 --> 00:40:16.270
<v Rafael Larcher>The measurement time, which can be as
quick as every minute, pulling data out of the

553
00:40:16.270 --> 00:40:21.159
<v Rafael Larcher>connected asset and then sending data to
the cloud at every hour.

554
00:40:21.290 --> 00:40:26.860
<v Rafael Larcher>So, as fast as every minute analyzing the
data, And as quick as sending data to the

555
00:40:26.860 --> 00:40:33.699
<v Rafael Larcher>cloud at every hour, or as slow as every 2
days, for instance, and you can also

556
00:40:33.699 --> 00:40:38.399
<v Rafael Larcher>change the, the measurement interval from
every minute all the way to I think 10

557
00:40:38.399 --> 00:40:39.000
<v Rafael Larcher>minutes.

558
00:40:39.459 --> 00:40:43.659
<v Rafael Larcher>So it's, it's flexible, and then that
would actually impact the battery life.

559
00:40:44.020 --> 00:40:48.020
<v Rafael Larcher>So if you're measuring it every minute and
sending data every hour to the cloud, you

560
00:40:48.020 --> 00:40:53.139
<v Rafael Larcher>most likely wouldn't get 4 years of the
battery life unless you're Plugged with the

561
00:40:53.139 --> 00:40:54.479
<v Rafael Larcher>24 volts wire as well.

562
00:40:56.639 --> 00:40:57.120
<v Laura>Awesome.

563
00:40:57.280 --> 00:40:58.909
<v Laura>Um, and then one more.

564
00:40:59.810 --> 00:41:04.989
<v Laura>Can this app receive data from third-party
drives or other sensors?

565
00:41:07.149 --> 00:41:09.550
<v Rafael Larcher>Not this solution that I showed to you
guys.

566
00:41:09.629 --> 00:41:11.270
<v Rafael Larcher>Uh, I mentioned about Sensei.

567
00:41:11.510 --> 00:41:18.340
<v Rafael Larcher>Sensei is product agnostic, so you can,
you can bring any Um, sensor

568
00:41:18.340 --> 00:41:20.159
<v Rafael Larcher>data from any manufactured.

569
00:41:20.959 --> 00:41:22.350
<v Rafael Larcher>Agnostic 100%.

570
00:41:22.790 --> 00:41:29.030
<v Rafael Larcher>We do offer though other solutions, um,
edge-based that are also product agnostic

571
00:41:29.030 --> 00:41:35.439
<v Rafael Larcher>that it can bring third-party, um Uh, the,
um, sensors to be analyzed as well.

572
00:41:37.870 --> 00:41:38.459
<v Laura>OK.

573
00:41:38.750 --> 00:41:39.370
<v Laura>Awesome.

574
00:41:40.550 --> 00:41:44.800
<v Laura>Um, OK, so that's all the questions we
have.

575
00:41:48.040 --> 00:41:50.600
<v Laura>Unless anyone speaks right now.

576
00:41:50.719 --> 00:41:55.919
<v Laura>But um thank you so much for all the
information and answering all the questions and

577
00:41:55.919 --> 00:41:57.800
<v Laura>thank you everyone for joining.

578
00:41:58.159 --> 00:42:01.530
<v Laura>Um, please reach out to Rafael if you have
any questions.

579
00:42:01.639 --> 00:42:04.939
<v Laura>He had his email posted in the slides.

580
00:42:05.439 --> 00:42:08.800
<v Laura>Um, and with that, that's all for now.

581
00:42:08.959 --> 00:42:10.100
<v Laura>Thank you so much.

582
00:42:11.070 --> 00:42:12.469
<v Rafael Larcher>Thank you guys, appreciate the time.

583
00:42:12.669 --> 00:42:13.610
<v Rafael Larcher>Hope you have a good day.

584
00:42:15.159 --> 00:42:15.580
<v Speaker 1>Thank you.

585
00:42:15.719 --> 00:42:17.060
<v Speaker 1>This concludes our webinar.

586
00:42:20.260 --> 00:42:25.219
<v Speaker 5>Please like and subscribe on all major
podcast channels and find out more about

587
00:42:25.219 --> 00:42:28.600
<v Speaker 5>Sensei predictive maintenance at
Siemens.com.
