Data-Driven Transformation in Telco Operators | White Paper | Polystar
The Telecom Industry is facing a deep transformation. Read about the CSP status, as well as the drivers for transformation. Download here
Telco automation is proceeding at different rates, and it’s not just a journey in technology. Here, we explore the state of automation.
Telco automation is proceeding at different rates – but it’s not just a journey in technology; there are other factors to consider. In this article, Thomas Nilsson explores the state of automation – and points to key breakthroughs that can help operators make critical leaps to the next level of the automation ladder.
If the telecoms industry is agreed that automation is the destination of travel and that the TMF has provided a roadmap to help us get there, then it’s also equally united in acknowledging the fact that every operator’s situation is different. As a result, despite the ambitions of some, in reality, we’re all moving at a different pace towards that goal.
This is a view we’ve confirmed through conversations with the analyst community – for example, STL partners has noted strong public commitments that a number of operators have made to reaching Level 4 on the TMF’s automation maturity model in a defined timeframe, while pointing out that others have been less publicly ambitious.
A key reason for this difference could be, they note, because these ambitions must also be seen against the recognition that this journey isn’t just about technology.
In practice, organizational and governmental changes are also required. One issue is that technical and organizational changes may not be completely aligned at present, which would account for some major differences in the rates of adoption.
Ensuring alignment is clearly essential. This is particularly important to avoid new gaps opening as leaders surge ahead, while others are still seeking the right path to begin their journey.
STL reckons one way for operators to take these first steps is by testing the water with smaller and simpler projects. These provide opportunities to determine the tech investment and requirements, while also exploring how these can be balanced by the necessary organizational changes. By focusing on very specific candidates for automation, it may be easier to ensure that all stakeholders are on the same page.
Thomas Nilsson, CPO at Polystar
At the same time, the vision – the aspiration – needs to be clearly articulated. This requires cross-functional teams, training, and overarching governance – to ensure that the organization can flex to adopt the new ways of operating via a growing footprint of automation.
All of which makes sense, but it’s important to remember that operators will continue to move at different rates and that it will take time for each to move up the automation maturity curve.
So, what we have is a very mixed landscape – but, nevertheless, there are promising signs, and we do have a unified vision. The question is, how can we help operators that have yet to cement their plans to move forwards?
Well, there are clearly obstacles to overcome between each maturity level. You can accomplish a great deal to achieve, say, Level 1, but there’s a threshold that you need to pass before you can begin the work required at the next. We think that there are two key thresholds that need to be crossed.
Specifically, we’re focused on moving from Level 1 to Level 2, and from Level 3 to Level 4. Both points provide clear demarcation and boundaries: reaching each demonstrates real and substantial progress towards autonomous networks and important transition points. But how do we pass these thresholds?
At the same time, the vision – the aspiration – needs to be clearly articulated. This requires cross-functional teams, training, and overarching governance – to ensure that the organization can flex to adopt the new ways of operating via a growing footprint of automation.
All of which makes sense, but it’s important to remember that operators will continue to move at different rates and that it will take time for each to move up the automation maturity curve.
So, what we have is a very mixed landscape – but, nevertheless, there are promising signs, and we do have a unified vision. The question is, how can we help operators that have yet to cement their plans to move forwards?
Well, there are clearly obstacles to overcome between each maturity level. You can accomplish a great deal to achieve, say, Level 1, but there’s a threshold that you need to pass before you can begin the work required at the next. We think that there are two key thresholds that need to be crossed.
Specifically, we’re focused on moving from Level 1 to Level 2, and from Level 3 to Level 4. Both points provide clear demarcation and boundaries: reaching each demonstrates real and substantial progress towards autonomous networks and important transition points. But how do we pass these thresholds?
The first breakthrough is data. Building a data strategy and getting it right takes effort – but the effort pays off, because understanding how data can be sorted, managed and made accessible is key to enabling the automation required at Level 2.
Because data is so fundamental, it crosses all domains and departments – which means that the data strategy, must, pace STL, encompass the necessary governance that will be required for further progress.
With respect to the data strategy, this requires an understanding of the availability and accessibility of data before it can be consolidated or triaged into a source that can be used across domains. It also requires – and here’s a governance issue – a clear understanding of the sovereignty rules in place, as well as alignment with international data protection requirements, such as the GDPR.
Learn more about data availability and accessibility in the previous article Data-driven operations
The first breakthrough is data. Building a data strategy and getting it right takes effort – but the effort pays off, because understanding how data can be sorted, managed and made accessible is key to enabling the automation required at Level 2.
Because data is so fundamental, it crosses all domains and departments – which means that the data strategy, must, pace STL, encompass the necessary governance that will be required for further progress.
With respect to the data strategy, this requires an understanding of the availability and accessibility of data before it can be consolidated or triaged into a source that can be used across domains. It also requires – and here’s a governance issue – a clear understanding of the sovereignty rules in place, as well as alignment with international data protection requirements, such as the GDPR.
Learn more about data availability and accessibility in the previous article Data-driven operations
But, securing both the data strategy and the necessary governance provides the foundation of what’s needed for the next leap – AI/ML. While many automations can be secured, based on small projects and the right access to the right sources of data, longer term, AI and ML are required because autonomous decisions mean that conditional alternatives must be considered, together with the context. Rule based data-driven automation isn’t sufficient to break through that barrier; AI and ML become necessary by default.
To make this transition and pave the way for Level 4 operations, not only do we have to choose the right AI / ML adoption and implementation strategy, but we also have to consider regulations (which are a moving target), as well as the maturity of the solutions under consideration – again, governance goes hand-in-hand with technical evaluations and deployments.
To support operators on this journey — regardless of where they sit in the maturity model — we’ve created a practical checklist that helps them to identify automation use cases that would benefit from AI and ML – reflecting the earlier suggestion that operators choose specific projects that can act as springboards for the wider spread of automation.
But, securing both the data strategy and the necessary governance provides the foundation of what’s needed for the next leap – AI/ML. While many automations can be secured, based on small projects and the right access to the right sources of data, longer term, AI and ML are required because autonomous decisions mean that conditional alternatives must be considered, together with the context. Rule based data-driven automation isn’t sufficient to break through that barrier; AI and ML become necessary by default.
To make this transition and pave the way for Level 4 operations, not only do we have to choose the right AI / ML adoption and implementation strategy, but we also have to consider regulations (which are a moving target), as well as the maturity of the solutions under consideration – again, governance goes hand-in-hand with technical evaluations and deployments.
To support operators on this journey — regardless of where they sit in the maturity model — we’ve created a practical checklist that helps them to identify automation use cases that would benefit from AI and ML – reflecting the earlier suggestion that operators choose specific projects that can act as springboards for the wider spread of automation.
It ensures alignment both between the technology required, as well as the internal governance needed. For example, identifying the team that will tackle the expected use case and the executive champion that will spearhead this in the organization, are critical success factors.
So, yes, there have indeed been bold commitments from the operator community – but there is a clear pathway for any operator to leverage automation in their business and to climb the maturity ladder in a way that fits their organization and needs.
We can show you how to start that journey and to make further steps up the maturity ladder. Read more about our solutions to learn more: