Firstly, it gathered the alarms coming from the Traffic Management System. These alarms, amongst others, indicate low Network Efficiency Ratio (NER), low Average Call Duration (ACD) and low Answer Seizure Ratio (ASR). False alarms, caused by stutters we ignored or correctly collated for more effective application and analysis.

The CORTEX solution would then gather the call records, for the faulty period, for the specific destination. These records contained all the relevant information from each call, and they were analysed to identify multiple failure scenarios ranging from mass call events to partial and whole route failures, including tight loops and specific route issues. These diagnostics were done by the CORTEX platform at machine speed resulting in a 90% decrease of time compared to the original, largely manual system.

Phase one of the implementation focused on fault identification. Once the fault was identified, the system raised a ticket, adding the relevant information, and the user would manually fix the faults through the Central Routing Engine (CRE).

In Phase two, the user would log onto CORTEX and would be able to approve the mitigation action which the system would automatically implement.

For the Final phase, the faults would be resolved without any user interaction of any kind. This would be a 100% automated solution to the problem.