WEBVTT
Language: en-US

1
00:00:01.340 --> 00:00:07.400
<v Rachel Green>Being able to, you know, on the fly, work
with a tool to support you in that is

2
00:00:07.400 --> 00:00:13.000
<v Rachel Green>really quite a bit of a game changer and
it's basically being a substitute for

3
00:00:13.000 --> 00:00:18.110
<v Rachel Green>having that expert who may not be
available in the moment.

4
00:00:18.479 --> 00:00:21.760
<v Speaker 2>Welcome to the Trend detection podcast
powered by Siemens.

5
00:00:22.065 --> 00:00:26.325
<v Niall Sullivan>Hello and welcome to the the latest
episode of the Trend detection podcast.

6
00:00:26.784 --> 00:00:31.155
<v Niall Sullivan>I'm really pleased to be joined by a new,
I say a new colleague, you are relatively

7
00:00:31.155 --> 00:00:35.584
<v Niall Sullivan>new, Rachel, but also new to the podcast
is what I meant as well, so I'd love to

8
00:00:35.584 --> 00:00:37.404
<v Niall Sullivan>welcome you to the podcast first of all.

9
00:00:37.584 --> 00:00:38.884
<v Niall Sullivan>Thank you for joining us today.

10
00:00:39.305 --> 00:00:39.865
<v Rachel Green>Thank you, Niall.

11
00:00:40.025 --> 00:00:40.965
<v Rachel Green>Happy to be here.

12
00:00:41.305 --> 00:00:42.544
<v Niall Sullivan>Fantastic, fantastic.

13
00:00:42.909 --> 00:00:44.590
<v Niall Sullivan>We've got, I was about to say we've got a
really cool topic.

14
00:00:44.669 --> 00:00:47.830
<v Niall Sullivan>We always have cool topics on this
podcast, but we're talking about something that's

15
00:00:47.830 --> 00:00:52.150
<v Niall Sullivan>very, you know, you know, incredibly
topical, and it's not AI, although AI is going

16
00:00:52.150 --> 00:00:54.130
<v Niall Sullivan>to play a part in this conversation, no
doubt.

17
00:00:54.470 --> 00:00:58.669
<v Niall Sullivan>But we're talking about actual, you know,
people, and more specifically, the, the

18
00:00:58.669 --> 00:01:01.599
<v Niall Sullivan>experts in the field or on the plant
floor.

19
00:01:02.069 --> 00:01:06.339
<v Niall Sullivan>Actually, what happens is Experts who have
been working year after year for many

20
00:01:06.339 --> 00:01:10.370
<v Niall Sullivan>years, lots of knowledge, lots of
experience, no machines at the back of their hand

21
00:01:10.370 --> 00:01:11.180
<v Niall Sullivan>when they leave.

22
00:01:11.489 --> 00:01:15.279
<v Niall Sullivan>And we know that's a common sort of
problem that, you know, gonna have to face very,

23
00:01:15.339 --> 00:01:16.660
<v Niall Sullivan>very soon and into the future.

24
00:01:16.769 --> 00:01:20.540
<v Niall Sullivan>So, we're going to cover quite a lot of
topics within that, but I guess before we

25
00:01:20.849 --> 00:01:25.669
<v Niall Sullivan>get started, Rachel, would be great to
just introduce yourself, your background and

26
00:01:26.050 --> 00:01:27.389
<v Niall Sullivan>your role at Siemens as well.

27
00:01:27.400 --> 00:01:28.069
<v Niall Sullivan>It'd be great.

28
00:01:28.489 --> 00:01:28.989
<v Rachel Green>Absolutely.

29
00:01:29.209 --> 00:01:29.639
<v Rachel Green>Thanks, Niall.

30
00:01:29.800 --> 00:01:31.010
<v Rachel Green>So, my name is Rachel Green.

31
00:01:31.400 --> 00:01:37.319
<v Rachel Green>And I've joined Siemens with the goal of
supporting predictive maintenance powered

32
00:01:37.319 --> 00:01:38.389
<v Rachel Green>by Sensai.

33
00:01:38.800 --> 00:01:44.440
<v Rachel Green>And in this role, I'm talking with a lot
of our customers, a lot of manufacturing

34
00:01:44.440 --> 00:01:50.379
<v Rachel Green>and industrial folks who are facing a lot
of challenges on their shop floors.

35
00:01:50.599 --> 00:01:55.720
<v Rachel Green>And oftentimes those challenges extend
well beyond just, you know, how are we

36
00:01:55.720 --> 00:01:57.080
<v Rachel Green>getting this PM done?

37
00:01:57.209 --> 00:01:59.769
<v Rachel Green>How are we avoiding unplanned downtime.

38
00:02:00.209 --> 00:02:05.050
<v Rachel Green>They're really dealing with who's showing
up for this shift.

39
00:02:05.330 --> 00:02:10.000
<v Rachel Green>Do they have the expertise in-house to
deal with the problems they're facing?

40
00:02:10.279 --> 00:02:15.050
<v Rachel Green>If they're outsourcing it to a vendor, you
know, how are they overseeing those

41
00:02:15.050 --> 00:02:16.470
<v Rachel Green>vendors services?

42
00:02:16.889 --> 00:02:22.289
<v Rachel Green>And I'm coming towards this having spent
the last decade in supporting different

43
00:02:22.289 --> 00:02:24.889
<v Rachel Green>manufacturing IOT technologies.

44
00:02:25.410 --> 00:02:30.529
<v Rachel Green>And it's been an amazing time to be
working with manufacturers, having gone through

45
00:02:30.529 --> 00:02:36.600
<v Rachel Green>the challenges around COVID, where we saw
huge leaps in technology adoption because

46
00:02:36.600 --> 00:02:40.880
<v Rachel Green>we had to, not necessarily because people
wanted to.

47
00:02:41.360 --> 00:02:45.289
<v Rachel Green>And then some of the supply chain
challenges that have come after that.

48
00:02:45.369 --> 00:02:48.710
<v Rachel Green>It's been a fascinating time to be in this
industry.

49
00:02:49.160 --> 00:02:54.330
<v Rachel Green>And one of the things that I like to
highlight is all of the time that I've been

50
00:02:54.330 --> 00:02:59.679
<v Rachel Green>working with customers, bringing them
technology solutions, the recurring theme that

51
00:02:59.679 --> 00:03:06.089
<v Rachel Green>they've always had is, Rachel, what we
really need are the people to embrace

52
00:03:06.089 --> 00:03:12.169
<v Rachel Green>these technology solutions and help us
drive the change management that we need to

53
00:03:12.169 --> 00:03:14.210
<v Rachel Green>make them daily solutions.

54
00:03:14.690 --> 00:03:19.809
<v Rachel Green>And so, that's kind of been the recurring
challenge and theme throughout this part

55
00:03:19.809 --> 00:03:25.949
<v Rachel Green>of my career, so much so that I actually
started teaching a manufacturing IOT

56
00:03:25.949 --> 00:03:30.029
<v Rachel Green>technology course at one of our local
colleges here in southeastern Michigan.

57
00:03:30.449 --> 00:03:36.289
<v Rachel Green>Even if I could only turn out 1012, 20
students per semester, figuring that that

58
00:03:36.289 --> 00:03:40.330
<v Rachel Green>would be part of, excuse me, part of
helping that change management.

59
00:03:40.789 --> 00:03:41.369
<v Niall Sullivan>Fantastic.

60
00:03:41.539 --> 00:03:45.550
<v Niall Sullivan>And I guess that, you know, if we're,
we're sort of maybe coming to the end of, like

61
00:03:45.550 --> 00:03:48.869
<v Niall Sullivan>the, the, you know, full circle of what
we're going to talk about today, but I guess

62
00:03:48.869 --> 00:03:50.029
<v Niall Sullivan>that's part of the solution, right?

63
00:03:50.070 --> 00:03:53.309
<v Niall Sullivan>You're sort of part of the solution in
terms of what you're doing at Siemens plus

64
00:03:53.309 --> 00:03:55.369
<v Niall Sullivan>what you're doing there, which is, is
really cool.

65
00:03:56.169 --> 00:03:59.509
<v Niall Sullivan>Well, well, I guess, so let's start with,
if we think about sort of the scale of the

66
00:03:59.509 --> 00:04:02.229
<v Niall Sullivan>challenge, because it is something that's
talked about a lot, you know, lost

67
00:04:02.229 --> 00:04:05.070
<v Niall Sullivan>knowledge leaving the manufacturing
sector.

68
00:04:05.190 --> 00:04:09.660
<v Niall Sullivan>So, what is the scale of this challenge
from your conversations, Rachel?

69
00:04:09.949 --> 00:04:10.229
<v Rachel Green>Yeah.

70
00:04:10.669 --> 00:04:16.829
<v Rachel Green>I think for every leader, for every
manager that's out there, they see the

71
00:04:16.829 --> 00:04:23.029
<v Rachel Green>statistics, you know, I think some of the
latest ones are, you know, that we have

72
00:04:23.029 --> 00:04:29.690
<v Rachel Green>around 1/3 of the manufacturing workforce
that is actually eligible for retirement.

73
00:04:30.179 --> 00:04:31.619
<v Rachel Green>I'm sure we can fact check that.

74
00:04:31.660 --> 00:04:36.480
<v Rachel Green>It might be a little bit on either side,
and it probably varies by vertical, but

75
00:04:36.480 --> 00:04:42.980
<v Rachel Green>either way, that's a huge number, and
those are some of the most seasoned people in

76
00:04:42.980 --> 00:04:47.559
<v Rachel Green>these facilities, the most institutional
knowledge, the most respect.

77
00:04:48.329 --> 00:04:54.450
<v Rachel Green>So, it can be a huge challenge, and over
the next 5 years, this is definitely

78
00:04:54.450 --> 00:04:59.970
<v Rachel Green>something that a lot of companies are
going to navigate how they handle the

79
00:04:59.970 --> 00:05:02.429
<v Rachel Green>retirement of key employees.

80
00:05:02.809 --> 00:05:09.209
<v Rachel Green>And the biggest challenge is that there's
not really a backlog of

81
00:05:09.209 --> 00:05:14.200
<v Rachel Green>workers, a pool for them to hire from to
replace that experience.

82
00:05:14.649 --> 00:05:19.130
<v Rachel Green>And, you know, it's one thing to read the
statistics in You know, the National

83
00:05:19.130 --> 00:05:24.250
<v Rachel Green>Association of Manufacturing always puts
out a study to help us understand what

84
00:05:24.250 --> 00:05:27.589
<v Rachel Green>trends are on people's minds and what the
statistics are.

85
00:05:27.980 --> 00:05:34.299
<v Rachel Green>But the reality of it is, is, you know, I
go to maintenance stand-up meetings with

86
00:05:34.299 --> 00:05:40.140
<v Rachel Green>teams and look around and you can see,
hey, if, if we're 1 year out, that person's

87
00:05:40.140 --> 00:05:41.679
<v Rachel Green>probably not going to be here.

88
00:05:41.820 --> 00:05:46.019
<v Rachel Green>They're saying this person is 6 months out
from retiring, it looks like several

89
00:05:46.019 --> 00:05:50.700
<v Rachel Green>other people might also be close to that,
and just imagining.

90
00:05:50.895 --> 00:05:57.165
<v Rachel Green>How that meeting would be different
without those contributors is a huge impact for

91
00:05:57.165 --> 00:05:58.415
<v Rachel Green>companies to navigate.

92
00:05:58.906 --> 00:06:02.286
<v Niall Sullivan>Yeah, no, and absolutely, and you can
imagine that as well, even with, because I was

93
00:06:02.286 --> 00:06:05.726
<v Niall Sullivan>thinking even if you've got time to
prepare, but I guess some of that much

94
00:06:05.726 --> 00:06:10.205
<v Niall Sullivan>knowledge, that much experience, even 6
months, even a year is probably not, not

95
00:06:10.406 --> 00:06:12.876
<v Niall Sullivan>long enough to, to really plan for that,

96
00:06:12.885 --> 00:06:13.205
<v Rachel Green>because.

97
00:06:13.246 --> 00:06:13.626
<v Rachel Green>Yeah.

98
00:06:13.752 --> 00:06:18.631
<v Rachel Green>And they, you know, a lot of them make
jokes about it, and they'll be like, this

99
00:06:18.631 --> 00:06:25.391
<v Rachel Green>person has been driving maintenance for
the last 37 years in our

100
00:06:25.391 --> 00:06:30.451
<v Rachel Green>industry, and then they're like, and we've
got this person who's 3 years out of a,

101
00:06:30.712 --> 00:06:36.592
<v Rachel Green>you know, university program, and trying
to bridge the gap between those two.

102
00:06:36.989 --> 00:06:42.869
<v Rachel Green>And some of it I think is technical
knowledge, but some of it is, if you've had 37

103
00:06:42.869 --> 00:06:49.429
<v Rachel Green>years to build up your who you are, what
you've done, how you've saved the day, and

104
00:06:49.429 --> 00:06:52.690
<v Rachel Green>especially because maintenance is not only
doing the.

105
00:06:53.119 --> 00:06:59.760
<v Rachel Green>Individual actions every day, every week,
every year, but there's also some element

106
00:06:59.760 --> 00:07:04.640
<v Rachel Green>of the hero because these are the folks
that come in if there is some type of

107
00:07:04.640 --> 00:07:09.399
<v Rachel Green>unanticipated failure, if there is some
type of breakdown, and get everything back

108
00:07:09.399 --> 00:07:09.959
<v Rachel Green>online.

109
00:07:10.279 --> 00:07:15.640
<v Rachel Green>And being the hero over that time builds
credibility, you know, these are people

110
00:07:15.640 --> 00:07:20.959
<v Rachel Green>that can hack the situation to get
something back up and running, even if it isn't

111
00:07:20.959 --> 00:07:22.239
<v Rachel Green>the permanent solution.

112
00:07:22.750 --> 00:07:25.459
<v Rachel Green>And that heroism has a following.

113
00:07:25.829 --> 00:07:31.649
<v Rachel Green>So if you're coming in new and trying to
build that credibility, build that you can

114
00:07:31.649 --> 00:07:34.989
<v Rachel Green>also be the hero, that you can be someone
that's confident in.

115
00:07:35.220 --> 00:07:39.559
<v Rachel Green>It takes more than just technical
knowledge to be in that role.

116
00:07:40.029 --> 00:07:41.500
<v Niall Sullivan>No, yeah, it's a really interesting point.

117
00:07:41.660 --> 00:07:48.420
<v Niall Sullivan>Yeah, yeah, the, the credibility as well,
because actually, it also feeds into the,

118
00:07:48.820 --> 00:07:51.359
<v Niall Sullivan>you know, if you think about the
technology and you mentioned it in your

119
00:07:51.579 --> 00:07:55.260
<v Niall Sullivan>introduction as well, sort of the change
and adoption, because it's also, we talk

120
00:07:55.260 --> 00:07:58.459
<v Niall Sullivan>about the trust in the technology as well,
and part of the reason why sometimes it's

121
00:07:58.459 --> 00:08:01.019
<v Niall Sullivan>harder, or takes a bit of time, let's say,
to trust.

122
00:08:01.480 --> 00:08:06.220
<v Niall Sullivan>The technology is because you've got these
amazing people with all of this knowledge

123
00:08:06.619 --> 00:08:09.279
<v Niall Sullivan>inside, so it's like we've got these
people here who know, know all this stuff,

124
00:08:09.359 --> 00:08:09.570
<v Niall Sullivan>right?

125
00:08:09.679 --> 00:08:12.440
<v Niall Sullivan>So, so is that, that's part of the
conversation as well,

126
00:08:12.519 --> 00:08:12.880
<v Rachel Green>I'm sure.

127
00:08:13.109 --> 00:08:13.820
<v Rachel Green>Absolutely.

128
00:08:13.950 --> 00:08:19.059
<v Rachel Green>And one of the most telling stories that
I've had in the last couple of years is,

129
00:08:19.279 --> 00:08:24.239
<v Rachel Green>you know, machines have a tendency to
break down once dinner is being served, once

130
00:08:24.239 --> 00:08:28.660
<v Rachel Green>it's dark outside, once people's kids are
on the sports field, or if it's a holiday.

131
00:08:29.209 --> 00:08:35.010
<v Rachel Green>So, of course, this was a 3rd shift story
and I had somebody who basically was

132
00:08:35.010 --> 00:08:38.090
<v Rachel Green>reporting in that they were called from
the plant.

133
00:08:38.530 --> 00:08:39.760
<v Rachel Green>They were just going to bed.

134
00:08:40.229 --> 00:08:46.719
<v Rachel Green>And the pivot that they, like, experienced
viscerally is instead of grabbing for

135
00:08:46.719 --> 00:08:53.080
<v Rachel Green>their car keys to go to the plant and
help, you know, grab a tool and get involved

136
00:08:53.080 --> 00:08:59.559
<v Rachel Green>in repairing the equipment, they first
grabbed their laptop and they were going to

137
00:08:59.559 --> 00:09:05.599
<v Rachel Green>the data being collected by these tools,
by remote sensors and wanting to see what

138
00:09:05.599 --> 00:09:06.760
<v Rachel Green>the data is telling them.

139
00:09:07.344 --> 00:09:10.414
<v Rachel Green>Before needing to see the actual equipment
themselves.

140
00:09:10.854 --> 00:09:16.294
<v Rachel Green>And that change in mindset between knowing
that we can rely on data to help us

141
00:09:16.294 --> 00:09:21.775
<v Rachel Green>remotely through some of these
technological tools versus having to be on site,

142
00:09:22.135 --> 00:09:26.974
<v Rachel Green>particularly in the middle of the night,
45 minute drive from the plant, disturbing

143
00:09:26.974 --> 00:09:29.934
<v Rachel Green>your family, you know, all those types of
things.

144
00:09:30.255 --> 00:09:33.414
<v Rachel Green>I mean, these are real pains that people
are having.

145
00:09:33.859 --> 00:09:38.340
<v Rachel Green>As you know, manufacturing facilities are
never in the most convenient locations, so

146
00:09:38.340 --> 00:09:42.099
<v Rachel Green>most people are commuting and to get back
there in the middle of the night in our

147
00:09:42.099 --> 00:09:45.020
<v Rachel Green>part of the world, you're always dealing
with deer and all that kind of stuff.

148
00:09:45.059 --> 00:09:51.280
<v Rachel Green>And I mean, this is a real change in
people's workload to have data to rely on

149
00:09:52.330 --> 00:09:55.159
<v Rachel Green>first instead of having to be there in
person first.

150
00:09:55.530 --> 00:09:58.619
<v Niall Sullivan>And again, to your point, I mean, if you
take that point even further with the topic

151
00:09:58.619 --> 00:10:01.640
<v Niall Sullivan>we're talking about today, so if you rely
on one person who.

152
00:10:02.195 --> 00:10:05.135
<v Niall Sullivan>Or, or a small number of people, I should
say you have to go to the plant.

153
00:10:05.835 --> 00:10:09.315
<v Niall Sullivan>It becomes even more problem, you know,
problematic because you can see, are they

154
00:10:09.315 --> 00:10:09.674
<v Niall Sullivan>available?

155
00:10:09.715 --> 00:10:14.515
<v Niall Sullivan>Are they, you know, can they get to the
plant in a reasonable time and things like

156
00:10:14.515 --> 00:10:14.724
<v Niall Sullivan>that.

157
00:10:14.835 --> 00:10:20.184
<v Niall Sullivan>So, if you take the data point away and
there's a few really known experts that they

158
00:10:20.184 --> 00:10:21.294
<v Niall Sullivan>rely on, and

159
00:10:22.385 --> 00:10:22.414
<v Rachel Green>that's.

160
00:10:22.424 --> 00:10:22.434
<v Rachel Green>Yeah.

161
00:10:23.755 --> 00:10:25.354
<v Rachel Green>This was so exemplified.

162
00:10:25.455 --> 00:10:30.094
<v Rachel Green>I actually talked with a company and they,
their maintenance strategy.

163
00:10:30.700 --> 00:10:34.159
<v Rachel Green>Was jokingly referred to as what would
David do?

164
00:10:34.630 --> 00:10:40.679
<v Rachel Green>And they had a person named David, who was
essentially that hero for them.

165
00:10:41.039 --> 00:10:45.799
<v Rachel Green>And to the point where not just at the
facility he was at, but they would fly this

166
00:10:45.799 --> 00:10:48.630
<v Rachel Green>person to other facilities to consult.

167
00:10:49.000 --> 00:10:51.739
<v Rachel Green>They would get his input, all that type of
thing.

168
00:10:51.849 --> 00:10:58.260
<v Rachel Green>He had become the expert, but also the
hero in this to help drive confidence

169
00:10:58.260 --> 00:11:02.840
<v Rachel Green>in maintenance changes, repairs, planning,
those types of things.

170
00:11:03.239 --> 00:11:09.799
<v Rachel Green>But to your point, What happens if David
wins the lottery or decides to retire or

171
00:11:09.799 --> 00:11:15.640
<v Rachel Green>anything else, you know, we try and design
systems that are not reliant on a single

172
00:11:15.640 --> 00:11:20.799
<v Rachel Green>person or their expertise because we want
to have the business continuity be more

173
00:11:20.799 --> 00:11:21.960
<v Rachel Green>flexible than that.

174
00:11:22.390 --> 00:11:27.150
<v Rachel Green>And you can always have that person's
input, but being able to involve others and

175
00:11:27.150 --> 00:11:33.830
<v Rachel Green>upskill others and rely on others is
really the kind of thing where having a tool in

176
00:11:33.830 --> 00:11:38.450
<v Rachel Green>place to do that will give you a lot more
confidence in, in the business long term

177
00:11:38.450 --> 00:11:41.950
<v Rachel Green>and not have a scenario where you're just
relying on one person.

178
00:11:42.479 --> 00:11:48.039
<v Rachel Green>Obviously, you might still have standout
leaders and amazing experts, but having

179
00:11:48.039 --> 00:11:53.400
<v Rachel Green>underlying systems to support everyone in
becoming the next generation standout

180
00:11:53.400 --> 00:11:55.559
<v Rachel Green>expert is really important too.

181
00:11:55.840 --> 00:11:56.150
<v Rachel Green>Yeah,

182
00:11:56.679 --> 00:12:00.500
<v Niall Sullivan>and I, I guess part, part of the, part of
the issue as well is that the knowledge,

183
00:12:00.969 --> 00:12:04.400
<v Niall Sullivan>you know, if we compare it again to the
technology side is the knowledge is sort of

184
00:12:04.400 --> 00:12:05.090
<v Niall Sullivan>trapped in.

185
00:12:05.299 --> 00:12:09.330
<v Niall Sullivan>These people's head, it's one thing
relying on them personally to fly them out all

186
00:12:09.330 --> 00:12:13.940
<v Niall Sullivan>over the place to do it, but even if some
of that knowledge was captured and, you

187
00:12:13.940 --> 00:12:17.099
<v Niall Sullivan>know, stored and easily accessible, that
doesn't solve the issue, of course, because

188
00:12:17.099 --> 00:12:23.059
<v Niall Sullivan>it needs to be interpreted and nothing
beats experience and knowledge, but yeah, so

189
00:12:23.059 --> 00:12:24.000
<v Niall Sullivan>I, I guess.

190
00:12:24.380 --> 00:12:28.020
<v Niall Sullivan>Yeah, I mean, I guess you sort of
explained it, but what, why this knowledge is sort

191
00:12:28.020 --> 00:12:33.010
<v Niall Sullivan>of trapped in heads and not documented
anywhere, because which would help, I guess,

192
00:12:33.219 --> 00:12:34.059
<v Rachel Green>towards this issue.

193
00:12:34.979 --> 00:12:39.820
<v Rachel Green>I mean, I think, I think the want for us
to be able to.

194
00:12:39.919 --> 00:12:46.719
<v Rachel Green>Approach it in a knowledge-based way, in a
standard operating procedure, and SOP is

195
00:12:46.719 --> 00:12:50.239
<v Rachel Green>fantastic and the world is definitely
gravitating that way and we want to have

196
00:12:50.239 --> 00:12:54.919
<v Rachel Green>checklists and SOPs for everything, and I
absolutely think those are critical and

197
00:12:54.919 --> 00:12:55.340
<v Rachel Green>important.

198
00:12:55.840 --> 00:13:02.520
<v Rachel Green>But the need for maintenance and
predictive maintenance is because of the chaos

199
00:13:02.520 --> 00:13:09.159
<v Rachel Green>of the operating environment and the
variables that are introduced by the

200
00:13:09.159 --> 00:13:13.840
<v Rachel Green>process itself, where the process is being
done, who's the operator running it.

201
00:13:14.309 --> 00:13:17.919
<v Rachel Green>And so you've got these factions basically
at war.

202
00:13:18.000 --> 00:13:22.440
<v Rachel Green>You've got the, you know, the SOP which
tells you this is exactly the way it's gonna

203
00:13:22.440 --> 00:13:25.280
<v Rachel Green>go, and then you've got reality, which
tells you, well, you've got different

204
00:13:25.280 --> 00:13:29.119
<v Rachel Green>operators, you've got different processes,
you've got different products which might

205
00:13:29.119 --> 00:13:35.119
<v Rachel Green>have different variables, and maintenance
is kind of a, a chaotic space and

206
00:13:35.119 --> 00:13:37.239
<v Rachel Green>especially if you've had a breakdown.

207
00:13:37.640 --> 00:13:41.520
<v Rachel Green>You're going to that machine and just
knowing they had to shut it down.

208
00:13:41.840 --> 00:13:46.719
<v Rachel Green>Well, did they have to shut it down
because quality of the product disintegrated, or

209
00:13:46.719 --> 00:13:51.599
<v Rachel Green>did they have to shut it down because it's
starting to rip itself apart and throw

210
00:13:51.599 --> 00:13:53.830
<v Rachel Green>parts and pieces all over the floor?

211
00:13:54.320 --> 00:13:59.559
<v Rachel Green>Those are two very different scenarios,
but both reasons to shut a machine down, and

212
00:13:59.559 --> 00:14:01.000
<v Rachel Green>it dictates a very different.

213
00:14:01.085 --> 00:14:03.726
<v Rachel Green>Places to start in your troubleshooting
technique.

214
00:14:04.046 --> 00:14:08.885
<v Rachel Green>And so, one of the challenges for how do
you create change management, how do you

215
00:14:08.885 --> 00:14:14.205
<v Rachel Green>create a system that supports this, is
creating something that's agile enough to

216
00:14:14.205 --> 00:14:19.176
<v Rachel Green>say, here's where you start, but your
troubleshooting might go in very, very

217
00:14:19.176 --> 00:14:20.116
<v Rachel Green>different ways.

218
00:14:20.406 --> 00:14:24.606
<v Rachel Green>And that's where some of the
conversational IA is really powerful.

219
00:14:25.531 --> 00:14:32.372
<v Rachel Green>We're seeing that ability to be agile
enough to maintain the

220
00:14:32.372 --> 00:14:34.122
<v Rachel Green>conversation during the repair.

221
00:14:34.411 --> 00:14:38.651
<v Rachel Green>OK, start with the least invasive, go to
the most invasive in terms of

222
00:14:38.651 --> 00:14:43.892
<v Rachel Green>troubleshooting technique, but also, if
you're finding this as you're doing your oil

223
00:14:43.892 --> 00:14:50.651
<v Rachel Green>analysis, then pivot to this type of
troubleshooting and being able to, you know, on

224
00:14:50.651 --> 00:14:53.971
<v Rachel Green>the fly, work with a tool to support you
in that.

225
00:14:54.409 --> 00:15:00.380
<v Rachel Green>is really quite a bit of a game changer
and it's basically being a substitute for

226
00:15:00.380 --> 00:15:06.940
<v Rachel Green>having that expert who may not be
available in the moment, may not be

227
00:15:06.940 --> 00:15:12.739
<v Rachel Green>available anymore if they've departed the
workforce and trying to stand up that

228
00:15:12.739 --> 00:15:13.359
<v Rachel Green>institutional knowledge.

229
00:15:14.020 --> 00:15:14.260
<v Rachel Green>Yeah,

230
00:15:14.419 --> 00:15:19.299
<v Niall Sullivan>and I, and I see that as well, it's what,
yeah, what, what I was thinking is that.

231
00:15:19.650 --> 00:15:23.940
<v Niall Sullivan>You know, back to my, my point about the
having some, you know, even if you document

232
00:15:23.940 --> 00:15:27.570
<v Niall Sullivan>everything right, but you still have to
sort of interpret that, that knowledge in

233
00:15:27.570 --> 00:15:27.739
<v Niall Sullivan>some way.

234
00:15:27.820 --> 00:15:30.979
<v Niall Sullivan>So, the tools you're referring to, you
know, Germanative AI, I knew AI would come

235
00:15:30.979 --> 00:15:31.200
<v Niall Sullivan>up.

236
00:15:31.640 --> 00:15:36.419
<v Niall Sullivan>So, that isn't a big take, to be fair,
but, but we know that's interesting.

237
00:15:36.715 --> 00:15:39.895
<v Niall Sullivan>how you position that as sort of like, you
know, not, you know, careful to say

238
00:15:39.895 --> 00:15:45.375
<v Niall Sullivan>replacement, but when, you know, if the
expert or the small subset of experts are

239
00:15:45.375 --> 00:15:49.315
<v Niall Sullivan>unavailable, then you've, if you've
captured the knowledge and documented it, then

240
00:15:49.534 --> 00:15:53.275
<v Niall Sullivan>you could, you know, you, you could use a
tool, AI to help.

241
00:15:53.669 --> 00:15:58.150
<v Niall Sullivan>Yeah, and work with it, ask the questions
you need, troubleshoot certain, certain

242
00:15:58.150 --> 00:16:01.760
<v Niall Sullivan>options, look back at previous cases, if
we're talking about Sensa, particularly

243
00:16:01.760 --> 00:16:05.349
<v Niall Sullivan>compared to previous cases, things like
that, and that's where you get, you know,

244
00:16:05.590 --> 00:16:09.109
<v Niall Sullivan>not a complete replacement, but rather
than, you know, you could ask, you know, what

245
00:16:09.109 --> 00:16:12.150
<v Niall Sullivan>happens to go when it went down or
whatever, you, you've got it documented, you can

246
00:16:12.150 --> 00:16:15.210
<v Niall Sullivan>ask, you can interrogate the system and
that kind of thing.

247
00:16:15.710 --> 00:16:20.750
<v Rachel Green>Yeah, and, and I think, you know, there
should be quite a bit of sensitivity around

248
00:16:20.750 --> 00:16:23.409
<v Rachel Green>what are we replacing and what are we.

249
00:16:23.869 --> 00:16:30.070
<v Rachel Green>Making more efficient because if we can
get that person to spend more time on the

250
00:16:30.070 --> 00:16:36.830
<v Rachel Green>floor, acting on the maintenance activity
instead of going through old work

251
00:16:36.830 --> 00:16:41.549
<v Rachel Green>orders, trying to find the maintenance
guide, trying to call the person that did the

252
00:16:41.549 --> 00:16:47.510
<v Rachel Green>last repair to find out what happened
then, less time on the investigation or

253
00:16:47.510 --> 00:16:50.869
<v Rachel Green>creating the plan and more time executing.

254
00:16:51.409 --> 00:16:58.169
<v Rachel Green>I think that's really the, the variable
there, and being able to execute with a high

255
00:16:58.169 --> 00:17:04.410
<v Rachel Green>degree of confidence, even if you have
less expert input is really where we want to

256
00:17:04.410 --> 00:17:05.209
<v Rachel Green>get people.

257
00:17:05.689 --> 00:17:11.530
<v Rachel Green>So, this might be, you know, your second
shift maintenance person and instead of

258
00:17:11.615 --> 00:17:17.416
<v Rachel Green>Having a 45 minute conversation with an
expert, can they use a tool to refer to

259
00:17:17.416 --> 00:17:22.495
<v Rachel Green>previous work orders, refer to previous
outcomes, make sure that they've consulted

260
00:17:22.495 --> 00:17:28.196
<v Rachel Green>the diagrams, the manuals, you know, all
the spare part inventory, and then be ready

261
00:17:28.196 --> 00:17:31.816
<v Rachel Green>to go, and maybe it's a 5-minute
conversation with an expert in.

262
00:17:31.911 --> 00:17:33.401
<v Rachel Green>Instead of a 45.

263
00:17:33.781 --> 00:17:38.381
<v Rachel Green>Maybe it's just text exchange while
they're getting themselves out to the equipment

264
00:17:38.381 --> 00:17:42.812
<v Rachel Green>and getting the tools and the spare parts
kitted and ready to go.

265
00:17:43.261 --> 00:17:48.141
<v Rachel Green>Those are things that make a real
difference when your downtime is being calculated

266
00:17:48.141 --> 00:17:49.881
<v Rachel Green>by the seconds or the minutes.

267
00:17:49.982 --> 00:17:52.102
<v Rachel Green>And that's, that's a real scenario.

268
00:17:52.530 --> 00:17:57.739
<v Niall Sullivan>And I think the idea as well, I mean,
yeah, again, easy to refer back to, to Sensai,

269
00:17:57.810 --> 00:18:02.089
<v Niall Sullivan>but what I think fits well is, you know,
in terms of prioritization as well, you

270
00:18:02.089 --> 00:18:06.829
<v Niall Sullivan>know, the, the, the technology can, you
know, it's not raising cases on everything

271
00:18:06.829 --> 00:18:11.810
<v Niall Sullivan>for every small little deviation, but it's
sort of pointing attention to where it

272
00:18:11.810 --> 00:18:12.319
<v Niall Sullivan>needs it most.

273
00:18:12.410 --> 00:18:17.449
<v Niall Sullivan>But then, and then subsequently, if you do
need an, you know, a human expert to come

274
00:18:17.449 --> 00:18:19.810
<v Niall Sullivan>into that, you can then focus their
attention on what's.

275
00:18:20.229 --> 00:18:23.589
<v Niall Sullivan>Needed most and not sort of running around
trying to, I know, putting out fires is

276
00:18:23.589 --> 00:18:28.390
<v Niall Sullivan>the typical phrase, isn't it, but, yeah,
but it's, it, it's a lot more focused, it's

277
00:18:28.390 --> 00:18:32.500
<v Niall Sullivan>focusing that expert where, you know,
where they can be most, where they can be most

278
00:18:32.500 --> 00:18:36.390
<v Niall Sullivan>useful, basically, rather than spreading
themselves too thin across lots of

279
00:18:36.390 --> 00:18:37.069
<v Niall Sullivan>different things.

280
00:18:37.369 --> 00:18:40.930
<v Rachel Green>Yeah, I mean, you mentioned putting out
fires and sometimes that's literal and

281
00:18:40.930 --> 00:18:46.030
<v Rachel Green>sometimes it's figurative, uh, but, you
know, the, the maintenance team, I have yet

282
00:18:46.050 --> 00:18:52.250
<v Rachel Green>to go into a facility and have had them
admit that they've got too many maintenance

283
00:18:52.250 --> 00:18:57.609
<v Rachel Green>experts, that they've got too much, too
many resources in those types of

284
00:18:57.609 --> 00:18:58.270
<v Rachel Green>departments.

285
00:18:58.569 --> 00:19:01.030
<v Rachel Green>I just am not seeing it in the US.

286
00:19:01.250 --> 00:19:07.040
<v Rachel Green>So, we're coming in assuming that this is
a department that is strapped.

287
00:19:07.329 --> 00:19:11.229
<v Rachel Green>There's not enough time for the activities
they likely need to do.

288
00:19:11.569 --> 00:19:18.050
<v Rachel Green>And so, every day, every hour, they're
basically balancing how are we spending our

289
00:19:18.050 --> 00:19:23.449
<v Rachel Green>time and how are we getting the most
output for that time.

290
00:19:24.020 --> 00:19:29.180
<v Rachel Green>So, there's the, you know, what fires are
we fighting today, but as you talk about

291
00:19:29.180 --> 00:19:33.430
<v Rachel Green>tools like Sensai and some of the others
that are out there, one of the things I

292
00:19:33.430 --> 00:19:37.000
<v Rachel Green>love to do is take it into more of a
strategic look.

293
00:19:37.339 --> 00:19:44.260
<v Rachel Green>If you have a facility that has limited
planned downtime, so maybe you do an annual

294
00:19:44.260 --> 00:19:49.160
<v Rachel Green>shutdown, and that shutdown's 4 days, and
during that day, you're going to bring in

295
00:19:49.420 --> 00:19:52.699
<v Rachel Green>tens or hundreds of vendors to get many,
many.

296
00:19:52.810 --> 00:19:56.300
<v Rachel Green>The activities done because it's the only
time you take the plant down.

297
00:19:56.810 --> 00:20:03.530
<v Rachel Green>Using Sensii or a tool like that to
prioritize those activities, using

298
00:20:03.530 --> 00:20:08.410
<v Rachel Green>Sensii to tell you, hey, we had this on
the list, but that equipment is still in a

299
00:20:08.410 --> 00:20:13.079
<v Rachel Green>green status, maybe it doesn't need to be
done on this shutdown, maybe we push that

300
00:20:13.079 --> 00:20:13.670
<v Rachel Green>off.

301
00:20:14.170 --> 00:20:20.410
<v Rachel Green>That can be just as helpful and valuable
of an activity in terms of prioritizing

302
00:20:20.410 --> 00:20:21.650
<v Rachel Green>what you need to do.

303
00:20:22.030 --> 00:20:28.530
<v Rachel Green>It also pushing off what you can push off
because you have strapped resources,

304
00:20:28.910 --> 00:20:35.489
<v Rachel Green>and those types of use cases are really
what our team spends time, you know, working

305
00:20:35.489 --> 00:20:39.989
<v Rachel Green>with our customers on to say, OK, you've
got this data, you've got this activity,

306
00:20:40.349 --> 00:20:44.770
<v Rachel Green>how do you work through this and what's
the best outcome for your facility based on

307
00:20:44.770 --> 00:20:47.709
<v Rachel Green>the data that you're seeing and the
resources you have.

308
00:20:48.089 --> 00:20:52.489
<v Rachel Green>And this is what our customer success team
does day in and day out is to help our

309
00:20:52.489 --> 00:20:54.969
<v Rachel Green>teams with that, and it's a real
challenge.

310
00:20:55.410 --> 00:20:59.290
<v Niall Sullivan>Yeah, and, and yeah, it's interesting
because you mentioned, because I know, of

311
00:20:59.290 --> 00:21:02.650
<v Niall Sullivan>course, for, for a number of reasons,
mainly, you know, military is, you know,

312
00:21:02.810 --> 00:21:05.910
<v Niall Sullivan>downtime is usually or unplanned downtime
is usually the big.

313
00:21:06.290 --> 00:21:10.250
<v Niall Sullivan>Sort of focus here, but yeah, but I hear
it more and more conversations, you know,

314
00:21:10.329 --> 00:21:14.719
<v Niall Sullivan>about pushing out planned maintenance
schedules or, or, yeah, or being, you know,

315
00:21:14.849 --> 00:21:17.469
<v Niall Sullivan>again, like I said before about this
prioritization, isn't it?

316
00:21:17.479 --> 00:21:18.270
<v Niall Sullivan>It's where you can.

317
00:21:18.750 --> 00:21:22.880
<v Niall Sullivan>Sort of go, OK, and I, I know with some
customers, they've even sort of almost

318
00:21:22.880 --> 00:21:26.630
<v Niall Sullivan>eliminated it, like, almost, you know, to
the point where they're trusting the

319
00:21:26.630 --> 00:21:27.760
<v Niall Sullivan>system so much.

320
00:21:27.819 --> 00:21:32.760
<v Niall Sullivan>Obviously, they take some time, but once
you get to a point where it, you know, and

321
00:21:32.760 --> 00:21:36.959
<v Niall Sullivan>not just, you know, a lot of people in
various different teams are starting to trust

322
00:21:36.959 --> 00:21:37.359
<v Niall Sullivan>the system.

323
00:21:37.469 --> 00:21:40.229
<v Niall Sullivan>So much that they can actually get to a
point where they're like, No, no, we know

324
00:21:40.229 --> 00:21:41.819
<v Niall Sullivan>what we're doing here now.

325
00:21:42.349 --> 00:21:46.290
<v Niall Sullivan>That's such a great say, you think all of
that resource that can be allocated

326
00:21:46.469 --> 00:21:50.709
<v Niall Sullivan>somewhere else to look at, you know, to do
something else, maybe implement, you

327
00:21:50.709 --> 00:21:54.630
<v Niall Sullivan>know, or scale out predictive maintenance
even more other projects or other

328
00:21:54.630 --> 00:21:56.130
<v Niall Sullivan>digitalization projects.

329
00:21:56.430 --> 00:21:57.140
<v Niall Sullivan>And things.

330
00:21:57.380 --> 00:21:58.689
<v Niall Sullivan>So that's the, that's the power of it.

331
00:21:58.869 --> 00:21:59.650
<v Rachel Green>Absolutely.

332
00:21:59.750 --> 00:22:05.270
<v Rachel Green>And anytime you're talking about pushing
out a, a, you know, a PM, that's, that's

333
00:22:05.270 --> 00:22:09.670
<v Rachel Green>something to really undertake seriously,
depending on the vertical that you're in,

334
00:22:09.750 --> 00:22:14.439
<v Rachel Green>there may be other institutional
requirements around why that PM.

335
00:22:14.689 --> 00:22:20.579
<v Rachel Green>Exists, but in most of them, we find that
there are opportunities to reevaluate the

336
00:22:20.579 --> 00:22:26.359
<v Rachel Green>frequency of planned maintenance
activities, and that can be one strategy towards

337
00:22:26.359 --> 00:22:31.780
<v Rachel Green>optimizing those activities, towards the
resources you have and the condition of

338
00:22:31.780 --> 00:22:32.839
<v Rachel Green>your machines.

339
00:22:33.099 --> 00:22:39.319
<v Rachel Green>And that's a huge way to utilize a
technology like Senseii, which really helps you

340
00:22:39.560 --> 00:22:41.280
<v Rachel Green>visualize that condition.

341
00:22:41.819 --> 00:22:45.810
<v Rachel Green>And we're using more than just vibration,
which is really important.

342
00:22:46.229 --> 00:22:51.479
<v Rachel Green>Vibration has been kind of the foundation
for condition monitoring for critical

343
00:22:51.479 --> 00:22:56.979
<v Rachel Green>equipment, particularly rotating
equipment, but Sensii is relatively sensor

344
00:22:56.979 --> 00:23:02.609
<v Rachel Green>agnostic, so we can bring in vibration
plus a lot of other things to help give you

345
00:23:02.609 --> 00:23:09.060
<v Rachel Green>contextual data to your conditional
monitoring program, and that really helps you

346
00:23:09.060 --> 00:23:11.140
<v Rachel Green>drive a more cohesive.

347
00:23:11.420 --> 00:23:16.729
<v Rachel Green>Understanding of that condition and the
process, and it usually helps you get

348
00:23:16.729 --> 00:23:22.290
<v Rachel Green>farther along in the troubleshooting and
the root cause analysis when issues do come

349
00:23:22.290 --> 00:23:27.890
<v Rachel Green>up, which can be so powerful to see in
terms of shortening your timeline to a

350
00:23:27.890 --> 00:23:28.430
<v Rachel Green>solution.

351
00:23:28.849 --> 00:23:33.170
<v Niall Sullivan>Yeah, and I think, yeah, and I mean, the
key word here, and I did a podcast recently

352
00:23:33.170 --> 00:23:37.989
<v Niall Sullivan>with Sensai's head of research, so person
responsible for all the, the clever

353
00:23:37.989 --> 00:23:39.910
<v Niall Sullivan>algorithms, or him and his team, I should
say.

354
00:23:40.459 --> 00:23:45.459
<v Niall Sullivan>In, in the background and, and just talk
about that word context is so important in

355
00:23:45.459 --> 00:23:49.380
<v Niall Sullivan>sense like, the, the more context you can
bring in, whether it's down to, you know,

356
00:23:49.699 --> 00:23:53.699
<v Niall Sullivan>you know, literal pictures of the, the,
what the machine is, right?

357
00:23:53.810 --> 00:23:57.479
<v Niall Sullivan>You know, and, and this detailed
description of what the asset in machine is.

358
00:23:57.969 --> 00:24:03.150
<v Niall Sullivan>You know, bringing work orders, upload
manuals, you know, into the knowledge tab.

359
00:24:03.530 --> 00:24:08.069
<v Niall Sullivan>And of course, even we talk about
expertise and ways to capture the knowledge, and

360
00:24:08.130 --> 00:24:13.089
<v Niall Sullivan>you can do that via Sensai as well, you
know, feedback on cases and, or adding notes

361
00:24:13.089 --> 00:24:16.589
<v Niall Sullivan>to, yeah, yeah, and this kind of thing, it
just continues to build, you know,

362
00:24:16.739 --> 00:24:19.550
<v Niall Sullivan>context, and it learns and it improves.

363
00:24:20.010 --> 00:24:22.839
<v Niall Sullivan>And I guess that's what we're, we're
coming to, right, in terms of, you know, how,

364
00:24:22.939 --> 00:24:26.569
<v Niall Sullivan>how do we preserve that knowledge, and
that's one way to do it or what, you know,

365
00:24:26.780 --> 00:24:30.579
<v Niall Sullivan>and use, using AI and of course, co-pilots
and things like that too.

366
00:24:30.939 --> 00:24:37.430
<v Rachel Green>Yep, yeah, it, there's, there's so many
real life examples of how that happens.

367
00:24:37.540 --> 00:24:43.619
<v Rachel Green>One of the, one of the examples I like to
use is with pumps, oftentimes you will get

368
00:24:43.619 --> 00:24:48.660
<v Rachel Green>some type of indicator that tells you that
pump is experiencing cavitation.

369
00:24:49.130 --> 00:24:54.170
<v Rachel Green>And then oftentimes you'll be able to get
a troubleshooting list of the things you

370
00:24:54.170 --> 00:24:55.479
<v Rachel Green>should look at for that.

371
00:24:55.969 --> 00:25:02.250
<v Rachel Green>But with Sensii, if you're getting not
only the vibration for that pump, as well as

372
00:25:02.250 --> 00:25:07.170
<v Rachel Green>upstream or downstream valve information
in terms of how that pump is being fed.

373
00:25:07.670 --> 00:25:11.790
<v Rachel Green>Then the troubleshooting goes to the next
level, because you might know exactly

374
00:25:11.790 --> 00:25:16.560
<v Rachel Green>which valve is malfunctioning that is
causing the cavitation in the pump.

375
00:25:16.989 --> 00:25:21.430
<v Rachel Green>So then, again, your strapped maintenance
personnel, instead of getting a list

376
00:25:21.430 --> 00:25:26.180
<v Rachel Green>that's this long of different things that
could be causing the cavitation, it's

377
00:25:26.180 --> 00:25:28.189
<v Rachel Green>immediately helping you understand.

378
00:25:28.329 --> 00:25:32.579
<v Rachel Green>And, hey, we're seeing cavitation in the
pump, but it looks like that's being caused

379
00:25:32.579 --> 00:25:37.550
<v Rachel Green>by starvation from this valve, you know,
go check the valve performance.

380
00:25:37.689 --> 00:25:42.729
<v Rachel Green>And those are two very different
maintenance scenarios in terms of execution.

381
00:25:42.849 --> 00:25:48.329
<v Rachel Green>So, being able to create that efficiency
and that confidence with what the data is

382
00:25:48.329 --> 00:25:49.089
<v Rachel Green>being collected.

383
00:25:49.719 --> 00:25:55.479
<v Rachel Green>Context is where we're really going to be
seeing, you know, the effectiveness of

384
00:25:55.479 --> 00:25:56.510
<v Rachel Green>these programs.

385
00:25:56.989 --> 00:26:01.800
<v Rachel Green>And I know that through a lot of
conversations, oftentimes people are like, oh,

386
00:26:01.839 --> 00:26:06.709
<v Rachel Green>we've got thousands of data points, but
it's how do we tie it together?

387
00:26:07.000 --> 00:26:13.160
<v Rachel Green>How do we create a data story that helps
someone that may not want to know about

388
00:26:13.160 --> 00:26:17.880
<v Rachel Green>those algorithms, may not want to know
about the back end of SensIIi or all the

389
00:26:17.880 --> 00:26:18.560
<v Rachel Green>amazing research.

390
00:26:18.645 --> 00:26:19.165
<v Rachel Green>We're doing.

391
00:26:19.484 --> 00:26:23.045
<v Rachel Green>They just want to know what should they do
today with this machine right now, you

392
00:26:23.045 --> 00:26:29.635
<v Rachel Green>know, we need to have confidence built for
them to be wanting to act on what we're

393
00:26:29.635 --> 00:26:36.204
<v Rachel Green>driving for, but we need to be able to do
that by recommending early in the process,

394
00:26:36.244 --> 00:26:38.125
<v Rachel Green>what data should they be collecting.

395
00:26:38.479 --> 00:26:43.319
<v Rachel Green>You know, if we're collecting vibration,
what is the context that goes with that to

396
00:26:43.319 --> 00:26:45.989
<v Rachel Green>make it actionable for their maintenance
teams?

397
00:26:46.359 --> 00:26:50.119
<v Rachel Green>And some of that might be data that's
available today, some of that might be data

398
00:26:50.119 --> 00:26:54.560
<v Rachel Green>that they have to work towards getting in
the future, you know, a phased deployment,

399
00:26:54.920 --> 00:27:01.280
<v Rachel Green>but helping customers create that vision
for what are the different types of failure

400
00:27:01.280 --> 00:27:07.135
<v Rachel Green>modes and how do we You create an amazing
data ecosystem to understand when those

401
00:27:07.135 --> 00:27:10.454
<v Rachel Green>are going to happen and when they do, what
the root cause is.

402
00:27:10.935 --> 00:27:16.655
<v Rachel Green>That's some of the things that Siemens is
really great at in terms of the system

403
00:27:16.655 --> 00:27:20.234
<v Rachel Green>architects that we have here with deep
industry experience.

404
00:27:20.375 --> 00:27:24.655
<v Rachel Green>And it's, you know, you alluded to the
fact that I'm relatively new to Siemens, but

405
00:27:24.655 --> 00:27:26.214
<v Rachel Green>have been doing this for a long time.

406
00:27:26.630 --> 00:27:32.630
<v Rachel Green>The Siemens employees that are creating
those systems architects and using edge

407
00:27:32.630 --> 00:27:38.890
<v Rachel Green>devices and everything else under the sun
to collect that contextual data to create

408
00:27:38.890 --> 00:27:44.709
<v Rachel Green>elegant solutions, that's one of the
things that is Siemens' strengths in terms of

409
00:27:44.709 --> 00:27:49.189
<v Rachel Green>delivering a solution like this because
they have such amazing expertise and such

410
00:27:49.189 --> 00:27:52.630
<v Rachel Green>amazing tech stacks to pull from to drive
that.

411
00:27:53.130 --> 00:27:59.319
<v Rachel Green>That may not be the same answer that
someone on the maintenance technician would

412
00:27:59.319 --> 00:28:03.880
<v Rachel Green>give, but that's the experience that they
should be getting out of this solution

413
00:28:03.880 --> 00:28:05.579
<v Rachel Green>when it's well developed.

414
00:28:05.959 --> 00:28:07.369
<v Niall Sullivan>Uh, absolutely great and.

415
00:28:07.800 --> 00:28:11.640
<v Niall Sullivan>I think one thing that resonated with me
because it has come up so many times, both,

416
00:28:11.719 --> 00:28:16.670
<v Niall Sullivan>you know, many years ago before the
acquisition, but this idea where, you know,

417
00:28:17.150 --> 00:28:20.280
<v Niall Sullivan>questions are asked about, you know, what
AI do you use, what algorithms do you use?

418
00:28:20.359 --> 00:28:23.880
<v Niall Sullivan>Do you have, you know, templated or this
kind of thing, and I, I.

419
00:28:23.964 --> 00:28:27.275
<v Niall Sullivan>I always loved this analogy, that's come
up time and time again, I still use it now,

420
00:28:27.564 --> 00:28:30.805
<v Niall Sullivan>you know, about, you know, when you buy an
iPhone, you don't, you know, how does it

421
00:28:30.805 --> 00:28:31.125
<v Niall Sullivan>work?

422
00:28:31.275 --> 00:28:33.655
<v Niall Sullivan>You know, how does it all, how does that
app pop up?

423
00:28:33.724 --> 00:28:35.444
<v Niall Sullivan>How does this and that work?

424
00:28:35.805 --> 00:28:39.084
<v Niall Sullivan>And to your point, you know, to a
maintenance person, they just want to know what to

425
00:28:39.084 --> 00:28:43.364
<v Niall Sullivan>prioritize and when, how it does it, as
long as the information is correct and it's,

426
00:28:43.604 --> 00:28:47.125
<v Niall Sullivan>you know, and it's a good use of their
time and helping them to work quicker, then

427
00:28:47.125 --> 00:28:48.724
<v Niall Sullivan>how it works in the background is.

428
00:28:49.260 --> 00:28:54.349
<v Niall Sullivan>Yeah, yeah, it, it's less, less important
to them, but, I mean, 11 thing I like

429
00:28:54.349 --> 00:28:59.829
<v Niall Sullivan>about, it, you know, I've seen Sensi
develop over the past 55 or 6 years, but, but

430
00:28:59.829 --> 00:29:03.510
<v Niall Sullivan>now we've got to a point where even we're,
you know, calculating sort of pop, you

431
00:29:03.510 --> 00:29:08.030
<v Niall Sullivan>know, 80% chance it's this or 30%, you
know, and this kind of thing is getting to

432
00:29:08.030 --> 00:29:08.949
<v Niall Sullivan>that sort of stage.

433
00:29:09.069 --> 00:29:10.130
<v Niall Sullivan>Use the word prescriptive.

434
00:29:10.219 --> 00:29:11.849
<v Niall Sullivan>I mean, we're, you know, towards that sort
of time.

435
00:29:11.910 --> 00:29:15.520
<v Niall Sullivan>I remember talking about it not too, too
many years ago, and it's always a fantasy

436
00:29:15.520 --> 00:29:17.089
<v Niall Sullivan>thing to say, but we're actually not.

437
00:29:17.569 --> 00:29:21.689
<v Niall Sullivan>Too far away from, from doing that, I
don't think, you know, I'll be confident in

438
00:29:21.689 --> 00:29:21.849
<v Niall Sullivan>saying.

439
00:29:22.770 --> 00:29:27.969
<v Rachel Green>And, and that's the thing is, you know, I
think we're, we're at this amazing tipping

440
00:29:27.969 --> 00:29:33.890
<v Rachel Green>point where most people are experiencing a
in their daily lives, but the question

441
00:29:33.890 --> 00:29:39.949
<v Rachel Green>is, are you experiencing it as an
unhelpful chatbot that doesn't.

442
00:29:40.510 --> 00:29:42.140
<v Rachel Green>Help you move the needle forward.

443
00:29:42.310 --> 00:29:46.699
<v Rachel Green>I just had that experience trying to book
some travel, you know, and you're like,

444
00:29:46.910 --> 00:29:49.750
<v Rachel Green>this chatbot is not on the same page that
I am.

445
00:29:49.819 --> 00:29:50.790
<v Rachel Green>I really need a human.

446
00:29:50.849 --> 00:29:54.790
<v Rachel Green>It's not, you know, the series of
questions that it's trying to funnel me into

447
00:29:54.790 --> 00:30:00.250
<v Rachel Green>doesn't meet my needs versus, you know,
uh, to your point, I know that my phone has

448
00:30:00.250 --> 00:30:00.949
<v Rachel Green>this technology.

449
00:30:00.989 --> 00:30:03.069
<v Rachel Green>I know that my car has this technology.

450
00:30:03.150 --> 00:30:07.964
<v Rachel Green>I know that, you know, The heating system
for my home has this technology.

451
00:30:08.084 --> 00:30:13.025
<v Rachel Green>Like, there are so many ways that these
solutions are baked into our everyday lives,

452
00:30:13.364 --> 00:30:18.994
<v Rachel Green>and getting this technology into the plant
floor, getting it to benefit the folks

453
00:30:18.994 --> 00:30:24.125
<v Rachel Green>that are doing the maintaining of this
equipment is definitely where we want it to

454
00:30:24.125 --> 00:30:29.800
<v Rachel Green>go, and we want it to be an elegant
solution, so much so that You know, the, the

455
00:30:29.800 --> 00:30:36.079
<v Rachel Green>phrasing of co-pilot, meaning that it
would be a solution that is sitting with them,

456
00:30:36.199 --> 00:30:38.040
<v Rachel Green>doing the work with them, you

457
00:30:38.040 --> 00:30:44.479
<v Rachel Green>know, being co-termed in what their goals
are, is really important to me in making

458
00:30:44.479 --> 00:30:48.599
<v Rachel Green>sure that they feel like it's an equal
partner in getting this done instead of

459
00:30:48.599 --> 00:30:53.959
<v Rachel Green>something that they have to fight with or
have to overly customize, you know, you

460
00:30:53.959 --> 00:30:57.000
<v Rachel Green>just want it to be an elegant solution
that can help you in the moment.

461
00:30:57.520 --> 00:31:02.229
<v Niall Sullivan>Yeah, and I think all of those examples
you gave, and particularly the, the travel

462
00:31:02.229 --> 00:31:06.060
<v Niall Sullivan>example you gave, human interpretation is
still very much important, even in Sensai,

463
00:31:06.069 --> 00:31:10.989
<v Niall Sullivan>an amazing platform or app such as Sensai
requires human interpretation, right?

464
00:31:11.069 --> 00:31:14.790
<v Niall Sullivan>So that's, that's the key, you bring the
two, bringing the two together.

465
00:31:15.290 --> 00:31:15.300
<v Niall Sullivan>Yeah.

466
00:31:15.430 --> 00:31:18.829
<v Niall Sullivan>So, so yeah, so we're we're coming towards
the end, it's the time, time has just

467
00:31:18.829 --> 00:31:19.369
<v Niall Sullivan>flown by.

468
00:31:19.469 --> 00:31:21.010
<v Niall Sullivan>It's been really interesting to chat.

469
00:31:21.189 --> 00:31:24.050
<v Niall Sullivan>I know we had a question, we talked about
this just before recording.

470
00:31:24.380 --> 00:31:29.500
<v Niall Sullivan>And it is the typical ending question of
10 years into the future, 50 years into the

471
00:31:29.500 --> 00:31:33.739
<v Niall Sullivan>future, which is probably about the same
thing at the moment, but, or 5 years into

472
00:31:33.739 --> 00:31:34.439
<v Niall Sullivan>the future, but.

473
00:31:34.930 --> 00:31:39.650
<v Niall Sullivan>Whatever time period we're looking at 10
years, but do, do we see this shift away

474
00:31:39.650 --> 00:31:45.170
<v Niall Sullivan>from the expertise being clustered in a
small number of experts, or do we, are we,

475
00:31:45.280 --> 00:31:49.250
<v Niall Sullivan>are we, do you think it's gonna sort of
widen out with the use of technology and AI

476
00:31:49.250 --> 00:31:50.599
<v Niall Sullivan>and how that develops?

477
00:31:50.810 --> 00:31:54.869
<v Niall Sullivan>It's gonna be more broadly distributed, I
guess, rather than centralized in a small

478
00:31:54.969 --> 00:31:56.390
<v Niall Sullivan>number of experts.

479
00:31:56.849 --> 00:31:57.430
<v Rachel Green>Yeah.

480
00:31:57.770 --> 00:32:02.290
<v Rachel Green>Well, first of all, we did talk about
this, and I just feel like, you know, the last

481
00:32:02.290 --> 00:32:04.109
<v Rachel Green>2 to 5 years have been.

482
00:32:04.829 --> 00:32:09.709
<v Rachel Green>Such an explosion of advancements that I
can't even imagine what's going to happen

483
00:32:09.709 --> 00:32:10.469
<v Rachel Green>in 10 years out.

484
00:32:10.589 --> 00:32:17.589
<v Rachel Green>But if I was making predictions, I do
think 10 years out that we will have less

485
00:32:17.589 --> 00:32:24.069
<v Rachel Green>of a focus on specialist knowledge because
technology and databases and

486
00:32:24.069 --> 00:32:29.010
<v Rachel Green>algorithms will help our generalists get
to specialist confidence.

487
00:32:29.599 --> 00:32:36.359
<v Rachel Green>I do think maintenance is going to be an
area that's harder for, you know, AI

488
00:32:36.359 --> 00:32:43.359
<v Rachel Green>to just try and understand what responses
will be because the inherent place where

489
00:32:43.359 --> 00:32:46.699
<v Rachel Green>you need to do maintenance is where chaos
has taken place.

490
00:32:47.160 --> 00:32:49.819
<v Rachel Green>So, I think, I think we'll get there.

491
00:32:49.989 --> 00:32:54.790
<v Rachel Green>I think it'll be a little slower than
maybe other areas of our daily lives to get

492
00:32:54.790 --> 00:32:57.750
<v Rachel Green>there, but I want to see it get there.

493
00:32:57.869 --> 00:33:03.709
<v Rachel Green>I want to see it make for safer
environments for our workers and for more

494
00:33:03.709 --> 00:33:04.150
<v Rachel Green>predictable.

495
00:33:04.469 --> 00:33:10.729
<v Rachel Green>And to be able to empower workers who
might not have 37 years of experience on

496
00:33:10.729 --> 00:33:11.369
<v Rachel Green>equipment.

497
00:33:11.810 --> 00:33:14.569
<v Rachel Green>Maybe they only have 3 to 5, but they can
still be the hero.

498
00:33:14.650 --> 00:33:19.369
<v Rachel Green>They can still come in and make confident
repairs and replacements and do a great

499
00:33:19.369 --> 00:33:19.839
<v Rachel Green>job.

500
00:33:20.209 --> 00:33:21.290
<v Rachel Green>So, I think we'll get there.

501
00:33:21.410 --> 00:33:26.119
<v Rachel Green>I think it'll be an exciting ride, and I'm
super excited to see what Sensai is

502
00:33:26.119 --> 00:33:29.609
<v Rachel Green>coming up with and how the product
developments will support those goals in the

503
00:33:29.609 --> 00:33:30.050
<v Rachel Green>short term.

504
00:33:30.410 --> 00:33:33.119
<v Niall Sullivan>Fantastic, fantastic, yeah, couldn't agree
more.

505
00:33:33.250 --> 00:33:37.689
<v Niall Sullivan>So yeah, there's, we'll, you know, so I
bet this podcast will be outdated within,

506
00:33:37.849 --> 00:33:43.650
<v Niall Sullivan>within about 6 months, maybe, so that's
what we're saying, or certainly, but, uh,

507
00:33:43.670 --> 00:33:47.079
<v Niall Sullivan>but yeah, it's, yeah, one thing we can
agree on, it's gonna be a very, it's a very

508
00:33:47.079 --> 00:33:50.530
<v Niall Sullivan>exciting time to, and I mean, there's a
lot in this space too.

509
00:33:50.949 --> 00:33:55.239
<v Niall Sullivan>But yes, we've come to the end of our
chat, but it's been really great, Rachel, I

510
00:33:55.239 --> 00:33:55.599
<v Niall Sullivan>must admit.

511
00:33:55.689 --> 00:33:58.579
<v Niall Sullivan>Hopefully we haven't scared you off from
coming on again very soon.

512
00:33:59.079 --> 00:33:59.239
<v Rachel Green>Nope.

513
00:33:59.400 --> 00:34:03.469
<v Rachel Green>Hopefully in less than 10 years' time
frame and we can keep updating what the

514
00:34:03.469 --> 00:34:07.219
<v Rachel Green>outlook looks like because this is such an
incredible changing space.

515
00:34:07.359 --> 00:34:10.699
<v Rachel Green>So, I'll look forward to coming back to
chat about the next topic.

516
00:34:11.179 --> 00:34:15.169
<v Niall Sullivan>Yeah, and yeah, I want to find out more
about your, you know, what you're teaching

517
00:34:15.169 --> 00:34:16.659
<v Niall Sullivan>outside of, outside of Siemens as well.

518
00:34:16.719 --> 00:34:18.860
<v Niall Sullivan>I think that's an interesting topic to
dive into.

519
00:34:19.139 --> 00:34:21.879
<v Niall Sullivan>We've got a bit more time as well, so
we'll definitely do that.

520
00:34:22.300 --> 00:34:22.770
<v Rachel Green>Excellent.

521
00:34:22.989 --> 00:34:23.540
<v Rachel Green>Sounds great.

522
00:34:23.699 --> 00:34:24.100
<v Rachel Green>Thanks, Niall.

523
00:34:24.889 --> 00:34:28.820
<v Niall Sullivan>No, thank you very much and thank you
everyone out there for listening, and we'll

524
00:34:28.820 --> 00:34:29.800
<v Niall Sullivan>see you on the next episode.

525
00:34:30.459 --> 00:34:31.439
<v Niall Sullivan>Thank you for joining us.

526
00:34:35.948 --> 00:34:36.049
<v Speaker 2>Right.

527
00:34:38.139 --> 00:34:41.610
<v Speaker 2>Please like and subscribe on all major
podcast channels.

528
00:34:41.689 --> 00:34:46.610
<v Speaker 2>And to find out more about Sensi
predictive maintenance, go to Siemens.com.
