Category Archives: IT projects

Civil service reform plan – real change or a tweak?

By Tony Collins

The civil service reform plan is to be published this afternoon, at 3.30pm.  The Cabinet Office minister  Francis Maude and Sir Bob Kerslake, the head of the civil service, write about it in today’s Daily Telegraph.

They say that the plan will help deliver a civil service culture that is “pacier, more innovative, less hierarchical and focused on outcomes not process”. They write:

“We also need sharper accountability, in particular from permanent secretaries and those leading major projects, and we need more digital services, better data and management information and for policy and implementation to be linked seamlessly together…”

In the same edition of the Telegraph Andrew Haldenby,  director of the independent think tank Reform, criticises the reform plan which, although not yet published, has been foretold in newspapers including the Financial Times yesterday.

He said the reform plan will “leave the flawed structures of Whitehall in place and do no more than propose some minor variations on a theme”.

We await publication of the paper before we judge it. We hope it will, at least, require the publication of “Gateway” review reports on the progress or otherwise of major IT-enabled projects.

Without timely publication of the Major Projects Authority’s Gateway reports, MPs and the public will continue to learn of failed schemes such as the NPfIT and Firecontrol when it is too late to do much about any rescue; and without contemporaneous publication there will continue to be no accountability for the rigour or otherwise of the reviews, or their outcome.

Civil service reform – meltdown or business as usual? – Institute for Government

Cabinet Office promises unprecedented openness on big, risky projects.

Civil service shake-up – Guardian

All change again for management of state IT projects in Florida

It is all change again when it comes to the management of IT and IT projects within one US state government.

According to this report, the state of Florida is preparing to do without a standalone agency that deals with technology, with the eventual demise of the Agency for Enterprise Information Technology (AEIT), a 16-person unit that helped set standards for technology purchasing and information security under the supervision of Florida’s governor and cabinet.

The Florida Legislature has passeda bill,  HB 5011, which would have replaced AEIT with an Office of State Technology (though quite how that would differ is unclear).  The Florida Governor, Rick Scott, vetoed the bill, and although the agency still exists, it will have no funding when the new fiscal year starts in July.

Many of its employees, including former state Chief Information Officer David Taylor, have already begun moving to other agencies, the report says.

As usual, the state of IT projects has come under fire with one politician, Denise Grimsley, arguing that studying some of the state’s technology initiatives – including an attempt to switch most of state government to a single e-mail system – led her to conclude that AEIT “in its current state was ill-suited to provide the statewide vision and oversight needed for certain enterprise information technology projects.”

Plus ca change.

Cabinet Office promises unprecedented openness on risky projects

By Tony Collins

The Cabinet Office has defended its decision not to publish “Gateway” review reports on the progress or otherwise of large and risky IT and construction projects.

Gateway reviews are regular, short and independent audits on the state of medium and high-risk projects. Their publication would allow  MPs and the public to have an early warning of a major project in trouble – rather than know of a project failure only after it has happened.

Campaigners have sought for a decade to have the review reports published; and the  Information Commissioner, in requiring the publishing of ID Card gateway reviews under FOI,  dismissed the generalised arguments put forward by officials for Gateway reviews to remain confidential.

The Conservatives, when in opposition, promised to publish Gateway review reports if they came to power. But departmental heads and senior officials have stopped this happening.

Now the Cabinet Office, in a statement to The Guardian, has suggested that the first annual report of the Major Projects Authority will more than compensate for the non-publication of Gateway review reports.

The statement says that the Authority’s ( delayed)  first annual report will “bring unprecedented scrutiny and transparency to our most expensive and highest risk programmes, changing forever the culture of secrecy that has allowed failure to be swept under the carpet”.

The statement continues:

“Historically, fewer than a third of government major projects have delivered to original estimates of time, cost and quality. Since April 2011 the Major Projects Authority has enforced a tough new assurance regime and begun raising leadership standards within the Civil Service.”

The Guardian asked the Cabinet Office whether the traffic light red/amber/green status of Gateway reviews will be published.  The spokesman replied:

“The annual report will contain details of the status of major projects.“

Comment:

We applaud the Major Projects Authority in scrutinising, and in rare cases helping to stop,  departmental projects that don’t have adequate business cases. The Authority’s work is vital in pre-empting ridiculous schemes such as the NPfIT.

But project  disasters that rely on  IT continue, at the Ministry of Justice for example.  Like the National Audit Office, the  Major Projects Authority has limited resources and cannot scrutinise everything. Even if it could, the system of government is not set up in such a way as to allow the Authority to have final say over whether a project is stopped, curbed or re-negotiated.

Preventing failure

Gateway review reports are a critical component in preventing IT-related project failures. If officials know the whistle is going to be authoritatively blown on their failing schemes they are likely to do all they can to avoid failure in the first place. If they know that nobody will be aware of doomed schemes until those involved have left or moved, they will have less incentive to make projects a success.

An annual report is no substitute for the contemporaneous publishing of Gateway review reports. Each Gateway review is several pages and puts into context the traffic light red/amber/green status of the project. An annual report will not contain every Gateway review report. If just the traffic light status is published that will be a start, but without the context of the report what will it mean?

[And it’s worth bearing in mind that the first annual report of the Major Projects Authority is already six months late.]

The non-publication of Gateway review reports is  a victory by senior officials over ministerial promises.  How can we believe that the coalition is committed to unprecedented openness when the final say remains with Sir Humphrey?

Cabinet Office promises to challenge culture of secrecy on IT projects.

Whitehall to relent on secrecy over mega projects?

How London IT director saves millions by buying patient record system.

By Tony Collins

An NHS organisation in London has bought an electronic patient record system for less than a third of the cost of similar technology that is being supplied by BT to other trusts in the capital and the south of England.

The £7.1m purchase by Whittington Health – a trust that incorporates Whittington Hospital near Archway tube station – raises further questions about why the Department of Health is paying BT between £31m and £36m for each installation of the Cerner Millennium electronic patient record [EPR] system under the NPfIT.

Whittington Health is buying the Medway EPR system from System C which is owned by McKesson. The plan is for the EPR to operate across GP, hospital and social care boundaries.

It will include a patient portal. The idea is that patients will use the portal to log on to their Whittington Health accounts, see and save test results and letters, and manage outpatient appointments on-line.

In a board paper, Whittington Health’s IT Director Glenn Winteringham puts the case for spending £7.1m on a single integrated EPR.  Winteringham puts the average cost of  System C’s Medway at £8m. This cost, he says, represents “significant value for money” against the average deployment costs for the NHS Connecting for Health solution (Cerner Millennium) for London of £31m. In the south of England the average cost of Cerner Millennium is £36m, says Winteringham in his paper.

He also points out that the new EPR will avoid costs for using “Rio” community systems. The NPfIT contract with BT for Rio runs out mid 2015. “From this date onwards the Trust will incur an annual maintenance and support cost. Implementing the EPR will enable cost avoidance to the [organisation] of £4m per year to use RIO (indicative quotes from BT are £2m instance of RIO and the [organisation] has 2 – Islington and Haringey).

BT’s quote to Whittington for Rio is several times higher than the cost of Rio when supplied directly by its supplier CSE Healthcare Systems. A CSE competitor Maracis has said that, during a debrief, it was told that its prices were similar to those offered by CSE Healthcare for a Rio deployment – then less than £600,000 for installation and five years of support.

In comparison BT’s quote to Whittington for Rio, as supplied under the NPfIT, puts the cost of the system at more than fifteen times the cost of buying Rio directly.

In short Whittington and Winteringham will save taxpayers many millions by buying Medway rather than acquiring Cerner and Rio from BT.

Why such a price difference?

The difference between the £31m and £36m paid to BT for Cerner Millennium and the £8m on average paid to System C could be partly explained by the fact that Whittington (and University Hospitals Bristol) bought directly from the supplier, not through an NPfIT local service provider contract between the Department of Health and BT. Under the NPfIT contract BT is, in essence, an intermediary.

But why should an EPR system cost several times more under the NHS IT scheme than bought outside it?

Comment:

Did officials who agreed to payments to BT for Cerner and Rio mistakenly add some digits?

Whittington’s purchase of System C’s Medway again raises the question – which has gone unanswered despite the best efforts of dogged MP Richard Bacon – of why the Department of Health has intervened in the NHS to pay prices for Rio and Cerner that caricature profligacy.

Perhaps the DH should give BT £8m for each installation of Cerner Millennium and donate the remaining £21m to a charity of BT’s choice. The voluntary sector would gain hundreds of millions of pounds and the DH could at last be praised for spending its IT money wisely.

Whittington buys Medway and scraps Rio – E-Health Insider

NHS IT supplier “corrects” Health CIO’s statements

MP seeks inquiry into BT’s £546m NHS deal

NPfIT go-live at Bristol – trust issues apology

Queensland audit brings in new broom to sweep away problem IT projects

There is nothing like an IT project disaster to spur the arrival of a new broom designed to ensure that it will never happen again.
 
Until next time.
 
According to the Queensland Courier-Mail in Australia, every computer system used across Queensland’s public service will be probed for flaws and inefficiencies under a A$5.2m audit set up to head off another costly IT project.
 
It follows the emergence of problems with a Queensland Health health payroll project which is now being audited after it was revealed that the costs required to put the project right would increase to over $400 million.
 
Newly appointed Queensland IT Minister Ros Bates ordered the audit to uncover how IT is being used across the government’s 19 departments and find where savings can be made.
 
The audit team, which comprises a seconded army of 32 public servants, will present its findings by the end of October.
 
In addition to the audit, as part of a push to achieve government IT efficiencies, departmental chief information officers have been stripped of their autonomy and will now report to the Queensland Government CIO.
 
Meanwhile, despite its payroll project problems, Queensland Health has won an excellence in eGovernment award for a project dubbed ‘The Viewer’ that has streamlined how clinicians access patient information about their patients.
 
The Viewer is a read-only web-based application that sources key patient information from existing Queensland Health systems, providing consolidated information in one place.
 
Before the project’s  implementation, patient data was stored in a range of paper and electronic record systems in over 260 different facilities.
 

Healthspace was failing in 2010 – why is it being kept alive?

By Tony Collins

“Too many failing projects are continued for too long” – Ian Watmore, House of Commons, 2009.

HealthSpace, a centrally-run system that has, for years, provided unneeded work for consultants based at Connecting for Health, software developers, civil servants, and IT suppliers,  at a cost of tens of millions of pounds, is to close “from” March 2013.

A report commissioned by the Department of Health and NHS Connecting for Health in 2010 found that the system had never worked satisfactorily. But the Department and CfH has kept the project going, paying consultants and IT suppliers, although it was clear from an early stage that the scheme was doomed.

Will the Department of Health continue paying consultants and IT suppliers for a system that is to be cancelled?

HealthSpace was designed to be a personal health organiser. It was based on a good idea – that some patients could benefit from access to their health records – but the technology was too complicated and never fit for the public to use. It is said that those involved in the project spoke in a technological, managerial and procurement language – and rarely mentioned patients.

The Guardian this week reports Charles Gutteridge, national clinical director for informatics at the Department of Health, as saying that Healthspace is “too difficult to make an account; it is too difficult to log on; it is just too difficult.”

The Department of Health later told The Guardian that Healthspace would be closed down “from” March 2013.

In 2010 a report by Trisha Greenhalgh and her team, The devil’s in the detail, which was commissioned by CfH, found that HealthSpace had involved professional advisers, software developers, security testing contractors, business managers who wrote the benefits realisation cases, lawyers who advised on privacy and regulatory matters and many others.

Yet the system was doomed from the start. Greenhalgh’s report in May 2010 revealed that:

“Project leads from participating NHS organisations repeatedly raised concerns with Connecting for Health in monthly management meetings about the low uptake of advanced HealthSpace accounts, since the benefits predicted, such as lower NHS costs and patient driven improvements to data quality, could not possibly be achieved unless the technology was used.”

Comment:

It’s not known how many millions has been wasted – and continues to be wasted – on Healthspace; and it is difficult to avoid the conclusion that the continuance of the scheme benefits nobody except those who are paid to work on it, which includes contractors and IT suppliers.

Why is the scheme to be cancelled “from” 2013, when it should have been cancelled when Trisha Greenhalgh and her team produced their report in May 2010?

Shouldn’t ministers have some control – especially given that we are supposed to be in an age of public sector austerity? Ian Watmore, Permanent Secretary at the Cabinet Office and former Government CIO, has said that failing projects are continued for too long. He said that in 2009. So isn’t it time ministers and particularly civil servants applied the principle of ‘fail early, fail cheaply‘?

Link:

In 2010 ComputerworldUK had an account of how Healthspace was being kept alive unnecessarily.

Fire ‘superstations’ without software cost £1m a month – The Times

By Tony Collins

The Times reports today that taxpayers are paying more than £1m a month on the rent and upkeep of fire control rooms across England that have never been used. The purpose-built control centres look ready for immediate use, with open-plan desks fitted with desktop monitors and keyboards, and huge screens on a wall at the front of the control rooms which are supposed to help fire and rescue crews mobilise appliances and manage incidents.

Only there’s no working software.  The Department for Communities and Local Government negotiated the end of a contract with the main contractor EADS for software to run the regional control centres in December 2010. Officials concluded that the software could not be delivered within an acceptable timeframe. The regional control centres were completed before the IT project was cancelled.

The cost of the centres has been uncovered after a request under the FOI Act. The Times devotes much of its page three to a story under the headline:

Revealed: scandal of the £1m-a-month fire service ‘superstations’ lying empty.

Only one of nine regional centres is in use. The other eight incur rent, electricity, water and repair costs at £1,134,566 a month. Costs will be incurred for years because there are no break clauses in the agreements to lease the buildings. Two leases come to an end in 2027, one in 2028, two in 2032, three in 2033 and one in 2035.

A spokesman for the Department said that agreement has been reached for a further two of the buildings to be used by local fire authorities. Officials are searching for public or private sector tenants to occupy the other regional centres.

Lord Prescott, the former Deputy Prime Minister, who authorised the start of the technology project in 2004,  said he had been kept in the dark by civil servants on the rising costs of the scheme. He said it had been on budget when he left the department in 2007.

Eric Pickles, the Communities Secretary, said the failure of Firecontrol was an “expensive reminder of why you can’t trust Labour to run anything”. But the Coalition’s coming to power has not stopped central government IT-related failures.

Why Firecontrol failed

Firecontrol  followed the same tracks to a cliff edge that have caught out civil servants, ministers and suppliers on other government  computer-related projects.

The National Audit Office and the Public Accounts Committee found that  the Firecontrol project was rushed, had little support from those who would use it, costs and complexity were underestimated, there was an over-reliance on consultants and a lack of accountability for decisions made  – or not made.

The idea was to replace 46 local control rooms with nine, linked regional centres, which would be equipped with new standardised computer systems to handle calls, mobilise equipment and manage incidents.

But the project was cancelled in December 2010 with ministers unsure the technology would ever work. The NAO estimates that £469m will be wasted on the project.

The NAO found that the scheme was “flawed from the outset”, largely because local fire and rescue officers did not want regional centres or major changes in the way they worked.  Introducing any large new system is difficult but with enthusiastic support serious problems can sometimes be overcome; but introducing a complex new system without support from those who would use it means staff will have little incentive to find ways around problems.

The NPfIT [National Programme for IT in the NHS] failed in part because it lacked support among GPs and NHS staff; and the complexity of introducing standardised technology in semi-autonomous hospitals – each one with different ways of working – was underestimated. It was the same with Firecontrol.

The complexity of introducing standardised systems in regional centres with no goodwill among staff – was underestimated.  From the start many local fire and rescue officers criticised the lack of clarity on how a regional approach would increase efficiency. “Early on, the Department’s inconsistent messages about the regionalisation of the Fire and Rescue Service led to mistrust and some antagonism,” said the NAO.

The technology project was rushed while local fire crews were excluded from project discussions. “The project progressed too fast without essential checks being completed. For example Departmental and Treasury approval was given without proper scrutiny of the project’s feasibility or validation of the estimated costs and savings,” said the Public Accounts Committee. The project went ahead before the full business case was written.

A review of the project as early as April 2004 found that the scheme was already in poor condition overall and at significant risk of failing to deliver. But the “Gateway” review report was kept secret for seven years.

Is the stage set for IT disasters in government to continue? So far the Coalition has decided, like Labour, to keep secret all internal reports on the progress or otherwise of its mega projects, including Universal Credit, though the policy on secrecy may be about to change, which Campaign4Change will report on separately.

Firecontrol – same mistakes repeated on other projects.

The real reason NHS Risk Register is a State secret?

By Tony Collins

Yesterday  (15 May 2012) the Information Commissioner Christopher Graham issued a finely-crafted report to Parliament on his concerns about the Government’s use of a ministerial veto to stop publication of the Transition Risk Register relating to health service reforms.

Graham’s concern is that the veto represents a new and worrying approach to Freedom of Information.

Graham cannot do anything about the veto but he can warn MPs when he feels the Government has gone too far. This he has done in his report which says that the previous three occasions on which the ministerial veto has been exercised related to the disclosure of Cabinet material under FOIA. Now the Government has applied the veto to information held by the Department of Health.

Says yesterday’s report: “ The Commissioner would wish to record his concern that the exercise of the veto in this case extends its use into other areas of the policy process. It represents a departure from the position adopted in the Statement of Policy and therefore marks a significant step in the Government’s approach to freedom of information.”

The Government’s decision to ban publication of the health service risk register is particularly relevant to IT-related projects. This is because the government uses exactly the same arguments to ban contemporaneous publication of Gateway reviews and other independent assessments of IT-related projects and programmes.

Risk registers and Gateway reviews of IT-enabled change projects are similar. They are designed to identify all the main risks associated with the project or programme and have a red/amber/green system of rating the risks.

The Government’s argues that risk registers (and Gateway reviews) are researched and written in a “safe space” that allows civil servants to give advice and recommendations in a frank way. This candour would be compromised if the civil servants thought their advice would be published, says the Government.

In issuing a veto on the health risk register Andrew Lansley, the Health Secretary said, in essence, that he could not trust civil servants to be entirely honest if they knew their reports would be made public.

Said Lansley:  “If risk registers are routinely or regularly disclosed at highly sensitive times in relation to highly sensitive issues, or there is legitimate concern that they could be, it is highly likely that the form and content will change: to make the content more anodyne; to strip out controversial issues or downplay them; to include argument as to why risks might be worth taking; to water down the RAG [red,amber, green] system.

“They would be drafted as public facing documents designed to manage the public perception of risk; not as frank internal working tools. These consequences (many of them insidious) would be to the detriment of good government.”

Lansley also wanted to ban publication to pre-empt sensational media coverage.  In this he was repeating the arguments made by civil servants under Labour who refused, under the FOI Act, to publish risk registers and Gateway reviews.  Said Lansley “I consider that the form and the frankness of the content of TRR [health service Transition Risk Register] would have been liable to create sensationalised reporting and debate.

“The content would also have been inherently highly open to misinterpretation by both the press seeking a headline and/or for political reasons. The likelihood of this occurring is particularly acute where the subject matter is, as with the Transition programme, controversial and the proposals at a highly sensitive stage.”

But the Commissioner did not accept that disclosure of the Transition Risk Register would affect the frankness and candour of future risk registers. The Commissioner also said that a ministerial veto should, by law, be made only in exceptional circumstances.  But the Government has failed to explain why there are exceptional circumstances in this case.  Said the Commissioner:

“The Commissioner does not consider that sufficient reasons have been given as to why this case is considered to be exceptional, particularly in light of the [Information] Tribunal’s decision dismissing the Department’s [Department of Health’s] appeal.

“The Commissioner notes that much of the argument advanced as to why the case is considered to be exceptional merely repeats the arguments previously made to Commissioner and the Tribunal and which were in part dismissed by the Tribunal.”

Graham concludes:

“In light of previous commitments he has made, and the interest shown by past Select Committees in the use of the ministerial veto, the Commissioner intends to lay a report before Parliament under section 49(2) FOIA on each occasion that the veto is exercised. This document fulfils that commitment.

“ Laying this report is an indication of the Commissioner’s concern to ensure that the exercise of the veto does not go unnoticed by Parliament and, it is hoped, will serve to underline the Commissioner’s view that the exercise of the ministerial veto in any future case should be genuinely exceptional…

“The arguments employed by the Department at the Tribunal and by the Secretary of State in explanation of the subsequent veto, both in the Statement of Reasons and in exchanges in the House of Commons around the Ministerial Statement, certainly use the language of ‘exceptional circumstances’ and ‘matter of principle’. But the arguments are deployed in support of what is in fact the direct opposite of the exceptional – a generally less qualified, and therefore more predictable, ‘safe space’.

“As such, the Government’s approach in this matter appears to have most to do with how the law might be changed to apply differently in future. This question falls naturally to consideration by the Justice Committee who have been undertaking post-legislative scrutiny of the Act.”

Comment:

The reason for the veto in the case of the health service risk register has little to do with protecting a safe space for frank discussion.

Civil servants already compile risk registers, Gateway reviews and similar reports on the basis that they may, at some point, be published. Officials are no more likely to be frank if they know their reports will be confidential than more guarded if they know the documents will be published. They will do what their job entails. Their job requires honesty. They will do that job whether or not reports are published.

The real reason for the veto – and the refusal of departments to publish all contemporaneous internal reports on large and complex programmes, particularly those with a large IT element – is that some new schemes within Government operate at a shambolic level.

Any new government, whatever its hue, soon learns to keep secret the fact that such programmes are sometimes characterised by near anarchy.

One outsider to the UK government, Australian David Pitchford, discovered the truth when he became Executive Director of Major Projects within the Efficiency and Reform Group which is part of the Cabinet Office. Pitchford may not have realised his comments would be reported when he told a project management conference in 2010 that “nobody in the UK Government seems to know how many projects they have on the books, nor how much these are likely to cost”.

He found that projects were launched, and continued, without agreed budgets or business cases.  Today, there is better scrutiny of major projects, by the Cabinet Office’s Major Projects Authority. But the MPA is limited in what it can do or scrutinise. Which leaves government in a general mess when it comes to implementing anything new.

Evidence for this mess comes from the National Audit Office. Its auditors tend to investigate departments as a whole more than they do specific projects but when they do the careful reader can see that projects such as the Rural Payments Agency’s Single Payment Scheme (a scant regard for public funds, said the NAO) and the C-NOMIS project for the prison service (kindergarten mistakes, said chair of Public Accounts Committee) were without a structure. Chaos prevailed – and ministers were among the last to know.

Publication of project reports encourages professionalism. Departmental heads can be held to account if Parliament knows what has gone wrong. That’s precisely the reason departmental heads don’t want risk registers and other project reports published. It’s why all internal reports on Universal Credit, the government’s biggest IT-related project, are kept secret in spite of FOI requests.

The ministerial veto in the case of the NHS risk register is the government and civil service colluding in keeping the public and Parliament in ignorance of internal management’s inability to run complex new projects and programmes in a professional way.

Ministers and permanent secretaries don’t especially mind media criticisms that are based on speculation. They don’t want their critics having authoritative internal reports. That’s why the Cabinet agreed the health service veto – and it’s one reason the government has a not-very-hidden aversion to the FOI Act.

The coalition cannot justly claim to cherish open government while it is refusing so many requests under FOI to publish contemporaneous taxpayer-funded reports on its major schemes.

We agree with the Information Commissioner that use of the ministerial veto is a step too far. No number of announcements by the Cabinet Office on open government will gloss over the fact that the coalition is even more secretive about mega-projects than Labour. That’s saying something.

US federal CIO points to greater consolidation of government email systems

By David Bicknell

It is interesting to see how the US Federal CIO Steven VanRoekel is pushing US departments to rationalise their email systems.

The Labour Department is the latest to be earmarked for email consolidation with seven contracts for separate email systems set to be shrunk down to one, the Washington Business Journal reported.

The federal government needs to eliminate duplication to save dollars but also to free up time and resources in agencies’ acquisition offices so more effort can be put into transformative information technology projects, VanRoekel told the recent Congressional Forum on Technology.

“There’s an effort under way to start to look at how many [information technology] systems people are running in these agencies,” he said. “How many email systems? At the Department of Labor there are seven. There’s an opportunity there to save money.”

VanRoekel pointed to rationalisation success at other departments. Three years ago, he suggested, the Agriculture Department was managing 21 email contracts and 1,000 mobile contracts to implement primarily a BlackBerry service.

The department reduced those numbers to one and three respectively. The new email system cost one-third as much as the systems that had been in place, and the mobile computing blanket purchasing agreements saved Agriculture 18 percent from its budget

Consolidation efforts also need to be strategic to ensure fair competition among contractors, VanRoekel said.

“Should we go extreme on consolidation, and run one email system? The Canadian government has done this; one email, one procurement system,” he said. “Contemplating how we’d manage that at our scale is one factor. But also, if we the government were to pick the winner, we would do a great disservice to business. We need to strike that balance.”

Australian payroll IT project cost grows from $64m to over $400m

David Bicknell

In Australia, the state government in Queensland is coming to terms with a failing IT project whose cost has grown from $64.5m to $412m.

The payroll system for Queensland Health first went live in early 2010, prompting thousands of employees to be underpaid, overpaid or not paid at all, and triggering a subsequent critical report by the state’s Auditor General. 

Late in 2010, the Bligh government said $209m would need to be spent to fix the system in the following three financial years, on top of the original $64.5 million implementation cost.

Now, according to The Brisbane Times, the cost of the failed payroll system will reach an estimated $412 million by the end of June this year, with further costs likely to be incurred in the future.

Failure to prepare: Government slammed over health payroll bungle

Smart state’s technology spending up in the air