Roaming Revenue Assurance (RRA) Health Check
21
Roaming Health Check Assuring your Roaming Revenues
-
Upload
xintec -
Category
Technology
-
view
405 -
download
4
description
For most operators, Roaming is an important contributor to overall revenues, sometimes upwards of 30% in certain markets. Although a high-value revenue stream, Roaming is very often excluded from the traditional Revenue Assurance function, and there is no means to fully verify the integrity of inter-Operator billing processes. Some very simple checks and controls can provide the Revenue Assurance Manager and /or Roaming Manager with valuable insight into the invoicing and revenue collections process. Rating and Billing Validation for instance can be implemented in complete independence from the Data Clearing House (DCH) or Financial Clearing House (FCH) for invoice verification purposes. XINTEC strongly recommends a Roaming Health Check, which will provide beautifully simple answers to the following questions: - Are my inbound and outbound TAP and NRTRDE traffic feeds consistent? Am I missing traffic from my TAP feed that is present in the NRTRDE feed or vice versa? - Do my outbound TAP files contain all the inbound roamer traffic present on domestic switch elements? - Am I rating my outbound TAP files correctly thereby collecting the correct revenue from my Roaming Partners? - Am I rating my inbound TAP files correctly thereby collecting the correct revenue from my subscribers? - Are my agreed IOTs being applied correctly in my billing system and are the discounts being applied correctly? - Are my outbound partner invoices being correctly calculated? By integrating your roaming data feeds, invoices and IOTs into the RAevolution Revenue Assurance solution, the recommended XINTEC Roaming Health Check wilprovide answers and clarity to the above questions and enable full Operator access to the reports and results generated by the system.
Transcript of Roaming Revenue Assurance (RRA) Health Check
Roaming Health Check
Assuring your Roaming Revenues
Key Operator Questions
• Is all Inbound traffic being invoiced to our Roaming Partners? Are the right rates applied?
• Do we receive all TAP files for our Outbound traffic?
• Are all our TAP files for Outbound traffic processed in our billing system at the correct rates?
The following slides show a sample report and an output of a Roaming Health Check
The Solution
A focused Roaming Health Check that leverages XINTEC RAevolution to provide checks and controls on Roaming Revenue streams.
A comprehensive reporting capability
• Number of Records in TAP
• Number of Records in NRTRDE
• Matching Records
• Mismatching records on Duration
• Mismatching records on Monetary Value (IOT Validation)
• Mismatching records on Start Time (duration matching)
• Records missing from TAP
• Records missing from NRTRDE
TAP-NRTRDE Reports
• The results of the validations and reconciliations are accessible online
• The reports and the underlying values can be exported in many different formats
TAP-NRTRDE Reports
• NRTRDE vs TAP (All call types)
Result: 88% average overall match
• NRT Voice Originating vs TAP Voice Originating
Result: 86% average overall match
• NRT Voice Terminating vs TAP Voice Terminating
Result: 87% average overall match
• NRT SMS Originating vs TAP SMS Originating
Result: 87% average overall match
• NRT SMS Terminating vs TAP SMS terminating
Result: 80% average overall match
Reconciliations Performed
• An average of 14-15% of mismatches on NRTRDE vs TAP for all call types with Roaming data
• The major contributor of mismatches is Terminating SMS Call Type (difference of ~135k TS records daily)
• Delays in TAP files arriving – to help overcome, re-run reconciliations over the last 7 days, with results progressively getting better over a period of time
• Mismatched investigated – Missing files/CDRs from certain partners
• Consistent VPMNID’s missing TAP/NRTRDE files over time
Reconciliation Results
RAevolution – % Matching
• Example: NRTRDE vs TAP – Reconciliation matches percentage
RAevolution – Record Volume
• NRTRDE and TAP CDR time – Record Volume Summary
Reconciliation Report
RAevolution – Case Study 1 NRTRDE vs TAP Date: 01/05/2014
No. of records in NRTRDE: 159605
No. of records in TAP: 164022
Matching: 139857
Records in NRTRDE not in TAP: 19547
Records in TAP not in NRTRDE: 24114
Recon Match %: 86.4%
Recon Mismatch %: 13.6%
RAevolution – Case Study 1
VPMNID Operator/Country Count
VPMN-ID 1 SAMPLE 7752
VPMN-ID 2 SAMPLE 7513
VPMN-ID 3 SAMPLE 1618
VPMN-ID 4 SAMPLE 1032
VPMN-ID 5 SAMPLE 567
VPMN-ID 6 SAMPLE 531
VPMN-ID 7 SAMPLE 529
VPMN-ID 8 SAMPLE 498
VPMN-ID 9 SAMPLE 407
VPMN-ID 1 SAMPLE 398
NRTRDE vs TAP: Top NRTRDE VPMINIDs with CDRs Missing Date: 01/05/2014
RAevolution – Case Study 2 NRTRDE Voice Originating vs TAP Voice Originating
Date: 01/05/2014
No. of records in NRTRDE: 4507
No. of records in TAP: 5100
Matching: 4065
Records in NRTRDE not in TAP: 339
Records in TAP not in NRTRDE: 932
Recon Match %: 85.5%
Recon Mismatch %: 14.5%
RAevolution – Case Study 3 NRTRDE Voice Terminating vs TAP Voice Terminating
Date: 01/05/2014
No. of records in NRTRDE: 7839
No. of records in TAP: 7851
Matching: 6476
Records in NRTRDE not in TAP: 1251
Records in TAP not in NRTRDE: 1263
Recon Match %: 83.1%
Recon Mismatch %: 16.9%
RAevolution – Case Study 4 NRTRDE SMS Originating vs TAP SMS Originating Date: 01/05/2014
No. of records in NRTRDE: 11697
No. of records in TAP 11632
Matching 10021
Records in NRTRDE not in TAP 1676
Records in TAP not in NRTRDE 1611
Recon Match % 85.9%
Recon Mismatch % 14.1%
RAevolution – Case Study 5 NRTRDE SMS Terminating vs TAP SMS Terminating Date: 01/05/2014
No. of records in NRTRDE: 132852
No. of records in TAP 109092
Matching 91643
Records in NRTRDE not in TAP 41226
Records in TAP not in NRTRDE 17611
Recon Match % 75.7%
Recon Mismatch % 24.3%
RAevolution – Additional Reports
• Additional Reports on Recon Mismatches – Top VPMNID’s
RAevolution – Additional Reports
• Daily Partners Received NRTRDE/TAP files
• Daily Partners Not Received NRTRDE/TAP files
• Large proportion of Roaming traffic for Terminating SMS call records
• Average of 13-14% mismatches across all call types.
• Consistent TAP partners missing: VPMNID-1 , VPMNID-2
• Consistent NRTRDE partners missing: VPMNID-1, VPMNID-2
Please note that the above is just a sample of a more in-depth report we can deliver as part of a Roaming Health Check.
For more detailed info please contact [email protected]
Conclusion
RAevolution can also configure more complex reconciliations and reports to include:
• IOT Validation – performing full re-rating of all inbound and outbound roaming traffic using the agreed IOTs and comparing the results with generated charges in TAP files
• Subscriber database reconciliation – reconciling subscribers databases to ensure consistency in all provisioned roaming services
Additional Reporting Tools
For more information please contact: [email protected]
XINTEC| Whelan House | South County Business Park | Leopardstown | Dublin 18 | Ireland
