WEBVTT
Language: en-US

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

2
00:00:06.219 --> 00:00:06.719
<v Speaker 1>Sullivan.

3
00:00:08.359 --> 00:00:13.020
<v Niall Sullivan>Hello, and welcome to this episode of the
trend detection, um, podcast.

4
00:00:13.439 --> 00:00:16.370
<v Niall Sullivan>Um, I'm really pleased, it's, uh, quite a
special episode today.

5
00:00:16.510 --> 00:00:20.180
<v Niall Sullivan>And we've got, um, one of our customers,
Chris from Blue Scope Steel.

6
00:00:20.639 --> 00:00:23.479
<v Niall Sullivan>Um, and we've got a really interesting
discussion today about, it's actually about a

7
00:00:23.479 --> 00:00:28.639
<v Niall Sullivan>particular success case, um, that, um,
that recently came, came through to us, which

8
00:00:28.639 --> 00:00:29.549
<v Niall Sullivan>is really fantastic.

9
00:00:29.600 --> 00:00:31.219
<v Niall Sullivan>We're gonna dive into exactly.

10
00:00:32.098 --> 00:00:36.138
<v Niall Sullivan>Um, what, what had happened and how that
was resolved with the help of, um, of

11
00:00:36.138 --> 00:00:40.179
<v Niall Sullivan>Sensai as well, but I guess before we get
started I'll just hand over to, um, to

12
00:00:40.179 --> 00:00:41.578
<v Niall Sullivan>Chris just to introduce yourself.

13
00:00:41.618 --> 00:00:42.558
<v Niall Sullivan>So over to you, Chris.

14
00:00:43.689 --> 00:00:44.189
<v Speaker 3>Yeah, good day.

15
00:00:44.240 --> 00:00:44.830
<v Speaker 3>My name's Chris.

16
00:00:44.880 --> 00:00:49.720
<v Speaker 3>I work for BlueScope Steel out of our Port
Kembla site, which is in Australia.

17
00:00:49.830 --> 00:00:53.419
<v Speaker 3>Um, I have a background in maintenance.

18
00:00:53.599 --> 00:00:55.680
<v Speaker 3>I've always worked in maintenance ever
since I left school.

19
00:00:55.790 --> 00:01:02.200
<v Speaker 3>Um, I joined BlueScope 1718 years ago, and
I've worked at the Metal Co lines for

20
00:01:02.200 --> 00:01:03.240
<v Speaker 3>most of that time.

21
00:01:04.180 --> 00:01:11.120
<v Speaker 3>Uh, start of 2022, we started a pilot
program in my native department, and

22
00:01:11.120 --> 00:01:13.309
<v Speaker 3>that was to introduce predictive
maintenance.

23
00:01:13.680 --> 00:01:18.069
<v Speaker 3>We chose Sensei over three or four
different platforms, um, and that was mainly

24
00:01:18.069 --> 00:01:23.040
<v Speaker 3>around the, the AI component and the
ability to, to tune it.

25
00:01:23.779 --> 00:01:26.870
<v Speaker 3>Sort of automatically with that thumbs up
and thumbs down feature, that was the

26
00:01:26.870 --> 00:01:28.410
<v Speaker 3>initial attraction.

27
00:01:28.510 --> 00:01:34.230
<v Speaker 3>Things have changed remarkably since then,
um, we've had 3 or 4 massive sort of step

28
00:01:34.230 --> 00:01:39.110
<v Speaker 3>changes in the capability of the app, and,
you know, we went through the pilot

29
00:01:39.110 --> 00:01:44.830
<v Speaker 3>program, it took roughly 12 months, we
onboarded around 300 assets across 3 metal

30
00:01:44.830 --> 00:01:51.239
<v Speaker 3>coating lines, and yeah, once the pilot
was complete, Uh, we decided to roll out,

31
00:01:51.379 --> 00:01:56.080
<v Speaker 3>uh, Australia wide, basically, um, and
that's what I'm responsible for, so I'm

32
00:01:56.540 --> 00:01:58.449
<v Speaker 3>predictive maintenance lead for Bluescope

33
00:01:58.449 --> 00:01:59.940
<v Speaker 3>Steel, Australian steel products.

34
00:02:00.730 --> 00:02:05.489
<v Speaker 3>We do support our global roll-out as well,
which is pushing into US, China,

35
00:02:05.809 --> 00:02:10.929
<v Speaker 3>Thailand, New Zealand, and a few other
bits and pieces around the place, so, I have

36
00:02:10.929 --> 00:02:17.050
<v Speaker 3>the awesome job of, of leading that, um,
that regime, I guess you'd call it, so

37
00:02:17.360 --> 00:02:24.289
<v Speaker 3>we've been going since 2022, and yeah,
we're, we're just about to, to

38
00:02:24.289 --> 00:02:29.889
<v Speaker 3>kick off in the US we're, um, probably 6
months deep in, New Zealand,

39
00:02:30.550 --> 00:02:33.210
<v Speaker 3>maybe 18 months deep in Western Port or
Melbourne.

40
00:02:34.500 --> 00:02:38.259
<v Speaker 3>And yeah, and across here at Port Kembla,
we're pushing into most of our business

41
00:02:38.259 --> 00:02:38.559
<v Speaker 3>units.

42
00:02:38.619 --> 00:02:44.250
<v Speaker 3>So it is, it, it's really cool to be part
of, and, um, you know, our team's growing,

43
00:02:44.300 --> 00:02:49.279
<v Speaker 3>so we're trying to accelerate how quickly
we onboard and, and get things, uh,

44
00:02:49.460 --> 00:02:50.699
<v Speaker 3>monitored through Sensi.

45
00:02:50.899 --> 00:02:57.600
<v Speaker 3>So, and also that's supported by a pretty,
pretty elaborate, um, LAwareN network

46
00:02:58.020 --> 00:03:00.800
<v Speaker 3>of sensors to add a little bit of context
when we're lacking.

47
00:03:01.279 --> 00:03:04.089
<v Speaker 3>Some of the data we need to, to onboard
our assets.

48
00:03:04.130 --> 00:03:10.089
<v Speaker 3>And, you know, like our steel mill have,
um, the complete array of age of equipment

49
00:03:10.089 --> 00:03:13.850
<v Speaker 3>and complexity of equipment from the very,
very simple to the, the latest and the

50
00:03:13.850 --> 00:03:15.100
<v Speaker 3>most modern equipment.

51
00:03:15.210 --> 00:03:20.009
<v Speaker 3>So we, we're dealing with a vast variety
of equipment and, you know, everything

52
00:03:20.009 --> 00:03:26.970
<v Speaker 3>from, um, you know, Bringing in iron ore
and raw materials to completely

53
00:03:26.970 --> 00:03:28.929
<v Speaker 3>finished products going out the gate to
our customers.

54
00:03:29.009 --> 00:03:33.009
<v Speaker 3>So it's pretty, uh, uh, when I say steel
mill, it's the whole thing from front to

55
00:03:33.009 --> 00:03:33.229
<v Speaker 3>back.

56
00:03:33.330 --> 00:03:36.089
<v Speaker 3>So, yeah, it's very cool to be part of
that.

57
00:03:36.130 --> 00:03:41.369
<v Speaker 3>And, um, you know, uh, I spent a long time
just in one department and now I sort of

58
00:03:41.369 --> 00:03:45.649
<v Speaker 3>pop up every around the place and try to
understand what the needs are of, of that

59
00:03:45.649 --> 00:03:50.570
<v Speaker 3>particular business unit and see where
Sens I can, Most quickly help them out with

60
00:03:50.570 --> 00:03:54.750
<v Speaker 3>what they are, what their sort of pain
points are, so that's that's a bit about me

61
00:03:54.750 --> 00:03:55.410
<v Speaker 3>and what I do.

62
00:03:56.619 --> 00:03:57.179
<v Niall Sullivan>Fantastic.

63
00:03:57.300 --> 00:04:00.899
<v Niall Sullivan>No, really good, um, really good good
background there, um, Chris.

64
00:04:00.979 --> 00:04:05.800
<v Niall Sullivan>um, and I guess, uh, you mentioned, you
know, the scale, you know, the scaling of

65
00:04:05.800 --> 00:04:08.660
<v Niall Sullivan>the platform across all those different
sites, um, globally, which is really

66
00:04:08.660 --> 00:04:09.779
<v Niall Sullivan>fantastic to hear.

67
00:04:10.039 --> 00:04:13.619
<v Niall Sullivan>What, what would you say has sort of been
the, been the key to that, you know, to

68
00:04:13.619 --> 00:04:14.699
<v Niall Sullivan>that global rollout?

69
00:04:14.940 --> 00:04:16.500
<v Niall Sullivan>It doesn't always happen that way.

70
00:04:17.549 --> 00:04:22.720
<v Speaker 3>I guess the, the success stories always
spark people's interest.

71
00:04:23.359 --> 00:04:27.640
<v Speaker 3>And that they kind of multiply when, when
people sort of, sort of hear some of the

72
00:04:27.640 --> 00:04:31.350
<v Speaker 3>success stories we've had and they're
like, Oh yeah, I have similar equipment, I

73
00:04:31.350 --> 00:04:36.549
<v Speaker 3>have similar needs in my department, or
it's completely the other way, where people

74
00:04:36.549 --> 00:04:39.029
<v Speaker 3>are like, Oh, that's cool, but can you do
something with this?

75
00:04:39.119 --> 00:04:45.230
<v Speaker 3>And um You know, It, it's, it's still all
about people and

76
00:04:45.549 --> 00:04:49.359
<v Speaker 3>engaging them in the right way and, and
finding the, you know, every, every

77
00:04:49.359 --> 00:04:53.200
<v Speaker 3>department will have those 2 or 3 people
that sort of naturally jump at the chance

78
00:04:53.200 --> 00:04:54.049
<v Speaker 3>to do something like this.

79
00:04:54.119 --> 00:04:57.910
<v Speaker 3>And it's really, it's finding those people
and, and getting started with them.

80
00:04:57.920 --> 00:05:02.440
<v Speaker 3>And that first sort of couple of success
stories that come from, you know, their own

81
00:05:02.440 --> 00:05:06.829
<v Speaker 3>department, and that's when the more
people like from that particular department,

82
00:05:06.880 --> 00:05:13.170
<v Speaker 3>they jump on, on the, the hype train, I
guess you'd say, and, um, It just multiplies

83
00:05:13.170 --> 00:05:17.450
<v Speaker 3>from there and then, you know, we, we
start to, to talk about our latest sort of

84
00:05:17.450 --> 00:05:22.309
<v Speaker 3>thing is, you know, to increase the rate
of onboarding, we're, we're trying to find

85
00:05:22.850 --> 00:05:27.390
<v Speaker 3>as many people as we can in the department
to onboard, say, 5 assets a month.

86
00:05:28.010 --> 00:05:33.899
<v Speaker 3>So if you start to, you know, if you find
345 people, and then, you know, You expand

87
00:05:33.899 --> 00:05:38.700
<v Speaker 3>their capabilities to get them up to 5 a
month, and then you add more people to that

88
00:05:38.700 --> 00:05:41.980
<v Speaker 3>group, and then you add more to their
capabilities, they can onboard more assets,

89
00:05:42.059 --> 00:05:42.820
<v Speaker 3>you know, per month.

90
00:05:42.899 --> 00:05:47.380
<v Speaker 3>So, that's the latest theory on how we're
trying to, to roll out, um.

91
00:05:48.200 --> 00:05:53.010
<v Speaker 3>So it's a big, it's a big push about
training and upskilling our people and in

92
00:05:53.010 --> 00:05:58.880
<v Speaker 3>giving access to the platforms, training
them up, and uh yeah, the, the LoanAN

93
00:05:58.880 --> 00:06:05.170
<v Speaker 3>network is, is handy, particularly on some
of the old, Uh, the older, less critical

94
00:06:05.170 --> 00:06:10.269
<v Speaker 3>sort of equipment, like we do our critical
things quite well, um, we find it's sort

95
00:06:10.269 --> 00:06:16.510
<v Speaker 3>of that next layer of criticality, not the
ultra like important stuff, it's the next

96
00:06:16.510 --> 00:06:18.190
<v Speaker 3>layer down that can not,

97
00:06:18.470 --> 00:06:21.950
<v Speaker 3>that doesn't get as much love as the
critical stuff where we can really start to

98
00:06:21.950 --> 00:06:27.529
<v Speaker 3>make an impact, uh, on, you know,
detecting anomalies and, and trending.

99
00:06:28.070 --> 00:06:33.269
<v Speaker 3>Sort of metrics that we're interested in
and yeah, that's where we can make most of

100
00:06:33.269 --> 00:06:34.149
<v Speaker 3>the impact.

101
00:06:35.309 --> 00:06:38.950
<v Speaker 3>And that's, you know, like, and that sort
of maybe frees you up to do the, the

102
00:06:38.950 --> 00:06:42.549
<v Speaker 3>critical stuff better, and, and not to say
that we can't do anything with the

103
00:06:42.549 --> 00:06:46.260
<v Speaker 3>critical stuff, it's just, you know, it's
critical for, for a reason because it's

104
00:06:46.260 --> 00:06:50.700
<v Speaker 3>probably a little bit more complex, um,
and it, it takes a little bit longer to, to

105
00:06:50.700 --> 00:06:55.290
<v Speaker 3>understand how we can implement Sensi sort
of in, in those more complex sort of

106
00:06:56.269 --> 00:06:57.510
<v Speaker 3>processes or, or machines.

107
00:06:57.630 --> 00:07:01.369
<v Speaker 3>So that's, that's generally how we try to
do things.

108
00:07:03.119 --> 00:07:07.089
<v Niall Sullivan>Yeah, and is it generally, I, I guess the
general point is it's about building

109
00:07:07.089 --> 00:07:08.890
<v Niall Sullivan>momentum internally.

110
00:07:09.209 --> 00:07:12.609
<v Niall Sullivan>I mean, or, or getting on the, and people
don't want to miss out if something really

111
00:07:12.609 --> 00:07:13.730
<v Niall Sullivan>positive's happening internally.

112
00:07:13.809 --> 00:07:17.839
<v Niall Sullivan>So how important is sort of sharing the
successes internally and widely?

113
00:07:18.049 --> 00:07:20.070
<v Niall Sullivan>And how do you do that, I guess, as well?

114
00:07:22.529 --> 00:07:27.959
<v Speaker 3>We have so many different like, um,
Steering committees and focus groups, and, you

115
00:07:27.959 --> 00:07:31.920
<v Speaker 3>know, we have groups of asset managers
that, that meet regularly and there, there's

116
00:07:31.920 --> 00:07:32.750
<v Speaker 3>so many different ways.

117
00:07:32.799 --> 00:07:37.679
<v Speaker 3>We have local intranets we can push out,
but it really is those, you know, those one

118
00:07:37.679 --> 00:07:38.000
<v Speaker 3>pages.

119
00:07:38.029 --> 00:07:41.839
<v Speaker 3>I think you'd probably come across, we
send a lot of them through to, you know, our,

120
00:07:42.040 --> 00:07:47.309
<v Speaker 3>our day to day sort of Sensor contacts and
Semen contacts that we, we report into,

121
00:07:47.320 --> 00:07:50.799
<v Speaker 3>and, and I'm not sure where they end up
in, in your organization, but that's a

122
00:07:50.799 --> 00:07:53.380
<v Speaker 3>really good way of sparking interest.

123
00:07:53.959 --> 00:07:58.640
<v Speaker 3>And then, um, You know, and, and those
people that, it's always easier to go to

124
00:07:58.640 --> 00:08:03.320
<v Speaker 3>people that are, are interested and, and
they have, you know, a few, a few people

125
00:08:03.320 --> 00:08:06.359
<v Speaker 3>that have got some spare time and they've
got a little bit of spare capacity and

126
00:08:06.359 --> 00:08:08.399
<v Speaker 3>money to, to kick it off.

127
00:08:08.500 --> 00:08:12.160
<v Speaker 3>Um, it's really hard to ignore those
people and they might not be the, the areas

128
00:08:12.160 --> 00:08:13.559
<v Speaker 3>that we've been asked to focus on.

129
00:08:13.640 --> 00:08:18.119
<v Speaker 3>So there's, there's, there's critical
parts of our business that we need to, you

130
00:08:18.119 --> 00:08:22.600
<v Speaker 3>know, improve reliability or capacity
because of, you know, expansions or, or

131
00:08:22.600 --> 00:08:23.679
<v Speaker 3>whatever we need to do.

132
00:08:23.760 --> 00:08:27.970
<v Speaker 3>And, But then it's the, so we've got to go
to the critical people, and then there's

133
00:08:27.970 --> 00:08:34.280
<v Speaker 3>sort of the um The next group of people
that sort of haven't been deemed as our

134
00:08:34.280 --> 00:08:38.299
<v Speaker 3>critical departments that need the help,
it's the other ones that have, you know,

135
00:08:38.520 --> 00:08:43.520
<v Speaker 3>maybe a will and, and a few spare people
that we, you know, you can't ignore them

136
00:08:43.520 --> 00:08:46.520
<v Speaker 3>because they're, they're so enthusiastic
and they're so on board, and they want to

137
00:08:46.520 --> 00:08:49.679
<v Speaker 3>jump on the hype train and, and get things
going in their department.

138
00:08:49.760 --> 00:08:55.359
<v Speaker 3>So it's trying to, it's a bit of a
balancing act, but, you know, we're, um, our, our

139
00:08:55.359 --> 00:08:59.200
<v Speaker 3>small team, and it, it is a small team,
it's growing at the moment, so.

140
00:08:59.929 --> 00:09:04.059
<v Speaker 3>That's good, and, and, and those sort of
things maybe toughen up in the, in the

141
00:09:04.059 --> 00:09:10.059
<v Speaker 3>steel market, it's, it's one of our key
focuses is to, you know, roll out predictive

142
00:09:10.059 --> 00:09:14.539
<v Speaker 3>maintenance and save money through routine
maintenance and also avoiding those, you

143
00:09:14.539 --> 00:09:19.710
<v Speaker 3>know, critical breakdowns that, you know,
cost you time, money, And lost production,

144
00:09:19.760 --> 00:09:24.919
<v Speaker 3>all those types of things, so it's, uh,
it's definitely central to our business now.

145
00:09:26.880 --> 00:09:30.289
<v Niall Sullivan>Yeah, so that, that is interesting you
mention about, you know, what do we, you

146
00:09:30.289 --> 00:09:31.890
<v Niall Sullivan>know, we as Siemens do internally.

147
00:09:31.940 --> 00:09:35.799
<v Niall Sullivan>So we do, we do share them internally
because obviously we want to celebrate

148
00:09:35.799 --> 00:09:37.400
<v Niall Sullivan>successes with customers.

149
00:09:37.520 --> 00:09:41.400
<v Niall Sullivan>And I think the people are amazed by some
of the, especially with, you know, the

150
00:09:41.400 --> 00:09:44.450
<v Niall Sullivan>Bluescope Steel case, case, uh, or
projects.

151
00:09:45.299 --> 00:09:49.609
<v Niall Sullivan>Um, as an example, because some of the
figures on there, almost to, to some people

152
00:09:49.609 --> 00:09:51.630
<v Niall Sullivan>it was like, wow, is that, is that really
true?

153
00:09:51.809 --> 00:09:55.200
<v Niall Sullivan>kind of thing that is, it's a common thing
with Sensa generally, is like, is that

154
00:09:55.200 --> 00:09:55.570
<v Niall Sullivan>really true?

155
00:09:55.650 --> 00:09:57.250
<v Niall Sullivan>Can it really do what it says?

156
00:09:57.320 --> 00:10:01.969
<v Niall Sullivan>But do you encounter that kind of sort of
skepticism internally when, you know, when

157
00:10:01.969 --> 00:10:06.780
<v Niall Sullivan>you see these great successes and, and
numbers and what's going, going on in the

158
00:10:06.780 --> 00:10:07.090
<v Niall Sullivan>project?

159
00:10:07.099 --> 00:10:07.330
<v Niall Sullivan>Well.

160
00:10:08.140 --> 00:10:14.179
<v Speaker 3>We're, we're very cautious about, you
know, Overestimating, and, and, and it is a

161
00:10:14.179 --> 00:10:18.710
<v Speaker 3>lot of estimating in that, when you, when
you sort of avoid some sort of, um,

162
00:10:19.090 --> 00:10:22.500
<v Speaker 3>breakdown like the one we're sort of
talking about today, it, it is a little bit

163
00:10:22.500 --> 00:10:28.599
<v Speaker 3>subjective, but we always are quite
conservative when we, when we do estimations,

164
00:10:28.619 --> 00:10:32.580
<v Speaker 3>and it, it's also based on past experience
too, like, you know, this particular one

165
00:10:32.580 --> 00:10:36.820
<v Speaker 3>we're talking about, this hydraulic
success case where we avoided 24 hours downtime

166
00:10:36.820 --> 00:10:37.840
<v Speaker 3>on a metal coating line.

167
00:10:38.190 --> 00:10:44.580
<v Speaker 3>Um, we know that that is, I mean, it's
still conservative, uh, because of the,

168
00:10:44.950 --> 00:10:49.799
<v Speaker 3>the potential ramifications of this
particular failure or potential failure.

169
00:10:50.210 --> 00:10:55.330
<v Speaker 3>Um, So we are always very conservative
and, and we report this into the highest

170
00:10:55.330 --> 00:11:02.109
<v Speaker 3>level of, of our company, so we, we
always, Um, have in the back of our mind that we

171
00:11:02.109 --> 00:11:07.030
<v Speaker 3>need to back up our estimations with, with
some sort of, um, facts and figures, and,

172
00:11:07.119 --> 00:11:11.000
<v Speaker 3>you know, generally we don't do that
ourselves as a predictive maintenance group.

173
00:11:11.039 --> 00:11:15.960
<v Speaker 3>We rely on the, the local departments to,
to sort of make those estimations, and

174
00:11:15.960 --> 00:11:18.479
<v Speaker 3>we're always very, very conserved in that
space.

175
00:11:18.559 --> 00:11:23.239
<v Speaker 3>So, um, You know, we're sort of always
open to scrutiny.

176
00:11:23.280 --> 00:11:27.719
<v Speaker 3>And the second that, you know, that
credibility is gone, then it, it's gone forever.

177
00:11:27.799 --> 00:11:33.799
<v Speaker 3>So we're always very, very conserved in
that space when we make estimations and, um,

178
00:11:33.869 --> 00:11:39.479
<v Speaker 3>it all, it's, it's based around, um, sort
of lost potential lost revenue is most of

179
00:11:39.479 --> 00:11:45.669
<v Speaker 3>the things that we calculate, but, um, now
sort of our, our general management and

180
00:11:45.669 --> 00:11:51.799
<v Speaker 3>executive are pushing us towards, um,
well, well, now that we've got this, Sort of

181
00:11:52.299 --> 00:11:56.419
<v Speaker 3>monitoring in place on certain assets, the
next step is to start to roll back some

182
00:11:56.419 --> 00:11:57.380
<v Speaker 3>of the maintenance,

183
00:11:57.929 --> 00:11:59.330
<v Speaker 3>the routine maintenance we have.

184
00:11:59.619 --> 00:12:03.700
<v Speaker 3>Uh, and, you know, you need to have a
little bit of, you know, longevity in the app

185
00:12:03.700 --> 00:12:08.260
<v Speaker 3>and, um, confidence in, in what you're
seeing that the app's telling you to, to

186
00:12:08.260 --> 00:12:08.849
<v Speaker 3>start to do that.

187
00:12:08.900 --> 00:12:13.369
<v Speaker 3>That's when, you know, you start to get
brave and turn off those maintenance plans

188
00:12:13.369 --> 00:12:18.039
<v Speaker 3>that have got us to the point we are now,
and, you know, it keeps, Keeps things

189
00:12:18.039 --> 00:12:22.340
<v Speaker 3>ticking over, it's, it's, yeah, that's,
that's when you really know you're cooking

190
00:12:22.340 --> 00:12:25.380
<v Speaker 3>that, you, you know, you've got the
confidence of the local maintenance

191
00:12:25.380 --> 00:12:30.659
<v Speaker 3>practitioners to start to turn off those
maintenance plans and, and rely on what the

192
00:12:30.659 --> 00:12:34.739
<v Speaker 3>app is, is actually telling you, so,
That's, that's a big step.

193
00:12:35.559 --> 00:12:36.599
<v Speaker 3>It's definitely a big step.

194
00:12:37.510 --> 00:12:41.320
<v Niall Sullivan>Yeah, it's that, it's that element of
trusting, getting to the point of where, you

195
00:12:41.320 --> 00:12:44.400
<v Niall Sullivan>know, you trust the app and what it's,
what it's telling you, right?

196
00:12:44.520 --> 00:12:49.590
<v Niall Sullivan>And that's, and that's obviously a very
key point of for adoption or widespread

197
00:12:49.590 --> 00:12:49.880
<v Niall Sullivan>adoption

198
00:12:49.880 --> 00:12:50.260
<v Speaker 3>is.

199
00:12:51.130 --> 00:12:55.859
<v Speaker 3>Uh, it actually is, and, you know, it's,
it's those, you know, you might save 2 or 3

200
00:12:55.859 --> 00:13:00.299
<v Speaker 3>maintenance people from coming in, uh,
Saturday night for a Saturday night

201
00:13:00.299 --> 00:13:02.219
<v Speaker 3>breakdown, and no one likes doing that,
right?

202
00:13:02.380 --> 00:13:03.500
<v Speaker 3>Like, no, everyone hates that.

203
00:13:03.539 --> 00:13:06.539
<v Speaker 3>And that's, that's one of the things I
really want to save people from doing those

204
00:13:06.539 --> 00:13:10.049
<v Speaker 3>Saturday night discos where, you know, you
get a phone call in the middle of the

205
00:13:10.049 --> 00:13:11.260
<v Speaker 3>night, come to work and fix this.

206
00:13:11.340 --> 00:13:15.059
<v Speaker 3>So we're trying to, you know, make sure
that doesn't happen, you know, and when you

207
00:13:15.059 --> 00:13:18.739
<v Speaker 3>save people from having to do that a
couple of times, they, they, they're on board

208
00:13:18.739 --> 00:13:23.609
<v Speaker 3>and You know, but it, it takes a whole
bunch more than that to, to get a whole

209
00:13:23.609 --> 00:13:26.510
<v Speaker 3>department on board where to the point
where they're like, OK, we're going to start

210
00:13:27.090 --> 00:13:31.400
<v Speaker 3>rolling back some of our maintenance plans
and, you know, fully trusting on,

211
00:13:31.770 --> 00:13:34.049
<v Speaker 3>trusting, and we're, we're all in on this
sort of process.

212
00:13:34.130 --> 00:13:39.450
<v Speaker 3>So that's the, um, that's the battle that
we're, that we're, well, I think we're

213
00:13:39.450 --> 00:13:44.130
<v Speaker 3>winning it, in, in at least most of the
places we're, we're rolling out in.

214
00:13:44.169 --> 00:13:46.169
<v Speaker 3>So, yeah, it's, it's very encouraging.

215
00:13:47.049 --> 00:13:47.559
<v Speaker 3>Very encouraging.

216
00:13:47.609 --> 00:13:47.979
<v Speaker 3>Yeah.

217
00:13:48.409 --> 00:13:52.929
<v Niall Sullivan>And just before we we go into that
specific case, um, success case we're gonna talk

218
00:13:52.929 --> 00:13:56.770
<v Niall Sullivan>about today, um, maybe Chris, you, you
explain a little bit more about the, the

219
00:13:56.770 --> 00:13:57.409
<v Niall Sullivan>KPIs.

220
00:13:57.489 --> 00:14:02.299
<v Niall Sullivan>So you mentioned a few, you know, the KPIs
that you'd maybe report upwards or that,

221
00:14:02.309 --> 00:14:04.679
<v Niall Sullivan>or the, or that you and the global teams
track.

222
00:14:04.809 --> 00:14:07.309
<v Niall Sullivan>What, maybe you could go into a bit more
detail about that.

223
00:14:09.049 --> 00:14:15.969
<v Speaker 3>So when we first started, first started,
uh, rolling out and within the, um, the

224
00:14:15.969 --> 00:14:21.130
<v Speaker 3>trial period, we would reports of downtime
avoided, you know, like you'd, you'd,

225
00:14:21.250 --> 00:14:26.729
<v Speaker 3>you'd see a, a problem with a, a, a
specific machine and you'd, you'd manage that

226
00:14:26.729 --> 00:14:31.000
<v Speaker 3>problem until some, um, Predetermined
downtime, or you, you manage it to the next

227
00:14:31.000 --> 00:14:35.349
<v Speaker 3>shutdown or, or, or whatever, like, and
that would be, OK, we saved, you know, 12

228
00:14:35.349 --> 00:14:38.919
<v Speaker 3>hours downtime by managing that blower or
that motor to that,

229
00:14:39.479 --> 00:14:40.679
<v Speaker 3>um, maintenance window.

230
00:14:40.719 --> 00:14:44.679
<v Speaker 3>We take care of it then and there, and,
you know, we've avoided a, a line stop, um,

231
00:14:44.750 --> 00:14:46.880
<v Speaker 3>an unplanned line stop and some, some
downtime.

232
00:14:46.969 --> 00:14:48.679
<v Speaker 3>So that's where we sort of started out.

233
00:14:48.789 --> 00:14:55.590
<v Speaker 3>But maybe as your, um, production units
become less loaded and there's, there's idle

234
00:14:55.590 --> 00:15:02.190
<v Speaker 3>time, then, Downtime avoided kind of
becomes useless, so you sort of change your

235
00:15:02.190 --> 00:15:08.799
<v Speaker 3>thinking a little bit into the point
where, OK, So we have, you know, maybe detected

236
00:15:08.799 --> 00:15:15.380
<v Speaker 3>a problem with a machine, a pump, or a
blower or a motor, and You know, we've We've

237
00:15:15.380 --> 00:15:18.460
<v Speaker 3>pulled it out of service and replaced it
with a refurbished or a new

238
00:15:18.460 --> 00:15:24.210
<v Speaker 3>unit, and You know, that repair on that
motor because the bearing, you know, we

239
00:15:24.210 --> 00:15:28.289
<v Speaker 3>detected it was hot and we managed it to
the point where the shutdown was, but it

240
00:15:28.289 --> 00:15:32.049
<v Speaker 3>kept running and the bearing didn't
collapse, which means we didn't damage the shaft

241
00:15:32.049 --> 00:15:37.630
<v Speaker 3>or the housing, so the repair is, Is a lot
more efficient than or cost efficient

242
00:15:37.630 --> 00:15:41.309
<v Speaker 3>than than what it would have been if we
wouldn't have detected that, and we had a an

243
00:15:41.309 --> 00:15:42.119
<v Speaker 3>in-service failure.

244
00:15:42.229 --> 00:15:46.309
<v Speaker 3>So we're, we're trying to, instead of the,
the downtime avoided, we're like, OK, now

245
00:15:46.309 --> 00:15:52.429
<v Speaker 3>we're saving money by, you know, a
repairing equipment in a much less sort of failed

246
00:15:52.429 --> 00:15:56.469
<v Speaker 3>state than, than what it would have been
if we didn't have the monitoring in place.

247
00:15:57.270 --> 00:16:02.020
<v Speaker 3>So we're trying to measure that and we're
trying to measure like well what's the,

248
00:16:02.030 --> 00:16:07.059
<v Speaker 3>um, What's the, the gain of offsetting
maintenance plans, like either changing the

249
00:16:07.059 --> 00:16:11.219
<v Speaker 3>frequency or, or shutting them down
altogether and just making them like a, a manual

250
00:16:11.219 --> 00:16:15.359
<v Speaker 3>call when, when the app tells us that, OK,
this, this asset's displaying some

251
00:16:15.729 --> 00:16:19.940
<v Speaker 3>elevated temperatures or vibrations or
current metrics that, that we haven't seen

252
00:16:19.940 --> 00:16:24.099
<v Speaker 3>before, and now is the time to sort of,
OK, let's, let's do a, an inspection at the

253
00:16:24.099 --> 00:16:25.820
<v Speaker 3>next, you know, maintenance window.

254
00:16:25.940 --> 00:16:31.940
<v Speaker 3>So, we're trying to calculate, Offset
savings from reducing or shutting down

255
00:16:31.940 --> 00:16:36.820
<v Speaker 3>maintenance plans and, You know, there's
sort of a general rule of thumb if you do

256
00:16:36.820 --> 00:16:39.760
<v Speaker 3>something in a planned fashion, you're
going to get the most efficient.

257
00:16:40.820 --> 00:16:43.099
<v Speaker 3>You know, labor cost outcome.

258
00:16:43.900 --> 00:16:47.739
<v Speaker 3>In that space rather than doing it, you
know, after hours or in an unplanned type

259
00:16:47.739 --> 00:16:48.239
<v Speaker 3>fashion.

260
00:16:48.900 --> 00:16:53.179
<v Speaker 3>So there's, there's savings to be, to be
had with doing things in a planned fashion.

261
00:16:53.460 --> 00:16:58.010
<v Speaker 3>Um, in theory, the, the less repair bills
and, you know, also shutting down of the

262
00:16:58.010 --> 00:17:02.539
<v Speaker 3>routine maintenance, and we only execute
instead of time-based, we're doing it, um,

263
00:17:02.979 --> 00:17:05.439
<v Speaker 3>when basically Sensai tells us to, so.

264
00:17:06.229 --> 00:17:09.869
<v Speaker 3>You know, and if you sort of gear that
towards, if you start at the, the things that

265
00:17:09.869 --> 00:17:14.060
<v Speaker 3>are frequent and we, and we're using
outside, you know, labor, if you sort of start

266
00:17:14.060 --> 00:17:18.030
<v Speaker 3>there, they're the, they're the sort of
big money winners if you start in that

267
00:17:18.030 --> 00:17:18.270
<v Speaker 3>space.

268
00:17:18.310 --> 00:17:23.390
<v Speaker 3>But also there's, there's thoughts of, you
know, internal labor is still valuable

269
00:17:23.390 --> 00:17:28.989
<v Speaker 3>and, and we always have more work on them
what we have labor available, um, So

270
00:17:28.989 --> 00:17:33.589
<v Speaker 3>there's still money to be to be saved, and
I guess how we think about it is, you

271
00:17:33.589 --> 00:17:39.140
<v Speaker 3>know, we're We're sort of offloading some
of those routine inspections or line walks

272
00:17:39.140 --> 00:17:44.680
<v Speaker 3>or whatever and we're making our people,
We're freeing people up from that to, to

273
00:17:44.680 --> 00:17:48.079
<v Speaker 3>redeploy them to more critical, high-level
things than just doing

274
00:17:48.079 --> 00:17:54.160
<v Speaker 3>some, you know, nice, nice to do, nice to
feel, um, inspections that, you know, 9

275
00:17:54.160 --> 00:17:56.520
<v Speaker 3>times out of 10 don't really tell you
anything.

276
00:17:57.800 --> 00:18:00.780
<v Speaker 3>So that's the latest sort of metrics that
we're looking with.

277
00:18:02.680 --> 00:18:06.439
<v Niall Sullivan>Yeah, I think, I think that's really
interesting actually how you say it, you know,

278
00:18:06.520 --> 00:18:10.400
<v Niall Sullivan>like you said, it's, it's evolved from
looking at things like downtime because we

279
00:18:10.400 --> 00:18:14.709
<v Niall Sullivan>often say with, with Senite, it's
actually, you know, looking beyond, we encourage

280
00:18:14.709 --> 00:18:20.219
<v Niall Sullivan>people to look beyond downtime as like the
metric to, um, to measure, um, success.

281
00:18:20.599 --> 00:18:23.979
<v Niall Sullivan>So that, yeah, so, so that's really, um,
really interesting.

282
00:18:24.079 --> 00:18:29.160
<v Niall Sullivan>But, um, if we, if we look now at the, you
know, the specific case we, you mentioned

283
00:18:29.160 --> 00:18:30.380
<v Niall Sullivan>before, so the hydraulic system.

284
00:18:30.949 --> 00:18:34.150
<v Niall Sullivan>And maybe I guess first of all, Chris, we
could just go into a bit of a brief

285
00:18:34.150 --> 00:18:38.199
<v Niall Sullivan>overview of the, you know, the background
to it, you know, where, where it's located

286
00:18:38.199 --> 00:18:40.890
<v Niall Sullivan>and that, and that kind of thing and what
was happening with it.

287
00:18:41.359 --> 00:18:45.109
<v Speaker 3>But some of the, some things get left
behind because that's, you know, you, there's

288
00:18:45.109 --> 00:18:50.040
<v Speaker 3>a certain amount of engineering time and
money and resources to, to upgrade and you

289
00:18:50.040 --> 00:18:55.160
<v Speaker 3>wanna, you know, obviously you look at
bang for buck type stuff and, um, anyway, you

290
00:18:55.160 --> 00:18:58.920
<v Speaker 3>get into this space where, you know, a few
bits and pieces get left behind and, and

291
00:18:58.920 --> 00:19:04.069
<v Speaker 3>maybe, This, this hydraulic system that
used to just, you know, hold a few snubbers

292
00:19:04.069 --> 00:19:09.489
<v Speaker 3>in the air and when the line stopped, it'd
lower a few snubbers and, That would be,

293
00:19:09.689 --> 00:19:11.079
<v Speaker 3>you know, it'd be sort of a

294
00:19:11.079 --> 00:19:15.569
<v Speaker 3>low criticality, doesn't really matter if
it stops type, um.

295
00:19:16.680 --> 00:19:22.209
<v Speaker 3>Piece of equipment And as you sort of
upgrade and modernize things, I think there

296
00:19:22.209 --> 00:19:25.530
<v Speaker 3>was a big movement to go from like
water-based hydraulics.

297
00:19:26.380 --> 00:19:30.180
<v Speaker 3>Which would service most of our exit ends
around our, our recoilers and coil cars

298
00:19:30.180 --> 00:19:30.689
<v Speaker 3>and stuff like that.

299
00:19:30.760 --> 00:19:33.979
<v Speaker 3>Anything with a really big cylinder on it,
we would use, um, sort of water-based

300
00:19:33.979 --> 00:19:37.939
<v Speaker 3>hydraulics on and anything a little bit
smaller, it would, it'd be sort of

301
00:19:37.939 --> 00:19:39.790
<v Speaker 3>mineral-based sort of equipment.

302
00:19:39.900 --> 00:19:44.719
<v Speaker 3>So, and now we're, we've got our mineral
hydraulics servicing some really critical

303
00:19:44.719 --> 00:19:49.140
<v Speaker 3>equipment that, you know, we use every
time we strip a coil off the end of a metal

304
00:19:49.140 --> 00:19:53.910
<v Speaker 3>coating line and, You know, all the
equipment is now driven by mineral hydraulics

305
00:19:53.910 --> 00:19:58.349
<v Speaker 3>instead of the old water-based hydraulics,
so you know, you convert over your valves

306
00:19:58.349 --> 00:20:01.709
<v Speaker 3>and you maybe change out a few cylinders
and stuff like that.

307
00:20:01.869 --> 00:20:07.790
<v Speaker 3>So that's how a typical sort of upgrade
would look, but maybe some of the hydraulic

308
00:20:07.790 --> 00:20:09.150
<v Speaker 3>system upgrades.

309
00:20:09.569 --> 00:20:13.689
<v Speaker 3>You know, there's not a lot of detection
or sensors on them, detecting, making sure

310
00:20:13.689 --> 00:20:17.589
<v Speaker 3>that it's all happy and safe and doing
what it, it needs to do, so maybe that's been

311
00:20:18.130 --> 00:20:23.729
<v Speaker 3>overlooked or outside scope or no money
left or, you know, multitude of reasons to,

312
00:20:23.890 --> 00:20:26.640
<v Speaker 3>you know, maybe not touch a hydraulic,
because it just, you know, it pumps out

313
00:20:26.640 --> 00:20:28.229
<v Speaker 3>hydraulic pressure, it does its job.

314
00:20:29.030 --> 00:20:35.670
<v Speaker 3>Until things sort of go wrong I guess,
and, and you end up with a, you know, really

315
00:20:35.670 --> 00:20:40.349
<v Speaker 3>nice new core cars and hydraulic equipment
and maybe your your hydraulic system's

316
00:20:40.349 --> 00:20:43.189
<v Speaker 3>not quite up to scratch, so, you know.

317
00:20:43.880 --> 00:20:47.770
<v Speaker 3>That's kind of a space we might have
fallen into here and there along the way, but

318
00:20:49.640 --> 00:20:55.280
<v Speaker 3>So that's how we get into that sort of
space and then you want to start to monitor

319
00:20:55.280 --> 00:21:00.880
<v Speaker 3>everything with Sensi and you know, OK,
well this hydraulic system is quite integral

320
00:21:00.880 --> 00:21:01.599
<v Speaker 3>to what we do.

321
00:21:02.579 --> 00:21:06.939
<v Speaker 3>What, what sensors do we have to monitor
it and, and see how it's, how it works, and

322
00:21:06.939 --> 00:21:12.099
<v Speaker 3>we have, you know, we have a, a visual
based sight blast that tells us the level,

323
00:21:12.130 --> 00:21:19.060
<v Speaker 3>and we have a low level, stop everything
type switch, and that's, that's all

324
00:21:19.060 --> 00:21:19.420
<v Speaker 3>we've got.

325
00:21:20.400 --> 00:21:26.920
<v Speaker 3>So there's not a lot you can do with that,
with, with, with Sensi, um, so we need

326
00:21:26.920 --> 00:21:33.729
<v Speaker 3>to potentially add in a few little IOT,
um, Wireless devices

327
00:21:33.729 --> 00:21:38.449
<v Speaker 3>which are, you know, they're not, they're
not perfect by any stretch of the

328
00:21:38.449 --> 00:21:44.849
<v Speaker 3>imagination, but for what you pay and the
convenience of, of just adding a wireless

329
00:21:44.849 --> 00:21:50.290
<v Speaker 3>sensor to a, a, an older type generation
hydraulic system, in

330
00:21:50.290 --> 00:21:56.609
<v Speaker 3>this particular one, Uh, our Western port
team added a pressure transmitter to just

331
00:21:56.609 --> 00:22:02.089
<v Speaker 3>use that to keep an eye on the, just the
head level in the tank, um, so that's,

332
00:22:02.250 --> 00:22:05.069
<v Speaker 3>that's what they've done in that
particular, and that does a good job.

333
00:22:05.329 --> 00:22:10.489
<v Speaker 3>Um, some other sensors that we've used,
Uh, in that sort of space too is there's,

334
00:22:10.609 --> 00:22:14.689
<v Speaker 3>there's other sort of in tank arrangement
where you could drop a probe in and it,

335
00:22:14.770 --> 00:22:18.469
<v Speaker 3>it'll give you a level and a temperature
as well, so that's kind of handy on

336
00:22:18.849 --> 00:22:24.819
<v Speaker 3>hydraulic systems, um, but yeah, this
particular example that they are, That's what

337
00:22:24.819 --> 00:22:30.300
<v Speaker 3>they've done in Western Port, so they've
just added an IoT pressure sensor to keep

338
00:22:30.300 --> 00:22:35.170
<v Speaker 3>an eye on the tank level and It's doing a,
and you know, like you, you get a,

339
00:22:35.369 --> 00:22:41.250
<v Speaker 3>maybe a data packet every half an hour,
which is, which is fine for a, um, and you

340
00:22:41.250 --> 00:22:44.890
<v Speaker 3>probably cover off a, a fair amount of
your, your failure modes with just, you know,

341
00:22:45.040 --> 00:22:51.800
<v Speaker 3>like, I mean, Big volume leaks are always
going to be problematic, um.

342
00:22:53.229 --> 00:22:56.739
<v Speaker 3>Because, you know, like, you don't have
very long to, to remedy what's going on

343
00:22:56.739 --> 00:23:01.479
<v Speaker 3>before, you know, it's, it's game over,
but the, the slower, sort of less noticeable

344
00:23:01.900 --> 00:23:06.699
<v Speaker 3>leak is the, is sort of the failure mode,
um, we're looking at trying to cover off

345
00:23:06.699 --> 00:23:06.979
<v Speaker 3>here.

346
00:23:07.839 --> 00:23:14.040
<v Speaker 3>And you know, the, this, this sensor was
maybe installed 6 months before the, before

347
00:23:14.040 --> 00:23:20.599
<v Speaker 3>the actual detection um occurred, and it's
sort of just sitting there reporting on

348
00:23:20.599 --> 00:23:26.459
<v Speaker 3>the tank level and, you know, all of a
sudden we, we had a case come up and, It was

349
00:23:26.459 --> 00:23:32.260
<v Speaker 3>a, and Chris had turned on forecasting,
which is another feature of the Sensai app.

350
00:23:32.300 --> 00:23:36.699
<v Speaker 3>It sort of, you know, you set up a
threshold and go, OK, you know, this tank, when

351
00:23:36.699 --> 00:23:42.030
<v Speaker 3>it gets down to sort of Uh, a level of 60,
I, I'd like to know about it, and so you

352
00:23:42.030 --> 00:23:44.739
<v Speaker 3>set your threshold up, and then, then we
turn on the threshold, so it sort of

353
00:23:44.739 --> 00:23:49.670
<v Speaker 3>predicts in the future, like, based on the
current metrics of how that level is, is

354
00:23:49.670 --> 00:23:54.969
<v Speaker 3>tracking, um, maybe in, Couple of weeks
that you're going to be at that tank.

355
00:23:56.170 --> 00:24:00.130
<v Speaker 3>Low level that you wanted to be reminded
of when that was due to happen, so they,

356
00:24:00.209 --> 00:24:06.079
<v Speaker 3>they got a threshold detection, um from
Sensii, they went and did a bit of

357
00:24:06.079 --> 00:24:11.300
<v Speaker 3>investigation, so this tank is, um, It's
under the normal operating force, so no-one

358
00:24:11.300 --> 00:24:15.579
<v Speaker 3>normally goes into that particular area to
keep an eye on it, and, and of course it

359
00:24:15.579 --> 00:24:19.339
<v Speaker 3>services the whole exit end of this
particular metal coating line, so there's,

360
00:24:19.540 --> 00:24:22.939
<v Speaker 3>there's pipework running off in all
different ways, going to all different sorts of,

361
00:24:23.699 --> 00:24:26.020
<v Speaker 3>Equipment in the exit in um.

362
00:24:27.609 --> 00:24:31.010
<v Speaker 3>But they, they use that detection to go,
OK, we need to go and investigate, we're

363
00:24:31.010 --> 00:24:34.969
<v Speaker 3>starting to, we've got a, a, a trend that,
that tells us that we're, we're losing

364
00:24:34.969 --> 00:24:40.829
<v Speaker 3>tank level, and we need to go and take a
look around and try and figure out, do we,

365
00:24:41.170 --> 00:24:41.939
<v Speaker 3>do we have a leak?

366
00:24:42.209 --> 00:24:42.800
<v Speaker 3>Where is the leak?

367
00:24:42.839 --> 00:24:43.810
<v Speaker 3>Is the leak visible?

368
00:24:43.930 --> 00:24:47.930
<v Speaker 3>Like, let's go and have a, just do an
inspection of the tank, so quick look around

369
00:24:47.930 --> 00:24:50.869
<v Speaker 3>the tank, couldn't find anything, so they
start to follow a bit of pipework.

370
00:24:51.410 --> 00:24:54.089
<v Speaker 3>Um, they ended up in a core car pit.

371
00:24:54.859 --> 00:25:00.250
<v Speaker 3>Where there's some fixed pipework that
runs to fuel the, the mobile core cars, and

372
00:25:00.380 --> 00:25:04.140
<v Speaker 3>yeah, I mean, I don't know if you've, if
you've seen the picture, but you can see

373
00:25:04.140 --> 00:25:06.380
<v Speaker 3>there's, there's some fixed pipework
there.

374
00:25:06.630 --> 00:25:09.660
<v Speaker 3>From the picture, it looks like it might
be like 3/4 of an inch or 0.5 inch

375
00:25:09.660 --> 00:25:14.510
<v Speaker 3>pipework, and you can see on one of the
joints there that it's just sprang a leak,

376
00:25:14.859 --> 00:25:19.780
<v Speaker 3>and, um, that leak was in a, An area of
the plant where, you know, it's down under

377
00:25:19.780 --> 00:25:23.380
<v Speaker 3>the normal operating floor, people don't
go down there unless they generally have a

378
00:25:23.819 --> 00:25:27.739
<v Speaker 3>very good reason, um, to go down there
because it's, you know, it's, it's dark, it's

379
00:25:27.739 --> 00:25:32.410
<v Speaker 3>slippery, it's not a place that, that
people are meant to go and, um, and take a

380
00:25:32.410 --> 00:25:33.459
<v Speaker 3>look at those things, so.

381
00:25:34.910 --> 00:25:35.890
<v Speaker 3>They found the leak.

382
00:25:37.630 --> 00:25:38.880
<v Speaker 3>Which was really good.

383
00:25:39.719 --> 00:25:43.680
<v Speaker 3>They thought that, you know, OK, the night
shift crew found the leak.

384
00:25:43.920 --> 00:25:47.050
<v Speaker 3>They They thought that it would be OK.

385
00:25:47.150 --> 00:25:48.540
<v Speaker 3>They just topped up the tank.

386
00:25:49.719 --> 00:25:52.439
<v Speaker 3>To cover off that, but you know, you can't
run like that because there's always a

387
00:25:52.439 --> 00:25:57.130
<v Speaker 3>potential because a leak like that can
get, can get quite bad quite quickly, so, um,

388
00:25:58.010 --> 00:26:02.359
<v Speaker 3>I guess the, the way that the, the offset,
the offset or the downtime avoided was

389
00:26:02.359 --> 00:26:08.530
<v Speaker 3>saved is they, they had time to um to
secure the hydraulic system, and, and also

390
00:26:08.530 --> 00:26:14.270
<v Speaker 3>secure the production line, so when we,
metal coating lines if, If you don't

391
00:26:14.270 --> 00:26:17.670
<v Speaker 3>progress the strip through the, the metal
bath, you can burn the strip off, and

392
00:26:17.670 --> 00:26:19.670
<v Speaker 3>that's, you know, then you need

393
00:26:19.670 --> 00:26:21.380
<v Speaker 3>to re-thread your metal can line.

394
00:26:21.430 --> 00:26:24.550
<v Speaker 3>That's kind of where the 24 hour downtime
avoided comes from.

395
00:26:24.670 --> 00:26:29.589
<v Speaker 3>So it gave the, the operations team time
to secure the production line, to, to set

396
00:26:29.589 --> 00:26:34.589
<v Speaker 3>up a, um, to get the line set up so they
could actually take some downtime and, and

397
00:26:34.589 --> 00:26:38.410
<v Speaker 3>work on this hydraulic system and, and
make repairs.

398
00:26:39.459 --> 00:26:45.819
<v Speaker 3>Um, to the hydraulic pipework, so, um, we
don't have, Um,

399
00:26:46.079 --> 00:26:49.890
<v Speaker 3>boilermakers on shift, so we had to wait
for the day shift crew to come in and, you

400
00:26:49.890 --> 00:26:53.300
<v Speaker 3>know, by that time, the line was set up
and, you know, we could get a boilermaker in

401
00:26:53.300 --> 00:26:55.400
<v Speaker 3>there to, to make some repairs.

402
00:26:55.449 --> 00:26:57.290
<v Speaker 3>I think they ended up repairing it in
situ.

403
00:26:58.180 --> 00:27:03.229
<v Speaker 3>Just tried to weld up the hole in the pipe
and Um, till they could get it to a

404
00:27:03.229 --> 00:27:07.989
<v Speaker 3>proper, you know, maintenance outage where
they could pull the pipework out and

405
00:27:07.989 --> 00:27:13.420
<v Speaker 3>either get it replaced or repaired in, in
a workshop, so that's, that's the general

406
00:27:13.420 --> 00:27:16.869
<v Speaker 3>story of, of that one, of that particular
success case.

407
00:27:18.030 --> 00:27:22.060
<v Niall Sullivan>Yeah, no, I think it's really interesting
going into that sort of detail about it

408
00:27:22.060 --> 00:27:26.060
<v Niall Sullivan>and really understanding, it is, you know,
it's rather unfortunately, I'd love to

409
00:27:26.060 --> 00:27:29.869
<v Niall Sullivan>speak to customers more about these and
understand exactly what goes beyond what I

410
00:27:29.869 --> 00:27:32.290
<v Niall Sullivan>see on that slide that, that shared
internally.

411
00:27:32.709 --> 00:27:36.989
<v Niall Sullivan>I guess it's all like you said, it's also
like a health and safety issue as well,

412
00:27:37.069 --> 00:27:37.349
<v Niall Sullivan>right?

413
00:27:37.619 --> 00:27:40.869
<v Niall Sullivan>So you said people shouldn't really go
down there unless there's a really good

414
00:27:40.869 --> 00:27:41.329
<v Niall Sullivan>reason.

415
00:27:41.729 --> 00:27:46.530
<v Niall Sullivan>So it's actually rather than, again, if
people can go down there when they know they

416
00:27:46.530 --> 00:27:48.520
<v Niall Sullivan>need to, then that's obviously a a
benefit,

417
00:27:48.569 --> 00:27:48.810
<v Speaker 3>right?

418
00:27:49.000 --> 00:27:55.199
<v Speaker 3>Yeah, and that's not sort of the only
safety concern, um, that's sort of wrapped up

419
00:27:55.199 --> 00:27:55.930
<v Speaker 3>in this episode.

420
00:27:56.040 --> 00:27:58.729
<v Speaker 3>So yeah, you know, we had the, the
hydraulic leak, that's not good.

421
00:27:58.810 --> 00:28:02.770
<v Speaker 3>There's always potential hazards involved
in that and, you know, working in and

422
00:28:02.770 --> 00:28:03.160
<v Speaker 3>around that.

423
00:28:03.290 --> 00:28:05.390
<v Speaker 3>So this, this hydraulic system.

424
00:28:05.900 --> 00:28:10.020
<v Speaker 3>Um, if we didn't have any sort of
forewarning, um, the only protection we had

425
00:28:10.020 --> 00:28:13.760
<v Speaker 3>outside of the IOT and, and sensor is
that, that low-level switch.

426
00:28:13.900 --> 00:28:17.180
<v Speaker 3>If, if that activates, it stops the pump
dead.

427
00:28:17.949 --> 00:28:22.829
<v Speaker 3>And you can't restart it until you, um,
you know, you get some level, we cover some

428
00:28:22.829 --> 00:28:25.550
<v Speaker 3>level back into the tank, because that's
set up to protect the pumps, right, that's,

429
00:28:25.630 --> 00:28:31.550
<v Speaker 3>that's pretty standard, um, that would
render our, our exit end of that production

430
00:28:31.550 --> 00:28:36.780
<v Speaker 3>line, um, You couldn't move it, it, it
would be, you, you couldn't move it forward

431
00:28:36.780 --> 00:28:40.540
<v Speaker 3>or backwards, there'd be no permissives or
any of the hydraulic systems to, to make

432
00:28:40.540 --> 00:28:46.260
<v Speaker 3>the, the exit and move, so, Yeah, you, you
would be, not be able to progress the

433
00:28:46.260 --> 00:28:47.859
<v Speaker 3>strip through the metal bath and then you
burn

434
00:28:47.859 --> 00:28:48.300
<v Speaker 3>it off.

435
00:28:48.660 --> 00:28:52.930
<v Speaker 3>The problem, like one of the bigger
problems with that is that then exposes a lot of

436
00:28:52.930 --> 00:28:57.319
<v Speaker 3>our operation teams to, to do a lot of
manual handling of the strip to recover it.

437
00:28:57.650 --> 00:29:02.969
<v Speaker 3>Um, and that's, that's not great, you
know, like, you know, we have precautions on,

438
00:29:03.079 --> 00:29:05.540
<v Speaker 3>on how we deal with that, but it's always
better not to do it at all.

439
00:29:05.650 --> 00:29:10.640
<v Speaker 3>So, um, you know, there's always lots of
potentials for strains and sprains and,

440
00:29:10.800 --> 00:29:14.329
<v Speaker 3>and, you know, cuts and abrasions when
you're handling, you know, sort of light

441
00:29:14.329 --> 00:29:15.250
<v Speaker 3>gauge metal strips.

442
00:29:15.349 --> 00:29:19.760
<v Speaker 3>So, That is definitely another thing to,
and that doesn't come across in the success

443
00:29:19.760 --> 00:29:23.479
<v Speaker 3>slide, but, you know, that's, when you
talk about them internally, that's another

444
00:29:23.479 --> 00:29:28.119
<v Speaker 3>thing that, you know, someone normally
talks about is the, You know, there's always

445
00:29:28.380 --> 00:29:33.430
<v Speaker 3>sort of multiplying factors when you sort
of avoid situations like this.

446
00:29:34.709 --> 00:29:35.060
<v Speaker 3>Yeah.

447
00:29:35.939 --> 00:29:40.380
<v Niall Sullivan>Yeah, no, absolutely, absolutely, it's
not, yeah, cause I, I guess the focus is

448
00:29:40.380 --> 00:29:42.140
<v Niall Sullivan>usually, you know, you see the big
headline figure.

449
00:29:42.180 --> 00:29:46.060
<v Niall Sullivan>I mean in this case I think it was 24
hours downtime, you know, saved, I believe on

450
00:29:46.060 --> 00:29:46.520
<v Niall Sullivan>this one.

451
00:29:47.099 --> 00:29:51.689
<v Niall Sullivan>but yeah, it's all these other benefits or
outcomes as well which are, you know,

452
00:29:52.180 --> 00:29:55.300
<v Niall Sullivan>just as important, you could say, I
suppose, well, more important if you think about

453
00:29:55.300 --> 00:29:56.119
<v Niall Sullivan>health and safety.

454
00:29:56.770 --> 00:29:57.689
<v Niall Sullivan>Um, definitely.

455
00:29:57.729 --> 00:30:00.089
<v Niall Sullivan>I was gonna, I was gonna touch on cos you
mentioned, you mentioned about the

456
00:30:00.089 --> 00:30:02.229
<v Niall Sullivan>forecasting functionality and sense.

457
00:30:02.359 --> 00:30:06.219
<v Niall Sullivan>I wanted to combine that with obviously
the new piece of functionality, rela

458
00:30:06.680 --> 00:30:11.890
<v Niall Sullivan>relatively new, um, and, going to be
enhanced even further very shortly as well, but

459
00:30:11.890 --> 00:30:14.189
<v Niall Sullivan>the, the copilot functionality.

460
00:30:14.530 --> 00:30:18.089
<v Niall Sullivan>So I guess first of all, Chris, maybe just
your general view on the functionality,

461
00:30:18.209 --> 00:30:19.030
<v Niall Sullivan>you know, so far.

462
00:30:19.780 --> 00:30:23.670
<v Niall Sullivan>Um, and you, you and your colleagues,
what, you know, their experience of it, but in

463
00:30:23.670 --> 00:30:27.790
<v Niall Sullivan>this particular example, how did it, cos I
know it was featured on the, on the

464
00:30:27.790 --> 00:30:30.689
<v Niall Sullivan>success side, how has it helped, you know,
to identify the fault and.

465
00:30:31.410 --> 00:30:37.880
<v Speaker 3>I, I, I, well, it, it just helps build
confidence in, in what it, what it can do,

466
00:30:38.010 --> 00:30:42.849
<v Speaker 3>and it gets people very excited about,
because it's still very, um, I guess I'd call

467
00:30:42.849 --> 00:30:47.599
<v Speaker 3>it juvenile, like, it's not very far down
the track, and that's based on, you know,

468
00:30:47.859 --> 00:30:53.540
<v Speaker 3>us and our case feedback and, and how
much, How much better the, the AI will be once

469
00:30:53.540 --> 00:30:57.640
<v Speaker 3>it ingests all that sort of information
and it sees, you know, you know, next time

470
00:30:57.640 --> 00:31:01.359
<v Speaker 3>we see a case like this, um, that's one of
the likely causes it's

471
00:31:01.359 --> 00:31:06.760
<v Speaker 3>obviously gonna throw at us, and it didn't
even need to see, Um, sort of that, like,

472
00:31:06.839 --> 00:31:11.000
<v Speaker 3>cause I, I had a look at the, what the
co-pilot said about this particular case, and

473
00:31:11.000 --> 00:31:12.160
<v Speaker 3>it, it mentioned three things.

474
00:31:12.239 --> 00:31:16.239
<v Speaker 3>And like, if you think about, you know,
what would you think about if you were

475
00:31:16.239 --> 00:31:18.640
<v Speaker 3>seeing a decline in the hydraulic tank
level?

476
00:31:19.000 --> 00:31:22.920
<v Speaker 3>Like you'd, you'd go, OK, um, we've got a
leak.

477
00:31:23.040 --> 00:31:24.760
<v Speaker 3>That's pretty basic, yep, nailed that one.

478
00:31:25.180 --> 00:31:31.229
<v Speaker 3>And then it, it spoke about, oh, this
might be a natural consumption of, of oil,

479
00:31:31.520 --> 00:31:38.140
<v Speaker 3>and, and that's also a possibility, um, we
do have other sort of lubrication, not so

480
00:31:38.140 --> 00:31:42.420
<v Speaker 3>much hydraulic tanks, but other
lubrication systems where, you know, as we change

481
00:31:42.420 --> 00:31:47.119
<v Speaker 3>our work roles here and there, there,
there's an, an, an amount of lubricating oil

482
00:31:47.380 --> 00:31:51.250
<v Speaker 3>in the workro bearing that, you know, you
lose when you pull that, that roll out of

483
00:31:51.250 --> 00:31:55.109
<v Speaker 3>service, so, you know, that's a likely
thing in our, In our

484
00:31:55.109 --> 00:31:59.270
<v Speaker 3>space, and the other one is, well,
whatever you've got to measure the level is, is

485
00:31:59.270 --> 00:31:59.709
<v Speaker 3>faulty.

486
00:31:59.790 --> 00:32:03.310
<v Speaker 3>So, you know, if you had a bit of a think
about what would be the 3 off the top of

487
00:32:03.310 --> 00:32:10.000
<v Speaker 3>your head, the top 3 likely scenarios that
That, um, probably you could

488
00:32:10.140 --> 00:32:14.180
<v Speaker 3>generate from seeing a, a decline in the
tank level like this, they're probably the

489
00:32:14.180 --> 00:32:19.660
<v Speaker 3>top three that I'd think of, um, and the
AI component, like, the co-pilot has, has

490
00:32:19.660 --> 00:32:20.099
<v Speaker 3>picked that up.

491
00:32:20.180 --> 00:32:26.260
<v Speaker 3>I mean, this is not, it's not an overly
complex type of, of case, um, but yeah, it's

492
00:32:26.260 --> 00:32:30.219
<v Speaker 3>sort of just, it gives people a little bit
of confidence like, OK, this, this is

493
00:32:30.219 --> 00:32:34.930
<v Speaker 3>worth, um, when you do get a case, it's
like, it is worth taking a look at that

494
00:32:34.930 --> 00:32:41.579
<v Speaker 3>particular, um, Suggestions or, or likely
outcomes that the, the co-pilot throws up

495
00:32:41.579 --> 00:32:47.339
<v Speaker 3>at you, so, that's really good, um, and it
gets people excited, you know, like,

496
00:32:47.859 --> 00:32:50.060
<v Speaker 3>what's gonna happen to the co-pilot when

497
00:32:50.060 --> 00:32:56.959
<v Speaker 3>we start, um, we have multiple cases and,
you know, How, how is that going to

498
00:32:56.959 --> 00:33:00.800
<v Speaker 3>affect it and, and enrich the, the
feedback that we're gonna get from it, you know,

499
00:33:00.989 --> 00:33:05.000
<v Speaker 3>if we put good solid case feedback in, how
much more is that going to enrich the

500
00:33:05.000 --> 00:33:11.459
<v Speaker 3>AI's capability of, you know, collecting
the, the information, uh, and, and

501
00:33:11.939 --> 00:33:16.489
<v Speaker 3>storing that sort of knowledge within the
system that we have from now for the, The

502
00:33:16.489 --> 00:33:19.939
<v Speaker 3>next generation to um to use and to, and

503
00:33:19.939 --> 00:33:24.569
<v Speaker 3>to build on, so that's, that's a really
important part of, what, what the app can

504
00:33:24.569 --> 00:33:31.469
<v Speaker 3>do, like we do have, um, Let's say a very
experienced workforce and some

505
00:33:31.469 --> 00:33:37.349
<v Speaker 3>of them coming to the end of their
careers, and how do we get what they know.

506
00:33:38.180 --> 00:33:44.270
<v Speaker 3>Um, Into a platform like this and you know
case feedback is a very good way and also

507
00:33:44.270 --> 00:33:50.910
<v Speaker 3>the possibility of uploading documentation
and having the AI ingest that is also,

508
00:33:52.089 --> 00:33:55.250
<v Speaker 3>That, that gets people really excited, you
know, cause there's, there's a multitude

509
00:33:55.250 --> 00:33:59.810
<v Speaker 3>of documents that we have that we can
upload into the system to, to help us out with

510
00:33:59.810 --> 00:34:06.130
<v Speaker 3>the, the copilot and what it can, the
power of that and what it can do, um, You

511
00:34:06.130 --> 00:34:08.100
<v Speaker 3>know, because like in a couple of years'
time, you know,

512
00:34:08.370 --> 00:34:13.250
<v Speaker 3>this one might not be super complicated
for, for everyone to look at, but there's

513
00:34:13.250 --> 00:34:17.870
<v Speaker 3>other ones that That aren't, you know,
maybe when the, the data that we have

514
00:34:17.870 --> 00:34:24.270
<v Speaker 3>available isn't straightforward in
explaining what's actually happening, um, with

515
00:34:24.270 --> 00:34:24.830
<v Speaker 3>the system.

516
00:34:24.949 --> 00:34:31.729
<v Speaker 3>So the potential is, is huge, and we're,
we're quite excited about where we can,

517
00:34:32.030 --> 00:34:33.070
<v Speaker 3>where we can take this.

518
00:34:33.120 --> 00:34:38.550
<v Speaker 3>And yeah, can't wait till the, we can
upload documents and, uh, and have that

519
00:34:38.550 --> 00:34:44.060
<v Speaker 3>uploaded into the, the AI and, um, Yeah,
excited about that.

520
00:34:44.999 --> 00:34:49.319
<v Niall Sullivan>Yeah, but, and that should, uh, I don't I
was about to put a timeline on it, but I'm

521
00:34:49.319 --> 00:34:52.358
<v Niall Sullivan>sure you're, you're in very close contact,
I know, with Dan and the team the team,

522
00:34:52.479 --> 00:34:54.589
<v Niall Sullivan>so they, they'll keep you up to date with
that.

523
00:34:54.638 --> 00:34:58.198
<v Niall Sullivan>But I know that is something being
actively, you know, explored and worked on.

524
00:34:58.358 --> 00:35:02.229
<v Niall Sullivan>That's one thing I can say, um, and you're
right, it's very, so I guess what you're

525
00:35:02.229 --> 00:35:06.458
<v Niall Sullivan>saying, Chris, as well, it's, it's, it's
almost this single source of truth that.

526
00:35:07.030 --> 00:35:10.310
<v Niall Sullivan>You know, for information and knowledge
capture, and that's what we've sort of

527
00:35:10.310 --> 00:35:11.750
<v Niall Sullivan>identified with this as well.

528
00:35:11.949 --> 00:35:14.870
<v Niall Sullivan>It's not just like a gimmicky kind of
thing, but it's actually it's somewhere you

529
00:35:14.870 --> 00:35:19.709
<v Niall Sullivan>can capture knowledge, and then we all, we
term it and talking to other customers as

530
00:35:19.709 --> 00:35:23.899
<v Niall Sullivan>well, I can sort of see where this works,
it's almost like a virtual maintenance

531
00:35:23.899 --> 00:35:28.070
<v Niall Sullivan>person who knows everything about your,
every asset, or in theory, you know, has the

532
00:35:28.070 --> 00:35:30.629
<v Niall Sullivan>data of course to start with and the
knowledge.

533
00:35:30.750 --> 00:35:33.969
<v Speaker 3>Yeah, absolutely, and like I think it was.

534
00:35:34.429 --> 00:35:38.389
<v Speaker 3>Because we've been playing with the, we
were involved in the beta trial of, of this,

535
00:35:38.429 --> 00:35:44.469
<v Speaker 3>and I think it was maybe day 3, we had a,
a case, um, where we're just looking at,

536
00:35:44.520 --> 00:35:48.530
<v Speaker 3>we're just monitoring the relationship
between, like a process variable and a

537
00:35:48.530 --> 00:35:53.429
<v Speaker 3>control valve, and, You know, it had been
synchronized for so long, you know, like,

538
00:35:53.590 --> 00:35:59.270
<v Speaker 3>you know, I'm at 100% flow, um, like 100%
valve open and I'm getting a flow of X.

539
00:35:59.429 --> 00:36:03.629
<v Speaker 3>And then like that relationship was well
established and it had been in the app for,

540
00:36:03.739 --> 00:36:08.989
<v Speaker 3>for a while, but then, um, we, we started
seeing a drift, you know, we, we started

541
00:36:08.989 --> 00:36:14.209
<v Speaker 3>to have to use more valve position to
maintain that same sort of, um, flow.

542
00:36:14.229 --> 00:36:18.909
<v Speaker 3>And the, what the co-pilot came up with,
it was, it was kind of a little bit.

543
00:36:19.449 --> 00:36:20.340
<v Speaker 3>Mind-boggling.

544
00:36:20.439 --> 00:36:23.810
<v Speaker 3>And like, how does it, where does it get
this information from?

545
00:36:23.929 --> 00:36:30.389
<v Speaker 3>How does it do it like in, You know, um,
Maybe not everyone that comes across it

546
00:36:30.389 --> 00:36:34.000
<v Speaker 3>understands how it works, I, I certainly
don't, but it, it was, it was saying

547
00:36:34.000 --> 00:36:39.260
<v Speaker 3>something like, oh, you know, you've
potentially got a restriction in your pipe, um,

548
00:36:39.879 --> 00:36:43.820
<v Speaker 3>or you've got a problem with your, your
control valve, like the calibration of your

549
00:36:43.820 --> 00:36:47.879
<v Speaker 3>control valves out, or what you're using
to measure your process variable, has

550
00:36:47.879 --> 00:36:52.500
<v Speaker 3>drifted, and I'm like, that's kind of, You
know, if you, if you sat down and thought

551
00:36:52.500 --> 00:36:53.860
<v Speaker 3>about it, you'd probably go,

552
00:36:53.929 --> 00:36:58.260
<v Speaker 3>yeah, OK, they're, they're probably 3
really good scenarios, and I'm like, this is,

553
00:36:58.340 --> 00:36:59.679
<v Speaker 3>this thing's 3 days old.

554
00:36:59.780 --> 00:37:06.649
<v Speaker 3>Like this is, this is kind of ridiculous
what it can do and That was a little bit, a

555
00:37:06.649 --> 00:37:11.409
<v Speaker 3>little bit scary in terms of, well, where
can we take this, what, what's it going to

556
00:37:11.409 --> 00:37:15.370
<v Speaker 3>be like in a couple of years' time when
it's had time to ingest more and see more

557
00:37:15.370 --> 00:37:22.040
<v Speaker 3>data and It's, um, yeah, I think that's a,
that's a really strong point of

558
00:37:22.040 --> 00:37:28.500
<v Speaker 3>this particular platform, and, um, You
know, It it makes it, yeah, like you, you

559
00:37:28.500 --> 00:37:29.580
<v Speaker 3>show them just the standard stuff,

560
00:37:29.659 --> 00:37:32.939
<v Speaker 3>oh yeah, we just monitor a tank level, and
you show your customers that, and they're

561
00:37:32.939 --> 00:37:36.179
<v Speaker 3>like, oh, that's cool, that'd be kind of
handy, but then you, you show them some of

562
00:37:36.179 --> 00:37:41.540
<v Speaker 3>the more, Higher level, complex,
complicated machines and some of the cases and the,

563
00:37:41.629 --> 00:37:46.709
<v Speaker 3>the co-pilot feedback, it's like, this has
a lot of potential, and then you say, oh,

564
00:37:46.790 --> 00:37:51.669
<v Speaker 3>by the way, we can feed this thing any
sort of, you know, functional specifications

565
00:37:51.669 --> 00:37:57.550
<v Speaker 3>we have or anything, make this procedures,
feed it, anything, and, you know, how

566
00:37:57.550 --> 00:37:59.629
<v Speaker 3>does it, how does it take the,

567
00:37:59.729 --> 00:38:04.590
<v Speaker 3>the wording in your, um, functional specs
and relate it to the wording that you

568
00:38:04.590 --> 00:38:05.889
<v Speaker 3>call, like your measures.

569
00:38:06.659 --> 00:38:10.419
<v Speaker 3>I don't know, but that's, that's going to
be the fun part, figuring that out and,

570
00:38:10.500 --> 00:38:15.320
<v Speaker 3>and how that all is, uh, is going to
benefit, you know, I guess, everyone that comes

571
00:38:15.320 --> 00:38:21.429
<v Speaker 3>across the, The app, so very exciting, um,
the potential is kind of mind boggling,

572
00:38:21.439 --> 00:38:22.120
<v Speaker 3>and yeah.

573
00:38:23.169 --> 00:38:26.270
<v Speaker 3>Can't wait to, I think we'll have our
hands on it by the end of the year.

574
00:38:27.080 --> 00:38:27.340
<v Niall Sullivan>Yeah,

575
00:38:28.060 --> 00:38:28.209
<v Speaker 3>absolutely.

576
00:38:29.469 --> 00:38:34.310
<v Niall Sullivan>Absolutely, and I think, um, I think for
you guys as well it's almost, you know, a

577
00:38:34.310 --> 00:38:37.110
<v Niall Sullivan>very big opportunity because you've got
such a, with the global rollout you're

578
00:38:37.110 --> 00:38:39.949
<v Niall Sullivan>talking about, you know, you're talking
about knowledge sharing and stuff that we be

579
00:38:39.949 --> 00:38:44.709
<v Niall Sullivan>able to compare this case over here to
this case over here, maybe even have

580
00:38:44.709 --> 00:38:47.899
<v Niall Sullivan>discussions and ask questions, bring
people into the conversation.

581
00:38:47.949 --> 00:38:50.629
<v Niall Sullivan>I mean I am getting ahead of myself
because that might be a bit later on, so I'm not

582
00:38:50.629 --> 00:38:54.229
<v Niall Sullivan>promising this just to, but I think this
is where it's heading.

583
00:38:54.350 --> 00:38:57.530
<v Niall Sullivan>I, I can safely say it's probably where
it's heading at some point in the future,

584
00:38:57.909 --> 00:38:58.830
<v Niall Sullivan>um, to bring.

585
00:38:59.250 --> 00:39:04.520
<v Niall Sullivan>You know, the collaboration between
machine people and the co-pilot basically is, is

586
00:39:04.520 --> 00:39:06.050
<v Niall Sullivan>sort of where I think it's going.

587
00:39:06.929 --> 00:39:08.909
<v Speaker 3>And we don't have a lot of.

588
00:39:09.689 --> 00:39:13.919
<v Speaker 3>I can't think of another platform that
that we have that is.

589
00:39:14.699 --> 00:39:19.459
<v Speaker 3>Like a global platform that anyone in our
business can, can take a look at.

590
00:39:19.540 --> 00:39:26.500
<v Speaker 3>Like we have lots of metal coating lines
around the world and, you know, like they

591
00:39:26.500 --> 00:39:30.780
<v Speaker 3>don't actually have to talk to me about,
well, where have you deployed monitoring,

592
00:39:30.860 --> 00:39:32.620
<v Speaker 3>like what machines, and how have you done
it.

593
00:39:32.659 --> 00:39:37.179
<v Speaker 3>They can just jump on, onto the app and
take a look, which is You know, that's,

594
00:39:37.270 --> 00:39:42.550
<v Speaker 3>that's really good, and you know, you're
talking about, um, You know Comparing

595
00:39:42.550 --> 00:39:46.520
<v Speaker 3>assets to assets and they don't have to be
sitting beside each other.

596
00:39:46.590 --> 00:39:50.709
<v Speaker 3>They can be on the other side of the world
like we have lots of Inductors we use to

597
00:39:50.709 --> 00:39:52.050
<v Speaker 3>heat up metal.

598
00:39:52.929 --> 00:39:57.330
<v Speaker 3>There's, there's no reason why we can't
have like a, a global dashboard with all the

599
00:39:57.330 --> 00:40:03.050
<v Speaker 3>same measures on there comparing
conductors in, you know, Thailand to Port Kembla to

600
00:40:03.050 --> 00:40:04.570
<v Speaker 3>Melbourne to, to New Zealand.

601
00:40:04.679 --> 00:40:06.870
<v Speaker 3>It, it's, it's a, it's a good platform.

602
00:40:07.090 --> 00:40:12.969
<v Speaker 3>There's not a lot of other platforms we
have where we can see real-time, um, data on

603
00:40:12.969 --> 00:40:16.949
<v Speaker 3>all those different sort of assets from
different parts of the world and, you know.

604
00:40:17.870 --> 00:40:21.860
<v Speaker 3>You know, if you've got a problem with
your particular inductor, and you, uh, I've

605
00:40:21.860 --> 00:40:26.629
<v Speaker 3>noticed that this conductance ratio or, or
something like that, or this power

606
00:40:26.629 --> 00:40:28.449
<v Speaker 3>factors change from here to here.

607
00:40:29.270 --> 00:40:33.209
<v Speaker 3>Can I find that in, you know, did this
happen somewhere else?

608
00:40:33.939 --> 00:40:37.580
<v Speaker 3>You know, I might be in Port Kembla, have
I seen this anywhere else around the

609
00:40:37.580 --> 00:40:38.050
<v Speaker 3>business?

610
00:40:38.100 --> 00:40:42.580
<v Speaker 3>And, you're like, oh, there's an inductor
in New Zealand that did the same thing six

611
00:40:42.580 --> 00:40:45.100
<v Speaker 3>months ago, but it's still chugging along.

612
00:40:45.149 --> 00:40:45.929
<v Speaker 3>It's OK.

613
00:40:46.100 --> 00:40:47.179
<v Speaker 3>Like it's still hanging in there.

614
00:40:47.260 --> 00:40:50.939
<v Speaker 3>Like, uh, and now I feel a little bit
more, OK, I feel a little bit more comfortable

615
00:40:50.939 --> 00:40:51.580
<v Speaker 3>with what I'm seeing.

616
00:40:51.659 --> 00:40:55.219
<v Speaker 3>Like, you know, you can, I, I don't know
what this is gonna, like, it's great to

617
00:40:55.219 --> 00:40:55.679
<v Speaker 3>have data.

618
00:40:55.800 --> 00:40:59.010
<v Speaker 3>It's, it's one thing to have data, it's
another thing to know how to react to it.

619
00:40:59.419 --> 00:41:02.800
<v Speaker 3>Um, and, and I guess that's where
co-piloting can help.

620
00:41:03.449 --> 00:41:08.310
<v Speaker 3>And, um, and, but just being able to, to
find that particular data in another asset

621
00:41:08.459 --> 00:41:13.239
<v Speaker 3>on the other side of the world without
even talking to them is, you know, that's a

622
00:41:13.239 --> 00:41:15.810
<v Speaker 3>phenomenal advantage to have as well.

623
00:41:15.929 --> 00:41:16.729
<v Speaker 3>So that's good.

624
00:41:17.590 --> 00:41:20.500
<v Niall Sullivan>Yeah, no, very powerful stuff, very
powerful stuff.

625
00:41:20.870 --> 00:41:24.949
<v Niall Sullivan>Um, I wanna be, I'm conscious of our time
because we're, we're slightly over, and I

626
00:41:24.949 --> 00:41:28.709
<v Niall Sullivan>know, um, it's late where you are, early
where I am, but not that that matters, but

627
00:41:28.709 --> 00:41:32.070
<v Niall Sullivan>it's late where you are, most importantly,
so I don't wanna keep you too much on,

628
00:41:32.149 --> 00:41:36.500
<v Niall Sullivan>but I just thought to finish, it'd be
interesting, um, and thank you for sharing,

629
00:41:36.590 --> 00:41:39.899
<v Niall Sullivan>you know, you, so much on that, on that
particular case in your experience in the

630
00:41:39.899 --> 00:41:40.030
<v Niall Sullivan>sense.

631
00:41:40.149 --> 00:41:42.169
<v Niall Sullivan>It's really, I mean, it's really useful
for the audience.

632
00:41:42.689 --> 00:41:46.820
<v Niall Sullivan>But just to finish, I guess for other
companies now looking at, um, you know,

633
00:41:47.020 --> 00:41:50.719
<v Niall Sullivan>deploying predictive maintenance
solutions, is there any sort of particular advice

634
00:41:51.100 --> 00:41:55.659
<v Niall Sullivan>you would give Chris, um, as you're, you
know, I, I'd say in the middle of a

635
00:41:55.659 --> 00:41:58.620
<v Niall Sullivan>successful deployment because it's still
ongoing, like I said, with new sites coming

636
00:41:58.620 --> 00:42:02.239
<v Niall Sullivan>on all the time, but do you have any
advice for people what, what they need to sort

637
00:42:02.239 --> 00:42:03.439
<v Niall Sullivan>of think about and consider?

638
00:42:04.840 --> 00:42:11.729
<v Speaker 3>Um, I think, uh, find a good vendor is, is
a good thing,

639
00:42:11.850 --> 00:42:18.370
<v Speaker 3>um, find a good vendor that, and we do a
lot of, um, digital transformation stuff on

640
00:42:18.370 --> 00:42:23.580
<v Speaker 3>different platforms, we have like
connected field workers and, Um, you know, uh,

641
00:42:23.699 --> 00:42:28.739
<v Speaker 3>authority to work systems and, you know,
um, another maintenance platform that

642
00:42:28.739 --> 00:42:33.530
<v Speaker 3>we're, we're in the middle of, you know,
and they're up to different stages of MVP

643
00:42:33.530 --> 00:42:34.580
<v Speaker 3>type stuff and, you know,

644
00:42:34.780 --> 00:42:36.290
<v Speaker 3>just about to roll that type of thing.

645
00:42:36.899 --> 00:42:39.620
<v Speaker 3>Find a good vendor that's, that's going to
be willing to work with you.

646
00:42:39.719 --> 00:42:42.520
<v Speaker 3>That's, that's a, a good piece of the
puzzle.

647
00:42:42.750 --> 00:42:45.810
<v Speaker 3>Um, It's still all about people.

648
00:42:47.260 --> 00:42:51.060
<v Speaker 3>Digital transformation is definitely all
about people finding the right people

649
00:42:51.060 --> 00:42:55.870
<v Speaker 3>within your business that That are, you
know, maybe sick of banging their head

650
00:42:55.870 --> 00:43:00.310
<v Speaker 3>against a brick wall and getting the same
result to, you know, what can we do to get

651
00:43:00.310 --> 00:43:00.469
<v Speaker 3>better?

652
00:43:00.590 --> 00:43:03.830
<v Speaker 3>Like, what's going to be the next step
change in our performance if you find people

653
00:43:03.830 --> 00:43:04.949
<v Speaker 3>that are thirsty for that.

654
00:43:05.620 --> 00:43:09.570
<v Speaker 3>Um Find those people and put them in the
thick of things.

655
00:43:10.270 --> 00:43:11.510
<v Speaker 3>And the last one is.

656
00:43:12.790 --> 00:43:13.429
<v Speaker 3>Data.

657
00:43:13.830 --> 00:43:14.699
<v Speaker 3>Gotta have data.

658
00:43:15.709 --> 00:43:20.310
<v Speaker 3>Data's kind of good, and you know there,
there's ways of supplementing, um, what you

659
00:43:20.310 --> 00:43:26.040
<v Speaker 3>have, like we do, reasonably good things,
like this is like tank level is, is one,

660
00:43:26.830 --> 00:43:30.949
<v Speaker 3>and that's not a complex piece of data,
that's, that's a very simple piece of data

661
00:43:30.949 --> 00:43:35.229
<v Speaker 3>and it's sometimes what you do with it
rather than what it actually is, and we have

662
00:43:35.229 --> 00:43:40.800
<v Speaker 3>other things like where we, um, we just
monitor how many times a, A hydraulic pump

663
00:43:40.800 --> 00:43:44.879
<v Speaker 3>starts to lift the dead weight accumulate
into the air per shift, and, you know,

664
00:43:45.120 --> 00:43:45.679
<v Speaker 3>normal is 2

665
00:43:45.679 --> 00:43:47.750
<v Speaker 3>or 3 times it starts in a 12-hour shift.

666
00:43:48.320 --> 00:43:49.969
<v Speaker 3>What does it mean if it starts at 6?

667
00:43:50.229 --> 00:43:54.159
<v Speaker 3>It probably means you've got a leak for
somewhere in, another group that, not this

668
00:43:54.159 --> 00:43:57.840
<v Speaker 3>particular group in Western Port, but
some, the plate mill people up here in Port

669
00:43:57.840 --> 00:44:02.399
<v Speaker 3>Kembba, like, they know that if that pump
starts, you know, 6 or 7 times in a shift

670
00:44:02.399 --> 00:44:04.919
<v Speaker 3>compared to the north to 3, they know
they've got a leak somewhere.

671
00:44:05.469 --> 00:44:09.750
<v Speaker 3>And, um, they know that that hydraulic
system, it supplies that cylinder, that

672
00:44:09.750 --> 00:44:13.909
<v Speaker 3>cylinder, and that cylinder, and then that
particular valve bank, and they just go

673
00:44:13.909 --> 00:44:19.199
<v Speaker 3>for a walk around and, you know, 9 times
out of 10, they can see a fairly obvious,

674
00:44:19.300 --> 00:44:21.429
<v Speaker 3>um, you know, leak somewhere.

675
00:44:21.510 --> 00:44:25.239
<v Speaker 3>So it's also Get your hands on your data,
um.

676
00:44:26.030 --> 00:44:30.110
<v Speaker 3>And it doesn't have to be anything super
complex to get started, and you know, once

677
00:44:30.110 --> 00:44:35.790
<v Speaker 3>you get started, you'll, you'll innovate
and tap into other people that You know,

678
00:44:36.649 --> 00:44:41.209
<v Speaker 3>like, it's, we should get a, a global sort
of sense like customers forum going that

679
00:44:41.209 --> 00:44:45.850
<v Speaker 3>we can, you know, just share a few ideas
and I'm sure there'd be some benefit in

680
00:44:45.850 --> 00:44:46.580
<v Speaker 3>that to.

681
00:44:47.629 --> 00:44:51.209
<v Speaker 3>Yeah, that would be my take, and it takes
a lot of energy, but that's all right.

682
00:44:51.540 --> 00:44:54.340
<v Speaker 3>You've got to find those people with the
energy and the passion and the drive to do

683
00:44:54.340 --> 00:44:54.560
<v Speaker 3>it.

684
00:44:55.350 --> 00:44:58.469
<v Speaker 3>And um The success will just come.

685
00:44:58.889 --> 00:45:00.290
<v Speaker 3>Trust the process, it'll come.

686
00:45:01.830 --> 00:45:03.100
<v Niall Sullivan>Yeah, absolutely.

687
00:45:03.260 --> 00:45:04.899
<v Niall Sullivan>No, really good advice there.

688
00:45:05.020 --> 00:45:09.290
<v Niall Sullivan>And, yeah, I mean, we, yeah, I guess we
call them sort of champions as well, so

689
00:45:09.290 --> 00:45:13.330
<v Niall Sullivan>people really, you know, sort of
passionate, believe in it, and can really drive it

690
00:45:13.330 --> 00:45:19.139
<v Niall Sullivan>within organization, um, as well across
organization, I guess, um, is key, like you

691
00:45:19.139 --> 00:45:19.399
<v Niall Sullivan>said.

692
00:45:20.780 --> 00:45:25.830
<v Niall Sullivan>Um, but no, yeah, but no, thank you, yeah,
thank you so much for your time again,

693
00:45:25.949 --> 00:45:26.229
<v Niall Sullivan>Chris.

694
00:45:26.310 --> 00:45:30.739
<v Niall Sullivan>Um, I found it really, um, interesting
diving into, um, to that success case, but

695
00:45:30.739 --> 00:45:34.590
<v Niall Sullivan>also obviously learning more about the
overall, um, sort of Blue Scope project and

696
00:45:34.590 --> 00:45:36.909
<v Niall Sullivan>long may it continue as well, so, to that.

697
00:45:37.310 --> 00:45:41.989
<v Niall Sullivan>Um, but I guess if people wanna sort of
reach out to you directly, um, maybe on

698
00:45:41.989 --> 00:45:43.550
<v Niall Sullivan>LinkedIn or something like that.

699
00:45:44.850 --> 00:45:46.689
<v Speaker 3>Not actually on LinkedIn yet.

700
00:45:46.810 --> 00:45:48.570
<v Speaker 3>I'd, I'd like to get around to do that.

701
00:45:48.689 --> 00:45:50.989
<v Speaker 3>That might be a good opportunity for me,
but, um.

702
00:45:52.080 --> 00:45:56.280
<v Speaker 3>I guess if, if they're, your, your
customers, then they, they can reach out, they

703
00:45:56.280 --> 00:45:58.669
<v Speaker 3>can probably get to me through the Siemens
people.

704
00:45:59.360 --> 00:46:00.879
<v Niall Sullivan>Exactly, exactly, that's a very good
point.

705
00:46:00.989 --> 00:46:03.959
<v Niall Sullivan>I don't know, I, I presume everyone's on
LinkedIn, but just because I am doesn't

706
00:46:03.959 --> 00:46:04.810
<v Niall Sullivan>mean everyone else is.

707
00:46:05.000 --> 00:46:06.520
<v Niall Sullivan>But no, that's, that's absolutely true.

708
00:46:06.590 --> 00:46:11.760
<v Niall Sullivan>So please reach out, um, to the Siemens
team, and we can, um, either, uh, make an

709
00:46:11.760 --> 00:46:16.600
<v Niall Sullivan>introduction to Chris or, or just explain
a little bit more about the, the fantastic

710
00:46:16.600 --> 00:46:17.760
<v Niall Sullivan>success going, going on.

711
00:46:18.159 --> 00:46:22.090
<v Niall Sullivan>Um, going on there as well, but for now,
thank you, Chris, for your time and for

712
00:46:22.090 --> 00:46:25.120
<v Niall Sullivan>taking part and thank you everyone out
there for listening, and we'll see you on the

713
00:46:25.120 --> 00:46:25.840
<v Niall Sullivan>next episode.

714
00:46:26.110 --> 00:46:26.939
<v Niall Sullivan>Thank you very much.

715
00:46:28.040 --> 00:46:28.459
<v Speaker 3>Thanks.

716
00:46:30.419 --> 00:46:35.379
<v Speaker 1>Please like and subscribe on all major
podcast channels and find out more about

717
00:46:35.379 --> 00:46:38.760
<v Speaker 1>Sensii predictive maintenance at
Siemens.com.
