Category Archives: IQ Trainwrecks and Customer Service

Quality Information – it can be a lottery!

Leave a reply

It’s been a little while since our last post of an IQTrainwreck. That doesn’t mean that they dont’ still occur. Only this past weekend Irish national broadcaster RTE published inaccurate information about the winning numbers in the Irish National Lottery draw at the end of the broadcast. .We’d like to show you video footage of the error but, to avoid compounding the error, RTE have edited the last few seconds from the end of the recording which is available on the RTE website.

According to The Irish Times RTE blame a software error for the incorrect display of numbers, which the broadcaster was forced to correct through continuity announcements during the remainder of the evening. Apparently a software update was applied ahead of the draw on Saturday 17th December.

The Irish National Lottery has expressed concern that anything might affect the collection of the winning prize, a trivial amount of only €4.9 million but point out that there is more than one way for a person to check their lottery numbers.

 

There are a few lessons to learn here for Information Quality Professionals

  1. When you are presenting mission critical information in time-sensitive environments, it is imperative that you have any changes to process, software, or technical architecture well tested before ‘show time’.
  2. When you are relying on the quality of information for critical decisions it is often worthwhile to take reference data points from other sources to validate and verify the source you are using, no matter how trusted or trustworthy they may have been in the past. Trust but Verify is a good mantra
  3. When using data for decision making where accuracy is a “Critical to Quality” factor you should seek out the most authoritative source. Often this mean going to the real world object or source data creator (in this case the National Lottery itself) rather than relying on a normally reliable surrogate source (the National Broadcaster in this case) in case errors or defects have crept into the data which is being presented by the surrogate.

 

 

Smart Grid, Dumb Data

Leave a reply

In September 2010 a massive gas explosion ripped through the San Francisco suburb of San Bruno, not too far from San Francisco International Airport. The explosion was so powerful it was registered as a magnitude 1.1 earthquake.

Subsequent investigations have identified that poor quality data was a contributory factor in the disaster. According to Fresnobee.com

The cause of the deadly rupture has not yet been determined, but the PUC said it is moving ahead with the penalty phase after the National Transportation Safety Board recently determined that PG&E incorrectly described the pipe as seamless when in fact it was seamed and welded, making it weaker than a seamless pipe.

Read more: http://www.fresnobee.com/2011/02/25/2285689/pge-faces-big-fine-over-gas-pipeline.html#

According to the San Francisco Chronicle the problems with PG&E’s data were nothing new, with problems stretching back almost 20 years.

Omissions or data-entry errors made when the system was developed – and left uncorrected – may explain why PG&E was unaware that the 1956-vintage pipeline that exploded in San Bruno on Sept. 9, killing eight people, had been built with a seam, according to records and interviews. Federal investigators have found that the explosion started at a poorly installed weld on the seam.

Continue reading →

Zero Entertainment in Norway

Leave a reply

This story comes from our Norwegian Correspondent, Mr. Arnt-Erik Hansen (former IAIDQ Director of Member Services). We let him tell his tale in his own words, with only minor editing….

++++

Norway is the only country in the world, as far as I know, with full transparency with regards to personal income, wealth and state tax. One of the big Autumnal Entertainments in Norway is the annual publication of the list of taxpayers, their incomes, and the amount of tax they have paid. . Here you can search for your neighbor, your friends, enemies, public companies or government officials to find what their income was, how much they contributed to the state and how wealthy they are. On October 20, 2010 the list was published on the internet

Newspapers, TV, and blogs (including this one) find this a great event to generate stories.  Every year there are stories about the person earning the least and the most. Not only that, they compare a person’s income to the average income in the country, according to your age. They will even go as far as determining the street in Norway with the lowest average income. This is business intelligence on real live data.

However the Norwegian tax authorities are not immune to data quality problems. Here are some of the stories I read in the newspapers today (all online of course [editor: Links to the stories will be posted here soon])

A polish citizen, address in Polen and with a modest Norwegian income is reported to have paid more than 119’000’000 Norwegian Kroner (approx US$20.4 million, or €14.6million ) in taxes for 2009. As a consequence he can claim to be the biggest contributor to the state coffers. Thanks Polen, I am sure that someone will be there to collect the money soon.

This is of course wrong and the reason is, most likely, that someone punched in the wrong number – a number with too many zeros. We’ll call this “The Fat Finger Zero Error“.

Apart from errors in the data itself, there appear to be errors in the actual interpretation of the data. For example, a lady working as a cleaner got a tax claim of no less than 84’005’501 Norwegian Kroner (€10.3million or US$14.4million). Her income for 2009 was reported by one newspaper to be 324’000 (US$55,600, or €39,818) so this is an obvious error. Another newspaper reported her income to be 240’000.

A key question is: What has happened here?

The answer from the tax authorities when asked to comment on this was simply – errors happen, unfortunately, and will be corrected immediately. However, the reason was, most likely, that someone punched in the wrong number – a number with too many zeros. Well, seems that someone has a problem with zeros.

There is another story to come about the “Fat Finger Zero” error.  But first we need to share some insight into the tax reporting and collection process in Norway works.

It’s not too different to any other country. Except in Norway the State sends you your forms filled in with the information the tax authorities have about you and you simply have to sign them and send them back.  And, like most tax authorities, they most likely know more about you than yourself.

For instance, banks in Norway send megabytes of data about all customers and their accounts to the tax authorities. Which leads us to our third IQTrainwreck example in this story…

This year two banks managed to put zeros behind the customer account balances instead of in front for 500 customers.  So €00000500 became €500,0000.

A possible root cause: the definition of the attributes in the file has gone astray.

But from two banks?

Or was the requirement wrong?

It  seems that Norway has a problem with zeros.

Oh, almost forgot to mention – today the Norwegian State Fund was valued above the 3’000 Billion mark for the first time. That’s 3’000’000’000’000 Norwegian Kroner (US$514,610,220,303).

I think I understand the problems with zeros. (But how much of that is due to tax collection errors? – the sting in the tail for Norwegian tax payers is that if there is an error in their tax calculations they have to pay the decided amount and then are refunded the amount of any error).

PS! If you look up my name you will find income 0, wealth 0 and taxes 0. The reason: I lived in Switzerland in 2009 and in that country you are invited to pay taxes and it is not a criminal offence if you don’t tell the state everything.

Bank overcharging in Ireland (again)

Leave a reply

In a taste of the change of emphasis that is seeping through the global financial services industry, the Irish Financial Services Regulatory Authority is pursuing 24 cases of overcharging by banks and insurance companies, according to this morning’s Irish Independent

Of course, stories of financial services overcharging and other information quality disasters in that industry are not new to the IQTrainwrecks reader. Over the years we’ve covered them here, here, here, here, here , here, here, and here (to select just a few).

We’ve also covered the growing “hard touch” trend in Financial Services that is bringing a clear “cost of non-quality” to bear on banking/financial services processes (see this post from August of last year).

Why is this now an IQTrainwreck again?

  • Regulators are adopting a tougher line with banks about overcharging/undercharging (a bit like the regulators did in my former industry – telecommunications).

The new chief of the Irish Financial Services regulator is concerned about the number of overcharging cases and recently said that:

It is clear from recent cases that change is needed in how firms handle charging and pricing issues.

  • Financial services companies, facing into severe cutbacks in budgets and man power are potentially increasingly exposed to the risks of manual work arounds in processes simply stopping, end-user computing controls not being run,  and ultimately inaccuracies and errors creeping into the information they hold about the money they hold for or have loaned to customers.

As the regulatory focus shifts from ‘light touch’ to ‘velvet fist’, those financial services companies who invest in appropriate strategies for managing the quality of information in a culture of quality will be best placed to avoid regulatory penalties.

Why 2k?

2 Replies

IT media sources are reporting that reports of the demise of the Y2k bug may have been premature. (see also here)

Systems affected included Spam control software and other security software from a leading vendor, network equipment from leading vendors as well as credit card payment systems in Germany and Australia, as well as (it seems) Windows Mobile. The bug was tweeted heavily on Twitter.

The effect of this bug seems to have been to catapult messages forward in time by a few years, resulting in credit card terminals rejecting cards as they failed date validation checks (the card expiry date was in the past apparently), valid emails being flagged as spam (because the message was date stamped in the future), and SMS messages appearing to come from the future.

The potential knock-on impacts of this error don’t bear thinking about. In the immediate term we have:

  • Embarrassment for credit card wielding shoppers who found themselves unable to pay for purchases or meals.
  • Missed emails due to them being flagged incorrectly as SPAM (although this has been fixed).
  • SMS confusion.

But, in this automated world where processes are triggered by business rules based on facts and information there are potentially other impacts:

  • Discovery of emails or SMS messages in criminal or civil litigation (will the lawyers think of looking in the future? Can the evidence be verified if it appears to be from the future?)
  • electronic transfer of data or funds based on rules
  • Calculation of interest payments or penalties based on date rules

The root cause of this problem appears to have been assumptions about dates, and the thought in 1999 that 2010 was sufficiently far in the future that (one must assume) everyone assumed that a better fix for the rules being applied would be developed by then.

Perhaps they should have checked their listings twice?

Leave a reply

The Irish Sunday Independent reports this past weekend that the Irish State Broadcaster RTE is facing legal action from its erstwhile privately owned competitor TV3  arising from what are described as “significant and egregious” errors in the listings published for TV3’s programmes over the Christmas period in the RTE owned listing’s magazine “The RTE Guide”. The errors affect listings over the core Christmas period and also the time of one movie which is due to be broadcast tonight at 9pm but which is listed incorrectly in the Guide.

In a wonderful example which highlights the potential downstream cost and revenue implications of poor quality information, TV3 says the error is so serious that it could have a fundamental impact on its Christmas viewing figures.

And, in TV-land, viewing figures translate into hard-to-come-by-in-a-recession advertising revenues.

TV3 have asked for RTE to pulp all copies of the RTE Guide still in shops and to replace them with reprints which show the correct listings. Failing this, they have asked RTE to give prime-time advertising coverage on TV and radio to TV3 programmes over the Festive Season, which would have the effect of reducing the prime-time advertising slots which RTE would have already sold over Christmas, hitting RTE’s revenue streams as well.

RTE, for their part, blame a 3rd party supplier for the errors.

Of course, this writer’s thoughts are with the ultimate information consumers here… the viewing public. If my house as a teenager was anything to go by, the RTE Guide will have been used as the basis for negotiations about who gets to see TV ‘live’ versus programming the video recorder.

A while ago, Daragh O Brien wrote on his blog about the likely rise in Information Quality litigation, particularly as studies have shown that people become more litigious during a recession. This looks like one of those cases and it seems 2010 will be an interesting year for Information Quality management principles in Ireland.

Double Debits – directly. (Another banking IQTrainwreck)

6 Replies

Courtesy of our Irish colleagues over on Tuppenceworth.ie comes yet another tale of poor quality information in financial services. Although this time it is at the lower end of the scale, at least on a per customer basis. However, the impacts on a customer are still irksome and problematic. And the solution the bank has put in place is a classic example of why inspecting defects out of a process is never an exact or value adding science.

It seems that Bank of Ireland has recently introduced some new software. Unfortunately, a bug in the software has resulted in certain transactions (deductions) being posted multiple times to accounts, resulting in cash-strapped Irish people being more strapped for cash than they’d expected.

Simon McGarr, (one of the authors over at Tuppenceworth) sums up the story and the reason why this is an IQTrainwreck:

I spotted a double charge on my account, for a pretty significant sum of money (is there any other kind?).

When I rang up to query it, I was told Bank of Ireland have changed their computer systems recently (Two weeks or so).

As a result, some transactions are being applied to accounts twice if they were processed through Laser [a debit card system in Ireland — ed.], or if they were a Pass machine [what the Irish call ATMs –ed.] withdrawal.

They say that if you spot the double charge, and ring them up to complain, they’ll send an email to their programmers to reverse the second charge.

I suggested to the polite customer services person that the bank might want to warn their clients to be alert for these double charges, as they could suffer additional charges (from appearing to breach their overdraft limits, for example) unless they spotted the bank’s mistake.

(Emphasis is added by this author)

Simon goes on to add (in a comment) that he has been without the benefit of his hard earned cash for 10 days (and counting).

Continue reading →

Apple App Store IQ Trainwreck

Leave a reply

It appears that Apple iPhone App developers are having difficulty getting paid at the moment, according to this story from The Register. (Gizmodo.com carries the story here, Techcrunch.com has it here,

According to The Register:

A backlog in Apple’s payment processing system has left some iPhone developers still waiting for February’s payments, leaving some at risk of bankruptcy and considering legal action against the lads in Cupertino.

Desperate developers have been told to stop e-mailing the iTunes finance system and to wait patiently for their money – in some cases tens of thousands of dollars – while Apple sorts things out.

It would appear from comments and coverage elsewhere that this problem has been occurring for some developers for longer (since late 2008 according to the TechCrunch article and this article from eequalsmcsquare.com (an iphone community site))

The article goes on to explain that:

According to postings on the iPhone developer community Apple has been blaming bank errors and processing problems for the delays. Complainants are being told that payments have been made, that bank errors have caused rejections[.]

One commenter on the story on The Register, commenting anonymously, attempts to shed some light on this with an explanation that, from an Information Quality point of view, sounds plausible.

  • Two American banks merged (was it Washington Mutual and Chase?) and the SWIFT code for the customers of one had to change. The bank didn’t tell the customers and Apple had the payments refused. Apple seem to be manually changing the codes in the payment system, but that’s separate from the web interface where devs enter their bank details.
  • A lot of American banks don’t have SWIFT codes at all. Royalties from e.g. EU sales are sent from Apple (Luxembourg) S.A.. The chances of this money arriving at Bank Of Smalltown seem slim at best.

This what we have here is a failure to manage master data correctly it seems, and also a glaring case of potentially incomplete data which would impact the ability for funds to flow freely from the App Store to the Developers.

The Anonymous commenter’s explanation would seem to hold water because Apple are claiming that “bank errors have caused rejections”. Having had some experience with electronic funds transfer processes, one of the reasons a funds transfer would fail would be if the data used was incorrect, inconsistent or inaccurate. This would happen if the SWIFT codes of Bank A had to change (or if Bank A and Bank B had to have new codes issued).

However, some commenters based in the EU have reported that they have given Apple updated bank details and are still awaiting payment, which suggests there may be yet another potential root cause at play here that may yet come to light.

Apple still owes me more than $7,500 since September 2008 for US and World regions. I supplied them with a new SWIFT code and a intermediary bank they could use last month, but still nothing. Sent them tons of emails but I never got to know what is really wrong/faulty so I just tried to give them another SWIFT code that DNB (Biggest bank in Norway) uses. All other region payments have been OK.” (quote from comment featured on this article)

So, for the potential impact on iPhone Apps developers cash flow, and the PR impact on one of Apple’s flagship services, and the fact that management of the accuracy, completeness and consistency of key master data for a process, this counts as an IQ Trainwreck.

I am who I am, except when I’m not.

Leave a reply

Steve Tuck, writing over at SmartDataCollective, shares a tale of an embarassing IQTrainwreck involving his brother. The root cause of Steve’s tale is ‘false positives’ in matching, but it goes to show how simple assumptions or errors in the management of the quality of information can lead to unforeseen and undesired consequences.

Steve’s brother had checked into a hotel for a trade conference. He went and had a shower and was quite surprised to come out of the bathroom to find another man standing in his room. It turned out that they both had the same name and were both attending the same event and the hotel had (despite all the other evidence to the contrary, like different companies and different credit card details) decided to merge the two reservations so two people wound up being booked into the same room.

The second Mr Tuck had to take his bags and go to a different hotel in the end, causing unnecessary aggravation for him (it is always nice to be staying in the hotel a conference is on in… the more relaxed pace over breakfast can help ease you into the day). Steve’s brother had the embarassment of being caught in little more than a towel.

For the embarassment factor and customer service impacts, this meets the criteria for an IQ Trainwreck. 

Thanks Steve.

This isn’t the first time we’ve covered this type of false positive IQ Trainwreck though. A scan of our archives brings up this story from 2007.

#AmazonFail – a classic Information Quality impact

1 Reply

So, Amazon recently delisted thousands (over 57000 to be precise) of books from their search and sales rankings. The Wall Street Journal carries the story, as does the Irish Independent (here), The China Post (here), ComputerWorld (here), the BBC (here)…. and there are many more. In the Twitter-sphere and BlogSphere, this issue was tagged as #AmazonFail. (some blog posts on this can be found here and… oh heck, here’s a link to a google search with over 400,000 results). There are over 13000 seperate Twitter posts about it, including a few highlighting alternatives to Amazon.

We have previously covered Amazon IQTrainwrecks here and here. Both involved inappropriate pushing of Adult material to customers and searchers on the Amazon site. Perhaps they are just over-compensating now?

It appears that these books were mis-categorised as “Adult” material, which Amazon excludes from searches and sales rankings. Because the books were, predominantly but not exlusively, relating to homosexual lifestyles, this provoked a storm of comment that Amazon was censoring homosexual material. However books about health and reproduction were also affected.

Amazon describe the #AmazonFail incident as a “ham fisted” cataloguing error which they attribute to one employee entering data in one field in one system. One commentator ascribes the blame to an algorithm in Amazon’s ranking and cataloguing tools. And a hacker has claimed that it was he who did it, exploiting a vulnerability in Amazon’s website. Continue reading →