Then, when the Moronistry of Defence came to review the contract, yet again they went for the lowest tender, this time it was Crapita who were the most mendacious. Crapita waltzed in, planning to rinse-and-repeat the HPE effort after using the know-how people to build a new system (as you say, shouldn't take long) before sacking them...
I know nothing of this fiasco but I do know that 16 years ago Crapita won the outsourcing bid for the Department of Employment system that ran part of the Youth Training Scheme. The existing system worked and was built in house, so Crapita assumed they could just TUPE over the staff who wrote it, leech the domain-specific expertise and then offshore the system maintenance. Nope.
Many essential staff refused to work for Crapita, even on secondment and resigned in the face of ultimatums. As a result, the system was rendered unsupportable[1] and procedures crashed back to paperwork for a couple of years (at great expense to the taxpayer, not Crapita).
[1] Governments meddle with the rules affecting systems like this with every budget so just keeping the system going in a fossilised state is never an option. Budget announcements are confidential and frequently immediately active so front-line systems have to be capable of implementing major changes at the drop of a hat while still supporting X levels of old rules that govern all the prior contracts. That means (or meant then) that you need people who hold most of the logic and codebase in their head. There was enough redundancy in the workforce to cope with flu, car accidents and alcoholism, but not enough to survive a pandemic like the "Crap Death".