Revenue Assurance ABE

The Revenue Assurance area of the SID provides revenue assurance controls, revenue assurance violations, revenue assurance key performance indicators (KPIs), revenue assurance objectives, and rules that map revenue assurance KPIs and threshold violations to revenue assurance trouble tickets.  Additionally, the scope of Revenue Assurance includes revenue assurance actions/responses that reconcile revenue assurance trouble tickets and bring the trouble tickets to closure.<br/><br/><font color="#e0121d"><b>Revenue Assurance ABE Level 2 Executive Summary</b></font><br/><font color="#29313b">Revenue leakage is considered a cost of doing business in the telecom industry. Revenues are lost due to several reasons such as network provisioning, mediation and CDR errors, billing and interconnect inconsistencies, lost of data and corrupted files, fragmented support systems and manual or fuzzy business processes.  Revenue Assurance research reports estimations are that the degree of exposure varies in the range of the 3% to 15% percent of the carriers’ revenue depending on factors such as services type, geography, carrier type, and RA maturity level.</font><br/><font color="#29313b">The main question for any business is how much leakage is acceptable and how to improve the operations and systems in such a way that minimizes those leakages.  Effective Revenue Assurance (RA) process must ensure the data integrity and synchronization across all the disparate systems and the network itself, in order to ensure operational and financial efficiency.  Such process provides analysis of the relationship between network resources, services, customers, and generated revenue, and will enable the service provider to detect revenue leakage (e.g. un-billed customers, mis-billed customers), stranded assets, and operational inefficiencies.</font><br/><font color="#29313b">In addition, a process management layer is required to allow RA managers and Financial Directors to enjoy the benefits of their achievements, track the revenue leakage identification, quantification and reclamation processes and easily report the results. A big challenge for RA and communications business in general is to move gradually the focus of process management away from resolving and reacting to problems that repeatedly occur, and towards the prevention of problems before they occur.</font><br/><font color="#29313b">The Revenue Assurance area of the SID provides revenue assurance controls, revenue assurance violations, revenue assurance key performance indicators (KPIs), revenue assurance objectives, and rules that map revenue assurance KPIs and threshold violations to revenue assurance trouble tickets.  Additionally, the scope of Revenue Assurance includes revenue assurance actions/responses that reconcile revenue assurance trouble tickets and bring the trouble tickets to closure.</font><br/><font color="#29313b">The Revenue Assurance ABE is a sub-ABE from Enterprise Risk ABE located in the Enterprise Domain.</font><br/><font color="#29313b">The Revenue Assurance Control ABE defines policy-based rules that represent the logical definition of comparisons performed on entities, such as bills and call detail records (CDRs), to identify Revenue Assurance Violations.  The Revenue Assurance Violation ABE models’ discrepancies identified based on applying the rules defined by Revenue Assurance Control entities.  </font><br/><font color="#29313b">Revenue Assurance KPI ABE models KPIs and Revenue Assurance Objectives whose violation trigger Revenue Assurance Trouble Tickets.  KPIs are defined on Revenue Assurance Violations and on other revenue assurance related entities, such as bills and CDRs.  Revenue Assurance Trouble Ticket ABE entities represent trouble tickets opened to resolve one or several causes (for example, Revenue Assurance Violations) that resulted in a Revenue Assurance KPI not meeting a Revenue Assurance Objective.</font><br/><font color="#29313b">Revenue Assurance Action/Response ABE entities represent the result of reconciling Revenue Assurance Trouble Tickets by initiating and performing a series of one or more activities. Revenue Assurance Action/Response ABE entities also model the root cause for Revenue Assurance Trouble Tickets based on rules that trigger root cause analysis.</font><br/><font color="#29313b">Revenue Assurance Assessment ABE entities measure the effectiveness of Revenue Assurance Controls, Revenue Assurance Objectives, and Revenue Assurance KPIs. Revenue Assurance Assessment ABE entities include recommendations of refining controls, objectives, and KPIs.</font><br/>