WEBVTT
Language: en-US

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

2
00:00:10.149 --> 00:00:15.149
<v Stephanie>Hello everyone, thank you for joining our
webinar Unlock the Power of Data-driven

3
00:00:15.149 --> 00:00:20.389
<v Stephanie>manufacturing, digital strategies to
accelerate manufacturing growth, presented by

4
00:00:20.389 --> 00:00:22.370
<v Stephanie>Ranak Mackwan and Hinaro Quiroz.

5
00:00:23.750 --> 00:00:27.850
<v Stephanie>Today they'll be talking about how
technologies like CMMS, predictive maintenance,

6
00:00:28.030 --> 00:00:32.970
<v Stephanie>FCA, IOT, remote monitoring, and machine
learning can streamline your operations.

7
00:00:33.409 --> 00:00:38.169
<v Stephanie>The role of data in Capital planning,
asset life cycle management, and how reporting

8
00:00:38.169 --> 00:00:42.549
<v Stephanie>and analytic tools can help you achieve
your financial goals with confidence.

9
00:00:43.330 --> 00:00:47.389
<v Stephanie>Before we get started, I want to just go
over some easy housekeeping items.

10
00:00:47.700 --> 00:00:50.180
<v Stephanie>All of your lines are muted during the
session.

11
00:00:50.619 --> 00:00:54.840
<v Stephanie>Please submit your questions to the
Q&amp;A feature at the bottom of your screen at any

12
00:00:54.840 --> 00:00:56.169
<v Stephanie>time during the webinar.

13
00:00:56.419 --> 00:00:59.580
<v Stephanie>We'll answer questions at the end of the
presentation.

14
00:00:59.939 --> 00:01:04.419
<v Stephanie>If you don't see the Ask a Question box,
you can open it with the question mark icon

15
00:01:04.419 --> 00:01:06.239
<v Stephanie>at the bottom center of your screen.

16
00:01:07.510 --> 00:01:11.790
<v Stephanie>The presentation is being recorded and it
will be available on demand after the

17
00:01:11.790 --> 00:01:12.430
<v Stephanie>webinar.

18
00:01:12.709 --> 00:01:17.220
<v Stephanie>We'll also send it via email with a link
so that you can come back to it or share it

19
00:01:17.220 --> 00:01:18.019
<v Stephanie>with colleagues.

20
00:01:18.389 --> 00:01:21.250
<v Stephanie>It usually gets sent within 24 to 48
hours.

21
00:01:21.830 --> 00:01:24.050
<v Stephanie>I'd like to introduce our two speakers for
today.

22
00:01:24.620 --> 00:01:28.739
<v Stephanie>With over a decade of hands-on experience
in both maintenance and engineering roles,

23
00:01:29.019 --> 00:01:34.720
<v Stephanie>ROAONAC brings a wealth of experience in
GMP, HACCP, and BRC programs.

24
00:01:35.180 --> 00:01:40.099
<v Stephanie>ROANA's experience includes lead
manufacturing and total quality, quality management

25
00:01:40.099 --> 00:01:44.339
<v Stephanie>environments, maintenance management and
fast-paced environments, and a deep

26
00:01:44.339 --> 00:01:48.389
<v Stephanie>understanding of building automation, PLC
systems, and equipment integration

27
00:01:48.389 --> 00:01:48.860
<v Stephanie>projects.

28
00:01:50.004 --> 00:01:54.605
<v Stephanie>Driven by innovation and a passion for
process improvement, ROANA is well versed in

29
00:01:54.605 --> 00:01:58.845
<v Stephanie>non-value added elimination principles and
has demonstrated successful project

30
00:01:58.845 --> 00:02:03.404
<v Stephanie>management skills in manufacturing plants,
spanning initiation, execution,

31
00:02:03.504 --> 00:02:05.464
<v Stephanie>monitoring and controlling and closing.

32
00:02:05.764 --> 00:02:10.285
<v Stephanie>Ranak is a professional engineer with his
Red Seal journeyman electrician ticket and

33
00:02:10.285 --> 00:02:11.904
<v Stephanie>has a PMP certification.

34
00:02:12.005 --> 00:02:13.264
<v Stephanie>He's based in Toronto.

35
00:02:14.649 --> 00:02:19.539
<v Stephanie>Knaro Kiraz is the solutions engineer at
Siemens, specializing in AI and predictive

36
00:02:19.539 --> 00:02:20.179
<v Stephanie>maintenance.

37
00:02:20.539 --> 00:02:24.860
<v Stephanie>He leverages AI to revolutionize
traditional maintenance strategies, driving

38
00:02:24.860 --> 00:02:26.800
<v Stephanie>sustainability and innovation.

39
00:02:27.139 --> 00:02:31.899
<v Stephanie>With extensive experience as a controls
engineer, industrial technician, and US Navy

40
00:02:31.899 --> 00:02:36.460
<v Stephanie>submarine electrician, Parro understands
the critical importance of reliability,

41
00:02:36.539 --> 00:02:39.339
<v Stephanie>efficiency, and continuous technological
improvement.

42
00:02:39.830 --> 00:02:44.259
<v Stephanie>He has successfully deployed projects
globally, making AI a reality that delivers

43
00:02:44.259 --> 00:02:46.669
<v Stephanie>tangible outcomes across various
industries.

44
00:02:47.029 --> 00:02:49.889
<v Stephanie>Now I will pass it over to our two
speakers to get started.

45
00:02:51.529 --> 00:02:51.970
<v Ronak Mekwan>Awesome.

46
00:02:52.089 --> 00:02:52.960
<v Ronak Mekwan>Thank you very much, Stephanie.

47
00:02:52.970 --> 00:02:56.490
<v Ronak Mekwan>That was a great, uh, introduction about
myself and Hanaro.

48
00:02:56.570 --> 00:02:57.320
<v Ronak Mekwan>So, hello everyone.

49
00:02:57.410 --> 00:03:01.009
<v Ronak Mekwan>Good afternoon to those who are joining us
from the Eastern Standard Zone, and good

50
00:03:01.009 --> 00:03:04.529
<v Ronak Mekwan>morning, whoever is joining us from the
Pacific Time Zone and the Central Time Zone.

51
00:03:05.169 --> 00:03:09.270
<v Ronak Mekwan>So myself, Ronak Mekwan, I come from the
manufacturing industry working mostly in

52
00:03:09.270 --> 00:03:10.110
<v Ronak Mekwan>the food and baroveol.

53
00:03:10.169 --> 00:03:14.289
<v Ronak Mekwan>I work in maintenance operation as well as
the engineering role.

54
00:03:14.449 --> 00:03:18.600
<v Ronak Mekwan>And today, I'm, I'm thrilled to talk about
all the different digital technology,

55
00:03:18.649 --> 00:03:19.809
<v Ronak Mekwan>what we have available.

56
00:03:20.229 --> 00:03:24.750
<v Ronak Mekwan>In the current market that can help
manufacturers run their day to day operations

57
00:03:24.750 --> 00:03:25.649
<v Ronak Mekwan>and maintenance.

58
00:03:25.990 --> 00:03:32.470
<v Ronak Mekwan>So before I start talking about all this
technology, let me get into a visual

59
00:03:32.470 --> 00:03:34.910
<v Ronak Mekwan>representation, what we call as an asset
pyramid.

60
00:03:35.600 --> 00:03:39.919
<v Ronak Mekwan>So when you look at this asset pyramid,
that's the entire visual representation of

61
00:03:39.919 --> 00:03:41.919
<v Ronak Mekwan>your entire asset management journey.

62
00:03:42.479 --> 00:03:46.320
<v Ronak Mekwan>So, if you buy any asset, and I'm just
going to give you a very basic example, let's

63
00:03:46.320 --> 00:03:50.720
<v Ronak Mekwan>say if you buy a brand new boiler or a
brand new air compressor, you always start

64
00:03:50.720 --> 00:03:54.580
<v Ronak Mekwan>from your, the very bottom layer, which is
the work management processes.

65
00:03:55.000 --> 00:03:58.559
<v Ronak Mekwan>So work management processes, whether it's
a part inventory management, whether it's

66
00:03:58.559 --> 00:04:02.690
<v Ronak Mekwan>a work order management, whether it's a
material management, Whether it's an asset

67
00:04:02.690 --> 00:04:06.970
<v Ronak Mekwan>registry to start building it from the
scratch, those are some of the core

68
00:04:06.970 --> 00:04:12.610
<v Ronak Mekwan>fundamental items that every organization,
every manufacturer, every maintenance

69
00:04:12.610 --> 00:04:17.850
<v Ronak Mekwan>department should and must follow if they
want a robust asset strategic asset

70
00:04:17.850 --> 00:04:18.750
<v Ronak Mekwan>management program.

71
00:04:18.970 --> 00:04:21.609
<v Ronak Mekwan>So that would be the most foundational
item.

72
00:04:21.940 --> 00:04:25.609
<v Ronak Mekwan>Then when you look at the second bottom
layer, how you envision your asset

73
00:04:25.609 --> 00:04:26.549
<v Ronak Mekwan>management journey.

74
00:04:27.079 --> 00:04:30.559
<v Ronak Mekwan>Now you have the work management, now you
have the asset registry, now you have your

75
00:04:30.559 --> 00:04:32.070
<v Ronak Mekwan>all your parts in place.

76
00:04:32.440 --> 00:04:37.399
<v Ronak Mekwan>Now you start implementing processes to
maintain your day to day operations.

77
00:04:37.480 --> 00:04:39.709
<v Ronak Mekwan>So what type of process that that would
be.

78
00:04:40.000 --> 00:04:44.399
<v Ronak Mekwan>So a very basic that, that, that can go
with any companies is RCA root cause

79
00:04:44.399 --> 00:04:49.480
<v Ronak Mekwan>analysis, reliability team, different
maintenance strategies such as PM compliance

80
00:04:49.480 --> 00:04:49.779
<v Ronak Mekwan>program.

81
00:04:50.279 --> 00:04:51.440
<v Ronak Mekwan>Work design standards.

82
00:04:51.500 --> 00:04:56.880
<v Ronak Mekwan>So those are the processes that will help
manufacturers to stay on top of your work

83
00:04:56.880 --> 00:05:03.000
<v Ronak Mekwan>order management, to detect any reactive
failure and act on it and basically work in

84
00:05:03.000 --> 00:05:04.369
<v Ronak Mekwan>a proactive mode.

85
00:05:05.100 --> 00:05:06.350
<v Ronak Mekwan>Rather than a reactive mode.

86
00:05:06.470 --> 00:05:08.410
<v Ronak Mekwan>So that would be the 2nd bottom layer.

87
00:05:08.589 --> 00:05:11.790
<v Ronak Mekwan>After that, now we have started to go into
digital mode.

88
00:05:12.190 --> 00:05:14.220
<v Ronak Mekwan>Now we are talking about the operational
technology.

89
00:05:14.450 --> 00:05:16.529
<v Ronak Mekwan>First, you already have your work order
management.

90
00:05:17.029 --> 00:05:22.149
<v Ronak Mekwan>Now you have implemented the personal, the
manual processes in place to look after

91
00:05:22.149 --> 00:05:23.690
<v Ronak Mekwan>those work management processes.

92
00:05:23.799 --> 00:05:28.269
<v Ronak Mekwan>Now, let's get into the operational
technology and we'll be touching all of them in

93
00:05:28.269 --> 00:05:29.250
<v Ronak Mekwan>our next slides.

94
00:05:29.970 --> 00:05:36.160
<v Ronak Mekwan>For example, CMMS or IOT remote monitoring
or predictive maintenance, or FCA billing

95
00:05:36.160 --> 00:05:40.570
<v Ronak Mekwan>automation system, or SCCATDA, which is
supervisory control and data acquisition

96
00:05:40.570 --> 00:05:46.130
<v Ronak Mekwan>that, that links all of your moving
existing production equipment into a single

97
00:05:46.130 --> 00:05:46.429
<v Ronak Mekwan>screen.

98
00:05:46.760 --> 00:05:53.079
<v Ronak Mekwan>So the idea here is you want to have a
full vision of your manufacturing industry,

99
00:05:53.200 --> 00:05:56.100
<v Ronak Mekwan>of your production environment on a single
screen.

100
00:05:56.279 --> 00:06:00.500
<v Ronak Mekwan>So if I'm a plant manager, if I'm a senior
level executive, if I want to understand,

101
00:06:00.559 --> 00:06:04.070
<v Ronak Mekwan>hey, what's happening as of today, April
9th, how's my day shift doing?

102
00:06:04.420 --> 00:06:07.690
<v Ronak Mekwan>How, what did they do in the next uh last
six hours?

103
00:06:08.350 --> 00:06:10.160
<v Ronak Mekwan>Those operational technology will provide.

104
00:06:10.299 --> 00:06:11.640
<v Ronak Mekwan>That information and data.

105
00:06:11.950 --> 00:06:15.510
<v Ronak Mekwan>Then we go get into the performance
management, and that's we're talking about the

106
00:06:15.510 --> 00:06:19.029
<v Ronak Mekwan>reporting and analytics, which we'll be
touching in our next slide as well.

107
00:06:19.109 --> 00:06:22.690
<v Ronak Mekwan>But that's where now you already have that
defined data available.

108
00:06:22.980 --> 00:06:24.589
<v Ronak Mekwan>Now you talk about strategy.

109
00:06:24.670 --> 00:06:29.709
<v Ronak Mekwan>Now you talk about how you can leverage
that information, that data that can take

110
00:06:29.709 --> 00:06:33.760
<v Ronak Mekwan>you to the next level, which is the
strategic asset management journey.

111
00:06:34.239 --> 00:06:40.200
<v Ronak Mekwan>That will help you and equip you to
increase the overall equipment lifespan, and

112
00:06:40.200 --> 00:06:44.839
<v Ronak Mekwan>then we will end up into asset investment
planning, which most of the manufacturers

113
00:06:44.839 --> 00:06:46.239
<v Ronak Mekwan>call Capital planning, right?

114
00:06:46.350 --> 00:06:49.959
<v Ronak Mekwan>But in a nutshell, it's, it's a synonym
for asset investment planning.

115
00:06:50.239 --> 00:06:52.519
<v Ronak Mekwan>How are you planning and managing your
assets?

116
00:06:52.589 --> 00:06:57.920
<v Ronak Mekwan>So this entire pyramid, what we call, and
this is very near and dear to my heart

117
00:06:57.920 --> 00:07:03.390
<v Ronak Mekwan>because that provides you a very Broad
level understanding of how you would like to

118
00:07:03.390 --> 00:07:07.429
<v Ronak Mekwan>manage your assets, if you are on an
intermediate level, if you're just starting

119
00:07:07.429 --> 00:07:11.670
<v Ronak Mekwan>your asset management journey, or if
you're on a well advanced level, that will tell

120
00:07:11.670 --> 00:07:15.230
<v Ronak Mekwan>you where you are and what would be the
next step in your journey.

121
00:07:15.309 --> 00:07:18.950
<v Ronak Mekwan>So, I just want to start this conversation
from this pyramid so everybody has a

122
00:07:18.950 --> 00:07:23.239
<v Ronak Mekwan>clear understanding of what would be an
ideal asset management journey look like for

123
00:07:23.239 --> 00:07:24.829
<v Ronak Mekwan>any organization.

124
00:07:26.440 --> 00:07:31.040
<v Ronak Mekwan>Moving on, so everyone knows, everything
starts from data, right?

125
00:07:31.160 --> 00:07:34.279
<v Ronak Mekwan>So let me give you an example, and as I
said, I come from manufacturing.

126
00:07:34.619 --> 00:07:37.970
<v Ronak Mekwan>Every morning in my previous work life, as
soon as I go, the first question I was

127
00:07:37.970 --> 00:07:39.489
<v Ronak Mekwan>asked, Hey, how did we do yesterday?

128
00:07:39.730 --> 00:07:40.899
<v Ronak Mekwan>What was the equipment downtime?

129
00:07:41.010 --> 00:07:42.239
<v Ronak Mekwan>What was the production throughput?

130
00:07:42.309 --> 00:07:46.940
<v Ronak Mekwan>What was the overall equipment
effectiveness, because that's what everybody wants to

131
00:07:46.940 --> 00:07:52.940
<v Ronak Mekwan>know and everybody is keen to learn about
the numbers, the projections, the

132
00:07:52.940 --> 00:07:53.540
<v Ronak Mekwan>performance, right?

133
00:07:53.660 --> 00:07:55.489
<v Ronak Mekwan>So what is the center of everything?

134
00:07:55.660 --> 00:07:56.660
<v Ronak Mekwan>It's the data.

135
00:07:57.309 --> 00:08:01.679
<v Ronak Mekwan>But let me ask you, everyone, and you can
ask yourself, just providing you with the

136
00:08:01.679 --> 00:08:07.559
<v Ronak Mekwan>numbers and just providing you with the
raw data, will that be helpful to make any

137
00:08:07.559 --> 00:08:10.700
<v Ronak Mekwan>judgment or any, any strategic decision?

138
00:08:10.920 --> 00:08:11.329
<v Ronak Mekwan>No, right?

139
00:08:11.519 --> 00:08:16.220
<v Ronak Mekwan>Because you need to convert data, and
that's why I have created this slide, which

140
00:08:16.640 --> 00:08:18.920
<v Ronak Mekwan>explains exactly what is the difference.

141
00:08:19.309 --> 00:08:20.989
<v Ronak Mekwan>Data and information.

142
00:08:21.109 --> 00:08:25.500
<v Ronak Mekwan>So as I said, data is just a raw
information that is coming out from any software.

143
00:08:25.579 --> 00:08:29.510
<v Ronak Mekwan>So for an example, if you have a CMMS
implemented, it will provide you raw

144
00:08:29.510 --> 00:08:34.380
<v Ronak Mekwan>information about, about, let's say
previous day you did 50 preventative work

145
00:08:34.380 --> 00:08:37.500
<v Ronak Mekwan>orders, but how you leverage that data.

146
00:08:37.750 --> 00:08:43.659
<v Ronak Mekwan>So in a, in a, in a layman term and a
laywoman term, When you convert data into

147
00:08:43.659 --> 00:08:50.099
<v Ronak Mekwan>actionable insights, when you tie in
actions against those numbers, that's when

148
00:08:50.099 --> 00:08:54.010
<v Ronak Mekwan>magic, magic starts to happen, and that's
where you start seeing different trends,

149
00:08:54.299 --> 00:08:58.539
<v Ronak Mekwan>different areas of uh what is trending and
what is not trending.

150
00:08:58.659 --> 00:09:00.320
<v Ronak Mekwan>For example, let me give you an example.

151
00:09:00.900 --> 00:09:05.460
<v Ronak Mekwan>If you get a trend of polyop production
equipment for the last one week, now you are

152
00:09:05.460 --> 00:09:06.619
<v Ronak Mekwan>comparing that trend.

153
00:09:06.909 --> 00:09:12.130
<v Ronak Mekwan>Into information saying, hey, one of my
production filler is constantly going down

154
00:09:12.130 --> 00:09:14.219
<v Ronak Mekwan>for at least 1 hour per shift.

155
00:09:14.280 --> 00:09:15.710
<v Ronak Mekwan>So now you have a trend.

156
00:09:15.989 --> 00:09:20.309
<v Ronak Mekwan>Now you have the data for the last 7 days,
that equals to almost 30 some hours worth

157
00:09:20.309 --> 00:09:22.909
<v Ronak Mekwan>of downtime just on one single piece of
equipment.

158
00:09:23.260 --> 00:09:27.580
<v Ronak Mekwan>So now, based on that information, now you
can start thinking more proactively to go

159
00:09:27.580 --> 00:09:30.729
<v Ronak Mekwan>back and talk to your maintenance team,
talk to your maintenance supervisor to

160
00:09:30.729 --> 00:09:35.099
<v Ronak Mekwan>understand what is the root cause, why we
are losing every day, one hour on a single

161
00:09:35.099 --> 00:09:36.619
<v Ronak Mekwan>piece of equipment, right?

162
00:09:36.700 --> 00:09:42.280
<v Ronak Mekwan>So, just wanted to give you a more basic
example to understand that only uh raw data

163
00:09:43.179 --> 00:09:43.900
<v Ronak Mekwan>cannot help.

164
00:09:43.979 --> 00:09:47.140
<v Ronak Mekwan>You need to come up with the trends, you
need to attach that with your actionable

165
00:09:47.140 --> 00:09:50.599
<v Ronak Mekwan>insights, and you need to understand what
is your end goal.

166
00:09:51.099 --> 00:09:55.830
<v Ronak Mekwan>If you have the data, how would you like
the data to interpret to provide your end

167
00:09:55.830 --> 00:09:56.030
<v Ronak Mekwan>goal?

168
00:09:56.090 --> 00:09:58.659
<v Ronak Mekwan>Is your end goal to improve the equipment
efficiency?

169
00:09:58.950 --> 00:10:02.669
<v Ronak Mekwan>Is your end goal to improve the quality
product that you produce?

170
00:10:02.909 --> 00:10:08.109
<v Ronak Mekwan>Is your end goal is to reduce your
maintenance costs, so based on that, you can

171
00:10:08.109 --> 00:10:12.590
<v Ronak Mekwan>leverage this information, leverage this
data that can help you moving forward.

172
00:10:13.570 --> 00:10:17.700
<v Ronak Mekwan>OK, so that, based on that information,
let's talk about CMS because I already

173
00:10:17.700 --> 00:10:21.500
<v Ronak Mekwan>mentioned CMMS almost a few times already
in this session.

174
00:10:21.609 --> 00:10:25.609
<v Ronak Mekwan>So CMMS, which stands for Computerized
Maintenance Management Software.

175
00:10:25.700 --> 00:10:29.780
<v Ronak Mekwan>Most of you who are already here, they
must have either heard this terminology or

176
00:10:29.780 --> 00:10:31.429
<v Ronak Mekwan>have used this terminology.

177
00:10:31.900 --> 00:10:36.090
<v Ronak Mekwan>There are multiple, I would say a number
of different CMMS softwares that are

178
00:10:36.090 --> 00:10:38.059
<v Ronak Mekwan>available in the current market right now.

179
00:10:38.510 --> 00:10:40.119
<v Ronak Mekwan>There are some which are more basic.

180
00:10:40.400 --> 00:10:42.119
<v Ronak Mekwan>There are some which are intermediate.

181
00:10:42.359 --> 00:10:44.039
<v Ronak Mekwan>There are some which are well advanced.

182
00:10:44.359 --> 00:10:50.330
<v Ronak Mekwan>So that's where if I were you, I would
first understand what is my use case.

183
00:10:50.719 --> 00:10:55.599
<v Ronak Mekwan>First, you need to ask yourself, is it,
you need to buy SMSS because your

184
00:10:55.599 --> 00:11:00.799
<v Ronak Mekwan>maintenance cost is very high and you
don't have any, any data to support why your

185
00:11:00.799 --> 00:11:02.000
<v Ronak Mekwan>maintenance cost is going high.

186
00:11:02.080 --> 00:11:03.340
<v Ronak Mekwan>You don't have any information.

187
00:11:03.640 --> 00:11:04.599
<v Ronak Mekwan>That's one point.

188
00:11:05.039 --> 00:11:08.559
<v Ronak Mekwan>If you are increasing unplanned equipment
downtime and you don't know how to fix it,

189
00:11:08.729 --> 00:11:09.789
<v Ronak Mekwan>that's another use case.

190
00:11:11.820 --> 00:11:15.739
<v Ronak Mekwan>Spare party inventory budget, like this
was a very, very big issue for me in my

191
00:11:15.739 --> 00:11:18.669
<v Ronak Mekwan>previous work life, spare party inventory
management, right?

192
00:11:18.859 --> 00:11:21.099
<v Ronak Mekwan>Because the inventory management is a
very, very big.

193
00:11:21.140 --> 00:11:22.969
<v Ronak Mekwan>People think it's a back burner, but it's
not.

194
00:11:23.039 --> 00:11:27.619
<v Ronak Mekwan>According to me, I have seen almost close
to $1 million worth of write-off every

195
00:11:27.619 --> 00:11:28.010
<v Ronak Mekwan>fiscal year.

196
00:11:28.429 --> 00:11:33.190
<v Ronak Mekwan>Because we are not tracking inventory
accurately, maintenance staff, maintenance

197
00:11:33.190 --> 00:11:37.960
<v Ronak Mekwan>trades are not signing out motors,
gearboxes, bearings that they use it.

198
00:11:38.210 --> 00:11:42.809
<v Ronak Mekwan>They physically use it on the piece of
equipment, but they don't follow the process.

199
00:11:43.049 --> 00:11:44.710
<v Ronak Mekwan>So that is that your use case?

200
00:11:45.539 --> 00:11:49.729
<v Ronak Mekwan>Missed production goals, that goes hand in
hand with the equipment efficiency, your

201
00:11:49.729 --> 00:11:50.539
<v Ronak Mekwan>customer confidence.

202
00:11:50.619 --> 00:11:55.630
<v Ronak Mekwan>So when you are uh tracking your customer
fill rate, is that your, is your customer

203
00:11:55.630 --> 00:11:56.880
<v Ronak Mekwan>fill rate is going low?

204
00:11:57.809 --> 00:12:03.330
<v Ronak Mekwan>Is, or if you're getting more customer
complaints, that becomes your another use

205
00:12:03.330 --> 00:12:03.809
<v Ronak Mekwan>case, right?

206
00:12:04.049 --> 00:12:07.760
<v Ronak Mekwan>And the last but, but not the least, and
this is the center of our today's topic,

207
00:12:08.090 --> 00:12:09.770
<v Ronak Mekwan>lack, lack of data.

208
00:12:10.150 --> 00:12:14.549
<v Ronak Mekwan>If you don't have data, and I have, I was
in that situation in previous work like

209
00:12:14.549 --> 00:12:15.849
<v Ronak Mekwan>that, I joined the company.

210
00:12:16.109 --> 00:12:18.150
<v Ronak Mekwan>I'm the leader of the maintenance
department.

211
00:12:18.309 --> 00:12:21.789
<v Ronak Mekwan>I was told to start reading the
maintenance, but hey, what, we don't have any

212
00:12:21.789 --> 00:12:25.909
<v Ronak Mekwan>historical data because we are using a
legacy software we can, which can only do

213
00:12:25.909 --> 00:12:31.260
<v Ronak Mekwan>minimum tasks, which does not have a
capacity and capability to tell me what

214
00:12:31.260 --> 00:12:34.409
<v Ronak Mekwan>happened in this particular facility for
the past 2 years.

215
00:12:34.880 --> 00:12:39.880
<v Ronak Mekwan>So, that can become my big use case and
based on that information, I went ahead and

216
00:12:39.880 --> 00:12:42.799
<v Ronak Mekwan>I, I, I install and implement a brand new
CMMS system.

217
00:12:42.880 --> 00:12:47.280
<v Ronak Mekwan>So, how do you define a well-designed
CMMS, right?

218
00:12:47.359 --> 00:12:51.590
<v Ronak Mekwan>So when I look at any system, and
regardless of whether it's a CMMS, whether it's a

219
00:12:51.590 --> 00:12:55.669
<v Ronak Mekwan>Capital planning system, there are 3 main
pillars for those systems.

220
00:12:55.880 --> 00:12:57.359
<v Ronak Mekwan>You need to understand the technology.

221
00:12:57.650 --> 00:13:00.559
<v Ronak Mekwan>The technology, is it meeting your
demands?

222
00:13:00.609 --> 00:13:02.210
<v Ronak Mekwan>Is it meeting your needs?

223
00:13:02.489 --> 00:13:07.830
<v Ronak Mekwan>Second is the people, and that includes
management as well as the firsthand

224
00:13:07.969 --> 00:13:11.809
<v Ronak Mekwan>operators, maintenance trades, because
they're all going to use this, right?

225
00:13:11.890 --> 00:13:16.330
<v Ronak Mekwan>So you need to have that understanding
that people's skill in mind to see, hey, if I

226
00:13:16.330 --> 00:13:21.080
<v Ronak Mekwan>buy this particular software, will that be
helpful for my, my current workforce,

227
00:13:21.150 --> 00:13:21.289
<v Ronak Mekwan>right?

228
00:13:21.330 --> 00:13:23.890
<v Ronak Mekwan>And the third piece is process that you
need to understand that.

229
00:13:24.590 --> 00:13:28.270
<v Ronak Mekwan>Whatever the system and software you buy,
will that be integrated into your ERP

230
00:13:28.270 --> 00:13:28.510
<v Ronak Mekwan>system?

231
00:13:28.630 --> 00:13:33.150
<v Ronak Mekwan>Most of the companies use SAP, IBM Maximo,
Oracle, JD Edwards.

232
00:13:33.340 --> 00:13:36.830
<v Ronak Mekwan>So there are different ERPs, there are
different CMMS, but will they integrate

233
00:13:36.830 --> 00:13:37.109
<v Ronak Mekwan>together?

234
00:13:37.299 --> 00:13:39.530
<v Ronak Mekwan>And that is very, very common questions.

235
00:13:39.820 --> 00:13:42.000
<v Ronak Mekwan>Every manufacturer has it in mind.

236
00:13:42.070 --> 00:13:45.700
<v Ronak Mekwan>So, these are some of the use cases and
some of the benefits.

237
00:13:45.900 --> 00:13:49.929
<v Ronak Mekwan>If you have a well-designed system, the
first and foremost thing that one of the

238
00:13:49.929 --> 00:13:54.539
<v Ronak Mekwan>huge benefits for me in my previous work
life was you increase your equipment life

239
00:13:54.539 --> 00:13:55.099
<v Ronak Mekwan>expectancy.

240
00:13:55.539 --> 00:13:58.859
<v Ronak Mekwan>You produce more quality products, you
meet your production goals.

241
00:13:58.940 --> 00:14:02.059
<v Ronak Mekwan>So that, that's the bread and butter for
any manufacturer.

242
00:14:02.299 --> 00:14:03.849
<v Ronak Mekwan>You need to complete your production
goals.

243
00:14:04.059 --> 00:14:10.280
<v Ronak Mekwan>If you are told to finish 2 million pounds
worth of ketchup, or if you're told to do

244
00:14:10.450 --> 00:14:14.210
<v Ronak Mekwan>2000 cases of finished product on a weekly
basis, that's your target.

245
00:14:14.380 --> 00:14:15.299
<v Ronak Mekwan>You need to meet that target.

246
00:14:15.380 --> 00:14:19.739
<v Ronak Mekwan>If you always achieve that, that's
wonderful, but you need to meet that minimum

247
00:14:19.739 --> 00:14:20.559
<v Ronak Mekwan>target levels.

248
00:14:21.119 --> 00:14:24.909
<v Ronak Mekwan>You need to make sure that you are
attaching and you're meeting all your regulatory

249
00:14:24.909 --> 00:14:26.349
<v Ronak Mekwan>compliance needs as well.

250
00:14:26.590 --> 00:14:32.200
<v Ronak Mekwan>And most important, you can track all your
assets, all the inventory which is

251
00:14:32.200 --> 00:14:33.590
<v Ronak Mekwan>attached to your assets.

252
00:14:33.840 --> 00:14:37.559
<v Ronak Mekwan>So now, that is also helpful from the
financial standpoint, right?

253
00:14:37.640 --> 00:14:40.539
<v Ronak Mekwan>So if most of you who have worked in a
managerial role.

254
00:14:40.690 --> 00:14:44.429
<v Ronak Mekwan>You need to work with finance at every end
of the fiscal year to go through the

255
00:14:44.429 --> 00:14:48.929
<v Ronak Mekwan>depreciation cycle, the equipment
depreciation cycle, to understand that, hey, if I

256
00:14:48.929 --> 00:14:54.049
<v Ronak Mekwan>have a 5 year old boiler with this
equipment efficiency, how much dollar value it

257
00:14:54.049 --> 00:14:55.020
<v Ronak Mekwan>has right now.

258
00:14:55.289 --> 00:14:59.789
<v Ronak Mekwan>So, equipment efficiency, depreciation,
everything goes hand in hand.

259
00:15:01.849 --> 00:15:06.250
<v Ronak Mekwan>So that is what a well designed CMMS can
help achieve your goal.

260
00:15:06.359 --> 00:15:12.609
<v Ronak Mekwan>So again, you need to go back, rethink
what is your use cases and how or which

261
00:15:12.609 --> 00:15:15.729
<v Ronak Mekwan>system will help you resolve those use
cases.

262
00:15:16.950 --> 00:15:22.840
<v Ronak Mekwan>So before we're moving on to the next
slide and next topic, which is FCA, I would

263
00:15:22.840 --> 00:15:27.510
<v Ronak Mekwan>like to ask everybody that, did you guys
hear this terminology called FCA which

264
00:15:27.510 --> 00:15:33.659
<v Ronak Mekwan>stands for Facility Condition Assessment
Framework, or have you used it?

265
00:15:33.950 --> 00:15:34.830
<v Ronak Mekwan>How much are you familiar?

266
00:15:34.869 --> 00:15:37.750
<v Ronak Mekwan>So you can say yes, no, I'm not sure.

267
00:15:46.510 --> 00:15:51.460
<v Ronak Mekwan>Oh, so, I'm, I'm seeing, uh, not sure and
most of the 100% for not sure.

268
00:15:51.510 --> 00:15:53.489
<v Ronak Mekwan>So that's interesting.

269
00:15:53.630 --> 00:15:55.909
<v Ronak Mekwan>So let's go and talk about FCA.

270
00:15:56.030 --> 00:16:00.929
<v Ronak Mekwan>So FCA, as I said, it stands for
facilities Condition assessment, right?

271
00:16:01.030 --> 00:16:06.659
<v Ronak Mekwan>So, if I give you a brief context about
where it all originated, so FCA facility

272
00:16:06.659 --> 00:16:07.510
<v Ronak Mekwan>condition assessment.

273
00:16:07.664 --> 00:16:11.484
<v Ronak Mekwan>It firstly originated in early 1970s,
right?

274
00:16:11.585 --> 00:16:16.784
<v Ronak Mekwan>So I'm talking, we are sitting in 25, so
almost 70 years ago, this concept

275
00:16:16.784 --> 00:16:21.825
<v Ronak Mekwan>originated and the early adopters in North
America were universities and healthcare

276
00:16:21.825 --> 00:16:22.494
<v Ronak Mekwan>facilities.

277
00:16:23.025 --> 00:16:27.664
<v Ronak Mekwan>The reason behind that that they were
getting into more and more complex engineering

278
00:16:27.664 --> 00:16:31.864
<v Ronak Mekwan>design within their facilities, their
maintenance costs were going really high.

279
00:16:32.190 --> 00:16:36.630
<v Ronak Mekwan>And they wanted to have more structural
approach when it comes to the Capital

280
00:16:36.630 --> 00:16:36.969
<v Ronak Mekwan>planning.

281
00:16:37.159 --> 00:16:40.229
<v Ronak Mekwan>So that's where they started looking into
this concept.

282
00:16:40.270 --> 00:16:45.909
<v Ronak Mekwan>And then as the year passed by in early
1980s, it got affiliated, it has a

283
00:16:45.909 --> 00:16:52.630
<v Ronak Mekwan>registered benchmark, and in starting
early 2000, 2010 decade, now we got

284
00:16:52.630 --> 00:16:57.789
<v Ronak Mekwan>into the SARS model, where we have the
digital technology that can help you.

285
00:16:58.619 --> 00:17:02.369
<v Ronak Mekwan>Run this entire process and provide you
with the final outcome.

286
00:17:02.460 --> 00:17:03.700
<v Ronak Mekwan>So, how does it work?

287
00:17:03.820 --> 00:17:06.280
<v Ronak Mekwan>So let me explain to you in a more basic
term.

288
00:17:06.459 --> 00:17:11.468
<v Ronak Mekwan>FCA meaning is The company will come and
it will tell you.

289
00:17:11.588 --> 00:17:14.399
<v Ronak Mekwan>So for an example, if you're running a
food and well plant or if you're running an

290
00:17:14.399 --> 00:17:17.989
<v Ronak Mekwan>automotive plant and if you have 5, I'll
talk about the utilities.

291
00:17:18.029 --> 00:17:22.928
<v Ronak Mekwan>If you have 5 boilers and you want to know
out of those 5 boilers, what is their

292
00:17:23.389 --> 00:17:27.909
<v Ronak Mekwan>health as of 2025, if you have a
20-year-old boiler, if you have a 10-year-old

293
00:17:27.909 --> 00:17:32.698
<v Ronak Mekwan>boiler, regardless of their age, what is
their life expectancy left?

294
00:17:32.948 --> 00:17:35.369
<v Ronak Mekwan>So that's where FCA comes into place.

295
00:17:36.520 --> 00:17:40.060
<v Ronak Mekwan>So in my next slide, I want to talk about
the three core fundamentals.

296
00:17:40.369 --> 00:17:41.430
<v Ronak Mekwan>So how FCA works.

297
00:17:41.550 --> 00:17:43.959
<v Ronak Mekwan>First, it's, it talks about the condition.

298
00:17:44.310 --> 00:17:49.069
<v Ronak Mekwan>So it tells you once the entire process is
completed, once the entire inspection is

299
00:17:49.069 --> 00:17:53.829
<v Ronak Mekwan>completed, it will, the 1st, 1st thing is,
they will tell you what is the current

300
00:17:53.829 --> 00:17:54.689
<v Ronak Mekwan>state of the condition.

301
00:17:54.910 --> 00:17:59.150
<v Ronak Mekwan>If your boiler is 20 years old, if you
have already done a corrective repair for

302
00:17:59.150 --> 00:18:03.550
<v Ronak Mekwan>almost 50 times, if you have already
replaced and rebuild the gearbox, if you have

303
00:18:03.550 --> 00:18:05.449
<v Ronak Mekwan>already replaced the motor for 5 times.

304
00:18:06.130 --> 00:18:08.020
<v Ronak Mekwan>That will tell you what is the condition.

305
00:18:08.410 --> 00:18:13.050
<v Ronak Mekwan>Now, it will go back that condition, they
will take it and they will compare it with

306
00:18:13.050 --> 00:18:17.569
<v Ronak Mekwan>the OEM, so original equipment
manufacturer, and their specifications.

307
00:18:18.489 --> 00:18:24.349
<v Ronak Mekwan>To tell you what is the expectancy life
left after comparing with the OEM.

308
00:18:24.689 --> 00:18:28.609
<v Ronak Mekwan>The last, but what is one of the most
important is the risk factor.

309
00:18:28.930 --> 00:18:33.290
<v Ronak Mekwan>So now, let's say after comparing the
current condition with the overall health,

310
00:18:33.609 --> 00:18:35.569
<v Ronak Mekwan>according to the OEM, now I get to know.

311
00:18:35.900 --> 00:18:41.170
<v Ronak Mekwan>That hey Ronak, out of your 5 boilers, one
of them is running at 80% capacity, one

312
00:18:41.170 --> 00:18:44.479
<v Ronak Mekwan>is running at 70%, and one is running at
only 50%.

313
00:18:44.969 --> 00:18:49.329
<v Ronak Mekwan>So now, based on that, they will provide
me a risk factor.

314
00:18:49.650 --> 00:18:55.770
<v Ronak Mekwan>So the final outcome I will get is what we
call is a facility condition index, and

315
00:18:55.770 --> 00:18:57.770
<v Ronak Mekwan>that will be in a percentage score.

316
00:18:58.050 --> 00:19:01.089
<v Ronak Mekwan>So let's say if I'm told 20% percentage.

317
00:19:01.295 --> 00:19:07.494
<v Ronak Mekwan>Score for one of the boilers, that means
that it might only last and stay

318
00:19:07.494 --> 00:19:08.915
<v Ronak Mekwan>operational for the next one year.

319
00:19:09.255 --> 00:19:15.324
<v Ronak Mekwan>So based on that data, based on the most
accurate data, I can feed in that

320
00:19:15.324 --> 00:19:17.734
<v Ronak Mekwan>information into my Capital planning
process.

321
00:19:18.055 --> 00:19:24.045
<v Ronak Mekwan>So how FCA can help manufacturer, first,
it can help you in your current day to day

322
00:19:24.045 --> 00:19:26.454
<v Ronak Mekwan>operation by telling you the current state
of the condition.

323
00:19:26.839 --> 00:19:30.760
<v Ronak Mekwan>So that can help you with your CMMS
system, day to day operations, allocating

324
00:19:30.760 --> 00:19:35.319
<v Ronak Mekwan>budget, monthly budget, allocating spare
part invoices, that's all fine and done.

325
00:19:35.699 --> 00:19:41.900
<v Ronak Mekwan>The second piece is now based on that risk
factor, now you can support and, and, and

326
00:19:41.900 --> 00:19:45.060
<v Ronak Mekwan>leverage that information for your Capital
planning process.

327
00:19:45.170 --> 00:19:50.780
<v Ronak Mekwan>So FCA for, for, if you ask me, it's, it's
an integral part of your asset management

328
00:19:50.780 --> 00:19:54.819
<v Ronak Mekwan>process because, because it can feed you
into your CMLS journey, and it can feed you

329
00:19:54.819 --> 00:19:57.459
<v Ronak Mekwan>into your, into your Capital planning
journey as well.

330
00:20:01.479 --> 00:20:01.839
<v Ronak Mekwan>OK.

331
00:20:02.069 --> 00:20:06.050
<v Ronak Mekwan>So we did talk about FC and how it can
help into the Capital planning.

332
00:20:06.640 --> 00:20:10.359
<v Ronak Mekwan>So the next piece, I would like to talk
about the entire Capital planning process

333
00:20:10.359 --> 00:20:13.479
<v Ronak Mekwan>and the, what we call ELM asset life cycle
management.

334
00:20:14.119 --> 00:20:17.920
<v Ronak Mekwan>Most of you who have, who are currently
working in maintenance or project or

335
00:20:17.920 --> 00:20:22.489
<v Ronak Mekwan>engineering, Must be familiar with this
design, what we call asset, asset management

336
00:20:22.489 --> 00:20:23.109
<v Ronak Mekwan>life cycle.

337
00:20:23.290 --> 00:20:27.530
<v Ronak Mekwan>These are 4 different stages, planning,
acquisition, operation, and maintenance, and

338
00:20:27.530 --> 00:20:28.290
<v Ronak Mekwan>disposable, right?

339
00:20:28.369 --> 00:20:34.060
<v Ronak Mekwan>So, data, technology, the historical and
real-time data, and that's where my

340
00:20:34.060 --> 00:20:38.849
<v Ronak Mekwan>colleague Inara will talk about real-time
data as well, but both historical data and

341
00:20:38.849 --> 00:20:40.170
<v Ronak Mekwan>real-time data information.

342
00:20:40.719 --> 00:20:45.790
<v Ronak Mekwan>Help you enormously when you are talking
and when you're planning for your projects.

343
00:20:46.000 --> 00:20:47.439
<v Ronak Mekwan>I can give you a really good example.

344
00:20:47.560 --> 00:20:51.599
<v Ronak Mekwan>So I was one of my company, I won't tell,
talk about the company name, but that

345
00:20:51.599 --> 00:20:55.599
<v Ronak Mekwan>company, I was installing a brand new
cooking deck, and that cooking desk, deck was

346
00:20:55.599 --> 00:20:57.310
<v Ronak Mekwan>one of my major customers, McDonald's.

347
00:20:57.670 --> 00:21:01.400
<v Ronak Mekwan>So we, the, the data, and you can
understand McDonald's customers, they have a very

348
00:21:01.400 --> 00:21:06.479
<v Ronak Mekwan>rigorous data, very rigorous R&amp;D and
product development team who I was working very

349
00:21:06.479 --> 00:21:07.040
<v Ronak Mekwan>closely with.

350
00:21:07.310 --> 00:21:10.709
<v Ronak Mekwan>So on that information, I had to go back
and forth working with the third-party

351
00:21:10.709 --> 00:21:15.949
<v Ronak Mekwan>equipment manufacturers, providing them
the R&amp;D data, product development data that,

352
00:21:15.989 --> 00:21:20.069
<v Ronak Mekwan>hey, this is what I want, this is the
texture I want, this is the thickness I want,

353
00:21:20.140 --> 00:21:24.530
<v Ronak Mekwan>this is the viscosity I want out of the
product, based on that information we

354
00:21:24.810 --> 00:21:27.939
<v Ronak Mekwan>created and implemented and executed that
entire project.

355
00:21:28.310 --> 00:21:32.869
<v Ronak Mekwan>So the moral of the story here is whether
you are in your planning stage,

356
00:21:32.949 --> 00:21:37.390
<v Ronak Mekwan>acquisition phase, operation and
maintenance stage, or when you're at the disposal

357
00:21:37.390 --> 00:21:37.750
<v Ronak Mekwan>stage.

358
00:21:38.780 --> 00:21:43.680
<v Ronak Mekwan>Every stage, you require some sort of a
data to justify that stage.

359
00:21:43.880 --> 00:21:47.359
<v Ronak Mekwan>If you're talking operational maintenance,
as I just talked about in my previous

360
00:21:47.359 --> 00:21:51.239
<v Ronak Mekwan>slide, you need all your data, whether
it's a historical data or real-time data.

361
00:21:51.520 --> 00:21:55.430
<v Ronak Mekwan>When you want to disposal, you need your
finance data, which I talked about the

362
00:21:55.540 --> 00:21:56.800
<v Ronak Mekwan>depreciation part.

363
00:21:57.229 --> 00:22:01.859
<v Ronak Mekwan>You know, uh, in my previous work life, I
had to write off the forklift because we

364
00:22:01.859 --> 00:22:06.290
<v Ronak Mekwan>weren't using it for years because it was
broken down, and the cost to repair that,

365
00:22:06.390 --> 00:22:11.150
<v Ronak Mekwan>it wasn't justifiable because the amount
of cost it had on my finance sheet.

366
00:22:12.229 --> 00:22:13.459
<v Ronak Mekwan>So what can I do?

367
00:22:13.670 --> 00:22:18.469
<v Ronak Mekwan>The finance said, hey, you still have
$16,000 left for the forklift, but to repair

368
00:22:18.469 --> 00:22:20.369
<v Ronak Mekwan>and to use it is $40,000.

369
00:22:20.810 --> 00:22:25.489
<v Ronak Mekwan>So, how do you justify that that's where
the data helps to make you a business case

370
00:22:25.489 --> 00:22:29.930
<v Ronak Mekwan>where you can take it back to your one up,
in this case, C-level executive to

371
00:22:29.930 --> 00:22:33.300
<v Ronak Mekwan>explain them the scenario and come up with
the final outcome, right?

372
00:22:33.390 --> 00:22:39.290
<v Ronak Mekwan>So, If you're doing any sort of a project,
always make sure that you need to go with

373
00:22:39.290 --> 00:22:45.130
<v Ronak Mekwan>every stage of this uh project stage with
data availability.

374
00:22:47.689 --> 00:22:49.849
<v Ronak Mekwan>OK, so the next.

375
00:22:50.839 --> 00:22:52.800
<v Ronak Mekwan>is data integration into Capital planning.

376
00:22:52.920 --> 00:22:54.359
<v Ronak Mekwan>So this is a very key notes.

377
00:22:54.439 --> 00:22:56.079
<v Ronak Mekwan>I think I already touched base on that.

378
00:22:56.400 --> 00:22:58.839
<v Ronak Mekwan>But make sure you do the financial
analysis.

379
00:22:59.069 --> 00:23:04.000
<v Ronak Mekwan>And this terminology, and it become very,
very popular in the last minimum 5 years,

380
00:23:04.119 --> 00:23:06.959
<v Ronak Mekwan>what we call ROI, which stands for return
on investment, right?

381
00:23:07.560 --> 00:23:11.369
<v Ronak Mekwan>Before that, I was never asked to, to
showcase what is the return on investment for

382
00:23:11.369 --> 00:23:16.130
<v Ronak Mekwan>any project I did, but right past,
post-COVID, there was a rigorous standard that

383
00:23:16.130 --> 00:23:18.900
<v Ronak Mekwan>most of the companies started implementing
that talks about ROI.

384
00:23:19.380 --> 00:23:20.579
<v Ronak Mekwan>What is the return on investment.

385
00:23:20.650 --> 00:23:26.619
<v Ronak Mekwan>So, if I'm investing, if the company is
investing, for example, $150,000 in buying a

386
00:23:26.619 --> 00:23:29.890
<v Ronak Mekwan>brand new cardboard compactor, what is the
ROI, right?

387
00:23:30.099 --> 00:23:31.410
<v Ronak Mekwan>How do you calculate ROI?

388
00:23:32.300 --> 00:23:34.099
<v Ronak Mekwan>ROI can be calculated in dollars.

389
00:23:34.180 --> 00:23:37.979
<v Ronak Mekwan>So let's say if you increase your
production by 5%, that's an easy math.

390
00:23:38.300 --> 00:23:41.040
<v Ronak Mekwan>If you're increasing your efficiency,
that's an ROI itself.

391
00:23:41.410 --> 00:23:45.599
<v Ronak Mekwan>If you're reducing your label, so the new
carbon conductor might need 1 person

392
00:23:45.979 --> 00:23:47.930
<v Ronak Mekwan>versus the old one which needed 2%.

393
00:23:48.000 --> 00:23:51.300
<v Ronak Mekwan>So now I'm elementing one labor, that's an
easy math as well.

394
00:23:51.420 --> 00:23:55.369
<v Ronak Mekwan>So, again, you need to come up with some
sort of an ROI calculation.

395
00:23:55.619 --> 00:23:59.099
<v Ronak Mekwan>Most of the company right now feel
comfortable if they have less than 3 years' worth

396
00:23:59.099 --> 00:23:59.689
<v Ronak Mekwan>an ROYI.

397
00:23:59.939 --> 00:24:01.140
<v Ronak Mekwan>I have done most of.

398
00:24:01.295 --> 00:24:05.535
<v Ronak Mekwan>My products that has less than 2 years'
worth of an ROI attached, but just to keep

399
00:24:05.535 --> 00:24:09.535
<v Ronak Mekwan>that in mind whenever you are doing some
sort of a Capital planning process, do some

400
00:24:09.535 --> 00:24:13.255
<v Ronak Mekwan>sort of an ROI calculation, whether it's
an efficiency, whether it's a time, whether

401
00:24:13.255 --> 00:24:16.494
<v Ronak Mekwan>it's a labor, and whether it's a
production.

402
00:24:17.410 --> 00:24:19.829
<v Ronak Mekwan>Uh, enhance and efficiency.

403
00:24:20.130 --> 00:24:21.849
<v Ronak Mekwan>Risk management, always do the risk
management.

404
00:24:21.930 --> 00:24:25.750
<v Ronak Mekwan>That's where also you need data backup,
and that's where you go back, leverage the

405
00:24:25.750 --> 00:24:30.949
<v Ronak Mekwan>historical data, leverage the FCA data,
and according to that, you can prioritize.

406
00:24:31.089 --> 00:24:33.989
<v Ronak Mekwan>So let's say for example, how you do the
priority assessment.

407
00:24:34.530 --> 00:24:37.739
<v Ronak Mekwan>The FCA data is telling you, you need two
boilers in the next 2 years.

408
00:24:37.930 --> 00:24:41.530
<v Ronak Mekwan>One of them is only 20% efficiency left,
and one has a.

409
00:24:41.685 --> 00:24:42.824
<v Ronak Mekwan>50% efficiency left.

410
00:24:43.025 --> 00:24:44.224
<v Ronak Mekwan>So that's where you prioritize.

411
00:24:44.385 --> 00:24:48.864
<v Ronak Mekwan>The first year, you would replace the one
which is only 20% left, and the second

412
00:24:48.864 --> 00:24:53.545
<v Ronak Mekwan>year, you will replace the one which still
has 50% of the life expectancy.

413
00:24:53.655 --> 00:24:59.704
<v Ronak Mekwan>So even for the priority assessment, as I
said, all you need is a strong, accurate

414
00:24:59.704 --> 00:25:02.145
<v Ronak Mekwan>data to justify your business case, right?

415
00:25:02.305 --> 00:25:05.844
<v Ronak Mekwan>Because without data, making guesswork
will not take us anywhere else.

416
00:25:06.420 --> 00:25:09.829
<v Ronak Mekwan>And based on that, you can allocate your
budget accordingly, because now you have

417
00:25:09.829 --> 00:25:10.750
<v Ronak Mekwan>your priority set.

418
00:25:11.069 --> 00:25:13.030
<v Ronak Mekwan>Now you have already done your risk
management.

419
00:25:14.040 --> 00:25:17.670
<v Ronak Mekwan>The next step is very easy, allocate your
budget based on the priority, right?

420
00:25:17.780 --> 00:25:19.910
<v Ronak Mekwan>So everything goes step by step.

421
00:25:19.989 --> 00:25:25.910
<v Ronak Mekwan>This is all three-step process which I had
followed, and which made me successful in

422
00:25:25.910 --> 00:25:27.670
<v Ronak Mekwan>all of those projects that I led.

423
00:25:30.979 --> 00:25:37.180
<v Ronak Mekwan>OK, so I think I, I, I did talk a lot
about historical data, CMMS and the Capital

424
00:25:37.180 --> 00:25:38.040
<v Ronak Mekwan>planning in FCA.

425
00:25:38.130 --> 00:25:42.699
<v Ronak Mekwan>But now, at this moment, I will pass it on
to my colleague, Anaro, and he will take

426
00:25:42.699 --> 00:25:43.829
<v Ronak Mekwan>us from here.

427
00:25:44.170 --> 00:25:44.430
<v Ronak Mekwan>Anaro.

428
00:25:45.339 --> 00:25:45.859
<v Speaker 4>Hey, thank you, R.

429
00:25:46.790 --> 00:25:49.589
<v Speaker 4>Hey, good morning, good afternoon,
depending on where you guys are located.

430
00:25:49.760 --> 00:25:54.280
<v Speaker 4>So, I'm gonna talk about predictive
maintenance and about how Brightly and since I

431
00:25:54.280 --> 00:25:57.760
<v Speaker 4>worked together to give you that closed
loop maintenance solution, right?

432
00:25:57.839 --> 00:26:00.050
<v Speaker 4>It's, it's all about streamlining our
data.

433
00:26:00.390 --> 00:26:04.479
<v Speaker 4>As Ranne mentioned, um, data is cool, uh,
information is better.

434
00:26:04.640 --> 00:26:07.780
<v Speaker 4>So it's, it's what you do with that, with
that data that you have.

435
00:26:08.079 --> 00:26:12.239
<v Speaker 4>So everybody here knows that you have
pieces of equipment that have very important

436
00:26:12.239 --> 00:26:13.579
<v Speaker 4>pieces of data within them.

437
00:26:13.910 --> 00:26:18.829
<v Speaker 4>Um, and, you know, with, with the rise of
ignition, with Skater systems, MES cake

438
00:26:18.829 --> 00:26:22.109
<v Speaker 4>systems out there, you're starting to
collect that data and you're starting to play

439
00:26:22.109 --> 00:26:26.670
<v Speaker 4>with it, you're starting to formulate OEM,
OEM dashboards, uh, but there's, there's

440
00:26:26.670 --> 00:26:30.739
<v Speaker 4>so much more potential there, and it's
about utilizing that data from your assets,

441
00:26:31.030 --> 00:26:31.180
<v Speaker 4>right?

442
00:26:31.270 --> 00:26:35.949
<v Speaker 4>Feeding them into AI and actually using AI
in a real-world scenario, taking that

443
00:26:35.949 --> 00:26:36.750
<v Speaker 4>real-time data.

444
00:26:37.189 --> 00:26:41.540
<v Speaker 4>Getting predictions, getting forecasts on
failures, and then the closed loop

445
00:26:41.540 --> 00:26:46.750
<v Speaker 4>maintenance part is utilizing Brightly
work orders, utilizing that, all that data

446
00:26:46.750 --> 00:26:50.270
<v Speaker 4>that's stored from your maintenance
people, and filling in that, that, that gap,

447
00:26:50.390 --> 00:26:50.540
<v Speaker 4>right?

448
00:26:50.589 --> 00:26:55.479
<v Speaker 4>We're experiencing a gap in the market
now, where, In an all-industrial uh

449
00:26:55.479 --> 00:26:59.400
<v Speaker 4>manufacturing operations, you're, you're
having issues with operators, you're having

450
00:26:59.400 --> 00:27:03.109
<v Speaker 4>issues with your maintenance guys, your,
your senior people are exiting the

451
00:27:03.109 --> 00:27:05.140
<v Speaker 4>workforce, and, and there's a gap.

452
00:27:05.439 --> 00:27:08.760
<v Speaker 4>So it's, it's about capturing that
information, capturing the knowledge and

453
00:27:08.760 --> 00:27:13.930
<v Speaker 4>expertise, and having it all feed back
into a tool that you could exploit, right?

454
00:27:14.359 --> 00:27:14.949
<v Speaker 4>So that's.

455
00:27:15.829 --> 00:27:21.640
<v Speaker 4>That's what, that's what actually
utilizingI um AI in a real world world scenario

456
00:27:21.640 --> 00:27:22.109
<v Speaker 4>means.

457
00:27:22.270 --> 00:27:27.290
<v Speaker 4>So when you look at traditional
maintenance events, you're talking about, Being

458
00:27:27.290 --> 00:27:33.290
<v Speaker 4>notified of an issue when an operator um
notices that there's uh an abnormal noise

459
00:27:33.290 --> 00:27:37.329
<v Speaker 4>or the machine stopped, you have a fault
on the HMI screen, so a maintenance

460
00:27:37.329 --> 00:27:39.219
<v Speaker 4>operator is called over, right?

461
00:27:39.329 --> 00:27:43.930
<v Speaker 4>Your maintenance engineers, manufacturing
engineers, your line techs, all of these

462
00:27:43.930 --> 00:27:48.449
<v Speaker 4>people show up with very limited
information to the event, and now they have to

463
00:27:48.449 --> 00:27:49.010
<v Speaker 4>troubleshoot.

464
00:27:49.290 --> 00:27:52.849
<v Speaker 4>And not only do they have to troubleshoot,
but they have to do it in a high-stress

465
00:27:52.849 --> 00:27:53.599
<v Speaker 4>environment, right?

466
00:27:53.890 --> 00:27:58.010
<v Speaker 4>We all know how critical it is, um, to get
equipment back up and running.

467
00:27:58.130 --> 00:27:59.599
<v Speaker 4>I'm talking from experience.

468
00:27:59.930 --> 00:28:03.609
<v Speaker 4>Leaving the Navy, I started working as an
industrial electrician in the automotive

469
00:28:03.609 --> 00:28:08.569
<v Speaker 4>vertical, so I know that my number one
priority was restoring that equipment back to

470
00:28:08.569 --> 00:28:12.349
<v Speaker 4>uh operability and getting, getting the
operation back up and running.

471
00:28:12.819 --> 00:28:16.020
<v Speaker 4>So, it's, it's, it's safety involved in
that.

472
00:28:16.099 --> 00:28:21.739
<v Speaker 4>It's, did I get it right, not verifying,
trying multiple things around the machine

473
00:28:21.739 --> 00:28:22.839
<v Speaker 4>to get it up and running.

474
00:28:23.130 --> 00:28:28.650
<v Speaker 4>And if it starts great, um, you watch it
run 5, 10 minutes and it takes off and it

475
00:28:28.650 --> 00:28:30.510
<v Speaker 4>runs for the rest of your shift, you're
OK.

476
00:28:30.930 --> 00:28:36.010
<v Speaker 4>But it's that part of verification, that
missing link of getting that close loop

477
00:28:36.010 --> 00:28:41.010
<v Speaker 4>audit, right, of actually knowing that
your maintenance action was efficient, that's

478
00:28:41.010 --> 00:28:44.969
<v Speaker 4>missing in a lot of our, a lot of our, our
teams and a lot of our culture.

479
00:28:45.500 --> 00:28:49.589
<v Speaker 4>um, that goes into developing a larger
complex problem.

480
00:28:49.709 --> 00:28:55.989
<v Speaker 4>Something that maybe needed lubrication or
alignment, turns into 10 small downtime

481
00:28:55.989 --> 00:28:59.989
<v Speaker 4>events and then generates a big downtime
event that has mechanical and electrical

482
00:28:59.989 --> 00:29:04.550
<v Speaker 4>failure, then now you have a major
downtime created with all these other little

483
00:29:04.550 --> 00:29:06.949
<v Speaker 4>stops that go along the way with that, so.

484
00:29:07.329 --> 00:29:11.689
<v Speaker 4>How does AI actually help you, help your
maintenance teams, help your engineers,

485
00:29:11.810 --> 00:29:15.280
<v Speaker 4>help your quality guys in real-world
scenarios?

486
00:29:15.359 --> 00:29:20.569
<v Speaker 4>Well, we developed Sensi to help you in 3
very specific categories that actually

487
00:29:20.569 --> 00:29:22.050
<v Speaker 4>streamline that entire event.

488
00:29:22.170 --> 00:29:26.300
<v Speaker 4>So number 1, your team is going to be
notified by an attention engine, right?

489
00:29:26.400 --> 00:29:27.089
<v Speaker 4>And it's that.

490
00:29:27.560 --> 00:29:33.359
<v Speaker 4>Um, ability to create notifications when
you need them and eliminate distractions.

491
00:29:33.439 --> 00:29:37.479
<v Speaker 4>If I have a system that's just generating
alarms for your guys, eventually they're

492
00:29:37.479 --> 00:29:38.599
<v Speaker 4>gonna stop looking at them, right?

493
00:29:38.680 --> 00:29:39.520
<v Speaker 4>They're gonna ignore them.

494
00:29:39.780 --> 00:29:42.119
<v Speaker 4>You're gonna be like, ah, whatever, it's
all false positives.

495
00:29:42.199 --> 00:29:43.569
<v Speaker 4>Who cares anyways, right?

496
00:29:43.880 --> 00:29:48.199
<v Speaker 4>So we understand that getting
notifications, getting the right notifications,

497
00:29:48.319 --> 00:29:51.319
<v Speaker 4>getting a high level of fidelity when it
comes to accuracy.

498
00:29:51.609 --> 00:29:56.089
<v Speaker 4>And then eliminating false positives is
very critical when we talk about predictive

499
00:29:56.089 --> 00:30:00.410
<v Speaker 4>maintenance and an alert notification
system for your maintainers to actually keep

500
00:30:00.410 --> 00:30:04.609
<v Speaker 4>them engaged and focused on the equipment
that they actually need to perform actions

501
00:30:04.609 --> 00:30:04.810
<v Speaker 4>on.

502
00:30:04.930 --> 00:30:09.819
<v Speaker 4>So, this dynamic AI powered notification
system, Allows us to do just that.

503
00:30:10.160 --> 00:30:14.920
<v Speaker 4>Now, this notification system is powered
by another AI engine that runs in the

504
00:30:14.920 --> 00:30:16.989
<v Speaker 4>background, which is all ML analytics.

505
00:30:17.229 --> 00:30:19.390
<v Speaker 4>It's the way we go about creating models.

506
00:30:19.699 --> 00:30:20.760
<v Speaker 4>Now, why is this important?

507
00:30:20.880 --> 00:30:25.800
<v Speaker 4>What differentiates Sensii from anything
else out there, you know, these black box

508
00:30:25.800 --> 00:30:30.910
<v Speaker 4>systems or these um Other predictive
maintenance solutions where they're, they're

509
00:30:30.910 --> 00:30:36.310
<v Speaker 4>solely model-based, based on data
scientists creating very specific sets of data and

510
00:30:36.310 --> 00:30:40.869
<v Speaker 4>data algorithms for your equipment, um,
all those things are nice, right?

511
00:30:40.979 --> 00:30:41.910
<v Speaker 4>They're, they're, they're good.

512
00:30:41.989 --> 00:30:43.349
<v Speaker 4>I'm not saying they don't work.

513
00:30:43.510 --> 00:30:47.709
<v Speaker 4>They work in very specific scenarios, but
when you alter that scenario, you change

514
00:30:47.709 --> 00:30:49.670
<v Speaker 4>the speed of your motor, you change the
recipe.

515
00:30:50.170 --> 00:30:53.199
<v Speaker 4>You change the product that you're
running, then you might as well throw all that

516
00:30:53.199 --> 00:30:55.729
<v Speaker 4>out the window and start back over again,
right?

517
00:30:55.849 --> 00:31:01.709
<v Speaker 4>What we, what we noticed is having and
leveraging ML uh to automatically create

518
00:31:02.260 --> 00:31:06.439
<v Speaker 4>models from the bottoms-up approach, kind
of like RONex pyramid there.

519
00:31:06.530 --> 00:31:10.540
<v Speaker 4>We're, we're going to start with the
measures and creating models around measures

520
00:31:10.540 --> 00:31:11.069
<v Speaker 4>individually.

521
00:31:11.410 --> 00:31:15.250
<v Speaker 4>Then we're gonna create a measure uh or a
model that encapsulates all of those

522
00:31:15.250 --> 00:31:19.130
<v Speaker 4>smaller models within itself, and that's
going to be your asset, that's going to be

523
00:31:19.130 --> 00:31:23.329
<v Speaker 4>your motor, that's going to be your pump,
that's going to be your robot, and then

524
00:31:23.329 --> 00:31:28.949
<v Speaker 4>based on that, we're gonna create
different models that mirror the equipment,

525
00:31:30.199 --> 00:31:31.229
<v Speaker 4>operation, its function, right?

526
00:31:31.290 --> 00:31:34.709
<v Speaker 4>If you're running an auto, I'm gonna
filter out all the data, I don't care.

527
00:31:34.969 --> 00:31:40.880
<v Speaker 4>If I am running in recipe A or recipe B,
product X, product Y, I'm going to change

528
00:31:40.880 --> 00:31:44.319
<v Speaker 4>the model and I'm going to create models
based on what you're actually running.

529
00:31:44.680 --> 00:31:50.079
<v Speaker 4>So, I'm going to have very, very, very
high fidelity and accurate models built

530
00:31:50.079 --> 00:31:53.939
<v Speaker 4>because I have an understanding of what
your equipment is actually doing.

531
00:31:54.640 --> 00:31:59.079
<v Speaker 4>Now, Now we have that portion covered,
right, we have our data, we transform the

532
00:31:59.079 --> 00:32:03.199
<v Speaker 4>data into information, into information in
the way of notifications for your

533
00:32:03.199 --> 00:32:07.839
<v Speaker 4>maintenance teams, now your maintenance
team is notified, notified that there's a

534
00:32:07.839 --> 00:32:12.280
<v Speaker 4>potential issue, a forecasted issue into a
piece of equipment, whether it's a robot,

535
00:32:12.560 --> 00:32:18.560
<v Speaker 4>whether it's a welder, whether it's a
pump, um, a conveyor, they're going to have a

536
00:32:18.560 --> 00:32:23.750
<v Speaker 4>notification to go do something, they're
going to see a measure, and, Any other

537
00:32:23.750 --> 00:32:24.469
<v Speaker 4>solution out there

538
00:32:24.469 --> 00:32:27.689
<v Speaker 4>is going to give you an alert, it's
probably a threshold-based system.

539
00:32:28.099 --> 00:32:32.099
<v Speaker 4>You get a 1, a 0 turning into a 1, and
that would require an action, but you still

540
00:32:32.099 --> 00:32:33.310
<v Speaker 4>don't know what to do, right?

541
00:32:33.760 --> 00:32:38.010
<v Speaker 4>And that's where that gap comes into play,
that knowledge and expertise gap.

542
00:32:38.319 --> 00:32:43.750
<v Speaker 4>We included Gen AI into our tool within
the last 6 months to help bridge that gap

543
00:32:43.880 --> 00:32:48.000
<v Speaker 4>and gather all the information, you know,
from Brightly, from your work orders,

544
00:32:48.160 --> 00:32:53.069
<v Speaker 4>gather the information from your
maintenance teams, gather information from the ML

545
00:32:53.069 --> 00:32:57.099
<v Speaker 4>analytics, gather information from my
notification process, my notes.

546
00:32:57.395 --> 00:33:01.114
<v Speaker 4>Everything that comes together from this
UI will actually give me a very

547
00:33:01.114 --> 00:33:02.435
<v Speaker 4>prescriptive portion, right?

548
00:33:02.515 --> 00:33:07.555
<v Speaker 4>That prescriptive maintenance culture
where I actually have a dialogue that guides

549
00:33:07.555 --> 00:33:12.395
<v Speaker 4>me through what is going on with my piece
of equipment, why the application has

550
00:33:12.395 --> 00:33:16.834
<v Speaker 4>notified me that there's an issue, what
that issue potentially means, and then what

551
00:33:16.834 --> 00:33:19.265
<v Speaker 4>the most important thing, how do I go
about fixing it?

552
00:33:19.435 --> 00:33:20.974
<v Speaker 4>And then once I do take an action.

553
00:33:21.420 --> 00:33:25.760
<v Speaker 4>All that closed system-based solution that
I just talked about is having a work

554
00:33:25.760 --> 00:33:30.630
<v Speaker 4>order done, having that data from that
work order automatically fed back into this

555
00:33:30.630 --> 00:33:35.560
<v Speaker 4>application, the co-pilot learning from
your action and saying, OK, this specific

556
00:33:35.560 --> 00:33:37.410
<v Speaker 4>event meant this, right?

557
00:33:37.560 --> 00:33:41.369
<v Speaker 4>Meant this particular maintenance action,
and then having the audit, right?

558
00:33:41.520 --> 00:33:46.640
<v Speaker 4>Having the action take place and then all
the measures return back to its normal

559
00:33:46.640 --> 00:33:50.199
<v Speaker 4>level of operation, which is the piece
that most of us are missing.

560
00:33:50.510 --> 00:33:55.709
<v Speaker 4>And understanding that what I did was
actually effective and did solve the problem

561
00:33:55.709 --> 00:33:56.750
<v Speaker 4>at its root cause.

562
00:33:58.000 --> 00:33:59.280
<v Speaker 4>Now, Sensai itself works.

563
00:34:01.250 --> 00:34:04.609
<v Speaker 4>Just like the pyramid that Bronak showed
when he started this presentation, right?

564
00:34:04.650 --> 00:34:07.270
<v Speaker 4>I mentioned that we're going to have a
bottoms-up approach.

565
00:34:07.849 --> 00:34:10.959
<v Speaker 4>The very base layer of that is going to be
your factory networks.

566
00:34:11.010 --> 00:34:12.489
<v Speaker 4>It's gonna be your assets, right?

567
00:34:12.570 --> 00:34:14.239
<v Speaker 4>The data sources themselves.

568
00:34:14.570 --> 00:34:19.489
<v Speaker 4>Now, I mentioned how Brightly comes into
the picture, how CMMS ties in and the work

569
00:34:19.489 --> 00:34:21.969
<v Speaker 4>orders are very valuable pieces of data.

570
00:34:22.239 --> 00:34:25.810
<v Speaker 4>All of that is categorized into your
maintenance data, your preventive, your

571
00:34:25.810 --> 00:34:29.909
<v Speaker 4>corrective, your reconfigurations, setting
changes, anything that you do.

572
00:34:30.550 --> 00:34:34.669
<v Speaker 4>To a piece of equipment that allows me to
filter out information and give the system

573
00:34:34.669 --> 00:34:36.899
<v Speaker 4>a better understanding, I'm going to take.

574
00:34:37.219 --> 00:34:41.469
<v Speaker 4>The operational data that comes from your
PLCs, that comes from your controllers,

575
00:34:41.510 --> 00:34:45.469
<v Speaker 4>your DCS systems, that lets me know if the
system is running auto, whether it's

576
00:34:45.469 --> 00:34:50.169
<v Speaker 4>running manual, your teach pendants, if I
throw that in teach, then I don't really

577
00:34:50.169 --> 00:34:50.189
<v Speaker 4>care.

578
00:34:50.590 --> 00:34:55.350
<v Speaker 4>what my disturbance torque on my axis are
for my robots, I know that you're running

579
00:34:55.350 --> 00:34:58.699
<v Speaker 4>it in manual, and that is not running its
normal operation, right?

580
00:34:58.949 --> 00:35:00.290
<v Speaker 4>So I'm gonna filter that data out.

581
00:35:00.550 --> 00:35:04.709
<v Speaker 4>I'm going to focus when the machine is
running, and then what product or what

582
00:35:04.709 --> 00:35:10.250
<v Speaker 4>recipe, what weight, what speed that um
particular process is running at.

583
00:35:10.629 --> 00:35:14.629
<v Speaker 4>The condition monitoring data comes from
your assets, from your motor, from your

584
00:35:14.629 --> 00:35:18.570
<v Speaker 4>drives, from your sensors, from your PLC,
from your DCS.

585
00:35:19.419 --> 00:35:24.030
<v Speaker 4>All that gets fed into the core platform
of Senseii, which is 3 different AI engines

586
00:35:24.030 --> 00:35:24.459
<v Speaker 4>running.

587
00:35:24.750 --> 00:35:29.830
<v Speaker 4>They're all layered together to give you
the detention diagnostics and forecasts,

588
00:35:30.030 --> 00:35:35.909
<v Speaker 4>tools that you see um as anomalies,
trends, and step changes and diagnostics, and

589
00:35:35.909 --> 00:35:40.570
<v Speaker 4>all of that is controlled through the
attention engine, which actually filters out

590
00:35:40.790 --> 00:35:45.590
<v Speaker 4>false positives and it's dynamically
changing the status of an asset as I see it.

591
00:35:45.830 --> 00:35:51.070
<v Speaker 4>Essentially a health status as I see it as
a maintainer on the UI so I only focus on

592
00:35:51.070 --> 00:35:55.989
<v Speaker 4>what is truly in an anomaly state and what
is truly degrading, right?

593
00:35:56.469 --> 00:35:59.350
<v Speaker 4>So, I'm gonna jump in and I'm gonna show
you guys the tool itself, right?

594
00:35:59.389 --> 00:36:00.909
<v Speaker 4>I think that's the best part of this.

595
00:36:01.229 --> 00:36:04.790
<v Speaker 4>I think you guys are gonna get a better
understanding from the tool itself than from

596
00:36:04.790 --> 00:36:07.100
<v Speaker 4>me trying to break down the tool within
slides.

597
00:36:07.429 --> 00:36:11.909
<v Speaker 4>So, I'm gonna jump into that and uh Give
me a second here.

598
00:36:16.439 --> 00:36:17.409
<v Speaker 4>All right, perfect.

599
00:36:17.679 --> 00:36:21.729
<v Speaker 4>So you guys should be able to see um this,
this, the tool itself.

600
00:36:21.800 --> 00:36:27.520
<v Speaker 4>This is the UI it's web-based, so that
means you could deploy this on any

601
00:36:27.520 --> 00:36:28.679
<v Speaker 4>web-capable device.

602
00:36:28.919 --> 00:36:31.800
<v Speaker 4>So, I have clients that deploy this on
tablets.

603
00:36:31.949 --> 00:36:35.620
<v Speaker 4>I have clients that deploy this up on
screens outside their maintenance shop.

604
00:36:35.879 --> 00:36:41.639
<v Speaker 4>Um, all these accounts, there's no limited
or we don't apply a limitation to how

605
00:36:41.639 --> 00:36:43.320
<v Speaker 4>much users utilize this, right?

606
00:36:43.600 --> 00:36:46.540
<v Speaker 4>It's all about having this data
accessibility and then.

607
00:36:47.360 --> 00:36:50.919
<v Speaker 4>transforming that into information that's
valuable to your quality guys, your

608
00:36:50.919 --> 00:36:54.479
<v Speaker 4>production guys, your maintenance guys, so
it's far more than just getting

609
00:36:54.479 --> 00:36:55.979
<v Speaker 4>notifications on failure.

610
00:36:56.239 --> 00:36:59.439
<v Speaker 4>It's understanding your equipment and then
how your equipment operated during

611
00:36:59.439 --> 00:37:03.709
<v Speaker 4>certain circumstances and then utilizing
that information to go about planning your

612
00:37:03.709 --> 00:37:04.659
<v Speaker 4>maintenance actions.

613
00:37:05.139 --> 00:37:09.540
<v Speaker 4>Understanding where some quality defects
came from because you have the status of

614
00:37:09.540 --> 00:37:10.260
<v Speaker 4>your equipment.

615
00:37:10.540 --> 00:37:13.280
<v Speaker 4>So what we have up here is a navigational
level.

616
00:37:13.459 --> 00:37:18.899
<v Speaker 4>Um, this layer allows me to create a
customized way of navigating through the

617
00:37:18.899 --> 00:37:19.850
<v Speaker 4>solution, right?

618
00:37:19.899 --> 00:37:23.300
<v Speaker 4>This could be a global map that gives me a
representation.

619
00:37:24.310 --> 00:37:29.300
<v Speaker 4>Of all my plants across the globe and
gives me a status indicator and an insight

620
00:37:29.590 --> 00:37:32.909
<v Speaker 4>into those things and as it pops up here,
you guys will see that, right?

621
00:37:33.070 --> 00:37:35.090
<v Speaker 4>You'll see a map of several industries
here.

622
00:37:35.360 --> 00:37:39.629
<v Speaker 4>Um, and I could jump into those, but as
you see those, every single layer that I

623
00:37:39.629 --> 00:37:42.179
<v Speaker 4>could jump into has a health indicator.

624
00:37:42.290 --> 00:37:46.760
<v Speaker 4>That health indicator is going to show me
the highest level of attention case that's

625
00:37:46.760 --> 00:37:51.229
<v Speaker 4>within that specific sector, and as I
navigate through those, you'll see all the

626
00:37:51.229 --> 00:37:55.360
<v Speaker 4>information that's down below, the list of
cases, and then the information on those

627
00:37:55.360 --> 00:37:59.320
<v Speaker 4>cases be filtered to the specific level of
navigation that I'm in.

628
00:37:59.439 --> 00:38:00.860
<v Speaker 4>I'm going to jump back into the.

629
00:38:01.239 --> 00:38:05.600
<v Speaker 4>The uh level that I was showing
previously, which is a level that we created for

630
00:38:05.600 --> 00:38:07.870
<v Speaker 4>some of our shows, so we're back, right?

631
00:38:07.919 --> 00:38:12.250
<v Speaker 4>We're looking at this very customized
imagery, and we have different sections here,

632
00:38:12.350 --> 00:38:15.959
<v Speaker 4>all with a condition indicator on their
own, but I have one in, that's in red,

633
00:38:16.080 --> 00:38:16.239
<v Speaker 4>right?

634
00:38:16.300 --> 00:38:17.520
<v Speaker 4>I want to focus on red.

635
00:38:17.840 --> 00:38:21.110
<v Speaker 4>So if this was my area of responsibility,
I'm gonna jump in here.

636
00:38:21.310 --> 00:38:25.379
<v Speaker 4>Now, I could see that it's further broken
down into this very specific area.

637
00:38:25.719 --> 00:38:30.870
<v Speaker 4>Now it's limited to the 3 assets with 3
cases associated to the area that I'm in.

638
00:38:31.239 --> 00:38:35.639
<v Speaker 4>I'm gonna hide the map because we're gonna
focus in on the information, and then how

639
00:38:35.639 --> 00:38:40.840
<v Speaker 4>this tool actually works for your
maintainer and for your quality guys, for your

640
00:38:40.840 --> 00:38:45.600
<v Speaker 4>manufacturing engineers, for the people
that are using this, not data scientists,

641
00:38:45.679 --> 00:38:46.040
<v Speaker 4>right?

642
00:38:46.360 --> 00:38:51.159
<v Speaker 4>Easily could be used, we have things where
you could exploit algorithms using

643
00:38:51.159 --> 00:38:55.189
<v Speaker 4>derived measures within the application,
but the tool is really designed on the

644
00:38:55.189 --> 00:38:58.679
<v Speaker 4>front end for the specific purpose of
solving problems.

645
00:38:58.760 --> 00:39:00.800
<v Speaker 4>So let's go, let's, let's go ahead and do
that.

646
00:39:01.239 --> 00:39:02.370
<v Speaker 4>So I have a pump.

647
00:39:02.679 --> 00:39:03.760
<v Speaker 4>I have an anomaly here.

648
00:39:03.830 --> 00:39:08.600
<v Speaker 4>It says it was opened 12 days ago, so I
get a date stamp, and then as I navigate

649
00:39:08.600 --> 00:39:11.760
<v Speaker 4>through these, you'll see that the
information on the right-hand side, my right

650
00:39:11.760 --> 00:39:14.719
<v Speaker 4>window is gonna change depending on what
case I have open.

651
00:39:14.840 --> 00:39:16.300
<v Speaker 4>So I'm gonna focus on the critical one.

652
00:39:16.830 --> 00:39:21.149
<v Speaker 4>The co-pilot is the newest addition here,
um, and as I mentioned, it's going to give

653
00:39:21.149 --> 00:39:23.610
<v Speaker 4>me the prescriptive portion of this tool.

654
00:39:23.719 --> 00:39:26.500
<v Speaker 4>So it's gonna let me know what's
happening, it's gonna let me know that I have a

655
00:39:26.500 --> 00:39:30.790
<v Speaker 4>rising trend, that I have a correlated
behavior on these other measures, and as you

656
00:39:30.790 --> 00:39:31.739
<v Speaker 4>see, they're all velocity.

657
00:39:31.790 --> 00:39:32.350
<v Speaker 4>I have RMM.

658
00:39:32.574 --> 00:39:35.854
<v Speaker 4>I have peak to peak, which lets me know
that these are coming from vibration

659
00:39:35.854 --> 00:39:36.695
<v Speaker 4>sensors, right?

660
00:39:36.975 --> 00:39:38.514
<v Speaker 4>But I don't need to be an expert.

661
00:39:38.614 --> 00:39:43.375
<v Speaker 4>I don't have to know that to go in to
actually have some impact within my

662
00:39:43.375 --> 00:39:44.094
<v Speaker 4>maintenance team.

663
00:39:44.334 --> 00:39:49.725
<v Speaker 4>So as I navigate down, right, I see the
historical information, the data, the

664
00:39:49.725 --> 00:39:53.814
<v Speaker 4>anomalies, the evidence that these applica
that the application is trying to show

665
00:39:53.814 --> 00:39:54.094
<v Speaker 4>me.

666
00:39:54.439 --> 00:39:57.290
<v Speaker 4>But the best part about this is the
possible explanations.

667
00:39:57.370 --> 00:40:01.449
<v Speaker 4>It's going to let me know, hey, it's very
likely that you're running cavitation, or

668
00:40:01.449 --> 00:40:05.090
<v Speaker 4>that you're dry running your pump, that
there's an issue with misalignment or wear,

669
00:40:05.239 --> 00:40:11.090
<v Speaker 4>or that it's normal behavior due to
operational cycles as its last possible reason

670
00:40:11.090 --> 00:40:15.080
<v Speaker 4>why I'm having it, experiencing this
rising trend in my measures.

671
00:40:15.449 --> 00:40:18.729
<v Speaker 4>Now, the information doesn't just stop
there, right?

672
00:40:18.810 --> 00:40:24.320
<v Speaker 4>It, it, I have the ability as a user to
interact directly with the co-pilot.

673
00:40:24.399 --> 00:40:26.580
<v Speaker 4>I could ask it what actions.

674
00:40:27.709 --> 00:40:29.060
<v Speaker 4>Should I take to resolve?

675
00:40:35.709 --> 00:40:40.350
<v Speaker 4>And the application is gonna give me the
reasons, right, as it previously stated in

676
00:40:40.350 --> 00:40:44.070
<v Speaker 4>the acid window, in the case window, I'm
sorry, um, but it's gonna break it down a

677
00:40:44.070 --> 00:40:47.469
<v Speaker 4>little bit further, and then it's gonna
let me know where that documentation is

678
00:40:47.469 --> 00:40:48.989
<v Speaker 4>coming from, and this is key.

679
00:40:49.229 --> 00:40:52.870
<v Speaker 4>This is making a system that has the
ability to ingest data.

680
00:40:53.489 --> 00:40:58.889
<v Speaker 4>Um, making it smarter, making it smarter
via the manuals that your OEMs provide when

681
00:40:58.889 --> 00:41:02.929
<v Speaker 4>they ship you your systems, OEM manuals
from your pumps, OEM manuals for your

682
00:41:02.929 --> 00:41:07.649
<v Speaker 4>motors, your VFD, your drives, um, all of
that information being stored here, so

683
00:41:07.649 --> 00:41:12.610
<v Speaker 4>it's easily accessible for the people, uh,
doing and planning, um, maintenance

684
00:41:12.610 --> 00:41:13.199
<v Speaker 4>actions.

685
00:41:13.449 --> 00:41:15.550
<v Speaker 4>So I could see I have a machine passport
template.

686
00:41:15.929 --> 00:41:21.489
<v Speaker 4>I could say I have asset data, I have
failure characteristics, and I have contextual

687
00:41:21.489 --> 00:41:26.209
<v Speaker 4>information that allows the system to
understand where this data comes from, what it

688
00:41:26.209 --> 00:41:28.889
<v Speaker 4>means to the system, and then what failure
characteristics.

689
00:41:29.469 --> 00:41:32.679
<v Speaker 4>The pump can experience based on the data
that it's collecting, right?

690
00:41:32.790 --> 00:41:36.159
<v Speaker 4>So it has an understanding of where these
things are coming from.

691
00:41:36.389 --> 00:41:38.310
<v Speaker 4>Now, it's not limited to just that.

692
00:41:38.389 --> 00:41:41.949
<v Speaker 4>This is where CMMS were Brightly come into
the picture.

693
00:41:42.149 --> 00:41:47.949
<v Speaker 4>If I had issues that have um with other
pumps or with this pump a year ago or 2

694
00:41:47.949 --> 00:41:48.570
<v Speaker 4>years ago.

695
00:41:49.020 --> 00:41:50.889
<v Speaker 4>And something similar is happening now.

696
00:41:51.010 --> 00:41:53.419
<v Speaker 4>If it's happened before, the system's
gonna tell me, right?

697
00:41:53.449 --> 00:41:58.320
<v Speaker 4>It's gonna reference old work orders that
let me know, hey, I've seen this before,

698
00:41:58.419 --> 00:41:59.459
<v Speaker 4>it means a lubrication.

699
00:41:59.510 --> 00:42:01.600
<v Speaker 4>I've seen this before, it means alignment,
right?

700
00:42:01.659 --> 00:42:08.239
<v Speaker 4>So I'm gonna ask it just what documented
work do you have on

701
00:42:08.340 --> 00:42:09.429
<v Speaker 4>damaged seals?

702
00:42:16.090 --> 00:42:20.250
<v Speaker 4>So it's gonna let me know that it does
have a maintenance log entry uh dated October

703
00:42:20.250 --> 00:42:21.040
<v Speaker 4>24th.

704
00:42:21.290 --> 00:42:25.129
<v Speaker 4>It's gonna let me where that document is
located, who the technician was, what type

705
00:42:25.129 --> 00:42:30.889
<v Speaker 4>of work was uh um took place, the cause of
damage, and then the, uh, the, it's gonna

706
00:42:30.889 --> 00:42:31.850
<v Speaker 4>give me the link to the act.

707
00:42:32.120 --> 00:42:33.139
<v Speaker 4>Work order itself, right?

708
00:42:33.239 --> 00:42:36.370
<v Speaker 4>And it's not limited to just understanding
text.

709
00:42:36.770 --> 00:42:41.330
<v Speaker 4>We have a state of the art VLM ingestion
ingestion system that breaks down imagery,

710
00:42:41.409 --> 00:42:41.580
<v Speaker 4>right?

711
00:42:41.689 --> 00:42:46.129
<v Speaker 4>So you could put flow charts, procedures,
yes and no decision points, and all of

712
00:42:46.129 --> 00:42:50.250
<v Speaker 4>that be stored within the system to be
available for your maintainers, for the

713
00:42:50.250 --> 00:42:52.709
<v Speaker 4>people that need it most, when they need
it most.

714
00:42:53.209 --> 00:42:56.070
<v Speaker 4>I know you're running out of time here,
um, but, uh.

715
00:42:56.489 --> 00:43:00.530
<v Speaker 4>I wanna leave a little bit of room for,
for some questions here at the end and

716
00:43:00.530 --> 00:43:04.409
<v Speaker 4>wanted to hopefully you guys to
understand, you know, that closed loop maintenance

717
00:43:04.409 --> 00:43:08.209
<v Speaker 4>that comes within predictive maintenance
in Sensai and Brightly.

718
00:43:15.199 --> 00:43:19.800
<v Speaker 4>I am gonna talk about, sorry, a little bit
here, um, about what this actually does

719
00:43:19.800 --> 00:43:25.739
<v Speaker 4>for your equipment, um, the robot reducer
replacement, this is a success case where,

720
00:43:25.760 --> 00:43:29.719
<v Speaker 4>um, this is what the, what the system
actually looks like for, for the automotive

721
00:43:29.719 --> 00:43:34.620
<v Speaker 4>people that are, that are here, you'll
understand, um, the complexity of doing,

722
00:43:35.159 --> 00:43:39.949
<v Speaker 4>taking an action on join to, on, on that
reducer, um, especially if it's a heavy,

723
00:43:40.080 --> 00:43:42.699
<v Speaker 4>big robot, um, having a counterbalanced
system.

724
00:43:43.159 --> 00:43:48.080
<v Speaker 4>And then having to hoist and remove all
the weight off of it, take the gearbox off,

725
00:43:48.399 --> 00:43:50.199
<v Speaker 4>take the motor off, replace that.

726
00:43:50.669 --> 00:43:54.719
<v Speaker 4>Um, getting it all back together and then
hopefully you don't have to master your

727
00:43:54.719 --> 00:43:57.199
<v Speaker 4>axis, and then verifying every single
point.

728
00:43:57.320 --> 00:44:03.800
<v Speaker 4>You're talking, taking a 4-hour
maintenance event for a very, very, very

729
00:44:03.800 --> 00:44:05.199
<v Speaker 4>experienced group of people.

730
00:44:05.520 --> 00:44:11.000
<v Speaker 4>Now, if you don't have that within your
facility, you're talking about 8+ more hours

731
00:44:11.000 --> 00:44:12.439
<v Speaker 4>to get all of that done, right?

732
00:44:12.489 --> 00:44:16.110
<v Speaker 4>It's, it's a long period of time to, to be
without your piece of equipment,

733
00:44:16.479 --> 00:44:19.040
<v Speaker 4>especially a robot that shuts down your
line, right?

734
00:44:19.159 --> 00:44:21.685
<v Speaker 4>We, We know the type of impact that has.

735
00:44:22.044 --> 00:44:26.645
<v Speaker 4>So, when you look at disturbance and you
look at torque on your axis, you could have

736
00:44:26.645 --> 00:44:32.524
<v Speaker 4>up to a 5-month lead time, where you have
a clear view into what's going on with

737
00:44:32.524 --> 00:44:35.445
<v Speaker 4>your equipment and plan that ahead of
time.

738
00:44:35.604 --> 00:44:40.205
<v Speaker 4>Know that that gearbox is gonna fail, and
instead of doing it on the fly while

739
00:44:40.205 --> 00:44:43.324
<v Speaker 4>production is running and trying to move
your operators around cause you know,

740
00:44:43.364 --> 00:44:48.165
<v Speaker 4>they're done for the day, um, planning it
on a downtime event, planning on a PDM.

741
00:44:48.540 --> 00:44:52.500
<v Speaker 4>On a, on a preventive maintenance,
predictive maintenance Saturday or Sunday, and

742
00:44:52.500 --> 00:44:58.340
<v Speaker 4>having this work done on your time and on
your schedule by having the equipment uh

743
00:44:58.340 --> 00:44:59.260
<v Speaker 4>planted for you.

744
00:44:59.979 --> 00:45:01.000
<v Speaker 4>And yeah, that's it, guys.

745
00:45:01.179 --> 00:45:01.739
<v Speaker 4>That's it on me.

746
00:45:01.820 --> 00:45:05.620
<v Speaker 4>So hopefully you guys enjoyed the
presentation, uh, and I'm excited to hear what

747
00:45:05.620 --> 00:45:07.139
<v Speaker 4>your ques, what your questions.

748
00:45:09.879 --> 00:45:10.810
<v Stephanie>Thank you both.

749
00:45:10.939 --> 00:45:11.899
<v Stephanie>That was fantastic.

750
00:45:11.969 --> 00:45:15.129
<v Stephanie>We do have some questions here that have
come in.

751
00:45:15.570 --> 00:45:22.449
<v Stephanie>Um, the first question that came in here
is for Ranak, and it has to do, the

752
00:45:22.449 --> 00:45:28.959
<v Stephanie>person is asking, can you explain what
would be the first step in explaining to a

753
00:45:28.959 --> 00:45:34.830
<v Stephanie>manager, uh, why, or I'm sorry, how to
make the case for an asset management system?

754
00:45:36.979 --> 00:45:41.560
<v Ronak Mekwan>Yes, so for, for the first case, so
depending on the maturity level, and this is,

755
00:45:41.820 --> 00:45:45.340
<v Ronak Mekwan>this is how I see it, and this is how I
pursued it in my previous career.

756
00:45:45.659 --> 00:45:49.919
<v Ronak Mekwan>So the first thing is you need to have
some sort of a business case, and you have to

757
00:45:49.919 --> 00:45:55.040
<v Ronak Mekwan>tie in that business case with the
production and with the overall quality.

758
00:45:55.100 --> 00:45:59.729
<v Ronak Mekwan>Like, by implementing asset management,
you will have, let's say I'm just throwing

759
00:45:59.729 --> 00:46:02.580
<v Ronak Mekwan>the number 5% more production by the end
of 2025.

760
00:46:02.955 --> 00:46:09.465
<v Ronak Mekwan>Or you can increase your facility
conditions by 15% or reduce maintenance

761
00:46:09.465 --> 00:46:13.104
<v Ronak Mekwan>costs by $100,000 on a monthly average.

762
00:46:13.215 --> 00:46:18.344
<v Ronak Mekwan>So something as any project, you need to
tie in the numbers, you need to tie in the

763
00:46:18.344 --> 00:46:19.745
<v Ronak Mekwan>data that can reflect.

764
00:46:19.814 --> 00:46:24.665
<v Ronak Mekwan>So if I'm a plant manager, if you come to
me, and if I'm a CEO and if you tell me,

765
00:46:24.725 --> 00:46:28.425
<v Ronak Mekwan>hey, I just need the asset management
without having any context behind it.

766
00:46:28.729 --> 00:46:30.090
<v Ronak Mekwan>It's not going to make any sense.

767
00:46:30.209 --> 00:46:36.669
<v Ronak Mekwan>So, only unless they understand the
impact, you need to make sure your business case

768
00:46:37.590 --> 00:46:41.209
<v Ronak Mekwan>has an impact on your company's overall
organization, right?

769
00:46:41.280 --> 00:46:45.929
<v Ronak Mekwan>So, as I said, go with your production
numbers, go with your maintenance numbers, or

770
00:46:45.929 --> 00:46:50.889
<v Ronak Mekwan>go with your overall expansion numbers,
something which is more visionary or more

771
00:46:50.889 --> 00:46:55.209
<v Ronak Mekwan>strategic, that can align with your
C-level executive mindset.

772
00:46:56.750 --> 00:46:57.360
<v Stephanie>Thank you.

773
00:46:57.520 --> 00:46:59.540
<v Stephanie>Uh, similar question for you, Henaro.

774
00:46:59.679 --> 00:47:06.600
<v Stephanie>This person is asking, when talking about
sensors and AI, how

775
00:47:06.600 --> 00:47:12.320
<v Stephanie>can we make the case to leadership that
this will improve the production process and

776
00:47:12.320 --> 00:47:13.219
<v Stephanie>improve output?

777
00:47:14.120 --> 00:47:14.889
<v Speaker 4>Yeah, absolutely.

778
00:47:15.010 --> 00:47:16.510
<v Speaker 4>So we conduct assessments, right?

779
00:47:16.639 --> 00:47:21.250
<v Speaker 4>Um, ROI has already been mentioned here a
couple of times, and ROI is a big, big,

780
00:47:21.330 --> 00:47:26.399
<v Speaker 4>big building block to proving this to
leadership on how an application like Senseite

781
00:47:26.399 --> 00:47:29.010
<v Speaker 4>could have an impact within your specific
environment.

782
00:47:29.330 --> 00:47:32.610
<v Speaker 4>So we assess downtime that you're
currently experiencing, right?

783
00:47:32.729 --> 00:47:38.239
<v Speaker 4>Um, and that goes not just breaking down
hour-wise, how much product you're losing,

784
00:47:38.530 --> 00:47:43.250
<v Speaker 4>but goes into labor, it goes into all the
things that actually impact a downtime

785
00:47:43.250 --> 00:47:43.530
<v Speaker 4>event.

786
00:47:43.840 --> 00:47:48.669
<v Speaker 4>And then we calculate the type of um
efficiencies and the increase in productivity

787
00:47:48.969 --> 00:47:52.330
<v Speaker 4>and sustainability within your equipment
by reducing that downtime.

788
00:47:52.409 --> 00:47:57.290
<v Speaker 4>Just to give you an average, our clients
experience a 30% reduction in downtime

789
00:47:57.290 --> 00:48:01.810
<v Speaker 4>within the first year, and within the
second year, they experience up to 50%, right?

790
00:48:01.850 --> 00:48:02.429
<v Speaker 4>And that's huge.

791
00:48:04.409 --> 00:48:04.649
<v Stephanie>Great.

792
00:48:04.770 --> 00:48:06.530
<v Stephanie>Here's another question for Henaro.

793
00:48:07.010 --> 00:48:13.260
<v Stephanie>Are the first two steps of data gathering
from the day of Sensi implementation, or

794
00:48:13.260 --> 00:48:16.250
<v Stephanie>does your team pull in the history that we
already have?

795
00:48:17.360 --> 00:48:18.449
<v Speaker 4>No, that's a very good question.

796
00:48:18.570 --> 00:48:19.629
<v Speaker 4>So we do both.

797
00:48:19.889 --> 00:48:25.510
<v Speaker 4>We, we could pull in historical data um to
kind of train the system and get it ready

798
00:48:25.510 --> 00:48:30.449
<v Speaker 4>and look at deviations um that you've
experienced previously, but we're mostly going

799
00:48:30.449 --> 00:48:35.879
<v Speaker 4>to start the attention engine, which is
what actually runs the application, day one,

800
00:48:36.050 --> 00:48:36.219
<v Speaker 4>right?

801
00:48:36.370 --> 00:48:38.729
<v Speaker 4>So from live data, and the reason why we
do that.

802
00:48:38.979 --> 00:48:43.260
<v Speaker 4>It's because all of those AI layers are
interlocked with each other, so when there

803
00:48:43.260 --> 00:48:48.540
<v Speaker 4>is an anomaly, the system expects
resulting actions, and without those actions in

804
00:48:48.540 --> 00:48:54.060
<v Speaker 4>your historical data, it skews the way the
attention engine perceives, um, like step

805
00:48:54.060 --> 00:48:59.979
<v Speaker 4>changes or um peaks within your data, it
perceives those as normal operation without

806
00:48:59.979 --> 00:49:01.239
<v Speaker 4>any active feedback.

807
00:49:03.639 --> 00:49:04.320
<v Stephanie>Fantastic.

808
00:49:04.389 --> 00:49:08.060
<v Stephanie>And we have one last question that appears
to be for the both of you.

809
00:49:08.639 --> 00:49:14.679
<v Stephanie>And it says, uh, knowing what you have
explained in this

810
00:49:14.679 --> 00:49:20.040
<v Stephanie>presentation, how would it have changed
both of your manufacturing experience when

811
00:49:20.040 --> 00:49:21.860
<v Stephanie>you were working in manufacturing?

812
00:49:23.780 --> 00:49:27.300
<v Ronak Mekwan>So, I, I can go first and I can talk about
it forever, right?

813
00:49:27.500 --> 00:49:31.540
<v Ronak Mekwan>Because as I said, I worked in operations,
I worked in maintenance, and I worked in

814
00:49:31.540 --> 00:49:31.889
<v Ronak Mekwan>engineering.

815
00:49:31.949 --> 00:49:34.580
<v Ronak Mekwan>So those are three different pillars of
the company.

816
00:49:34.699 --> 00:49:38.860
<v Ronak Mekwan>But when I talk about these asset
management and all these manufacturing practices,

817
00:49:39.989 --> 00:49:43.820
<v Ronak Mekwan>Before, when, when I was, and I won't talk
about the company, but we didn't have any

818
00:49:43.820 --> 00:49:46.159
<v Ronak Mekwan>data, and that's where we implemented the
Scara system.

819
00:49:46.219 --> 00:49:50.780
<v Ronak Mekwan>We implemented the brand new CMMS system,
and we started tracking the data.

820
00:49:51.100 --> 00:49:56.639
<v Ronak Mekwan>The very first month were chaotic because
first change management, trades,

821
00:49:56.699 --> 00:49:59.030
<v Ronak Mekwan>maintenance, unionized companies, they
don't like it, right?

822
00:49:59.129 --> 00:50:03.060
<v Ronak Mekwan>So first thing first, the change
management was, was a hard piece, and that's where

823
00:50:03.060 --> 00:50:04.870
<v Ronak Mekwan>we have to get to work with the people
skill.

824
00:50:05.139 --> 00:50:10.370
<v Ronak Mekwan>But that in the sense, Second piece, when
people start seeing the impact of the data

825
00:50:10.540 --> 00:50:15.310
<v Ronak Mekwan>onto your day to day or into their day to
day operations and their work life, that's

826
00:50:15.310 --> 00:50:16.820
<v Ronak Mekwan>where the magic starts happening.

827
00:50:16.899 --> 00:50:21.820
<v Ronak Mekwan>So let's say if I'm a first line operator,
and if I say that no, now Rex team is

828
00:50:21.820 --> 00:50:25.300
<v Ronak Mekwan>maintaining this piece of conveyance very
well, so I don't have to go and take that

829
00:50:25.469 --> 00:50:26.909
<v Ronak Mekwan>cardboard away every 5 minutes.

830
00:50:26.979 --> 00:50:28.870
<v Ronak Mekwan>It's taking away a lot of my headache.

831
00:50:29.149 --> 00:50:32.250
<v Ronak Mekwan>Now I'm seeing that that improvement.

832
00:50:32.550 --> 00:50:34.229
<v Ronak Mekwan>Slowly but steadily, it's coming out.

833
00:50:34.320 --> 00:50:37.879
<v Ronak Mekwan>So, as I say, it's a journey, and that's
what I have it on the screen right now.

834
00:50:38.080 --> 00:50:38.760
<v Ronak Mekwan>It's a journey.

835
00:50:38.830 --> 00:50:41.000
<v Ronak Mekwan>Asset management is not like a flicking
the switch.

836
00:50:41.320 --> 00:50:45.830
<v Ronak Mekwan>You start, it's a baby steps, but as soon
as people start seeing the difference,

837
00:50:46.120 --> 00:50:50.399
<v Ronak Mekwan>people start seeing the improvements
around that, they will start putting more trust

838
00:50:50.399 --> 00:50:54.840
<v Ronak Mekwan>and they will start getting more engaged,
especially around working around the

839
00:50:54.840 --> 00:50:58.979
<v Ronak Mekwan>unionized company worker, working around
different diverse group of culture.

840
00:50:59.320 --> 00:51:00.459
<v Ronak Mekwan>That's what I would like to say.

841
00:51:02.620 --> 00:51:03.459
<v Speaker 4>Yeah, from my end.

842
00:51:04.370 --> 00:51:08.889
<v Speaker 4>Unfortunately, when I came up um working
as an industrial electrician, these tools

843
00:51:08.889 --> 00:51:09.850
<v Speaker 4>weren't around, right?

844
00:51:09.989 --> 00:51:11.189
<v Speaker 4>Co-pilot wasn't a thing.

845
00:51:11.310 --> 00:51:16.489
<v Speaker 4>I didn't have access to a Gen AI capable
system that could walk me through some of

846
00:51:16.489 --> 00:51:20.149
<v Speaker 4>the issues and walk my teams through some
of the issues that, you know, our

847
00:51:20.149 --> 00:51:25.169
<v Speaker 4>experience in industrial manufacturing,
um, but The, the way this would have changed

848
00:51:25.229 --> 00:51:27.060
<v Speaker 4>if I were in that environment now.

849
00:51:27.350 --> 00:51:29.310
<v Speaker 4>I mean, it's, it's, it's a huge impact.

850
00:51:29.429 --> 00:51:31.909
<v Speaker 4>Number one, like Roenick said, it's a
journey, right?

851
00:51:31.979 --> 00:51:33.510
<v Speaker 4>Predictive maintenance is not magic.

852
00:51:33.750 --> 00:51:37.379
<v Speaker 4>It's not something that I'm gonna be able
to just walk in your facility, open up a

853
00:51:37.379 --> 00:51:40.750
<v Speaker 4>box, and then you're gonna start getting
predictions left and right, and the system

854
00:51:40.750 --> 00:51:42.629
<v Speaker 4>telling you that something's gonna fail at
3 p.m.

855
00:51:42.629 --> 00:51:43.850
<v Speaker 4>on a, on a Friday.

856
00:51:44.070 --> 00:51:46.929
<v Speaker 4>Um, it is, it is definitely.

857
00:51:47.399 --> 00:51:52.320
<v Speaker 4>Exploiting data, understanding where the
gaps are, doing assessments, and then

858
00:51:52.320 --> 00:51:56.080
<v Speaker 4>taking the data that matters, putting it
into a system to give you tangible results,

859
00:51:56.320 --> 00:52:00.800
<v Speaker 4>and then those results having the type of
impact where me as a maintainer, utilizing

860
00:52:00.800 --> 00:52:06.000
<v Speaker 4>this tool not only affects um my level of
attention, it reduces my stress.

861
00:52:06.239 --> 00:52:09.360
<v Speaker 4>I'm able to focus on the piece of
equipment that need it.

862
00:52:09.560 --> 00:52:12.530
<v Speaker 4>Um, I'm able to plan things in ahead,
which is the biggest thing, right?

863
00:52:12.600 --> 00:52:17.129
<v Speaker 4>Is understanding whether I have the
components at hand to make a certain repair.

864
00:52:17.429 --> 00:52:21.110
<v Speaker 4>Um, talking to my production guys and
being like, hey, I need 30 minutes here.

865
00:52:21.229 --> 00:52:22.500
<v Speaker 4>I need an hour over here.

866
00:52:22.790 --> 00:52:23.870
<v Speaker 4>When can I do these things?

867
00:52:23.949 --> 00:52:27.939
<v Speaker 4>And then having those things be planned
out without a system running, which affects

868
00:52:27.939 --> 00:52:28.669
<v Speaker 4>safety, right?

869
00:52:28.860 --> 00:52:33.629
<v Speaker 4>Affects my troubleshooting, doing things
under power, um, and everybody here knows

870
00:52:33.629 --> 00:52:34.669
<v Speaker 4>lockout tag out, right?

871
00:52:34.739 --> 00:52:40.270
<v Speaker 4>But realistically, like, are your
maintainers following that type of procedure, uh,

872
00:52:40.510 --> 00:52:42.270
<v Speaker 4>you know, every time there's a downtime
event.

873
00:52:42.530 --> 00:52:46.570
<v Speaker 4>And it's, it's taking all those things
into consideration when you're talking about

874
00:52:46.570 --> 00:52:48.489
<v Speaker 4>a journey of this of this magnitude.

875
00:52:50.600 --> 00:52:54.969
<v Stephanie>Awesome, thank you both for answering
those questions and for the fantastic

876
00:52:54.969 --> 00:52:56.010
<v Stephanie>presentation.

877
00:52:56.399 --> 00:52:57.850
<v Stephanie>This concludes our webinar.

878
00:52:58.000 --> 00:53:00.270
<v Stephanie>Thank you so much to everyone for
attending.

879
00:53:00.290 --> 00:53:03.810
<v Stephanie>As a reminder, the recording, uh, will be
available soon.

880
00:53:04.169 --> 00:53:08.449
<v Stephanie>You'll receive it in your email with
information on how to, uh, view that recording

881
00:53:08.449 --> 00:53:10.030
<v Stephanie>and how to share it with others.

882
00:53:10.370 --> 00:53:11.489
<v Stephanie>And as always, if you.

883
00:53:11.600 --> 00:53:17.080
<v Stephanie>Have any questions, you can feel free to
reach out and we look forward to seeing you

884
00:53:17.080 --> 00:53:18.000
<v Stephanie>at our next webinar.

885
00:53:18.080 --> 00:53:22.320
<v Stephanie>Those are always available on our LinkedIn
page, and you'll get more information via

886
00:53:22.320 --> 00:53:23.989
<v Stephanie>email about our upcoming webinars.

887
00:53:24.320 --> 00:53:26.879
<v Stephanie>Thank you so much and enjoy the rest of
your day.

888
00:53:28.669 --> 00:53:33.629
<v Speaker 1>Please like and subscribe on all major
podcast channels and find out more about

889
00:53:33.629 --> 00:53:37.149
<v Speaker 1>Sensi predictive maintenance at
Siemens.com.
