Turning Avoided Downtime Into Financial Value - with Rafael Iadocicco

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.

When predictive maintenance prevents a breakdown, the operational benefit may be clear. Proving its financial value is harder. Because the failure never happened, manufacturers need a credible way to estimate what was avoided without exaggerating the impact.

In this episode of the Trend Detection podcast, we were joined by Rafael Iadocicco, Customer Success Manager at Siemens, to explore how manufacturers can turn avoided downtime into a fair, transparent and repeatable estimate of financial value.

In this episode, we discussed:

Why calculating avoided downtime begins with the operational story, not the financial formula

How early warnings, inspections and maintenance actions create a credible chain of evidence

Why maintenance, operations and finance must agree on the affected scope, avoided hours and financial basis

When a simple cost-per-hour calculation is sufficient and when a detailed breakdown is needed

How to account for lost production, scrap, restart waste, emergency labour and spare parts

Why conservative assumptions build more trust than pursuing the largest possible number

How to avoid exaggeration, double counting and confusion between gross impact and net value

How a consistent process can be replicated across assets, plants and industries

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

I, I like to say that avoid downtime is never an exact science. Goal is not the precision of the door. The main goal is a fair, transparency, and repeatable estimate that business trust. Welcome to the trend detection podcast, powered by Siemens. Hello and welcome to the latest episode of the trend detection podcast. I'm really pleased to be joined by Siemens colleague today, Rafael, and new, new to the podcast, Rafael, so welcome first of all. Thanks a lot, Neil, for the invited to have me. This is a pleasure to be here talking to you. Fantastic, fantastic, and today we're talking about, well, downtime actually, which is a word we've used many times on this podcast. But the reason why we're bringing it to the table today, it's actually an interesting thing that Rafael brought to the table. It was a presentation for a customer about turning avoided downtime into financial value, which, you know, maybe sounds obvious to some, but it's not, not always clear how best to do that. So that's exactly what we're gonna cover today. But I guess before we do, Rafael, maybe you could introduce yourself to the audience and what your role is at Siemens. OK, so is. It's a pleasure to talk with all the, your audience, and I am an electrical engineer. I, I have 20 years working by Siemens. I started in Siemens, Brazil and now in Siemmens US and now I am a customer success manager. Supporting all the customers with the same side that the product manager too. Fantastic, fantastic, so yeah, again, you're a perfect person to have on the podcast, so, I mean, maybe let's just open up the discussion to start with, so, you know, why is it difficult to turn downtime into financial value, first of all? It's difficult because the, the, the failure never happened. It's different because the break it down never, never happened, and so you, you need to use your experience and to identify what they could happen if this part of these assets break or shoot down suddenly. This is the point of the main. Difficult thing when we start to think of what actual worth in avoiding the downtime. It's different, the big, the challenge is not the math of how to calculate and bring the the downtime avoided to the financial, the money, but the bigger point is, if I leave this and I didn't receive any early detection. What could happen? That's the point. How much hours I avoid with this, this, this, of course, today we have AI to support us, but we start with the, the, the knowledge and experience for maintenance and cooperation. But the goal here is not to reach the perfect number, but the goal here is create a transparent and clear path that we can. Estimate it very well how we, what we avoided. Yeah, so I guess, maybe, maybe the, the first thing to think about is, so what evidence actually makes an avoided breakdown credible rather than something that's hypothetical. In taking on your point you just mentioned there, well, I think that to be a credible case, we need to have a clear chain of evidence. We, like I said, we start with early warning, then the mentors can do an inspection and confirm that there is an issue in disaster. Then it will become the action and the agreed consequence between the maintenance, operation, financial. And everything should be recording the assumptions that to have a very confidence level. With this, we make the value transparency harder than a a a hypothetical. Maybe Rafael, you could walk us through an example, so from the first warning to then putting a financial value on the intervention. Maybe that's the best way to illustrate it. Yes, let us imagine that we have an asset and you receive an early warning from Sengsai, and, and the mentors go there and make an inspection and identify that there is a problem developing in the bearing. So what they they they managed to do, they take, take advantage for a plan and stop it and change the bearing or make all the repair that is necessary to fix this issue based on previous problems or on his nausea or the medicine knowledge, they can estimate that they avoid 4 hours of a breakdown. So then we apply a proven financial basis or they start calculation in details what they avoided if they avoided production loss, material loss, or extra maintenance labor and everything that should be included in this calculation. This, the result is important and estimated gross impacted and with the assumption clear documented to be very transparent, to be very trust and replicable. I don't know, we can, I can, for example, you have a, a, a machine and this, this problem you avoid 4 hours with breakdown. Imagine that this machine produces 500 units per hour. So you have an idea in 4 hours, you just move, make a very easy multiplication, 4 hours times 500 units per hour, so you have the amount. Then you start to, I, I lost some material, I lost some, I need more spare parts or not, so you can add some points here to, to enhancement data calculation, but everything needs to be very clear and transparent. And I guess, and that's interesting you, I mean it's a really good example you shared there, but I guess before, before anyone reaches for a calculator for that, there needs to be some alignment, and I think you mentioned briefly. The teams involved, which are potentially maintenance, operations, and finance, so what, what needs to be agreed between those different departments first before calculations can even begin? Well, before the calculation, all the teams need to agree about the event. You, you have the event, the avoid hours, they affect scope, what I, I want to say that. The scope is only this machine. The the problem affect only this machine or they affect the line or the whole plant. That is something that is make it very clear. Sometimes you, you, you have a a a feeder in in in start of the line. If this machine is stopped, the whole line is stopped. So you, you need to understand the whole effect in the Scorpipe effect, and then you go to financial basin. Minance and operation validation, the operation story and fantasy validation, the, the impaction in converting money. Everything, all, all the, all the teams need to be very synchronized and aligned about this. Mentors give the, the, the action, the issue, operation give you all the information about how they are lost or not the. The scope and the, the material and the scope and the financial helps with the money. And we've always talked about, you know, you know, different stakeholders and they're an important part of the process, but, and, and we know stakeholder alignment's obviously important, but, you know, is it often that each of those departments are in agreement about. You know, about a calculation or or or in disagreement, and I know it depends on the customer is the short answer, but do you, do you see where there might be agreement and where there might be sort of disagreement in that process? Yes, there is no one team that has our answers. So you, you need to be very aligned with our process in, in, in, in, in the supply chain in, in the production. So if you have uh the synchronized and you, you work everybody to work together, it's easier to have a a a very trust and credible, how to say this, it's easier to, to understand the, the, the, the impact of the this downtime well when you have the cooperation between all the teams. And you know, I'm again thinking about the impact, you know, you know, the example, going back to the example you gave actually and I'm just thinking how you might estimate how long a machine would have been down without exaggerating that impact and what should you do when there's uncertainty, because I know, and again it's, it's in line with what you're saying there needs to be agreement across then, but first of all you need a, an estimate that is realistic, right, I guess is what I'm saying. Yes, you're totally right. Uh, we, we start using operational experience and the days from similar failures. We can consider the timing of diagnosis of the problem, get people and parts completed the repair, restart the machine, and return to normal production. Do not choose the largest possible number. Who's who's the most reasonable number that the, the teams can support? When there is an uncertain or or right when there is an uncertainty number, who is the conservative estimating? Is who is it that something that is agreed between the teams and make this more, how to say, more transparent. If otherwise you always overestimated and exaggerated and the the numbers start to be not very trustable. Yep, and I guess another part of it is thinking about what cost to consider as well, cos, I mean, we can list some examples here, I think you've already mentioned a few already, but. You know, where you've got, you know, the downtime potentially itself, but you know, the scrap, restart losses, emergency repairs, any additional damage to the machines in question, so how, and that's quite a long list already, right, but how do, how do you bring those into that calculation and still get that agreement cos that's a lot, lot of things going on, let's say. Yeah, like you said, it depends on the customer, depends on the industry, you have a lot of numbers comes, but for sure, the last productions is the, the often in the big eaten, but it is not the only one like we said before. We should, we should also consider labor or overhead that continues during the stop. Scrap it shutdown. Imagine that you are producing something and during the stop, you need to scrap all the material that that are inside of the machine. So this is a kind of something that you need to put in this calculation. Waste waste during restart. Imagine that when you restart the machine. The first units is not in the quality that you need, so you need scrap as well, energy labor or spare parts, or imagine that you can hire a specialist or a company to fix a special part of the machine. So you have a lot of cases, a lot of things that can contribute to this calculation, but you can We, we can also have a very easy calculation. One hour from this line, stop at is 500, 5000 hour, or you can go item by item, and depends of of the the the issue, depends on the the the case. And I know, I know we've talked about what goes into a calculation, who needs to be involved, and. And you've, you've explained that really well, but I guess just to play devil's advocate a little bit, you know, when, when would a sort of a simple cost per hour calculation be enough versus what you've been describing, Rafael, which is a more of a detailed breakdown, you know, is there a time where a much simpler calculation would work reasonably well? Yes, we, we need to, uh, in this case, we should not claim the full, the full production value perms. I would like to divide into two paths. The first in a simple path is sitting in one table, maintenance, operation, and financial, and we know how many units this machine produces per hour. We know how much employees need to run this machine, and you put everything that contribution for this, for this line or for this machine. And financial support for the money. So you have a very clear and agreed value per hour for this line or machine. So is when you have some warning and you make some work event or you make, you, you, you, you use a plan and stop to fix this asset and you based on Your early experiences. So I, I avoided for hours. So you have a number to to make a very simple multiplication. But if you have a uh an biggest issue or something that's not before agreed, you start calculation item by item. So you start calculation, if this bearing, I have a problem with this bearing, I need to change the shift. I I have to change the, the. The conveyor, everything that you can include it. So usually it's easier. You go, you sit before with all things and agreed about the value of this hour for this machine or this line of this plant. If this happens out of this agreement, record and make all the documents necessary to be transparent, to be clear, and to be audit. And make all the points, how many hours you need to fix it, how many the spare parts, everything. And I guess to go on a slightly different, cos you mentioned different, you know, different lines or even different, different plants, but how well, say you're working with a global customer of plants all around the world, how, how does uh, A similar break or potential breakdown saved in 11 plant compared to another plant, do they have to be treated, I guess, completely differently in, in terms of how you would calculate the, you know, the potential savings there, and again, I know it depends on different factors, but yeah, if they're relatively similar, is there any sort of crossover between that between you sort of multiple similar cases where there's where intervention's been spotted early? Well, we, we try to support the customers, but the the customer knows better than us about their production, and if you have the plant, the plant A and plant B, the nature is the customer has for each plant, the cost is because you have taxes, you have a lot of things different from state for state, city for city. So, but the, the process and base of calculation should be the same, should not have a a a lot of difference in the calculation. You have some particulars, but you and depends on what you are producing. We have customers that production, for, for example, you have 3 or 4 kinds of production in the same line of products. So you, you, you, you need to understand what is production in that time and what is the cost involved in this, with this product. So it can be a a a a discordance or there is not agreed between two different plants, but the, the process to calculate or the process how to identify and avoid problems should be the same. The math can be different, but the process to start on the warning and investigation and action should be the same. Oh, absolutely, absolutely, and I guess, yeah, I guess there's, you might have answered this a little bit already, but in terms of, I'm sure when trying to report financial value, there's, you know, there's traps you can sort of fall into, you know, things like double counting or trying to. Distinguished gross avoided costs and, and things like this. So what are the traps that you'd sort of recommend people avoid when trying to calculate the financial value? I, I think the main trap are exaggerated hours, the wrong financial base and double counting. This is the main trap that I see in the process. We should first report the estimated gross impact if we want to show the net value. We then substructure the intervention causes and relevant problem costs. Keeping those numbers separate makes the, the, the story much clearer for the process. Right, that makes, that makes a lot of sense. So I guess one thing we haven't covered, Rafael is thinking about vertical, you know, or, or industry and, and wondering whether the, how, how this calculation is put together, does it differ depending if you're in sort of life sciences versus. You know, mining versus automotive, or is the, are the fundamentals basically the same? Yeah, each, each industry has your particular, I mean, if you are producing food, you have more attention in the quality in the, the clean rooms, you, you, you, you, you have more, you have one kind of concern. If a production flip flops, there is another kind of concern that you don't need you even about the pilot. So each industry has your particular when you make the complaintation about the downtime avoid the the wharf turning, turning this in money because the loss of production or the scrap of products can be different between. The process, I, I think it is that I don't know if I, I answered right to your question, sorry for that. No, no, you did, you absolutely did. So we know there's different processes, but in general, I think that what you're saying is the pro the process is, is the same, but obviously we know there's, you know, different manufacturing environments will mean adjustments to how things are calculated. Yes, I like to say that avoid downtime is never an exact science. Goal is not the precision of the door. The main goal is a fair, transparency, and repeatable estimate that business trust. If you have a clear process, you have everything documented and not exaggerating or double counting. You have a very good and strong process to replicable and make this worth and present for all stakeholders how much you save for the company. Yeah, and I think that's, that's the right way to put it, cos I know there will be people out there who'll be thinking, or maybe overthink is probably the phrase where, you know, they're trying to think of the exact right cost, right, but I think you said a really good phrase earlier, it's about, you know, one that feels comfortable to those everyone involved, right? Rather than looking for perfection. Yes, we, we need to start with a very strong case, you have a warning, evidence, investigation, and we're using a plan to stoppage to do that. And when you start the the right way, the process, you can replicate and very it is give you a lot of trust for the, the, the whole company. Exactly, exactly. So I guess we're coming towards the end. Now, um, I think we, we've covered it in, in great depth, but I guess the, the only final question remains is, you know, for, for a listener who's, who isn't measuring this consistently, you know, what's the first step or the most simple step they could take today to sort of calculate the potential savings. And then how can they turn that into like a repeatable process in other parts of their plant or other sites in, in their scope? I think the first of all, trying to get agreement between all parts involved, maintenance operation and financial. Start before have a, a case, made this exercise to calculate. After that, it start with a strong case, like I said, with all the documentation, all, all the transparency, and. I think I have some points here. Trust is more important than the biggest number. The estimate should be fair and transparent, to be repeatable. The calculation starts with the operation story. First validate the vein, the hours and the scope, then calculate the money. And again, I, I know that I already told you, but for the audience. A very strong work or a very strong teamwork is better than trying to avoid or estimate this alone. Working together with all the the the the sectors, the teams is better than you trying to identify alone. Yeah, cos I mean certainly it's a lot of pressure to put on one person. To, to come up with a, a number you need, you need the different inputs, and that could even be, maybe that's a good question actually, is we've talked a lot about the customer side, but maybe what would a vendor like Siemens provide to the process, Rafael, aside from the, the software, if we're talking about Sen side, but, you know, aside from that, what, what expertise can, can we provide as Siemens? Well, oh. SS has a huge portfolio, not only CSI. We have a lot of software to energy saving or OE production. We have a lot of softwares and tools that we can support with this, but I think that the best what we can offer is our support, the team behind of this all these tools and how we can. Understand the customer needs and drive the customer inside of finished portfolio. That's the man. I, I, I would like to say that problems happens all the time, but how you fix this and how you treat your customer is make a difference for, for the, the market. Exactly, and I think that's a, a perfect way for us to, to finish today, Rafael. So once again, thank you for joining us. For the very first time, and hopefully you'll, you'll be open to coming back on in the future as well. Thanks a lot in you for the opportunity and I have, I, I, I wish you a very good day and, and I am open every time that you need, please come with me. …

Full transcript (WebVTT)