Section 5 : Chapter 1

For example, if we notice that we typically process 100,000 minutes

a day, and for three days in a row the number of minutes going in is
less than 50,000 minutes, there might be a problem somewhere up-
stream of this system in the revenue management chain.

In the same way, if we notice certain batches of CDRs entering the

mediation system are being output at a ratio significantly higher or
lower than the expected 90%, we also have reason to investigate.

Using Aging-, Error-

and Reject-File Reports
I/O reports provide us with an overview of how the overall pro-
cess is working, but aging, error and reject files give us much more
precise information. These reports can also supply us with valuable
information at several levels.

Just the fact that the size of the file has changed dramatically from
the norm tells us that there is a possibility that there is a problem
somewhere in the system.

If the error file has grown especially large, that’s a good indication
there might be a problem somewhere else in the system. (By exam-
ining the records, for example, we might find the same switch has
been producing a large number of records with incorrect code infor-
mation, or we might find that reference information is missing for
some new customers and all their CDRs are being rejected.)

Using Reference-Data Reports

Reference-data reports are useful, not to discover leakage, but for
when potential leakage situations are discovered. They help us
quickly determine if either the lack of, or incorrect, reference data
might be the cause of the problem.

Using Distribution Reports

Distribution reports allow the analyst to do ratio analysis on a pool
of data, based upon different criteria.

For example, distribution reports for a given system could be gen-

erated by region for the input stream and output stream. What the

eXcellence in Telecommunications 273