Software failures key in T5 fiasco, says BA

Pro

12 May 2008

Willie Walsh may have joined British Airways as the man who turned around Aer Lingus, but he faces a major test as he deals with the recent Heathrow Terminal 5 systems failures.

Software failures were a key part of the Terminal 5 opening fiasco (T5), but it is still unclear whether British Airways (BA) or the British Airports Authority (BAA) are responsible, a British Commons Transport Committee heard recently

BAA is responsible for the contracts with IT suppliers, and so takes part responsibility for costly baggage system errors in the first three days of T5 opening. But BA is responsible for training staff to use the systems correctly, including the correct procedures in the event of software failure.

 

advertisement



 

“We compromised on the testing regime and this impacted on operations, but this was because of delays in the completion of the building programme,” said BA chief executive Willie Walsh. However, BAA were responsible for the building programme, and thus for rushed testing.

“The totality of the testing regime did not adequately reflect the first few days of operations,” said BAA chief executive Colin Matthews. “There were then a number of problems that arose very specifically from within the software.”

These software issues were identified relatively quickly, but the knock-on effect on operations became catastrophic, said BAA non-executive chairman Nigel Rudd.

Neither BA or BAA currently plan to sue any suppliers.

While the failure of major public sector IT systems have had much press over the last few years, such a public failure of a private enterprise system is relatively rare.

Read More:


Back to Top ↑