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

and there is no reason to expect to duplicate another telco’s leak-

age areas.

Your focus should always be on areas with the largest risk of leak-
age in your own organization.

The Structural Approach to

Deploying Revenue Assurance Systems
Clearly and unequivocally, deployment of a revenue assurance sys-
tem and development of requirements should be based on:
1. An assessment of the firm’s current revenue assurance cov-
erage and identification of the top priority areas – those
with the highest risk of the greatest leakage
2. An assessment of those areas’ operational and organiza-
tional capabilities
3. The deployment of systems, coupled with operational and
organizational adjustments, to truly address the leakage
risk areas in a fundamental way

CRITICAL SUCCESS FACTORS IN

RA SYSTEM DEVELOPMENT
No matter which method is employed to determine the scope of a
proposed system development activity, there are several consider-
ations to keep in mind:

1. It is a Collection
of Capabilities, Not an Application
People who fall into the trap of considering systems and operations
as two separate things end up creating many requirements for a sys-
tem without considering who, what, where, when, how, and why
they will be used. A revenue assurance system fits into the larger
revenue assurance environment, and that fit is critical to its useful-
ness and ultimate success.

324