WEBVTT
Language: en-US

1
00:00:02.029 --> 00:00:07.230
<v Speaker 1>Welcome to the trend detection podcast
powered by Siemens, and now your host, Nel

2
00:00:07.230 --> 00:00:07.789
<v Speaker 1>Sullivan.

3
00:00:11.340 --> 00:00:15.329
<v Liz McGinn>Hi everyone, um, I'm Liz McGinn and I'm
the host for our panel discussions today.

4
00:00:15.460 --> 00:00:19.780
<v Liz McGinn>So today we'll be talking about scaling
success, the cultural shift for predictive

5
00:00:19.780 --> 00:00:21.440
<v Liz McGinn>maintenance and digital transformation.

6
00:00:21.620 --> 00:00:26.420
<v Liz McGinn>I'm joined by three panelists today, Nick,
who you heard speak earlier, Natalie, who

7
00:00:26.420 --> 00:00:30.579
<v Liz McGinn>you heard mentioned during the BlueScope,
and then Todd, um, who's recently joined

8
00:00:30.579 --> 00:00:31.409
<v Liz McGinn>us at Sunsai.

9
00:00:31.459 --> 00:00:34.169
<v Liz McGinn>So, could you please introduce yourselves
before you get started?

10
00:00:34.259 --> 00:00:35.380
<v Liz McGinn>Nick, could you start, please?

11
00:00:38.799 --> 00:00:42.529
<v Speaker 3>Hi Liz, um, yeah, so, uh, I think
everybody heard the introduction earlier on

12
00:00:42.529 --> 00:00:47.479
<v Speaker 3>actually, so, uh, for those who missed it,
um, I've spent 30 years at the

13
00:00:47.479 --> 00:00:53.159
<v Speaker 3>intersection, uh, of transbusiness and
technology, helping companies, uh, improve

14
00:00:53.159 --> 00:00:56.099
<v Speaker 3>their operating performance through those,
those tools.

15
00:00:58.069 --> 00:01:00.080
<v Liz McGinn>Awesome, thank you, Natalie.

16
00:01:01.009 --> 00:01:01.650
<v Natalie>Hi, everyone.

17
00:01:01.810 --> 00:01:06.830
<v Natalie>Um, I've been working with Sensai for the
last, I think, 4.5 years now, uh, and the

18
00:01:06.830 --> 00:01:08.089
<v Natalie>delivery of the tools.

19
00:01:08.169 --> 00:01:11.769
<v Natalie>So I worked with BlueScope and other
customers to get them on boarded and trained up

20
00:01:11.769 --> 00:01:14.309
<v Natalie>and make sure that Sensai is doing what
they want to do.

21
00:01:15.930 --> 00:01:17.040
<v Liz McGinn>Awesome, and Todd.

22
00:01:17.959 --> 00:01:18.879
<v Todd Martin>Uh, thanks Liz.

23
00:01:19.110 --> 00:01:25.440
<v Todd Martin>Uh, listen, I'm Todd Martin and I am the
Siemens Sensi managed Services lead and I

24
00:01:25.440 --> 00:01:32.260
<v Todd Martin>recently joined the Siemens team after
retiring from, uh, Nissan, um, where

25
00:01:32.400 --> 00:01:39.239
<v Todd Martin>I used, uh, Sensai for 7 years, um, was
involved in

26
00:01:39.239 --> 00:01:39.580
<v Todd Martin>the.

27
00:01:40.360 --> 00:01:46.199
<v Todd Martin>Um, the proof of concept that brought the
um system on board there and, you know,

28
00:01:46.370 --> 00:01:50.830
<v Todd Martin>implemented, designed many of the data
collection systems to provide the data to the

29
00:01:50.830 --> 00:01:51.690
<v Todd Martin>Sensi system.

30
00:01:53.040 --> 00:01:53.480
<v Liz McGinn>Awesome.

31
00:01:53.599 --> 00:01:54.319
<v Liz McGinn>Thank you.

32
00:01:54.680 --> 00:01:55.519
<v Liz McGinn>So, let's jump in.

33
00:01:55.629 --> 00:01:59.959
<v Liz McGinn>Um, before we can talk about what needs to
shift in a maintenance team or a

34
00:01:59.959 --> 00:02:03.989
<v Liz McGinn>company's culture to implement predictive
maintenance or any new technology, we

35
00:02:03.989 --> 00:02:07.239
<v Liz McGinn>should first kind of figure out what's
currently happening within the maintenance

36
00:02:07.239 --> 00:02:07.400
<v Liz McGinn>team.

37
00:02:07.519 --> 00:02:11.399
<v Liz McGinn>So, Todd, as you've worked, uh, you know,
in maintenance before, what's currently

38
00:02:11.399 --> 00:02:14.259
<v Liz McGinn>happening that you're, you saw during your
experience?

39
00:02:15.669 --> 00:02:19.919
<v Todd Martin>So especially in a large facility, you
know, your maintenance teams are broken up

40
00:02:19.919 --> 00:02:24.119
<v Todd Martin>into a lot of different departments or
groups that, you know, focus on certain areas

41
00:02:24.119 --> 00:02:29.500
<v Todd Martin>on there so a lot of times they may have
their own individual ways of doing things,

42
00:02:29.520 --> 00:02:35.960
<v Todd Martin>um, so that's something that you have to
consider, um, each of those groups probably

43
00:02:35.960 --> 00:02:42.860
<v Todd Martin>have different KPIs based on the processes
that are going on in those areas, um,

44
00:02:43.479 --> 00:02:44.039
<v Todd Martin>so.

45
00:02:45.119 --> 00:02:51.000
<v Todd Martin>You know, also their training may be
different, um, just because it's different

46
00:02:51.000 --> 00:02:51.839
<v Todd Martin>equipment.

47
00:02:52.570 --> 00:02:59.410
<v Todd Martin>Um, So there's a lot of different
experience, backgrounds and skill

48
00:02:59.410 --> 00:03:03.130
<v Todd Martin>sets that are um going on in those um
different groups.

49
00:03:04.720 --> 00:03:06.330
<v Liz McGinn>Yeah, the training is uh interesting.

50
00:03:06.410 --> 00:03:09.289
<v Liz McGinn>It's kind of callback to BlueScope talking
about their training.

51
00:03:09.610 --> 00:03:11.610
<v Liz McGinn>Natalie, do you, um, want to kind of speak
to that?

52
00:03:11.690 --> 00:03:14.110
<v Liz McGinn>Were you involved in their training aspect
of it?

53
00:03:15.639 --> 00:03:21.699
<v Natalie>Yeah, Bluescope was a really interesting
one, So for, for training them, I worked

54
00:03:21.699 --> 00:03:25.300
<v Natalie>hands on with them and just getting them
in using the app and figuring out how to

55
00:03:25.300 --> 00:03:26.309
<v Natalie>monitor their equipment.

56
00:03:26.419 --> 00:03:31.139
<v Natalie>So we had lots of one on one sessions with
myself and Chris Watson to figure out how

57
00:03:31.139 --> 00:03:31.899
<v Natalie>these machines work.

58
00:03:31.979 --> 00:03:34.339
<v Natalie>They did not have traditional condition
indicators.

59
00:03:34.419 --> 00:03:37.899
<v Natalie>They did not have vibration monitoring on
the rotating equipment for the most part.

60
00:03:38.020 --> 00:03:39.559
<v Natalie>So we had to get really creative.

61
00:03:39.940 --> 00:03:45.699
<v Natalie>And throughout that process of figuring
out what to bring into Sensei and how to

62
00:03:45.699 --> 00:03:48.759
<v Natalie>configure it, they really learned a lot
about how the app works.

63
00:03:50.720 --> 00:03:51.750
<v Liz McGinn>Nice, awesome.

64
00:03:52.250 --> 00:03:56.380
<v Liz McGinn>And they mentioned also during that time
that they talked about this role of like

65
00:03:56.380 --> 00:03:59.990
<v Liz McGinn>figuring out who can be champions and the
importance of having that.

66
00:04:01.350 --> 00:04:06.429
<v Natalie>Yeah, so BlueScope, they, they really did
a lot of things right, and I think one of

67
00:04:06.429 --> 00:04:10.630
<v Natalie>the biggest things that they did that led
to their success is that they had drive

68
00:04:10.630 --> 00:04:14.779
<v Natalie>from the bottom up, the end users in all
the different areas, their site, their

69
00:04:14.779 --> 00:04:17.630
<v Natalie>sites are massive, and they wanted to use
it.

70
00:04:18.519 --> 00:04:23.089
<v Natalie>But they also had support from the top
bottom to, uh, incentivize and engage their

71
00:04:23.089 --> 00:04:28.290
<v Natalie>end users, uh, into using Sensei and to
really integrate it into their, their

72
00:04:28.290 --> 00:04:28.769
<v Natalie>system.

73
00:04:28.869 --> 00:04:33.109
<v Natalie>So, I think that was their, a really key
part of why they were successful.

74
00:04:33.200 --> 00:04:37.929
<v Natalie>And actually when I went on site to do
some introductions and to do some training,

75
00:04:38.010 --> 00:04:42.250
<v Natalie>we had one session planned in which people
from the site could come in and sit in

76
00:04:42.250 --> 00:04:44.970
<v Natalie>and learn about Senseii and figure out how
they can get started.

77
00:04:45.399 --> 00:04:49.929
<v Natalie>And there were so many people that showed
up that we needed to make a 2nd 1, so that

78
00:04:50.279 --> 00:04:50.920
<v Natalie>everybody could join.

79
00:04:51.079 --> 00:04:56.600
<v Natalie>So I think, I think the key in finding the
right champion is whoever is sponsoring

80
00:04:56.600 --> 00:05:01.640
<v Natalie>the project needs to sell Sensai
internally so that people can see the benefits of

81
00:05:01.640 --> 00:05:01.760
<v Natalie>it.

82
00:05:01.839 --> 00:05:05.720
<v Natalie>People should want this because it will
make them more efficient in the long run.

83
00:05:07.869 --> 00:05:11.440
<v Liz McGinn>Yeah, Nick, you mentioned something
similar during your presentation is kind of what

84
00:05:11.440 --> 00:05:15.140
<v Liz McGinn>does this mean to me versus just what does
it mean to the company?

85
00:05:16.390 --> 00:05:21.640
<v Speaker 3>Absolutely, and, and, as Natalie was
saying a second ago, those champions, I

86
00:05:21.640 --> 00:05:25.369
<v Speaker 3>sometimes I describe them to to companies
I work with as Yodas.

87
00:05:25.880 --> 00:05:30.200
<v Speaker 3>Yeah, it's, who are the Yodas in, in, in
the production facility that these are

88
00:05:30.200 --> 00:05:34.720
<v Speaker 3>typically the people that have been there
for 30 years that when something goes

89
00:05:34.720 --> 00:05:36.589
<v Speaker 3>wrong, they know how to fix it.

90
00:05:36.720 --> 00:05:39.799
<v Speaker 3>It's not necessarily written down
somewhere, they're just the wise people.

91
00:05:40.239 --> 00:05:42.380
<v Speaker 3>If you can win those people over.

92
00:05:43.089 --> 00:05:48.500
<v Speaker 3>That's so infectious in terms of getting
everybody on, on board.

93
00:05:49.109 --> 00:05:54.320
<v Speaker 3>Uh, and I think the, the other thing that
I think is linked to the training is, I,

94
00:05:54.399 --> 00:05:59.359
<v Speaker 3>I've seen a lot pilots and projects get
deliver the training to the end user.

95
00:06:00.010 --> 00:06:03.970
<v Speaker 3>And that that's great, but if they don't
keep using the tool.

96
00:06:05.100 --> 00:06:09.260
<v Speaker 3>They forget how to use it, they forget
about the benefits, and it becomes another

97
00:06:09.260 --> 00:06:12.440
<v Speaker 3>one of those um implementations that's
gathering dust on the shelf.

98
00:06:12.940 --> 00:06:18.970
<v Speaker 3>So it, I, I think in addition to just
that, that training motion, it's keep that

99
00:06:18.970 --> 00:06:20.380
<v Speaker 3>continuous engagement.

100
00:06:20.739 --> 00:06:25.290
<v Speaker 3>You know, I talked about some of that
feedback loops, yeah, what's working, equally,

101
00:06:25.299 --> 00:06:29.420
<v Speaker 3>what's important, what's not working, and
keep that improvement, making things

102
00:06:29.420 --> 00:06:30.200
<v Speaker 3>better all the time.

103
00:06:32.510 --> 00:06:33.309
<v Liz McGinn>That's awesome.

104
00:06:33.429 --> 00:06:37.709
<v Liz McGinn>I mean, you mentioned, I guess, this
whole, um, feedback in the training loops and

105
00:06:37.709 --> 00:06:41.660
<v Liz McGinn>the training, sorry, training and also
this champion.

106
00:06:41.739 --> 00:06:46.410
<v Liz McGinn>I know Todd has some experience kind of,
you know, pushing the sense I kind of

107
00:06:46.540 --> 00:06:48.609
<v Liz McGinn>predictive maintenance digitalization
journey forward.

108
00:06:48.670 --> 00:06:50.929
<v Liz McGinn>Do you want to speak to a little bit um on
that?

109
00:06:51.429 --> 00:06:52.029
<v Todd Martin>Yeah, sure.

110
00:06:52.640 --> 00:06:55.239
<v Todd Martin>So yeah, definitely you've gotta have
champions.

111
00:06:55.489 --> 00:06:59.109
<v Todd Martin>One of the key things you, you, you want
your champions, you wanna pick them from a

112
00:06:59.109 --> 00:07:04.890
<v Todd Martin>pool of people that are excited about the
technology or technology in general, um,

113
00:07:05.279 --> 00:07:09.679
<v Todd Martin>you know, you're gonna have different, um,
age groups within the maintenance

114
00:07:09.679 --> 00:07:13.269
<v Todd Martin>departments you're gonna have your, your
newer techs, then you're gonna have your

115
00:07:13.269 --> 00:07:16.959
<v Todd Martin>older techs, you know, you'll get your
most resistance from the older techs because

116
00:07:16.959 --> 00:07:17.859
<v Todd Martin>they're old school.

117
00:07:18.739 --> 00:07:23.100
<v Todd Martin>So a lot of times it helps you grab those
younger guys who have grown up with the

118
00:07:23.100 --> 00:07:28.489
<v Todd Martin>technology um and that's really where
they're focused at on this new cool, you know,

119
00:07:28.859 --> 00:07:34.399
<v Todd Martin>software application um and are hungry to
make a name for themselves.

120
00:07:35.670 --> 00:07:39.910
<v Todd Martin>You know, in their group, you know, to
stand out, so it's kind of important that

121
00:07:40.149 --> 00:07:44.750
<v Todd Martin>those are really good resource, you know,
ones to have as a champion, um.

122
00:07:45.700 --> 00:07:52.399
<v Todd Martin>Um, So And and the other thing is too is
not to have too many of

123
00:07:52.399 --> 00:07:52.769
<v Todd Martin>them.

124
00:07:53.760 --> 00:08:00.500
<v Todd Martin>Um, you, you really, you really wanna have
potentially one oversight on here to

125
00:08:00.500 --> 00:08:03.619
<v Todd Martin>make sure that it's being utilized, you
know, properly.

126
00:08:04.399 --> 00:08:10.269
<v Todd Martin>As we, as I saw in the past, you know,
some areas are gonna have more benefit from,

127
00:08:10.279 --> 00:08:14.279
<v Todd Martin>um, from Sensei than other ones, it's just
the nature of the type of pieces of

128
00:08:14.279 --> 00:08:14.679
<v Todd Martin>equipment.

129
00:08:14.859 --> 00:08:17.959
<v Todd Martin>Some wear out slower than others and have
problems.

130
00:08:18.119 --> 00:08:21.260
<v Todd Martin>Some are faster, the faster ones you see
more benefit from.

131
00:08:22.359 --> 00:08:26.059
<v Todd Martin>And you know, so it's, it's keeping them
engaged and.

132
00:08:27.040 --> 00:08:28.109
<v Todd Martin>Across the board

133
00:08:29.779 --> 00:08:33.659
<v Speaker 3>I think Todd, just to build off a little
bit what Todd was saying as well though.

134
00:08:34.669 --> 00:08:36.460
<v Speaker 3>I think it's really important to think
about.

135
00:08:37.369 --> 00:08:42.659
<v Speaker 3>These tools like Sensai and predictive
maintenance, they're not just the tools for

136
00:08:42.659 --> 00:08:47.340
<v Speaker 3>the maintenance teams, you know, I, I
talked about creating more visibility and

137
00:08:47.340 --> 00:08:49.809
<v Speaker 3>curiosity around this.

138
00:08:50.140 --> 00:08:55.140
<v Speaker 3>So if you start showing the machine health
to the operators, not the maintenance

139
00:08:55.140 --> 00:08:58.500
<v Speaker 3>teams as well, that becomes part of their
daily routine.

140
00:08:58.570 --> 00:09:03.260
<v Speaker 3>It, it becomes something that they care
about, not just the production run.

141
00:09:03.619 --> 00:09:08.659
<v Speaker 3>So it's about elevating that same
information and making it more broadly accessible

142
00:09:08.659 --> 00:09:12.299
<v Speaker 3>and visible also helps that journey
significantly.

143
00:09:16.200 --> 00:09:19.570
<v Liz McGinn>Yeah, you mentioned a really nice phrase
there that it's a tool to help this

144
00:09:19.570 --> 00:09:20.760
<v Liz McGinn>predictive maintenance journey.

145
00:09:20.809 --> 00:09:23.070
<v Liz McGinn>I know, uh Natalie loves to use that
phrase.

146
00:09:24.059 --> 00:09:25.940
<v Natalie>Yeah, I feel very strongly about that.

147
00:09:26.059 --> 00:09:30.409
<v Natalie>I think there's some common misconceptions
that Sensai itself is predictive

148
00:09:30.409 --> 00:09:32.130
<v Natalie>maintenance, but it's not.

149
00:09:32.219 --> 00:09:35.119
<v Natalie>Predictive maintenance is a whole process
and a whole strategy.

150
00:09:35.700 --> 00:09:39.979
<v Natalie>Senseii is a tool to help you achieve
that, but you have to use it, and you probably

151
00:09:39.979 --> 00:09:43.059
<v Natalie>have to change some other practices as
well in order to actually achieve predictive

152
00:09:43.059 --> 00:09:43.419
<v Natalie>maintenance.

153
00:09:43.530 --> 00:09:47.659
<v Natalie>So let's say Sensai tells you about
something, let's say you have potentially 4

154
00:09:47.659 --> 00:09:49.619
<v Natalie>months before you need to maintain a piece
of equipment.

155
00:09:49.700 --> 00:09:51.440
<v Natalie>What are you going to do with that
information?

156
00:09:51.900 --> 00:09:56.299
<v Natalie>So, That's something that we, we often
help our customers with is like, OK, you got

157
00:09:56.299 --> 00:09:58.909
<v Natalie>all your data in, but that's just one
small part of the puzzle.

158
00:09:58.989 --> 00:09:59.909
<v Natalie>What are you going to do with it?

159
00:10:02.440 --> 00:10:03.390
<v Todd Martin>Yes, definitely.

160
00:10:05.190 --> 00:10:05.690
<v Liz McGinn>Oh, go ahead.

161
00:10:06.450 --> 00:10:08.909
<v Todd Martin>No, I, I wanna say I agree 100%.

162
00:10:08.950 --> 00:10:13.260
<v Todd Martin>It's just like, um, you've got to take
that information and you might have to change

163
00:10:13.260 --> 00:10:17.229
<v Todd Martin>your um maintenance practices to, um, to
handle that.

164
00:10:17.669 --> 00:10:21.950
<v Todd Martin>You're gonna learn probably way sooner
that something's going on with your equipment

165
00:10:21.950 --> 00:10:25.349
<v Todd Martin>than what you can justify actually doing
the work on it yet.

166
00:10:26.150 --> 00:10:29.760
<v Natalie>Or you might like Mixer, you, you might
work with operations to change how you're

167
00:10:29.760 --> 00:10:33.520
<v Natalie>using the equipment to make it last a
little bit longer to, to baby it a little bit

168
00:10:33.520 --> 00:10:36.000
<v Natalie>so it makes it to the next shutdown,
things like that.

169
00:10:39.239 --> 00:10:43.840
<v Liz McGinn>How is that affecting um kind of the KPIs
that people are looking at when they're,

170
00:10:44.000 --> 00:10:46.219
<v Liz McGinn>you know, investing in this kind of thing.

171
00:10:46.760 --> 00:10:50.479
<v Natalie>So the KPIs can be really difficult to
calculate, especially when there's, there's

172
00:10:50.479 --> 00:10:51.280
<v Natalie>so many unknowns.

173
00:10:51.330 --> 00:10:55.080
<v Natalie>If you're doing predictive maintenance,
the thing hasn't failed, so.

174
00:10:56.059 --> 00:11:00.219
<v Natalie>It's hard to anticipate and like in every
case, what might have happened if you

175
00:11:00.219 --> 00:11:04.140
<v Natalie>hadn't done it, um, but it is something we
do work, it's hard, but we work closely

176
00:11:04.140 --> 00:11:07.200
<v Natalie>with our customers to try and put hard
numbers to these things.

177
00:11:07.820 --> 00:11:12.940
<v Natalie>Uh, a lot of times people come up with
kind of generic KPIs and so we, we try to

178
00:11:12.940 --> 00:11:14.039
<v Natalie>make them quantifiable.

179
00:11:17.780 --> 00:11:21.940
<v Speaker 3>We, we na, I mean, we talked earlier on
about the disconnect between operational

180
00:11:21.940 --> 00:11:26.559
<v Speaker 3>KPIs and the financial metrics that the
business runs, run against, and I think.

181
00:11:27.460 --> 00:11:31.260
<v Speaker 3>For most businesses I work with, that that
that that connection has to be

182
00:11:31.260 --> 00:11:37.969
<v Speaker 3>strengthened over time, because an OEE, a
20% OEE improvement in OEE or a 20%, uh,

183
00:11:38.020 --> 00:11:44.659
<v Speaker 3>15% reduction in unplanned downtime, what
does that really mean and who really cares

184
00:11:44.659 --> 00:11:45.140
<v Speaker 3>about it?

185
00:11:46.239 --> 00:11:53.200
<v Speaker 3>But also, I, I think we should also think
about KPIs in terms of making

186
00:11:53.200 --> 00:11:59.559
<v Speaker 3>them not just financial, but relevant to
the people that need to make decisions.

187
00:11:59.929 --> 00:12:03.229
<v Speaker 3>And that doesn't necessarily mean
managers.

188
00:12:03.609 --> 00:12:06.150
<v Speaker 3>That could be the maintenance teams, that
could be the operator.

189
00:12:06.450 --> 00:12:10.960
<v Speaker 3>It could just be a health statement or a
health score of my machine, and we wanna

190
00:12:10.960 --> 00:12:11.950
<v Speaker 3>keep it green.

191
00:12:12.289 --> 00:12:15.349
<v Speaker 3>And we wanna keep it green 90% of the
time.

192
00:12:15.919 --> 00:12:20.799
<v Speaker 3>So you don't, you know, it, they, they all
roll up, but it's actually, you know, I

193
00:12:20.799 --> 00:12:21.909
<v Speaker 3>talk about buzzwords, yeah?

194
00:12:22.280 --> 00:12:24.320
<v Speaker 3>It's, it's making things simple.

195
00:12:24.400 --> 00:12:30.619
<v Speaker 3>How many, how many Big Macs did we not, we
saved this week, yeah, or this month?

196
00:12:31.080 --> 00:12:36.080
<v Speaker 3>It sounds stupid, it may be slightly, it
might be slightly, but it kind of makes it

197
00:12:36.080 --> 00:12:36.750
<v Speaker 3>relevant.

198
00:12:37.039 --> 00:12:40.599
<v Speaker 3>And I think that's the key for KPIs rather
than just pure financial statements.

199
00:12:43.700 --> 00:12:48.340
<v Liz McGinn>Yeah, it makes sense to have this kind of
tangible um thing cause, you know, people

200
00:12:48.340 --> 00:12:51.460
<v Liz McGinn>can't really imagine how much is actually
being saved, but if you put it in a

201
00:12:51.460 --> 00:12:53.880
<v Liz McGinn>tangible, it makes a lot of sense.

202
00:12:54.700 --> 00:12:57.169
<v Speaker 3>You could, you could bonus on, you could
bonus on big backs, yeah.

203
00:13:00.070 --> 00:13:00.080
<v Speaker 3>Exactly.

204
00:13:02.520 --> 00:13:06.400
<v Liz McGinn>And I guess the other thing that we uh
kind of spoke about is kind of the time,

205
00:13:06.719 --> 00:13:11.520
<v Liz McGinn>another tangible KPI that is the time that
you'd spend fixing things because you can

206
00:13:11.520 --> 00:13:14.900
<v Liz McGinn>kind of quantify how long it is fixing
these things.

207
00:13:16.559 --> 00:13:17.130
<v Todd Martin>Mhm.

208
00:13:18.400 --> 00:13:20.799
<v Todd Martin>You fix it, you can fix it during a
breakdown.

209
00:13:21.940 --> 00:13:27.869
<v Todd Martin>Or um you can fix it, do, you know,
scheduled downtime, avoiding overtime.

210
00:13:31.200 --> 00:13:31.710
<v Todd Martin>Yeah.

211
00:13:32.460 --> 00:13:36.419
<v Speaker 3>But, but I, I, I think Todd, you were
using a French phrase earlier on called wrench

212
00:13:36.419 --> 00:13:36.580
<v Speaker 3>time.

213
00:13:36.659 --> 00:13:38.719
<v Speaker 3>How much wrench time is a maintenance
person?

214
00:13:39.440 --> 00:13:44.919
<v Speaker 3>Actually got fixing things rather than
analyzing data, and I think there's a

215
00:13:44.919 --> 00:13:50.489
<v Speaker 3>combination of what I just mentioned and
making SIT KPIs really simple, so it gives

216
00:13:50.489 --> 00:13:55.710
<v Speaker 3>direction to the people to do something,
and then then they're not, not, not

217
00:13:55.710 --> 00:13:59.500
<v Speaker 3>spending time analyzing why they should be
doing it, they know what they need to do,

218
00:13:59.690 --> 00:14:03.750
<v Speaker 3>and they go off and have the maximum
wrench time poss possible.

219
00:14:04.369 --> 00:14:04.650
<v Todd Martin>Yep.

220
00:14:05.409 --> 00:14:08.830
<v Todd Martin>You know, wrench time repairing or um
doing preventative maintenance.

221
00:14:13.450 --> 00:14:13.900
<v Todd Martin>Nice.

222
00:14:14.500 --> 00:14:18.859
<v Liz McGinn>It's a really great point and I guess um I
want to circle back to kind of this point

223
00:14:18.859 --> 00:14:21.659
<v Liz McGinn>of our whole event here is the scaling.

224
00:14:21.820 --> 00:14:24.520
<v Liz McGinn>Can you guys speak a little bit to the
importance of scaling?

225
00:14:26.460 --> 00:14:26.469
<v Liz McGinn>Uh,

226
00:14:27.419 --> 00:14:28.400
<v Natalie>I can get started.

227
00:14:29.900 --> 00:14:30.700
<v Natalie>Sorry, Todd.

228
00:14:31.289 --> 00:14:32.000
<v Liz McGinn>I'll go for it.

229
00:14:32.739 --> 00:14:37.270
<v Natalie>Uh, so Sensii really shines at scale, and
I think one of the beautiful things about

230
00:14:37.270 --> 00:14:43.530
<v Natalie>Sensai is if I have, say 10 motors that
are roughly the same, same data coming in,

231
00:14:43.619 --> 00:14:46.419
<v Natalie>or if I have 100 or even 1000 motors
coming in.

232
00:14:47.059 --> 00:14:52.299
<v Natalie>It's pretty much the same amount of effort
to configure 10 as it is to configure

233
00:14:52.299 --> 00:14:54.119
<v Natalie>100, the way the app is set up.

234
00:14:54.739 --> 00:15:00.450
<v Natalie>So why not get 100 or 1000 in and give
yourself more chance to to catch something,

235
00:15:00.929 --> 00:15:04.140
<v Natalie>um, if it's all the same to, to you, to
get the data in there.

236
00:15:04.809 --> 00:15:09.250
<v Natalie>Um, and then another part of Sensai that
that is often overlooked if you're not on

237
00:15:09.250 --> 00:15:13.969
<v Natalie>boarding many assets at the same time, is
the capacity to view your assets in a

238
00:15:13.969 --> 00:15:14.440
<v Natalie>fleet.

239
00:15:14.619 --> 00:15:18.099
<v Natalie>So if you have a whole line of assets and
they're performing roughly the same thing

240
00:15:18.099 --> 00:15:23.179
<v Natalie>in the same way, you can look at their
data together and see outliers that they may

241
00:15:23.179 --> 00:15:26.780
<v Natalie>have been on board in a stable state, but
they may be sitting, you know, if

242
00:15:26.780 --> 00:15:30.260
<v Natalie>everybody else is sitting here, one might
be sitting up here, might be stable, but

243
00:15:30.260 --> 00:15:32.219
<v Natalie>very different, and you might want to know
about that.

244
00:15:32.799 --> 00:15:38.929
<v Natalie>Um, so some things like that, I know
BlueScope use that view a lot in the app, and

245
00:15:38.929 --> 00:15:42.210
<v Natalie>if you don't scale and you don't have that
duplication of asset types, then you

246
00:15:42.210 --> 00:15:43.250
<v Natalie>don't really get to see it.

247
00:15:47.440 --> 00:15:53.419
<v Todd Martin>Yeah, definitely, um, you know, scaling,
you know what helps is is that you're gonna

248
00:15:53.419 --> 00:15:57.260
<v Todd Martin>go into this predictive maintenance
journey on here, you know.

249
00:15:59.609 --> 00:16:03.030
<v Todd Martin>One of the easiest thing to do is, OK,
we're gonna pick these few assets and we're

250
00:16:03.030 --> 00:16:05.950
<v Todd Martin>gonna, we're gonna start monitoring them
all that, but.

251
00:16:07.119 --> 00:16:11.119
<v Todd Martin>Of course it's gonna be successful, but
how do you make it successful on everything

252
00:16:11.119 --> 00:16:18.000
<v Todd Martin>else and as easy as possible, so going
into the journey, thinking very

253
00:16:18.000 --> 00:16:21.440
<v Todd Martin>high level outside of the box, um,
determining.

254
00:16:22.450 --> 00:16:24.429
<v Todd Martin>How do I set this up so that.

255
00:16:25.099 --> 00:16:30.380
<v Todd Martin>I can easily bring more and different
types of assets on there, you know, do you

256
00:16:30.380 --> 00:16:36.380
<v Todd Martin>have existing um condition based
monitoring systems that you're gonna use, you know,

257
00:16:36.580 --> 00:16:40.570
<v Todd Martin>so how do we access those and make it as
easy as possible on there or if I'm gonna

258
00:16:40.570 --> 00:16:45.179
<v Todd Martin>bring in new one, new condition based
monitoring systems, let's do it in such a way

259
00:16:45.179 --> 00:16:49.820
<v Todd Martin>that I can just, you know, use all these
pieces, the same pieces over and over

260
00:16:49.820 --> 00:16:52.520
<v Todd Martin>again, maybe you do use them in a very
creative way.

261
00:16:52.919 --> 00:16:57.809
<v Todd Martin>To get that information and it just it's
easier and faster to implement the system.

262
00:17:01.020 --> 00:17:04.000
<v Speaker 3>Yeah, I think definitely when you look at
that, Todd, as you mentioned, that

263
00:17:04.000 --> 00:17:04.869
<v Speaker 3>repeatability.

264
00:17:05.630 --> 00:17:09.869
<v Speaker 3>That's one of the true paths, but that,
that almost, as I mentioned earlier on, had

265
00:17:09.869 --> 00:17:13.229
<v Speaker 3>to, you have to start before you're in the
implementation.

266
00:17:13.550 --> 00:17:17.969
<v Speaker 3>You need to do a bit of work understanding
how many of those assets are similar,

267
00:17:18.510 --> 00:17:22.829
<v Speaker 3>how, what are the things I wanna measure,
are they consistently measured in the same

268
00:17:22.829 --> 00:17:23.219
<v Speaker 3>way?

269
00:17:23.589 --> 00:17:27.589
<v Speaker 3>Don't get caught out with different time
stamps between different facilities in

270
00:17:27.589 --> 00:17:29.469
<v Speaker 3>different locations, stupid things like
that.

271
00:17:29.670 --> 00:17:31.810
<v Speaker 3>I've seen get catch companies out of time.

272
00:17:32.250 --> 00:17:34.630
<v Speaker 3>And time again, so they lose the relevance
of it.

273
00:17:35.170 --> 00:17:39.689
<v Speaker 3>Um, I was really interested in what
Natalie was saying as well about the, being able

274
00:17:39.689 --> 00:17:42.949
<v Speaker 3>to classify or group assets together.

275
00:17:43.369 --> 00:17:47.599
<v Speaker 3>Um, you know, one of the things I talk
about a lot is about the true potential of,

276
00:17:47.689 --> 00:17:48.810
<v Speaker 3>of, of manufacturing.

277
00:17:49.170 --> 00:17:53.359
<v Speaker 3>So it's not about how, where you're
performing, it's actually the difference between

278
00:17:53.359 --> 00:17:56.770
<v Speaker 3>your average performance and your lowest
uh worst performer.

279
00:17:57.400 --> 00:18:00.719
<v Speaker 3>And understanding that difference and why
that might be, and if you can bring that

280
00:18:00.719 --> 00:18:03.680
<v Speaker 3>up, and the whole, your whole system
improves.

281
00:18:03.949 --> 00:18:07.719
<v Speaker 3>So that true potential view, that that's a
really interesting way and a nice

282
00:18:07.719 --> 00:18:12.739
<v Speaker 3>actually KPI you can then look at and look
at the actual knock-on effect in terms of

283
00:18:13.000 --> 00:18:14.050
<v Speaker 3>financial performance then.

284
00:18:14.989 --> 00:18:19.430
<v Natalie>And I think when, when you go through and
you look at KPIs and you figure out what

285
00:18:19.430 --> 00:18:23.390
<v Natalie>you want to monitor and and what you want
to track, it will lead you to the

286
00:18:23.390 --> 00:18:25.569
<v Natalie>conclusion that it's best to scale.

287
00:18:26.270 --> 00:18:29.670
<v Natalie>Sometimes folks just want to come in and
put their most critical, most problematic

288
00:18:29.670 --> 00:18:32.949
<v Natalie>assets into Sensai, but really what are
you going to get out of that?

289
00:18:33.489 --> 00:18:36.670
<v Natalie>Um, may, it may give you something you
didn't already know, but you're probably

290
00:18:36.670 --> 00:18:38.829
<v Natalie>already over monitoring that asset.

291
00:18:39.489 --> 00:18:43.829
<v Natalie>Why don't you get in full lines of asset
and reduce your planned maintenance and,

292
00:18:43.890 --> 00:18:46.430
<v Natalie>you know, track things that maybe you
haven't tracked before.

293
00:18:47.979 --> 00:18:50.280
<v Natalie>There's a lot of possibilities when you're
on board at scale.

294
00:18:54.119 --> 00:18:54.569
<v Liz McGinn>Awesome.

295
00:18:54.689 --> 00:18:58.770
<v Liz McGinn>So we're about 20 minutes in, so we've got
about 10 minutes left and I'd like to um

296
00:18:58.770 --> 00:19:00.170
<v Liz McGinn>kind of jump into some questions.

297
00:19:00.250 --> 00:19:04.089
<v Liz McGinn>So please, if anyone has any questions for
our experts here, um, throw it into the

298
00:19:04.089 --> 00:19:04.689
<v Liz McGinn>chat.

299
00:19:04.959 --> 00:19:11.390
<v Liz McGinn>Um, so for first question, curious, uh,
Here's customers want to start a

300
00:19:11.390 --> 00:19:16.630
<v Liz McGinn>PDM project with a POC, but from my point
of view, since that PDM projects don't

301
00:19:16.630 --> 00:19:18.589
<v Liz McGinn>include a POC phase in the process models.

302
00:19:18.670 --> 00:19:19.489
<v Liz McGinn>Is this right?

303
00:19:19.910 --> 00:19:25.349
<v Liz McGinn>How should I encounter um the customers in
this matter?

304
00:19:26.329 --> 00:19:31.650
<v Natalie>So, one thing that we are trying to do is
kind of change the language a little bit,

305
00:19:31.969 --> 00:19:36.310
<v Natalie>cause you're right, we, we don't do it
necessarily proof of concept all the time,

306
00:19:36.410 --> 00:19:40.310
<v Natalie>um, because Well, it works, it's going to
work, right?

307
00:19:40.430 --> 00:19:42.770
<v Natalie>Um, I don't know, I can say that.

308
00:19:44.069 --> 00:19:47.099
<v Natalie>Um, what, what we're calling it instead is
an initial deployment.

309
00:19:47.310 --> 00:19:52.430
<v Natalie>So maybe you do an initial deployment of
50 assets, narrow it down to just a handful

310
00:19:52.430 --> 00:19:53.500
<v Natalie>of asset types.

311
00:19:53.709 --> 00:19:59.349
<v Natalie>So 50 assets, maybe 3 different types,
motors, fans, pumps, something like that.

312
00:19:59.709 --> 00:20:03.869
<v Natalie>And that will still help you see value
because you have repeatability in there, um,

313
00:20:04.099 --> 00:20:07.270
<v Natalie>and just try to, you know, make sure
you're selecting assets that actually have a

314
00:20:07.270 --> 00:20:12.109
<v Natalie>chance of giving value in the timeline
that you're looking at.

315
00:20:14.760 --> 00:20:15.979
<v Natalie>Hopefully, that answers that question.

316
00:20:19.719 --> 00:20:20.339
<v Liz McGinn>Awesome.

317
00:20:20.839 --> 00:20:24.959
<v Speaker 3>I, I, I think, I think we also just need
to recognize that as a manufacturer, and I,

318
00:20:25.040 --> 00:20:27.579
<v Speaker 3>I, I, I, I have to say neutral in this,
yeah.

319
00:20:28.300 --> 00:20:30.979
<v Speaker 3>There's skepticism, there's money on the
table here.

320
00:20:31.479 --> 00:20:35.359
<v Speaker 3>They want the proof is always in the
pudding, as I, I don't know if that translates,

321
00:20:35.400 --> 00:20:38.750
<v Speaker 3>it goes across the pond to America well,
but in, in we said the proof's in the

322
00:20:38.750 --> 00:20:39.180
<v Speaker 3>pudding.

323
00:20:39.640 --> 00:20:46.439
<v Speaker 3>So, yeah, a POC is always perceived to be
a lower risk approach to go

324
00:20:46.439 --> 00:20:48.500
<v Speaker 3>in to demonstrate the value.

325
00:20:49.540 --> 00:20:55.060
<v Speaker 3>What I see going wrong is there is no plan
to scale thereafter.

326
00:20:55.989 --> 00:21:02.810
<v Speaker 3>So We should always go into a proof of
concept with if we can

327
00:21:02.810 --> 00:21:06.239
<v Speaker 3>demonstrate success, this is the plan on
day 2.

328
00:21:07.229 --> 00:21:11.670
<v Speaker 3>Or, or actually day one, after the end of
the POC where we start to deploy more

329
00:21:11.670 --> 00:21:17.550
<v Speaker 3>broadly, and, and that's when we talk
about scale, but that's when the value

330
00:21:17.550 --> 00:21:19.150
<v Speaker 3>increases for the customer.

331
00:21:19.430 --> 00:21:24.310
<v Speaker 3>They've proven it, they're comfortable
with it, the skepticism, yeah, and we've

332
00:21:24.310 --> 00:21:28.229
<v Speaker 3>always done it this way, has gone out the
window because they've seen it as a new

333
00:21:28.229 --> 00:21:29.189
<v Speaker 3>way, a better way.

334
00:21:29.890 --> 00:21:30.869
<v Speaker 3>And they moved forward

335
00:21:32.880 --> 00:21:37.920
<v Natalie>I think one of the key words you used in
there, Nick, was, uh, if we achieve

336
00:21:37.920 --> 00:21:43.680
<v Natalie>success, so you have to decide to define
quantifiably what is success and make sure

337
00:21:43.680 --> 00:21:45.270
<v Natalie>it's actually an attainable thing.

338
00:21:45.800 --> 00:21:49.670
<v Natalie>You could say we want to have like 50
hours of downtime avoided on these 4 assets

339
00:21:49.670 --> 00:21:50.479
<v Natalie>over the next month.

340
00:21:50.640 --> 00:21:52.479
<v Natalie>Like, how often do they actually fail?

341
00:21:52.560 --> 00:21:54.140
<v Natalie>Could you, could, is it possible?

342
00:21:54.660 --> 00:21:54.869
<v Natalie>Right?

343
00:21:54.979 --> 00:21:58.689
<v Natalie>So you have to make sure you're defining
those, or whether you call it a proof of

344
00:21:58.689 --> 00:22:02.260
<v Natalie>concept or an initial deployment, I would
consider them to be the same, really the

345
00:22:02.260 --> 00:22:02.989
<v Natalie>same thing.

346
00:22:03.219 --> 00:22:07.339
<v Natalie>Um, the most important thing from my
perspective is that like Nick said, you're,

347
00:22:07.589 --> 00:22:13.319
<v Natalie>you're defining success, having a plan,
but also using the app to its full capacity

348
00:22:13.540 --> 00:22:16.199
<v Natalie>and not limiting it in this initial
deployment.

349
00:22:16.260 --> 00:22:20.920
<v Natalie>So limiting it might mean, you know, not
using the copilot, or it might mean.

350
00:22:21.479 --> 00:22:25.170
<v Natalie>Um, I'm not actually sending in live data
and trying to use, you know, historic

351
00:22:25.170 --> 00:22:28.109
<v Natalie>data, which is not, it's just not how the
app works.

352
00:22:31.939 --> 00:22:37.670
<v Liz McGinn>How do you talk to customers who are kind
of adverse to implementing this new

353
00:22:37.670 --> 00:22:38.030
<v Liz McGinn>technology?

354
00:22:38.390 --> 00:22:41.949
<v Liz McGinn>How would, like, what kind of
recommendations would you, you know, have when you

355
00:22:41.949 --> 00:22:46.709
<v Liz McGinn>walk into these who are, you know, these
old school who are like, no, thank you, I

356
00:22:46.709 --> 00:22:48.410
<v Liz McGinn>don't want to do an extra step.

357
00:22:51.310 --> 00:22:58.189
<v Todd Martin>Um, Well, in the case of ours that we did
do a, a, a, a proof of concept and we were

358
00:22:58.189 --> 00:23:02.449
<v Todd Martin>able to demonstrate with that proof of
concept that the, that the technology was

359
00:23:02.689 --> 00:23:05.209
<v Todd Martin>100% effective, um.

360
00:23:06.400 --> 00:23:10.640
<v Todd Martin>Catching the, um, catching the conditions
that we initially wanted to catch with it.

361
00:23:10.920 --> 00:23:11.449
<v Todd Martin>Um.

362
00:23:14.150 --> 00:23:20.900
<v Todd Martin>So Going from there, you know, was like,

363
00:23:20.979 --> 00:23:23.219
<v Todd Martin>OK, hey, we just showed it.

364
00:23:24.079 --> 00:23:28.689
<v Todd Martin>That was enough to show, you know,
management that the system was.

365
00:23:29.500 --> 00:23:33.319
<v Todd Martin>Was um worked successful and accurate.

366
00:23:34.719 --> 00:23:36.290
<v Todd Martin>We scaled it up immediately.

367
00:23:37.219 --> 00:23:43.339
<v Todd Martin>And the fact that we was actually able to
get ROI within a month,

368
00:23:44.180 --> 00:23:48.630
<v Todd Martin>you know, of on there was Got most of the
hardcore.

369
00:23:50.040 --> 00:23:52.979
<v Todd Martin>Mm, then some of the other ones that were
a little more hesitant.

370
00:23:54.209 --> 00:23:56.189
<v Todd Martin>Was you just ignored us and.

371
00:23:57.520 --> 00:23:58.670
<v Todd Martin>And here you go.

372
00:23:59.199 --> 00:24:00.109
<v Todd Martin>As you can imagine.

373
00:24:00.729 --> 00:24:03.660
<v Todd Martin>Unfortunately, you wanna try to avoid that
situation.

374
00:24:04.599 --> 00:24:06.910
<v Todd Martin>Um, as much as possible, but.

375
00:24:08.760 --> 00:24:12.560
<v Natalie>I think the, the important thing is like,
like Todd is saying, is the internal

376
00:24:12.560 --> 00:24:19.160
<v Natalie>messaging, um, within the users and the
champions of Sensei, Capture those

377
00:24:19.160 --> 00:24:23.680
<v Natalie>successes, document them, spread the
messaging internally, like, hey, this thing is

378
00:24:23.680 --> 00:24:28.339
<v Natalie>saving us work, it's preventing downtime
avoided, and You know, whatever else your

379
00:24:28.339 --> 00:24:32.660
<v Natalie>KPIs are and making sure that that
information is being shared internally.

380
00:24:34.300 --> 00:24:39.500
<v Todd Martin>Yeah, definitely just, you know, since I
started it 7 years ago, there's 7 years of

381
00:24:39.500 --> 00:24:44.979
<v Todd Martin>lessons learned that you can rely on to
help you with, with this journey and you

382
00:24:44.979 --> 00:24:49.880
<v Todd Martin>know, getting going with it and it's, it's
all good valuable information and proven.

383
00:24:51.630 --> 00:24:57.510
<v Speaker 3>I, I, I think just, just also listening,
if people are objecting and creating these

384
00:24:57.510 --> 00:25:03.229
<v Speaker 3>barriers, I think it's also important to
understand why they're objecting.

385
00:25:03.890 --> 00:25:08.609
<v Speaker 3>Because the, the, oh I don't wanna do it
that way, there's a reason why.

386
00:25:08.810 --> 00:25:10.910
<v Speaker 3>I it, it, it can be ranging from.

387
00:25:11.569 --> 00:25:16.369
<v Speaker 3>You know, lack of knowledge of what
benefits the tools could actually give them, the

388
00:25:16.369 --> 00:25:17.209
<v Speaker 3>process could give them.

389
00:25:17.839 --> 00:25:21.869
<v Speaker 3>It could be actually they're protect, they
feel they need to be in job protection

390
00:25:21.869 --> 00:25:24.040
<v Speaker 3>mode, that this is, this is a threat.

391
00:25:25.000 --> 00:25:29.880
<v Speaker 3>So understanding those objections,
obviously you can address that on a 1 to 1, but

392
00:25:29.880 --> 00:25:34.319
<v Speaker 3>another important thing is these same
resistance points will actually be quietly

393
00:25:34.319 --> 00:25:34.959
<v Speaker 3>elsewhere.

394
00:25:35.780 --> 00:25:40.329
<v Speaker 3>So taking those things, and you know when
I was talking about earlier on, not it's

395
00:25:40.329 --> 00:25:44.619
<v Speaker 3>not just about the the KPI it's about
actually the emotional connection.

396
00:25:45.099 --> 00:25:47.400
<v Speaker 3>Why does this make my life better?

397
00:25:47.979 --> 00:25:51.319
<v Speaker 3>Not just about it improves, you know,
unplanned downtime for example.

398
00:25:52.790 --> 00:25:57.709
<v Speaker 3>That allows you to bring those into your
communication as well and address it uh

399
00:25:57.709 --> 00:25:58.430
<v Speaker 3>more broadly.

400
00:25:59.140 --> 00:26:05.910
<v Speaker 3>At some point, you know, you could drag
the horse to water, but you can't always

401
00:26:05.910 --> 00:26:07.489
<v Speaker 3>necessarily make it drink.

402
00:26:08.030 --> 00:26:11.709
<v Speaker 3>And change happens and you have to
progress.

403
00:26:12.189 --> 00:26:14.939
<v Speaker 3>So, you know, I think there's a lot you
can do.

404
00:26:15.229 --> 00:26:19.949
<v Speaker 3>There's a lot of things around the KPIs
and just subtle messaging, addressing the

405
00:26:19.949 --> 00:26:20.589
<v Speaker 3>concerns.

406
00:26:21.510 --> 00:26:25.709
<v Speaker 3>But at some, at some point, there are,
these are also businesses, yeah, we're all

407
00:26:25.709 --> 00:26:29.050
<v Speaker 3>working, we all work for a business, so we
have to go forward and make the

408
00:26:29.050 --> 00:26:30.109
<v Speaker 3>improvements we talk about.

409
00:26:34.180 --> 00:26:37.890
<v Liz McGinn>Yeah, I know, um, in our conversations,
you know, prepping for this, we mentioned

410
00:26:37.890 --> 00:26:42.949
<v Liz McGinn>something about the shift from
firefighting to the preventing and kind of that view

411
00:26:42.949 --> 00:26:48.819
<v Liz McGinn>of not being able to You look like a hero
when you, uh, you know, put out the fires.

412
00:26:49.109 --> 00:26:52.660
<v Liz McGinn>Doesn't really matter if you might have
started it in the, you know, in the

413
00:26:52.660 --> 00:26:57.250
<v Liz McGinn>background, but if you put it out and you
save it, then it tends to be, um, kind of

414
00:26:57.390 --> 00:26:57.589
<v Liz McGinn>that.

415
00:26:57.660 --> 00:27:01.150
<v Liz McGinn>So how do you Um, kind of encourage that
shift over.

416
00:27:02.880 --> 00:27:04.060
<v Todd Martin>Um, safety.

417
00:27:06.290 --> 00:27:12.859
<v Todd Martin>Um, sorry, sorry, Nick, but you know,
safety, the, the safety of your own

418
00:27:12.859 --> 00:27:17.810
<v Todd Martin>maintenance techs, um, as many of you're
aware of, you know, if you, if you're

419
00:27:17.810 --> 00:27:21.739
<v Todd Martin>trying to work on repair something during
a breakdown during production, there's

420
00:27:21.739 --> 00:27:25.859
<v Todd Martin>always this push to get done as quickly as
possible and get production going, and

421
00:27:25.859 --> 00:27:28.640
<v Todd Martin>that's really where a lot of your
accidents can happen.

422
00:27:29.969 --> 00:27:36.650
<v Todd Martin>By by getting that into a more controlled
environment, the safety of your techs, and

423
00:27:36.650 --> 00:27:41.780
<v Todd Martin>they can see that they're more prepped and
they're gonna be working in a much safer

424
00:27:41.780 --> 00:27:42.079
<v Todd Martin>environment.

425
00:27:44.089 --> 00:27:45.380
<v Todd Martin>That's a good point.

426
00:27:47.430 --> 00:27:47.739
<v Speaker 3>Yeah.

427
00:27:48.859 --> 00:27:53.780
<v Speaker 3>Liz, you made me smile because, um, I, I
used the phrase of, um, everybody loves to

428
00:27:53.780 --> 00:27:57.219
<v Speaker 3>be the hero, everybody loves to be the Red
Adair putting out the fires, but it's

429
00:27:57.219 --> 00:28:00.890
<v Speaker 3>only at some point you realize that Red
Adair was also the arsonist.

430
00:28:01.459 --> 00:28:06.560
<v Speaker 3>So, um, exactly to your, to, to, to the
point you were talking about, I, I think.

431
00:28:07.390 --> 00:28:11.829
<v Speaker 3>Uh, the, the safety thing is, I, I, I, a
lot of this is just, is about job

432
00:28:11.829 --> 00:28:13.280
<v Speaker 3>satisfaction as well, yeah.

433
00:28:14.170 --> 00:28:19.329
<v Speaker 3>Being, being actually proactive means that
you're not under the pressure, you'll

434
00:28:19.329 --> 00:28:25.530
<v Speaker 3>feel that you're actually making a
difference rather than just trying to maintain

435
00:28:25.750 --> 00:28:28.550
<v Speaker 3>the status quo that keeps crumbling around
you.

436
00:28:29.199 --> 00:28:32.569
<v Speaker 3>And I think that is really, um I, I've
talked about this recently in some other

437
00:28:32.569 --> 00:28:37.229
<v Speaker 3>podcasts, really, really important for
shop, shop floor morale.

438
00:28:37.770 --> 00:28:44.369
<v Speaker 3>And these tools really help, you know,
make people feel like they're adding value,

439
00:28:44.810 --> 00:28:47.329
<v Speaker 3>not just trying to keep the lights on.

440
00:28:47.530 --> 00:28:51.949
<v Speaker 3>So I think that's to me one of the most
beneficial things that we can do.

441
00:28:55.339 --> 00:28:56.459
<v Liz McGinn>It's a really good point.

442
00:28:56.579 --> 00:29:00.739
<v Liz McGinn>It's nice to, um, kind of have that uh
aspect of it.

443
00:29:00.780 --> 00:29:04.489
<v Liz McGinn>It's no one likes to have to work extra
weekends because there's these unplanned

444
00:29:04.489 --> 00:29:04.930
<v Liz McGinn>downtimes.

445
00:29:04.979 --> 00:29:08.400
<v Liz McGinn>They want to spend time with family and
friends and do their own thing.

446
00:29:08.540 --> 00:29:10.439
<v Liz McGinn>So, that makes a lot of sense.

447
00:29:11.260 --> 00:29:14.170
<v Liz McGinn>Um, we are just on time.

448
00:29:14.670 --> 00:29:18.310
<v Liz McGinn>Um, so thank you guys so much for joining
us today.

449
00:29:18.709 --> 00:29:19.949
<v Liz McGinn>Really appreciate it.

450
00:29:22.290 --> 00:29:24.329
<v Liz McGinn>And we'll pass it back off over to Nile.

451
00:29:26.699 --> 00:29:31.660
<v Speaker 1>Please like and subscribe on all major
podcast channels and find out more about

452
00:29:31.660 --> 00:29:35.040
<v Speaker 1>Sensei predictive maintenance at
Siemens.com.
