Category: (5) eTOM Process Type
Process Identifier: 1.6.12.2.3.1
Original Process Identifier:
Maturity Level: 3
This process describes what happens, operationally, after the Fraud / Wholesale Team detected a fraudulent case and handed it over for corrective action
This process describes what happens, operationally, after the Fraud / Wholesale Team detected a fraudulent case and handed it over for corrective action. Revenue Assurance & Fraud Management have internal processes in the Enterprise Management Once a case has been detected, it is not the job of RA or FM to correct, it. ( Separation of audit and operations). Revenue Assurance & Fraud Management would hand it back to applicable teams in the business to correct/address the matter. This process describes what happens after the Fraud / Wholesale Team detected a fraudulent case. The falsification of records by telephone carriers between one another, in order to deliberately miscalculate the money owed by one telephone network to another. It also includes possible triggers to Fraud Management, i.e. the prevalence of Anti-Tromboning Revenue Assurance & Fraud Management would normally hand it back to 1) the Operational Team responsible for Wholesale to fix it (to avoid a conflict of interest) (i.e. a Operations Defect). 2) Sometimes its handed back to Development (i.e. a Development Defect)or 3) To Product management (i.e. a Product Management Defect) to correct. How Operations/Dev/Product Management handles it is where there is major difference between retail and wholesale: In Wholesale, such fraud detection is not against a single individual but against a Legal entity, (see the case of Route Quality Blending), hence there must be clear workflows to determine the next step of action (reporting, negotiation. For the latter/ Wholesale billing the operations people have to take a number of steps, and this is what is described in those processes.
This was created from the Frameworx 16.0 Model