WEBVTT
Language: en-US

1
00:00:00.800 --> 00:00:06.320
<v Stewart McVinnie>What kind of comes back to that trust
piece is this engineer, Trust Sensei.

2
00:00:07.050 --> 00:00:10.529
<v Stewart McVinnie>He knows that if Sensor see there's a
problem, there's a problem to find.

3
00:00:10.930 --> 00:00:17.190
<v Stewart McVinnie>And he proceeded to kind of climb all over
this, this motor roll gearbox assembly,

4
00:00:17.649 --> 00:00:21.889
<v Stewart McVinnie>and right down to the depths of it, where
he found the mounting bolts of the gearbox

5
00:00:21.889 --> 00:00:23.510
<v Stewart McVinnie>to be loose, 3 out of 4 of them.

6
00:00:24.399 --> 00:00:30.500
<v Stewart McVinnie>And if we didn't have that trust, you'd
give up and say, oh, it must be a false case

7
00:00:30.500 --> 00:00:33.759
<v Stewart McVinnie>from Senseii, the coupling's fine and the
mode is fine.

8
00:00:34.200 --> 00:00:38.860
<v Stewart McVinnie>But having that trust, and the drive to
keep looking until we find the root cause,

9
00:00:39.400 --> 00:00:45.599
<v Stewart McVinnie>has led us to tighten up 3 bolts and and
lead to a 12 hour downtime avoided, which,

10
00:00:45.759 --> 00:00:51.400
<v Stewart McVinnie>you know, 12 hours in in any industry, in
any Um, plant is, is fantastic.

11
00:00:51.759 --> 00:00:56.889
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens, and now your host, Nel

12
00:00:56.889 --> 00:00:57.439
<v Speaker 2>Sullivan.

13
00:00:59.400 --> 00:01:04.739
<v Niall Sullivan>Hello, um, and welcome to this very
special episode of the trend detection podcast.

14
00:01:05.120 --> 00:01:11.199
<v Niall Sullivan>Um, I'm joined by Stu McVinnie, um, from
Bluescope New Zealand, and Bluescope Steel

15
00:01:11.199 --> 00:01:12.519
<v Niall Sullivan>New Zealand, in fact.

16
00:01:13.000 --> 00:01:17.639
<v Niall Sullivan>Um, and a lot of regular listeners will
know we've, we've spoken a lot to Bluescope

17
00:01:17.639 --> 00:01:18.010
<v Niall Sullivan>Steel.

18
00:01:18.150 --> 00:01:23.839
<v Niall Sullivan>I'm a very fantastic customer of Siemens
and of the Sensai product, and we've spoken

19
00:01:23.839 --> 00:01:25.879
<v Niall Sullivan>to Colin Robertson and Chris Watson.

20
00:01:26.220 --> 00:01:29.139
<v Niall Sullivan>Um, very recently as part of our live
event, um, you can check that out on the

21
00:01:29.139 --> 00:01:30.430
<v Niall Sullivan>podcast now.

22
00:01:30.790 --> 00:01:35.029
<v Niall Sullivan>Um, but today we're talking about
BlueScope New Zealand's very unique part of the

23
00:01:35.029 --> 00:01:39.790
<v Niall Sullivan>story as well, and all of the success, um,
they've achieved so far and, and will

24
00:01:39.790 --> 00:01:41.470
<v Niall Sullivan>achieve into the future as well,
hopefully.

25
00:01:41.709 --> 00:01:46.110
<v Niall Sullivan>Um, we're gonna focus on a particular
success case and dive, deep dive into that.

26
00:01:46.309 --> 00:01:50.849
<v Niall Sullivan>Um, again, we did a similar one with Chris
Swanson of Bluescope as well recently,

27
00:01:51.029 --> 00:01:51.470
<v Niall Sullivan>um.

28
00:01:52.000 --> 00:01:56.650
<v Niall Sullivan>But before we go into that, um, Stu, it'd
be great to get, um, a bit of, you know,

29
00:01:56.930 --> 00:02:01.209
<v Niall Sullivan>an idea of your background, um, and of
Bluescope New Zealand as well and where that

30
00:02:01.209 --> 00:02:03.430
<v Niall Sullivan>fits into the, the overall picture of
Bluescope.

31
00:02:03.569 --> 00:02:04.809
<v Niall Sullivan>Um, so over to you.

32
00:02:06.059 --> 00:02:06.410
<v Stewart McVinnie>Yeah, cool.

33
00:02:06.489 --> 00:02:10.449
<v Stewart McVinnie>Thanks, Noel and good to be here and it is
pretty cool to be able to share our our

34
00:02:10.449 --> 00:02:16.050
<v Stewart McVinnie>journey and focus it around one of our
recent success cases because it is very

35
00:02:16.050 --> 00:02:17.729
<v Stewart McVinnie>successful and it's great to be able to
share that.

36
00:02:18.630 --> 00:02:20.649
<v Stewart McVinnie>Um, just to kind of set the scene.

37
00:02:20.990 --> 00:02:25.750
<v Stewart McVinnie>I I'm Stewart McVinn, the digital
transformation manager here at New Zealand Steel

38
00:02:25.750 --> 00:02:28.029
<v Stewart McVinnie>and we're a relatively new team.

39
00:02:28.270 --> 00:02:33.229
<v Stewart McVinnie>Digital transformation has been around,
yeah, just gone 3 years now, um, primarily

40
00:02:33.229 --> 00:02:37.970
<v Stewart McVinnie>focused around what we call the asset
intelligence, of which size is a really big

41
00:02:37.970 --> 00:02:43.589
<v Stewart McVinnie>part of trying to better and get the most
out of our manufacturing assets.

42
00:02:45.270 --> 00:02:50.110
<v Stewart McVinnie>Um, to set the scene a little bit on us as
New Zealand Steel, um, you mentioned

43
00:02:50.110 --> 00:02:53.869
<v Stewart McVinnie>already the term unique, and we are very
unique down here at the bottom of the

44
00:02:53.869 --> 00:02:54.369
<v Stewart McVinnie>world.

45
00:02:55.080 --> 00:02:57.210
<v Stewart McVinnie>Um, we are New Zealand's only steelmaker.

46
00:02:57.750 --> 00:03:00.070
<v Stewart McVinnie>And what makes us unique is our process.

47
00:03:00.389 --> 00:03:04.149
<v Stewart McVinnie>So we're a fully integrated steel
business, which means we do everything from the

48
00:03:04.149 --> 00:03:06.570
<v Stewart McVinnie>raw materials all the way through to
finished goods.

49
00:03:06.990 --> 00:03:10.789
<v Stewart McVinnie>Um, but our raw materials are iron sands
of our West Coast beaches.

50
00:03:11.630 --> 00:03:16.509
<v Stewart McVinnie>So we have a unique process where we can
take, we mine these iron sands, and then

51
00:03:16.509 --> 00:03:20.990
<v Stewart McVinnie>process them through our iron making,
steel making, and rolling mills, uh, to supply

52
00:03:20.990 --> 00:03:23.509
<v Stewart McVinnie>a large majority of New Zealand's domestic
steel market.

53
00:03:24.539 --> 00:03:27.210
<v Stewart McVinnie>Um, so been around since 1965.

54
00:03:27.770 --> 00:03:31.529
<v Stewart McVinnie>So we're pretty well set in this industry
within New Zealand.

55
00:03:32.149 --> 00:03:38.330
<v Stewart McVinnie>I mean we're a pretty loyal, um, bunch of
customers with a pretty well-known product

56
00:03:38.330 --> 00:03:39.449
<v Stewart McVinnie>base across the country.

57
00:03:40.020 --> 00:03:44.250
<v Stewart McVinnie>Um, and yes, we are a subsidiary of Blue
Scope Steel, so some of our colleagues that

58
00:03:44.250 --> 00:03:46.570
<v Stewart McVinnie>you'll have spoken to a part of the
Australian business.

59
00:03:47.270 --> 00:03:50.460
<v Stewart McVinnie>Um, so yeah we are New Zealand Steel under
that Blue Scope Steel umbrella.

60
00:03:52.630 --> 00:03:53.229
<v Niall Sullivan>Fantastic.

61
00:03:53.389 --> 00:03:57.669
<v Niall Sullivan>And I, I guess, um, before we go deep dive
into the success case, Stuart, it, it'd

62
00:03:57.669 --> 00:04:01.869
<v Niall Sullivan>be interesting to know the story behind
the implementation of Sensai.

63
00:04:01.949 --> 00:04:05.899
<v Niall Sullivan>Of course, there's a, a global rollout,
um, of Bluescope Steel, but very

64
00:04:05.899 --> 00:04:09.529
<v Niall Sullivan>specifically to New Zealand, you know, so
what, what led to the implementation?

65
00:04:10.899 --> 00:04:15.270
<v Stewart McVinnie>Yeah, well, you mentioned that global
rollout, and it was a really good use case.

66
00:04:15.509 --> 00:04:20.790
<v Stewart McVinnie>Um, so they kind of set the scene about 6
to 12 months ahead of, ahead of us kicking

67
00:04:20.790 --> 00:04:21.429
<v Stewart McVinnie>things off.

68
00:04:21.670 --> 00:04:25.350
<v Stewart McVinnie>But it was enough for our management kind
of team to get a bit of a feel for what

69
00:04:25.350 --> 00:04:30.910
<v Stewart McVinnie>the opportunity was, to see some of the
potential benefits, and then draw some of

70
00:04:30.910 --> 00:04:32.489
<v Stewart McVinnie>those similarities.

71
00:04:32.709 --> 00:04:37.489
<v Stewart McVinnie>We also have aging equipment, um, some of
our continuous improvement.

72
00:04:37.809 --> 00:04:42.540
<v Stewart McVinnie>Sort of methodologies we're kind of
flatlining and some of that, um, that growth.

73
00:04:44.160 --> 00:04:48.279
<v Stewart McVinnie>We're all faced with the changing
workplace, and we're always looking for that

74
00:04:48.279 --> 00:04:51.619
<v Stewart McVinnie>modern approach for a step change in our
asset performance.

75
00:04:52.230 --> 00:04:56.760
<v Stewart McVinnie>And so that's where the decision came to
create the digital transformation team, and

76
00:04:56.760 --> 00:05:00.700
<v Stewart McVinnie>to then adopt asset intelligence, which is
a big part of.

77
00:05:03.239 --> 00:05:03.640
<v Niall Sullivan>I see.

78
00:05:03.760 --> 00:05:05.079
<v Niall Sullivan>So that's interesting actually.

79
00:05:05.200 --> 00:05:10.100
<v Niall Sullivan>So you, you formulated the team at that
point to, to, I guess, manage the rollout of

80
00:05:10.119 --> 00:05:14.100
<v Niall Sullivan>that particular project or other digital
transformation initiatives as well?

81
00:05:14.399 --> 00:05:18.299
<v Niall Sullivan>Was, was the predictive maintenance one
was the trigger for it, let's say.

82
00:05:19.220 --> 00:05:24.859
<v Stewart McVinnie>Yeah, well, we, we created the digital
transformation team with a suite of modules,

83
00:05:25.279 --> 00:05:26.440
<v Stewart McVinnie>um, envisaged to happen.

84
00:05:26.519 --> 00:05:27.380
<v Stewart McVinnie>We had some.

85
00:05:27.790 --> 00:05:31.790
<v Stewart McVinnie>Data work, we had some predictive
maintenance, and we're considering some things

86
00:05:31.790 --> 00:05:33.910
<v Stewart McVinnie>like digital twins and mobile workers.

87
00:05:34.230 --> 00:05:38.750
<v Stewart McVinnie>Um, so there was a suite of modules that,
um, our asset intelligence program of

88
00:05:38.750 --> 00:05:44.269
<v Stewart McVinnie>work, um, was envisaging working through,
um, be a big part of that and one of the

89
00:05:44.269 --> 00:05:46.809
<v Stewart McVinnie>early things that got off the ground was
the predictive working with Sensi.

90
00:05:49.709 --> 00:05:50.100
<v Niall Sullivan>Fantastic.

91
00:05:50.130 --> 00:05:53.190
<v Niall Sullivan>And, and how long have you been using the,
the system now?

92
00:05:53.429 --> 00:05:54.929
<v Niall Sullivan>I guess just for context for the audience.

93
00:05:55.790 --> 00:05:57.290
<v Stewart McVinnie>Yeah, we've.

94
00:05:58.140 --> 00:06:03.420
<v Stewart McVinnie>We've been working with Sensei for
probably the best part of 2 years now, um, but

95
00:06:03.420 --> 00:06:07.940
<v Stewart McVinnie>really only been using the tool in anger,
um, pretty much since Christmas.

96
00:06:08.450 --> 00:06:14.380
<v Stewart McVinnie>Um, so that's about about 67 months now,
where we've had since I really providing

97
00:06:14.380 --> 00:06:18.359
<v Stewart McVinnie>value, implemented in production, and
being used by our people.

98
00:06:19.690 --> 00:06:25.130
<v Niall Sullivan>And I, and I guess, you know, seeing a
success relatively soon is very positive,

99
00:06:25.230 --> 00:06:25.369
<v Niall Sullivan>right?

100
00:06:25.450 --> 00:06:27.670
<v Niall Sullivan>So the success we're talking about today,
um.

101
00:06:28.459 --> 00:06:32.380
<v Niall Sullivan>Yeah, you know, it's obviously a a great
sign of the system's success and your

102
00:06:32.380 --> 00:06:33.040
<v Niall Sullivan>success as well.

103
00:06:33.950 --> 00:06:38.799
<v Stewart McVinnie>Oh, the, the early success has been
fantastic for building a business case, right?

104
00:06:39.230 --> 00:06:44.790
<v Stewart McVinnie>Um, to date, we've only got about 300
assets on board and success for us probably is

105
00:06:44.790 --> 00:06:45.709
<v Stewart McVinnie>around 5000.

106
00:06:46.489 --> 00:06:53.489
<v Stewart McVinnie>So, to be, to have had 4 wins in 6 months
with 300 assets, I think it's it's an

107
00:06:53.489 --> 00:06:58.089
<v Stewart McVinnie>absolutely fantastic start, and a real
good demonstration of what the potential of

108
00:06:58.089 --> 00:07:02.329
<v Stewart McVinnie>this is, when we hit that sort of target
rollout of 3000 to 5000 assets.

109
00:07:03.940 --> 00:07:08.109
<v Niall Sullivan>And, yeah, and clearly, like I said it's
lots of room to grow there as well.

110
00:07:08.179 --> 00:07:09.820
<v Niall Sullivan>So that's a really exciting part as well.

111
00:07:10.660 --> 00:07:13.609
<v Niall Sullivan>Success already, but, you know, still lots
of potential, right?

112
00:07:15.230 --> 00:07:21.989
<v Stewart McVinnie>Uh, we, we, when you look at the 4 success
cases for 300 assets, you do the math,

113
00:07:22.000 --> 00:07:24.709
<v Stewart McVinnie>they, they're going to keep flowing and as
we roll more and more out.

114
00:07:26.799 --> 00:07:31.279
<v Niall Sullivan>And I guess, yeah, so let's, um, deep dive
into the, the success we're, we're

115
00:07:31.279 --> 00:07:31.959
<v Niall Sullivan>talking about today.

116
00:07:32.059 --> 00:07:38.799
<v Niall Sullivan>So, it was actually, um, so Sensai
actually detected, um, elevated vibration in the

117
00:07:38.799 --> 00:07:40.880
<v Niall Sullivan>gearbox, I believe, um.

118
00:07:41.899 --> 00:07:48.779
<v Niall Sullivan>So, as this is an example of early
detection capability, um, how has

119
00:07:48.779 --> 00:07:53.359
<v Niall Sullivan>it changed your maintenance practices sort
of fundamentally as a, as an example?

120
00:07:54.649 --> 00:08:00.049
<v Stewart McVinnie>Maintenance practices wise, we're still
pretty early in that journey, so 300 assets

121
00:08:00.369 --> 00:08:03.459
<v Stewart McVinnie>across our site is not a lot, so we've
only just scratched the surface.

122
00:08:04.350 --> 00:08:08.670
<v Stewart McVinnie>So we haven't seen a big shift in those
maintenance practices, but we're starting to

123
00:08:08.670 --> 00:08:13.510
<v Stewart McVinnie>see, um, some change small changes in the
in the people working in those spaces.

124
00:08:13.950 --> 00:08:19.350
<v Stewart McVinnie>Um, moving from that uh reactive to
proactive has been something we've observed

125
00:08:19.350 --> 00:08:24.790
<v Stewart McVinnie>already with just a few assets where
people are starting to spend less time in the

126
00:08:24.790 --> 00:08:27.670
<v Stewart McVinnie>mornings looking at trends and those
assets onboarded.

127
00:08:27.970 --> 00:08:30.730
<v Stewart McVinnie>And really just sit back and wait for so
to bring up a case.

128
00:08:31.130 --> 00:08:34.130
<v Stewart McVinnie>So that's freed up some more time in the
morning where they'd normally be looking at

129
00:08:34.130 --> 00:08:34.739
<v Stewart McVinnie>assets.

130
00:08:35.010 --> 00:08:36.609
<v Stewart McVinnie>They're now just reviewing cases.

131
00:08:37.169 --> 00:08:38.669
<v Stewart McVinnie>So that's been a bit of a shift there.

132
00:08:39.390 --> 00:08:43.630
<v Stewart McVinnie>And the other small one around the kind of
maintenance side of things is we have

133
00:08:43.630 --> 00:08:47.039
<v Stewart McVinnie>managed to eliminate some vibration
analysis inspections.

134
00:08:47.669 --> 00:08:52.109
<v Stewart McVinnie>So we we've got since I monitoring an
asset that a person was going out once a month

135
00:08:52.109 --> 00:08:54.390
<v Stewart McVinnie>to go and see how it's performing.

136
00:08:54.969 --> 00:08:59.830
<v Stewart McVinnie>Uh, we've now only a small amount,
probably 90 hours worth of work, something like

137
00:08:59.830 --> 00:09:04.390
<v Stewart McVinnie>that, but we have managed to take a little
bit of that work as we've onboarded

138
00:09:04.390 --> 00:09:06.309
<v Stewart McVinnie>assets onto into sense size.

139
00:09:06.390 --> 00:09:12.049
<v Stewart McVinnie>So just Early indications of what some of
these opportunities are to address some of

140
00:09:12.049 --> 00:09:13.659
<v Stewart McVinnie>that maintenance planning.

141
00:09:15.270 --> 00:09:19.219
<v Niall Sullivan>Yeah, and then that's really good examples
of, you know, like you said, even in sort

142
00:09:19.219 --> 00:09:22.349
<v Niall Sullivan>of very early stages, sort of embracing
the technology and trust, because, you know,

143
00:09:22.469 --> 00:09:26.270
<v Niall Sullivan>trust to the system, you know, is key to
sort of adoption and rollout.

144
00:09:26.460 --> 00:09:30.349
<v Niall Sullivan>Um, was there sort of any particular
initiatives you did with the maintenance teams

145
00:09:30.349 --> 00:09:34.950
<v Niall Sullivan>to sort of encourage them to, to look at
Sensai and, and use the information that's

146
00:09:34.950 --> 00:09:36.150
<v Niall Sullivan>available through Sensai?

147
00:09:36.880 --> 00:09:38.909
<v Stewart McVinnie>Oh, you, you nailed it with trust.

148
00:09:39.070 --> 00:09:43.590
<v Stewart McVinnie>Trust was everything because We only had
one chance to bring a lot of these people

149
00:09:43.590 --> 00:09:49.320
<v Stewart McVinnie>on board, and If you lose someone's trust
early on, it's really hard to get it back,

150
00:09:49.419 --> 00:09:52.739
<v Stewart McVinnie>and then it's going to be really tough
sell to get, since I'm moving forward from

151
00:09:52.739 --> 00:09:53.059
<v Stewart McVinnie>there.

152
00:09:53.619 --> 00:09:57.880
<v Stewart McVinnie>So we actually had a pretty robust pilot
to start things off.

153
00:09:58.309 --> 00:10:02.059
<v Stewart McVinnie>And the idea with that pilot was to get
all the learnings, to get everything

154
00:10:02.059 --> 00:10:08.500
<v Stewart McVinnie>polished up and tidied, to fix all the
bugs and issues, so that when we went to

155
00:10:08.500 --> 00:10:12.539
<v Stewart McVinnie>production and rolled out, people had that
trust because they weren't getting a

156
00:10:12.539 --> 00:10:14.520
<v Stewart McVinnie>product that wasn't fit for purpose.

157
00:10:15.330 --> 00:10:19.859
<v Stewart McVinnie>Um, it also gave us that credibility and
the confidence to go out with our sales

158
00:10:19.859 --> 00:10:24.260
<v Stewart McVinnie>pitch to our customers, our internal
customers and say, hey, we've got a fantastic

159
00:10:24.260 --> 00:10:29.020
<v Stewart McVinnie>tool that works, rather than saying, we
think this will work, but if it gets

160
00:10:29.020 --> 00:10:29.940
<v Stewart McVinnie>annoying, let us know.

161
00:10:30.059 --> 00:10:34.859
<v Stewart McVinnie>So, we really spent a lot of effort and
time upfront to make sure that we got it all

162
00:10:34.859 --> 00:10:37.099
<v Stewart McVinnie>right, and it would work, we rolled it
out.

163
00:10:37.419 --> 00:10:39.299
<v Stewart McVinnie>And then the trust just came from using
it.

164
00:10:39.859 --> 00:10:44.739
<v Stewart McVinnie>Um, people reviewing cases, monitoring
their assets, start building into their

165
00:10:44.739 --> 00:10:50.219
<v Stewart McVinnie>habits and routine, um, and that trust
slowly builds and kind of ironically.

166
00:10:51.010 --> 00:10:56.059
<v Stewart McVinnie>Those areas that had the most cases,
started to build trust in it quicker, because

167
00:10:56.059 --> 00:10:58.840
<v Stewart McVinnie>they saw those opportunities and benefits
coming through more often.

168
00:10:59.460 --> 00:11:03.580
<v Stewart McVinnie>Um, the trouble we've seen with some areas
is they might get one case every week or

169
00:11:03.580 --> 00:11:07.979
<v Stewart McVinnie>two, because they've only got a couple of
assets on boarded, in which case, you're

170
00:11:07.979 --> 00:11:12.500
<v Stewart McVinnie>kind of losing interest in between,
whereas those that are getting several a week,

171
00:11:12.700 --> 00:11:16.619
<v Stewart McVinnie>um, keep their finger on the pulse and
really get to demons see the demonstration of

172
00:11:16.619 --> 00:11:17.979
<v Stewart McVinnie>Sensei firsthand, so.

173
00:11:18.900 --> 00:11:23.250
<v Stewart McVinnie>That, that has been, it's been a really
important part of our roll out and really

174
00:11:23.250 --> 00:11:23.669
<v Stewart McVinnie>successful.

175
00:11:24.489 --> 00:11:28.849
<v Stewart McVinnie>And the other one is just around, around
our digital transformation team.

176
00:11:29.510 --> 00:11:35.190
<v Stewart McVinnie>Um, so, we've actually, a lot of our teams
come from internal within the business.

177
00:11:35.570 --> 00:11:39.570
<v Stewart McVinnie>So that brings some credibility, some
relationships and some experience in previous

178
00:11:39.570 --> 00:11:39.890
<v Stewart McVinnie>roles.

179
00:11:39.969 --> 00:11:44.770
<v Stewart McVinnie>So, when we say something works and are
advocating for it, it just comes with the

180
00:11:44.770 --> 00:11:48.479
<v Stewart McVinnie>extra layer of credibility to kind of get
us on the front foot for some of these

181
00:11:48.479 --> 00:11:49.070
<v Stewart McVinnie>customers.

182
00:11:50.219 --> 00:11:56.710
<v Stewart McVinnie>But, but all in all, Building that trust
is probably Been a little bit easier than

183
00:11:56.710 --> 00:12:02.440
<v Stewart McVinnie>expected, but, likely because of the work
we did up front, so we didn't have to, um,

184
00:12:02.590 --> 00:12:06.369
<v Stewart McVinnie>kind of explain many problems because they
didn't crop up because we'd we'd solved

185
00:12:06.369 --> 00:12:07.190
<v Stewart McVinnie>it in the pilots.

186
00:12:08.809 --> 00:12:12.159
<v Niall Sullivan>Yeah, and that, yeah, that, that's really
interesting as well, because I guess

187
00:12:12.169 --> 00:12:15.159
<v Niall Sullivan>sometimes there's a keenness, and maybe
it's, yeah, it's not necessarily a bad

188
00:12:15.159 --> 00:12:19.409
<v Niall Sullivan>thing, and enthusiasm start big and, and
go big as soon as possible.

189
00:12:19.489 --> 00:12:23.210
<v Niall Sullivan>But, yeah, what you're saying is it's use
the pilot as a learning, as a learning

190
00:12:23.210 --> 00:12:23.559
<v Niall Sullivan>curve.

191
00:12:23.770 --> 00:12:27.570
<v Niall Sullivan>Pick up the learnings, introduce insights
to the teams, and then see hopefully some

192
00:12:27.570 --> 00:12:31.409
<v Niall Sullivan>early successes and cases and go from
there and just build the momentum.

193
00:12:31.539 --> 00:12:32.489
<v Niall Sullivan>Maybe that's another good word.

194
00:12:32.559 --> 00:12:36.010
<v Niall Sullivan>I don't want to put words into your mouth,
of course, but momentums often comes up

195
00:12:36.010 --> 00:12:37.549
<v Niall Sullivan>in my conversations as well.

196
00:12:38.270 --> 00:12:42.549
<v Stewart McVinnie>Yeah I don't know if I'd use momentum at
this stage, but the building up was, was

197
00:12:42.549 --> 00:12:43.969
<v Stewart McVinnie>really, really important.

198
00:12:44.659 --> 00:12:48.039
<v Stewart McVinnie>And and we're very well supported from our
management team here.

199
00:12:48.739 --> 00:12:52.559
<v Stewart McVinnie>Very early on, we identified the pilot is
important.

200
00:12:53.099 --> 00:12:56.979
<v Stewart McVinnie>We identified that getting our data
foundation is important, and we identified some

201
00:12:56.979 --> 00:13:00.260
<v Stewart McVinnie>of the automation things that we wanted to
achieve as important.

202
00:13:00.530 --> 00:13:04.500
<v Stewart McVinnie>But that meant effort upfront to deliver
quickly later on.

203
00:13:04.820 --> 00:13:10.179
<v Stewart McVinnie>And when we had that real robust support
from our management team saying, Yes, we

204
00:13:10.179 --> 00:13:12.780
<v Stewart McVinnie>beg you to do that because we know it'll
be worth it in the long run.

205
00:13:13.140 --> 00:13:17.979
<v Stewart McVinnie>And and the prime example was The reason
earlier on I said we started an anger at

206
00:13:17.979 --> 00:13:24.500
<v Stewart McVinnie>Christmas, is we had been playing around
and deploying up probably for about 6

207
00:13:24.500 --> 00:13:27.099
<v Stewart McVinnie>months before Christmas.

208
00:13:27.969 --> 00:13:29.359
<v Stewart McVinnie>And it wasn't working.

209
00:13:29.419 --> 00:13:31.880
<v Stewart McVinnie>And we actually stopped, deleted
everything.

210
00:13:32.830 --> 00:13:36.469
<v Stewart McVinnie>reassessed our philosophy, and reloaded
everything in March.

211
00:13:36.590 --> 00:13:41.229
<v Stewart McVinnie>So we've effectively stopped for three
months, post-Cristmas, deleted all started

212
00:13:41.229 --> 00:13:42.750
<v Stewart McVinnie>again, and I've never looked back.

213
00:13:42.830 --> 00:13:44.750
<v Stewart McVinnie>It's been really, really fantastic.

214
00:13:44.869 --> 00:13:48.169
<v Stewart McVinnie>So, that's an example of how we built into
it.

215
00:13:48.510 --> 00:13:54.090
<v Stewart McVinnie>We've gone in stages, we've learned, and
we've had that support from our business to

216
00:13:54.469 --> 00:14:00.440
<v Stewart McVinnie>stop and fix it, when we found an issue,
not Always looking for the fastest, biggest

217
00:14:00.440 --> 00:14:03.140
<v Stewart McVinnie>deployment, it was let's get it right for
the long term success.

218
00:14:04.690 --> 00:14:06.010
<v Niall Sullivan>And that, and that's fascinating as well.

219
00:14:06.070 --> 00:14:09.690
<v Niall Sullivan>I mean, that's, that's such a brave
decision because like I said, a lot of, you

220
00:14:09.690 --> 00:14:11.609
<v Niall Sullivan>know, people would just sort of try and
continue.

221
00:14:11.690 --> 00:14:15.650
<v Niall Sullivan>It'll improve if, if we keep going and
keep going, it'll improve, but you just

222
00:14:15.650 --> 00:14:20.169
<v Niall Sullivan>decided to stop, scrap it, and almost
start from scratch, and you, you're seeing the

223
00:14:20.169 --> 00:14:23.429
<v Niall Sullivan>rewards now as well, which is just
fantastic to hear.

224
00:14:24.359 --> 00:14:27.640
<v Stewart McVinnie>Yeah, it was Wasn't a comfortable decision
to make.

225
00:14:27.979 --> 00:14:32.559
<v Stewart McVinnie>But looking back, totally the right
decision to make, would make it again any day.

226
00:14:34.260 --> 00:14:35.539
<v Niall Sullivan>And I mean, look where we are.

227
00:14:35.609 --> 00:14:39.219
<v Niall Sullivan>So you mentioned multiple successes, you
know, with, you know, with, um, you know,

228
00:14:39.340 --> 00:14:40.460
<v Niall Sullivan>300 assets, you said.

229
00:14:40.539 --> 00:14:41.739
<v Niall Sullivan>So, you know, amazing success.

230
00:14:41.780 --> 00:14:47.260
<v Niall Sullivan>We, the one we're focusing on today
actually is, it mentions 12 hours of, um,

231
00:14:47.460 --> 00:14:52.059
<v Niall Sullivan>avoided downtime, which we know,
especially in, in your industry is very significant

232
00:14:52.059 --> 00:14:52.659
<v Niall Sullivan>for a number of reasons.

233
00:14:52.739 --> 00:14:57.440
<v Niall Sullivan>I mean maybe you could sort of outline
that a bit, Stu, um, first of all, and then

234
00:14:57.619 --> 00:15:01.020
<v Niall Sullivan>maybe we could quantify the, you know, the
actual financial impact of that.

235
00:15:01.070 --> 00:15:02.200
<v Niall Sullivan>What does that mean in actual?

236
00:15:02.750 --> 00:15:05.919
<v Niall Sullivan>Not maybe not specific card numbers, but,
you know, the financial impact generally.

237
00:15:07.250 --> 00:15:09.400
<v Stewart McVinnie>Yeah, well, on, on the use case itself.

238
00:15:10.530 --> 00:15:12.539
<v Stewart McVinnie>1 12 hours is significant for us.

239
00:15:12.700 --> 00:15:16.580
<v Stewart McVinnie>That's that's half a day's operation,
especially on a plant that's close to the

240
00:15:16.580 --> 00:15:17.309
<v Stewart McVinnie>bottleneck.

241
00:15:17.619 --> 00:15:19.460
<v Stewart McVinnie>It's, that's a really, really good one.

242
00:15:20.179 --> 00:15:25.590
<v Stewart McVinnie>But it was, it was an absolute fantastic
case where, the case was generated in the

243
00:15:25.590 --> 00:15:31.309
<v Stewart McVinnie>morning and the engineer of that plant
went out to investigate the gearbox in

244
00:15:31.309 --> 00:15:36.039
<v Stewart McVinnie>question and You walk out there with some
preconceived sort of ideas, right?

245
00:15:36.080 --> 00:15:40.419
<v Stewart McVinnie>You walk out thinking it's going to be a
loose coupling, or it's going to be motor,

246
00:15:40.760 --> 00:15:42.880
<v Stewart McVinnie>um cowling issues or something like that.

247
00:15:43.000 --> 00:15:45.750
<v Stewart McVinnie>So they've gone out and they've rattled
the cowling, they've looked at the coupling,

248
00:15:45.799 --> 00:15:49.479
<v Stewart McVinnie>they've looked for backlash in the
gearbox, haven't actually found anything.

249
00:15:50.309 --> 00:15:57.270
<v Stewart McVinnie>Uh, but what kind of comes back to that
trust piece is this engineer trusts Sensai.

250
00:15:57.809 --> 00:16:01.289
<v Stewart McVinnie>He knows that if Sensai says there's a
problem, there's a problem to find.

251
00:16:01.650 --> 00:16:07.909
<v Stewart McVinnie>And he proceeded to kind of climb all over
this, this motor roll gearbox assembly

252
00:16:08.349 --> 00:16:12.609
<v Stewart McVinnie>and right down to the depths of it, where
he found the mounting bolts of the gearbox

253
00:16:12.609 --> 00:16:14.130
<v Stewart McVinnie>to be loose, 3 out of 4 of them.

254
00:16:15.119 --> 00:16:21.229
<v Stewart McVinnie>And if we didn't have that trust, you'd
give up and say, oh, it must be a false case

255
00:16:21.229 --> 00:16:24.469
<v Stewart McVinnie>from Sensei, the coupling's fine and the
mode is fine.

256
00:16:24.929 --> 00:16:30.250
<v Stewart McVinnie>But having that trust and the drive to
keep looking until we find the root cause has

257
00:16:30.250 --> 00:16:36.559
<v Stewart McVinnie>led us to tighten up 3 bolts and and lead
to a 12 hour downtime avoided, which, you

258
00:16:36.559 --> 00:16:39.479
<v Stewart McVinnie>know, 12 hours in in any industry in any.

259
00:16:40.109 --> 00:16:46.270
<v Stewart McVinnie>Um, plant is fantastic and It's not just
the downtime avoided, it's the fact that

260
00:16:47.640 --> 00:16:52.440
<v Stewart McVinnie>If those bolts had failed, and we had that
catastrophic failure, you'd also lose the

261
00:16:52.440 --> 00:16:53.880
<v Stewart McVinnie>role of the gearbox and the motor.

262
00:16:54.359 --> 00:16:58.460
<v Stewart McVinnie>Um, so it's time, and it's that asset cost
replacement as well.

263
00:17:00.010 --> 00:17:03.010
<v Stewart McVinnie>Yeah, but in terms of, sorry, no,

264
00:17:03.070 --> 00:17:04.489
<v Niall Sullivan>no, no, you guys sorry

265
00:17:05.209 --> 00:17:08.949
<v Stewart McVinnie>I was gonna say but in terms of trying to
quantify 12 hours.

266
00:17:09.769 --> 00:17:15.548
<v Stewart McVinnie>Um, the, the important thing to remember
is we want to benchmark and comparable KPI

267
00:17:15.548 --> 00:17:17.409
<v Stewart McVinnie>for measuring the performance of Sensei.

268
00:17:17.938 --> 00:17:23.698
<v Stewart McVinnie>And the complication you get is when you
try and convert a KPI of ours to a

269
00:17:23.698 --> 00:17:24.568
<v Stewart McVinnie>financial one.

270
00:17:25.178 --> 00:17:30.380
<v Stewart McVinnie>Because, Your your financial value or your
value of an hour varies so much, it could

271
00:17:30.380 --> 00:17:35.130
<v Stewart McVinnie>vary by plant, it could vary by the
market, like steel is a commodity product, so,

272
00:17:35.449 --> 00:17:39.540
<v Stewart McVinnie>at the moment we're quite low in the cycle
with steel's not worth much, um, and

273
00:17:39.819 --> 00:17:42.339
<v Stewart McVinnie>other times the cycle steel can be worth
an absolute fortune.

274
00:17:42.459 --> 00:17:47.000
<v Stewart McVinnie>So, depending on where you are in the
cycle, an hour can be worth quite a quite a

275
00:17:47.189 --> 00:17:48.199
<v Stewart McVinnie>quite a bit different.

276
00:17:48.579 --> 00:17:52.420
<v Stewart McVinnie>So an hour today is not what an hour in a
year or a month is.

277
00:17:52.849 --> 00:17:57.650
<v Stewart McVinnie>So it's, you got to be careful trying to
compare these sort of benefits on dollar

278
00:17:57.650 --> 00:18:02.550
<v Stewart McVinnie>values, because you're not really
comparing like for like at times.

279
00:18:03.160 --> 00:18:06.229
<v Stewart McVinnie>Hence why we primarily look for hours, um.

280
00:18:06.880 --> 00:18:08.719
<v Stewart McVinnie>And it's not just ours either, right?

281
00:18:08.800 --> 00:18:13.280
<v Stewart McVinnie>You've got Um, if you've got yield
improvements that come from Sensei, you could be

282
00:18:13.280 --> 00:18:18.060
<v Stewart McVinnie>talking tons, uh, we could be talking some
defects or downgrade, which is a quality

283
00:18:18.790 --> 00:18:19.199
<v Stewart McVinnie>savings.

284
00:18:19.280 --> 00:18:23.760
<v Stewart McVinnie>So there's a number of different KPIs that
can be used to measure the benefits of

285
00:18:23.760 --> 00:18:29.359
<v Stewart McVinnie>Sensei, um, but to To give you a bit of a
steer on where that value could sort of

286
00:18:29.359 --> 00:18:35.520
<v Stewart McVinnie>sit, well, if it's, if you're a high idle
plant, um, not fully utilized, 12 hours of

287
00:18:35.520 --> 00:18:39.920
<v Stewart McVinnie>downtime, might not be worth anything,
because you've got that spare capacity to

288
00:18:39.920 --> 00:18:41.660
<v Stewart McVinnie>make up the lost opportunity.

289
00:18:42.280 --> 00:18:46.560
<v Stewart McVinnie>Um, but if you are a bottleneck plant, 12
hours of downtime, it's in the tens of

290
00:18:46.560 --> 00:18:47.199
<v Stewart McVinnie>thousands.

291
00:18:47.839 --> 00:18:50.069
<v Stewart McVinnie>Um, in terms of opportunity, so.

292
00:18:51.030 --> 00:18:57.469
<v Stewart McVinnie>Since I really does, at the end of the
day, provide significant benefits across

293
00:18:57.469 --> 00:18:59.290
<v Stewart McVinnie>multiple KPIs within a business.

294
00:19:01.069 --> 00:19:05.030
<v Niall Sullivan>Yeah, and, and you've perfectly
articulated, Stu, what we talk about internally a

295
00:19:05.030 --> 00:19:08.310
<v Niall Sullivan>lot or, or with other customers as well,
because it is easy to focus on that, um,

296
00:19:08.469 --> 00:19:14.310
<v Niall Sullivan>downtime metric as the, the metric, but
you've just explained very well why, you

297
00:19:14.310 --> 00:19:18.469
<v Niall Sullivan>know, there's so many other benefits that
maybe people wouldn't even have thought

298
00:19:18.469 --> 00:19:19.229
<v Niall Sullivan>of, right?

299
00:19:19.469 --> 00:19:23.310
<v Niall Sullivan>But were the, were those other KPIs, were
they, those identified sort of early on,

300
00:19:23.430 --> 00:19:26.089
<v Niall Sullivan>you know, when you're just starting to
implement the technology, or do they become,

301
00:19:26.810 --> 00:19:30.089
<v Niall Sullivan>Obvious, you know, just become obvious as,
you know, the rollout began and more

302
00:19:30.089 --> 00:19:31.170
<v Niall Sullivan>assets were on boarded.

303
00:19:32.900 --> 00:19:38.109
<v Stewart McVinnie>As a business, we live and breathe those
sort of KPIs downtime avoided, quality

304
00:19:38.109 --> 00:19:40.329
<v Stewart McVinnie>loss, yield, defects.

305
00:19:40.949 --> 00:19:44.260
<v Stewart McVinnie>That's kind of our bread and butter, so
they're always front of mind, but for

306
00:19:44.260 --> 00:19:50.790
<v Stewart McVinnie>simplicity, since I was initially just,
um, justified on downtime avoided or hours,

307
00:19:51.510 --> 00:19:55.750
<v Stewart McVinnie>um, because that's such a big piece of the
pie anyway, that if we nail that we've

308
00:19:55.750 --> 00:20:00.270
<v Stewart McVinnie>more than justified the investment in
digital transformation and since I, um.

309
00:20:00.619 --> 00:20:02.839
<v Stewart McVinnie>But absolutely those other aspects.

310
00:20:03.890 --> 00:20:09.010
<v Stewart McVinnie>Have always been part of our mind and as
we start to get closer to that successful

311
00:20:09.010 --> 00:20:14.489
<v Stewart McVinnie>deployment to what we kind of 3 to 5000
assets, targeting downtime, then we can look

312
00:20:14.489 --> 00:20:17.189
<v Stewart McVinnie>to say alright, now, how can we target
quality loss?

313
00:20:17.209 --> 00:20:22.890
<v Stewart McVinnie>How can we target yield improvements, um,
and they're, they're kind of like add-ons

314
00:20:22.890 --> 00:20:26.390
<v Stewart McVinnie>and as we progress to further leverage
what SensI is providing us.

315
00:20:29.359 --> 00:20:33.199
<v Niall Sullivan>Uh, yeah, and I, it's interesting to say
sort of, you know, further leverage as well

316
00:20:33.199 --> 00:20:36.319
<v Niall Sullivan>because it, what I liked about this
success case as well, you mentioned it was all

317
00:20:36.319 --> 00:20:40.280
<v Niall Sullivan>around, you know, um, uh, the loose base
and bolts.

318
00:20:40.339 --> 00:20:44.839
<v Niall Sullivan>So it's like it's spotted, you know, quite
or potentially spotted a, um, uh, like a

319
00:20:44.839 --> 00:20:46.359
<v Niall Sullivan>hidden maintenance issues.

320
00:20:46.410 --> 00:20:50.479
<v Niall Sullivan>I mean, is there ever sort of examples of
that from Sensai generally, not, not with

321
00:20:50.479 --> 00:20:55.349
<v Niall Sullivan>this case, but other cases as well where
it's spotted unexpected maintenance issues,

322
00:20:55.359 --> 00:20:57.839
<v Niall Sullivan>which you may not have known about, right?

323
00:20:58.680 --> 00:21:04.229
<v Stewart McVinnie>Yeah, well, across Bluescope we share all
these success cases, and I'm aware that um

324
00:21:04.569 --> 00:21:08.489
<v Stewart McVinnie>one of the other sites had a cracked motor
base which they found.

325
00:21:08.650 --> 00:21:13.829
<v Stewart McVinnie>Once again, so hard to find because a
crack can be hairline, but enough to create

326
00:21:13.829 --> 00:21:15.079
<v Stewart McVinnie>vibration and misalignment.

327
00:21:15.170 --> 00:21:19.530
<v Stewart McVinnie>So those are the sort of things that we've
definitely seen elsewhere across across

328
00:21:19.530 --> 00:21:20.849
<v Stewart McVinnie>Bluescope, um.

329
00:21:21.689 --> 00:21:26.939
<v Stewart McVinnie>But what where it really helps is we put
routine PMs in place, right?

330
00:21:26.969 --> 00:21:30.689
<v Stewart McVinnie>So we might send someone out to inspect it
once a month, but human nature is you go

331
00:21:30.689 --> 00:21:33.329
<v Stewart McVinnie>out there every month, nothing changes.

332
00:21:33.810 --> 00:21:37.729
<v Stewart McVinnie>You look at the easy stuff, you give it a
wiggle, and you leave because there's

333
00:21:37.729 --> 00:21:39.709
<v Stewart McVinnie>nothing that's changed since last month.

334
00:21:40.250 --> 00:21:45.989
<v Stewart McVinnie>And, as you kind of get a bit complacent
with the same thing every month.

335
00:21:46.810 --> 00:21:50.280
<v Stewart McVinnie>You become less and less likely to look at
the little details to get down as an

336
00:21:50.280 --> 00:21:53.949
<v Stewart McVinnie>awkward place to access the bolts on the
gearbox to check them, so.

337
00:21:54.900 --> 00:22:01.099
<v Stewart McVinnie>What what Sensesize is doing is it's
providing the extra line of defense, um, to

338
00:22:01.099 --> 00:22:06.099
<v Stewart McVinnie>help us catch those minor details uh if
and when they arise.

339
00:22:07.729 --> 00:22:10.130
<v Niall Sullivan>Yeah, actually, extra line defense is an
interesting one.

340
00:22:10.609 --> 00:22:13.729
<v Niall Sullivan>so I always bring it back to another
customer I interviewed a few years ago who

341
00:22:13.729 --> 00:22:16.609
<v Niall Sullivan>described Sensai as like a, a tool in his
toolbox.

342
00:22:16.849 --> 00:22:19.969
<v Niall Sullivan>So, it's all, it's sort of thinking along
the same lines, I feel.

343
00:22:20.089 --> 00:22:22.250
<v Niall Sullivan>Different analogies, but along the same
sort of line.

344
00:22:23.599 --> 00:22:28.790
<v Stewart McVinnie>Yeah, it's it's actually a tool, um, it's
a tool to improve the performance and

345
00:22:29.010 --> 00:22:30.209
<v Stewart McVinnie>management of our assets.

346
00:22:30.979 --> 00:22:33.709
<v Stewart McVinnie>And it's, it's going to take.

347
00:22:34.680 --> 00:22:40.280
<v Stewart McVinnie>More trust, more evidence, more rollout to
start really ripping out our routine

348
00:22:40.280 --> 00:22:45.189
<v Stewart McVinnie>maintenance inspections and putting full
faith and inside, but that's got to be the

349
00:22:45.189 --> 00:22:49.319
<v Stewart McVinnie>long-term goal, right, the long-term
opportunity, um, and I think that'll be an

350
00:22:49.319 --> 00:22:54.479
<v Stewart McVinnie>incremental progress as we roll out, get
more cases, get more trust, make sure that

351
00:22:54.479 --> 00:22:59.430
<v Stewart McVinnie>we've got our configuration right because
If you don't configure Sensei right, it

352
00:22:59.430 --> 00:23:03.949
<v Stewart McVinnie>won't pick up the minor details, in which
case, Sensei's not working, and you've got

353
00:23:03.949 --> 00:23:04.349
<v Stewart McVinnie>rid of your

354
00:23:04.349 --> 00:23:05.969
<v Stewart McVinnie>PMs, you're not set up for success.

355
00:23:06.790 --> 00:23:10.849
<v Stewart McVinnie>Um, so if we make sure we get that
configuration right as well, trust it, prove it,

356
00:23:10.910 --> 00:23:15.349
<v Stewart McVinnie>then we can keep ripping out some of those
PMs and remove it from a last line of

357
00:23:15.349 --> 00:23:18.969
<v Stewart McVinnie>defense to your primary, um, tool of
choice.

358
00:23:20.660 --> 00:23:24.180
<v Niall Sullivan>And, and just to, uh, we'll step back a
bit because you mentioned before about, you

359
00:23:24.180 --> 00:23:28.089
<v Niall Sullivan>know, you share the successes across, you
know, other, other Bluescope sites, which,

360
00:23:28.140 --> 00:23:29.219
<v Niall Sullivan>you know, is fantastic.

361
00:23:29.300 --> 00:23:33.760
<v Niall Sullivan>So how has that sort of knowledge sharing
helped with, you know, your rollout

362
00:23:34.209 --> 00:23:37.300
<v Niall Sullivan>personally, you know, because obviously
it's from both sides as well, but, you know,

363
00:23:37.420 --> 00:23:41.020
<v Niall Sullivan>how, how's that collaboration and
knowledge sharing helped you?

364
00:23:41.150 --> 00:23:41.229
<v Niall Sullivan>Uh,

365
00:23:41.920 --> 00:23:48.660
<v Stewart McVinnie>it's been so great to be 6 to 12 months
behind them, um, because you learn what has

366
00:23:48.660 --> 00:23:49.540
<v Stewart McVinnie>and hasn't worked.

367
00:23:50.040 --> 00:23:56.109
<v Stewart McVinnie>Um, we can pick up the phone and call
other people in the business when we have

368
00:23:56.109 --> 00:24:02.510
<v Stewart McVinnie>questions and um and ask for advice, um,
but it's also allowed us to

369
00:24:05.109 --> 00:24:07.680
<v Stewart McVinnie>Tailor our deployment specific to us in
New Zealand.

370
00:24:09.040 --> 00:24:15.589
<v Stewart McVinnie>And one of the, one of the things we
identified really early on, was that There's

371
00:24:15.589 --> 00:24:21.829
<v Stewart McVinnie>quite a bit of subject matter, subject
matter expert knowledge needed to learn how

372
00:24:21.829 --> 00:24:26.170
<v Stewart McVinnie>to use Sensei, but then, know exactly what
sort of information you have for your

373
00:24:26.170 --> 00:24:28.150
<v Stewart McVinnie>assets to then configure Sensei.

374
00:24:28.790 --> 00:24:33.660
<v Stewart McVinnie>So, we had hypothesized that early on, but
seeing the rollout through other areas of

375
00:24:33.660 --> 00:24:38.209
<v Stewart McVinnie>business, we then started to realize that
that kind of hypothesis is right, and

376
00:24:38.910 --> 00:24:43.150
<v Stewart McVinnie>subject matter expert resource was going
to be the toughest challenge to everything

377
00:24:43.150 --> 00:24:44.089
<v Stewart McVinnie>we did rolling out.

378
00:24:45.069 --> 00:24:50.869
<v Stewart McVinnie>Uh, so what we, we based a lot of our kind
of coming back to that it upfront to go

379
00:24:50.869 --> 00:24:57.270
<v Stewart McVinnie>fast later on, we actually put a lot of
time in upfront to prioritize automation and

380
00:24:57.270 --> 00:25:00.469
<v Stewart McVinnie>automation and standardization ofs like
configuration.

381
00:25:01.400 --> 00:25:07.859
<v Stewart McVinnie>So we actually built our own tool to
Leverage a lot of Synthesized API

382
00:25:07.859 --> 00:25:11.530
<v Stewart McVinnie>capabilities, so we could automatically
integrate.

383
00:25:11.859 --> 00:25:14.780
<v Stewart McVinnie>We could standardize the configuration of
Sensei.

384
00:25:15.260 --> 00:25:21.280
<v Stewart McVinnie>We could effectively turn it into a single
click solution that utilize common,

385
00:25:21.939 --> 00:25:24.520
<v Stewart McVinnie>um, asset configuration strategies.

386
00:25:25.410 --> 00:25:28.790
<v Stewart McVinnie>To take that subject matter expert
knowledge.

387
00:25:29.530 --> 00:25:34.089
<v Stewart McVinnie>Away from our people having to learn
sensi, and then just leverage what they know

388
00:25:34.089 --> 00:25:41.010
<v Stewart McVinnie>about their plants so that they would, for
example, we have pre pre-developed

389
00:25:41.010 --> 00:25:43.930
<v Stewart McVinnie>a template for what an electric motor
should have.

390
00:25:44.410 --> 00:25:47.109
<v Stewart McVinnie>An electric motor should have a run
signal, probably should have temperature,

391
00:25:47.329 --> 00:25:52.250
<v Stewart McVinnie>probably should have speed and vibration,
um, and potentially a load.

392
00:25:53.270 --> 00:25:58.989
<v Stewart McVinnie>And from that information, we can then use
that to configure with whatever data they

393
00:25:58.989 --> 00:26:00.910
<v Stewart McVinnie>have that matches those that template.

394
00:26:01.150 --> 00:26:05.130
<v Stewart McVinnie>We can pre-configure everything in Sensor
using standard governance, naming

395
00:26:05.130 --> 00:26:09.910
<v Stewart McVinnie>conventions, all your configuration
groups, eliminating that sense our knowledge

396
00:26:09.910 --> 00:26:13.890
<v Stewart McVinnie>ensuring that what we're deploying is
accurate, repeatable.

397
00:26:14.719 --> 00:26:15.739
<v Stewart McVinnie>And trustworthy.

398
00:26:16.119 --> 00:26:21.339
<v Stewart McVinnie>So that was one of the big learnings we
had from following the Australian business,

399
00:26:21.920 --> 00:26:28.479
<v Stewart McVinnie>is we had a theory, we saw the need for
that, and put a lot of time and effort

400
00:26:28.479 --> 00:26:33.560
<v Stewart McVinnie>into building an automated solution which
is now allowing us to accelerate quite

401
00:26:33.560 --> 00:26:36.300
<v Stewart McVinnie>quickly, given the effort we put in
upfront.

402
00:26:37.790 --> 00:26:39.790
<v Niall Sullivan>Yeah, that, that, that was the point I was
gonna make actually.

403
00:26:39.939 --> 00:26:44.949
<v Niall Sullivan>It sort of set, set the, the groundwork
for, for scale, which, um, you know, looks

404
00:26:44.949 --> 00:26:48.459
<v Niall Sullivan>like to be the next sort of frontier for
you guys, you know, scale across more, more

405
00:26:48.459 --> 00:26:49.290
<v Niall Sullivan>assets, right?

406
00:26:50.369 --> 00:26:51.300
<v Stewart McVinnie>Yeah, exactly.

407
00:26:51.380 --> 00:26:57.150
<v Stewart McVinnie>We've We've built our automation, we've
got our data foundations in place.

408
00:26:57.449 --> 00:27:00.829
<v Stewart McVinnie>We've proven the pilot, we've got our
subject matter experts on board.

409
00:27:01.140 --> 00:27:01.689
<v Stewart McVinnie>Let's go.

410
00:27:02.510 --> 00:27:07.790
<v Stewart McVinnie>And that's our goal for this financial
year, is to prioritize pretty much nothing

411
00:27:07.790 --> 00:27:09.329
<v Stewart McVinnie>other than since I roll out.

412
00:27:11.209 --> 00:27:14.849
<v Niall Sullivan>And, and what, what we haven't spoken
about is sort of a key aspect of the app,

413
00:27:15.089 --> 00:27:19.969
<v Niall Sullivan>particularly over the last 12 to 18 months
is, um, the generative AI capabilities,

414
00:27:20.050 --> 00:27:22.839
<v Niall Sullivan>the, the, the, the co-pilot capabilities.

415
00:27:22.930 --> 00:27:25.829
<v Niall Sullivan>I just wanted to get a feel from you, um,
Stuart, at this stage.

416
00:27:25.890 --> 00:27:31.050
<v Niall Sullivan>Um, I guess how, you know, how, how are
your colleagues sort of responding to the

417
00:27:31.050 --> 00:27:31.449
<v Niall Sullivan>co-pilot?

418
00:27:31.479 --> 00:27:34.130
<v Niall Sullivan>Are they, you know, how are they using it
to sort of inform?

419
00:27:34.170 --> 00:27:39.250
<v Niall Sullivan>I know this success case in particular,
um, gave some indication and hopefully

420
00:27:39.250 --> 00:27:43.089
<v Niall Sullivan>assisted with the, You know, the
investigation of the issue, but maybe you could

421
00:27:43.089 --> 00:27:45.349
<v Niall Sullivan>give a bit more uh detail around that.

422
00:27:46.589 --> 00:27:52.869
<v Stewart McVinnie>Yeah, the co-pilot capability is still
pretty new for us, um, because the thing with

423
00:27:52.869 --> 00:27:56.109
<v Stewart McVinnie>copilot is it learns from what we're
putting in the system, right?

424
00:27:56.640 --> 00:28:02.150
<v Stewart McVinnie>And as we've only got 300 assets in there,
we haven't had a huge amount of cases, we

425
00:28:02.150 --> 00:28:07.849
<v Stewart McVinnie>haven't put a lot of feedback in, given
not a huge amount of cases, so the, the

426
00:28:07.849 --> 00:28:12.949
<v Stewart McVinnie>seaside copilot feedback at this stage is,
um, is relatively light, just because it

427
00:28:12.949 --> 00:28:14.719
<v Stewart McVinnie>hasn't got that to build on, um.

428
00:28:15.000 --> 00:28:19.750
<v Stewart McVinnie>But we do expect it to become quite
informative as we provide more feedback because

429
00:28:20.369 --> 00:28:21.410
<v Stewart McVinnie>It all makes sense, right?

430
00:28:21.489 --> 00:28:27.250
<v Stewart McVinnie>With with generative AI we know what it
can do, and if we are giving it feedback and

431
00:28:27.250 --> 00:28:32.329
<v Stewart McVinnie>we see a similar case in 12 months' time,
we totally expect copilot to say, hey, we

432
00:28:32.329 --> 00:28:35.030
<v Stewart McVinnie>saw this 12 months ago, here's what you
decided then, so.

433
00:28:36.180 --> 00:28:40.300
<v Stewart McVinnie>I think we're aligned with the vision and
the opportunity that co-pilot's going to

434
00:28:40.300 --> 00:28:45.979
<v Stewart McVinnie>bring, um, and we're going to see that as
we give it more time, build the cases, get

435
00:28:45.979 --> 00:28:49.959
<v Stewart McVinnie>our documentation and senseize so that
it's start to build up that knowledge base to

436
00:28:50.219 --> 00:28:52.750
<v Stewart McVinnie>provide more and more of that valuable
feedback from.

437
00:28:54.459 --> 00:28:58.180
<v Niall Sullivan>Yeah, and actually if we take, take a
little step back from that as well, because

438
00:28:58.180 --> 00:29:03.900
<v Niall Sullivan>another maybe not forgotten functionality
related to Gen AI and in Sensei, but it's

439
00:29:03.900 --> 00:29:08.459
<v Niall Sullivan>in, in the case itself where, you know,
there's, there's graphs and things like that

440
00:29:08.459 --> 00:29:12.380
<v Niall Sullivan>which people can interpret, but actually
it's the summaries of, you know, what's

441
00:29:12.380 --> 00:29:15.459
<v Niall Sullivan>happening, what, what could potentially
you could do, you know, rather than trying

442
00:29:15.459 --> 00:29:19.199
<v Niall Sullivan>to interpret and look at graphs, you can
now just say, oh, there's a snapshot of

443
00:29:19.199 --> 00:29:19.790
<v Niall Sullivan>what's happening.

444
00:29:20.130 --> 00:29:22.770
<v Niall Sullivan>You know, maybe comparing it to different
cases and things like that.

445
00:29:23.069 --> 00:29:27.689
<v Niall Sullivan>So I see that as a sort of a big plus as
well, uh, separate to the co-pilot, I guess

446
00:29:27.689 --> 00:29:28.449
<v Niall Sullivan>in that respect.

447
00:29:29.880 --> 00:29:32.550
<v Stewart McVinnie>Yeah, since size there to make our lives
easy, right?

448
00:29:33.109 --> 00:29:37.880
<v Stewart McVinnie>Interpret interpreting a vibration or a
temperature or pressure trend, that's what a

449
00:29:37.880 --> 00:29:42.069
<v Stewart McVinnie>lot of our people have done for the last,
since 1965, right?

450
00:29:42.530 --> 00:29:45.339
<v Stewart McVinnie>We've done it for decades, so that's
nothing new to us.

451
00:29:45.550 --> 00:29:49.339
<v Stewart McVinnie>But what's fantastic is since that tells
us exactly where to look and why.

452
00:29:50.140 --> 00:29:53.290
<v Stewart McVinnie>So you're not having to trawl through the
last 24 hours of data.

453
00:29:53.469 --> 00:29:57.550
<v Stewart McVinnie>You come in in the morning and it's
highlighted a 1 hour window on a case saying,

454
00:29:57.800 --> 00:29:59.189
<v Stewart McVinnie>here's a problem, have a look at it.

455
00:29:59.569 --> 00:30:05.130
<v Stewart McVinnie>So it's just, it's giving us that push in
the right direction, far more streamlined

456
00:30:05.130 --> 00:30:10.369
<v Stewart McVinnie>and making us be more efficient with our
time, um, instead of looking at hours with

457
00:30:10.369 --> 00:30:13.030
<v Stewart McVinnie>the trends that likely have nothing in
them.

458
00:30:13.739 --> 00:30:17.660
<v Stewart McVinnie>Um, and then when we do have something in
them, you've got to be alert enough to

459
00:30:17.660 --> 00:30:21.780
<v Stewart McVinnie>pick it up, where a sense size pointing us
straight to where the the opportunity is.

460
00:30:23.109 --> 00:30:26.420
<v Niall Sullivan>Yeah, and the way, the way I sort of
explain it as well is even someone like me can

461
00:30:26.420 --> 00:30:30.750
<v Niall Sullivan>interpret some of that stuff, right, so it
makes it easy for everyday people like me

462
00:30:31.530 --> 00:30:31.540
<v Stewart McVinnie>or

463
00:30:32.150 --> 00:30:37.510
<v Niall Sullivan>so, yeah, so it's such, such powerful, um,
such powerful, um, functionality.

464
00:30:38.250 --> 00:30:43.890
<v Niall Sullivan>Um, so, yeah, I guess as we, we come
towards the end, Stu, um, and we've covered so

465
00:30:43.890 --> 00:30:47.410
<v Niall Sullivan>much, it's been really interesting to
learn about your, um, story at Bluescope New

466
00:30:47.410 --> 00:30:47.589
<v Niall Sullivan>Zealand.

467
00:30:48.170 --> 00:30:51.410
<v Niall Sullivan>Um, and you've sort of touched upon this
question already, but maybe to, you know,

468
00:30:51.489 --> 00:30:54.650
<v Niall Sullivan>sort of bring it together and summarize,
sort of, what does the future look like,

469
00:30:54.890 --> 00:31:00.050
<v Niall Sullivan>um, with Sensai and the deployment and
what, what are you looking to focus on next,

470
00:31:00.209 --> 00:31:01.630
<v Niall Sullivan>um, regarding that?

471
00:31:03.380 --> 00:31:05.439
<v Stewart McVinnie>Yeah, so, so for us.

472
00:31:06.280 --> 00:31:08.349
<v Stewart McVinnie>The focus at the moment is now to roll it
out.

473
00:31:09.290 --> 00:31:14.640
<v Stewart McVinnie>Um, so, we've got 300 assets targeting
3500 assets.

474
00:31:14.969 --> 00:31:19.930
<v Stewart McVinnie>So that's about engaging with our teams,
training our people, identifying the

475
00:31:19.930 --> 00:31:25.530
<v Stewart McVinnie>priorities within these assets that we're
looking to target as a roll out, deploy it

476
00:31:25.530 --> 00:31:26.449
<v Stewart McVinnie>and monitor it.

477
00:31:26.930 --> 00:31:31.689
<v Stewart McVinnie>So, that's our focus, my team's going to
be out working with the plants to make this

478
00:31:31.689 --> 00:31:36.170
<v Stewart McVinnie>happen and that's literally our almost our
primary focus for the next 12 months.

479
00:31:36.579 --> 00:31:37.810
<v Stewart McVinnie>We working on.

480
00:31:38.140 --> 00:31:41.140
<v Stewart McVinnie>What's critical, and what's most suitable
for Sensei.

481
00:31:42.209 --> 00:31:44.369
<v Stewart McVinnie>And then it's sit back and kind of enjoy
it, right?

482
00:31:44.689 --> 00:31:49.989
<v Stewart McVinnie>It's tweak it, it's refine it, um, it
brings some more of those more complex type

483
00:31:49.989 --> 00:31:50.930
<v Stewart McVinnie>problems in.

484
00:31:51.670 --> 00:31:57.329
<v Stewart McVinnie>Um, so I kind of alluded to some of the
quality, um, opportunities and the likes

485
00:31:57.329 --> 00:32:01.680
<v Stewart McVinnie>where That's not quite, it's not
necessarily as black and white as the motor

486
00:32:01.680 --> 00:32:02.359
<v Stewart McVinnie>vibrating.

487
00:32:02.719 --> 00:32:07.880
<v Stewart McVinnie>It could be a combination of process
parameters that drift, which leads to quality

488
00:32:07.880 --> 00:32:08.319
<v Stewart McVinnie>defects.

489
00:32:08.400 --> 00:32:13.839
<v Stewart McVinnie>So, as we build more experience and get
the low hanging fruit, then we keep pushing

490
00:32:13.839 --> 00:32:15.219
<v Stewart McVinnie>into that, um.

491
00:32:16.180 --> 00:32:19.280
<v Stewart McVinnie>More, more complex, but equally beneficial
area.

492
00:32:21.160 --> 00:32:26.010
<v Niall Sullivan>And, and I guess also, um, maybe a word
towards the collaboration with the, uh,

493
00:32:26.319 --> 00:32:27.369
<v Niall Sullivan>maybe originally the SensaT.

494
00:32:27.939 --> 00:32:31.119
<v Niall Sullivan>I'm trying to think of the timeline you
gave, but maybe with the, with the Siemens

495
00:32:31.119 --> 00:32:34.319
<v Niall Sullivan>team, you know, how, how has that sort of
collaboration helped with the sort of

496
00:32:34.319 --> 00:32:36.939
<v Niall Sullivan>implementation and ongoing support?

497
00:32:38.000 --> 00:32:38.979
<v Stewart McVinnie>Yeah the.

498
00:32:39.880 --> 00:32:43.660
<v Stewart McVinnie>The the the support all the way through
has been super forthcoming.

499
00:32:44.410 --> 00:32:49.130
<v Stewart McVinnie>Um, so early on when we were trying to
kind of build a business case to support it,

500
00:32:49.209 --> 00:32:54.239
<v Stewart McVinnie>yes, we could say here's what we've done
in our pilot in Australia, um, but the the

501
00:32:54.239 --> 00:32:58.290
<v Stewart McVinnie>Sensite team at the time were, were really
supportive to help continue to build

502
00:32:58.290 --> 00:33:03.410
<v Stewart McVinnie>that, shape it and scope it for New
Zealand, um, and then throughout the

503
00:33:03.410 --> 00:33:08.609
<v Stewart McVinnie>implementation, um, the team's been
fantastic, and like I said, we've done something

504
00:33:08.609 --> 00:33:12.280
<v Stewart McVinnie>quite unique in terms of our automation
capabilities, um.

505
00:33:12.819 --> 00:33:16.020
<v Stewart McVinnie>And I like to think we've got a pretty
good relationship with the backend team at

506
00:33:16.020 --> 00:33:20.819
<v Stewart McVinnie>Sensive because we've asked some curly
questions, we've requested some features that

507
00:33:20.819 --> 00:33:26.540
<v Stewart McVinnie>a lot of possibly no one's ever asked for,
uh, so we've really pushed the boundary

508
00:33:26.540 --> 00:33:32.500
<v Stewart McVinnie>of that graphQL capability, um, but the
support and openness from the Sensite team

509
00:33:32.500 --> 00:33:38.680
<v Stewart McVinnie>to take our feedback on board, implement
it, open doors so we can pursue our vision.

510
00:33:38.810 --> 00:33:40.280
<v Stewart McVinnie>It has been massive, and then.

511
00:33:41.310 --> 00:33:47.150
<v Stewart McVinnie>The the ongoing support, um, and expert
knowledge on the use of the tool has really

512
00:33:47.150 --> 00:33:47.949
<v Stewart McVinnie>been helpful lately.

513
00:33:48.069 --> 00:33:52.510
<v Stewart McVinnie>So how do we continue to drive down
nuisance cases?

514
00:33:52.589 --> 00:33:55.489
<v Stewart McVinnie>How can we tune the algorithm to be more
accurate and responsive?

515
00:33:56.339 --> 00:34:01.890
<v Stewart McVinnie>That that intricate knowledge that the
Sensi team have of the tool is invaluable for

516
00:34:01.890 --> 00:34:05.329
<v Stewart McVinnie>us to rapidly develop and continue to
improve because if we're going to learn the

517
00:34:05.329 --> 00:34:07.729
<v Stewart McVinnie>hard way, it's all going to take time,
right?

518
00:34:07.890 --> 00:34:13.370
<v Stewart McVinnie>But we literally meet with the team
weekly, um, to continue to refine and tweak and

519
00:34:13.370 --> 00:34:14.149
<v Stewart McVinnie>develop the tool.

520
00:34:15.899 --> 00:34:17.399
<v Niall Sullivan>No, that's really fantastic to hear.

521
00:34:17.540 --> 00:34:22.100
<v Niall Sullivan>Um, uh, and what I would say on the
product side is that we do, uh, I'll speak,

522
00:34:22.419 --> 00:34:27.340
<v Niall Sullivan>speak on behalf of the product team, but,
um, genuinely do speak to customers

523
00:34:27.340 --> 00:34:32.620
<v Niall Sullivan>regularly, you know, in, in small
sessions, um, you know, uh, give background on,

524
00:34:32.699 --> 00:34:36.300
<v Niall Sullivan>you know, what's coming up in the roadmap
in terms of new, new functionality and

525
00:34:36.300 --> 00:34:40.090
<v Niall Sullivan>things and not, like you said, offer
customers like yourself the opportunity to

526
00:34:40.090 --> 00:34:40.719
<v Niall Sullivan>actually provide.

527
00:34:41.610 --> 00:34:45.100
<v Niall Sullivan>Feedback and implement it into the
products as well, importantly, so that, that

528
00:34:45.100 --> 00:34:46.020
<v Niall Sullivan>does, that does happen.

529
00:34:46.100 --> 00:34:47.469
<v Niall Sullivan>So I'll give a shout out to those guys.

530
00:34:47.889 --> 00:34:51.889
<v Niall Sullivan>They, they do a fantastic job, um, as well
as the rest of the team, I should say, as

531
00:34:51.889 --> 00:34:52.179
<v Niall Sullivan>well.

532
00:34:52.290 --> 00:34:56.889
<v Niall Sullivan>Um, but, um, but yeah, no, for today's
shoot, that's, I think we've, we've come to

533
00:34:56.889 --> 00:35:02.070
<v Niall Sullivan>the end, but it's been really interesting
learning about, um, your success, um, and

534
00:35:02.070 --> 00:35:02.860
<v Niall Sullivan>continued success.

535
00:35:02.939 --> 00:35:06.820
<v Niall Sullivan>I could, I could only hope that, that, the
trajectory seems to be very much, um, you

536
00:35:06.820 --> 00:35:08.620
<v Niall Sullivan>know, scaling up and seeing more success.

537
00:35:08.719 --> 00:35:10.699
<v Niall Sullivan>So I do, um, wish you all the best.

538
00:35:11.159 --> 00:35:13.610
<v Niall Sullivan>With that and look forward to hearing all,
all about it as well.

539
00:35:13.729 --> 00:35:15.959
<v Niall Sullivan>Maybe we could do another one of these to
discuss it, who knows?

540
00:35:16.120 --> 00:35:18.459
<v Niall Sullivan>But, um, it's been a real pleasure to talk
to you today.

541
00:35:19.949 --> 00:35:20.590
<v Stewart McVinnie>Yeah, thank you, Nia.

542
00:35:20.719 --> 00:35:25.149
<v Stewart McVinnie>I think it's a great opportunity, right,
to share our story with other people, um,

543
00:35:25.159 --> 00:35:30.000
<v Stewart McVinnie>but yeah, to cycle back in a year or so
when we've got 4000 assets, it'll be a great

544
00:35:30.000 --> 00:35:34.959
<v Stewart McVinnie>story to tell and a real demonstration of
what setsite scale can look like, right?

545
00:35:35.860 --> 00:35:37.239
<v Niall Sullivan>Absolutely, absolutely.

546
00:35:37.469 --> 00:35:41.280
<v Niall Sullivan>Um, and it's on the record now, so I can
hold that, hold you to it.

547
00:35:42.469 --> 00:35:43.520
<v Niall Sullivan>No, fantastic.

548
00:35:43.639 --> 00:35:49.159
<v Niall Sullivan>So, um, so yeah, I'd like to thank you for
your time, Stu, um, and I'd like to thank

549
00:35:49.159 --> 00:35:53.100
<v Niall Sullivan>everyone, um, wherever you are for
listening, and we'll see you on the next episode.

550
00:35:53.479 --> 00:35:54.399
<v Niall Sullivan>Thank you very much.

551
00:35:55.800 --> 00:35:56.419
<v Stewart McVinnie>Thanks now.

552
00:35:59.540 --> 00:36:04.500
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

553
00:36:04.500 --> 00:36:07.879
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
