Jeepers creepers. My eyes popped out when I reviewed the proposal by Moshe Zolotov of cVidya to include fraud management in the TM Forum’s process map, the eTOM. In short, it gives a process map for fraud management that is the same as the process map for revenue assurance (apart from changing the names on the boxes).
Surely that cannot be right. Are revenue assurance and fraud management the same? I do not think so. I think you cannot take a revenue assurance analyst, ask them to swap desks with a fraud analyst, and expect them to do each other’s jobs. But maybe I am wrong – what do most of you working in RA and Fraud Management teams think? Let me know by commenting here, or else come down to the forum at the TMF and share your thoughts there. Any feedback is welcome!
The data may be the same and from the same sources but the culture and training are very different. Carriers try combining the groups, most divide them again. Alex
I think the difference is in the personality of the individual. Some people are by nature distrustful and can think like a criminal to catch the criminal. Others can\’t get into the mind of the fraudster and that I believe is difference between good fraud analytics and bad fraud analytics.
Sure, the basic operations process and base data are or can be the same and I think this is where the TMForum is coming from. The eTOM view is generic enough to cater for that. Has that approach been successful in churning out successful RA departments? Not that I have seen. The devil is in the detail and we miss many dimensions of this detail.
I think that no its the same but is similar.
Similar in metodology. Both need take a cases or requeriments get analisys & probes, identify root sources and planing actions inmediated for close leaks or faults and define solutions for root sources.
Its diferent because fraud need recopilation of probes fisical, get study of camps, and its focus in persons in many cases with applied laws and action of disuation. RA dont need it.