These Change Management teams are commonly handling thousands of change requests each year, many of which will be Service affecting and Service impacting; from software updates, patches and releases, to configuration changes, and upgrades or replacement of physical hardware these must be managed within an operators business critical processes.
Mistakes, oversight, miscalculations, poor planning and unexpected errors can cause service outage, impairment or frustration for 100s if not 1000s of customers. For most CSPs this has a financial impact; not only do they end up compensating customers, but they lose the faith their customers had in them and they risk the cessation of their service contract.
Requests submitted to Change Management teams must be assessed to determine impact on services to customers. Manually this is a time-consuming task, fraught with risk and complexity and often un-orchestrated behaviour. Risks increase as, in addition to the volume of activities, there is always a volume of intrinsic knowledge and undocumented variations to contend with, alongside all of the documented, well understood business process rules.
Change Management Teams receive high volumes of requests, some of which are highly complex. A Change Management team at capacity through either volumetric pressure, complexity or both are more prone to mistakes. Whether this results in contractual, customer facing issues and obligations not being achieved, or worse still, a failure to meet statutory obligations an operators reputation is always on the line.
Protecting customers from experiencing unexpected disruption or loss of service, or ensuring it met its statutory and regulatory obligations were central to an automation investment.
The customer had a detailed understanding of the automation candidate for CORTEX. It also wanted to layer in improved communication to the correct customers and stakeholders at the correct time. This was is critical.
Importantly, it wanted to minimise unexpected downtime or systems availability for customer impacting Change Requests. Automation was to support its intelligence around any service impacting CR.
CORTEX determined the type and scope of the required change request from the information contained within or attached to the request. This is then correlated with the inventory management system to identify the impacted network components and confirm who the affected customers would be.
Adhering to the organisations defined CR processes, CORTEX could then send the required notifications to relevant departmental contacts and/or customer stakeholders. This was to be fully auditable for governance and compliance reporting.
Under certain conditions, the system should surface a CR for a human to review. For the human-in-the-loop approach to automation the same team would only need to review a small percentage of the CRs, freeing the team to spend more time to complex Change Management deliberations and decisions.
The software increased capacity 600+ days per year, or the equivalent of 3x FTEs.
The aggregated response time handling of Change Requests reduced by 90% so service to the business materially improved.
Our software alone is not the reason why people buy CORTEX, we know what really matters to CSPs. Discover the difference with We Are CORTEX
Deliver business value quickly
I have a long term technology strategy but I need my automation to start delivering quickly and cannot wait for all of the legacy systems.
Hyper scalability for Communication Service Provider operations
We work in a high volume business and our automation tools need to execute at speed and scale out to handle huge volumes of transactions.
Enterprise-grade automation platform
We want to automate business critical operations and we need central controls and governance around our automation estate to avoid citizen-developers running unnecessary risks.
As a dedicated CSP business we deep dive into every area of a CSP, take a look at some of our other use cases here.
Customer billing relies on an extensive underlying infrastructure to monitor, record, maintain data and apply required contractual parameters for accurate billing.
The current IT stack used within the circuit writing process required manual data input leading to inefficiencies.
Manual network fault management on trouble tickets for network infrastructure that were raised from customer complaints, by the operations teams.
The customer wanted to maximise the quality of their international voice network services whilst minimising costs.
Voice Resource Management was a manually performed process, from order to allocation and further provision.
Minimising unexpected downtime or systems availability for customer impacting Change Requests.