New Zealand Steel Success Case Deep Dive - with Stewart McVinnie

Trend Detection Podcast ·

Show notes

Welcome to the Trend Detection podcast, brought to you by Senseye Predictive Maintenance – which gives you visibility and insights into all your assets, from single machines to full plants to help you reduce downtime, increase knowledge sharing and accelerate digital transformation across your organization.

In this episode:

Learn how New Zealand Steel, as the country's only steel maker, implemented predictive maintenance technology to enhance their unique iron sand-to-steel manufacturing process

Discover how a strategic pilot program and robust data foundation helped build trust and drive successful adoption of predictive maintenance across the organization

Understand how early detection of equipment issues, like loose gearbox mounting bolts, helped avoid 12 hours of critical downtime and potential catastrophic failures

Explore how automation and standardization of configurations helped scale the implementation from 300 to a target of 3,000-5,000 assets while maintaining quality

Learn about the multiple benefits beyond just downtime prevention, including quality improvements, yield optimization, and how proper data governance enables future digital transformation initiatives.

You can find out more about how Senseye Predictive Maintenance can reduce unplanned downtime and contribute towards improved sustainability within your manufacturing plants, by visiting: www.siemens.com/senseye-predictive-maintenance

Transcript

What kind of comes back to that trust piece is this engineer, Trust Sensei. He knows that if Sensor see there's a problem, there's a problem to find. And he proceeded to kind of climb all over this, this motor roll gearbox assembly, and right down to the depths of it, where he found the mounting bolts of the gearbox to be loose, 3 out of 4 of them. And if we didn't have that trust, you'd give up and say, oh, it must be a false case from Senseii, the coupling's fine and the mode is fine. But having that trust, and the drive to keep looking until we find the root cause, has led us to tighten up 3 bolts and and lead to a 12 hour downtime avoided, which, you know, 12 hours in in any industry, in any Um, plant is, is fantastic. Welcome to the trend detection podcast powered by Siemens, and now your host, Nel Sullivan. Hello, um, and welcome to this very special episode of the trend detection podcast. Um, I'm joined by Stu McVinnie, um, from Bluescope New Zealand, and Bluescope Steel New Zealand, in fact. Um, and a lot of regular listeners will know we've, we've spoken a lot to Bluescope Steel. I'm a very fantastic customer of Siemens and of the Sensai product, and we've spoken to Colin Robertson and Chris Watson. Um, very recently as part of our live event, um, you can check that out on the podcast now. Um, but today we're talking about BlueScope New Zealand's very unique part of the story as well, and all of the success, um, they've achieved so far and, and will achieve into the future as well, hopefully. Um, we're gonna focus on a particular success case and dive, deep dive into that. Um, again, we did a similar one with Chris Swanson of Bluescope as well recently, um. But before we go into that, um, Stu, it'd be great to get, um, a bit of, you know, an idea of your background, um, and of Bluescope New Zealand as well and where that fits into the, the overall picture of Bluescope. Um, so over to you. Yeah, cool. Thanks, Noel and good to be here and it is pretty cool to be able to share our our journey and focus it around one of our recent success cases because it is very successful and it's great to be able to share that. Um, just to kind of set the scene. I I'm Stewart McVinn, the digital transformation manager here at New Zealand Steel and we're a relatively new team. Digital transformation has been around, yeah, just gone 3 years now, um, primarily focused around what we call the asset intelligence, of which size is a really big part of trying to better and get the most out of our manufacturing assets. Um, to set the scene a little bit on us as New Zealand Steel, um, you mentioned already the term unique, and we are very unique down here at the bottom of the world. Um, we are New Zealand's only steelmaker. And what makes us unique is our process. So we're a fully integrated steel business, which means we do everything from the raw materials all the way through to finished goods. Um, but our raw materials are iron sands of our West Coast beaches. So we have a unique process where we can take, we mine these iron sands, and then process them through our iron making, steel making, and rolling mills, uh, to supply a large majority of New Zealand's domestic steel market. Um, so been around since 1965. So we're pretty well set in this industry within New Zealand. I mean we're a pretty loyal, um, bunch of customers with a pretty well-known product base across the country. Um, and yes, we are a subsidiary of Blue Scope Steel, so some of our colleagues that you'll have spoken to a part of the Australian business. Um, so yeah we are New Zealand Steel under that Blue Scope Steel umbrella. Fantastic. And I, I guess, um, before we go deep dive into the success case, Stuart, it, it'd be interesting to know the story behind the implementation of Sensai. Of course, there's a, a global rollout, um, of Bluescope Steel, but very specifically to New Zealand, you know, so what, what led to the implementation? Yeah, well, you mentioned that global rollout, and it was a really good use case. Um, so they kind of set the scene about 6 to 12 months ahead of, ahead of us kicking things off. But it was enough for our management kind of team to get a bit of a feel for what the opportunity was, to see some of the potential benefits, and then draw some of those similarities. We also have aging equipment, um, some of our continuous improvement. Sort of methodologies we're kind of flatlining and some of that, um, that growth. We're all faced with the changing workplace, and we're always looking for that modern approach for a step change in our asset performance. And so that's where the decision came to create the digital transformation team, and to then adopt asset intelligence, which is a big part of. I see. So that's interesting actually. So you, you formulated the team at that point to, to, I guess, manage the rollout of that particular project or other digital transformation initiatives as well? Was, was the predictive maintenance one was the trigger for it, let's say. Yeah, well, we, we created the digital transformation team with a suite of modules, um, envisaged to happen. We had some. Data work, we had some predictive maintenance, and we're considering some things like digital twins and mobile workers. Um, so there was a suite of modules that, um, our asset intelligence program of work, um, was envisaging working through, um, be a big part of that and one of the early things that got off the ground was the predictive working with Sensi. Fantastic. And, and how long have you been using the, the system now? I guess just for context for the audience. Yeah, we've. We've been working with Sensei for probably the best part of 2 years now, um, but really only been using the tool in anger, um, pretty much since Christmas. Um, so that's about about 67 months now, where we've had since I really providing value, implemented in production, and being used by our people. And I, and I guess, you know, seeing a success relatively soon is very positive, right? So the success we're talking about today, um. Yeah, you know, it's obviously a a great sign of the system's success and your success as well. Oh, the, the early success has been fantastic for building a business case, right? Um, to date, we've only got about 300 assets on board and success for us probably is around 5000. So, to be, to have had 4 wins in 6 months with 300 assets, I think it's it's an absolutely fantastic start, and a real good demonstration of what the potential of this is, when we hit that sort of target rollout of 3000 to 5000 assets. And, yeah, and clearly, like I said it's lots of room to grow there as well. So that's a really exciting part as well. Success already, but, you know, still lots of potential, right? Uh, we, we, when you look at the 4 success cases for 300 assets, you do the math, they, they're going to keep flowing and as we roll more and more out. And I guess, yeah, so let's, um, deep dive into the, the success we're, we're talking about today. So, it was actually, um, so Sensai actually detected, um, elevated vibration in the gearbox, I believe, um. So, as this is an example of early detection capability, um, how has it changed your maintenance practices sort of fundamentally as a, as an example? Maintenance practices wise, we're still pretty early in that journey, so 300 assets across our site is not a lot, so we've only just scratched the surface. So we haven't seen a big shift in those maintenance practices, but we're starting to see, um, some change small changes in the in the people working in those spaces. Um, moving from that uh reactive to proactive has been something we've observed already with just a few assets where people are starting to spend less time in the mornings looking at trends and those assets onboarded. And really just sit back and wait for so to bring up a case. So that's freed up some more time in the morning where they'd normally be looking at assets. They're now just reviewing cases. So that's been a bit of a shift there. And the other small one around the kind of maintenance side of things is we have managed to eliminate some vibration analysis inspections. So we we've got since I monitoring an asset that a person was going out once a month to go and see how it's performing. Uh, we've now only a small amount, probably 90 hours worth of work, something like that, but we have managed to take a little bit of that work as we've onboarded assets onto into sense size. So just Early indications of what some of these opportunities are to address some of that maintenance planning. Yeah, and then that's really good examples of, you know, like you said, even in sort of very early stages, sort of embracing the technology and trust, because, you know, trust to the system, you know, is key to sort of adoption and rollout. Um, was there sort of any particular initiatives you did with the maintenance teams to sort of encourage them to, to look at Sensai and, and use the information that's available through Sensai? Oh, you, you nailed it with trust. Trust was everything because We only had one chance to bring a lot of these people on board, and If you lose someone's trust early on, it's really hard to get it back, and then it's going to be really tough sell to get, since I'm moving forward from there. So we actually had a pretty robust pilot to start things off. And the idea with that pilot was to get all the learnings, to get everything polished up and tidied, to fix all the bugs and issues, so that when we went to production and rolled out, people had that trust because they weren't getting a product that wasn't fit for purpose. Um, it also gave us that credibility and the confidence to go out with our sales pitch to our customers, our internal customers and say, hey, we've got a fantastic tool that works, rather than saying, we think this will work, but if it gets annoying, let us know. So, we really spent a lot of effort and time upfront to make sure that we got it all right, and it would work, we rolled it out. And then the trust just came from using it. Um, people reviewing cases, monitoring their assets, start building into their habits and routine, um, and that trust slowly builds and kind of ironically. Those areas that had the most cases, started to build trust in it quicker, because they saw those opportunities and benefits coming through more often. Um, the trouble we've seen with some areas is they might get one case every week or two, because they've only got a couple of assets on boarded, in which case, you're kind of losing interest in between, whereas those that are getting several a week, um, keep their finger on the pulse and really get to demons see the demonstration of Sensei firsthand, so. That, that has been, it's been a really important part of our roll out and really successful. And the other one is just around, around our digital transformation team. Um, so, we've actually, a lot of our teams come from internal within the business. So that brings some credibility, some relationships and some experience in previous roles. So, when we say something works and are advocating for it, it just comes with the extra layer of credibility to kind of get us on the front foot for some of these customers. But, but all in all, Building that trust is probably Been a little bit easier than expected, but, likely because of the work we did up front, so we didn't have to, um, kind of explain many problems because they didn't crop up because we'd we'd solved it in the pilots. Yeah, and that, yeah, that, that's really interesting as well, because I guess sometimes there's a keenness, and maybe it's, yeah, it's not necessarily a bad thing, and enthusiasm start big and, and go big as soon as possible. But, yeah, what you're saying is it's use the pilot as a learning, as a learning curve. Pick up the learnings, introduce insights to the teams, and then see hopefully some early successes and cases and go from there and just build the momentum. Maybe that's another good word. I don't want to put words into your mouth, of course, but momentums often comes up in my conversations as well. Yeah I don't know if I'd use momentum at this stage, but the building up was, was really, really important. And and we're very well supported from our management team here. Very early on, we identified the pilot is important. We identified that getting our data foundation is important, and we identified some of the automation things that we wanted to achieve as important. But that meant effort upfront to deliver quickly later on. And when we had that real robust support from our management team saying, Yes, we beg you to do that because we know it'll be worth it in the long run. And and the prime example was The reason earlier on I said we started an anger at Christmas, is we had been playing around and deploying up probably for about 6 months before Christmas. And it wasn't working. And we actually stopped, deleted everything. reassessed our philosophy, and reloaded everything in March. So we've effectively stopped for three months, post-Cristmas, deleted all started again, and I've never looked back. It's been really, really fantastic. So, that's an example of how we built into it. We've gone in stages, we've learned, and we've had that support from our business to stop and fix it, when we found an issue, not Always looking for the fastest, biggest deployment, it was let's get it right for the long term success. And that, and that's fascinating as well. I mean, that's, that's such a brave decision because like I said, a lot of, you know, people would just sort of try and continue. It'll improve if, if we keep going and keep going, it'll improve, but you just decided to stop, scrap it, and almost start from scratch, and you, you're seeing the rewards now as well, which is just fantastic to hear. Yeah, it was Wasn't a comfortable decision to make. But looking back, totally the right decision to make, would make it again any day. And I mean, look where we are. So you mentioned multiple successes, you know, with, you know, with, um, you know, 300 assets, you said. So, you know, amazing success. We, the one we're focusing on today actually is, it mentions 12 hours of, um, avoided downtime, which we know, especially in, in your industry is very significant for a number of reasons. I mean maybe you could sort of outline that a bit, Stu, um, first of all, and then maybe we could quantify the, you know, the actual financial impact of that. What does that mean in actual? Not maybe not specific card numbers, but, you know, the financial impact generally. Yeah, well, on, on the use case itself. 1 12 hours is significant for us. That's that's half a day's operation, especially on a plant that's close to the bottleneck. It's, that's a really, really good one. But it was, it was an absolute fantastic case where, the case was generated in the morning and the engineer of that plant went out to investigate the gearbox in question and You walk out there with some preconceived sort of ideas, right? You walk out thinking it's going to be a loose coupling, or it's going to be motor, um cowling issues or something like that. So they've gone out and they've rattled the cowling, they've looked at the coupling, they've looked for backlash in the gearbox, haven't actually found anything. Uh, but what kind of comes back to that trust piece is this engineer trusts Sensai. He knows that if Sensai says there's a problem, there's a problem to find. And he proceeded to kind of climb all over this, this motor roll gearbox assembly and right down to the depths of it, where he found the mounting bolts of the gearbox to be loose, 3 out of 4 of them. And if we didn't have that trust, you'd give up and say, oh, it must be a false case from Sensei, the coupling's fine and the mode is fine. But having that trust and the drive to keep looking until we find the root cause has led us to tighten up 3 bolts and and lead to a 12 hour downtime avoided, which, you know, 12 hours in in any industry in any. Um, plant is fantastic and It's not just the downtime avoided, it's the fact that If those bolts had failed, and we had that catastrophic failure, you'd also lose the role of the gearbox and the motor. Um, so it's time, and it's that asset cost replacement as well. Yeah, but in terms of, sorry, no, no, no, you guys sorry I was gonna say but in terms of trying to quantify 12 hours. Um, the, the important thing to remember is we want to benchmark and comparable KPI for measuring the performance of Sensei. And the complication you get is when you try and convert a KPI of ours to a financial one. Because, Your your financial value or your value of an hour varies so much, it could vary by plant, it could vary by the market, like steel is a commodity product, so, at the moment we're quite low in the cycle with steel's not worth much, um, and other times the cycle steel can be worth an absolute fortune. So, depending on where you are in the cycle, an hour can be worth quite a quite a quite a bit different. So an hour today is not what an hour in a year or a month is. So it's, you got to be careful trying to compare these sort of benefits on dollar values, because you're not really comparing like for like at times. Hence why we primarily look for hours, um. And it's not just ours either, right? You've got Um, if you've got yield improvements that come from Sensei, you could be talking tons, uh, we could be talking some defects or downgrade, which is a quality savings. So there's a number of different KPIs that can be used to measure the benefits of Sensei, um, but to To give you a bit of a steer on where that value could sort of sit, well, if it's, if you're a high idle plant, um, not fully utilized, 12 hours of downtime, might not be worth anything, because you've got that spare capacity to make up the lost opportunity. Um, but if you are a bottleneck plant, 12 hours of downtime, it's in the tens of thousands. Um, in terms of opportunity, so. Since I really does, at the end of the day, provide significant benefits across multiple KPIs within a business. Yeah, and, and you've perfectly articulated, Stu, what we talk about internally a lot or, or with other customers as well, because it is easy to focus on that, um, downtime metric as the, the metric, but you've just explained very well why, you know, there's so many other benefits that maybe people wouldn't even have thought of, right? But were the, were those other KPIs, were they, those identified sort of early on, you know, when you're just starting to implement the technology, or do they become, Obvious, you know, just become obvious as, you know, the rollout began and more assets were on boarded. As a business, we live and breathe those sort of KPIs downtime avoided, quality loss, yield, defects. That's kind of our bread and butter, so they're always front of mind, but for simplicity, since I was initially just, um, justified on downtime avoided or hours, um, because that's such a big piece of the pie anyway, that if we nail that we've more than justified the investment in digital transformation and since I, um. But absolutely those other aspects. Have always been part of our mind and as we start to get closer to that successful deployment to what we kind of 3 to 5000 assets, targeting downtime, then we can look to say alright, now, how can we target quality loss? How can we target yield improvements, um, and they're, they're kind of like add-ons and as we progress to further leverage what SensI is providing us. Uh, yeah, and I, it's interesting to say sort of, you know, further leverage as well because it, what I liked about this success case as well, you mentioned it was all around, you know, um, uh, the loose base and bolts. So it's like it's spotted, you know, quite or potentially spotted a, um, uh, like a hidden maintenance issues. …

Full transcript (WebVTT)