Overview of Revenue Assurance and Fraud Management Systems

Slides:



Advertisements
Similar presentations
Real-Time Business Assurance
Advertisements

Testing Relational Database
Module 3: Business Information Systems
Risk Management Case Study. agenda Firm Overview Case Study – Risk Management Q&A.
SERVICE MANAGER 9.2 PROBLEM MANAGEMENT TRAINING JUNE 2011.
Divisional Engineer (Mediation and Billing)
Network Instruments Troubleshooting Techniques. What to look for in network monitoring solutions… Key Elements Real Time Statistics Visual Network Traffic.
General Ledger and Reporting System
1 Non-Cash Assets Chapter 9. 2 List the five categories of tangible non-cash misappropriations discussed in this chapter. Discuss the data on non-cash.
© The McGraw-Hill Companies, Inc., 2006 Slide 10-1 Cash and Financial Investments.
Chapter 19: Network Management Business Data Communications, 4e.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 11: Monitoring Server Performance.
1 Output Controls Ensure that system output is not lost, misdirected, or corrupted and that privacy is not violated. Exposures of this sort can cause serious.
Lesson 13-Intrusion Detection. Overview Define the types of Intrusion Detection Systems (IDS). Set up an IDS. Manage an IDS. Understand intrusion prevention.
NetFlow Analyzer Drilldown to the root-QoS Product Overview.
Best Practices – Overview
Chapter 4 IDENTIFYING RISKS AND CONTROLS IN BUSINESS PROCESSES.
Network Management: Accounting and Performance Strategies - Graphically Rich Book Network Management: Accounting and Performance Strategies by Benoit Claise.
McGraw-Hill The McGraw-Hill Companies, Inc., 2000 SNMP Simple Network Management Protocol.
EPayment ePayment Introduction It is the process of electronic transfer of bill data between booking and payment office Department of Post collects.
Client Case Studies Revenue Assurance & Revenue Intelligence.
Service Charging Platform. Converged Billing 0 Account Balance Management 0 Subscription Charges 0 Balance Transfer 0 Charges 0 Limitations 0 Credit Reservation.
CS490D: Introduction to Data Mining Prof. Chris Clifton April 14, 2004 Fraud and Misuse Detection.
Information Management in British Telecom Jon Hill.
The Islamic University of Gaza
Introduction Business Process Fundamentals
Managing the development and purchase of information systems (Part 1)
Information System and Management
Conditions and Terms of Use
OCAN College Access Program Data Submissions Vonetta Woods HEI Analyst, Ohio Board of Regents
Help Service for Consultants & Telecommunication Services Presentation on Revenue Assurance Sana’a-Yemen Tel: Fax:
Mr. Ran Mitra Vice President Intelligent Networks Division New Ways to Generate Profit in a Real-Time Billing Environment.
Module 10: Monitoring ISA Server Overview Monitoring Overview Configuring Alerts Configuring Session Monitoring Configuring Logging Configuring.
Event Management & ITIL V3
EInduction Overview 1 eDropship Post-Induction Process October 6, 2010 MTAC Workgroup 138.
1 Unit 1 Information for management. 2 Introduction Decision-making is the primary role of the management function. The manager’s decision will depend.
Lecturer: Gareth Jones. How does a relational database organise data? What are the principles of a database management system? What are the principal.
ISV Innovation Presented by ISV Innovation Presented by Business Intelligence Fundamentals: Data Cleansing Ola Ekdahl IT Mentors 9/12/08.
Ensuring the Integrity of Financial Information Ensuring the Integrity of Financial Information C H A P T E R 5.
Client: The Boeing Company Contact: Mr. Nick Multari Adviser: Dr. Thomas Daniels Group 6 Steven BromleyJacob Gionet Jon McKeeBrandon Reher.
BUSINESS FUNCTIONS & INFORMATION SYSTEM. What is a System? System is simply a set of components that interact to accomplish some purpose. Business is.
Major Information Flows in the Production Process
CHAPTER 2 TYPES OF BUSINESS INFORMATION SYSTEM. INTRODUCTION Information System support business operations by processing data related to business operation.
Chapter 1 An Introduction to Information Systems
Module 10: Implementing Administrative Templates and Audit Policy.
Telecom Analytics Day III. Detecting Subscriber Fraud... High number of calls to Black Listed numbers High Roaming charges High Internet Usages High number.
-1- Oracle E-Business Suite R12.1 Accounts Receivables Essentials Partner Boot Camp Training Courseware.
Network management Network management refers to the activities, methods, procedures, and tools that pertain to the operation, administration, maintenance,
1 Module: Enviance Glossary Speaking the Same Language.
HEI/OCAN College Access Program Data Submissions.
Regional Telecommunications Workshop on FMRANS 2015 Presentation.
1.Why it is important to study and understand information systems. 2.Distinguish data from information. 3.Name the components of an information system.
WORKSHOP ON ACCREDITATION OF BODIES CERTIFYING MEDICAL DEVICES INT MARKET TOPIC 9 CH 8 ISO MEASUREMENT, ANALYSIS AND IMPROVEMENT INTERNAL AUDITS.
1 Processing Claims and Appealing Decisions Chapter 7 © 2010 The McGraw-Hill Companies, Inc. All rights reserved.
Overview of Revenue Assurance and Fraud Management Systems
Fraud Management Now let us continue and understand fraud management in detail. Let us consider Saurabh’s example to understand the steps followed in fraud.
Chapter 11 Designing Inputs, Outputs, and Controls.
Network management system
Network Management Functions
Information System and Management
Engineering Processes
Data Quality By Suparna Kansakar.
Order-to-Cash (Project-Based Services) Scenario Overview
Revenue Assurance Best Practices & Fraud Management
Order-to-Cash (Project-Based Services) Scenario Overview
Payments, collections and RA
Intrusion Detection Systems
Well Come To Our Presentation Accounting Information System Topic: Report on Revenue Cycle.
Presentation transcript:

Overview of Revenue Assurance and Fraud Management Systems

Revenue Assurance(RA) Increased focus on RA due to Regulatory pressure of reporting revenue Increasing pressure to show more profit Struggle for existing revenue management systems to keep with technological breakthrough(introduction of new network elements in the network) Complex revenue management systems

Revenue Leakage Revenue leakage is the difference between revenue supposed to be earned and the actual revenue (actual cash) realized. Causes of revenue leakage Incomplete customer records Accumulated CDR errors Incorrect rating CDR late to mediation Corrupt CDRs Failure to create CDRs

Possible leakage points Signaling errors on switch System capacity mismatches (Overflow) Misaligned processing or logic rules Failure to activate or provision the customer correctly Failure to track customer activity properly Improper registration and management of network inventory Mediation related Failure to filter records correctly Incorrect application of customer Identifiers Incorrect formatting of CDRs Dropped records Duplicate records Billing related Usage beyond billing stop Incorrect Call plans Billing errors Late billing Over Discounting

Possible leakage points Collections Dunning Related Failure to track old accounts Misapplication of credits Inefficient and ineffective dunning practices Failure to feed back the dunning lessons to Marketing , sales and product planning groups Provisioning and customer service related leakages Physical circuits not ceased when account terminated Over Provisioning Improper update of customer status Provisioning without notification of billing start

RA defined Revenue management Chain: The systems and operations that are concerned with the direct capture ,processing and collection of revenues Revenue Assurance: The process of guaranteeing that the revenue management chain is functioning as specified Or Revenue assurance is a business process to detect ,probe correct revenue leakage, to minimize opportunity loss, to minimize/ avoid costs.

RA- Solution Architecture IN Mediation Third party content Provider CRM Provisioning System PMS Inventory Management System Network Element Postpaid Billing System Interconnect Billing System Subscriber Records Interconnect Usage Records Subscriber Records Payment Records Usage Records Postpaid Subscriber Records Subscriber Records Payment Records Accessory Details Usage Records Configuration Data & Business Rule Content Usage Records Subscriber Order Status Usage Records Rating Configuration Data Configuration Data Postpaid Usage Records Data Capture Layer Adapters Data Capture Others Adapters DC Engine/DC Bus DC Adapter CDR Adapter Profile Adapters DC Repository Analysis Server Analysis Engine Rule Engine Reports Engine Real time KPIs and Alarm

RA Functional Scope The primary scope for RA is mentioned below: Subscriber Profile Verification across Network Element Intelligent Network CRM Post-paid Billing System Usage Verification across Switch Mediation Post-paid Billing Interconnect Billing Third party contents Payment Verification between PMS and Post-paid billing system. Configuration Verification Interconnect billing Call Testing System – to verify rating output of Post-paid Billing System. Configuration of Alarms and KPI Reports

Subscriber Reconciliation Subscriber Instance and Services reconciliation between CRM & Postpaid Billing The Purpose of reconciliation of subscriber records between CRM and Postpaid Billing is   Subscriber Instance reconciliation Identify Subscribers present in CRM and not present in Postpaid Billing Identify Subscribers present in Postpaid Billing and not present in CRM Subscriber Services reconciliation Identify Subscriber services present in CRM and not present in Postpaid Billing Identify Subscriber services present in Postpaid Billing and not present in CRM

Subscriber Reconciliation Subscriber Instance and service reconciliation between Network Element and Postpaid Billing  The Purpose of reconciliation of subscriber instance Network Element and Postpaid Billing is   Subscriber Instance reconciliation Identify Subscribers present in Network Element and not present in Postpaid Billing Identify Subscribers present in Postpaid Billing and not present in Network Element.  Subscriber Services reconciliation Identify Subscriber services present in Network Element and not present in Postpaid Billing Identify Subscriber services present in Postpaid Billing and not present in Network Element.

Subscriber Reconciliation Subscriber Instance and service reconciliation between Network Element and CRM   The Purpose of reconciliation of subscriber instance between Network Element and CRM is Subscriber Instance reconciliation Identify Subscribers present in Network Element and not present in CRM Identify Subscribers present in CRM and not present in Network Element. Subscriber Services reconciliation Identify Subscriber services present in Network Element and not present in CRM Identify Subscriber services present in CRM and not present in Network Element.

Fulfillment of new orders Timely Fulfillment of new orders  The Purpose is to ensure timely fulfillment of new orders without any delay Identify the orders which are failed at provisioning due to some problem Identify the orders which are pending at provisioning

Usage Reconciliation Objective of Usage Reconciliation module is to reduce/remove revenue leakage due to CDRs not transmitted successfully across Network Element to Billing System Usage Reconciliation Between Different Systems Following usage reconciliations are carried out in this module:  Control log level and CDR level reconciliation between Network Element and Mediation Control log level and CDR level reconciliation between Mediation and Postpaid Billing Control log level and CDR level reconciliation between Mediation and Interconnect Billing Rated CDR level reconciliation between Retail Billing and Interconnect Billing xDR level reconciliation between Postpaid Billing and Third Party Content Provider Call type and specific destination wise control Log Level report from Mediation Control Log Level Traffic analysis Control Log level and CDR level Rejected CDR analysis at Mediation, Postpaid billing and Interconnect billing Missing CDR file sequence at Mediation, Postpaid billing and Interconnect billing Aging of rejected CDRs at Postpaid billing Aging of rejected CDRs at Mediation Aging of rejected CDRs at Interconnect Billing  

Usage Reconciliation Control log level and CDR level reconciliation between Network Element and Mediation The Purpose of usage reconciliation between Network Element and Mediation is: Identify discrepancy in CDR count, MoU between files received from Network Element and Mediation through control log reconciliation For selected files, Identify CDRs present in Network Element and not in Mediation Identify CDRs present in both Network Element and Mediation, but have different MoU  

Usage Reconciliation Control log level and CDR level reconciliation between Mediation and Postpaid Billing The Purpose of usage reconciliation between Mediation and Post Paid Billing System is: Identify discrepancy in CDR count, MoU between files received from Mediation and Post Paid Billing System through control log reconciliation For selected files, Identify CDRs present in Mediation and not in Post Paid Billing System Identify CDRs present in both Mediation, and Post Paid Billing System but have different MoU

Usage Reconciliation Control log level and CDR level reconciliation between Mediation and Interconnect Billing   The Purpose of usage reconciliation between Mediation and Interconnect Billing System is: Identify discrepancy in CDR count, MoU between files received from Mediation and Interconnect Billing System through control log reconciliation For selected files, Identify CDRs present in Mediation and not in Interconnect Billing System Identify CDRs present in both Mediation, and Interconnect Billing System but have different MoU

Usage Reconciliation Rated CDR level reconciliation between Retail Billing and Interconnect Billing   The Purpose of Rated CDR reconciliation between Retail Billing and Interconnect Billing System is: For Sample CDRs Identify Rated CDRs for which operator is being paid but subscriber is not charged. Identify Rated CDRs for which subscriber is charged but operator is not being paid.

Usage Reconciliation xDR level reconciliation between Postpaid Billing and Third Party Content Provider The Purpose of xDR reconciliation between Postpaid Billing and Third Party Content Provider is: For sample xDRs Identify xDRs present in Postpaid Billing and not in Third Party Content Provider. Identify xDRs present in Third Party Content Provider and not in Postpaid Billing.  

Reject CDR analysis Control Log level and CDR level Rejected CDR analysis at Mediation, Postpaid billing and Interconnect billing  The Purpose of this module is to identify the CDRs rejected at the Mediation, Postpaid billing and Interconnect billing due to wrong format (addition of new field in the CDR format) or abnormal situation.

Missing CDR files Missing CDR file sequence at Mediation, Postpaid billing and Interconnect billing Purpose  To identify the CDR files Sent by Network Element but missing at Mediation Sent by Mediation but missing at Post Paid Billing System Sent by Mediation but missing at Interconnect Billing System

Payment reconciliation Objective The objective of payment reconciliation module is to reduce/remove revenue leakage due to discrepancies across different system and to achieve this, perform reconciliation/verification of payment information across different systems. Payment reconciliation between Payment Management System (PMS) and Postpaid Billing System  The Purpose of reconciliation of payment records between PMS and Postpaid Billing is Identify payment records present in PMS and not present in Postpaid Billing System Identify payment records present in Postpaid Billing System and not present in PMS Identify payment records having different values in Postpaid Billing System and PMS  

RA Runtime Schedule

Fraud Management system Telecom Fraud Telecommunications fraud is an act of obtaining telecommunication services and/or the instruments, equipment or devices with no intention of paying for them or abuse of services. Fraudsters’ motivation is either to make money or to use services at no or reduced cost or to acquire anonymity to mask criminal activities or obtain the sheer thrill of challenging the telecom’s network security

Fraud Fraud is broadly categories as: Usage Frauds: Frauds that are committed for the purpose of using services without intention of paying for them are categorized under Usage Frauds. Subscription Frauds: Some subscribers obtain subscription for services using false identity with no intent to pay.

Minotaur FMS – Functional Architecture Usage Data Subscriber Data Event Data Server Customer Data Server Partitioning, Filtering, Validation Fraud Detection Engine (FDE) Candidate Fraud Detector & High Usage Detector Rules, Thresholds, Lists, Profiling etc. Case Outcome Server FDE Configuration Manager Suspect Behavior Alert Case History Builder & Internal Alarm Analysis Alarms Collection, Case History Management, Case Outcome Analysis Tickets Case Manager Administration, CM Configuration, Investigation Management Fraud Analyst Reports

Possible Fraud Scenarios Usage Fraud Misuse of another Subscriber’s services Misuse of operator’s services Running unauthorized private exchange Electronic device fraud Security issues Usage data (i.e. EDRs) and usage pattern resulting from any such activities is analyzed by FMS and input data is matched against defined rule conditions and associated thresholds. Any deviation to defined values / rules will generate alarms for the further investigations. There is no limitation on number of rules that can be defined in FMS. As per the requirement user can define any number of rules / thresholds

Fraud Scenarios Subscription Frauds Activation fraud Adjustment in discounts or credits for a subscriber Manipulation of credit limit for a subscriber Change of applicable tariff plan Incorrect application of payments Subscriber data anomalies between Network Elements and Billing Removal of suspensions, adding unauthorized services/lines Fraudulent Subscriptions normally result in very high or abnormal usage of services. This is alerted through usage alarms by setting various rules on usage data as mentioned earlier. FMS has functionality to build and store the profile of subscriber along with billing information. It also stores the profiles previously classified as fraudsters. FMS also evaluates Log files from the various systems (if they would be fed to FMS in required format) like the CRM and Billing for suspect activity as it also profiled user / system level activities

Resolution of Fraud Tickets The Intelligent alarm Analysis (IAA) server, will generate a ticket based on the SBA’s, Behavioral History pertaining to the Services used by the entity and scorecard The Ticket will be passed onto the Case Manager Server, where it is redirected to users with particular roles. Here the type of fraud, priority and workflow is taken into consideration while assigning the tickets The User / Subscriber Analyst with the appropriate role and privilege will accept the ticket and classify it as either a fraudulent case or a non fraudulent one. If the ticket is identified as a non fraudulent one, the User / Subscriber Analyst will close the ticket marking it as a non fraud ticket closure. Here the Case Outcome Server will update the entity profile in the CFD by adaptive feedback to neural models, rules and known fraud case histories. This will help in increasing the accuracy while checking the profile violations against the defined rules.

Resolution The user / subscriber analyst task is to analyze and investigate each case and then make a fraud or non fraud decision. It is general practice to have a set of basic questions which if applied will give the user/analyst an idea of what has occurred and also the ability to quantify the problem being investigated. A checklist of questions would be as follows; Who is the subscriber? New or Old subscriber , Residential, Business or VIP What combination of lines/services are installed Account history – when activated, any bills issued, paid, outstanding, unbilled Subscriber details linked to BSNL employees Any links to previous identified fraud accounts Obtain contracts for further examination Additional call/reverse analysis to identify if subscriber linked to BSNL employee Cross reference known fraudsters database  

Resolution Not Fraud Make a note of the concerns on the FMS, If the usage pattern recurs it should be investigated further Fraud Make a note of the concerns on the FMS, even if finally determined to be non-fraudulent Take appropriate action such as call barring or disconnection, in line with company guidelines Subject fraudulent account to post detection analysis

FMS Run time Schedule

Thank You