Oracle Archives - Bad Buying

Anyone who has been around in business for a few years knows that there is nothing more nerve-wracking, tense and challenging then implementing a new technology solution in a mission-critical area for the business. When I was researching my Bad Buying book, I found enough case studies on that topic to have pretty much filled the book with that alone.

I did include a few examples, from different sectors and countries, from an Australian government payroll system disaster to the US drugs firm FoxMeyer, who went bankrupt after major problems with a project that included two software providers plus a systems integrator.

But despite the challenges, digitisation is essential. A recent articl e quoted Malcom Harrison, CEO of the esteemed Chartered Institute of Procurement and Supply, as saying this. “Whatever your corporate goal might be, a digital platform is critical to making more informed decisions”.

Unfortunately, CIPS itself has run into difficulties related to its own set of new digital platforms which it has been implementing over the last year or so, including its website, customer and membership systems. In an email to CIPS members recently, CEO Malcolm Harrison apologised for the inconvenience members and students have experienced over recent months in using the platforms. I had seen some comments which were critical of the new platform around social media, and even a comment sent to the Spend Matters website. Several mentioned exam booking as a particularly problematical area. But clearly the problems are wider than that.

In the email, Harrison explained that CIPS chose tech giant Oracle as the software provider, after a thorough procurement process. But Oracle don’t do implementation themselves – which is true of many major software providers. (Company valuations are generally higher for pure-play software firms than for combined software / services businesses). Instead, an Oracle approved systems integration partner, Enigen, has worked on that task.

In the email, a joint statement from CIPS and Oracle said this: CIPS, Oracle and Enigen are committed to modernizing the CIPS member and customer experience. Oracle has stepped in to ensure the project delivers on its full potential.”

The cynical might wonder how Oracle will “ensure” that delivery, given they don’t do implementation, and some might feel there is an implication there that Enigen are at fault, that Oracle having to “step in” to sort things out.

A spokesperson for Enigen gave us this short statement: “This has been a complex project with many evolving and additional requirements. We are working collaboratively with CIPS and Oracle to create an exceptional digital experience for their members.”

We will come back to that statement in part 2 of this commentary – it is interesting to see that mention of “evolving and additional requirements”. That will no doubt set off alarm bells with readers who have experience of large software programmes! And of course, if Oracle has now “stepped in” to sort out the problems, it does beg the question as to why this level of integrated involvement from the firm was not already planned and present in the implementation programme.

I don’t want to be too critical here. To be honest, I managed to get through my lengthy procurement leadership career avoiding responsibility for many significant systems programmes. That was partly deliberate and partly luck (thanks to RBS for buying NatWest just as we were starting the mega-SAP programme … which RBS canned, incidentally). This is intrinsically difficult work – when I talked to a good friend of mine, one of the best complex programme managers I have ever met, he simply said, “it can happen to the best of us”.

But these events are not a great advert for the procurement profession, or for the firms involved, so hopefully the issues can be resolved quickly. I would also hope that CIPS will be open with members as to what has gone wrong. That could represent a learning opportunity that might help thousands of other CIPS members and their organisations, and CIPS has plenty of opportunities to feature this programme and all the experience gathered from it through its own channels. In that spirit, in Part 2 we will suggest some general good practice points (not necessarily linked to the CIPS case) when it comes to major systems implementation programmes.

We write pretty regularly about public sector procurement disasters, probably more than we cover private sector failures. When I was researching and writing the Bad Buying book, I found it easier to find stories about government entities than those featuring major private sector firms.

There are a number of reasons for that. Some areas of government spending – such as defence – are just very difficult and complex. So it is a challenge in any and every country to execute that type of procurement well. There is also the political factor, politicians who want to leave a “legacy” for instance, or who want to pursue a certain policy despite the fact that there is no procurement solution that is likely to work.

But the biggest reason is probably just the nature of government, meaning there is a higher probability that a disastrous IT system implementation will get into the public domain. So we find out about numerous tech failures in the UK public sector, going back to the DSS ICL “Benefit Card” fiasco, to the ongoing Home Office/Police Airwave failure.

So it was interesting and unusual to see a high profile private sector firm mentioned in the press recently for a significant IT problem. According to the Times, Waitrose, the upmarket supermarket chain and part of the John Lewis Group, has seen problems with stock management in recent months, which is being blamed on the implementation of a new Oracle / JDA ERP system.

But it is an odd example, because although the Times report was quite detailed, Waitrose has strenuously denied that there is a problem. So the newspaper says, “The idea is to replace the partnership’s antiquated systems with the Oracle system. But during the switchover, when the two systems have to temporarily “talk” to each other, the Oracle system has been producing incorrect numbers. Every time a new part of the system is introduced, more problems emerge… “

The report says that product availability has slipped from 3/94% to around 91% compared to an industry average of 92%. Well, to be honest, that does not sound like a major problem, although many readers did comment on the article to back up the claim, complaining about lack of product in their local stores. Particularly cheese …

Waitrose then denied that there is a particular problem or that there are system issues, claiming that their product availability is still better than several major competitors. But one point which did make me wonder was the statement that the implementation has been ongoing for 6 years now. That does seem like a long time – even given Covid – to get a new system in place.

Coincidentally, I heard from a friend the other day about another organisation in a very different industry (but one that will be well-known to most readers here) that has had major Oracle implementation problems this year. Now clearly many ERP implementations do succeed, or Oracle and SAP would not have grown to be two of the largest tech firms in the world. But it is also clear that things can go wrong.

I included a salutary tale in the Bad Buying book, all about FoxMeyer, a US pharma distributor. That ERP implementation appeared to set off a train of events that ended up with bankruptcy, and illustrated a number of common failings in IT disasters. The case study seemed to show defining the requirement wrongly; relying too much on external consulting-type expertise for the implementation; several suppliers sharing unclear accountability and blaming each other when things went wrong; trying to integrate different systems that did not really want to integrate; and poor programme management. We all probably recognise some of those warning signs.

So whatever the truth about Waitrose, if your organisation is planning or going through a major systems implementation, be very careful. Get the right expertise lined up, including at a minimum, some internal “intelligent client” resource even if you are using consultants for much of the work. Be cautious, do your risk management properly, define accountabilities, never assume different systems will integrate easily (e.g. consider the data architecture), plan carefully, put the governance and reporting in place….

It is a long list, so good luck!

Tag Archive for: Oracle

What’s Gone Wrong With CIPS Systems?

Waitrose Denies that New Systems are Causing Stock Issues