0% found this document useful (0 votes)
24 views

Objectives For Revenue Assurance Systems Design

This document discusses the process of designing a revenue assurance system. It explains that the first step is identifying what information is available from existing operational systems, as this will influence the design. The second step is gap analysis to determine what additional information is needed. Only after these steps can the process of crafting a revenue assurance solution begin. It provides examples of the types of traffic information that may be needed from the network and billing systems.

Uploaded by

Morad M Swid
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
24 views

Objectives For Revenue Assurance Systems Design

This document discusses the process of designing a revenue assurance system. It explains that the first step is identifying what information is available from existing operational systems, as this will influence the design. The second step is gap analysis to determine what additional information is needed. Only after these steps can the process of crafting a revenue assurance solution begin. It provides examples of the types of traffic information that may be needed from the network and billing systems.

Uploaded by

Morad M Swid
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

T h e Te l c o R e v e n u e A s s u r a n c e H a n d b o o k

traffic volume information from the network environment or need-


ing to know how much CDR traffic is processed by Mediation.

The next step – gap analysis – is more difficult. This is the process
of determining what information is needed that is not readily avail-
able from the operational systems. Gap analysis will identify the
various sources of information that require extra work from the rev-
enue assurance system.

The process of crafting a revenue assurance solution can only come


after identifying what needed information is available from opera-
tional systems.

1. Total minutes of traffic / switch


2. Total minutes into mediation from switches
3. Total minutes from meditation to billing
4. Total minutes billed to customers

Prepaid Roaming
Network Mediation Billing Settlement Reconciliation Reconciliation Collection Dunning

Circuit Call Center Mangement


Mediation Billing Interconnect
Switches Intelligent Customization of CRM System
Mgmt.
System(s) System(s) Network Core Systems Billing System
OSS System
Service Order Mgmt System

Network Service Orders


Inventory Sales and Order Mgmt. and
Management Billing Adjustments
• Order Management System • Call Center Management System
• OSS • Internet Ordering System
• Network Inventory • CRM System
• Billing System • Billing System
Mgmt System
• Point of Sale System • Service Order Management System
• Channel Partner Order Entry System

Figure 6.1.3 Finding total minutes

Objectives for Revenue


Assurance Systems Design
Given this analysis, it is now possible to visualize the design of a
good (or best-practices-based) revenue assurance system. Some
requirements include developing a system that:

334

You might also like