WEBVTT
Language: en-US

1
00:00:01.139 --> 00:00:05.460
<v Chris Garrison>They might have 3 or 4 vibration analysts
on staff, people that they've developed

2
00:00:05.460 --> 00:00:07.920
<v Chris Garrison>from, from engineering and for maintenance
over time.

3
00:00:08.100 --> 00:00:12.939
<v Chris Garrison>Um, and send them off to get
certifications and, and, uh, maybe they would be in

4
00:00:12.939 --> 00:00:17.200
<v Chris Garrison>kind of an apprenticeship mode until they
can move into a, to a senior analyst role.

5
00:00:18.319 --> 00:00:23.389
<v Chris Garrison>But long story short, there, it takes
several years to develop an an analyst.

6
00:00:23.620 --> 00:00:29.190
<v Chris Garrison>Um, you can, you know, confidently look at
vibration data in its raw forms and, um.

7
00:00:30.030 --> 00:00:32.580
<v Chris Garrison>And accurately, you know, identify faults.

8
00:00:33.479 --> 00:00:37.020
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens.

9
00:00:37.200 --> 00:00:39.159
<v Speaker 2>And now your host, Nel Sullivan.

10
00:00:41.400 --> 00:00:45.349
<v Niall Sullivan>Hello and welcome to the latest episode of
the trend detection podcast.

11
00:00:46.169 --> 00:00:51.250
<v Niall Sullivan>I'm really pleased to be joined today, um,
by Chris Garrison, um, who has been on

12
00:00:51.250 --> 00:00:52.250
<v Niall Sullivan>the podcast before.

13
00:00:52.610 --> 00:00:57.529
<v Niall Sullivan>Um, it's been a, a trend recently, um,
where we've been discussing how many times,

14
00:00:58.400 --> 00:01:00.090
<v Niall Sullivan>uh, the guest has actually been on the
podcast.

15
00:01:00.150 --> 00:01:03.069
<v Niall Sullivan>I don't know if you remember Chris off the
top of your head, how many times, cause

16
00:01:03.069 --> 00:01:04.989
<v Niall Sullivan>I, I tend to forget these things, but

17
00:01:05.690 --> 00:01:09.430
<v Chris Garrison>yeah, 3 or 43 or 4.

18
00:01:09.650 --> 00:01:10.650
<v Chris Garrison>This may be the 4th time.

19
00:01:11.290 --> 00:01:12.250
<v Niall Sullivan>Yeah, there we go.

20
00:01:12.410 --> 00:01:12.690
<v Niall Sullivan>There we go.

21
00:01:12.769 --> 00:01:14.489
<v Niall Sullivan>And many more to come, I'm sure as well.

22
00:01:14.669 --> 00:01:15.589
<v Niall Sullivan>Um, I'd like to think.

23
00:01:15.930 --> 00:01:21.000
<v Niall Sullivan>But, um, but yeah, so today, today we're
talking about, um, vibration analysis, a

24
00:01:21.000 --> 00:01:25.489
<v Niall Sullivan>topic you're very deeply involved in, I
guess, I mean, we could talk, go into sort

25
00:01:25.489 --> 00:01:30.019
<v Niall Sullivan>of your background, Chris, and And how
you'll talk about this topic with customers

26
00:01:30.019 --> 00:01:33.580
<v Niall Sullivan>as well is going to be of great interest
and of course how it relates to predictive

27
00:01:33.580 --> 00:01:36.010
<v Niall Sullivan>maintenance, of course, because that's why
we're here, right?

28
00:01:36.220 --> 00:01:40.540
<v Niall Sullivan>So, um, but I guess before we get started,
Chris, maybe a quick intro from your side

29
00:01:40.540 --> 00:01:43.699
<v Niall Sullivan>for people who may not have listened to
your previous episodes before, just what you

30
00:01:43.699 --> 00:01:46.199
<v Niall Sullivan>do at Siemens and that kind of thing.

31
00:01:46.779 --> 00:01:46.900
<v Niall Sullivan>Yeah,

32
00:01:46.980 --> 00:01:47.300
<v Chris Garrison>absolutely.

33
00:01:47.510 --> 00:01:52.930
<v Chris Garrison>Been working with um Siemens and the Sensi
product for roughly 3 years in total now,

34
00:01:53.019 --> 00:01:54.239
<v Chris Garrison>but have been in the.

35
00:01:54.889 --> 00:02:00.410
<v Chris Garrison>Uh, predictive maintenance and condition
monitoring space for, uh, 22 or 23 years

36
00:02:00.410 --> 00:02:05.809
<v Chris Garrison>now, um, which feels like a lot to say,
but, uh, yeah, working with vibration

37
00:02:05.809 --> 00:02:11.550
<v Chris Garrison>analysis, instrumentation, and of course,
um, Um, you know, platforms, uh, such as,

38
00:02:11.600 --> 00:02:12.929
<v Chris Garrison>as Sensei.

39
00:02:13.710 --> 00:02:20.169
<v Chris Garrison>So yeah, 2022 years of, uh, And predictive
maintenance and condition monitoring

40
00:02:20.169 --> 00:02:20.309
<v Chris Garrison>background.

41
00:02:22.259 --> 00:02:26.270
<v Niall Sullivan>And I guess where did you first come
across this term vibration analysis?

42
00:02:26.550 --> 00:02:29.050
<v Niall Sullivan>Much earlier on in your career, I can only
presume.

43
00:02:29.910 --> 00:02:36.589
<v Chris Garrison>Yeah, yeah, um, in the beginning, it was,
uh, lugging around, uh, kind of

44
00:02:36.589 --> 00:02:41.669
<v Chris Garrison>heavy recording equipment, data
collectors, uh, a lot of personnel going to take

45
00:02:41.669 --> 00:02:44.009
<v Chris Garrison>surveys on US aircraft carriers.

46
00:02:45.050 --> 00:02:50.250
<v Chris Garrison>They would collect, uh, every machinery,
uh, or, excuse me, collect data from every

47
00:02:50.250 --> 00:02:54.179
<v Chris Garrison>piece of machinery on, on an aircraft
carrier, uh, once per quarter.

48
00:02:54.690 --> 00:03:00.649
<v Chris Garrison>It's called an MCA survey, um, and then
they would bring all the, the recorded data

49
00:03:00.649 --> 00:03:07.369
<v Chris Garrison>back and analyze it and issue a report to,
uh, help ensure readiness of the US

50
00:03:07.369 --> 00:03:07.830
<v Chris Garrison>Navy.

51
00:03:08.679 --> 00:03:13.440
<v Chris Garrison>And we've come a long way since then and
how we gather that data and how fluid and

52
00:03:13.440 --> 00:03:17.119
<v Chris Garrison>how quickly we can respond and provide
those types of details.

53
00:03:17.199 --> 00:03:23.440
<v Chris Garrison>But yeah, yeah, back in about 2004, I
guess now, um, it really started with manual

54
00:03:23.440 --> 00:03:27.880
<v Chris Garrison>data acquisition and going back and, and
digging into that data for, for weeks on

55
00:03:27.880 --> 00:03:30.059
<v Chris Garrison>end and, and providing manual reports.

56
00:03:32.259 --> 00:03:36.220
<v Niall Sullivan>And then what led you into sort of the
world of predictive maintenance as well then,

57
00:03:36.339 --> 00:03:38.149
<v Niall Sullivan>just to bring the two together, I guess
early on.

58
00:03:38.169 --> 00:03:38.300
<v Niall Sullivan>Yeah,

59
00:03:38.419 --> 00:03:43.220
<v Chris Garrison>yeah, um, I think, you know, working with
with machinery and and maintenance and

60
00:03:43.220 --> 00:03:44.179
<v Chris Garrison>then um.

61
00:03:45.119 --> 00:03:50.139
<v Chris Garrison>Joining an organization way, way back, uh,
ABB in the very beginning.

62
00:03:50.979 --> 00:03:57.690
<v Chris Garrison>Um, You know, just, just the interest of
problem solving and

63
00:03:58.889 --> 00:04:02.059
<v Chris Garrison>You know, providing good insightful
information from the very beginning.

64
00:04:02.139 --> 00:04:04.520
<v Chris Garrison>I think the mission is, is very much the
same today.

65
00:04:05.279 --> 00:04:10.630
<v Chris Garrison>Um, you know, can we, uh, prolong asset
life?

66
00:04:10.960 --> 00:04:14.080
<v Chris Garrison>Can we be more proactive in planning?

67
00:04:14.850 --> 00:04:21.019
<v Chris Garrison>Um, be less reactive, and, and I think
that, um, the goals are much the same and

68
00:04:21.019 --> 00:04:24.899
<v Chris Garrison>they've evolved over time and gotten much
more fluid and efficient.

69
00:04:25.179 --> 00:04:29.859
<v Chris Garrison>But, um, yeah, yeah, it's, it's always
been gratifying work, um, to be able to

70
00:04:29.859 --> 00:04:36.619
<v Chris Garrison>identify a potential or pending problem,
um, head it off and, uh, save everybody

71
00:04:36.619 --> 00:04:39.579
<v Chris Garrison>some time, headache, money, all of the
above.

72
00:04:41.209 --> 00:04:42.640
<v Niall Sullivan>No, exactly, exactly.

73
00:04:42.970 --> 00:04:48.040
<v Niall Sullivan>But I, I guess to, you know, move back
towards the, the vibration analysis side, um,

74
00:04:48.250 --> 00:04:51.369
<v Niall Sullivan>so I get this question might be obvious to
many people listening out there, so

75
00:04:51.369 --> 00:04:52.010
<v Niall Sullivan>apologies for this.

76
00:04:52.089 --> 00:04:56.450
<v Niall Sullivan>So I'm asking it from my perspective and
my understanding as a non-technical person,

77
00:04:56.489 --> 00:05:01.200
<v Niall Sullivan>I guess, but, um, what actually is
vibration analysis and how does it work in

78
00:05:01.200 --> 00:05:01.910
<v Niall Sullivan>reality?

79
00:05:02.769 --> 00:05:03.209
<v Chris Garrison>Sure, sure.

80
00:05:03.369 --> 00:05:09.390
<v Chris Garrison>So, obviously, every, every rotating piece
of equipment, um, Produces, you know,

81
00:05:09.510 --> 00:05:12.649
<v Chris Garrison>vibration, movement, uh, sound
measurements.

82
00:05:13.510 --> 00:05:18.920
<v Chris Garrison>And uh you know, from, from the shafting
of the equipment spinning up and rotating

83
00:05:18.920 --> 00:05:21.809
<v Chris Garrison>within all of its confining components
such as bearings.

84
00:05:22.510 --> 00:05:26.869
<v Chris Garrison>Um, every moving part within, within an
asset, you know, provides some excitation,

85
00:05:26.950 --> 00:05:29.489
<v Chris Garrison>some movement, a, a signal that can be
monitored.

86
00:05:30.149 --> 00:05:36.350
<v Chris Garrison>Um, maybe we've, you know, touched on the
history lessons in past podcasts, but It,

87
00:05:36.359 --> 00:05:40.880
<v Chris Garrison>it started with, uh, with guys with a
screwdriver to their ear, you know, walking up

88
00:05:40.880 --> 00:05:47.720
<v Chris Garrison>to a machine and, and, uh, and listening
and they could tell by the whine or, or, or

89
00:05:47.720 --> 00:05:53.640
<v Chris Garrison>sound of the machinery if it might have a
bearing issue and I think transferring

90
00:05:53.640 --> 00:05:58.839
<v Chris Garrison>that, that human ear, uh, magnifying it
and moving into, to providing some

91
00:05:58.839 --> 00:06:00.109
<v Chris Garrison>instrumentation to actually.

92
00:06:01.130 --> 00:06:06.540
<v Chris Garrison>Um, cover more or all of the frequencies
within a piece of equipment is really where

93
00:06:06.540 --> 00:06:08.579
<v Chris Garrison>that, uh, where that started.

94
00:06:11.100 --> 00:06:12.839
<v Niall Sullivan>And that's a, that's an interesting point
as well.

95
00:06:12.899 --> 00:06:17.619
<v Niall Sullivan>I mean, how, maybe we go into it deeper a
little later, but how do you bring those

96
00:06:17.619 --> 00:06:18.769
<v Niall Sullivan>two sort of close together?

97
00:06:18.899 --> 00:06:22.540
<v Niall Sullivan>So the technology side and the person who,
like I said, it's almost instinct, right?

98
00:06:22.619 --> 00:06:25.679
<v Niall Sullivan>It's someone who's known, known these
machines for many, many years.

99
00:06:25.820 --> 00:06:28.079
<v Niall Sullivan>And, so how do you bring those together in
reality?

100
00:06:29.329 --> 00:06:34.899
<v Chris Garrison>Yeah, I, I think in the beginning, um,
there was maybe some, some cautionary

101
00:06:34.899 --> 00:06:38.820
<v Chris Garrison>feelings about predictive maintenance,
about, um, you know, how effective it could

102
00:06:38.820 --> 00:06:39.440
<v Chris Garrison>be.

103
00:06:39.859 --> 00:06:46.019
<v Chris Garrison>I think you had a lot of career, um,
engineers and, and maintenance managers out

104
00:06:46.019 --> 00:06:50.220
<v Chris Garrison>there that knew their equipment inside and
out, and if they could hear it, that was

105
00:06:50.220 --> 00:06:51.040
<v Chris Garrison>good enough.

106
00:06:51.489 --> 00:06:55.820
<v Chris Garrison>Um, and I think breaking, breaking through
that barrier and showing them that with

107
00:06:55.820 --> 00:06:58.660
<v Chris Garrison>some acoustics equipment with
accelerometers and so on.

108
00:06:59.160 --> 00:07:03.760
<v Chris Garrison>You know, you can, you can learn that a
little bit before your human ear, ear can,

109
00:07:03.869 --> 00:07:08.839
<v Chris Garrison>can pick that up and maybe we, we're 2
weeks out, 3 weeks out from, from what you

110
00:07:08.839 --> 00:07:11.440
<v Chris Garrison>might later, you know, pick up with your
own ear.

111
00:07:11.470 --> 00:07:17.089
<v Chris Garrison>And I think that, um, Slowly you build
that trust and and people realize that this

112
00:07:17.089 --> 00:07:19.670
<v Chris Garrison>equipment can can obviously detect beyond.

113
00:07:20.649 --> 00:07:25.970
<v Chris Garrison>Um, but even maybe your best, uh, mechanic
out there can hear with a screwdriver or

114
00:07:25.970 --> 00:07:29.170
<v Chris Garrison>with their, you know, with their ear
alone.

115
00:07:29.980 --> 00:07:32.609
<v Chris Garrison>And yeah, yeah, I think it's a, it's a,
it's a process.

116
00:07:32.660 --> 00:07:38.320
<v Chris Garrison>I think today, hopefully, um, vibration
analysis is much more of a known and trusted

117
00:07:38.320 --> 00:07:40.320
<v Chris Garrison>entity, but maybe not always the case.

118
00:07:42.540 --> 00:07:45.290
<v Niall Sullivan>So I guess what are the sort of, you sort
of touched on it then.

119
00:07:45.339 --> 00:07:48.859
<v Niall Sullivan>So what are the sort of misconceptions
around vibration analysis?

120
00:07:48.940 --> 00:07:53.140
<v Niall Sullivan>What's the, yeah, what presumptions are
made, let's say around, around it.

121
00:07:54.140 --> 00:07:55.959
<v Chris Garrison>Yeah, I, I think that um.

122
00:07:57.529 --> 00:08:01.170
<v Chris Garrison>There has to be some care taken about the
application, the instrumentation.

123
00:08:01.209 --> 00:08:05.970
<v Chris Garrison>I think that, you know, today, maybe more
than ever, there are so many choices out

124
00:08:05.970 --> 00:08:06.309
<v Chris Garrison>there.

125
00:08:07.290 --> 00:08:13.609
<v Chris Garrison>Um, and it's not really a, a, uh, you
know, one for one, pick, pick any sensor, put

126
00:08:13.609 --> 00:08:17.450
<v Chris Garrison>it on any machine, you know, there's some
solution in there and there's some

127
00:08:17.450 --> 00:08:21.890
<v Chris Garrison>considerations that have to take place,
and I, and I think that There have been

128
00:08:21.890 --> 00:08:27.959
<v Chris Garrison>times where um sensors have been maybe
just kind of thrown out en masse, put on

129
00:08:27.959 --> 00:08:30.290
<v Chris Garrison>equipment without too much thought or
planning.

130
00:08:31.019 --> 00:08:35.419
<v Chris Garrison>And, and you know that could produce false
positives, false negatives.

131
00:08:36.330 --> 00:08:41.859
<v Chris Garrison>Uh Old, older engineer that I used to work
with, uh, referred to it as whack a mole,

132
00:08:42.359 --> 00:08:48.068
<v Chris Garrison>um, having problems erupt all over the
plant and, and, you know, now this new

133
00:08:48.068 --> 00:08:52.078
<v Chris Garrison>vibration equipment is, is telling you
you've got more problems and, and how much of

134
00:08:52.078 --> 00:08:52.948
<v Chris Garrison>it is actionable.

135
00:08:53.138 --> 00:08:56.500
<v Chris Garrison>Uh, I think Those are the cautionary
tales.

136
00:08:57.590 --> 00:09:03.340
<v Chris Garrison>But the good news is with, with proper
planning, um, with proper solutioning,

137
00:09:03.349 --> 00:09:08.469
<v Chris Garrison>matching the right sensors to the right
assets, um, you know, we can absolutely

138
00:09:08.469 --> 00:09:14.500
<v Chris Garrison>avoid all of that and uh You know, I, I
guess as with most things, some of these

139
00:09:14.500 --> 00:09:16.280
<v Chris Garrison>lessons are learned the hard way.

140
00:09:18.200 --> 00:09:19.239
<v Niall Sullivan>No, exactly, exactly.

141
00:09:19.400 --> 00:09:21.919
<v Niall Sullivan>And you, you mentioned one thing, you
know, an important part of the puzzle as well

142
00:09:21.919 --> 00:09:24.239
<v Niall Sullivan>as, you know, selecting vibration sensors.

143
00:09:24.289 --> 00:09:28.840
<v Niall Sullivan>So, you know, I mean, how to, how can
someone sort of go about choosing the right

144
00:09:28.840 --> 00:09:33.469
<v Niall Sullivan>sensors for their particular use case, the
right vibration sensor, I should say.

145
00:09:33.880 --> 00:09:38.840
<v Chris Garrison>Yeah, yeah, um, just, just preceding our
podcast here, we're spending a good hour or

146
00:09:38.840 --> 00:09:42.719
<v Chris Garrison>two on this very subject and, and, um, you
know.

147
00:09:43.119 --> 00:09:46.919
<v Chris Garrison>There's a lot to decipher and different
spec sheets and different things out there.

148
00:09:47.159 --> 00:09:53.880
<v Chris Garrison>We have a lot of Siemens and Sensei
approved partner solutions where we kind of vet

149
00:09:53.880 --> 00:09:56.400
<v Chris Garrison>them and match them to different asset
classes.

150
00:09:56.510 --> 00:09:58.419
<v Chris Garrison>So there are certainly.

151
00:09:59.150 --> 00:10:03.659
<v Chris Garrison>Folks on, on our team that, that can delve
in and, and help with that process.

152
00:10:03.789 --> 00:10:10.549
<v Chris Garrison>Um, we also, you know, try to provide
some, some straightforward material to that

153
00:10:10.549 --> 00:10:15.390
<v Chris Garrison>end to, to help you make some decisions
about sensors and instrumentation, but, um,

154
00:10:16.510 --> 00:10:23.510
<v Chris Garrison>Yeah, I think that uh it's something
everybody who is in the position of, of, you

155
00:10:23.510 --> 00:10:26.979
<v Chris Garrison>know, choosing censors should, should
educate themselves a bit and, and certainly I

156
00:10:26.979 --> 00:10:29.039
<v Chris Garrison>hope we can, we can help with that.

157
00:10:29.849 --> 00:10:30.890
<v Chris Garrison>Uh, where possible,

158
00:10:32.859 --> 00:10:37.500
<v Niall Sullivan>And then I guess, yeah, so again,
selection, the first thing, but you, you mentioned

159
00:10:37.500 --> 00:10:40.820
<v Niall Sullivan>also about sort of the rollout process
and, you know, whack a mole.

160
00:10:40.979 --> 00:10:41.890
<v Niall Sullivan>Well, I do love that.

161
00:10:41.900 --> 00:10:45.900
<v Niall Sullivan>I'm gonna take that one away, I think
we'll be it's a future podcast, but, um, but

162
00:10:45.900 --> 00:10:46.780
<v Niall Sullivan>that sort of strategy.

163
00:10:46.880 --> 00:10:51.859
<v Niall Sullivan>So what, you know, you know, I guess why,
why do a lot of organizations approach it

164
00:10:51.859 --> 00:10:55.809
<v Niall Sullivan>that way, just roll it out as far and wide
as they can and what can they, what

165
00:10:55.809 --> 00:10:57.640
<v Niall Sullivan>should they be thinking about instead?

166
00:10:58.380 --> 00:10:59.900
<v Chris Garrison>Yeah, uh, great question.

167
00:11:00.260 --> 00:11:04.229
<v Chris Garrison>So, um, ROI I think is, is top of mind,
right?

168
00:11:04.349 --> 00:11:08.830
<v Chris Garrison>Maintenance budgets can, can be some of
the first under threat, um.

169
00:11:09.880 --> 00:11:15.090
<v Chris Garrison>If you're going to have a Capital expense
or an operational, you know, opex expense

170
00:11:15.090 --> 00:11:19.049
<v Chris Garrison>for, for these sensors, um, where are
you're going to get the greatest payback,

171
00:11:19.099 --> 00:11:22.890
<v Chris Garrison>where you're going to get the greatest
justification, um, so looking at things like

172
00:11:22.890 --> 00:11:23.809
<v Chris Garrison>machine criticality.

173
00:11:24.900 --> 00:11:30.099
<v Chris Garrison>Um, you know, what assets within your
facility are going to stop the show, if you

174
00:11:30.099 --> 00:11:30.520
<v Chris Garrison>will.

175
00:11:31.179 --> 00:11:36.340
<v Chris Garrison>Um, you know, that, that might be one of
the best places to start to, to get that

176
00:11:36.340 --> 00:11:39.140
<v Chris Garrison>return, um, and, and then kind of moving
outward from there.

177
00:11:39.260 --> 00:11:45.380
<v Chris Garrison>So, We're starting a brand new discussion
with the, with the facility.

178
00:11:45.840 --> 00:11:51.640
<v Chris Garrison>We might say, you know, um, have you done
uh criticality assessment just yet?

179
00:11:52.270 --> 00:11:57.219
<v Chris Garrison>Um, you know, surely maintenance and
operations and everyone knows what's most

180
00:11:57.219 --> 00:12:01.710
<v Chris Garrison>critical in there, um, you know, to their
operations and what can shut down the

181
00:12:01.710 --> 00:12:02.070
<v Chris Garrison>plant.

182
00:12:03.070 --> 00:12:08.109
<v Chris Garrison>But, uh, you know, seeing if maybe they
formalize that process and uh we can get a

183
00:12:08.109 --> 00:12:12.849
<v Chris Garrison>look at what's most critical and what
challenges might exist around those assets.

184
00:12:15.219 --> 00:12:19.659
<v Niall Sullivan>And if I guess if we talk about vibration
analysis again, and industrial equipment,

185
00:12:19.780 --> 00:12:21.789
<v Niall Sullivan>so what, why is it so important?

186
00:12:22.349 --> 00:12:25.099
<v Niall Sullivan>You know, because there's lots of
different types of analysis that could be a lot

187
00:12:25.099 --> 00:12:26.460
<v Niall Sullivan>done and lots of different data types.

188
00:12:26.530 --> 00:12:30.729
<v Niall Sullivan>So why, why does vibration stand out with
certain use cases?

189
00:12:31.049 --> 00:12:31.260
<v Niall Sullivan>Yeah,

190
00:12:31.380 --> 00:12:36.700
<v Chris Garrison>there's lots of great PDM technologies,
um, vibration just seems to stand the test

191
00:12:36.700 --> 00:12:38.380
<v Chris Garrison>of time of being the most encompassing.

192
00:12:39.059 --> 00:12:44.659
<v Chris Garrison>If you have to choose one technology that
can identify, you know, the most fault

193
00:12:44.659 --> 00:12:48.119
<v Chris Garrison>modes within a piece of equipment, it's
generally vibration.

194
00:12:49.539 --> 00:12:55.049
<v Chris Garrison>If you have hyper low speed uh equipment,
um, or, or, or different types of assets,

195
00:12:55.099 --> 00:13:01.599
<v Chris Garrison>you know, you know, you might be able to
use thermography, um, Uh, you know, Oil

196
00:13:01.599 --> 00:13:05.599
<v Chris Garrison>analysis for some of these gearboxes and
things, but most of the other predictive

197
00:13:05.599 --> 00:13:09.919
<v Chris Garrison>maintenance technologies are rather niche,
if you will, you know, they're targeted

198
00:13:09.919 --> 00:13:11.900
<v Chris Garrison>to specific assets or specific.

199
00:13:12.780 --> 00:13:17.070
<v Chris Garrison>Um, problem statements out there, ultra
low speed equipment and so on.

200
00:13:17.429 --> 00:13:20.969
<v Chris Garrison>Vibration just kind of seems to be the
overall.

201
00:13:22.669 --> 00:13:25.109
<v Chris Garrison>I don't want to say one size fits all, but
it's the most encompassing of the

202
00:13:25.109 --> 00:13:25.809
<v Chris Garrison>technologies.

203
00:13:27.500 --> 00:13:31.950
<v Niall Sullivan>Yeah, and, and comes in maybe the right
words in the, in the sense, I mean, does it

204
00:13:31.950 --> 00:13:36.179
<v Niall Sullivan>cover certain machine types or certain
industries, but I guess what you're saying,

205
00:13:36.270 --> 00:13:40.099
<v Niall Sullivan>Chris, is no, it's, it's very sort of
broad can be broadly applied.

206
00:13:40.669 --> 00:13:44.369
<v Chris Garrison>Yeah, yeah, um, there's a lot of
commonalities in, in equipment.

207
00:13:45.070 --> 00:13:48.909
<v Chris Garrison>Certainly there are considerations from,
um, different verticals, whether it's food

208
00:13:48.909 --> 00:13:50.270
<v Chris Garrison>and beverage, oil and gas.

209
00:13:51.020 --> 00:13:52.609
<v Chris Garrison>Um, auto manufacturing.

210
00:13:53.570 --> 00:14:00.369
<v Chris Garrison>But in the end, we've got, you know,
typically motors, um, driving different pieces

211
00:14:00.369 --> 00:14:01.010
<v Chris Garrison>of equipment.

212
00:14:02.010 --> 00:14:07.770
<v Chris Garrison>And um the considerations really are are
in how variable that equipment might be in,

213
00:14:07.780 --> 00:14:09.130
<v Chris Garrison>in its operational environment.

214
00:14:09.200 --> 00:14:10.750
<v Chris Garrison>Does it change speeds a lot?

215
00:14:11.630 --> 00:14:14.929
<v Chris Garrison>Um, does it run at ultra low speeds, um.

216
00:14:16.530 --> 00:14:18.450
<v Chris Garrison>Uh, is the environment, you know.

217
00:14:19.179 --> 00:14:24.950
<v Chris Garrison>Particularly Um, harsh, you know, are
there really high temperatures, really low

218
00:14:24.950 --> 00:14:26.309
<v Chris Garrison>temperatures, and so on.

219
00:14:26.789 --> 00:14:29.390
<v Chris Garrison>So, yeah, I think you're, you're, you're
considering all these things.

220
00:14:29.429 --> 00:14:31.489
<v Chris Garrison>We're putting, um, calibrated.

221
00:14:32.539 --> 00:14:36.020
<v Chris Garrison>Sensors and things out into these
industrial environments and we've got to be able

222
00:14:36.020 --> 00:14:39.619
<v Chris Garrison>to stand up to to the elements, so that's
one consideration.

223
00:14:41.869 --> 00:14:46.059
<v Niall Sullivan>And do you, I don't know if it's the right
way to phrase, but do you, do you often,

224
00:14:46.280 --> 00:14:50.119
<v Niall Sullivan>do you get sort of questioned about why
vibration analysis versus another type of

225
00:14:50.119 --> 00:14:50.739
<v Niall Sullivan>analysis?

226
00:14:50.820 --> 00:14:54.359
<v Niall Sullivan>I know it's always, you know, a discussion
with the customer and finding out what's

227
00:14:54.359 --> 00:14:57.039
<v Niall Sullivan>best, and obviously there's a reason why
they work with vendors like Siemens to

228
00:14:57.039 --> 00:14:59.159
<v Niall Sullivan>provide that sort of advice.

229
00:14:59.320 --> 00:14:59.440
<v Chris Garrison>But

230
00:14:59.440 --> 00:15:01.419
<v Niall Sullivan>is there any sort of question marks?

231
00:15:04.320 --> 00:15:06.280
<v Chris Garrison>Yeah, yeah, I think, um.

232
00:15:07.909 --> 00:15:13.299
<v Chris Garrison>Especially today, uh, you know, you've got
these, these kind of inherent data points

233
00:15:13.299 --> 00:15:19.030
<v Chris Garrison>that are available from the OEM, um, maybe
you have, uh, some kind of vibration data

234
00:15:19.030 --> 00:15:24.130
<v Chris Garrison>already provided as part of the package
from the motor, you know, uh, manufacturer.

235
00:15:24.750 --> 00:15:28.150
<v Chris Garrison>Maybe you have, um, current and
temperature and some of these other things.

236
00:15:28.229 --> 00:15:34.650
<v Chris Garrison>So what we really do is, is look at, um,
failure mode or fault mode

237
00:15:34.869 --> 00:15:36.109
<v Chris Garrison>coverage, um.

238
00:15:37.010 --> 00:15:42.940
<v Chris Garrison>If we've got a small, highly efficient
servo motor, um, maybe criticality or, or

239
00:15:42.940 --> 00:15:48.059
<v Chris Garrison>replacement cost is rather low, and we've
got, um, you know, current and

240
00:15:48.059 --> 00:15:53.549
<v Chris Garrison>temperature, and we can calculate torque
and, and Things of that nature, you know,

241
00:15:53.659 --> 00:15:55.270
<v Chris Garrison>maybe you don't need vibration, right?

242
00:15:55.309 --> 00:15:58.809
<v Chris Garrison>That there is a, you know, an expense
associated with instrumenting.

243
00:15:59.390 --> 00:16:02.630
<v Chris Garrison>You don't have to put a vibration sensor
on everything, you know, particularly in

244
00:16:02.630 --> 00:16:03.830
<v Chris Garrison>our world, um.

245
00:16:04.880 --> 00:16:11.090
<v Chris Garrison>Thankfully, for, for Sensei, we can work
with the data that is available um from

246
00:16:11.090 --> 00:16:14.580
<v Chris Garrison>those motor manufacturers or from those
equipment manufacturers in general.

247
00:16:15.280 --> 00:16:21.080
<v Chris Garrison>But, um, as you move on to, to larger
equipment or as you look to be more

248
00:16:21.080 --> 00:16:28.020
<v Chris Garrison>encompassing with, with fault mode
coverage, um, It's not, uh, it's

249
00:16:28.020 --> 00:16:32.090
<v Chris Garrison>not really a stretch to where you start to
look at vibration analysis to, to fill in

250
00:16:32.090 --> 00:16:35.080
<v Chris Garrison>those gaps, uh, to cover more failure
modes.

251
00:16:37.190 --> 00:16:41.640
<v Niall Sullivan>And when, when implementing sort of either
vibration sensors or vibration analysis,

252
00:16:41.719 --> 00:16:45.919
<v Niall Sullivan>is there, what are some, some of the sort
of challenges or things organizations sort

253
00:16:45.919 --> 00:16:49.280
<v Niall Sullivan>of need to consider before, you know, sort
of going ahead with that?

254
00:16:50.380 --> 00:16:53.619
<v Chris Garrison>Oh, loaded question, very loaded question.

255
00:16:54.479 --> 00:16:54.840
<v Niall Sullivan>Um, I don't try to.

256
00:16:56.020 --> 00:16:57.900
<v Chris Garrison>No, no, I, I think, um.

257
00:16:58.729 --> 00:17:01.780
<v Chris Garrison>I think cooperation across different um.

258
00:17:02.659 --> 00:17:05.739
<v Chris Garrison>Different departments and different
stakeholders within an organization is very

259
00:17:05.739 --> 00:17:12.380
<v Chris Garrison>important, um, having IT and those
involved with data security involved from the

260
00:17:12.380 --> 00:17:18.780
<v Chris Garrison>very beginning, um, understanding and
assessing, you know, whether data can be moved

261
00:17:18.780 --> 00:17:24.859
<v Chris Garrison>to the cloud fluidly, um, or whether it
needs to be stored on the edge and, and, and

262
00:17:24.859 --> 00:17:26.060
<v Chris Garrison>maybe moved to different ways.

263
00:17:26.180 --> 00:17:28.500
<v Chris Garrison>So, so data architecture, in short.

264
00:17:29.489 --> 00:17:36.310
<v Chris Garrison>Um, and then of course, uh, you know,
machinery, um, there is, uh.

265
00:17:37.130 --> 00:17:39.130
<v Chris Garrison>Data interpretation and analysis, right?

266
00:17:39.170 --> 00:17:45.689
<v Chris Garrison>Who, who's going to take action on, on the
results, you know, they're um put forth

267
00:17:45.689 --> 00:17:47.130
<v Chris Garrison>by a platform like Sensei.

268
00:17:48.010 --> 00:17:54.369
<v Chris Garrison>Um, How, how might you feed information
back into the platform, um.

269
00:17:55.229 --> 00:17:56.729
<v Chris Garrison>To kind of close that loop, right?

270
00:17:56.910 --> 00:18:00.989
<v Chris Garrison>Um, let's say a fault has been identified,
maintenance has gone out and they've

271
00:18:00.989 --> 00:18:06.310
<v Chris Garrison>corrected it, um, you know, closing that
loop might be, uh, having the work order.

272
00:18:07.020 --> 00:18:11.699
<v Chris Garrison>Information fed back into a platform like
Sensei where you kind of close the loop

273
00:18:11.699 --> 00:18:15.140
<v Chris Garrison>and say, yeah, that that problem was
confirmed, we, we changed the bearing or we

274
00:18:15.140 --> 00:18:16.040
<v Chris Garrison>swapped the motor.

275
00:18:16.770 --> 00:18:19.280
<v Chris Garrison>Um And we're off and running.

276
00:18:19.859 --> 00:18:22.579
<v Chris Garrison>So maybe a long winded answer there, but
um.

277
00:18:23.380 --> 00:18:28.650
<v Chris Garrison>Going back to your original question,
having maintenance, plant management, having

278
00:18:28.650 --> 00:18:31.630
<v Chris Garrison>everyone on board, I think from the
beginning is, is very important.

279
00:18:32.250 --> 00:18:37.630
<v Chris Garrison>Um, Because it really takes that kind of
cross-department cooperation, I think, to,

280
00:18:37.750 --> 00:18:39.109
<v Chris Garrison>to, to be successful.

281
00:18:41.339 --> 00:18:45.479
<v Niall Sullivan>Yeah, no, absolutely, absolutely, it's,
it's something we often, we often talk about

282
00:18:45.619 --> 00:18:48.530
<v Niall Sullivan>on the, on this podcast as well, the
importance of alignment.

283
00:18:48.619 --> 00:18:53.140
<v Niall Sullivan>Don't, don't try and, you know, start
these projects or continue these projects

284
00:18:53.140 --> 00:18:55.839
<v Niall Sullivan>without alignment with other stakeholders.

285
00:18:56.310 --> 00:19:00.760
<v Niall Sullivan>Um, but maybe you could sort of talk us
through sort of a typical implementation of

286
00:19:00.760 --> 00:19:02.380
<v Niall Sullivan>vibration analysis, Chris.

287
00:19:02.479 --> 00:19:08.829
<v Niall Sullivan>Um, you know, what, if there is a typical,
and I know, no one, no project is the

288
00:19:08.829 --> 00:19:12.109
<v Niall Sullivan>same, right, but maybe there's an average
you could, you could take.

289
00:19:13.329 --> 00:19:16.239
<v Chris Garrison>Um, I really think it starts with an asset
list, you know.

290
00:19:17.050 --> 00:19:22.290
<v Chris Garrison>What, what equipment is in scope, what
equipment is already being considered, um, is

291
00:19:22.290 --> 00:19:25.609
<v Chris Garrison>that asset list really, you know,
encompassing all of the equipment?

292
00:19:26.390 --> 00:19:28.890
<v Chris Garrison>That, that could be monitored or should be
monitored.

293
00:19:29.430 --> 00:19:35.250
<v Chris Garrison>Um, again, back to criticality, but what's
most important to the facility and the

294
00:19:35.300 --> 00:19:35.689
<v Chris Garrison>operations.

295
00:19:36.390 --> 00:19:41.430
<v Chris Garrison>Um, you know, I want to clarify, I guess
that vibration analysis and, and predictive

296
00:19:41.430 --> 00:19:45.349
<v Chris Garrison>maintenance in general, certainly doesn't
have to just be applied to your most

297
00:19:45.349 --> 00:19:45.989
<v Chris Garrison>critical assets.

298
00:19:46.130 --> 00:19:48.130
<v Chris Garrison>I think we talked about it as a starting
point.

299
00:19:48.750 --> 00:19:49.189
<v Chris Garrison>Um.

300
00:19:50.069 --> 00:19:54.130
<v Chris Garrison>And when you're doing things like putting
on vibration sensors on the equipment, you

301
00:19:54.130 --> 00:19:56.689
<v Chris Garrison>know, you do have some expenditures there
to consider.

302
00:19:57.209 --> 00:20:02.619
<v Chris Garrison>Um, But even, even the, the least critical
type of equipment, you know, is a

303
00:20:02.619 --> 00:20:05.109
<v Chris Garrison>potential candidate for predictive
maintenance.

304
00:20:05.459 --> 00:20:08.310
<v Chris Garrison>I think you're, you're just at that point
thinking about spend, right?

305
00:20:08.500 --> 00:20:12.310
<v Chris Garrison>Do you want to, um, add additional
instrumentation?

306
00:20:12.939 --> 00:20:16.790
<v Chris Garrison>Um, what can be done with the data
environment you have today, I think we talked a

307
00:20:16.790 --> 00:20:22.270
<v Chris Garrison>lot about that, um, going back to You
know, whatever data might already be there

308
00:20:22.270 --> 00:20:25.489
<v Chris Garrison>from the OEM that's being fed into a DCS
system and so on.

309
00:20:26.150 --> 00:20:31.869
<v Chris Garrison>Um, But yeah, you can do a lot with the
data you currently have and then go to

310
00:20:31.869 --> 00:20:33.390
<v Chris Garrison>vibration from there.

311
00:20:33.479 --> 00:20:35.849
<v Chris Garrison>So back to the asset list, criticality.

312
00:20:36.530 --> 00:20:41.250
<v Chris Garrison>Um, Return on investment, maybe, you know,
cost versus benefit.

313
00:20:42.380 --> 00:20:47.239
<v Chris Garrison>For vibration and then digging into the
characteristics of that equipment.

314
00:20:47.420 --> 00:20:48.619
<v Chris Garrison>Um, how does it operate?

315
00:20:48.750 --> 00:20:52.479
<v Chris Garrison>Does it change, um, during its operational
characteristics frequently?

316
00:20:53.099 --> 00:20:55.959
<v Chris Garrison>Um, does it ramp up or ramp down in speed?

317
00:20:56.699 --> 00:21:01.859
<v Chris Garrison>Um, you know, again, maybe kind of
repetitive, but, um, the environment, how harsh

318
00:21:01.859 --> 00:21:02.300
<v Chris Garrison>is it?

319
00:21:03.180 --> 00:21:07.550
<v Chris Garrison>Um, is it, uh, maybe an Ax hazard rated
environment?

320
00:21:07.660 --> 00:21:13.109
<v Chris Garrison>Do we need to have special equipment that,
uh, is explosion proof, um, or spark

321
00:21:13.109 --> 00:21:13.569
<v Chris Garrison>proof?

322
00:21:14.650 --> 00:21:16.770
<v Chris Garrison>All those things, so, so, so much there.

323
00:21:17.790 --> 00:21:21.390
<v Niall Sullivan>Yeah, that is a lot of detail and that's
why there's scope workshops to, to go

324
00:21:21.390 --> 00:21:23.199
<v Niall Sullivan>through all this in, in great detail,
right?

325
00:21:23.510 --> 00:21:24.069
<v Niall Sullivan>Absolutely.

326
00:21:25.849 --> 00:21:29.569
<v Niall Sullivan>And in I mean you talked about right at
the beginning of the podcast you talked

327
00:21:29.569 --> 00:21:33.890
<v Niall Sullivan>about, you know, the the person walking
around, you know, getting a feel for the,

328
00:21:34.250 --> 00:21:40.400
<v Niall Sullivan>for the machine and things like that and
of course we're in an age of AI or cloud as

329
00:21:40.469 --> 00:21:41.930
<v Niall Sullivan>well, but AI and cloud.

330
00:21:42.209 --> 00:21:46.839
<v Niall Sullivan>But how, how have those two, technologies
or elements, how have they sort of

331
00:21:46.839 --> 00:21:49.089
<v Niall Sullivan>transformed vibration analysis?

332
00:21:50.380 --> 00:21:55.170
<v Chris Garrison>Oh, yeah, some fantastic changes there,
right?

333
00:21:55.290 --> 00:22:00.280
<v Chris Garrison>Um, going back to the old, um, naval
environment or marine environment I first kind

334
00:22:00.280 --> 00:22:05.910
<v Chris Garrison>of entered into where People went out and,
and collected data and, and, you know, it

335
00:22:05.910 --> 00:22:12.160
<v Chris Garrison>may be weeks really, um, before you had
some interpretation of that data, um,

336
00:22:12.640 --> 00:22:19.209
<v Chris Garrison>and before you were able to act on it and
You know, Failure mode progression rates

337
00:22:19.209 --> 00:22:23.130
<v Chris Garrison>can certainly vary greatly, and, and some
things may already fail by the time, you

338
00:22:23.130 --> 00:22:23.910
<v Chris Garrison>know, you really.

339
00:22:24.760 --> 00:22:26.839
<v Chris Garrison>Complete that round trip and and uh.

340
00:22:27.589 --> 00:22:31.910
<v Chris Garrison>And get an actionable report in the right
hands so somebody can do something to be

341
00:22:31.910 --> 00:22:33.410
<v Chris Garrison>preventative, to be proactive.

342
00:22:34.199 --> 00:22:41.119
<v Chris Garrison>Um, But, um, you know, with, with cloud
environments you can bring the experts right

343
00:22:41.119 --> 00:22:41.810
<v Chris Garrison>to your plant.

344
00:22:41.920 --> 00:22:48.239
<v Chris Garrison>You can, you know, deploy some of the most
advanced analytics, um, a platform like

345
00:22:48.239 --> 00:22:50.630
<v Chris Garrison>Senseii is always evolving, right?

346
00:22:50.750 --> 00:22:55.479
<v Chris Garrison>Um, software updates are fluid in the
cloud, new feature, new development, new

347
00:22:55.479 --> 00:23:02.000
<v Chris Garrison>function is, is right there and, and
ready, um, no more, you know, deploying kind of

348
00:23:02.000 --> 00:23:02.959
<v Chris Garrison>that, that, um.

349
00:23:03.640 --> 00:23:06.699
<v Chris Garrison>That bulkier on-site software upgrade.

350
00:23:07.160 --> 00:23:13.319
<v Chris Garrison>So I think you move data from, from the
plant floor to the cloud to the experts, you

351
00:23:13.319 --> 00:23:18.880
<v Chris Garrison>know, through the, through the best
analytics packages there are out there, and you

352
00:23:18.880 --> 00:23:24.040
<v Chris Garrison>could be alerted in minutes or hours of
impending, you know.

353
00:23:25.449 --> 00:23:27.329
<v Chris Garrison>faults and, and problems developing.

354
00:23:29.520 --> 00:23:33.959
<v Niall Sullivan>I guess has it, has it enabled the sort of
scalability of vibration analysis as

355
00:23:33.959 --> 00:23:38.349
<v Niall Sullivan>well, whereas it might be done very on
unlimited numbers of assets and things like

356
00:23:38.349 --> 00:23:41.540
<v Niall Sullivan>that, but I guess that's, that's one thing
to, that's a real benefit, right?

357
00:23:43.010 --> 00:23:45.349
<v Chris Garrison>Yeah, yeah, and I think, you know, um.

358
00:23:45.939 --> 00:23:49.020
<v Chris Garrison>There's a limited amount of people that
are interested in going out and kind of

359
00:23:49.020 --> 00:23:53.540
<v Chris Garrison>making a career out of vibration analysis
and becoming, you know, level 3 and 4

360
00:23:53.540 --> 00:23:59.680
<v Chris Garrison>certified experts at data interpretation,
and I think that um This really uh.

361
00:24:00.630 --> 00:24:05.439
<v Chris Garrison>Bridges that gap and allows you again to
to kind of bring the expert right into any

362
00:24:05.439 --> 00:24:10.869
<v Chris Garrison>size facility, whether it's, you know, a
small pumping station somewhere, um, you

363
00:24:10.869 --> 00:24:15.839
<v Chris Garrison>know, relatively small plant where you,
you wouldn't employ a vibration analysis or

364
00:24:15.839 --> 00:24:17.199
<v Chris Garrison>excuse me, a vibration analyst.

365
00:24:18.000 --> 00:24:21.020
<v Chris Garrison>Um, and maybe, you know, you wouldn't, um.

366
00:24:22.089 --> 00:24:28.130
<v Chris Garrison>You wouldn't uh pay the expenses to have
some someone come in remotely periodically.

367
00:24:28.329 --> 00:24:33.479
<v Chris Garrison>Um, you can now put in some, some
cost-effective equipment and some kind of, um,

368
00:24:33.489 --> 00:24:38.170
<v Chris Garrison>architecture to, to just bring data to the
cloud and monitor that from wherever you

369
00:24:38.170 --> 00:24:38.709
<v Chris Garrison>are in the world.

370
00:24:41.030 --> 00:24:44.819
<v Niall Sullivan>You mentioned that vibration analysis, so
that, you know, a person, you know, doing,

371
00:24:44.910 --> 00:24:46.099
<v Niall Sullivan>doing the analysis.

372
00:24:46.150 --> 00:24:51.060
<v Niall Sullivan>Is that usually an in, you know, an
in-house role or someone who's brought in sort

373
00:24:51.060 --> 00:24:53.349
<v Niall Sullivan>of externally, or can it sort of depends.

374
00:24:53.390 --> 00:24:54.709
<v Niall Sullivan>It could be either way.

375
00:24:55.000 --> 00:24:56.819
<v Chris Garrison>Yeah, I would say it greatly depends.

376
00:24:56.890 --> 00:25:02.869
<v Chris Garrison>Um, you know, 1520 years ago, if you went
to a very large plant that maybe had

377
00:25:02.869 --> 00:25:04.170
<v Chris Garrison>thousands of assets.

378
00:25:05.020 --> 00:25:11.079
<v Chris Garrison>Um You know, I think of things like oil
and gas, uh, Chevron Phillips, and the like.

379
00:25:12.089 --> 00:25:17.209
<v Chris Garrison>Uh, they might have 3 or 4 vibration
analysts on staff, people that they developed

380
00:25:17.209 --> 00:25:21.250
<v Chris Garrison>from engineering and for maintenance over
time, um, and send them off to get

381
00:25:21.250 --> 00:25:26.010
<v Chris Garrison>certifications and, and, uh, maybe they
would be in kind of an apprenticeship mode

382
00:25:26.010 --> 00:25:29.109
<v Chris Garrison>until they can move into a, to a senior
analyst role.

383
00:25:30.010 --> 00:25:36.130
<v Chris Garrison>But long story short, there, it takes
several years to develop an analyst, um, who

384
00:25:36.130 --> 00:25:42.270
<v Chris Garrison>can, you know, confidently look at
vibration data in its raw forms and um And

385
00:25:42.270 --> 00:25:44.109
<v Chris Garrison>accurately, you know, identify faults.

386
00:25:44.270 --> 00:25:49.510
<v Chris Garrison>And I think that's another area where, of
course, AI and ML are helping bridge the

387
00:25:49.510 --> 00:25:51.229
<v Chris Garrison>gap a bit, um.

388
00:25:53.050 --> 00:25:58.849
<v Chris Garrison>But you know, there is still some, some
human element to Data analysis and making

389
00:25:58.849 --> 00:26:01.270
<v Chris Garrison>some decisions as far as vibration goes.

390
00:26:01.969 --> 00:26:06.359
<v Chris Garrison>Some of it's still some, you know,
somewhat subjective, and it's a good idea to have

391
00:26:06.359 --> 00:26:09.130
<v Chris Garrison>somebody at least familiar, um,
interpreting.

392
00:26:11.140 --> 00:26:12.400
<v Chris Garrison>Results and recommendations.

393
00:26:13.439 --> 00:26:18.560
<v Niall Sullivan>Yeah, and of course, as we, you know, as
we know, Senite is very much a decision

394
00:26:18.560 --> 00:26:19.520
<v Niall Sullivan>support tool, right?

395
00:26:19.560 --> 00:26:24.040
<v Niall Sullivan>And any, any AI technology is there to be
supporting or to give you a different

396
00:26:24.040 --> 00:26:24.520
<v Niall Sullivan>viewpoint.

397
00:26:24.680 --> 00:26:27.849
<v Niall Sullivan>Like if you're talking to a colleague, you
could, you, you know, you could ask their

398
00:26:27.849 --> 00:26:32.780
<v Niall Sullivan>advice and their experience, but you're
asking AI for that advice instead with

399
00:26:32.780 --> 00:26:36.300
<v Niall Sullivan>obviously the difference that they've got
all the knowledge of it, you know, in

400
00:26:36.300 --> 00:26:37.900
<v Niall Sullivan>theory, all of the assets as well.

401
00:26:38.160 --> 00:26:40.420
<v Niall Sullivan>Um, so that's the way to position it,
right?

402
00:26:41.750 --> 00:26:46.130
<v Chris Garrison>Yeah, and, and I think there's so, so many
intriguing things ahead in that regard.

403
00:26:47.130 --> 00:26:51.520
<v Chris Garrison>Um, You know, different facilities have
different maintenance strategies, right,

404
00:26:51.650 --> 00:26:58.550
<v Chris Garrison>where one plant might simply dispose of a
motor and replace it outright.

405
00:26:58.930 --> 00:27:03.910
<v Chris Garrison>Another plant might might service that
motor, you know, and, and, and actually

406
00:27:04.560 --> 00:27:06.770
<v Chris Garrison>Replace bearings, for instance, um.

407
00:27:07.500 --> 00:27:13.859
<v Chris Garrison>Another might, uh, might be less, less
risk tolerant to a developing fault in the

408
00:27:13.859 --> 00:27:17.079
<v Chris Garrison>first sign of a problem, they might, you
know, change out that asset or do

409
00:27:17.079 --> 00:27:17.520
<v Chris Garrison>something.

410
00:27:18.170 --> 00:27:22.569
<v Chris Garrison>Um, rather substantial to to head off a
pending fault and others might.

411
00:27:23.930 --> 00:27:28.689
<v Chris Garrison>Be more accepting of risk and run things
closer to failure, you know, I think.

412
00:27:30.280 --> 00:27:34.099
<v Chris Garrison>It varies so greatly that it's hard to
have a a um.

413
00:27:34.900 --> 00:27:40.140
<v Chris Garrison>Just a canned AI engine that says this is
happening, do this.

414
00:27:40.939 --> 00:27:44.599
<v Chris Garrison>Um, but, you know, now with things like
um.

415
00:27:45.410 --> 00:27:52.010
<v Chris Garrison>Co-pilot and generative AI, I think we can
get a lot closer to, um, you know,

416
00:27:52.170 --> 00:27:58.530
<v Chris Garrison>AI understanding that um You know, based
on the work order history and all the

417
00:27:58.530 --> 00:28:04.109
<v Chris Garrison>things that this facility does, this is
the the relevant and relative action item.

418
00:28:05.609 --> 00:28:07.859
<v Chris Garrison>That that should be performed, if that
makes sense.

419
00:28:08.250 --> 00:28:09.410
<v Chris Garrison>So much more of a, you know.

420
00:28:10.390 --> 00:28:12.380
<v Chris Garrison>Uh, hands on, uh, maybe intimate.

421
00:28:13.040 --> 00:28:17.729
<v Chris Garrison>Um, Type of recommendation versus a a one
size fits all.

422
00:28:18.880 --> 00:28:23.859
<v Niall Sullivan>Exactly, not just generic advice, but
advice very much contextualized to your

423
00:28:23.859 --> 00:28:28.130
<v Niall Sullivan>assets, your organization, and the
knowledge of your maintenance teams as an

424
00:28:28.130 --> 00:28:28.579
<v Niall Sullivan>example.

425
00:28:29.310 --> 00:28:30.680
<v Chris Garrison>Yeah, I think that's a perfect way to put
it.

426
00:28:31.400 --> 00:28:31.900
<v Chris Garrison>Yeah.

427
00:28:32.430 --> 00:28:33.329
<v Niall Sullivan>No, fantastic.

428
00:28:33.949 --> 00:28:36.089
<v Niall Sullivan>So yeah, so it looks like we've come to
the end.

429
00:28:36.150 --> 00:28:39.510
<v Niall Sullivan>Um, it's been really great, um, to learn
about this subject, Chris.

430
00:28:39.630 --> 00:28:44.550
<v Niall Sullivan>Thank you so much for joining us, um, and
giving us the, the lowdown on, on

431
00:28:44.550 --> 00:28:46.930
<v Niall Sullivan>vibration analysis as well.

432
00:28:47.150 --> 00:28:51.489
<v Niall Sullivan>Um, but yeah, thank you for your time and
thank you everyone out there for listening

433
00:28:51.550 --> 00:28:52.969
<v Niall Sullivan>and we'll see you on the next episode.

434
00:28:53.589 --> 00:28:54.449
<v Niall Sullivan>Thank you very much.

435
00:28:55.150 --> 00:28:55.469
<v Chris Garrison>Thank you.

436
00:28:58.849 --> 00:29:03.810
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

437
00:29:03.810 --> 00:29:07.189
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.

438
00:32:18.170 --> 00:32:22.719
<v Chris Garrison>They might have 3 or 4 vibration analysts
on staff, people that they developed from,

439
00:32:22.800 --> 00:32:24.989
<v Chris Garrison>from engineering and for maintenance over
time.

440
00:32:25.130 --> 00:32:29.969
<v Chris Garrison>Um, and send them off to get
certifications and, and, uh, maybe they would be in

441
00:32:29.969 --> 00:32:34.390
<v Chris Garrison>kind of an apprenticeship mode until they
can move into a, to a senior analyst role.

442
00:32:35.290 --> 00:32:41.560
<v Chris Garrison>But long story short, there, it takes
several years to develop an analyst who can,

443
00:32:41.650 --> 00:32:48.189
<v Chris Garrison>you know, confidently look at vibration
data in its raw forms and um And accurately,

444
00:32:48.339 --> 00:32:49.469
<v Chris Garrison>you know, identify faults.
