Network Inventory

I said, look. This was the the first starting point for us, right, to put the foundation. Just to put it in perspective, even in just moving the cold inventory into the Amdocs. We cleaned out about four million attributes along the way. Alright. So all various different things that we needed to do. So this all goes plays back to the AI generation that they're about to live in. Without that data plane, you're not gonna be able to do the automation efforts that you really wish to do. We're about to move our acquired business inventory, and that actually is coming from five different inventory platforms back into one. So Coles can be very unique. Right? We've only got one inventory platform that houses all of our network assets. That's And I think that's where we now start to see the gen two AI piece coming in. And back to your original question, which I didn't answer, Joris, actually, which was the how does this improve customer experience? Right. Well, actually, what we want to be able to do is provide all of that real time data back to our customers so they can see their services, they can see the utilization, they can actually have a source of information that they can trust about their network capabilities as well. But more importantly, internally within our own organization, we're gonna start using that for capacity management capabilities as well. Where do we invest in our network? What areas of the network inventory do we think maybe out of date, out of support in driving risk from a cyber perspective as well? So, again, I think this is just the foundational element that really allows us to drive the value as we go forward, not only for Colt, but more importantly, customers as Couple of firsts for us, one was that we were doing a transformation on the inventory platform, first time pretty much in its history because the previous one had been around for that long. Second time second thing was that we're going into the cloud. So we're making this cloud native, and we decided that we were putting cloud for two reasons, really. One is we weren't we weren't sure how big the platform needed to be for the acquired business, so this gave us a scaling effect. But also, as we grow as an organization, we didn't want infrastructure to be a a compounding problem in the future. So therefore, creating a capability that could scale up and scale down with the organization. What I'd say another first is that we went through a major transformation of a quite a complex problem, But we did that in fifteen months with a partnership with Amdocs on time, on budget, and keeping our acquisition on track as well. Mason.