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

reports might show is that on a given day 25% of the CDRs are from
Region One and 2% are from Region Two. We could then com-
pare this ratio against the output ratios for the same two regions. If
we find that the ratios vary greatly, we have reason to suspect prob-
lems.

Ratio and distribution analysis between pools (between the input,

output, error, suspense and reject pools) is one source of insight, but
an even more useful type of report compares ratios for a single pool
over extended periods of time.

For example, we might discover that a given region typically repre-

sents 10% of our overall traffic on any given day, and that 20% of its
traffic is typically for SMS.

Network Mediation Postpaid Prepaid Interconnect Roaming Collections Dunning Fraud

I/O
Aging
Error
Reject

Reference Data
Distribution

Table 5.1.1 Monitoring report requirements

By setting up alarms to check on the “normal range of ratios,” we

can quickly develop an early warning system that will tell us when
there is a problem somewhere upstream from the report.

JUDGMENT AND THE HUMAN FACTOR

One simple fact should be clear from all of our discussion about
monitoring reports and how to use them. That fact is, there is really
no way to develop monitoring reports, or any other kinds of reports,
that will definitively flag leakage when it occurs.

What we can do is create reports that arm intelligent and well-trained

revenue assurance analysts with the clues they need to stay on top
of leakage risk situations. By detecting those situations sooner, they
can minimize the losses associated with leakage events.

274