WEBVTT
Language: en-US

1
00:00:01.179 --> 00:00:05.530
<v Brad Parsons>I, I guess from culture's a thing that
happened when no one's looking, right?

2
00:00:06.460 --> 00:00:09.420
<v Brad Parsons>Whether you're running a business or
whether you're working in a large

3
00:00:09.420 --> 00:00:14.539
<v Brad Parsons>multinational, um, you can pretty much see
how the culture or how effective the

4
00:00:14.539 --> 00:00:19.100
<v Brad Parsons>culture is, uh, in terms of, you know,
what's actually happening when, when the boss

5
00:00:19.100 --> 00:00:19.760
<v Brad Parsons>isn't there.

6
00:00:22.389 --> 00:00:27.590
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens, and now your host, Nel

7
00:00:27.590 --> 00:00:28.149
<v Speaker 2>Sullivan.

8
00:00:32.299 --> 00:00:37.040
<v Niall Sullivan>Hello and welcome to the latest episode of
the Trend Detection podcast.

9
00:00:37.659 --> 00:00:40.180
<v Niall Sullivan>Um, I'm really pleased to be joined by a
brand new guest.

10
00:00:40.380 --> 00:00:43.060
<v Niall Sullivan>Um, I know we have a lot of recurring
guests, but it's always great to have a brand

11
00:00:43.060 --> 00:00:45.520
<v Niall Sullivan>new face or voice, I should say on the
podcast.

12
00:00:45.970 --> 00:00:52.180
<v Niall Sullivan>Um, Brad Parsons, who's the CEO and
co-founder of Reliability, um, all the way in

13
00:00:52.180 --> 00:00:54.880
<v Niall Sullivan>Australia, so we're in completely
different time zones at the moment.

14
00:00:55.250 --> 00:00:58.409
<v Niall Sullivan>Um, but we're, we're gonna have a really
great conversation today.

15
00:00:58.450 --> 00:01:02.830
<v Niall Sullivan>It's something we at Sensi Predictive
Maintenance, the team within Siemens, we're,

16
00:01:03.090 --> 00:01:07.529
<v Niall Sullivan>we're often talking about this cultural
shift required for embracing predictive

17
00:01:07.529 --> 00:01:09.970
<v Niall Sullivan>maintenance, and that's exactly what we're
gonna talk about today.

18
00:01:10.050 --> 00:01:13.599
<v Niall Sullivan>And it'll be great to get, um, Brad's
unique sort of perspective on this.

19
00:01:13.680 --> 00:01:17.489
<v Niall Sullivan>But I guess before we go into the topic in
more detail, Brads, if you could just

20
00:01:17.489 --> 00:01:20.029
<v Niall Sullivan>sort of introduce yourself to the
audience, that'd be, that'd be really cool.

21
00:01:21.120 --> 00:01:23.080
<v Brad Parsons>Hi everyone, my name is Brad Parsons.

22
00:01:23.199 --> 00:01:27.239
<v Brad Parsons>Uh, I know I might have mentioned I've got
a business called Reliability.

23
00:01:27.599 --> 00:01:31.160
<v Brad Parsons>I'm the CEO and founder of that business,
but I also might try and talk through

24
00:01:31.160 --> 00:01:34.559
<v Brad Parsons>another business that I founded prior to
reliability called Movis.

25
00:01:35.099 --> 00:01:40.260
<v Brad Parsons>Um, Movis is a product and product and
services business, but reliability is a

26
00:01:40.260 --> 00:01:42.779
<v Brad Parsons>consulting and solutions business.

27
00:01:42.860 --> 00:01:45.139
<v Brad Parsons>So, 22 sides of that coin.

28
00:01:45.250 --> 00:01:50.260
<v Brad Parsons>Um, one has built a product, multiple
products and gone to market, uh, with services

29
00:01:50.260 --> 00:01:50.849
<v Brad Parsons>attached.

30
00:01:51.220 --> 00:01:56.300
<v Brad Parsons>That's Movis, and with reliability, um,
we're really a consulting house, so we have

31
00:01:56.300 --> 00:01:59.980
<v Brad Parsons>our in-house methodologies, but we also
bring the best of breed solutions from

32
00:01:59.980 --> 00:02:03.500
<v Brad Parsons>around the world, um, such as the Siemens
product, um, Sentai in particular.

33
00:02:04.080 --> 00:02:06.910
<v Brad Parsons>Um, but yeah, like, excited to be here and
see where this goes.

34
00:02:08.300 --> 00:02:09.220
<v Niall Sullivan>Yeah, no, fantastic.

35
00:02:09.330 --> 00:02:10.220
<v Niall Sullivan>Thanks for joining us.

36
00:02:10.339 --> 00:02:14.410
<v Niall Sullivan>And, um, what I like about that, is so,
so, essentially what you're saying

37
00:02:14.410 --> 00:02:17.720
<v Niall Sullivan>completely independent in the sense that,
you know, you're not, you know, focused on

38
00:02:17.720 --> 00:02:18.380
<v Niall Sullivan>Siemens, for example.

39
00:02:18.460 --> 00:02:22.220
<v Niall Sullivan>It's, it's actually what's, you know, you
know, talking to the customers and

40
00:02:22.220 --> 00:02:25.460
<v Niall Sullivan>understanding what do they need and then
picking, not as easy as this, picking off

41
00:02:25.460 --> 00:02:29.970
<v Niall Sullivan>the shelves, what you, What you think's
the, and putting it together, orchestrating.

42
00:02:30.039 --> 00:02:34.119
<v Niall Sullivan>I mean, what you described yourself just
before we, we came on air as, um, it's a

43
00:02:34.119 --> 00:02:35.029
<v Niall Sullivan>really interesting term.

44
00:02:35.679 --> 00:02:39.550
<v Brad Parsons>Yeah, the, the title, I kind of called
myself on LinkedIn where you can find me as

45
00:02:39.550 --> 00:02:41.000
<v Brad Parsons>ecosystem orchestrator.

46
00:02:41.300 --> 00:02:46.380
<v Brad Parsons>Uh, I don't see myself as a CEO
traditionally, like I was with the Movis business.

47
00:02:46.910 --> 00:02:52.070
<v Brad Parsons>Um, with reliability, we're more about
generating value outside the business than

48
00:02:52.070 --> 00:02:52.770
<v Brad Parsons>inside the business.

49
00:02:52.990 --> 00:02:56.630
<v Brad Parsons>So, that's really trying to find, as I
said, best of breed, best of breed solutions,

50
00:02:56.710 --> 00:03:01.669
<v Brad Parsons>best of breed technologies, and bringing
them together, um, to solve the customer's

51
00:03:01.669 --> 00:03:01.949
<v Brad Parsons>problem.

52
00:03:02.029 --> 00:03:05.979
<v Brad Parsons>There's no cus customer's problem,
unfortunately, is exactly the same.

53
00:03:06.059 --> 00:03:11.509
<v Brad Parsons>You need to kind of bring different um
capabilities to the fore and really

54
00:03:11.509 --> 00:03:13.149
<v Brad Parsons>understand the challenges that they're
trying to solve.

55
00:03:15.039 --> 00:03:20.320
<v Niall Sullivan>And that, and yeah, and I guess what, what
we're covering today is, is an important,

56
00:03:20.369 --> 00:03:24.889
<v Niall Sullivan>but maybe, I mean, maybe you disagree or
agree, but an overlooked aspect of like

57
00:03:24.889 --> 00:03:28.869
<v Niall Sullivan>adopting new technologies, which is this
cultural element.

58
00:03:29.210 --> 00:03:32.929
<v Niall Sullivan>Um, so from your point of view, Brian,
you've been involved in many sort of projects

59
00:03:32.929 --> 00:03:37.250
<v Niall Sullivan>in, you know, around technology, but how
would you sort of define cultural adoption

60
00:03:37.250 --> 00:03:40.350
<v Niall Sullivan>in this, in the context of adopting new
technologies?

61
00:03:41.320 --> 00:03:45.669
<v Brad Parsons>I, I guess from culture's a thing that
happened when no one's looking, right?

62
00:03:46.559 --> 00:03:49.520
<v Brad Parsons>Whether you're running a business or
whether you're working in a large

63
00:03:49.520 --> 00:03:54.679
<v Brad Parsons>multinational, um, you can pretty much see
how the culture or how effective the

64
00:03:54.679 --> 00:03:59.199
<v Brad Parsons>culture is, uh, in terms of, you know,
what's actually happening when, when the boss

65
00:03:59.199 --> 00:03:59.830
<v Brad Parsons>isn't there.

66
00:04:00.000 --> 00:04:04.460
<v Brad Parsons>Um, so I, I certainly know that from
experience, but, I, I guess in terms of

67
00:04:05.160 --> 00:04:10.839
<v Brad Parsons>understanding how culture supports
technology adoption, I, I did a, I did a similar

68
00:04:10.839 --> 00:04:15.559
<v Brad Parsons>sort of, uh, webinar last year, um, and I
was asked to kind of define that in more

69
00:04:15.559 --> 00:04:16.200
<v Brad Parsons>specifics.

70
00:04:17.059 --> 00:04:21.920
<v Brad Parsons>And there's, from, from look kind of
looking back at my experience and looking back

71
00:04:21.920 --> 00:04:26.720
<v Brad Parsons>and, and talking to others, there's really
kind of four cultures, if you like.

72
00:04:26.839 --> 00:04:31.519
<v Brad Parsons>Um, there's a collaborative culture, um,
there's a control culture, and we'll talk

73
00:04:31.519 --> 00:04:32.779
<v Brad Parsons>about that a little bit later.

74
00:04:32.920 --> 00:04:36.600
<v Brad Parsons>Um, there's a compete culture, you know,
that always wants to be the first and the

75
00:04:36.600 --> 00:04:41.720
<v Brad Parsons>best, and then there's a create culture,
you know, which is the invented here

76
00:04:41.720 --> 00:04:45.220
<v Brad Parsons>syndrome, which can, which can work
against you if you're a technology provider.

77
00:04:45.579 --> 00:04:49.779
<v Brad Parsons>Um, really it's trying to understand the
culture that's present, um, and maybe

78
00:04:49.779 --> 00:04:52.899
<v Brad Parsons>there's a cultural transformation going on
as well as part of a digital

79
00:04:52.899 --> 00:04:57.450
<v Brad Parsons>transformation effort, but really
understanding the foundation of what's there, um,

80
00:04:57.619 --> 00:05:01.459
<v Brad Parsons>particularly if you're a technology or
services provider, knowing what you're going

81
00:05:01.459 --> 00:05:03.570
<v Brad Parsons>into, um, really understands it.

82
00:05:03.609 --> 00:05:08.899
<v Brad Parsons>I mean, people define culture in many
ways, uh, but that's it, that's kind of how I

83
00:05:08.899 --> 00:05:09.179
<v Brad Parsons>see it.

84
00:05:10.899 --> 00:05:14.140
<v Niall Sullivan>And And you, you, you mentioned those
different areas.

85
00:05:14.250 --> 00:05:19.019
<v Niall Sullivan>Is that quite broadly, can that be quite
broadly used to define implementations of

86
00:05:19.019 --> 00:05:20.250
<v Niall Sullivan>all different types of products?

87
00:05:20.299 --> 00:05:23.179
<v Niall Sullivan>I mean, maybe today we're, we're leaning
towards predictive maintenance, but if we

88
00:05:23.179 --> 00:05:26.679
<v Niall Sullivan>talk about, you know, other, other
products as well, is it, can it be broadly

89
00:05:26.750 --> 00:05:28.440
<v Niall Sullivan>applied to other products as well?

90
00:05:29.029 --> 00:05:29.269
<v Brad Parsons>Absolutely.

91
00:05:29.470 --> 00:05:33.230
<v Brad Parsons>I think it can be broadly applied, you
know, fortunately my wife's a change manager

92
00:05:33.230 --> 00:05:38.910
<v Brad Parsons>of 30 years, so I, I kind of hear, hear
this, and she's run large program teams as

93
00:05:38.910 --> 00:05:40.149
<v Brad Parsons>the head of change.

94
00:05:40.230 --> 00:05:45.350
<v Brad Parsons>So, I kind of hear a lot of this, you
know, not just at home, uh, but at work, not

95
00:05:45.350 --> 00:05:46.730
<v Brad Parsons>just at work, but at home as well.

96
00:05:47.570 --> 00:05:51.970
<v Brad Parsons>Depending on that culture that's present,
that will really influence the way in

97
00:05:51.970 --> 00:05:57.529
<v Brad Parsons>which you want to engage in terms of
predictive maintenance, and we'll talk through

98
00:05:57.529 --> 00:06:03.529
<v Brad Parsons>it a little bit further, but maybe there's
multiple cultures that actually exist and

99
00:06:03.529 --> 00:06:07.079
<v Brad Parsons>particularly in the sort of digital
transformation, you know, I've been doing these,

100
00:06:07.209 --> 00:06:12.529
<v Brad Parsons>these sort of projects uh for the last
sort of 1010 plus years, back in the, you

101
00:06:12.529 --> 00:06:15.470
<v Brad Parsons>know, sort of 2012, 2013 was when I first
started.

102
00:06:16.299 --> 00:06:21.059
<v Brad Parsons>And what you'll find is, it can actually,
culture can vary not only out of the site

103
00:06:21.059 --> 00:06:24.619
<v Brad Parsons>level at the company level, but sort of
down to the department level.

104
00:06:24.940 --> 00:06:31.320
<v Brad Parsons>One culture, um, you know, is not
dominant, you're not dealing with, you know, um,

105
00:06:31.339 --> 00:06:35.459
<v Brad Parsons>the vanilla, um, you're actually dealing
with the chocolate, the strawberry, and the

106
00:06:35.459 --> 00:06:38.980
<v Brad Parsons>vanilla, um, and really depends, you need
to understand the audience you're, you're

107
00:06:38.980 --> 00:06:39.760
<v Brad Parsons>working with and.

108
00:06:40.179 --> 00:06:43.940
<v Brad Parsons>You need to kind of adjust the way you
work with them um to be conscious of that

109
00:06:43.940 --> 00:06:48.260
<v Brad Parsons>culture, um, you know, don't, don't assume
everyone's the same, I think it's

110
00:06:48.260 --> 00:06:49.380
<v Brad Parsons>probably the general guys there.

111
00:06:50.489 --> 00:06:54.369
<v Niall Sullivan>No, exactly, and I think one thing again
we, we briefly spoke about before is this

112
00:06:54.369 --> 00:06:58.529
<v Niall Sullivan>sort of, you know, when you're rolling out
technology globally as well, is that it,

113
00:06:58.690 --> 00:07:03.510
<v Niall Sullivan>that you becomes even more, uh, even more
important to consider, right?

114
00:07:03.730 --> 00:07:07.049
<v Niall Sullivan>So even in the same organization doesn't
mean the culture is same in this part to

115
00:07:07.049 --> 00:07:08.149
<v Niall Sullivan>this part, right?

116
00:07:08.850 --> 00:07:10.290
<v Brad Parsons>Yeah, absolutely, um.

117
00:07:11.000 --> 00:07:15.160
<v Brad Parsons>Yeah, I was just reflecting back on that
sort of question and, and, and really

118
00:07:15.160 --> 00:07:18.899
<v Brad Parsons>having done dope global deployments with
Movis, we got out to sort of 18 countries,

119
00:07:19.200 --> 00:07:24.600
<v Brad Parsons>so with multiple different um cultures
span that and, you know, you can make

120
00:07:24.600 --> 00:07:29.440
<v Brad Parsons>assumptions, you can make an assumption
that the, the Chinese, the Japanese, the

121
00:07:29.440 --> 00:07:35.239
<v Brad Parsons>Indian culture is very top-down, and, you
know, maybe um stereotypically that's the

122
00:07:35.239 --> 00:07:38.480
<v Brad Parsons>case, and you'd look at Australia and the
US where it's very bottom up.

123
00:07:38.829 --> 00:07:43.690
<v Brad Parsons>Um, going in with a particular approach,
um, and, and in my experience in talking to

124
00:07:43.690 --> 00:07:47.029
<v Brad Parsons>some of the solutions that we provide as
part of the reliability fleet or the

125
00:07:47.029 --> 00:07:52.630
<v Brad Parsons>ecosystem, selling bottom up and top-down,
making sure that you're addressing the

126
00:07:52.630 --> 00:07:56.750
<v Brad Parsons>needs of both of those, um, you know, both
of those parts of the business.

127
00:07:57.190 --> 00:08:00.470
<v Brad Parsons>The senior management, you know, wanna,
wanna know things like performance, they

128
00:08:00.470 --> 00:08:03.649
<v Brad Parsons>wanna know long-term visibility, obviously
wanna know financial outcomes.

129
00:08:04.040 --> 00:08:07.480
<v Brad Parsons>Um, whereas the, the, the shop floor,
particularly in the predictive maintenance,

130
00:08:07.600 --> 00:08:10.899
<v Brad Parsons>they want to know how is it going to
impact them on a day to day basis.

131
00:08:10.959 --> 00:08:15.480
<v Brad Parsons>They want to know what their jobs look
like in the future, they want to know what

132
00:08:15.480 --> 00:08:20.179
<v Brad Parsons>tomorrow's like when they come into, you
know, into the shop, uh, into the factory.

133
00:08:20.720 --> 00:08:24.519
<v Brad Parsons>You need to address all those concerns,
um, you know, and that is part of the

134
00:08:24.519 --> 00:08:28.440
<v Brad Parsons>cultural transformation that any
technologies or any solutions in the predictive

135
00:08:28.440 --> 00:08:31.339
<v Brad Parsons>maintenance space, um, have to understand
and compensate for.

136
00:08:33.799 --> 00:08:37.760
<v Niall Sullivan>And look at, yeah, and it's interesting
you mentioned different stakeholders require

137
00:08:37.760 --> 00:08:41.580
<v Niall Sullivan>different, you know, levels of engagement
and, and that kind of thing, but I guess

138
00:08:41.630 --> 00:08:44.619
<v Niall Sullivan>if we go into the actual detail of that in
terms of.

139
00:08:45.380 --> 00:08:49.460
<v Niall Sullivan>You know, how does a culture, you know,
good or bad, sort of affect the deployment

140
00:08:49.460 --> 00:08:53.380
<v Niall Sullivan>of, let's say, predictive maintenance, you
know, what, what, what can affect it,

141
00:08:53.419 --> 00:08:57.520
<v Niall Sullivan>what factors can affect the, the success
or failure, let's say.

142
00:08:58.640 --> 00:09:04.289
<v Brad Parsons>Um, yeah, there's quite a, quite a few, I
mean, I, back to those sort of seas, um,

143
00:09:04.409 --> 00:09:09.690
<v Brad Parsons>you know, does, does the business have a
culture of being able to adopt and adapt

144
00:09:09.690 --> 00:09:10.989
<v Brad Parsons>technology as part of their business?

145
00:09:11.369 --> 00:09:15.809
<v Brad Parsons>Uh, often when you, when we work with, you
know, big multinationals, they actually

146
00:09:15.809 --> 00:09:19.130
<v Brad Parsons>have kind of figured this out a little
bit, and they will have an adoption site, a

147
00:09:19.130 --> 00:09:24.130
<v Brad Parsons>site that they know is innovative, a site
that, you know, is open to new ideas, that

148
00:09:24.130 --> 00:09:25.549
<v Brad Parsons>is open to be challenged.

149
00:09:26.049 --> 00:09:31.489
<v Brad Parsons>And at the plant floor and at the
executive level, there's an understanding that

150
00:09:31.489 --> 00:09:32.369
<v Brad Parsons>mistakes can happen.

151
00:09:32.479 --> 00:09:36.489
<v Brad Parsons>There's an understanding that, um, you
know, there's an adoption and learning curve.

152
00:09:36.640 --> 00:09:41.710
<v Brad Parsons>There, there's an understanding that we
might not have all the answers upfront, but

153
00:09:41.710 --> 00:09:46.000
<v Brad Parsons>we're all sort of driving in the same, in,
in the same direction.

154
00:09:46.570 --> 00:09:48.950
<v Brad Parsons>And I think that's, that's, that's one
element.

155
00:09:49.200 --> 00:09:55.080
<v Brad Parsons>Um, if I look at, The success of
predictive maintenance solutions, there's this sort

156
00:09:55.080 --> 00:10:00.320
<v Brad Parsons>of pivot point, you know, when you get the
basics right in terms of implementation,

157
00:10:00.440 --> 00:10:03.559
<v Brad Parsons>you know, you've got a networking up and
running, you've got the technology

158
00:10:03.559 --> 00:10:04.260
<v Brad Parsons>deployed.

159
00:10:05.039 --> 00:10:11.159
<v Brad Parsons>You get to a point where you've, you've
kind of expanded beyond the, the, the target

160
00:10:11.159 --> 00:10:11.880
<v Brad Parsons>customer segment.

161
00:10:12.000 --> 00:10:14.520
<v Brad Parsons>Say it was the maintenance team, you know,
that's, that's your first target

162
00:10:14.520 --> 00:10:15.000
<v Brad Parsons>audience.

163
00:10:15.739 --> 00:10:19.650
<v Brad Parsons>When you start to mature that solution and
start to evolve that within the business,

164
00:10:19.780 --> 00:10:24.500
<v Brad Parsons>you have to involve other parts of the
business, uh, you know, for, for production's

165
00:10:24.500 --> 00:10:25.570
<v Brad Parsons>the most obvious one, right?

166
00:10:25.669 --> 00:10:31.539
<v Brad Parsons>So, if there is not a culture of working
collaborative, collaboratively, if there's

167
00:10:31.539 --> 00:10:36.780
<v Brad Parsons>not a culture of open and shared
communication, And even shared performance

168
00:10:36.780 --> 00:10:40.419
<v Brad Parsons>indicators, um, there was a guy called,
there's a guy called Drew Troyer, I don't

169
00:10:40.419 --> 00:10:44.619
<v Brad Parsons>know if you you've come across him, but
he's a real maintenance leader, um, and he

170
00:10:44.619 --> 00:10:49.289
<v Brad Parsons>put a note out this morning on, on
LinkedIn, I, I saw that and commented, and he was

171
00:10:49.289 --> 00:10:52.580
<v Brad Parsons>actually talking about culture and
cultural adoption and had a whole bunch of

172
00:10:52.580 --> 00:10:55.580
<v Brad Parsons>recommendations, but I sort of had to
chime in and sort

173
00:10:55.580 --> 00:11:00.570
<v Brad Parsons>of say, you know, in order for businesses
to adopt this broadly, I, I think one of

174
00:11:00.570 --> 00:11:05.020
<v Brad Parsons>the key things that's often overlooked and
missed is, is around performance metrics.

175
00:11:05.799 --> 00:11:09.559
<v Brad Parsons>If you have a team like maintenance and
you have a team like production, and they're

176
00:11:09.559 --> 00:11:14.320
<v Brad Parsons>both being measured on an independent set,
that's fine, but if they don't have

177
00:11:14.320 --> 00:11:18.890
<v Brad Parsons>shared um performance metrics, then
they're working against each other.

178
00:11:19.080 --> 00:11:22.479
<v Brad Parsons>So, maintenance want to take down the
machines so they can do their work, that's

179
00:11:22.479 --> 00:11:23.070
<v Brad Parsons>obvious.

180
00:11:23.479 --> 00:11:27.940
<v Brad Parsons>Production want to keep the machines
running, so they can get their targets as well.

181
00:11:28.280 --> 00:11:34.469
<v Brad Parsons>You've, you've got two polar opposites
trying to compete, uh, really for the same

182
00:11:34.469 --> 00:11:35.479
<v Brad Parsons>time on machines.

183
00:11:36.109 --> 00:11:41.320
<v Brad Parsons>And if you don't have universal metrics,
um, and there's obviously the high ones,

184
00:11:41.440 --> 00:11:46.599
<v Brad Parsons>profitability, you know, um, throughput,
they're the, they're the big ones, but if

185
00:11:46.599 --> 00:11:50.200
<v Brad Parsons>you don't start to target down the shop
floor and do operational performance metrics

186
00:11:50.200 --> 00:11:54.590
<v Brad Parsons>at the floor, the one we like to use, and
it's really the foundation of reliability

187
00:11:54.590 --> 00:11:55.200
<v Brad Parsons>is energy productivity.

188
00:11:56.760 --> 00:12:02.349
<v Brad Parsons>So that's really, How much juice, you
know, how much electricity is required to

189
00:12:02.349 --> 00:12:06.020
<v Brad Parsons>produce an output or a widget or a bottle
or whatever you're producing, maybe in

190
00:12:06.020 --> 00:12:12.869
<v Brad Parsons>food and be, but what that does is unify
those two groups to say, OK, if we run

191
00:12:12.869 --> 00:12:17.789
<v Brad Parsons>this machine harder, the performance of
the machine will decay, it will use more

192
00:12:17.789 --> 00:12:18.510
<v Brad Parsons>energy, right?

193
00:12:18.669 --> 00:12:23.469
<v Brad Parsons>And you may, knowing that, you may, you
may make the call to run that.

194
00:12:23.950 --> 00:12:29.530
<v Brad Parsons>If the priority is production, then you,
you, at that time, you might want to put,

195
00:12:29.750 --> 00:12:34.309
<v Brad Parsons>you know, more productivity through the
business, but if you're getting to the point

196
00:12:34.309 --> 00:12:38.789
<v Brad Parsons>where that cost is driving up too highly,
where it impacts the profitability of the

197
00:12:38.789 --> 00:12:40.750
<v Brad Parsons>business down to the product line,
process.

198
00:12:41.614 --> 00:12:47.065
<v Brad Parsons>bottle, for example, um, then you want to
do that trade-off, um, and that kind of

199
00:12:47.065 --> 00:12:52.065
<v Brad Parsons>metric gives you a unifying way to, to, to
kind of look at it, rather than those

200
00:12:52.065 --> 00:12:56.385
<v Brad Parsons>sort of very high level profitability,
it's very targeted, uh, between those 22

201
00:12:56.385 --> 00:12:57.565
<v Brad Parsons>groups, if that makes sense.

202
00:12:59.010 --> 00:12:59.650
<v Niall Sullivan>No, of course.

203
00:12:59.809 --> 00:13:01.309
<v Niall Sullivan>Uh, no, it does make sense.

204
00:13:01.450 --> 00:13:07.690
<v Niall Sullivan>Um, and I guess, uh, just sort of time
what you're saying, um, together, sorry, time

205
00:13:07.690 --> 00:13:09.169
<v Niall Sullivan>what you're saying together, Brad.

206
00:13:09.250 --> 00:13:14.210
<v Niall Sullivan>Um, I guess a lot of this comes down to
sort of leadership as well, you know, at

207
00:13:14.210 --> 00:13:16.450
<v Niall Sullivan>various different levels, um.

208
00:13:17.080 --> 00:13:19.789
<v Niall Sullivan>Yeah, and leadership sort of pulling
together, so it's not about one person

209
00:13:19.789 --> 00:13:22.710
<v Niall Sullivan>necessarily, but it's like a, a leadership
group pulling together, maybe in those

210
00:13:22.710 --> 00:13:26.590
<v Niall Sullivan>different areas that you mentioned, but
yeah, how important is leadership to this

211
00:13:26.590 --> 00:13:29.109
<v Niall Sullivan>whole, you know, to the success of these
type of projects?

212
00:13:30.219 --> 00:13:34.479
<v Brad Parsons>Ah, I mean, you, you're kind of stating
the obvious, leadership is pretty key, if

213
00:13:34.479 --> 00:13:40.219
<v Brad Parsons>the, if the leaders aren't able to
demonstrate the behavior that they're trying to

214
00:13:40.219 --> 00:13:45.510
<v Brad Parsons>influence and, ah, and the outcomes that
they're trying to achieve, Nobody, no-one

215
00:13:45.510 --> 00:13:46.849
<v Brad Parsons>in their right mind's going to follow it.

216
00:13:46.950 --> 00:13:51.349
<v Brad Parsons>Um, leadership, the leadership have to
demonstrate that the behavior that they want

217
00:13:51.349 --> 00:13:51.820
<v Brad Parsons>to see.

218
00:13:52.070 --> 00:13:57.979
<v Brad Parsons>Now, that, that goes all the way down to,
you know, how do they make decisions, and,

219
00:13:58.059 --> 00:14:03.989
<v Brad Parsons>and the key part of sort of this
predictive, uh, maintenance and digital adoption is

220
00:14:03.989 --> 00:14:10.489
<v Brad Parsons>really transitioning from, What is sort of
hero mentality or what is, we've always

221
00:14:10.489 --> 00:14:14.770
<v Brad Parsons>done it that way, towards more
data-centric behaviors.

222
00:14:14.969 --> 00:14:20.130
<v Brad Parsons>Now, that is a, that is a big shift, you
know, that's a big shift from, um, you

223
00:14:20.130 --> 00:14:24.530
<v Brad Parsons>know, we, we've had people in the plant
for 30 years, and now they've need to look

224
00:14:24.530 --> 00:14:28.969
<v Brad Parsons>at the data, you know, why, why should
they have to go down that, that, that, that

225
00:14:28.969 --> 00:14:29.229
<v Brad Parsons>approach?

226
00:14:29.960 --> 00:14:33.280
<v Brad Parsons>And I think in my experience, you've got
to, you've got to work with both of those

227
00:14:33.280 --> 00:14:39.359
<v Brad Parsons>factors, you've got to transition towards
a data-led, but in doing so, look to the

228
00:14:39.359 --> 00:14:41.479
<v Brad Parsons>experience of the people in the, in, in
the plant.

229
00:14:41.890 --> 00:14:45.200
<v Brad Parsons>They understand these machines and they
understand how to operate them, and they've

230
00:14:45.200 --> 00:14:47.510
<v Brad Parsons>been there a long time, they understand
how these things fail.

231
00:14:48.429 --> 00:14:53.950
<v Brad Parsons>If you're deploying sensors, for example,
you may, this experience may be able to be

232
00:14:53.950 --> 00:15:00.590
<v Brad Parsons>drawn upon to understand at what levels
can we set alarms, at what tolerances can we

233
00:15:00.590 --> 00:15:02.109
<v Brad Parsons>get, you know, can we live with.

234
00:15:02.609 --> 00:15:08.289
<v Brad Parsons>Um, how can, you know, the, the technology
enable the capability that's already

235
00:15:08.289 --> 00:15:08.650
<v Brad Parsons>there.

236
00:15:08.770 --> 00:15:12.750
<v Brad Parsons>We're not, we're not talking about direct
replacement, what we're talking about is,

237
00:15:13.210 --> 00:15:17.989
<v Brad Parsons>um, sort of systemizing the knowledge
that's already there, building that repository

238
00:15:18.250 --> 00:15:20.734
<v Brad Parsons>so you can be, Repeatable and scalable.

239
00:15:21.104 --> 00:15:26.395
<v Brad Parsons>That wealth of knowledge, unfortunately,
in, in a lot of Western worlds is walking

240
00:15:26.395 --> 00:15:27.215
<v Brad Parsons>out the door.

241
00:15:27.354 --> 00:15:32.354
<v Brad Parsons>Um, you know, I'm in my mid-50s, but a lot
of the customers that we talk to and work

242
00:15:32.354 --> 00:15:38.190
<v Brad Parsons>with, um, are in their late 50s, 60s, In a
very short space of time, we're going to

243
00:15:38.190 --> 00:15:39.979
<v Brad Parsons>see a lot of people walking out of the
workforce.

244
00:15:39.989 --> 00:15:45.830
<v Brad Parsons>I, I think the US is, is slightly ahead of
us, uh, but certainly I know that, um, a

245
00:15:45.830 --> 00:15:47.489
<v Brad Parsons>wealth of experience is working out the
door.

246
00:15:47.669 --> 00:15:51.849
<v Brad Parsons>This digital adoption we're talking about,
um, predictive maintenance in particular,

247
00:15:52.190 --> 00:15:57.179
<v Brad Parsons>is an opportunity to help capture that
and, We've seen projects, um, you know, in

248
00:15:57.179 --> 00:16:03.070
<v Brad Parsons>the US and Europe and here in Australia
where that is a goal of the, of the, of the

249
00:16:03.070 --> 00:16:07.340
<v Brad Parsons>transformation, a goal of the project is
to capture that knowledge, capture that

250
00:16:07.340 --> 00:16:13.619
<v Brad Parsons>tacit, um, you know, untouchable knowledge
that, that goes, that has come with these

251
00:16:13.619 --> 00:16:15.400
<v Brad Parsons>people that have been in these plants for
a long time.

252
00:16:16.260 --> 00:16:20.530
<v Brad Parsons>I think that's, that's probably a key
tenement that's probably not understood that,

253
00:16:20.609 --> 00:16:26.520
<v Brad Parsons>that particularly well is when you're
losing that knowledge, these tools are a way

254
00:16:26.520 --> 00:16:27.830
<v Brad Parsons>to capture and retain that.

255
00:16:27.960 --> 00:16:31.559
<v Brad Parsons>Um, so you want to kind of work with the
existing skills that are there, is, is

256
00:16:31.559 --> 00:16:33.679
<v Brad Parsons>probably a, um, a point I'd like to raise
there.

257
00:16:35.650 --> 00:16:39.530
<v Niall Sullivan>And I guess that's an interesting point
what you're saying about the change in

258
00:16:39.530 --> 00:16:43.309
<v Niall Sullivan>workforce, because that also, of course,
means there's a, there's a change in

259
00:16:43.599 --> 00:16:44.559
<v Niall Sullivan>culture as well.

260
00:16:44.690 --> 00:16:48.289
<v Niall Sullivan>I mean, the, the, I guess the two go, they
go hand in hand, and it maybe it's

261
00:16:48.289 --> 00:16:48.469
<v Niall Sullivan>almost.

262
00:16:49.150 --> 00:16:53.669
<v Niall Sullivan>It's almost not, yeah, I guess it's
forcing companies in some respects to, to change

263
00:16:53.669 --> 00:16:57.179
<v Niall Sullivan>their culture is that the workforce
changes and people have been there a long time,

264
00:16:57.270 --> 00:17:01.429
<v Niall Sullivan>maybe with a certain mentality, not all
the time, but, um, a lot of the time, and,

265
00:17:01.510 --> 00:17:06.260
<v Niall Sullivan>and that's leading to this new, new
embrace of technologies like predictive

266
00:17:06.260 --> 00:17:07.089
<v Niall Sullivan>maintenance, maybe.

267
00:17:08.930 --> 00:17:13.459
<v Brad Parsons>Yeah, I mean you can generalize all you
like, um and and you know, you can do a

268
00:17:13.459 --> 00:17:14.160
<v Brad Parsons>little bit of that.

269
00:17:14.300 --> 00:17:20.920
<v Brad Parsons>So I, I guess a younger workforce
generally ah tends to be, tends to be more

270
00:17:21.170 --> 00:17:26.099
<v Brad Parsons>agile at technology adoption, you know, a
lot of the younger, younger workforce is

271
00:17:26.099 --> 00:17:30.819
<v Brad Parsons>so used to technology adoption that, you
know, it's a, it's a core capability or a

272
00:17:30.819 --> 00:17:34.979
<v Brad Parsons>core skill or or even a core behavior in
which they learn to do.

273
00:17:35.560 --> 00:17:41.849
<v Brad Parsons>The younger workforce typically uh looks
to data, um, A, because they don't have the

274
00:17:41.849 --> 00:17:47.609
<v Brad Parsons>experience that an older workforce um can
draw upon, so, providing them with the

275
00:17:47.609 --> 00:17:53.729
<v Brad Parsons>tools um that is, you know, um, really
supported by the workforce that's been there

276
00:17:53.729 --> 00:17:54.520
<v Brad Parsons>a long time.

277
00:17:55.069 --> 00:18:01.250
<v Brad Parsons>Using those tools, gives them a bit of a
leg up and and kind of gets the experience

278
00:18:01.250 --> 00:18:04.709
<v Brad Parsons>to be shared, so we're we're all looking
at the same, the same data, we're all

279
00:18:04.709 --> 00:18:10.089
<v Brad Parsons>looking at the same, Um, piece of paper,
we can all start to learn, and both of

280
00:18:10.089 --> 00:18:14.420
<v Brad Parsons>those groups, um, are going to have
different perspectives, so, you know, they come

281
00:18:14.420 --> 00:18:18.819
<v Brad Parsons>from different backgrounds, they come from
different, um, sort of skills and, and

282
00:18:18.819 --> 00:18:24.140
<v Brad Parsons>experiences, so having, you know, the data
to be there, having the technology to be

283
00:18:24.140 --> 00:18:24.939
<v Brad Parsons>there to,

284
00:18:25.119 --> 00:18:29.729
<v Brad Parsons>to look from two different lenses, um,
same coin, different sides, uh, I think is,

285
00:18:29.739 --> 00:18:31.439
<v Brad Parsons>um, is also invaluable as well.

286
00:18:32.349 --> 00:18:36.640
<v Niall Sullivan>Yeah, and you know, like I said, both both
perspectives, it's almost you're looking

287
00:18:36.640 --> 00:18:40.339
<v Niall Sullivan>for a blend, a blend of both, they both
bring things to the table, right?

288
00:18:40.520 --> 00:18:41.839
<v Niall Sullivan>Lots of positives to the table.

289
00:18:42.239 --> 00:18:45.400
<v Brad Parsons>Absolutely, yeah, just, just before we
came on, we were talking about that sort of

290
00:18:45.400 --> 00:18:50.000
<v Brad Parsons>top down, bottom up, you know, that, those
cult those different cultural aspects.

291
00:18:50.680 --> 00:18:55.239
<v Brad Parsons>Senior leaders have a perspective they're
trying to, to hit, they have goals and

292
00:18:55.239 --> 00:18:56.339
<v Brad Parsons>targets they're trying to hit.

293
00:18:56.890 --> 00:19:01.530
<v Brad Parsons>Uh, people in the shop floor have a
different set of targets, but ultimately, you

294
00:19:01.530 --> 00:19:05.079
<v Brad Parsons>know, they're working towards the same
outcomes, but they're measured differently,

295
00:19:05.209 --> 00:19:07.630
<v Brad Parsons>and I think that's probably kind of key.

296
00:19:08.250 --> 00:19:12.439
<v Brad Parsons>Understanding how people are measured is
probably a, a real indication of, you know,

297
00:19:13.010 --> 00:19:15.000
<v Brad Parsons>the sort of culture that's there.

298
00:19:15.410 --> 00:19:20.250
<v Brad Parsons>Um, trying to understand it, you know, a
person's KPI will, will pretty quickly tell

299
00:19:20.250 --> 00:19:26.699
<v Brad Parsons>you, um, kind of, the behavior that's
going to result from that, and, I guess

300
00:19:27.439 --> 00:19:32.560
<v Brad Parsons>what, you know, any solution needs to, or
any services or any, you know, external

301
00:19:32.560 --> 00:19:38.040
<v Brad Parsons>parties need to be aware of is if you are
driven by really short-term KPIs, really

302
00:19:38.040 --> 00:19:44.500
<v Brad Parsons>short-term uh metrics, then you, you will
get a reactive behavior, you know, because

303
00:19:44.750 --> 00:19:45.239
<v Brad Parsons>that's the

304
00:19:45.239 --> 00:19:46.300
<v Brad Parsons>time and window.

305
00:19:46.709 --> 00:19:51.520
<v Brad Parsons>If if you look at predictive maintenance
um per se, what we're trying to do is take

306
00:19:51.520 --> 00:19:53.900
<v Brad Parsons>the measurement windows out longer and
longer.

307
00:19:54.290 --> 00:19:58.839
<v Brad Parsons>Um, a reactive maintenance is, is a very
short-term perspective.

308
00:19:58.969 --> 00:20:01.050
<v Brad Parsons>It breaks, we fix it, right?

309
00:20:01.140 --> 00:20:06.579
<v Brad Parsons>And if, if that's the horizon and that's
the metrics that have been, um, driven by

310
00:20:06.579 --> 00:20:09.010
<v Brad Parsons>the business, that's the culture that's
been driven by the business.

311
00:20:09.380 --> 00:20:12.939
<v Brad Parsons>What you're trying to do is actually sort
of get, get ahead of the game, you know,

312
00:20:13.060 --> 00:20:19.859
<v Brad Parsons>trying to, Um, rectify the issue long
before it happens, that can tear down existing

313
00:20:19.859 --> 00:20:25.280
<v Brad Parsons>cultures, you know, the, the sort of hero
culture or the prospecting, um, culture,

314
00:20:25.459 --> 00:20:29.619
<v Brad Parsons>you know, we, we wanna get in, we wanna
see something, we wanna fix it, um, we wanna

315
00:20:29.619 --> 00:20:32.650
<v Brad Parsons>see those gold nuggets and get those
immediate rewards.

316
00:20:33.020 --> 00:20:37.650
<v Brad Parsons>Um, with, I, I, I'll give you an example
from, from sort of my previous work with

317
00:20:37.650 --> 00:20:43.020
<v Brad Parsons>Movis, sometimes you can predict a failure
many, many months in advance.

318
00:20:43.640 --> 00:20:50.280
<v Brad Parsons>Now, that from, from someone who's used to
working on a week to week, day to day

319
00:20:50.280 --> 00:20:55.920
<v Brad Parsons>basis, that is just well beyond the scope
of, of, of, um, you know, contemplation.

320
00:20:56.959 --> 00:21:01.439
<v Brad Parsons>I can think of a particular example with a
customer um who's in the building

321
00:21:01.439 --> 00:21:02.270
<v Brad Parsons>services business.

322
00:21:02.520 --> 00:21:08.800
<v Brad Parsons>They had these big concrete vats and the
vats would mix, and the, the, the concrete

323
00:21:08.800 --> 00:21:10.619
<v Brad Parsons>had to stay mixed.

324
00:21:11.000 --> 00:21:15.500
<v Brad Parsons>As soon as the mixer failed, no surprise,
the concrete had all set.

325
00:21:16.000 --> 00:21:21.939
<v Brad Parsons>Now, you can imagine when you've got a
significant vat of concrete.

326
00:21:22.439 --> 00:21:27.119
<v Brad Parsons>What happens when you need to try and, um,
you know, take the concrete out, it is a

327
00:21:27.119 --> 00:21:27.829
<v Brad Parsons>significant amount of effort.

328
00:21:27.880 --> 00:21:32.959
<v Brad Parsons>We're talking weeks of work and
jackhammers and, you know, long nights, um, not an

329
00:21:32.959 --> 00:21:33.939
<v Brad Parsons>ideal situation.

330
00:21:34.680 --> 00:21:39.880
<v Brad Parsons>When we spoke to the business and said,
you know, this, this uh particular VAT is

331
00:21:39.880 --> 00:21:43.520
<v Brad Parsons>not looking good, we're seeing a trend
that, that is, you know, heading towards a

332
00:21:43.520 --> 00:21:44.020
<v Brad Parsons>failure.

333
00:21:44.959 --> 00:21:49.239
<v Brad Parsons>Their first question was, well, well, how
long, and we sort of said, well, it could

334
00:21:49.239 --> 00:21:53.060
<v Brad Parsons>be in the order of sort of 2 months, 2 to
3 months away.

335
00:21:53.560 --> 00:21:54.859
<v Brad Parsons>Oh, no problems.

336
00:21:55.040 --> 00:21:59.660
<v Brad Parsons>The next question we asked you if it was
to fail, what were your next steps?

337
00:22:00.619 --> 00:22:03.459
<v Brad Parsons>So the next steps while, while we send in
a replacement.

338
00:22:03.739 --> 00:22:06.010
<v Brad Parsons>How many replacements do you have in the
country?

339
00:22:06.699 --> 00:22:07.829
<v Brad Parsons>Well, that's a good question.

340
00:22:08.219 --> 00:22:09.280
<v Brad Parsons>We'll, we'll come back to you.

341
00:22:09.939 --> 00:22:12.119
<v Brad Parsons>The long, long story short, they only had
one.

342
00:22:12.500 --> 00:22:15.760
<v Brad Parsons>It was at a particular plant, it was
already set aside for another purpose.

343
00:22:16.140 --> 00:22:17.619
<v Brad Parsons>So in reality, they had none.

344
00:22:18.540 --> 00:22:23.300
<v Brad Parsons>So, you know, the predictive maintenance
tool was then used to track the

345
00:22:23.300 --> 00:22:29.180
<v Brad Parsons>deterioration of that asset over a couple
of months, and they would be able, they

346
00:22:29.180 --> 00:22:34.660
<v Brad Parsons>were able to nurse it towards the next uh
major shutdown and they were able to ship

347
00:22:34.660 --> 00:22:36.000
<v Brad Parsons>in a replacement unit.

348
00:22:37.010 --> 00:22:40.900
<v Brad Parsons>That was something that was a real wake-up
call for the business.

349
00:22:41.209 --> 00:22:43.439
<v Brad Parsons>Out of that, we got literally a global
deployment.

350
00:22:43.689 --> 00:22:50.229
<v Brad Parsons>It was an iconic um event that had
happened that really saved the business

351
00:22:50.569 --> 00:22:56.369
<v Brad Parsons>because it was, you know, a fairly
critical asset uh within the plant, but it was an

352
00:22:56.369 --> 00:23:00.770
<v Brad Parsons>example on which everyone could kind of
relate to and latch onto, and I think

353
00:23:00.770 --> 00:23:07.479
<v Brad Parsons>that's, when you're looking at culture,
um, you need to have, You know, I wanna say

354
00:23:07.479 --> 00:23:12.280
<v Brad Parsons>it, you wanna have heroes or you wanna
have good examples, you wanna have um you

355
00:23:12.280 --> 00:23:12.819
<v Brad Parsons>know,

356
00:23:14.000 --> 00:23:15.900
<v Brad Parsons>examples that people can relate to.

357
00:23:16.939 --> 00:23:21.180
<v Brad Parsons>And I think that's, you know, where
solution providers and where customers in their

358
00:23:21.180 --> 00:23:25.819
<v Brad Parsons>transformation journeys need to understand
that those early examples are absolute

359
00:23:25.819 --> 00:23:32.479
<v Brad Parsons>gold because they represent a future that
the existing um culture doesn't have.

360
00:23:32.900 --> 00:23:38.819
<v Brad Parsons>So, these shared stories, um, these ways
in which they can, um, you know, kind of

361
00:23:38.819 --> 00:23:43.060
<v Brad Parsons>communicate value about where we're going
and why we're going, and, you know, maybe

362
00:23:43.060 --> 00:23:49.459
<v Brad Parsons>it's a safety issue, I've seen other
examples where a multi, sort of 3 to 5 m fan,

363
00:23:50.060 --> 00:23:55.219
<v Brad Parsons>um, woke up the supervisor in the middle
of the night with a critical failure that

364
00:23:55.219 --> 00:23:55.819
<v Brad Parsons>was imminent.

365
00:23:56.479 --> 00:24:02.209
<v Brad Parsons>Now that, unfortunately, and and I guess
fortunately, that critical fan, if it had

366
00:24:02.209 --> 00:24:06.430
<v Brad Parsons>have sheared off, would have went through
a populated area about 3 a.m.

367
00:24:06.430 --> 00:24:11.250
<v Brad Parsons>in the morning, um, and, you know,
seriously could, could have done some damage.

368
00:24:11.319 --> 00:24:14.300
<v Brad Parsons>There's humans there, the guards weren't
up to scratch.

369
00:24:14.839 --> 00:24:18.140
<v Brad Parsons>They hadn't, you know, kept the
maintenance up.

370
00:24:18.319 --> 00:24:22.359
<v Brad Parsons>It would have torn through the guards, it
would have, you know, heaven forbid, torn

371
00:24:22.359 --> 00:24:23.020
<v Brad Parsons>through people.

372
00:24:23.479 --> 00:24:30.280
<v Brad Parsons>Um, but again, safety, um, a shared
example, this is why we kind of need

373
00:24:30.280 --> 00:24:37.150
<v Brad Parsons>this technology, um, anchoring, anchoring
to existing, um, cultural norms, uh,

374
00:24:37.239 --> 00:24:38.500
<v Brad Parsons>for example, safety.

375
00:24:39.540 --> 00:24:44.670
<v Brad Parsons>Um, is what we're looking to do, um,
because then it becomes much easier for that

376
00:24:44.670 --> 00:24:49.390
<v Brad Parsons>transformation of that culture, because it
is already reinforcing an existing

377
00:24:49.390 --> 00:24:53.069
<v Brad Parsons>culture, that might be saving money, that
might be safety, that might be, you know,

378
00:24:53.260 --> 00:24:57.589
<v Brad Parsons>half a dozen different things, but make
sure it reinforces an existing culture

379
00:24:57.589 --> 00:25:01.949
<v Brad Parsons>that's already there would be, you know,
how I'd, how I'd kind of try and phrase

380
00:25:01.949 --> 00:25:02.290
<v Brad Parsons>that.

381
00:25:03.520 --> 00:25:03.910
<v Niall Sullivan>Yeah.

382
00:25:04.189 --> 00:25:07.589
<v Niall Sullivan>No, um, and, um, uh, there's really good
examples there as well.

383
00:25:07.680 --> 00:25:11.959
<v Niall Sullivan>I mean, we, we tend to, you know, when
we're talking to customers, it's not, uh, we

384
00:25:11.959 --> 00:25:15.400
<v Niall Sullivan>see it's, well, it's crucial really, both,
both for us to, you know, to see the

385
00:25:15.400 --> 00:25:19.400
<v Niall Sullivan>success, but also for more importantly for
customers to, to see the success and then

386
00:25:19.400 --> 00:25:20.829
<v Niall Sullivan>share that success internally.

387
00:25:21.040 --> 00:25:24.319
<v Niall Sullivan>So we capture the sort of asset, what we
call the asset successes.

388
00:25:24.430 --> 00:25:29.719
<v Niall Sullivan>So, if, um, Sensai spots an an issue with
machine, it saves, you know, 24 hours in

389
00:25:29.719 --> 00:25:31.880
<v Niall Sullivan>downtime, and we even add.

390
00:25:32.089 --> 00:25:35.609
<v Niall Sullivan>You know, some of the guidance our sort of
co-pilot gave, which led to it as well.

391
00:25:35.979 --> 00:25:38.160
<v Niall Sullivan>But there's actually a really good
podcast, which I think I've shared with you,

392
00:25:38.229 --> 00:25:43.130
<v Niall Sullivan>Brad, from our customer BlueScope Steel
where, um, Chris Banson from the Blue Scope

393
00:25:43.130 --> 00:25:47.650
<v Niall Sullivan>team actually describes this in a lot of
detail, how it sort of, uh, and, again, for

394
00:25:47.650 --> 00:25:50.819
<v Niall Sullivan>them, it was the safety issue was they had
to.

395
00:25:51.459 --> 00:25:55.430
<v Niall Sullivan>You know, it, it, because it was quite a
dangerous, tricky part to get to, to

396
00:25:55.430 --> 00:25:56.109
<v Niall Sullivan>actually fix it.

397
00:25:56.189 --> 00:25:58.859
<v Niall Sullivan>So it's actually a risk to actually go in,
so they wanted to make sure they did it

398
00:25:58.859 --> 00:26:03.459
<v Niall Sullivan>at the right time with the right, uh, so
again, it's a, it's a safety measure in

399
00:26:03.459 --> 00:26:03.869
<v Niall Sullivan>mind.

400
00:26:04.069 --> 00:26:08.550
<v Niall Sullivan>So, um, so from your point of view,
capturing the successes and communicating them

401
00:26:08.550 --> 00:26:10.890
<v Niall Sullivan>internally is how you breed this culture
of.

402
00:26:11.310 --> 00:26:15.130
<v Niall Sullivan>You know, adoption around predictor
maintenance and building sort of momentum behind

403
00:26:15.130 --> 00:26:18.569
<v Niall Sullivan>that deployment, I guess, the global
deployment, if you want to call it that.

404
00:26:19.150 --> 00:26:25.069
<v Brad Parsons>Yeah, absolutely, find sites, as I said
before, find sites that are ready, they are

405
00:26:25.069 --> 00:26:30.430
<v Brad Parsons>willing, they are able to, to kind of have
those change, you know, typically, as I

406
00:26:30.430 --> 00:26:34.640
<v Brad Parsons>said, um, iconic sites, there will be a
technology adoption plan for the more

407
00:26:34.640 --> 00:26:36.739
<v Brad Parsons>established multinational players.

408
00:26:36.790 --> 00:26:42.560
<v Brad Parsons>There will be a site, That uh typically
receives the technology first because the

409
00:26:42.560 --> 00:26:46.400
<v Brad Parsons>culture is there to support it, and if it,
and if it's not a single site, maybe it's

410
00:26:46.400 --> 00:26:51.199
<v Brad Parsons>a supervisor, maybe it's a particular part
of the plan, um, who is open to new

411
00:26:51.199 --> 00:26:55.630
<v Brad Parsons>ideas, who is willing to experiment, who's
willing to learn and willing to fail, um,

412
00:26:55.719 --> 00:26:59.359
<v Brad Parsons>you know, nothing, nothing's perfect, um,
but that's the kind of culture you're

413
00:26:59.359 --> 00:27:02.439
<v Brad Parsons>trying to look for uh in the adoption of
predictive maintenance.

414
00:27:03.719 --> 00:27:08.089
<v Niall Sullivan>And I've been looking to um ask this
question throughout and it's one that's

415
00:27:08.089 --> 00:27:11.250
<v Niall Sullivan>actually towards the beginning of the, the
list cos it actually sort of makes sense

416
00:27:11.250 --> 00:27:11.489
<v Niall Sullivan>cos.

417
00:27:11.989 --> 00:27:16.030
<v Niall Sullivan>Is, I wanted to ask about sort of a
definition of predictive maintenance because

418
00:27:16.030 --> 00:27:19.229
<v Niall Sullivan>I'm, and I'm wondering whether that
affects the culture as well.

419
00:27:19.310 --> 00:27:21.989
<v Niall Sullivan>So if you have one part of the
organization thinks, oh, predictive maintenance is

420
00:27:21.989 --> 00:27:25.530
<v Niall Sullivan>this, this and this, and the other part of
the organization or different, you know,

421
00:27:25.839 --> 00:27:30.869
<v Niall Sullivan>the production to senior leadership,
everyone has a different, um, uh, a different

422
00:27:30.869 --> 00:27:33.800
<v Niall Sullivan>interpretation of predictive maintenance,
and I know from the market.

423
00:27:34.130 --> 00:27:38.290
<v Niall Sullivan>There's a lot of thing, a lot of products,
you know, in the market that say they do

424
00:27:38.290 --> 00:27:42.280
<v Niall Sullivan>predictive maintenance or AI or whatever,
and they, and they don't really, in

425
00:27:42.280 --> 00:27:44.630
<v Niall Sullivan>reality, it's sort of an empty cupboard.

426
00:27:44.810 --> 00:27:48.880
<v Niall Sullivan>So does that cause some friction in terms
of, like, in, in terms of the culture,

427
00:27:48.890 --> 00:27:51.290
<v Niall Sullivan>because maybe some, and it may be.

428
00:27:51.385 --> 00:27:52.704
<v Niall Sullivan>Expectations are all messed up as well.

429
00:27:52.824 --> 00:27:55.744
<v Niall Sullivan>Someone has some big expectations here or
maybe low expectations here.

430
00:27:55.905 --> 00:27:56.425
<v Niall Sullivan>I don't know,

431
00:27:56.505 --> 00:28:02.265
<v Brad Parsons>but I, I think you, I think you're really
spot on when you say that.

432
00:28:02.425 --> 00:28:05.285
<v Brad Parsons>There, there is definitely a misalignment
of expectations.

433
00:28:05.665 --> 00:28:11.265
<v Brad Parsons>If, if you look at traditionally
maintenance environments, preventative maintenance,

434
00:28:11.775 --> 00:28:15.744
<v Brad Parsons>everyone understands that um reactive
maintenance, everyone understands that, and

435
00:28:15.744 --> 00:28:19.969
<v Brad Parsons>you may have, Uh, you may have
preventative maintenance with condition monitoring,

436
00:28:20.119 --> 00:28:23.000
<v Brad Parsons>right, so that might be part of it, you
might have robiology, you might have a

437
00:28:23.000 --> 00:28:27.040
<v Brad Parsons>vibration expert or a VA that comes in,
does your vibration analysis.

438
00:28:27.770 --> 00:28:32.530
<v Brad Parsons>You know, every, you know, a couple of
weeks or a month, um, what we're talking

439
00:28:32.530 --> 00:28:38.160
<v Brad Parsons>about when we're talking um predictive
maintenance is you're going from this, um,

440
00:28:38.489 --> 00:28:43.489
<v Brad Parsons>human supported decisions, which is those
reactive and preventive, so they're very

441
00:28:43.489 --> 00:28:45.000
<v Brad Parsons>human-centered decisions.

442
00:28:45.410 --> 00:28:49.599
<v Brad Parsons>What we're talking about is with uh
predictive maintenance is more data-centered

443
00:28:49.599 --> 00:28:51.150
<v Brad Parsons>decisions, and that's probably the key.

444
00:28:51.729 --> 00:28:58.699
<v Brad Parsons>What people often miss is there is there a
transition step and, The willingness to

445
00:28:58.699 --> 00:29:03.780
<v Brad Parsons>change your maintenance strategy, even if
it's not across the whole business, is

446
00:29:03.780 --> 00:29:05.300
<v Brad Parsons>really key to this transformation.

447
00:29:05.939 --> 00:29:10.020
<v Brad Parsons>Transitioning from a preventative, sorry,
preventative maintenance towards a

448
00:29:10.020 --> 00:29:13.979
<v Brad Parsons>predictive maintenance is a key step in
between, and that's condition-based

449
00:29:13.979 --> 00:29:14.599
<v Brad Parsons>maintenance.

450
00:29:14.939 --> 00:29:20.859
<v Brad Parsons>So are we using the condition of the
machine to drive the prioritization,

451
00:29:21.969 --> 00:29:25.900
<v Brad Parsons>Of when that maintenance happens and
potentially what maintenance happens, it

452
00:29:25.900 --> 00:29:27.880
<v Brad Parsons>depends on how, how advanced you are.

453
00:29:28.420 --> 00:29:34.479
<v Brad Parsons>I think predictive maintenance, the key
part is really, is it data enabled decision

454
00:29:34.479 --> 00:29:39.099
<v Brad Parsons>making, uh, you could go down further down
the track and say, oh, prescriptive, but

455
00:29:39.099 --> 00:29:45.660
<v Brad Parsons>I think one of the things that uh I do
really wanna call out is, Predictive

456
00:29:45.660 --> 00:29:49.310
<v Brad Parsons>maintenance is more than identification of
maintenance.

457
00:29:49.719 --> 00:29:54.339
<v Brad Parsons>Let, let's say you identify that, that VAT
was gonna fail next Thursday.

458
00:29:55.060 --> 00:30:01.750
<v Brad Parsons>You need to predict, you know, and
schedule, am I gonna have a

459
00:30:01.750 --> 00:30:07.310
<v Brad Parsons>person that's trained, skilled and able to
maintain that machine next Thursday?

460
00:30:07.869 --> 00:30:10.630
<v Brad Parsons>Am I gonna have the spare parts available?

461
00:30:10.989 --> 00:30:15.540
<v Brad Parsons>Am I gonna be able to get access to the
plant and shut down that production line,

462
00:30:15.589 --> 00:30:15.969
<v Brad Parsons>for example?

463
00:30:17.410 --> 00:30:24.010
<v Brad Parsons>Do I have all of the elements in place to
enable that predictive maintenance

464
00:30:24.010 --> 00:30:24.819
<v Brad Parsons>strategy?

465
00:30:25.130 --> 00:30:29.849
<v Brad Parsons>Otherwise, what happens, and I've seen it,
and this is the miscommunication of, of

466
00:30:29.849 --> 00:30:36.569
<v Brad Parsons>expectations, you can predict an asset
will fail and you can do absolutely nothing

467
00:30:36.569 --> 00:30:37.010
<v Brad Parsons>about it.

468
00:30:39.140 --> 00:30:39.660
<v Brad Parsons>All right.

469
00:30:40.650 --> 00:30:45.439
<v Brad Parsons>And that's, that's a real thing that
absolutely happens day in day out.

470
00:30:45.739 --> 00:30:47.670
<v Brad Parsons>There's no point in predicting.

471
00:30:48.510 --> 00:30:53.329
<v Brad Parsons>You know, weeks and months in advance, if
you don't have the capability to take

472
00:30:53.329 --> 00:30:53.910
<v Brad Parsons>action.

473
00:30:54.640 --> 00:30:57.780
<v Brad Parsons>Otherwise that, you know, that's a fairy
tale, and.

474
00:30:58.819 --> 00:31:05.619
<v Brad Parsons>To get cultural adoption, to get cultural
acceptance, it's more than identification

475
00:31:05.619 --> 00:31:07.680
<v Brad Parsons>of a failure in advance.

476
00:31:08.180 --> 00:31:12.939
<v Brad Parsons>It's about a systems view, and this is
really predictive maintenance, this is what

477
00:31:12.939 --> 00:31:19.380
<v Brad Parsons>we're missing in the thinking is, do we
have the full systems to not only identify

478
00:31:19.380 --> 00:31:24.699
<v Brad Parsons>it, but to schedule it, to plan it, to
prioritize it, and to complete it.

479
00:31:25.160 --> 00:31:29.680
<v Brad Parsons>And then the backside of that predictive
maintenance is, do we have the data to

480
00:31:29.680 --> 00:31:33.130
<v Brad Parsons>support the decision that we made to say
it was a good one?

481
00:31:34.420 --> 00:31:41.229
<v Brad Parsons>Are we in a feedback loop where the data,
um, the data that supported

482
00:31:41.229 --> 00:31:44.540
<v Brad Parsons>the decision is reinforced by the action
taken?

483
00:31:45.030 --> 00:31:50.989
<v Brad Parsons>You may predict that um you're gonna get
an impeller failure on a pump, but if you

484
00:31:50.989 --> 00:31:54.969
<v Brad Parsons>pull open the impeller, if you pull open
the pump and find there's nothing wrong

485
00:31:54.969 --> 00:31:59.849
<v Brad Parsons>with the impeller, it's a really great way
culturally to kill your program.

486
00:32:00.750 --> 00:32:05.709
<v Brad Parsons>Because, you know, the boy who cried wolf,
that's not going to happen too many

487
00:32:05.709 --> 00:32:06.410
<v Brad Parsons>times.

488
00:32:07.069 --> 00:32:13.910
<v Brad Parsons>If you don't have the technology to do
that, but if you also aren't preparing them

489
00:32:13.910 --> 00:32:19.170
<v Brad Parsons>for the fact that it might be the Ampella,
but it might be these three other things,

490
00:32:19.989 --> 00:32:24.630
<v Brad Parsons>give them the data to be able to
understand that, then you're kind of missing the

491
00:32:24.630 --> 00:32:28.369
<v Brad Parsons>trick, you're killing your cultural
adoption at the very start, so.

492
00:32:29.219 --> 00:32:34.890
<v Brad Parsons>In short, it's a systems-based change, but
it's also a behavior change.

493
00:32:34.979 --> 00:32:38.979
<v Brad Parsons>We need to kind of, we're changing the
systems in which, uh, you know, the plant

494
00:32:38.979 --> 00:32:42.780
<v Brad Parsons>works, but we're also changing the, the
mindset and the behavior of those people in

495
00:32:42.780 --> 00:32:43.410
<v Brad Parsons>the plant.

496
00:32:43.939 --> 00:32:47.819
<v Brad Parsons>We're setting their expectations, as you
said at the start, um, we've got, we've

497
00:32:47.819 --> 00:32:50.900
<v Brad Parsons>gotta manage the expectations on both of
those accounts.

498
00:32:53.209 --> 00:32:54.930
<v Niall Sullivan>No, fantastic, fantastic.

499
00:32:55.369 --> 00:33:00.839
<v Niall Sullivan>Um, and I guess as, as we sort of come
towards the end, um, of our, of our time, um,

500
00:33:00.920 --> 00:33:04.969
<v Niall Sullivan>what we used to do on the podcast, Brad,
is sort of summarize, you know, you know,

501
00:33:05.089 --> 00:33:08.089
<v Niall Sullivan>we've, we've covered quite a lot of
ground, there's been really fascinating

502
00:33:08.089 --> 00:33:08.810
<v Niall Sullivan>conversation, but I guess.

503
00:33:09.880 --> 00:33:12.790
<v Niall Sullivan>And I think it's a bit of an unfair
question because there's so many facts involved

504
00:33:12.790 --> 00:33:17.170
<v Niall Sullivan>and, um, it's not, as, as we've discussed,
it's not an easy thing to achieve, but if

505
00:33:17.170 --> 00:33:21.170
<v Niall Sullivan>someone is looking to adopt predictive
maintenance and they, uh, and they're

506
00:33:21.170 --> 00:33:24.569
<v Niall Sullivan>thinking about, you know, the cultural
side of things, how do they, how can they get

507
00:33:24.569 --> 00:33:24.880
<v Niall Sullivan>their.

508
00:33:25.579 --> 00:33:29.819
<v Niall Sullivan>Organisations be engaged with the project,
understand the project, what we're trying

509
00:33:29.819 --> 00:33:32.969
<v Niall Sullivan>to achieve and bring in stakeholders
together, what, what would be those sort of

510
00:33:32.969 --> 00:33:36.219
<v Niall Sullivan>initial steps to think about, even though
there's a lot to consider, maybe there's

511
00:33:36.219 --> 00:33:40.359
<v Niall Sullivan>some sort of initial steps just to think
through first, maybe.

512
00:33:41.260 --> 00:33:47.369
<v Brad Parsons>Yeah, I think the success or failure of a
predictive maintenance project is not

513
00:33:47.369 --> 00:33:48.160
<v Brad Parsons>about technology.

514
00:33:48.790 --> 00:33:53.390
<v Brad Parsons>It, it, it's about any meaningful change,
whether it's predictive maintenance or

515
00:33:53.390 --> 00:33:55.569
<v Brad Parsons>others, is about the people.

516
00:33:56.829 --> 00:34:01.750
<v Brad Parsons>You know, foremost, this is about helping
people to move from one state to another,

517
00:34:01.790 --> 00:34:03.550
<v Brad Parsons>and this is exactly what we're talking
about.

518
00:34:03.630 --> 00:34:05.449
<v Brad Parsons>This is, this is cultural adoption.

519
00:34:06.069 --> 00:34:10.469
<v Brad Parsons>The, the projects that in my experience
that I've seen are most successful, it's got

520
00:34:10.469 --> 00:34:14.629
<v Brad Parsons>nothing to do with how fancy the sex or
sexy the dashboards are or the, or the

521
00:34:14.629 --> 00:34:15.489
<v Brad Parsons>sensors are.

522
00:34:16.159 --> 00:34:22.330
<v Brad Parsons>But it, it's about those that those
customers or those projects where the data is

523
00:34:22.330 --> 00:34:23.070
<v Brad Parsons>trusted.

524
00:34:23.409 --> 00:34:28.689
<v Brad Parsons>If you get the trust from the data, then
the decisions can follow that, then the

525
00:34:28.689 --> 00:34:34.850
<v Brad Parsons>actions can happen from that, then the
success comes and that success breeds

526
00:34:34.850 --> 00:34:35.149
<v Brad Parsons>success.

527
00:34:35.250 --> 00:34:41.939
<v Brad Parsons>The more reinforced behavior that you get,
the more um, You know, the more the, the,

528
00:34:42.000 --> 00:34:47.050
<v Brad Parsons>the, the guy on the plant floor goes home
and says, you wouldn't believe it, this

529
00:34:47.060 --> 00:34:51.219
<v Brad Parsons>technology saved my bacon, whether it's a
safety incident, unfortunately, or

530
00:34:51.219 --> 00:34:56.419
<v Brad Parsons>hopefully not, whether it's shutting down
the you know, production, uh, you know,

531
00:34:56.560 --> 00:34:58.879
<v Brad Parsons>managed to avoid um shutting down
production.

532
00:34:59.419 --> 00:35:02.540
<v Brad Parsons>Over the next year, uh, I guess over the
next few years, we're just going to see

533
00:35:02.540 --> 00:35:04.770
<v Brad Parsons>more and more of that, and I've been
working on this for 10 years.

534
00:35:04.820 --> 00:35:07.000
<v Brad Parsons>I started Movis back in 2015, so.

535
00:35:07.399 --> 00:35:13.800
<v Brad Parsons>I've seen the transformation, but we're
now at a point where the technology is, is

536
00:35:13.800 --> 00:35:15.000
<v Brad Parsons>in a really good state.

537
00:35:15.110 --> 00:35:20.459
<v Brad Parsons>The Senseii product's fantastic, and the
reason why I'm so excited about Sensei is

538
00:35:20.560 --> 00:35:23.280
<v Brad Parsons>it pulls from multiple data sources.

539
00:35:23.479 --> 00:35:27.479
<v Brad Parsons>We're not looking at a single source,
we're looking at multiple perspectives, and

540
00:35:27.479 --> 00:35:32.679
<v Brad Parsons>that's really the fundamentals of success
in predictive maintenance is enabling our

541
00:35:32.679 --> 00:35:36.979
<v Brad Parsons>workforce to work collaboratively,
collaboratively to work together.

542
00:35:37.780 --> 00:35:43.149
<v Brad Parsons>To work on common metrics, to work on
common data, and that's what, that's what

543
00:35:43.149 --> 00:35:45.550
<v Brad Parsons>really um cultural success is for me.

544
00:35:46.030 --> 00:35:51.280
<v Brad Parsons>When you get a group of people working
together towards the same goals, um,

545
00:35:51.389 --> 00:35:56.310
<v Brad Parsons>operating, you know, in the same channel,
uh, I think that's where we get the

546
00:35:56.310 --> 00:36:01.260
<v Brad Parsons>success and, just deploying technology for
technology's sake will not get you there.

547
00:36:01.520 --> 00:36:03.889
<v Brad Parsons>Having a group of people working together.

548
00:36:04.790 --> 00:36:08.399
<v Brad Parsons>In unison, that's where all the successes
are gonna happen, that's where all the

549
00:36:08.399 --> 00:36:12.060
<v Brad Parsons>wins uh are happening in my experience
over the last couple of years.

550
00:36:12.520 --> 00:36:16.949
<v Brad Parsons>That's probably the best summary I can
get, but really the reality is, we talked

551
00:36:16.949 --> 00:36:23.060
<v Brad Parsons>about it earlier, if you have a workforce
that's transitioning out, this kind of

552
00:36:23.060 --> 00:36:27.739
<v Brad Parsons>technology is not about pure growth, this
is about survival.

553
00:36:28.360 --> 00:36:33.959
<v Brad Parsons>Your skills and your experience are going
out the door, um, this kind of technology

554
00:36:33.959 --> 00:36:35.310
<v Brad Parsons>will keep you on par.

555
00:36:35.909 --> 00:36:39.989
<v Brad Parsons>How well you're able to deploy and, and
implement that within your culture, within

556
00:36:39.989 --> 00:36:43.040
<v Brad Parsons>your business will determine how
successful you are after that.

557
00:36:43.159 --> 00:36:48.459
<v Brad Parsons>So, we're looking at steady-state, um,
successful deployments and cultural adoptions

558
00:36:48.719 --> 00:36:50.280
<v Brad Parsons>will be the determining factor.

559
00:36:52.260 --> 00:36:55.229
<v Niall Sullivan>Excellent, and that's, that's really,
that's really great advice for people to take

560
00:36:55.229 --> 00:37:01.260
<v Niall Sullivan>away, um, but I guess also Brad, just to,
just as we finish, in terms of if people

561
00:37:01.260 --> 00:37:05.580
<v Niall Sullivan>want to find out more about you and, and
reliability and, and what you're doing,

562
00:37:05.629 --> 00:37:08.889
<v Niall Sullivan>what, where are the best places for them
to, to, to do that?

563
00:37:09.510 --> 00:37:11.850
<v Brad Parsons>Uh, by all means, hit, hit me up on
LinkedIn.

564
00:37:12.030 --> 00:37:14.649
<v Brad Parsons>Um, I've got thousands and thousands of
followers.

565
00:37:14.790 --> 00:37:20.169
<v Brad Parsons>Um, I've been on LinkedIn, I think since
about 2003, I think I was in very early,

566
00:37:20.429 --> 00:37:20.989
<v Brad Parsons>um.

567
00:37:21.489 --> 00:37:23.370
<v Brad Parsons>But yeah, I'm, I'm pretty active on
LinkedIn.

568
00:37:23.409 --> 00:37:26.949
<v Brad Parsons>If you ping me, I'll get back to you
pretty quickly and then probably in 24 hours.

569
00:37:28.090 --> 00:37:28.500
<v Niall Sullivan>Fantastic.

570
00:37:28.620 --> 00:37:32.620
<v Niall Sullivan>Well, um, yeah, we'll add a link to your,
your, um, profile in the, in the show

571
00:37:32.620 --> 00:37:35.560
<v Niall Sullivan>notes as well so people can easily reach
out to you.

572
00:37:35.699 --> 00:37:38.860
<v Niall Sullivan>Um, but hopefully we'll also have you back
on the podcast as well, just throwing

573
00:37:38.860 --> 00:37:40.840
<v Niall Sullivan>that out there, um, and putting it on the
record.

574
00:37:41.580 --> 00:37:45.100
<v Niall Sullivan>Um, but no, it's been, it's been really
great to, um, to chat and just get an

575
00:37:45.100 --> 00:37:49.459
<v Niall Sullivan>external perspective cos like I said, we
do talk a lot about it in, in Siemens and.

576
00:37:49.729 --> 00:37:53.969
<v Niall Sullivan>And the, the Sensai platform, um, and Doc
Dopship it's really great to get that

577
00:37:53.969 --> 00:37:56.449
<v Niall Sullivan>external perspective and from all the
projects you've been on.

578
00:37:56.520 --> 00:38:01.169
<v Niall Sullivan>So thank you, um, so much for your time
and for staying so late as well, um, in your

579
00:38:01.169 --> 00:38:02.070
<v Niall Sullivan>day, um.

580
00:38:03.379 --> 00:38:08.340
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

581
00:38:08.340 --> 00:38:11.719
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
