WEBVTT
Language: en-US

1
00:00:04.000 --> 00:00:08.550
<v Peter O'Hara>The communication from the management, why
they're doing this is particularly these

2
00:00:08.550 --> 00:00:13.039
<v Peter O'Hara>days with AI, you know, a lot of people
are worried that AI is going to take over

3
00:00:13.039 --> 00:00:16.639
<v Peter O'Hara>their jobs, but I've yet to see AI hold a
spanner.

4
00:00:16.930 --> 00:00:18.809
<v Speaker 2>Welcome to the trend detection podcast.

5
00:00:19.120 --> 00:00:20.409
<v Speaker 2>Powered by Siemens.

6
00:00:20.559 --> 00:00:20.959
<v Speaker 2>Hello

7
00:00:20.959 --> 00:00:24.600
<v Speaker 3>and welcome to the latest episode of the
Trend detection podcast.

8
00:00:24.959 --> 00:00:29.950
<v Speaker 3>I'm really pleased to be joined again by
Peter O'Hara from our customer success team

9
00:00:29.950 --> 00:00:30.659
<v Speaker 3>at Sensai.

10
00:00:30.750 --> 00:00:31.469
<v Speaker 3>How are you, Pete?

11
00:00:31.799 --> 00:00:33.279
<v Peter O'Hara>I'm very good, thank you, buddy.

12
00:00:33.340 --> 00:00:33.840
<v Peter O'Hara>How are you?

13
00:00:34.700 --> 00:00:36.220
<v Speaker 3>Very good, very good, thank you.

14
00:00:36.419 --> 00:00:39.099
<v Speaker 3>Been a busy period for recording,
recording podcasts actually.

15
00:00:39.220 --> 00:00:40.029
<v Speaker 3>This will go out.

16
00:00:40.500 --> 00:00:43.849
<v Speaker 3>I'm on holiday in early September, so I'm
really pushing through the topics at the

17
00:00:43.849 --> 00:00:46.380
<v Speaker 3>moment, so looking forward to another
great conversation though.

18
00:00:46.419 --> 00:00:50.930
<v Speaker 3>We're, we're talking today about scale,
that favorite word of ours that we've been

19
00:00:50.930 --> 00:00:56.340
<v Speaker 3>using for a number of years, but more
specifically about how we roll out PDF across

20
00:00:56.340 --> 00:00:57.020
<v Speaker 3>all sites.

21
00:00:57.470 --> 00:01:02.069
<v Speaker 3>Because this episode actually you came to
me with some real life questions from a

22
00:01:02.069 --> 00:01:06.440
<v Speaker 3>customer, which, you know, translates
perfectly to our podcast format, and this, and

23
00:01:06.440 --> 00:01:09.669
<v Speaker 3>this was one of them, and I thought it was
a really interesting one to start with.

24
00:01:10.230 --> 00:01:13.589
<v Speaker 3>So just to get your, your thoughts on it
first of all, you know, how, how have you

25
00:01:13.589 --> 00:01:18.660
<v Speaker 3>seen sort of the scaling of PDM sort of
across your time and with Sensai, Pete?

26
00:01:18.910 --> 00:01:19.889
<v Speaker 3>How has it changed?

27
00:01:21.050 --> 00:01:27.940
<v Peter O'Hara>I think, I think one of the, the key
changes from the, the world

28
00:01:27.940 --> 00:01:34.000
<v Peter O'Hara>of Sensi was when we were acquired by
Siemens, and then that allows us

29
00:01:34.459 --> 00:01:40.730
<v Peter O'Hara>the conversations perhaps at a, a broader
level with customers who want to scale.

30
00:01:41.260 --> 00:01:47.050
<v Peter O'Hara>We still see some people wanting to, you
know, prove the technology, as they say,

31
00:01:47.059 --> 00:01:48.639
<v Peter O'Hara>and start off with a pilot, which.

32
00:01:49.919 --> 00:01:56.599
<v Peter O'Hara>We're a little bit against because from
the previous podcasts, if you want to try

33
00:01:56.599 --> 00:02:01.980
<v Peter O'Hara>this out on 10 machines, then what's the
likelihood of it being interesting to

34
00:02:02.559 --> 00:02:02.959
<v Peter O'Hara>anybody.

35
00:02:03.480 --> 00:02:10.119
<v Peter O'Hara>So it's nice when we have customers who
say, yeah, I'm like the idea, we want

36
00:02:10.119 --> 00:02:15.919
<v Peter O'Hara>to run with it, and then they commit and
they provide enough human resources and

37
00:02:15.919 --> 00:02:16.440
<v Peter O'Hara>the.

38
00:02:17.119 --> 00:02:21.990
<v Peter O'Hara>ITOT infrastructure and all of that sort
of stuff to actually do it at a reasonable

39
00:02:21.990 --> 00:02:25.259
<v Peter O'Hara>pace, so yeah, it's exciting when
customers are like that.

40
00:02:26.220 --> 00:02:29.779
<v Speaker 3>Yeah, well, they're, they're almost more,
more eager than us to scale, right?

41
00:02:29.860 --> 00:02:32.970
<v Speaker 3>I guess maybe that situation happens from
time to time.

42
00:02:33.020 --> 00:02:36.649
<v Speaker 3>It's like, no, you know, may, you know,
before some of the groundwork's put in

43
00:02:36.649 --> 00:02:40.130
<v Speaker 3>place, they're, they're already looking
further ahead, which, which is obviously a

44
00:02:40.130 --> 00:02:40.460
<v Speaker 3>positive,

45
00:02:40.580 --> 00:02:40.779
<v Peter O'Hara>right?

46
00:02:41.020 --> 00:02:45.789
<v Peter O'Hara>Yeah, I think, yeah, having a customer who
has a plan of, right, let's roll out

47
00:02:45.789 --> 00:02:50.119
<v Peter O'Hara>across, you know, 10 number of factories
this year, then.

48
00:02:50.729 --> 00:02:56.699
<v Peter O'Hara>That is good because if, if it's a case of
well we'll roll out this factory and then

49
00:02:57.279 --> 00:03:01.800
<v Peter O'Hara>we will wait a year and try and get the
budget to do the next one and that sort of

50
00:03:01.800 --> 00:03:02.940
<v Peter O'Hara>thing, you're always.

51
00:03:04.070 --> 00:03:08.029
<v Peter O'Hara>How can I say this politely, it's the same
amount of work from my point of view, but

52
00:03:08.029 --> 00:03:12.949
<v Peter O'Hara>it's, you're not sure what the outcome's
going to be, whereas you can get a bit of

53
00:03:12.949 --> 00:03:18.309
<v Peter O'Hara>momentum if you roll out across site in,
say, 3 months and then.

54
00:03:19.089 --> 00:03:20.949
<v Peter O'Hara>You can move to the next site and the.

55
00:03:21.720 --> 00:03:26.630
<v Peter O'Hara>You know, there's a similar team of people
with the similar ambition and there's a

56
00:03:26.630 --> 00:03:33.559
<v Peter O'Hara>little bit of enthusiasm to get things
moving, that is much better than being

57
00:03:33.559 --> 00:03:38.820
<v Peter O'Hara>the other way where it's like, right, OK,
we've got these 10 machines and then

58
00:03:39.679 --> 00:03:44.740
<v Peter O'Hara>people are less engaged because the 10
machines aren't failing because out of, you

59
00:03:44.759 --> 00:03:49.119
<v Peter O'Hara>know, in a space of 3 months, probably 0
of them will fail.

60
00:03:49.580 --> 00:03:56.199
<v Peter O'Hara>And the PDM people who should be using
SenseI are out fighting their usual

61
00:03:56.199 --> 00:04:02.419
<v Peter O'Hara>fires, and so it's harder to show, I
suppose, yeah, we use the term success, what

62
00:04:02.419 --> 00:04:02.919
<v Peter O'Hara>does that mean?

63
00:04:03.020 --> 00:04:08.360
<v Peter O'Hara>But you know, it's hard to show success
when there's nothing actually going wrong to

64
00:04:08.740 --> 00:04:13.020
<v Peter O'Hara>prove yourself on, whereas doing it at
scale, as I always say, Sei's brilliant at

65
00:04:13.020 --> 00:04:16.380
<v Peter O'Hara>scale because it's not about everything
you look at, it's about everything you don't

66
00:04:16.380 --> 00:04:16.989
<v Peter O'Hara>need to look at.

67
00:04:17.678 --> 00:04:19.128
<v Peter O'Hara>Mhm it's being monitored.

68
00:04:19.449 --> 00:04:23.169
<v Speaker 3>And uh, I guess the first question I'd
ask, when you, when we have such

69
00:04:23.169 --> 00:04:27.639
<v Speaker 3>enthusiastic, when we do have enthusiastic
customers looking to, you know, at scale

70
00:04:27.639 --> 00:04:32.648
<v Speaker 3>very early on, I mean, do they, do they
realize exactly what's required to do that

71
00:04:32.648 --> 00:04:36.109
<v Speaker 3>and what they're taking on internally as
you mentioned, you know, quite rightly

72
00:04:36.109 --> 00:04:39.609
<v Speaker 3>about some of the, you know, some of the
factors in place and maybe some of the

73
00:04:39.609 --> 00:04:43.049
<v Speaker 3>things that need to be in place, but do
they sort of realize at this stage what it

74
00:04:43.049 --> 00:04:44.968
<v Speaker 3>takes to, to scale?

75
00:04:45.890 --> 00:04:52.839
<v Peter O'Hara>Hopefully we can tell them, but yeah, we
do have customers who don't listen to our

76
00:04:52.839 --> 00:04:59.769
<v Peter O'Hara>advice and our previous experiences, but
usually someone who's

77
00:04:59.769 --> 00:05:02.369
<v Peter O'Hara>enthusiastic to run with it.

78
00:05:03.190 --> 00:05:06.149
<v Peter O'Hara>Then It's easier to.

79
00:05:07.059 --> 00:05:13.239
<v Peter O'Hara>Maybe I say, slow them down a little bit
more than someone who just wants to start

80
00:05:13.239 --> 00:05:19.910
<v Peter O'Hara>slowly and then prove in every area, when
like I say, they're probably not

81
00:05:19.910 --> 00:05:25.440
<v Peter O'Hara>monitoring enough equipment to make it,
you know, a good investment for, you know,

82
00:05:25.559 --> 00:05:29.519
<v Peter O'Hara>to see return on investment when you're
only monitoring 10 things and then they're

83
00:05:29.519 --> 00:05:34.679
<v Peter O'Hara>not failing, then you've got the cost of
the people and Sensai and whatnot looking

84
00:05:34.679 --> 00:05:37.040
<v Peter O'Hara>at things that aren't failing, whereas if
you do it at

85
00:05:37.040 --> 00:05:37.459
<v Peter O'Hara>scale.

86
00:05:38.130 --> 00:05:43.910
<v Peter O'Hara>You will usually capture things fairly
quickly that are in the, in a failure mode,

87
00:05:44.049 --> 00:05:45.649
<v Peter O'Hara>and then that's.

88
00:05:46.390 --> 00:05:53.190
<v Peter O'Hara>When customers Can see like oh this has
picked up X or Y, then they are

89
00:05:53.190 --> 00:05:58.329
<v Peter O'Hara>more engaged to, you know, to roll it out
elsewhere, is what I find.

90
00:05:58.869 --> 00:05:59.190
<v Peter O'Hara>And,

91
00:05:59.390 --> 00:06:03.869
<v Speaker 3>and in terms of, you know, so I guess I'm
just thinking the differences between sort

92
00:06:03.869 --> 00:06:06.869
<v Speaker 3>of rolling out PDM from one site to
multiple sites.

93
00:06:06.910 --> 00:06:10.670
<v Speaker 3>I mean, what, what sort of gets harder as,
you know, thinking starts to go beyond

94
00:06:10.670 --> 00:06:12.489
<v Speaker 3>that first, that first site.

95
00:06:13.470 --> 00:06:14.190
<v Peter O'Hara>I think.

96
00:06:15.269 --> 00:06:20.950
<v Peter O'Hara>One of the areas, and it's one of the
things I've said in numerous other podcasts

97
00:06:20.950 --> 00:06:24.940
<v Peter O'Hara>about cookie cuttering, the solution is
that if the.

98
00:06:26.089 --> 00:06:31.070
<v Peter O'Hara>Further sites don't have the same issues,
then sometimes a cookie cutter approach

99
00:06:31.450 --> 00:06:37.250
<v Peter O'Hara>will not have the same effects, and I have
been even like around different shops

100
00:06:37.250 --> 00:06:41.029
<v Peter O'Hara>within a facility and people say, well,
they're.

101
00:06:41.980 --> 00:06:45.630
<v Peter O'Hara>Telling us we've got to roll out sensor,
but we don't have those problems, and

102
00:06:45.630 --> 00:06:48.230
<v Peter O'Hara>you're like, OK, so what problems do you
have?

103
00:06:48.709 --> 00:06:52.790
<v Peter O'Hara>And in one of the previous ones I was
saying about someone who, saying we don't have

104
00:06:52.790 --> 00:06:56.190
<v Peter O'Hara>a downtime problem, and then we're looking
at his equipment and we're like, well,

105
00:06:56.230 --> 00:07:00.609
<v Peter O'Hara>yeah, we, we replace these motors every 6
months because we once had a failure after

106
00:07:00.609 --> 00:07:05.829
<v Peter O'Hara>7 months, and it's like, OK, well maybe we
should look at monitoring those and

107
00:07:05.829 --> 00:07:11.119
<v Peter O'Hara>pushing that window, and then if we can
see, you know, degradation in the data.

108
00:07:11.769 --> 00:07:15.649
<v Peter O'Hara>Prior to when you're changing them out and
you change them out and the data returns

109
00:07:15.649 --> 00:07:17.549
<v Peter O'Hara>to normal, then perfect.

110
00:07:17.890 --> 00:07:24.049
<v Peter O'Hara>If, however, there's no degradation in the
data, well maybe we can push the, you

111
00:07:24.049 --> 00:07:27.119
<v Peter O'Hara>know, the life expectancy of these motors
and increase that.

112
00:07:27.529 --> 00:07:29.329
<v Peter O'Hara>So again, I'm not saying.

113
00:07:30.429 --> 00:07:33.190
<v Peter O'Hara>Don't do all your usual maintenance
strategies.

114
00:07:34.420 --> 00:07:38.510
<v Peter O'Hara>Just because you're now monitoring the
sense side, but it's a way of trying to, you

115
00:07:38.510 --> 00:07:42.890
<v Peter O'Hara>know, hopefully adapt and improve the
maintenance strategies to make them more cost

116
00:07:42.890 --> 00:07:47.850
<v Peter O'Hara>effective and by not replacing parts that
don't need to be replaced, you can save an

117
00:07:47.850 --> 00:07:48.709
<v Peter O'Hara>awful lot of money.

118
00:07:49.290 --> 00:07:52.890
<v Speaker 3>And it's really interesting because I do
remember we, probably on the last podcast

119
00:07:52.890 --> 00:07:56.399
<v Speaker 3>we did together, you, you talked about the
cookie cutter approach and, and you know,

120
00:07:56.529 --> 00:07:59.970
<v Speaker 3>you know, in marketing we talk about, you
know, scale, but of course different sites

121
00:07:59.970 --> 00:08:03.369
<v Speaker 3>can have different approaches, different
system architectures, different.

122
00:08:04.059 --> 00:08:06.269
<v Speaker 3>Processes you can't, you can't sort of
never presume.

123
00:08:06.350 --> 00:08:09.589
<v Speaker 3>So how, you know, if we're talking about,
and we talk about champions a lot, I mean

124
00:08:09.589 --> 00:08:14.149
<v Speaker 3>we've talked about that, and the
importance of like one, let's say global, or maybe

125
00:08:14.149 --> 00:08:19.190
<v Speaker 3>more than one global champion, but how do
they, how do they sort of navigate, you

126
00:08:19.190 --> 00:08:22.579
<v Speaker 3>know, that trying to roll it out when,
like I said, different types of different,

127
00:08:22.750 --> 00:08:26.070
<v Speaker 3>completely different situations, different
KPIs, different success criteria and that

128
00:08:26.070 --> 00:08:26.309
<v Speaker 3>kind of thing.

129
00:08:26.429 --> 00:08:26.720
<v Speaker 3>Yeah,

130
00:08:27.140 --> 00:08:27.549
<v Peter O'Hara>so I

131
00:08:27.549 --> 00:08:28.089
<v Speaker 3>think.

132
00:08:28.700 --> 00:08:34.130
<v Peter O'Hara>So we've got some customers and they have
completely different IT infrastructures in

133
00:08:34.130 --> 00:08:40.940
<v Peter O'Hara>every site, and so, when you say roll out
site to site, then they may

134
00:08:40.940 --> 00:08:44.380
<v Peter O'Hara>even have the same sort of machines, but
if they have different.

135
00:08:45.450 --> 00:08:50.330
<v Peter O'Hara>There are equipment providers around the
world in different IT then we may not be

136
00:08:50.330 --> 00:08:55.650
<v Peter O'Hara>able to use exactly the same approach to
get data from their site, whereas we have

137
00:08:55.650 --> 00:08:59.219
<v Peter O'Hara>other customers and they've got the same
IT infrastructure all over the place and

138
00:08:59.219 --> 00:09:04.330
<v Peter O'Hara>then it is almost as simple as just
hooking up the next section.

139
00:09:04.739 --> 00:09:08.229
<v Peter O'Hara>So, but I think with.

140
00:09:09.239 --> 00:09:10.590
<v Peter O'Hara>Both situations.

141
00:09:11.299 --> 00:09:14.130
<v Peter O'Hara>You know, stakeholder engagement is going
to be critical.

142
00:09:14.320 --> 00:09:18.859
<v Peter O'Hara>The communication from the management, why
they're doing this is particularly these

143
00:09:18.859 --> 00:09:23.340
<v Peter O'Hara>days with AI, you know, a lot of people
are worried that AI is going to take over

144
00:09:23.340 --> 00:09:29.419
<v Peter O'Hara>their jobs, but I've yet to see AI hold a
spanner, so I think it can improve the

145
00:09:29.419 --> 00:09:34.659
<v Peter O'Hara>maintainer's efficiency because we're
removing some of the the routine checks and

146
00:09:34.659 --> 00:09:39.539
<v Peter O'Hara>the things that they don't need to do,
whereas AI can do that at scale, but then.

147
00:09:40.289 --> 00:09:46.010
<v Peter O'Hara>They're just, we're making their job more
efficient and effective, but this isn't

148
00:09:46.010 --> 00:09:47.450
<v Peter O'Hara>going to be replacing people.

149
00:09:48.400 --> 00:09:50.359
<v Peter O'Hara>I think, like I say.

150
00:09:51.229 --> 00:09:56.630
<v Peter O'Hara>Capturing lessons learned from one site to
the next is important, but I would also

151
00:09:56.630 --> 00:09:58.849
<v Peter O'Hara>ask customers when.

152
00:09:59.630 --> 00:10:05.469
<v Peter O'Hara>They engage with us to listen to some of
our advice about certain things, and we

153
00:10:05.469 --> 00:10:09.030
<v Peter O'Hara>have customers who have completely
different.

154
00:10:10.020 --> 00:10:15.210
<v Peter O'Hara>Like sensing setups, um, way of users
engaging with the system in one country

155
00:10:15.210 --> 00:10:21.619
<v Peter O'Hara>compared to the other, and then they're
asking why the, the results are varying.

156
00:10:21.690 --> 00:10:28.239
<v Peter O'Hara>Well, I've got one customer who in one
part of the world, they have people, they pay

157
00:10:28.450 --> 00:10:31.859
<v Peter O'Hara>Siemens to actively monitor Sensi and to
tell their.

158
00:10:32.429 --> 00:10:37.229
<v Peter O'Hara>Maintainers, what is going wrong and what
to do about it, and then in another part

159
00:10:37.229 --> 00:10:41.340
<v Peter O'Hara>of the world, they don't have the sensing
technology to allow that.

160
00:10:41.789 --> 00:10:47.510
<v Peter O'Hara>They bought their, you know, they didn't
go through the sensing technology that we

161
00:10:47.510 --> 00:10:53.190
<v Peter O'Hara>had recommended, but they've got good
sensors for PDM but not that, not to be able

162
00:10:53.190 --> 00:10:57.570
<v Peter O'Hara>to provide that kind of remote service
level of support, because we can say.

163
00:10:58.510 --> 00:11:03.510
<v Peter O'Hara>This vibration is increasing, but we don't
have the level of data coming in to say

164
00:11:03.979 --> 00:11:07.369
<v Peter O'Hara>which part of the machine and, you know,
what they need to do about it.

165
00:11:07.820 --> 00:11:13.320
<v Peter O'Hara>So you can't compare the results from one
site to the results from another site, but

166
00:11:13.940 --> 00:11:19.020
<v Peter O'Hara>you can look at operating in slightly
different ways and still getting good success

167
00:11:19.020 --> 00:11:21.500
<v Peter O'Hara>from both sites, you just, it's harder to
compare them.

168
00:11:22.869 --> 00:11:26.619
<v Speaker 3>And, and I think, I mean, I, I've got a
great example from the other day.

169
00:11:26.659 --> 00:11:29.859
<v Speaker 3>I can actually say it's because the
podcast's just been approved, but our customer

170
00:11:29.859 --> 00:11:34.869
<v Speaker 3>Highland Peelets I spoke to, uh, I
interviewed for this very podcast, and that one

171
00:11:34.869 --> 00:11:39.349
<v Speaker 3>thing that sort of stood out to me is how
Sensi's enabled sort of increased

172
00:11:39.349 --> 00:11:39.900
<v Speaker 3>collaboration.

173
00:11:40.109 --> 00:11:45.909
<v Speaker 3>I know we're not talking about big
rollout, but even through the various teams

174
00:11:45.909 --> 00:11:50.530
<v Speaker 3>reliability operations and things like
that, and it, and it makes me.

175
00:11:51.239 --> 00:11:55.049
<v Speaker 3>You know, wonder both on a site view, but
also a global view.

176
00:11:55.250 --> 00:11:58.890
<v Speaker 3>I mean, how do you balance that sort of,
you know, giving people sort of global

177
00:11:58.890 --> 00:12:01.530
<v Speaker 3>access, because that's a lot of knowledge
and a lot of sharing of knowledge, I think

178
00:12:01.530 --> 00:12:06.000
<v Speaker 3>you mentioned as well, versus, you know,
what should be contained within one site.

179
00:12:06.250 --> 00:12:09.789
<v Speaker 3>I don't know if it, it's probably an
approach different customer to customer, right,

180
00:12:09.849 --> 00:12:13.289
<v Speaker 3>in terms of when they think about scale,
but, you know, you know, how is, how is

181
00:12:13.289 --> 00:12:14.590
<v Speaker 3>that generally balanced?

182
00:12:14.820 --> 00:12:14.830
<v Speaker 3>Uh,

183
00:12:15.570 --> 00:12:19.690
<v Peter O'Hara>yeah, I, I suppose the, in the Sensi
world.

184
00:12:20.719 --> 00:12:27.559
<v Peter O'Hara>We believe that sharing knowledge is a
good thing and we are against, particularly

185
00:12:27.559 --> 00:12:28.780
<v Peter O'Hara>knowledge silos.

186
00:12:29.080 --> 00:12:33.440
<v Peter O'Hara>There are some customers out there who
for.

187
00:12:34.200 --> 00:12:38.280
<v Peter O'Hara>Reasons that I still don't understand,
will not want one site being able to see what

188
00:12:38.280 --> 00:12:40.650
<v Peter O'Hara>another site is doing, and.

189
00:12:42.039 --> 00:12:46.710
<v Peter O'Hara>For me, surely you want to share best
practices, and I would suggest our best

190
00:12:46.710 --> 00:12:53.559
<v Peter O'Hara>customers are the ones who openly share
best practice and if a, a

191
00:12:53.559 --> 00:12:59.380
<v Peter O'Hara>site is monitoring something and they want
to bring their similar version online,

192
00:12:59.719 --> 00:13:02.799
<v Peter O'Hara>the best place to do is to look at the
other site and what are they doing, what

193
00:13:02.799 --> 00:13:07.059
<v Peter O'Hara>results are they getting, and what would
we do in our situation.

194
00:13:07.159 --> 00:13:09.380
<v Peter O'Hara>So I'm, I'm more.

195
00:13:10.059 --> 00:13:16.039
<v Peter O'Hara>Open to the standard Sensii way is you
have one customer instance per, well,

196
00:13:16.179 --> 00:13:20.880
<v Peter O'Hara>customer I suppose, and then you break it
down to the different installations.

197
00:13:21.859 --> 00:13:24.359
<v Peter O'Hara>And then from that we have.

198
00:13:25.450 --> 00:13:32.289
<v Peter O'Hara>Everybody who can access the application
can see everywhere, but the, the, the right

199
00:13:32.289 --> 00:13:35.599
<v Peter O'Hara>access is controlled to only their area of
operation.

200
00:13:36.130 --> 00:13:41.049
<v Peter O'Hara>So, you can have someone from one country
looking at how another country's doing

201
00:13:41.049 --> 00:13:45.010
<v Peter O'Hara>stuff, you, they can search for, but I
wonder if they've got this asset type in

202
00:13:45.010 --> 00:13:49.869
<v Peter O'Hara>there and then they can see, OK, this
asset type, what are they measuring, and

203
00:13:50.090 --> 00:13:52.260
<v Peter O'Hara>again, you can look and see what.

204
00:13:52.929 --> 00:13:54.450
<v Peter O'Hara>Success KPIs, etc.

205
00:13:54.929 --> 00:13:58.150
<v Peter O'Hara>that they've entered there, so I think
transparency.

206
00:13:59.289 --> 00:14:04.929
<v Peter O'Hara>Is a good thing from the customer's point
of view because it shares knowledge and

207
00:14:04.929 --> 00:14:11.909
<v Peter O'Hara>learning, and then from a sensei point of
view, it's so much better if

208
00:14:12.849 --> 00:14:17.969
<v Peter O'Hara>customer sites get a little bit
competitive with each other because then they, they

209
00:14:17.969 --> 00:14:21.890
<v Peter O'Hara>will, you know, try to be the site that.

210
00:14:22.309 --> 00:14:27.780
<v Peter O'Hara>Adds the more machines or has recorded the
most particular KPIs and that sort of

211
00:14:27.780 --> 00:14:32.349
<v Peter O'Hara>thing, and that's, if you can gamify it a
little bit like that, then it's good from

212
00:14:32.349 --> 00:14:38.549
<v Peter O'Hara>a sensei point of view, and I would
suggest if the customers are using the system to

213
00:14:38.549 --> 00:14:41.489
<v Peter O'Hara>its fullest capacity, it's good for them
as well.

214
00:14:42.619 --> 00:14:45.739
<v Speaker 3>Yeah, that's, yeah, it's interesting, the
internal competition, it's always, it's

215
00:14:45.739 --> 00:14:48.190
<v Speaker 3>always gonna be there though, it's just
human nature, isn't it?

216
00:14:48.380 --> 00:14:50.440
<v Speaker 3>Of course, cos everyone wants to be
successful.

217
00:14:50.619 --> 00:14:54.020
<v Speaker 3>I look, I know you, I know you talked
about it before in terms of, we talked about

218
00:14:54.020 --> 00:14:58.770
<v Speaker 3>cookie cutter and it's very difficult to
do that, but I guess the lesson here is,

219
00:14:58.940 --> 00:15:02.179
<v Speaker 3>you know, it, you know, it's very
difficult to standardize, but you can certainly

220
00:15:02.179 --> 00:15:02.700
<v Speaker 3>learn.

221
00:15:03.119 --> 00:15:03.130
<v Speaker 3>Yeah.

222
00:15:04.039 --> 00:15:07.330
<v Speaker 3>Right, in terms of what, what was
successful for you, what was maybe not, and then

223
00:15:07.330 --> 00:15:10.510
<v Speaker 3>it's maybe adapting that thinking to that
particular site.

224
00:15:10.630 --> 00:15:14.109
<v Speaker 3>It's maybe the better approach rather than
thinking, oh, they've done a great job,

225
00:15:14.190 --> 00:15:18.530
<v Speaker 3>let's just copy it, the blueprint,
exactly, and, and go again.

226
00:15:19.030 --> 00:15:24.549
<v Peter O'Hara>Cos if you're trying to, if you don't have
the same problem as the first site, for

227
00:15:24.549 --> 00:15:30.229
<v Peter O'Hara>example, then you might have newer
machines, whereas the, the first site has taken

228
00:15:30.229 --> 00:15:32.750
<v Peter O'Hara>on PDM because they've got a reliability
problem.

229
00:15:33.400 --> 00:15:38.539
<v Peter O'Hara>Well if you've got a lot of brand new
machines, then maybe you've got, you know, a,

230
00:15:38.669 --> 00:15:43.400
<v Peter O'Hara>a spares capacity problem or something
like that, so, just monitoring the same thing

231
00:15:43.400 --> 00:15:46.780
<v Peter O'Hara>and expecting the same results, you know,
you're not going to.

232
00:15:47.460 --> 00:15:49.580
<v Peter O'Hara>Reduce downtime if you don't have a
downtime problem.

233
00:15:50.330 --> 00:15:53.530
<v Peter O'Hara>But if you've got an over maintenance
problem, you can reduce your maintenance costs

234
00:15:53.530 --> 00:15:56.400
<v Peter O'Hara>or your spares costs or you know that sort
of thing.

235
00:15:56.770 --> 00:16:02.710
<v Peter O'Hara>So that, that's the only thing I would
say, like I say, about the cookie cutter is

236
00:16:03.289 --> 00:16:04.450
<v Peter O'Hara>you just have to.

237
00:16:05.309 --> 00:16:11.169
<v Peter O'Hara>Two things really, make sure you're trying
to solve a problem that exists and.

238
00:16:12.090 --> 00:16:17.049
<v Peter O'Hara>Make sure that the people who are engaged,
well hopefully people are engaged on the

239
00:16:17.049 --> 00:16:22.409
<v Peter O'Hara>site, but people at the site, you know,
want to solve this problem with you, you

240
00:16:22.409 --> 00:16:27.289
<v Peter O'Hara>know, the, the engagement of those people,
if they, sometimes, depending on the

241
00:16:27.289 --> 00:16:30.700
<v Peter O'Hara>company culture, if they see it as
something being forced on them by head office,

242
00:16:31.250 --> 00:16:32.549
<v Peter O'Hara>there's gonna be resistance.

243
00:16:33.130 --> 00:16:37.289
<v Peter O'Hara>And then, you know, part of my job is to
try and overcome that resistance, try and

244
00:16:37.289 --> 00:16:40.510
<v Peter O'Hara>get them to see what a good thing it is,
but if.

245
00:16:41.390 --> 00:16:43.190
<v Peter O'Hara>The, the management.

246
00:16:44.159 --> 00:16:46.539
<v Peter O'Hara>Don't, you know, the local management
don't celebrate.

247
00:16:47.530 --> 00:16:54.419
<v Peter O'Hara>The success of a sense I Win, if, if
people are, you have a downtime avoided

248
00:16:54.419 --> 00:17:01.419
<v Peter O'Hara>or production materials saved or whatever,
and people don't want to celebrate

249
00:17:01.419 --> 00:17:04.479
<v Peter O'Hara>that, then it's going to be harder for.

250
00:17:05.359 --> 00:17:09.250
<v Peter O'Hara>Someone like, or, you know, people using
Sensei to feel that, OK, there's a benefit

251
00:17:09.250 --> 00:17:15.489
<v Peter O'Hara>of doing this because, especially if
they're being pulled into lots of different

252
00:17:15.489 --> 00:17:19.209
<v Peter O'Hara>directions, if you've got quite a small
deployment and like I say, things are

253
00:17:19.209 --> 00:17:24.849
<v Peter O'Hara>failing elsewhere and the, the bits that
you've got Sensi running on are the newer

254
00:17:24.849 --> 00:17:30.770
<v Peter O'Hara>bits because they have the, the readings
available, then people's attention might

255
00:17:30.770 --> 00:17:31.430
<v Peter O'Hara>not be.

256
00:17:32.459 --> 00:17:36.739
<v Peter O'Hara>Put on, you know, the sense I world,
they're going to be fighting the fires that

257
00:17:36.739 --> 00:17:41.180
<v Peter O'Hara>they've, they always have done, so you
need often, you know, it's a process

258
00:17:41.180 --> 00:17:47.660
<v Peter O'Hara>management a change, I suppose that you're
putting in a new system and you want it

259
00:17:47.660 --> 00:17:51.339
<v Peter O'Hara>to complement their existing workflow.

260
00:17:52.140 --> 00:17:58.130
<v Peter O'Hara>But also you've got to appreciate that if
that existing workflow is already

261
00:17:59.189 --> 00:17:59.869
<v Peter O'Hara>working at.

262
00:18:00.739 --> 00:18:06.880
<v Peter O'Hara>110, 20%, then fitting something on top of
that is going to cause friction.

263
00:18:07.500 --> 00:18:09.439
<v Peter O'Hara>Hm No.

264
00:18:12.650 --> 00:18:15.310
<v Speaker 3>No, no, that makes, that, that makes a lot
of sense as well.

265
00:18:15.550 --> 00:18:18.989
<v Speaker 3>I mean, I'm also, I guess the other thing
to consider because we've talked about,

266
00:18:19.069 --> 00:18:22.410
<v Speaker 3>we've gone straight to sort of scale, or
I've gone straight to scale, but actually

267
00:18:22.550 --> 00:18:26.219
<v Speaker 3>what I was also thinking is what, where, I
mean, which site do you start with as

268
00:18:26.219 --> 00:18:26.329
<v Speaker 3>well?

269
00:18:26.430 --> 00:18:28.260
<v Speaker 3>How's that sort of determined?

270
00:18:28.390 --> 00:18:32.300
<v Speaker 3>Because I guess that's quite important,
isn't it, to lay, I mean, maybe the, the

271
00:18:32.300 --> 00:18:33.609
<v Speaker 3>answer is it's whichever.

272
00:18:34.219 --> 00:18:37.959
<v Speaker 3>I mean, is it more of a customer led
decision or is it more, you know, do we have

273
00:18:37.959 --> 00:18:40.260
<v Speaker 3>input into that, you know, how does that
work?

274
00:18:40.780 --> 00:18:47.420
<v Peter O'Hara>Yeah, I imagine it's partly customer led
and partly the region

275
00:18:47.420 --> 00:18:51.500
<v Peter O'Hara>selling the solution led because they'll
probably try and get.

276
00:18:52.489 --> 00:18:56.670
<v Peter O'Hara>You know, they will be engaging with the,
whatever local team that is.

277
00:18:57.329 --> 00:18:57.689
<v Peter O'Hara>So.

278
00:18:58.479 --> 00:19:04.760
<v Peter O'Hara>Yeah, I think when we, when we start to,
right, the initial sales process.

279
00:19:05.930 --> 00:19:09.949
<v Peter O'Hara>They'll be engaging, you know, the people
in their region, and so.

280
00:19:10.719 --> 00:19:17.390
<v Peter O'Hara>Again, I kind of believe that it will work
better if the solution is rolled

281
00:19:17.390 --> 00:19:23.089
<v Peter O'Hara>out in that area, in that region, because
you have Bighton, and like I say, the

282
00:19:23.089 --> 00:19:23.650
<v Peter O'Hara>thing you.

283
00:19:24.910 --> 00:19:30.819
<v Peter O'Hara>I would like to avoid is sense I'm being
forced on people because.

284
00:19:31.939 --> 00:19:36.060
<v Peter O'Hara>Certain people buy our solution, but they
don't actually use it.

285
00:19:37.030 --> 00:19:39.989
<v Peter O'Hara>People who use it are the, the maintainers
and.

286
00:19:40.619 --> 00:19:44.459
<v Peter O'Hara>The, you know, maybe the project engineers
or whomever at the different sites who

287
00:19:44.459 --> 00:19:45.479
<v Peter O'Hara>are rolling this out.

288
00:19:46.810 --> 00:19:53.489
<v Peter O'Hara>So The people who will make it a success
are the people at the site, and if it's

289
00:19:53.489 --> 00:19:57.390
<v Peter O'Hara>a somebody at head office thinking this is
a great idea, I'm sold on it, right,

290
00:19:57.890 --> 00:20:04.489
<v Peter O'Hara>you're gonna use it and those people don't
want to, then the project

291
00:20:04.489 --> 00:20:11.369
<v Peter O'Hara>will struggle for, you know, momentum, I
think, so yeah, I, I

292
00:20:11.369 --> 00:20:16.609
<v Peter O'Hara>think definitely customer led, but local
buy-in, you really

293
00:20:16.609 --> 00:20:17.010
<v Peter O'Hara>need.

294
00:20:18.089 --> 00:20:24.489
<v Peter O'Hara>Somebody who Understands the vision of PDM
wants to.

295
00:20:25.500 --> 00:20:31.599
<v Peter O'Hara>Do things in a slightly different way to
improve the.

296
00:20:32.310 --> 00:20:38.109
<v Peter O'Hara>Customers their productivity and hopefully
improve their.

297
00:20:39.329 --> 00:20:43.489
<v Peter O'Hara>The, I can't think of a better word than,
the work life is like less firefighting,

298
00:20:43.609 --> 00:20:45.150
<v Peter O'Hara>less stress.

299
00:20:45.250 --> 00:20:52.209
<v Peter O'Hara>You want to be planning your, your next
few weeks ahead and not just reacting to

300
00:20:52.209 --> 00:20:57.189
<v Peter O'Hara>something being broken and the management
shouting at you, why did this happen?

301
00:20:58.229 --> 00:21:02.160
<v Speaker 3>Yeah, and I, I guess when you, when we're
thinking about a site level, choosing sort

302
00:21:02.160 --> 00:21:04.760
<v Speaker 3>of assets and lines to focus on is another
thing, but I guess.

303
00:21:05.170 --> 00:21:08.979
<v Speaker 3>Choosing the site maybe becomes obvious
because they, they'll, there'll be an

304
00:21:08.979 --> 00:21:12.369
<v Speaker 3>obvious issue there, whether it's too much
downtime, you know, too much over

305
00:21:12.369 --> 00:21:15.859
<v Speaker 3>maintenance, too, you know, maybe that,
that's what springs them into thinking,

306
00:21:15.939 --> 00:21:19.579
<v Speaker 3>maybe we should look at predictive
maintenance, use this as the starting point as we

307
00:21:19.579 --> 00:21:24.420
<v Speaker 3>know this, this plant needs some
attention, and then let's look for other use cases

308
00:21:24.420 --> 00:21:27.540
<v Speaker 3>in other plants and it sort of naturally
progresses from there.

309
00:21:27.819 --> 00:21:28.199
<v Speaker 3>Yeah.

310
00:21:28.540 --> 00:21:32.219
<v Peter O'Hara>I mean, one of our biggest customers.

311
00:21:33.250 --> 00:21:39.329
<v Peter O'Hara>Years ago when we were first put in one of
their plants and they were like, you

312
00:21:39.329 --> 00:21:44.130
<v Peter O'Hara>know, you haven't saved any downtime here
in the first like 3 months, I was like.

313
00:21:45.300 --> 00:21:46.099
<v Peter O'Hara>Have we missed anything?

314
00:21:46.180 --> 00:21:48.219
<v Peter O'Hara>Like, well, no, we don't have a problem on
these machines.

315
00:21:48.339 --> 00:21:53.130
<v Peter O'Hara>You're like, so, OK, so what machines do
you have a problem with?

316
00:21:53.219 --> 00:21:56.060
<v Peter O'Hara>Oh well, it's those ones over there, like,
well, let's have a look at the data from

317
00:21:56.060 --> 00:21:57.000
<v Peter O'Hara>those ones over there.

318
00:21:57.420 --> 00:22:04.420
<v Peter O'Hara>But we needed to almost get to that point
for the local

319
00:22:04.420 --> 00:22:06.400
<v Peter O'Hara>team, I guess, to feel empowered enough to
say.

320
00:22:07.369 --> 00:22:11.569
<v Peter O'Hara>What, I don't think it was a head office
thing, but you know, the, the management

321
00:22:11.569 --> 00:22:18.510
<v Peter O'Hara>have said over there that facility have
saved loads of, loads of costs by

322
00:22:18.810 --> 00:22:20.390
<v Peter O'Hara>doing this, so we're going to do it.

323
00:22:20.609 --> 00:22:24.689
<v Peter O'Hara>And then they rolled it out on the same
machines and in this particular place.

324
00:22:25.469 --> 00:22:31.270
<v Peter O'Hara>They had an over maintenance problem on
those machines, but they also had other

325
00:22:31.270 --> 00:22:35.699
<v Peter O'Hara>machines that were failing, and so, I was
like, well, let's, let's look at those

326
00:22:35.699 --> 00:22:37.829
<v Peter O'Hara>ones next, roll those out and.

327
00:22:38.569 --> 00:22:43.510
<v Peter O'Hara>That's how we got the buy-in, and now they
are definitely like the, the biggest

328
00:22:43.770 --> 00:22:49.209
<v Peter O'Hara>plant, I think we've still got online and
are always adding new things, and that's

329
00:22:49.609 --> 00:22:53.050
<v Peter O'Hara>one of the, the things with them is, you
know, every year they have a.

330
00:22:54.030 --> 00:22:58.520
<v Peter O'Hara>A plan to what are we going to add this
year, and they just slowly, slowly.

331
00:22:59.119 --> 00:23:02.900
<v Peter O'Hara>Add new things, so the same team now are
operating over.

332
00:23:03.660 --> 00:23:05.089
<v Peter O'Hara>Lots and lots of different shops.

333
00:23:05.780 --> 00:23:08.910
<v Peter O'Hara>But it's just been an incremental
expansion.

334
00:23:09.420 --> 00:23:09.819
<v Peter O'Hara>And, and

335
00:23:09.819 --> 00:23:13.140
<v Speaker 3>it is interesting, yeah, because it's back
to the point we talked about before about

336
00:23:13.140 --> 00:23:17.020
<v Speaker 3>comparing before across sites, you know,
when you're preparing completely different

337
00:23:17.020 --> 00:23:17.699
<v Speaker 3>metrics, I mean.

338
00:23:18.829 --> 00:23:22.420
<v Speaker 3>Yeah, it's very difficult to do that, but
they must, we must have a way to somehow

339
00:23:22.420 --> 00:23:26.380
<v Speaker 3>compare performance, I say it's a
competitive thing as well, even if the metrics are

340
00:23:26.380 --> 00:23:30.339
<v Speaker 3>slightly different or different assets and
different, you know, how, how do you sort

341
00:23:30.339 --> 00:23:31.400
<v Speaker 3>of go about that?

342
00:23:32.060 --> 00:23:38.959
<v Peter O'Hara>Well, we've got, so we have dashboards for
people like me to have a look at.

343
00:23:39.439 --> 00:23:43.790
<v Peter O'Hara>So we can make sure that the, you know,
the customer's engaged and that they are

344
00:23:43.790 --> 00:23:48.030
<v Peter O'Hara>recording the different KPIs and that sort
of thing, so we can pull that information

345
00:23:48.030 --> 00:23:49.500
<v Peter O'Hara>out and share it with the customers.

346
00:23:50.030 --> 00:23:56.750
<v Peter O'Hara>We have in the application, we have the
like a home screen that has all

347
00:23:56.750 --> 00:24:02.640
<v Peter O'Hara>the KPIs that are added by the customers
and then it has a look at app performances,

348
00:24:02.709 --> 00:24:06.589
<v Peter O'Hara>so how many alerts, how many alerts are
open, how many closed, and.

349
00:24:07.000 --> 00:24:12.800
<v Peter O'Hara>Yeah, the, the different KPIs that are
being stored by the customers, so having that

350
00:24:12.800 --> 00:24:16.599
<v Peter O'Hara>is the very easy way of comparing things.

351
00:24:17.219 --> 00:24:20.560
<v Peter O'Hara>When you look at the less easy way.

352
00:24:21.760 --> 00:24:28.520
<v Peter O'Hara>You kind of get a feel from my point of
view about how customers are engaged

353
00:24:28.520 --> 00:24:32.800
<v Peter O'Hara>and when they're logging into the
application and things like that, so.

354
00:24:33.520 --> 00:24:36.819
<v Peter O'Hara>For the, the earlier days of a deployment.

355
00:24:37.689 --> 00:24:44.380
<v Peter O'Hara>We can see user behavior, so that's quite
a good way of just checking the

356
00:24:44.380 --> 00:24:50.619
<v Peter O'Hara>pulse of a project, but generally once
it's at scale, then yeah, it's about the

357
00:24:50.619 --> 00:24:57.079
<v Peter O'Hara>KPIs and things like, you know, making
sure that all your

358
00:24:57.380 --> 00:25:01.260
<v Peter O'Hara>sensors are online and reading and things
like that, that you're not having stuff

359
00:25:01.260 --> 00:25:04.500
<v Peter O'Hara>behind the scenes, kind of like dropping
off and people not noticing.

360
00:25:04.880 --> 00:25:09.910
<v Peter O'Hara>So we have a lot of customers, but the
management side of reports are.

361
00:25:10.989 --> 00:25:15.270
<v Peter O'Hara>Different to the users' reports, if you
see what I mean, so the users get told, oh,

362
00:25:15.670 --> 00:25:17.329
<v Peter O'Hara>you've got an alert on here because.

363
00:25:18.089 --> 00:25:22.079
<v Peter O'Hara>You know, this is trending up or that's
normallying down or whatever, but then the

364
00:25:22.079 --> 00:25:27.410
<v Peter O'Hara>management are like, well how many cases
have not been responded to in this week and

365
00:25:27.410 --> 00:25:29.329
<v Peter O'Hara>you know what KPIs we've put in and.

366
00:25:30.150 --> 00:25:31.250
<v Peter O'Hara>That sort of stuff.

367
00:25:31.790 --> 00:25:35.329
<v Speaker 3>Yeah, no, that again, makes, makes a lot
of sense.

368
00:25:35.709 --> 00:25:38.949
<v Speaker 3>As as we sort of come towards the end, I
wanted to sort of split.

369
00:25:39.819 --> 00:25:44.219
<v Speaker 3>Well, yeah, look at two sides of the coin,
I guess, so just to sort of summarize, I

370
00:25:44.219 --> 00:25:48.410
<v Speaker 3>wanna look at, you know, the positives and
what would look like in, uh, you know, 23

371
00:25:48.410 --> 00:25:51.979
<v Speaker 3>years' time as things roll out
successfully, but what are some of the sort of the

372
00:25:51.979 --> 00:25:55.530
<v Speaker 3>classic mistakes you, you've seen over the
years, Pete, in terms of these sort of

373
00:25:55.530 --> 00:25:56.660
<v Speaker 3>multi-site rollouts?

374
00:25:56.739 --> 00:26:03.180
<v Speaker 3>What, what can even subtly sort of derail,
you know, these sort of programs, you

375
00:26:03.180 --> 00:26:05.800
<v Speaker 3>know, if, if, if it's not spotted early
on.

376
00:26:06.140 --> 00:26:07.040
<v Peter O'Hara>Yeah, I think.

377
00:26:07.979 --> 00:26:14.930
<v Peter O'Hara>Definitely the uh the stakeholder
engagement, like I say, the, the head office,

378
00:26:14.939 --> 00:26:20.359
<v Peter O'Hara>you must do this side of things and if
there's resistance, that can cause a problem.

379
00:26:21.310 --> 00:26:22.000
<v Peter O'Hara>One of the.

380
00:26:22.939 --> 00:26:27.219
<v Peter O'Hara>The things we talk about, obviously we've
actually I haven't mentioned it this time,

381
00:26:27.339 --> 00:26:30.579
<v Peter O'Hara>the, the good old sense and knowledge
platform about getting the right people in the

382
00:26:30.579 --> 00:26:32.689
<v Peter O'Hara>room at the right time and to discuss
things.

383
00:26:33.099 --> 00:26:37.160
<v Peter O'Hara>One of the areas I see often is.

384
00:26:38.229 --> 00:26:43.430
<v Peter O'Hara>There's not enough documentation
internally for.

385
00:26:44.219 --> 00:26:50.250
<v Peter O'Hara>The flow of data, so at the beginning of a
project, people know what machines are

386
00:26:50.250 --> 00:26:54.530
<v Peter O'Hara>being captured, of course like what
machines, what data are being captured from the

387
00:26:54.530 --> 00:26:57.810
<v Peter O'Hara>machines and its route into, into Sensei.

388
00:26:58.969 --> 00:27:02.930
<v Peter O'Hara>But then give it 2 or 3 years and then
we'll get a support ticket, and it'll be

389
00:27:02.930 --> 00:27:07.010
<v Peter O'Hara>like, oh, my machine, you know, you're
not, you're not showing the data from my

390
00:27:07.010 --> 00:27:07.250
<v Peter O'Hara>machine.

391
00:27:08.119 --> 00:27:14.219
<v Peter O'Hara>And it's like, well, OK, I can pretty much
guarantee you that isn't a

392
00:27:15.160 --> 00:27:17.260
<v Peter O'Hara>quote unquote, a sense side problem, it's
a.

393
00:27:18.189 --> 00:27:20.770
<v Peter O'Hara>Site getting the data to Sesite problem.

394
00:27:21.670 --> 00:27:23.180
<v Peter O'Hara>So then you have to.

395
00:27:24.280 --> 00:27:31.119
<v Peter O'Hara>Be able to unpick the, the data pipeline
to see where the problem is, so that's

396
00:27:31.560 --> 00:27:37.489
<v Peter O'Hara>typically an area that I, I see, and in a
way it's good that.

397
00:27:38.619 --> 00:27:45.160
<v Peter O'Hara>The, you know, the maintainers just expect
the data to be there, but We need to

398
00:27:45.520 --> 00:27:51.560
<v Peter O'Hara>capture that documentation, ideally have
it within the good old Sensdy knowledge

399
00:27:51.560 --> 00:27:57.310
<v Peter O'Hara>platform, so we can add this information
in the early stages of a deployment,

400
00:27:57.880 --> 00:28:02.859
<v Peter O'Hara>particularly if you've got, you know, IT
support tickets, you know, which.

401
00:28:03.920 --> 00:28:07.520
<v Peter O'Hara>If it's an email address or a phone
number, have that actually within the

402
00:28:07.520 --> 00:28:11.290
<v Peter O'Hara>application, so the application, if you
ask it, it can tell you.

403
00:28:11.650 --> 00:28:15.359
<v Peter O'Hara>So you know, the co-pilot type stuff, if
it has that information, it can regurgitate

404
00:28:15.359 --> 00:28:18.729
<v Peter O'Hara>it, if that's not captured at the start of
a project, it won't be able to.

405
00:28:19.599 --> 00:28:24.239
<v Peter O'Hara>And yeah, I suppose those are probably the
biggest thing.

406
00:28:24.319 --> 00:28:25.619
<v Peter O'Hara>The other thing is you have.

407
00:28:26.640 --> 00:28:29.540
<v Peter O'Hara>A user of Sensei and.

408
00:28:30.750 --> 00:28:37.680
<v Peter O'Hara>When they Get promoted or leave the
company, then there's can be a lack of

409
00:28:37.680 --> 00:28:39.900
<v Peter O'Hara>backfilling of some issues.

410
00:28:41.229 --> 00:28:42.890
<v Peter O'Hara>In the past where, you know.

411
00:28:44.119 --> 00:28:50.959
<v Peter O'Hara>That Experience and knowledge leaves, and
so one of the, the

412
00:28:50.959 --> 00:28:55.319
<v Peter O'Hara>beauties of having the co-pilot and like I
say, the knowledge documentation and

413
00:28:55.319 --> 00:28:59.520
<v Peter O'Hara>things like that, if we load that
information into the system, then the system will

414
00:28:59.520 --> 00:29:04.719
<v Peter O'Hara>know it and it will be able to say, oh,
last time you saw this issue, these are the

415
00:29:04.719 --> 00:29:06.140
<v Peter O'Hara>work events that you put in.

416
00:29:06.479 --> 00:29:12.319
<v Peter O'Hara>So that's brilliant if people have used
the system to its fullest capabilities, but

417
00:29:12.319 --> 00:29:15.520
<v Peter O'Hara>things like, say the data pipeline and
stuff like that.

418
00:29:16.439 --> 00:29:22.250
<v Peter O'Hara>Often, that's not captured or uploaded in
the early stages, so one of the things I

419
00:29:22.250 --> 00:29:26.750
<v Peter O'Hara>do when I take over a project is I try and
make sure that that information's there,

420
00:29:26.770 --> 00:29:28.050
<v Peter O'Hara>and then I just know that.

421
00:29:29.040 --> 00:29:34.319
<v Peter O'Hara>You know, down the line, it's going to
allow for a much smoother kind of like

422
00:29:34.319 --> 00:29:37.040
<v Peter O'Hara>troubleshooting type situation for
customers.

423
00:29:38.089 --> 00:29:39.060
<v Speaker 3>Yeah, so it's,

424
00:29:39.869 --> 00:29:39.989
<v Peter O'Hara>yeah,

425
00:29:40.310 --> 00:29:44.349
<v Speaker 3>so, so it's again, so we talked about
quite a lot about capturing the knowledge so

426
00:29:44.349 --> 00:29:45.540
<v Speaker 3>it can be reused.

427
00:29:45.790 --> 00:29:45.989
<v Speaker 3>Yeah.

428
00:29:46.329 --> 00:29:48.989
<v Speaker 3>Yeah, not, yeah, not just, yeah, for those
circumstances, you know, where people

429
00:29:48.989 --> 00:29:54.229
<v Speaker 3>leave and you know new people come in and
they can come up to speed, but also just

430
00:29:54.229 --> 00:29:58.869
<v Speaker 3>to, to understand what the project's for,
which assets, more detailed information

431
00:29:58.869 --> 00:30:01.060
<v Speaker 3>on, on, on that side of things.

432
00:30:01.510 --> 00:30:05.569
<v Peter O'Hara>Yeah, and so our delivery process now.

433
00:30:06.280 --> 00:30:10.920
<v Peter O'Hara>We ask the customers to fill out these
asset passports, which are, you know, why are

434
00:30:10.920 --> 00:30:17.119
<v Peter O'Hara>you monitoring these machines, what are
the measures and that sort of thing, and I

435
00:30:17.119 --> 00:30:21.160
<v Peter O'Hara>haven't really been that involved in the
early stage of of the delivery side, but

436
00:30:21.160 --> 00:30:25.920
<v Peter O'Hara>it, it might seem like paperwork for
paperwork's sake, but once those asset

437
00:30:25.920 --> 00:30:29.000
<v Peter O'Hara>passports are loaded in, you know, 3 or 4
years' time and somebody comes with a

438
00:30:29.000 --> 00:30:31.650
<v Peter O'Hara>project like, why are we monitoring this
piece of equipment?

439
00:30:32.219 --> 00:30:36.219
<v Peter O'Hara>Which has been asked from me for older
projects.

440
00:30:36.959 --> 00:30:41.160
<v Peter O'Hara>And You can tell them, oh why you don't
even, don't even mean to ask me, you can ask

441
00:30:41.160 --> 00:30:44.189
<v Peter O'Hara>copilot, why are we monitoring these, and
it will tell you why you're monitoring

442
00:30:44.189 --> 00:30:48.969
<v Peter O'Hara>them and what successes you've had with
them, but again, that's, you're a little.

443
00:30:49.709 --> 00:30:53.430
<v Peter O'Hara>Extra level of detail that, you know.

444
00:30:54.079 --> 00:30:55.579
<v Peter O'Hara>Back when we started all of this.

445
00:30:56.540 --> 00:31:01.739
<v Peter O'Hara>It wouldn't, well it wouldn't have been
captured within Sense IV application, so

446
00:31:01.739 --> 00:31:07.500
<v Peter O'Hara>it's within our records and that sort of
stuff, but yeah, customers capturing that

447
00:31:07.500 --> 00:31:09.699
<v Peter O'Hara>themselves is a very good idea.

448
00:31:10.609 --> 00:31:14.050
<v Speaker 3>And, and that happens every time new, new
assets, so we talk about the scale piece

449
00:31:14.050 --> 00:31:19.500
<v Speaker 3>again as new assets are on board the same
passport will be created and so

450
00:31:19.500 --> 00:31:20.310
<v Peter O'Hara>I would hope so.

451
00:31:20.609 --> 00:31:25.329
<v Peter O'Hara>But once it's, once customers are
self-serving, then.

452
00:31:25.979 --> 00:31:30.859
<v Peter O'Hara>You know, there's no way of us policing
that they are uploading this information,

453
00:31:30.939 --> 00:31:36.000
<v Peter O'Hara>whereas usually, like you say about the,
the start of a project, you'll have

454
00:31:36.339 --> 00:31:41.500
<v Peter O'Hara>probably special project engineers
involved and they are very keen on this and

455
00:31:41.500 --> 00:31:43.640
<v Peter O'Hara>they'll document everything and then.

456
00:31:44.619 --> 00:31:49.500
<v Peter O'Hara>They will move off to their other special
projects in the next few years, and so

457
00:31:49.500 --> 00:31:51.969
<v Peter O'Hara>usually other people start to onboard
stuff.

458
00:31:52.300 --> 00:31:58.040
<v Peter O'Hara>Now, hopefully, again, they are keeping
records, but that becomes a little bit more

459
00:31:58.619 --> 00:32:04.859
<v Peter O'Hara>like customer centric and somebody like
myself, if we're engaged with them, we can

460
00:32:04.859 --> 00:32:09.520
<v Peter O'Hara>advise, you really ought to be capturing
this stuff and hopefully we've set good

461
00:32:09.780 --> 00:32:12.859
<v Peter O'Hara>working practices, but that's one area
that.

462
00:32:13.540 --> 00:32:15.660
<v Peter O'Hara>You know, it's over to the customer to
actually do.

463
00:32:16.680 --> 00:32:17.280
<v Speaker 3>No, exactly.

464
00:32:17.400 --> 00:32:20.400
<v Speaker 3>I mean, and that's ultimately what we
want, really, in a way is that they're,

465
00:32:20.609 --> 00:32:22.640
<v Speaker 3>they're the ones sort of leading and
taking it forward.

466
00:32:22.739 --> 00:32:25.140
<v Speaker 3>So, uh, so, no, absolutely.

467
00:32:25.239 --> 00:32:28.800
<v Speaker 3>And then, yeah, and then, so finally, I
want to finish on, obviously a positive as

468
00:32:28.800 --> 00:32:29.040
<v Speaker 3>well.

469
00:32:29.189 --> 00:32:32.680
<v Speaker 3>So, what good looks like, say, 23 years
down the line.

470
00:32:32.719 --> 00:32:37.130
<v Speaker 3>I mean, we could just say since I deployed
everywhere, but I guess there's other

471
00:32:37.130 --> 00:32:41.680
<v Speaker 3>sort of nuances underneath that, you know,
changes in behavior or that kind of

472
00:32:41.680 --> 00:32:41.859
<v Speaker 3>thing.

473
00:32:42.270 --> 00:32:43.469
<v Speaker 3>And obviously successful results,

474
00:32:43.520 --> 00:32:43.989
<v Peter O'Hara>of course.

475
00:32:44.199 --> 00:32:44.900
<v Peter O'Hara>I think.

476
00:32:45.780 --> 00:32:50.300
<v Peter O'Hara>What we've discussed in other podcasts,
you know, the, you want to be tracking the

477
00:32:50.300 --> 00:32:53.420
<v Peter O'Hara>savings and it's not necessarily just.

478
00:32:54.290 --> 00:32:57.699
<v Peter O'Hara>Within Sensei itself, but you can look at.

479
00:32:58.469 --> 00:33:04.949
<v Peter O'Hara>The improved part supply, you can look at
your, the labor save because you're not

480
00:33:04.949 --> 00:33:09.770
<v Peter O'Hara>investigating failures and stuff like
that, so you can look at stuff that's outside

481
00:33:09.770 --> 00:33:13.050
<v Peter O'Hara>of Sensei and track that for improvements.

482
00:33:14.270 --> 00:33:18.310
<v Peter O'Hara>It would be nice if customers were looking
at how many assets have we onboarded this

483
00:33:18.310 --> 00:33:25.189
<v Peter O'Hara>year, and despite the, like, oh yeah,
let's roll out, then there

484
00:33:25.189 --> 00:33:30.189
<v Peter O'Hara>will always be, well usually there will
always be more areas that you can add stuff

485
00:33:30.189 --> 00:33:30.530
<v Peter O'Hara>to.

486
00:33:30.910 --> 00:33:36.550
<v Peter O'Hara>So most customers will still be adding
areas over the, you know.

487
00:33:37.250 --> 00:33:41.969
<v Peter O'Hara>The, the next few years, you might have a
lull, they might go like 3 years or so

488
00:33:41.969 --> 00:33:45.170
<v Peter O'Hara>where they've got everything they want and
then they'll, you know, retool or they'll

489
00:33:45.170 --> 00:33:47.930
<v Peter O'Hara>put a new line in or whatever and then it,
it'll jump up again.

490
00:33:48.290 --> 00:33:52.270
<v Peter O'Hara>But often you've got customers who are
like, right, what shall we do next?

491
00:33:52.369 --> 00:33:56.290
<v Peter O'Hara>And then, they, you know, they put the
troublesome stuff on first, put the stuff

492
00:33:56.290 --> 00:34:01.130
<v Peter O'Hara>that is very similar, but then there are
other things, I, I've mentioned it in the

493
00:34:01.130 --> 00:34:01.979
<v Peter O'Hara>past, things like.

494
00:34:02.449 --> 00:34:07.219
<v Peter O'Hara>Temperature of control panels and stuff
like that, stuff that is like really, really

495
00:34:07.219 --> 00:34:07.729
<v Peter O'Hara>simple.

496
00:34:08.820 --> 00:34:14.179
<v Peter O'Hara>Never, never goes wrong, but then it only
takes one person to fail to turn the AC

497
00:34:14.179 --> 00:34:18.560
<v Peter O'Hara>back on after they've maintained it, and
then suddenly you've got a really expensive

498
00:34:19.179 --> 00:34:23.139
<v Peter O'Hara>downtime because you've, you've burnt out
one of your drives or whatever, so, those

499
00:34:23.139 --> 00:34:23.919
<v Peter O'Hara>sorts of.

500
00:34:25.250 --> 00:34:30.129
<v Peter O'Hara>Assets when they come online and it's, you
know, flip a switch at scale and

501
00:34:30.129 --> 00:34:34.689
<v Peter O'Hara>everything's just boom and it's there and,
you know, it's unusual to get an alert

502
00:34:34.689 --> 00:34:39.229
<v Peter O'Hara>from them, that's the, what happens over
the, the subsequent years.

503
00:34:40.249 --> 00:34:41.239
<v Peter O'Hara>Which is always nice.

504
00:34:42.669 --> 00:34:44.989
<v Speaker 3>Yeah, no, fantastic, fantastic.

505
00:34:45.469 --> 00:34:49.270
<v Speaker 3>Yeah, so I think that that brings us to
the end today, Pete, but thank you for

506
00:34:49.270 --> 00:34:52.300
<v Speaker 3>sharing your, your experiences of, um,
sort of sense I roll out.

507
00:34:52.340 --> 00:34:54.090
<v Speaker 3>It's been really great to chat with you
today.

508
00:34:54.600 --> 00:34:57.350
<v Peter O'Hara>Try and think of some more questions for
you to ask me next time.

509
00:34:57.949 --> 00:35:00.389
<v Speaker 3>No, exactly, keep me, keep me on my toes,
that sounds good.

510
00:35:00.500 --> 00:35:02.340
<v Speaker 3>But no, thank you for joining us, Pete.

511
00:35:02.669 --> 00:35:05.669
<v Speaker 3>Thank you, everyone out there for
listening, wherever you are, and we'll speak to

512
00:35:05.669 --> 00:35:06.449
<v Speaker 3>you on the next episode.

513
00:35:06.820 --> 00:35:07.199
<v Speaker 3>Yeah, thanks.

514
00:35:09.489 --> 00:35:12.969
<v Speaker 2>Please like and subscribe on all major
podcast channels.

515
00:35:13.050 --> 00:35:17.969
<v Speaker 2>And to find out more about Sensi
predictive maintenance, go to Siemens.com.
