Contract management Archives

You may know the expression “don’t spoil the ship for a ha’pworth of tar*”, but we have a case now where the ship most certainly has been spoiled – or at least put out of service for some considerable time – because of a tiny error in manufacturing. The impact of this has also led to a tricky contract management situation.

In August 2022, the British aircraft carrier Prince of Wales broke down just one day after departing its Portsmouth base for training exercises off the US coast. That was hugely embarrassing for the Navy given the ship had cost some £3.1 billion and this wasn’t the first problem since initial launch in 2019. This time, the issue was traced to a starboard propeller shaft fault and an installation error. Responding to a recent parliamentary question, Ben Wallace, the UK Defence Minister, said that based on “initial reports” the shaft was misaligned by 0.8 – 1 millimetre. That is a tiny mistake, but apparently caused a huge problem.

As well as the operational issues this caused, the question of who should pay for the error is also complex. Construction and delivery of the warship was carried out by a consortium of three firms under the banner of the now defunct Aircraft Carrier Alliance. BAE Systems, Babcock and Thales were all involved, which makes it complex to assess liability. Will the Ministry of Defence (MOD) end up paying or will they be able to pin the responsibility onto one or more of the firms?

A report on the “Breaking Defence” website said that the MOD “declined to comment on why the repair bill liability decision has not been made yet, nor when a decision is likely to be made”. But MOD did say that repairs were likely to cost some £25 million, and that an investigation was looking at how to ensure the failure was not repeated. Well yes, one would hope that the same won’t happen again!

John Healey, the Labour Party’s shadow defence secretary pointed out that since the ship entered service in December 2019, it had spent 411 days in dock for repairs, compared to just 267 days at sea. A previous deployment also ended in embarrassment and a quick return to base in Portsmouth after an internal flood left the engine room and electrical cabinets submerged for 24 hours. The current repairs were supposed to be completed at the Rosyth dockyard in Scotland by February, but at time of writing (May 2023) still seem to be going on.

We could draw analogies here between our (literal) flagship and the wider state of the UK. Still pretending to be a significant global power, but incapable of actually doing anything to live up to that fantasy and all that sort of thing. But keeping to the facts, in a more mundane fashion it does highlight the importance of absolute clarity in the contract whenever you are buying from a consortium of any kind – and that doesn’t just apply in the military world of course.

Don’t assume a consortium will act as one entity if something goes wrong. It’s just as likely that each party will fight to protect their own position, which can leave the buyer in a difficult position, as we may be seeing here. So a strong and clearly written contract, including a definition of what will happen if there are issues after the formal consortium is dissolved, is essential.

And you can see why the UK Treasury (finance ministry) is not too keen on increasing the MOD’s budget for spending on more equipment, even given the present Russian threat. Cases like this (as well as high-profile failures such as the Ajax armoured vehicles) all add to a lack of confidence that such money would be spent well.

* A bit of research suggests that the expression was originally about sheep rather than ships! I didn’t know that…

In my Bad Buying book, I wrote about the IT disaster that affected millions of TSB bank customers back in 2018. Here is the story from the book.

“In 2015 Sabatell acquired TSB, a UK-based retail bank, formally part of the Lloyds TSB Group. TSB at some point needed to move onto its own IT platform, rather than continuing to use the Lloyds group systems, as they were now competitors to their former parent company. But the move, in April 2018, turned into a disaster.

Account holders couldn’t use mobile or Internet banking, and some reported seeing accounts details from other account holders. Customers struggled for weeks to make mortgage and business payments, as the new TSB systems failed to function properly. The issue was serious enough to be raised in the British Parliament, and in September 2018 TSB’s CEO, Paul Pester, resigned.

In March 2019 The Sunday Times reported that an investigation into the affair put much of the blame onto the IT firm that handled the transition.13 However, the twist was that this firm was SABIS – which is part of the Sabatell Group itself. So although it has a separate identity, this was in effect the internal IT function of the group that owned TSB.

Reports suggested a range of technical and programme management issues around the deployment of new software, rather than problems with the underlying infrastructure. But whatever the cause, the whole episode cost TSB £330 million,14 and there is a ‘provisional agreement’ (according to the firm’s annual report) for SABIS to pay TSB £153 million. In November 2019 an independent report from law firm Slaughter and May concluded that the issues arose because ‘the new platform was not ready to support TSB’s full customer base’ and, second, ‘SABIS was not ready to operate the new platform’.

Questions have to be asked about the choice of ‘supplier’ here. Was SABIS the right choice to carry out this challenging task? It certainly doesn’t appear so, in retrospect. Did TSB have a choice, or was the firm told by top Sabatell management that it had to use SABIS? Would a firm with a wider and broader experience of banking systems than SABIS have done better? And why didn’t TSB accept the offer of help from Lloyds, which was made as soon as news of the problems broke?”

Now, five years later, there is an interesting postscript. Carlos Abarca, who was the TSB chief information officer, has been fined £81,620 by the Prudential Regulation Authority (PRA), the body that provides oversight of the UK banking system. In their 35 page report, they explain how Abarca’s failure caused a debacle that might have threatened financial stability more widely.

He apparently ignored early signs that the migration was not going well before the big switchover. He “did not ensure that TSB formally reassessed Sabis’s ability and capacity to deliver the migration on an ongoing basis”. Sabis told Abarca that they were migration ready and that subcontractors had given written confirmation that their infrastructure was fit for purpose. but the Authority felt this was not enough because the statements were caveated with comments about outstanding tasks. Abarca also did not obtain a written updated confirmation of readiness from Sabis when he told his own Board everything was ready for the transition.

The PRA said, “Mr Abarca’s failings undermined TSB’s operational resilience and contributed to the significant disruption TSB experienced to the provision of critical functions and potentially impacting on financial stability”.

This might be the first time a senior executive has been fined and disgraced for a failure in contract and project management. Now clearly in most industries, there is no equivalent of the PRA to carry out this sort of investigation and take such action if someone screws up in a similar manner. But if you are in the financial services industry in the UK, it is a warning. If you are responsible in some way for operations, and that includes some procurement and contract management activities, then you must be very careful and must conduct your work with considerable diligence. And make sure you cover your back carefully at every point if a supplier tells you, “yes, everything is fine, don’t worry”!

Tag Archive for: Contract management

Huge Ship, Tiny Error, Major Problem

TSB Systems and Contracting Failure- CIO Fined