RA Tools Overview

It is difficult to get a good, honest overview of revenue assurance tools. Vendors tell you about the tools they offer, not the tools they do not offer. Have you ever noticed how every year their product offerings get broader and broader, yet they never said there were gaps in the offering the year before? ;) Consultants always play safe and tell you about the state of tools three years ago, so telcos do not try something new and blame the consultants when it does not work. Of course, the three-year-old tools might not work either, but that is a different problem. And nobody talks about the niche tools provided by niche providers (except the niche providers, of course) although these may be better suited to the needs of some customers than the multi-purpose offerings pushed by more mainstream suppliers. Well, if you want some advice on how to go about negotiating the minefield of automating revenue assurance, you came to the right place. I have just added a new presentation about revenue assurance tools to the site. Take a look at it on the downloads page. It identifies two possible goals for automation: improved detection (what most vendors talk about), and improved correction (which most vendors conveniently forget to mention). Then the presentation recaps on the Four C's that form the basis for all processing and hence is the subject matter for all revenue assurance, and explains the types of tools suitable for detecting errors within each of the Four C's. Finally, the SPIRIT mnemonic is introduced, giving the six golden rules that should be followed by any telco before it starts deploying new tools. If you want to find out more, look here.

Always Cutting Costs...

Is ECtel, the Israeli vendor of RA and FMS software, cutting costs a little too far? Vendors should be careful with their money. It is good for their business and creates the right impression with customers. But I got an anonymous tip-off that indicates ECtel should think about increasing the amount they spend on software. Take a look at this PDF document on ECtel's website. It is a short list of abbreviations that supplements a letter of warranty from HP Israel. If you scroll to the bottom, you can see a tell-tale sign of doing things on the cheap: an advert for trial version software used to create the PDF file. By not buying the latest PDF-writing software from Adobe, I guess ECtel can argue they saved about US$300 of their investors' money ;)

Revenue Assurance Trademarked?

Here is a surprising revelation. It turns out one company has trademarked Revenue Assurance which I guess is conclusive proof that intellectual property can be utterly daft and meaningless. Which company do you think has nabbed the phrase for itself? Judging from this press release (look at the bottom), it is IneoQuest, Massachusetts supplier of specialized products for video quality management. Who would have thought it?

Razorsight: New Software, Same Old Values

Why do people still bother writing those corporate statements of values? Enron must have had one. Worldcom had one. The Mafia must have one. It probably says something about not discriminating between victims based on race, religion or sex, and that they support strong family values with in-house marriage counseling services and flexible working hours. It was with some bemusement that I read the recent press release from Razorsight, the revenue and cost optimization vendor headquartered in Virginia, USA. It tells you all about how they have lots of great new versions of their software, and makes no mention of the US$4.5m fine and court order that forced them to remove the bits they stole from rival TEOCO. Hey, but I guess nobody pays anyone at Razorsight to tell the unpleasant truth of how they do business. Then again, nobody pays me to do it either, but I do it anyway. It must have something to do with my values, though I have never bothered to come up with some silly list as if that proved anything. Anyhow, as I was looking at Razorshite's website I noticed that they also claim to have corporate values; read them here. These are a few that caught my eye:

  • Drive for excellence and take pride in everything you do - were they proud of how they handled themselves in court, as they admitted their wrongdoing?
  • Commit to winning with integrity and to following the highest standards of ethics and professionalism - erm... does that mean they have told their current and prospective customers all of the reasons why they had to change their software, and maybe even do something that shows they intend to follow their stated values, and are not just paying lip-service to them?
  • Be flexible, learn from experience and tackle challenges with fervor - so what have they learned from the experience of having been caught stealing? Will they share those learning experiences with us, and set a better example for others?
  • Crush our competition through unparalleled teamwork - CRUSH the competition!!?!? Who wrote this - Borat?
  • Take time to laugh; don’t take yourself too seriously - great! That means nobody should get upset because I had a little fun... ;)

AT&T Award For ATS Employees

US revenue assurance vendor Advanced Technologies & Services (ATS) will be particularly proud of a couple of their employees this week. Paul Gilbert and Lee Helwig of ATS have received Outstanding Performance and Contribution awards from AT&T. AT&T uses the SimCall product supplied by ATS. You can read the press release here.

cVidya Slights AT&T, ECtel and Subex

Last week I blogged that cVidya and BT had won this year's World BSS Award for revenue assurance. The award has doubtless boosted egos at cVidya, but perhaps the effects have gone too far. Since the award was announced, cVidya has managed to find reasons to subtly, but publicly, denigrate two of its larger competitors and one very large telco.

On June 15, cVidya's Chief Scientist, Dr. Gadi Solotorevsky, blogged about the settlement of a class action law suit about third party services billed by AT&T. According to the news story, the same kind of law suit has been filed with all the other big mobile providers in the US, but AT&T is the first to settle. Per the details of the settlement, the refunds to customers will be modest. For example, the settlement covers customers between 2004 and 2008, but no more than 3 months of third party subscription charges will be refunded. The case looks pretty simple to me. Third party providers used unscrupulous tactics to get customers to sign up for services without making it clear how much they cost. They used the same tactics with all US mobile providers. Many customers who got suckered spotted the unexpected costs on their bills and complained. AT&T, for one, gave refunds to customers who complained. Lawyers spied the opportunity to make some money, by suing on behalf of all customers charged for those third party services, and not just the ones who complained. AT&T, wanting to protect its reputation, opted for a reasonable settlement instead of fighting the law suit and appearing unsympathetic to the customers who had been swindled. Solotorevsky, in his blog, drew the following conclusions about AT&T and its approach to revenue assurance and risk management:

Now AT&T acknowledges the problem, do their existing mechanisms permit to discover which customers where unjustly charged, and if not, what mechanisms are needed? It seems that AT&T will wait until the individual customers complaints. Is this approach something that regulation can permit in the long run?...

...Don’t $4.3 million to the plaintiffs’ lawyers + whatever payments (which I assume will be higher) to the customers + the cost of handling all the individual claims justify some investment in RA tools, and proactive RA methodologies, to prevent such things from happening?...

...Content is out there and it is a mayor [sic] opportunity for SPs. Just supplying it without taking appropriate practices is a mayor [sic] risk – it is the SPs responsibility to mitigate the risks, to really enjoy the fruits of the content revolution.

I think this criticism goes too far. Solotorevksy is saying that not only AT&T, but also the businesses supplying AT&T with revenue assurance and risk management tools and advice have done too little. That is a bold assertion to make about a large publicly-listed company in the country which is home to the Sarbanes-Oxley act and all that entails about internal controls. To begin with, to say that AT&T now acknowledges the problem implies they did not acknowledge it before. The settlement, however, is not an admission of wrongdoing by AT&T. Because AT&T has given refunds to those customers that complained directly, we know AT&T has already acknowledged third party misinformation is a genuine issue. The obligation asked of AT&T by Solotorevksy, that it have mechanisms to discover who has been unjustly charged, would be onerous. A customer is unjustly charged if the customer was misinformed about costs. But what kind of mechanism, other than reviewing all the marketing output of third parties, would allow AT&T to identify when third parties misinform their customers? Even if AT&T realizes, as a result of complaints, that third parties provided inadequate information in general, it does not follow that they should be able to identify which customers have been unjustly charged. To do that, you would need to identify which specific customers had been misinformed. That is the same as knowing what had been communicated to each individual customer. A customer that gets inadequate information through one channel may have also obtained adequate information about costs through another. How would AT&T be able to tell which customers were adequately informed from those that were not? To do so would be impractical. The best option is the option that AT&T has taken, which is to assume that all customers who either complain or who sign up to compensation via this law suit were misinformed. It also, fairly and reasonably, has established that customers have some responsibility for checking their own bills and taking steps to protect their own interests, which is why the subscription refunds will cover no more than three months of payments, no matter how long the third party subscription charges were levied in practice.

There is no doubt that AT&T would rather avoid the cost of legal fees, handling complaints, and refunding customers. That does not justify a conclusion that extra investment in revenue assurance would have enabled AT&T to avoid these costs this time. It is definitely a step too far to blame inadequate revenue assurance tools. I cannot imagine what kind of tool would even be relevant. This issue is about the customer’s understanding of the services they signed up for, and of the charges they will pay for them. I usually cite these kinds of issues as proof that tools are not the solution to all revenue assurance problems, despite the over-zealous way that revenue assurance developers try to pretend that software solves every problem. No tool is going to tell you if a customer understands or misunderstands something, or if the blame belongs with how the information was communicated or with the customer for failing to read or listen properly. A reconciliation will not help you determine if a human being was tricked, or whether they simply made a mistake. The right to complain does not imply every complaint is justified. A proactive review of information to be provided to customers does help to mitigate the risk of misunderstandings, but it is not clear what responsibility a network provider could and should take over the information or misinformation given out by third parties. Clearly the primary responsibility for clear communication is with the third party, and networks should be reluctant to adopt any universal obligation to protect customers from the improper behavior of companies outside of their control. Even if the network tries to review the marketing practices of third parties, and seeks to approve them before signing up a third party supplier, an unscrupulous third party could always vary the content afterwards, or try to deceive the network about what it says to customers and what it does not say to customers. I really think AT&T deserves an apology about the implication that it may have supplied third party content without taking appropriate steps to mitigate the risk to themselves and to their customers.

This cVidya blog draws an unwarranted conclusion about the investment made by AT&T in its revenue assurance tools. I do not think it is fair to conclude that AT&T has made an inadequate investment in revenue assurance, and in revenue assurance tools in particular, just because of the decision to reach a settlement of this law suit. There are some things that are bigger than revenue assurance, like reputation. A business needs to defend its reputation even when the threat to its reputation is not justified by any wrong-doing or failure on its part. The timing of cVidya's criticism of AT&T is especially peculiar. Last week BT and cVidya won the prize for best revenue assurance project in the World BSS Awards. The runners-up were AT&T and ECtel. ECtel, like cVidya, are an Israeli revenue assurance business. By implication, if AT&T's tools are inadequate, either ECtel has provided them with inadequate tools, or AT&T simply has not purchased enough of the right tools. Either way, I think cVidya should be more careful about statements that could be interpreted as slurs about the quality and adequacy of work performed by their professional peers and competitors.

The next day, cVidya's press release made it clear how proud they were to be co-winners of this years award for best revenue assurance project. In the press release they stated:

cVidya was awarded this recognition for deploying its MoneyMap®/Configuration and MoneyMap®/ Rating and Billing Verification solution within the RA Center of Excellence at the British Telecom group, demonstrating a strategic and comprehensive RA program covering all business units of BT, and handling both the business aspects and the operational day-to-day challenges of Revenue Assurance.

This looks like a very deliberate snub of Subex and any other revenue assurance vendors that cVidya must know has supplied the various business units in BT. The press release encourages the reader to believe that cVidya's products are used to provide comprehensive revenue assurance across all units. However, it was only in January of this year that BT Global - one of those BT units - signed a multi-million dollar deal to deploy a Subex revenue assurance bureau. See the press release here. It is reasonable to expect some exaggeration when businesses market their products, but exaggeration can go too far. Either cVidya's solutions in BT are comprehensive, or they are not. If they are comprehensive, then there would be no need for rival vendors to supply individual BT units with additional revenue assurance solutions. If they are not comprehensive, then cVidya should avoid using language that implies they are. Snubbing rival vendors might seem like a good idea, until you realize you must also be snubbing the people in BT who signed those deals and work with the rival vendors. If you really want a strategic and comprehensive revenue assurance program, you have to work with your colleagues, not badmouth them. The irony here is that cVidya is guilty of some dubious marketing the day after it chastises AT&T for not doing enough to prevent and address misleading marketing.

Perhaps cVidya is only guilty of some careless language. Even so, if I was in AT&T, ECtel or Subex, I do not think I would be feeling too complementary towards cVidya right now. cVidya needs to draw a line, in public, between fairly promoting its own products and being disrespectful to its rivals and the people in operators who decide to buy rival products. It would be generous to say that these recent cVidya comments sit on that line, if they do not cross over it. Insulting rivals at least is understandable. Criticizing potential customers is not. cVidya and Solotorevsky have played an admirable role in supporting RA in the industry, particularly through the TM Forum, but they risk going too far and making it hard for rival telcos and vendors to collaborate with them in future. The RA industry is small, and it employs some very thin-skinned people with long memories (as I have learned the hard way!) so you never know when relationships will be reversed, giving old enemies an opportunity for payback. Being an independent consultant, I say what I think, safe in the knowledge that ultimately, I will never be able to please everyone. I need to give useful advice, and that advice cannot always be positive about all things at all times. cVidya is vying to be a global supplier that has to keep its investors happy by making big sales all over the world. cVidya do not have that luxury to slight potential customers by saying they have made bad choices by not buying enough tools, or by buying the wrong tools. What goes around, comes around. Perhaps cVidya should spend a little more time analyzing their own performance, whether it wins awards or not. They can start by taking a look at my recent blog about the leakage I noticed on my own BT bill... ;)

BSS Survey

Since 2000, Hugh Roberts has compiled a short but revealing annual survey into BSS attitudes, which he runs in parallel to managing the World BSS Awards. It is that time of year again, and having had a sneak peak at the early results, it looks like they will once again be a useful indicator of what the future holds for BSS. Amongst the twelve questions are a few dedicated to revenue assurance. All the questions are relevant to revenue assurance practitioners, because they point the way to how BSS will change in future, and hence the challenges to be faced by revenue assurance. Anyone who takes part in the survey will get to see the results. That is a good return for spending a few minutes answering a dozen quick multiple-choice questions. To take part, you can either:

The closing date for entries is the end of June.

Who Is Best At Revenue Assurance?

On Tuesday I was in Amsterdam, in a glorious old building, hosting a training session on revenue assurance maturity at BIMS 2008. I talked for 2 hours straight after lunch, with the hot sun beating on the curtains to the darkened room, but everybody managed to stay awake. That counts as a success. During the session, we had some very interesting debates about how difficult it would be to reach the top level of maturity, and I pointed out that we had not seen anyone reach the top level, at least not per the TMF's version of the maturity model (I have no interest in other so-called maturity models, which seem to be based around the idea that if you buy tools X, Y and Z you get to instantly reach the top level of maturity and remain there ever afterwards - even if your people do not know how to use the tools, or even if the tools are irrelevant to your business model!). The point, of course, it to construct a model that gets proportionately harder as you keep going up. Improving maturity is like climbing a mountain. The slopes get steeper and the oxygen is thinner as you go up, slowing the progress of even the best climbers. As you go higher, there is also more and more risk that hazards, bad luck or an accident will force you to go back down again. There should be at least the same degree of difficulty for an experienced telco to go from the penultimate to the ultimate level of maturity as there is for an inexperienced telco to move off the bottom level. In fact, it should be harder to reach the top. A telco at the bottom should find it easy to buy experience and copy what other companies have done. At the very top, you cannot buy experience because there is no relevant experience on the market, and the best results will never be delivered by copying another business, as all businesses will have unique challenges. I know that is a tough message that some audiences may not want to hear: in the real world, many have to satisfy bosses who only want to hear if they are the best and do not want to hear that there is a big difference between good and best. However, I was heartened that my group agreed about the importance of increasing the difficulty of the next challenge that follows each success.

After the session, I too was succumbing to the heat. I had taken an early morning flight into Amsterdam, and my tiredness started to catch up on me. I sat in a couple of very interesting presentations but when they finished I found it hard to get to my feet and get into the mood for some hobnobbing on the exhibition floor. Fortunately for me, as I shuffled my away across the building, I spied Eli “The Craic” Krakauer of cVidya, sneaking his way into the building. Sneaking is the right word - he was wearing jogging sneakers that looked a little incongruous with his suit. Eli explained it was because somebody had stood on his foot the day before, though I suspect the real reason is that they allow him to stealthily creep up on his competitors and listen to what promises they are making. Eli is an entertaining character, and always full of gossip (none of which I can share here, I am sorry to say). He must have done all of his sales rounds for the day, because we amiably chatted whilst waiting to hear the big news of the day: the announcement of the winners of the World BSS Awards, and of the revenue assurance award in particular. Although cVidya were nominated, from the look of Eli's sneakers, I assumed that cVidya were not in the running. How wrong I was! I found myself straightening Eli's tie and looking after his bags whilst he collected the award for the best revenue assurance project on behalf of BT and cVidya.

One of the reasons for being genuinely surprised at the announcement was that BT had won the same award last year. That suggests they must really have impressed the judges to win the same award two years running. Does this justify the conclusion that BT are world leaders in revenue assurance? They have certainly been doing it long enough. One old Gartner report refers to a revenue assurance project run by BT Wholesale in 1991. Given that the broad thrust of the current BT/cVidya project is centred on BT's Wholesale division, you might wonder if the prize has been given to the business which has made the most progress over the longest time or the business which reports doing the same thing over and over ;) You could spin an argument that BT revenue assurance has sucked in skills from other UK telcos, and hence turn this into an argument that the UK is the worldwide center of excellence for revenue assurance. There are ways to bolster the argument that the UK sets the pace in revenue assurance. For example, the award nominess included UK multiplay provider Carphone Warehouse, and the 2005 joint award winners Azure were a British firm spun out of BT and since bought by Subex. Even those clowns at US-based GRAPA have a strong British bias, with 3 Brits represented on its 7-strong executive committee. What a shame that they have no influence over the Mattison clan who make all the decisions for GRAPA...

Israelis might reasonably counter that they, as a nation, are world leaders in revenue assurance. Not only did Tel Aviv-based cVidya share in this year's first prize, but Rosh Ha’ayin-based ECtel finished second in collaboration with AT&T. But the location of suppliers in global markets will be determined by costs as well as availability of skills, so this is not a totally reliable guide. Measures of leakage are not a reliable guide, because people have reasons to exaggerate their leakage in both directions, and no part of the world appears to be performing all that much better than any other part of the world. Maturity assessments might be a better guide, though I noted with disappointment during my tutorial the evidence that telcos tended to borrow from the TMF's maturity assessment the parts they liked, and ignore the parts they did not like. That might lead to high maturity scores, but anyone can score high if they only measure themselves in the most flattering way possible. From my own experience, I am aware of two telcos that may be on the verge of achieving the highest level of maturity, but part of the reason why they are doing so well is that they are keenly focused on doing the work, and not so focused on promoting themselves. That means that their successes may be less likely to attract awards and plaudits than other telcos...

Of course, my initial question is silly. There is no way to tell who is best, or even to agree what we mean when we talk about the best in revenue assurance. The judges at the World BSS Awards have to rely on the honesty of the people who apply for awards. As soon as you do that, you move away from a completely fair determination of who is best to a subjective appraisal of who told the most uplifting story, even if it is not entirely true. The judges will need to agree what is best between themselves, but best will mean different things to different people. Road safety is a good analogy to revenue assurance, as both exhibit many attitudes to risk and how it should be mitigated. One driver will think of road safety in terms of driving a Volvo, with impact-resistant bars around the cabin and many airbags to protect them in the event of a crash. Another will think in terms of the better design of roads, by straightening bends and using road signs. Another will think in terms of laws and police enforcement to punish bad drivers and remove them from the road. Another will just drive slowly and carefully. What is best in revenue assurance depends on your attitude to risk. Many revenue assurance vendors sell the metaphorical equivalent of seatbelts and airbags - tools to protect you and cushion the blow after an accident has taken place, but which do nothing to reduce the risk of an accident in the first place. Some telcos place the onus on employees in their business to take care and avoid mistakes, but lack the rules and police to encourage and enforce policies designed to reduce risk. Consultants may point out some ways to straighten roads - by eliminating needless complexity in processes - but whilst these improvements may reduce black spots for leakage, they may do nothing to improve the design of data highways in the long run. There is no single best attitude to risk, because some telcos will desire more risk and others less, and both may have perfectly valid reasons for their attitude to risk. What the maturity model tells us is that however the risks are managed and mitigated, there has to be an appreciation of the balance of proactive and reactive techniques available, with decisions driven by the most effective ways to serve the telco's interests and fine-tuning of risk management based on results so far. Sometimes that will lead to investment in more alarms and airbags, sometimes it will promote straighter roads and better processes, sometimes it will increase the authority to police and enforce rules. The balance must be set differently for each company. To get the optimal balance, all risk mitigation strategies must be considered and explored and used together. Those telcos that can see revenue assurance in the context of overall risk management will be the ones deserving to be called best. In Amsterdam, I saw some signs that the real leaders in telcos do appreciate this. In future years I hope we see some of them standing on the podium and collecting the awards they will deserve.

Adserve Assurance

When you browse the internet, the adverts you see are often delivered from dedicated advert servers. The idea is that you get a constant rotation of the messages on these virtual billboards, and the adverts can be tailored to reflect an individual's supposed interests. We are still at the early days of sophistication when it comes to profiling users. As a result, the rules used will be relatively simple right now, but will get more complicated over time. We all know that the risk of mistakes goes up as rules get more complicated. Yet mistakes happen already. Just now, one very mainstream English-language site served me an advert written in Swedish that pointed to a Swedish website. Of course, this advert is going to be ineffectual. It is the wrong advert for me, and presenting it to me is a wasted opportunity (although I admit that, in this case, I still clicked through!) In turn, the Swedes paying for the ad may not be getting good value for money if delivery is too random. This spells out a need for adserve assurance - the assurance that internet adverts are delivered to the correct and intended audience. To me, that sounds like a potential new growth area for revenue assurance.

It Is Not What You Know...

The inspiration for today's post comes from “D” in Israel... someone who wisely prefers to remain anonymous. The latest press release from cVidya prompted D to observe:

"cVidya Networks finalizes a managed services project for a tier 1 operator in Asia. The project resulted in reduction of 90% in leakage within the first 3 months."

If cVidya is so good and diligent and many other fine adjectives...and knows the amount of leakage the customer is experiencing, why stop at 90%...?

Good question! But I do not suppose we will ever hear the answer ;) To be fair to cVidya, the same comment can be made about their rivals too. The only way to know the total value of leakage for certain (and hence be able to calculate what percentage you have saved) would be to run perfect systems and processes end-to-end, and compare the results to those you get with the current imperfect systems and processes. Any differences in the results can then be assumed to be due to the errors and leakages in the imperfect systems and processes. But then, how would you know your ‘perfect’ systems and processes really are perfect, unless you compare them to another series of perfect systems and processes... and how do you know those systems and processes are perfect unless you compare them to perfect systems and processes... and so on....

Really, this problem is philosophical. It is about the boundaries of knowledge. Some things cannot be known with certainty, such as the total value of leakage and hence the percentage impact of something we do to reduce it. The problem comes down to what Donald Rumsfeld famously called the known knowns, the known unknowns, and the unknown unknowns. The history of revenue assurance shows us that leakage often lurks in the unknown unknowns, the areas that are not just lacking control, but where we did not even anticipate the need for control. More importantly, no matter how confident we are about the quality of our work, we should always be ready to believe that there may be some unknown unknowns - places outside the boundaries of your visibility where things go wrong that you have not anticipated. For example, I recently discovered a new kind of leakage - on my own bill of all places - that nobody will be systematically checking for. If you fail to appreciate the risk that there are unknown causes of leakage, you fail to understand why we need revenue assurance.

This problem about knowledge and certainty has a long history. Trying to attain perfect and certain knowledge about something by comparing it to something else leads to an infinite regression. This was recognized by Plato right at the start of western philosophy. Aristotle called it the Third Man Argument. They lived over 2000 years ago, and were very smart men. If they never found a satisfactory solution, and nobody has solved it in the meantime, I guess we can safely assume that nobody in revenue assurance will find an answer anytime soon. That means we should stop pretending to know what we do not know, no matter how inconvenient that may be.

Abstraction Reactions

In the telecommunications industry, time is money in a very literal sense. Even those with the most basic understanding of telecoms know that. In one of my former jobs, I fondly remember tormenting an audit junior from a Big 4 firm that was tasked with the important job of identifying weaknesses in my revenue assurance strategy. She kept stressing the importance of not losing minutes, so I kept asking her where I would normally find these ‘minutes’ she kept referring to. Poor girl, she lacked the training to even begin to formulate an answer. There was no talk of protocols to transmit files or definitions of the fields in call records. Instead, she just kept saying that minutes could be lost, as if minutes were sheep and I was the shepherd. She simply did not know the subject matter or the terminology, which was why it was so easy to give her a hard time. It tells you a lot that the Big 4 employ audit teams with such high-level briefings that, when placed under pressure, they can be cracked so easily. Do I feel bad that I was mean? Not really. Time is money, metaphorically as well as literally, and telcos pay for the time of their auditors, and for the time of staff like me as well. If I had really wanted to tear the audit junior apart, I would have pointed out that her questions could be best described as value-add because there was no connection between them and the reliability of the financial accounts (if you lost data on transactions, it would be prudent not to recognize the revenue, hence leakage may impact the final revenue number, but does not impact the integrity of the final number). And there is not much value added by an auditor who asks questions without being able to properly understand the answers. Even so, I finally relented and took pity on the poor girl, explaining what CDRs are and where they come from, so she could write up her pathetic management letter points and bluff a little more persuasively at the next client she visited.

Part of the problem with telecommunications operations, like any complex subject matter, is that the abstractions people use to understand the topic are not going to be consistently reliable. The poor audit junior knew that losing minutes was bad, but had no idea that the minutes she was talking about are an abstraction based on the difference between two data fields - start time and end time - and that a record of a call is itself nothing but a stream of data more or less bulked up into files of whatever format on whatever disk space associated with whatever computer. Not knowing that, the audit junior was obviously going to struggle to go into detail as to how these minutes might be lost. Her abstract model knew that minutes started somewhere, and ended somewhere else, but she had no idea of what they were or how they might go missing. She also was going to find it hard to conceive of the many ways that minutes can go missing. She could understand losing or corrupting data, but would always have conceptual blind spots when it came to the difficulties of knowing whether you recorded the start and end time accurately to begin with, or the cumulative loss if you chop off some digits in the trade-off between processing burden and precision. For me, abstraction is the single biggest problem for revenue assurance. Lots of people want to talk intelligently and confidently in terms of abstract representations of what can go wrong. The problem with most of those abstractions, even if very intelligent and given by someone very confident (unlike the poor audit junior) is that they ultimately wil break down. Abstractions may obscure vital aspects of what is happening in the detail, or skew the perception of risk so that effort is mis-directed. I have been in more than one telco that has put disproportionate effort into assuring usage compared to non-usage, because people could imagine what might go wrong with usage but not with non-usage. Similarly, when checking usage, people tend to put disproportionate effort into the problem of getting data from one place to another, and forget about problems like assuring whether the data was any good in the first place. Abstraction is vital for communicating and for having an overall understanding of the domain where risks are treated according to priority, but poor abstraction leads to poor decisions. Like so many things in life, the devil, with revenue assurance, is in the detail.

There are layers and layers of abstraction to telecoms, of course, and I use the word layer deliberately there. Knowledge of detail is essential, but knowing the detail of the layers OSI architecture, or of the COSO framework, or of the eTOM, is only going to get you so far. In the end, they are all useless unless you can also understand the connections between those abstractions and the systems and practices in place at whichever telco you are dealing with. I fondly remember another group of auditors, who were employed to check the accuracy of retail billing. They spent a day asking their questions of whatever poor souls they decided to pick upon. At the end of the day, they came to the conclusion that they had serious concerns with the precision of the records used. That resulted in some serious concerns on my part - about the competence of these auditors. After a couple of pertinent questions about the systems at fault, it transpired they had wasted the day reviewing records only used for interconnect billing. Although the auditors made a gross error in performing their work, on one level it is easy to understand. They got so tied up with the detail of the systems they were looking at, they forgot to ask some themselves some basic questions about how those systems related to their audit goals. Detailed knowledge is fundamental, but there is no individual is going to have enough knowledge to cover all aspects of revenue assurance. The trick is to be able to apply a useful abstract model, and to bend and change it to reflect the real and detailed facts. That requires professional scepticism, not only of the statements presented as fact, but also of the abstract models used to organize those facts. The two are in constant tension. The abstraction may lead to questions about the details, and the details may prompt questions about the suitability of the abstraction.

There is another aspect to abstraction that people sometimes skirt around or conveniently ignore. Abstraction goes deeper and higher than just the technical detail of how systems and processes work. If you want to get really sceptical at the detailed end of revenue assurance, you end up needing to understand things like the fetch-decode-execute cycle of CPUs or the speed transmitting radio waves through the air or electrons down a wire. I have seen people talk, at a supposedly detailed level, like these things are constants for the businesses they are talking about. A moment's reflection should have satisfied anyone with competence that they are not. Switches are designed specifically to deal with high volumes with little variance in their performance, but their performance does vary according to load. The laws of physics may be universal, so electrons and radio waves all travel at the same speed, but that is not the same as saying that transmission always takes the same amount of time - transmitting over a longer distance obviously takes longer than over a shorter distance, but I have seen supposedly detailed and scientific technical audits that blundered by stating that the times, and not the speeds, are a constant. At the other end of the scale, we must not lose sight of why we do revenue assurance. Somebody needs to see a benefit, be it customers or shareholders. Yet many abstractions of revenue assurance simply come up with some hideously and unjustifiable assertion about what all customers and/or shareholders want, or worse still pretends that all stakeholder goals can be neatly and conveniently aligned. That may help revenue assurance vendors sell their products, with taglines about improving customer confidence, increasing revenues, and achieving regulatory goals as if all three are harmonious. However, only a simpleton (or somebody not stepping back and taking a moment to think about what they are doing) actually believes that the priorities of all stakeholders are identical and are equally satisfied by the same choices. In all choices there will be trade-offs, and an oversimple perspective on what stakeholders want only causes revenue assurance people to persuade themselves of their success, whilst failing to recognize the compromises they have chosen.

Building up revenue assurance abstractions to link the most excruciating detail with the most pervasive understanding of stakeholders is a never-ending process. It requires perpetual addition and refinement. The irony is that revenue assurance is about spotting and stopping errors and wastage, yet without the right abstractions, you may not be able to communicate about them, or even conceive of them.

Time Is Money

A recent UK study by the Consumers’ Association has concluded that government agencies and large businesses are unjustifiably profiting from customer calls. See here for the summary of their findings, and here for a good explanation of the story from the BBC. Despite efforts by the regulator to promote non-geographic numbers that are charged on a neutral basis, the organizations surveyed were continuing to use numbers where they received a proportion of the call charge. For example, the government agency responsible for vehicle and driver licences, the DVLA, earned UK£3.4m (US$6.8m) from incoming calls over the course of a year. This means that, if a person is accessing a government service, or complaining about a faulty product, they are being made to pay an unjustifiable charge to do that. What is more, the longer they are kept waiting, the greater the charge they pay. Taxpayers and customers are being made to pay for an entitlement, and worse still the organizations are rewarded for slow service.

Time is money for the private citizen as well as the organization they deal with, so arguably it is the customer who should be paid when they receive slow service. Telcos, of course, are just middlemen in this exchange. They charge their standard rate for providing a service of whatever duration, but they are the enablers and middlemen for this unjustifiable transfer of money. Whilst it may be very good business on one scale, I wonder if it ultimately contributes to the cynicism of end users about telcos. In addition, if telcos send out bills with big and unexpected charges, they can assume they too will receive a call of complaint. Even if the complaint is not justified, the telco still bears the cost of having to deal with that complaint. For that reason, telcos may benefit by helping the regulator and encouraging the switch to numbers that involve no element of revenue share, thus reducing the costs to the consumer and to themselves. It should even aid telco profits, as a reduction in call costs will make it more likely that customers will make a call, rather than follow the advice from the Consumer Association to use alternative and cheaper forms of communication like email. To understand all the ramifications of such a change, you should also factor in the timing of cashflows and degree of credit risk. Does doing the maths on a change like this sound like a job for revenue assurance, or (for those who like to keep their revenue assurance focused on its core remit) for the newer kinds of enhanced-scope revenue assurance + miscellaneous business analytic teams that we are seeing more of? Possibly. But my guess is that all are too busy to consider the impacts and relationships, or doubt they could influence the telco to do anything about it anyway. Such is the challenge of abstraction in a complex environment. Sometimes it is just easier to get on with looking for those lost minutes instead of adding value. And, after all, time is money - and nobody wants to waste time doing something that is not their job...