The shadow of government big IT looms...
Oh no! Look at all this fragmented spending! Something must be done!
Well, the fundamental solution to that is centralised procurement on a ubiquitous system.
Wait, hasn't the government tried this somewhere before? Oh, that's right. They tried this with the Medical Research Council.
A centralised procurement system, based on an Oracle solution. Not just that, but attendance management, pay roll, and a whole slew of finance and admin systems, all rolled into one.
The idea that this should free up the small research units and institutes from requiring their own costly admin staff for dealing with the day-to-day running. If successful, it was to be rolled out to the other science councils, too.
Long story short, it was an unmitigated disaster. Running wildly over budget, the cumbersome system has alleviated the need for admin staff in individual units by practically 0% drastically limited our choice of suppliers and caused no end of other issues. Especially after they fired most of the staff at Swindon who were supposed to be running it.
On top of that, the MRC had a major barney with the contractor, so the whole system is largely unsupported. This means every time a java update comes out, all the custom written components (which are primarily used by our admin for paying us, etc.) break!
Currently, the recommendation from head office is for us to stick with IE8!
You can take that recommendation and shove it up your $^&*" so far that your "£^%&^ bursts, and you get infected with !"($^% until the )(*&$% runs out your (!£$&!!!
Wait, doesn't this also imply that our head office are currently using IE8? the head office that now centrally stores all my salary and bank details?
Sorry, but every time somebody sees a few cost figures like the ones in this article, they swing around to the same failed idea. It's like the Trident programme. It may seem expensive and/or wasteful, but when you really weigh up the alternatives, it's still the most cost effective option.