Project Leader: Gadi Solotorevsky,
TM Forum Staff Support: Debbie Burkett
Project Champions: China Unicom, Mobile TeleSystems, Swisscom, Telstra
Project Member Companies: The Billing College, cVidya, Datamat, Ernst & Young, Logan-Orviss, Microsoft, Revenue Protect, SubexAzure, Tata Consultancy Services, T-Mobile
The Revenue Assurance modeling team addresses standardization in the OSS/BSS space relating to problems of lost revenues and reduced profitability as a consequence of process flaws. Its purpose is to create and maintain an extensible framework and methodology which enables the deployment of an effective Revenue Assurance processes across various activities, processes, systems and network technologies.
The resulting framework serves a wide range of interest from the original group of RA technical practitioners through to business stakeholders looking for best practices and approaches to identifying, addressing and preventing these revenue leakage. The frameworks addresses revenue management issues at the root cause and discusses important concepts regarding network provisioning, mediation and CDR errors, billing and interconnect inconsistencies, loss of data and corrupted files, fragmented support systems and manual or fuzzy business processes.
Current project team objectives include:
• Concentrate activities on how Revenue Assurance can be managed within the context of the existing TMF framework (NGOSS, eTOM, SID and TAM). In particular look to leveraging the existing NGOSS work to create a very powerful process model to drive Revenue Assurance activities.
• Maintain, and update TR131 and GB941
• Specific work targets would include the creation of documents which addresses:
• An extended list of real life examples of typical RA cases related to the RA checklist published in GB941
• A document and tool for assessment of Revenue Assurance maturity based on the Revenue Assurance maturity model published in TR131
• Guidelines for Revenue Assurance RFPs
• Standardization of RA KPIs – and Benchmarking Study
• In addition the team would look at mapping Revenue Assurance into TAM
• Initiate a catalyst project on revenue assurance for the TMW in Nice 2008
• Continue to initiate and take part in catalyst projects to validate the models and the guidelines in various technology environments.
• RA Assurance Benchmarking Study