The ‘IR problem’ is a significant drain on resources. Automation is the only way forward – but how does this work in practice?
The ‘IR problem’ is a significant drain on resources. Automation is the only way forward – but how does this work in practice?
In this, our second in a three-part series of blogs on end-to-end automation of RAEX (Roaming Agreement Exchange) IR.21/IR.85 and the business and roaming revenue opportunities that brings, we will explore the second stage in the IR.21 automation process: Assess (we explore Detect, the first step, and Deploy, the final step, in the other two blogs in this series).
Assess: The second stage of automating the RAEX IR.21 / IR.85 problem
After changes to IR.21 or IR.85 documents have been detected and catalogued, the next step is to assess the impact of those changes. Since changes need to be applied to multiple systems – from the core network to service enabling elements, as well OSS and BSS platforms – this means that the new settings need to be compared to the previous configurations.
But it’s not enough simply to know that x needs to be changed to y – you must also understand how this impacts your service portfolio for your home customers, as well as other roamers you are supporting. This is complex and cannot be overlooked. You need to clearly understand the repercussions.
Until now, the changes needed to be accurately detailed for manual execution by network engineering and IT teams. You also needed to capture a record of these changes for audit and compliance purposes.
With each partner change impacting multiple systems, the complexity quickly becomes obvious. It means that there are numerous challenges in effecting these changes to overcome. Just some of those challenges, which can take days for each update, include:
- Translating validated partner updates into internal network impacts
- ‘Swivel-chair work’ – mapping to many network element types and instances through different systems
- Avoiding service outages due to inaccurate dependency analysis
- And many more
CORTEX Roaming solution for the RAEX IR.21 / IR.85 challenge
In contrast, the We Are CORTEX Evolved Roaming solution enables the impact assessment of all required changed to be automated, so that the final step – Deployment – can proceed smoothly.
This assessment allows you to determine the changes that need to be made in order to implement the updates required in the new IR.21 or IR.85 document. For example, the inventory is queried to determine the current state of affected assets. Similarly, the core network and its associated platforms, as well as EMS / NMS solutions are also checked.
Automation for each change can then be reviewed and checked before handing over key data such as the required network changes to the operations and admin team. All required changes are logged, creating an audit trail and documentary record.
The We Are CORTEX Evolver Roaming solution supports full observability so that, not only can actions be monitored in the network but also the internal state can be compared with the external outputs and conditions ultimately experienced by users and devices.
This comprehensive assessment allows you to manage the workflows associated with each change and to ensure that they can be implemented automatically – once you are satisfied that the changes are acceptable and that you have followed governance procedures. It also captures a complete record of the required changes so that they can be included in audit processes.
Our experience shows that our customers employing the CORTEX Evolved Roaming Solution can cut the Assess stage from a manual process taking days to minutes.
As a result, operators, MNOs and MVNOs can overcome the challenges of managing changes to their crucial RAEX IR.21/IR.85 documents, avoiding the potential impacts and pitfalls of manual processing.
Our automation platform and roaming solution provides:
- Process decoupling
- Reusable automation components
- Integrated change management
- Flexible interfacing
- Minimum viable processes
- Operational safety
Which means that every step of the process for managing changes to IR.21 and IR.85 documents can be automated, with effective governance and oversight at each critical juncture.
An incremental approach to RAEX IR.21 / IR.85 automation
The logic of the We Are CORTEX Evolved Roaming solution is independent of the underlying action – it does not depend on the inputs and outputs but rather the outcomes expected. This means that changes to the underlying network and OSS/BSS footprint can easily be accommodated.
So, automations are preserved as the network evolves because our Evolved Roaming solution is based on reusable ‘process fragments’, which perform specific tasks and can be composed into chains or process flows. Importantly, each is independent of the systems it interacts with.
This flexibility also enables an incremental approach to be adopted, so that you can focus on automating the most important parts of the process first and gradually build out to cover all necessary actions.
The We Are CORTEX Evolved Roaming Solution also enables operators to comply with the requirements of security policies and regulations that impact service providers – for example, NIS-2, the TSA, CRA, DORA and more. Operators can meet internal security benchmarks, while complying with external regulations.
To find out more, download our paper “Evolving IR.21 and IR.85 – what should the right solution look like?” today, or contact us to discuss your needs.
