Revenue Assurance & Fraud Management Systems

Revenue Assurance Management

Revenue Assurance is the collection of data quality and process improvement methods that reduce leakages, improve profits, revenues and cash flows without influencing demand.

Revenue Assurance is mainly about revenues and profits, revenue assurance activities in a communications organization has significant implications on operational and strategic aspects of the service provider.

These methods can be employed in proactive, active, or reactive manners as part of providing “Revenue Assurance” for the service provider.

RA Control & Configuration should be capable to establish the policies and rules to be applied to the Revenue Assurance process.

It should include base lining acceptable limits and values from which actions will be taken. RA Control & Configuration also assures that the RA process is executing according to specified rules and controls.

RA Correction & Recovery Initiation should provide the necessary functionality to initiate correction of the revenue assurance anomalies as well as recovery of the lost revenue.

Given that Revenue Assurance should detect issues originating in ordering, provisioning, billing, and usage, so Revenue Assurance will only initiate the correction process.

RA Tracking & Management applications should provide necessary functionality to assure that Revenue Assurance anomalies are remedied in an efficient manner. This is done by monitoring the life cycle of revenue assurance activities, including monitoring, analysis, and initiation of correction & recovery.

RA Tracking & Management applications provides necessary functionality to assure that Revenue Assurance problems are assigned, coordinated, and corrected efficiently, escalating as needed per established business rules. Problems are tracked from inception to resolution, including verification

RA Monitoring applications should provide the necessary functionality to collect and monitor data from within fulfillment, assurance, and billing, as well as information from supplier/partner transactions.

This should include data collected from the product, service, and resource (network) layers. RA Monitoring applications also pull data from multiple sources and bash the results.

These applications should analyze processes (both inter-process and intra-process) for RA anomalies.

RA Monitoring should look for situations that are outside of the established baselines and triggers alerts when those situations are detected for further analysis.

RA Monitoring should look for both “immediate” anomalies as well as predicts anomalies via trend analysis, RA Monitoring should also consider proactive measures such as acceptance testing of new or updated products, business or system flows, etc.

RA Reporting should provide the necessary functionality to report on the status of revenue assurance activities and provide management reports.

RA Reporting should provide the functionality to report on the status of Revenue Assurance activities, including the status of issues currently being monitored, analyzed, and remedied. RA Reporting also should report on data derived from the fulfillment, assurance, and billing data collected for monitoring.

RA Analysis should provide the necessary functionality to investigate and diagnose revenue assurance anomalies identified via RA Monitoring. This should include both automated analysis per established RA policies and business rules as well as manual analysis/investigation.

RA Analysis applications should provide necessary functionality to diagnose revenue assurance related problems.

This should involve:-
Categorization and grouping of revenue assurance anomalies
Auto-analysis per established policies and business rules
Assignment of anomalies to work queues for human managed assessments
Use of various analytics tools to support assessment