Closed-loop automation is key to driving new levels of operational performance and efficiency – and delivering better customer experiences. But, it’s dependent on access to accurate sources of information.
Closed-loop automation has become a key focus topic in the telecoms industry, as innovators seek to find ways to automate key processes and to realise the promise predictive problem resolution (in other words, identifying and solving problems before they have any detrimental impact on customer experience), as this insight article from the TMF explains.
From identifying and understanding anomalies to implementing corrective actions via Root Cause Analysis, the TMF is seeking to create a framework that will help the industry create a common approach to the problem. Known as “Closed-loop Anomaly Detection and Resolution Automation” (or CLADRA, for short), the approach promises to bring fresh momentum to cross-industry efforts and help support interoperability.
This is an important step. It also has repercussions for inventory management. The article notes that “Closed-loop automation leverages data to intelligently identify all anomalies in the service path and use AI to map it to find the most likely cause for a particular incident”. The key words here, from our perspective are “service path”. Why?
Well, service path means the entirety of components that are involved in a service, end-to-end. In other words, the resources involved in delivering that service – whether they are physical, logical or virtual. So, to support CLADRA, what you also need is a clear understanding of all network resources and how they correlate with the services, service paths and, of course (since we’re really talking about experience), the customers that consume them.
The collection, aggregation and maintenance of this data is almost a perfect definition of the role of network inventory solutions. Further, this also implies two key roles. First, the collection, as we note, of all such data, into a single repository that is maintained and updated to ensure accuracy. Second, the accessibility of this information to systems that are involved in the CLADRA process – and, indeed, any other process that needs it.
This is of fundamental importance. While CLADRA - and other approaches - offer great promise, they are entirely dependent on ensuring that all loops can be closed, for which data is required. Thus, there needs to be a single repository of network inventory data that can be queried and interrogated, whenever that is necessary.
That’s what CROSS provides. As a consolidated record of all inventory, it provides the correlation of assets and resources that is needed to fuel solutions involved in CLADRA and other activities. It’s accessible via open APIs, so any system that needs this data – whether from the OSS or the BSS can obtain it, when required. As such, it plays a fundamental role in delivering closed-loop operators, automated fault finding and optimised business processes.
So, if you need to find the missing link that can bring your automation efforts together, why not have a chat with our team? We’ll show you how CROSS can be integrated with your systems, to deliver the master view of inventory and resources you need to support your automation efforts and investments.