Fujitsu seemingly built a flawed computer system - they aren't the first and they wont be the last. But it was the Post Office that signed it off for use in live, and the Post Office that decided to prosecute and bankrupt their own sub postmasters rather than face up to its flaws
Fujitsu bosses knew about Post Office Horizon IT flaws, says insider
A former senior developer who worked for Fujitsu on the Post Office IT system that led to subpostmasters being falsely accused of fraud, has claimed bosses knew of fundamental flaws before going live
The Post Office’s Horizon IT system should “never have seen the light of day” and bosses at supplier Fujitsu allowed it to be rolled out into the Post Office network despite being told it was not fit for purpose, according to a senior developer who worked on the project before it went live.
“Everybody in the building by the time I got there knew it was a bag of s**t”, he said. “It had gone through the test labs God knows how many times, and the testers were raising bugs by the thousand.”
The senior developer said he was contracted to work on the Horizon project between 1998 and 2000, at one point holding the job title Horizon Epos [electronic point of sale] development manager. He has asked to remain anonymous, but is prepared to give sworn witness statements to solicitors acting for subpostmasters in their ongoing appeals against past convictions.
The developer has also asked Computer Weekly to pass his contact details to the government’s Post Office Horizon IT inquiry, chaired by former High Court judge Wyn Williams.
Senior managers were aware
The most serious allegation raised by the developer is that senior managers at Fujitsu were aware that an important element of the Horizon system did not function correctly and could not be fixed.For the first 10 years of Horizon’s existence, transaction and account data was stored on terminals in each branch before being uploaded to a central database via ISDN. Our source says this part of the system simply did not work.
“The cash account was a piece of software that sat on the counter NT box, asleep all day,” he said. “At the end of the day, or a particular point in the day, it came to life, and it ran through the message store from the point it last finished. It started at a watermark from yesterday and combed through every transaction in the message store, up until the next watermark.
“A lot of the messages in there were nonsense, because there was no data dictionary, there was no API that enforced message integrity. The contents of the message were freehand, you could write whatever you wanted in the code, and everybody did it differently. And then, when you came back three weeks later, you could write it differently again.”
He gave an example of a message stored previously when a customer bought a stamp. It was feasible that a new message for buying a stamp weeks later could be slightly different.
“When the cash count came along, it found a message it was not expecting and either ignored it, tripped up, or added something it shouldn’t be adding,” he said.
In 2015, Computer Weekly reported another anonymous source who identified the cash writing program as a possible cause of serious problems. He told us the Post Office was warned about the risk of data corruption on the bespoke asynchronous communication system which sent messages between branches and the central Horizon set-up.
Speaking to Computer Weekly in 2015, the anonymous source told us: “The asynchronous system did not communicate in real time, but does so using a series of messages that are stored and forwarded, when the network connection is available. This means that messages to and from the centre may trip over each other. It is perfectly possible that, if not treated properly, messages from the centre may overwrite data held locally.”
Four years later, former Fujitsu engineer Richard Roll wrote in a witness statement to the High Court: “The issues with coding in the Horizon system were extensive. Furthermore, the coding issues impacted on transaction data and caused financial discrepancies on the Horizon system at branch level.”
Roll’s evidence, which was accepted by the judge, suggests that the problems with Horizon identified by our source had not been dealt with by the time the system went live.
Other experts familiar with Horizon that Computer Weekly approached have also supported the developer’s claims.
The developer said he made his superiors at Fujitsu aware of the extent of the Epos system problems, telling them explicitly that the cash account needed to be scrapped.
“I broke it down and said: you can keep these bits at a push if you have to,” he said. “But that bit in the middle, these bits of the engine, the gearbox, you need to throw them away and rebuild them. Starting with the cash account. You’ve got to throw the cash account away and you’ve got to rewrite it.”
Full article https://www.computerweekly.com/news...out-Post-Office-Horizon-IT-flaws-says-insider
Last edited: