Category Archives: IT-related failures

RBS/Natwest: Some lessons from the IT crash – Bank of England Governor.

By Tony Collins

Sir Mervyn King, Governor Bank of England, promised today that there would be a “very detailed inquiry” once problems at RBS/Natwest are back to normal.

Such a report would be unusual because the cause or causes of IT-related crashes in the public and private sectors are usually kept secret unless in rare cases a legal action comes to court.

Mervyn King told the Treasury Committee today:

“Once the current difficulties are over then we will need the FSA to go in and carry out a very detailed investigation to find out first of all what went wrong but even more importantly why it took so long to recover.

“Computer systems will always go wrong from time to time. The important things are your back-up systems and the time it takes to implement recovery. As of now we have kept in very close touch. My office was in touch with senior RBS management right through the weekend. Our banking director was in touch with RBA and FSA on this right since this problem began … It is still going to take time to catch up, to get back to normal.

“The important thing now is that we provide whatever support is needed to let them put it right. Once it is back to normal then we must carry out a very detailed inquiry.

“To my mind, one of the big lessons from this is that it shows everyone is how important the basic functions of banking actually are: what can go wrong when the system of payments from person to another is interrupted. Fortunately it has been one bank, albeit a very big bank, and customers of that bank have been affected, and of course customers of other banks have been affected, and payments have not gone through.

“I hope this is a reminder, a demonstration, to everyone, for example, of what might have happened if we had not rescued RBS in the autumn of 2008. The whole payment system would have collapsed. [It is] why it is so important to ensure you have a banking system where the people running it are completely focused on this essential service function of banking to provide … customers with a functioning payment system.

Learning from supermarkets.

“I have been driven by the belief that the nature of banking and providing these kinds of services is very different from investment banking operations. Those are important but they are very different. When you go out and see how supermarkets operate, the senior management is utterly focused on ensuring that the IT systems, the ordering systems, the delivery system, works hour by hour. That is very important to ensure that that is true of the banking system as well…”

Comment:

History  is, to some extent, the story of the unforeseen, in which case a published report on the cause of the problems at RBS/Natwest could be helpful to other banks and major organisations whose ageing systems are vulnerable to an unforeseen failure of huge proportions.

A published report on the crisis may show systemic management failures. The mere fear of such a report would be an added deterrent – additional to potential losses and payments of compensation – to any bank that does not give the attention it should to operational systems, even when those systems support a retail banking operation that may represent a small part, perhaps only 2% of a bank’s balance sheet.

It is ironic that RBS is publicly owned. Will the IT disaster now be added to the list of other public sector failures? Did RBS, now in the public sector, drop its IT-related standards and caution in part because the commercial imperative was absent?

Natwest/RBS – what went wrong?

Natwest/RBS – what went wrong?

By Tony Collins

Outsourcing to India and losing IBM mainframe skills in the process? The failure of CA-7 batch scheduling software which had a knock-on effect on multiple feeder systems?

As RBS continues to try and clear the backlog from last week’s crash during a software upgrade, many in the IT industry are asking how it could have happened.

Stephen Hester, RBS’s boss, told the BBC today:

“In simple terms there was a software change which didn’t go right. Although that was put right quickly there then was a big backlog of things that had to be reprocessed in sequence. That got on top of our technical teams … it is like the landing path at Heathrow. Once you get out of sequence it takes a time to get back into sequence even if the original fault is put right.

“Our people are working incredibly hard … I am pleased to report that as of today RBS and Natwest systems are operating normally.

“We need to make sure they stay normal for the next few days. There is still some significant catch-up today, much less tomorrow and so on as we go through the week.”

The immediate technical cause of the problems might not have been too difficult for those inside the bank to establish – but finding out how and why it happened, why processes were not in place to stop a backlog of work building up, and why testing of the upgrade did not pre-empt the failure may take weeks and possibly months to establish.

Attributing blame could take many years. After BSkyB appointed EDS to supply a CRM system in 2000, and the project failed, it was ten years later before a court reached a judgment on blame. The cause of the failed project was never definitively established.

Official cause of system crash

The official cause of RBS/Natwest’s problems was given at the weekend by Susan Allen, Director of Customer Services, RBS Group which includes Natwest and Ulster Bank. She told Paul Lewis of BBC’s Moneybox programme:

“Earlier this week we had a problem in our overnight backup. So a piece of software failed that started all the updates that happened to our systems overnight.

“What that has meant practically is that information on customers’ accounts has not been updated… It is horrendous.

“The underlying problem has been fixed, so the computer software that failed has been replaced. That is in and working. The challenge we now have is bringing all the systems back up and working through all the data that should have been gone through over the last three nights …

“We have 12 million customers in Natwest and RBS and just over 100,000 in Ulster Bank. So it is affecting a serious number of people. It is having a terrible impact.

“We are encouraging all of our customers to call us, come and see us in our branches … we have branches open late .. and have doubled the number of people on the phone. Call centres are open 24 hours a day.”

Call centres use 0845 numbers which are chargeable for some. Lewis asked, Why are you making people pay to fix a problem that’s your fault?

“Customers should not be having to pay for those calls,”replied Allen. “If that is a problem for people we will take a look at that.”

Lewis: Will you re-imburse people for their calls?

“Absolutely. We recognise there will be lots of different expenses as a result of this. We apologise and want to make sure they are not out of pocket. If people have got claims they should put them through to us…we will need the information to deal with the claims.”

Lewis: Will you refund charges by credit card companies for late payments?

“We will. We will… we will make sure nobody is out of pocket… in one instance we got cash in a cab to a customer’s home… clearly we trust our customers so if we can see that somebody has a certain amount coming in every week we will give them money against that. So we ask people to come in and bring identification with them such as their bank card, we will do what we can to help.

“We will look after our customers. We realise this has had a huge impact on people. We are not underestimating it … clearly there are things that have gone wrong and we cannot put everything right.”

Lewis: How much damage has this done to the reputation of the bank?

“Time will tell. For us it is pretty devastating. We pride ourselves on being a bank that really cares about our customers and wants to deliver great service. We absolutely mean it.”

Lewis: Should you get a bonus?

“We only get performance bonuses when we perform and this has not been a good performance.”

Comment:

Her explanation of the cause of the IT crash is unclear but otherwise Susan Allen’s answers to Paul Lewis’s questions were exemplary. Her openness and unaffected humility is surely the best way to handle a PR crisis. Small comfort for the millions affected though.

Technical cause of the crash?

Some of those commenting to The Register appear to have a good knowledge of RBS systems. There are suggestions RBS has lost some important IBM mainframe software skills in outsourcing.

One or two have suggested that the crash was caused by a failure of the bank’s CA-7 batch scheduling software. In February RBS had an “urgent requirement” in Hyderabad, India, for people with four to seven years experience of CA7.

One comment on The Register said that RBS runs updates on customer accounts overnight on an IBM mainframe, via a number of feeder systems that include BACS. “The actual definitive customer account updates were carried out by a number of programs written in assembly language dating back to about 1969-70, and updated since then. These were also choc-full of obscure business rules … and I do not believe anyone there really knew how it all worked anymore, even back in 2001…

“Of course the moral is complex mainframe systems require staff with the skills, and in this case, the specific system knowledge to keep things smooth. The fewer of these you have, the more difficult it is to recover from problems like this.”

Robert Peston, the BBC’s Business Editor, asks whether outsourcing was to blame.

“In my conversations with RBS bankers, there is an implication that outsourcing contributed to the problems – though they won’t say whether this is an issue of basic competence or of the complexities of co-ordinating a rescue when a variety of parties are involved.”

An RBS spokesperson told The Register that the software error occurred on a UK-based piece of software.

Some lessons from the crisis – Bank of England Governor.

How CIOs and IT suppliers view GovIT change

By Tony Collins

CIOs and IT suppliers give their views on Government ICT in an authoritative report published today by the Institute for Government

Inside the wrapper of generally positive words, a report published today on government ICT by the Institute for Government suggests that major change is unlikely to happen, despite the best efforts of  CIOs and the Cabinet Office minister Francis Maude.

The report “System upgrade? The first year of the Government’s ICT strategy”  says progress has been made. But its messages suggest that reforms are unlikely to  amount to more than tweaks.

These are some of the key messages in the report:

If the minister and CIOs cannot direct change who can?

–          “… while the Minister for the Cabinet Office and government CIO are viewed as being responsible for delivering the ICT strategy (for example by the Public Accounts Committee) they currently lack the full authority to direct change.”

Not so agile

–           “While just over half of government departments may be running an agile project, there were concerns that these were often very minor projects running on the fringe of the departments.”

–          “We heard concerns from the supplier community and those inside government that in some areas projects may be being labelled as ‘agile’ without having really changed the way in which they were run.”

–          “CIOs should question whether they are genuinely improving the ways that they are working in areas such as agile, or whether they are just attaching a label to projects to get a tick in the box,” says the Institute for Government.

Savings not real?

–          “There was also an element of challenge to the savings figures provided by government. For example, some from government and the supplier community questioned whether the numbers represented genuine savings or just cuts in the services provided or deferred expenditure. “

–          “Others … cautioned that project scope creep or change requests could reduce actual savings in time. It was pointed out that the NAO [National Audit Office] will scrutinise whether savings have been achieved in future, which was seen as a clear incentive for accuracy – but there were, nonetheless, concerns that pressure to provide large savings figures meant that inadequate attention might be paid to verifying the savings …”

CIOs want faster ICT progress

–          “Among the CIOs we interviewed, there was a clear recognition that government ICT needed to improve.  ‘You expect an Amazon experience from a government department…’ ”

Lack of money good for change

–          “As one ICT lead noted, a lack of money was ‘always helpful’ in driving change as it promoted cross-government solution-sharing and led to more rigour in approving new spend.”

–          “Both ICT leaders and suppliers felt that the ICT moratorium had been a helpful stimulus for increased focus on value for money.”

–          “Though some of the larger suppliers felt bruised by the ‘smash and grab’ of initial interactions with the Coalition government, there was a recognition that the moratorium had been about ‘stopping things which were inappropriate’”.

GDS challenges norms

–          “New ways of working in the new Government Digital Service and the opening up of government through the Transparency agenda were also seen as providing a challenge to existing norms.”

–          The new Government Digital Service (GDS) is providing an example of a new way of doing things, and was pointed to by those inside and outside of government as embodying mould-breaking attitudes, using innovative techniques and … delivering results on very short timescales. Several interviews mentioned being invigorated by the positive approach of the GDS and their focus on delivering services to meet end-user needs.

ICT so poor staff circumvent it

–          “Public servants are increasingly frustrated that the ICT they use in their private lives appears to be far more advanced than the tools available to them at work. Indeed, there are already examples of employees circumventing the ICT that government provides them as they attempt to perform their job more effectively: creating what is known as a system of ‘shadow ICT’ that creates significant challenges for maintaining government security, collaborative working and government knowledge management.”

Joined-up Govt impossible?

–          “The possibility that departmental incentives continue to trump corporate contributions is further suggested by our survey results. Individuals do not yet feel that corporate contributions are valued or rewarded … elements of the [ICT] strategy call for departments to give up an element of autonomy and choice for the ‘greater good’. Several CIOs expressed concerns that by adopting elements of the strategy that were being developed or delivered by another department, they would end up having to accept a service that had been designed  around the needs of a different department.”

–          “Similarly, there were concerns that the host department would be at the top priority in the event of any problems or opportunities to develop services further. This speaks to a strongly department-centric culture. Suppliers noted, for example, that certain parts of government were still happy to ‘pay a premium for their autonomy’.”

–          “… the vast majority of those we spoke to suggested that departmental interests would almost always ultimately trump cross-government interests in the current government culture and context.”

–          “CIOs felt that they would be rewarded for delivery of departmental priorities – not pan-government work …”

CIO Council frustrations

“CIOs noted that there could be a discrepancy between what got agreed at the old CIO Council meetings and what people actually went away and did. Larger department CIOs also expressed frustration that – despite holding the largest budgets and carrying the largest delivery risks – their voices could easily be outweighed by the multitude of other people round the table.”

“The delivery board model [which has superseded CIO Council] has been recognised by both big and small departments as pragmatically dealing with both sides of this issue. Larger departments now form part of an inner-leadership circle, but with this recognition of their clout comes additional responsibility to own and drive through parts of the strategy… the challenge will now be to ensure that the ICT strategy doesn’t become a ‘large department-only’ affair and that other ICT leads can be effectively engaged.”

Canny suppliers?

–          The majority of ICT leads …stated that they believed the ICT strategy would benefit their department and government as a whole. This confidence was less apparent in the attitudes of suppliers who were, on the whole, more sceptical of government’s ability to drive change, though again generally supportive of the direction of travel.

A toothless ICT Strategy is of little value?

–          “…There was also a lack of clarity on how different elements of the [ICT] strategy would be enforced. As one ICT leader commented … ‘Is this a mandatable strategy or a reference document?’ ”

–          … “there are risks that the strategy could be delivered in a way that still doesn’t transform ICT performance.”

Francis Maude an asset

–          “Government ICT has also been a priority of the Minister for the Cabinet Office, Francis Maude – giving the [change] agenda unprecedented ministerial impetus. He has been a visible face of ICT to many inside and outside of government, from demanding departmental data on ICT to being heavily involved in negotiations with ICT suppliers. Though few of his ministerial colleagues appear as passionate about improving government ICT, the CIOs we interviewed overwhelmingly expressed confidence that they would receive the support they needed to implement the changes in ICT.”

Smaller-budget CIOs out of the loop?

–          “With the CIO Council in hiatus for most of the last year, the CIOs of smaller departments felt out of the loop …”

Most ICT spending is outside SW1

–          “Suppliers and other ICT leaders pointed out, rightly, that the vast majority of ICT expenditure happens outside SW1 – with agencies, local government and organisations like primary care trusts and police forces still determining much of the citizen and workforce experience of ICT.”

SMEs still left out?

–          “Smaller suppliers … were generally encouraged that government was trying to use more contractual vehicles which would be open to them – but noted that it was ‘still extremely difficult to get close to government as an SME’.”

Who knows if use of ICT is improving?

–          “Government still lacks the information it needs to judge whether use of ICT across government is improving.”

System upgrade? The first year of the Government’s ICT Strategy.

Too early to claim success on GovIT – Institute for Government

Is internal audit a waste of money?

By Tony Collins

Today’s National Audit Office report “The effectiveness of internal audit in central government” raises questions about whether the £70m cost of internal auditors is a pointless expense.

Internal auditors are supposed to be the “eyes and ears” in the organisation to highlight what is going wrong.  But their reports are kept secret – so why should civil servants take any notice of them, and what incentive do the internal auditors have to blow the whistle on failing schemes if they are going to be ignored?

The NAO suggests that internal audit has not been helpful in providing early warning of IT-repeated disasters such as Firecontrol. But it does not recommend that internal audit reports are published. Neither does yesterday’s Civil Service Reform Plan.

The NAO says

“Our value-for-money studies, such as the procurement of Type 45 destroyers and the development of new fire and rescue regional control centres, have identified many instances where there has been poor value for money because core systems have not provided sufficiently realistic, robust or comprehensive information to allow effective oversight and decision-making.

“In many cases these weaknesses have not been identified by internal audit.”

The NAO concludes in today’s report that the £70m spent annually on internal audit is “poor value for money”. Internal audit in central government employs 1,000 people says the NAO.

The effectiveness of internal audit in central government – today’s NAO report

Gateway reports on major projects to remain secret?

By Tony Collins

Comment

The civil service reform plan, which was published yesterday, is disappointing. It is so consensual that it has nothing particularly punchy to offer. It reads like the report of a tennis club match in which the finalists were such good friends that neither wanted to win; and each surrendered alternate points until those watching drifted into the bar.

The reform plan has been approved by senior civil servants and even former Labour ministers. In the House of Commons yesterday Labour’s spokesmen reacted with indifference and unions too have said little.

One reason, perhaps, is that the plan is full of good intentions that promise further documents and consultations that are full of good intentions. In short there’s nothing for potential opponents to worry about.

On improving the delivery of major projects, the reform plan is vague to the point of being self-mocking. It proposes:

– Requiring greater testing and scrutiny of major projects by departmental boards and the [Cabinet Office’s] Major Projects Authority before they move to full implementation;

– Regular publication of project progress and the production of an annual report on progress, scrutinised by the Departmental Board;

–  Commencing training of all leaders of major projects through the Major Projects Leadership Academy by the end of 2014; and

– Significantly reducing the turnover of Senior Responsible Officers.

The phrase “significantly reducing” means nothing in practice; and does the promise of “regular publication of project progress reports” mean anything in practice, other than, perhaps, the publication of press releases on project progress written by the PR departments of HMRC, the DWP and the MoJ?.

Cabinet Office minister Francis Maude could have confronted permanent secretaries with an important policy change that required the civil service to publish independent Gateway review reports on the progress or otherwise of major IT and construction projects. Perhaps Maude has not done so because he wanted consensus. But he has probably ended up with a reform plan that nobody believes in and to which nobody objects.

The Cabinet Office’s Major Projects Authority will do its best to stop IT-related project failures but it has limited control and civil service secrecy working against it. The reform plan changes none of this.

Doubtless the disasters will continue.

Civil Service Reform Plan

Useful critique of Civil Service Reform Plan by Institute for Government.

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

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?

Francis Maude talks open govt – and Whitehall does the opposite

By Tony Collins

“If people do not know what you’re doing, they don’t know what you’re doing wrong.” – Sir Arnold Robinson, Cabinet Secretary in a discussion on open government in Yes Minister.

Francis Maude, the Cabinet Office minister, said all the right things at the Intellect World Class Public Services conference 2012.

He said that:

– smaller, innovative and efficient suppliers were finding themselves locked out of the supply of services to Government because of what was described by Parliament as a powerful “oligopoly” of large suppliers

– for the first time in Government “we are using agile, iterative processes, open source technology platforms and world-class in-house development teams alongside the best digital innovation the market can offer”

– “We must eliminate failure waste. At the moment, a large proportion of our service delivery costs are incurred through incomplete or failed digital transactions. And these transactions create cross-channel duplication, which burdens the user and costs Government a huge amount in repeated costs. For HMRC alone, they estimate that 35% of calls to its contact centres are avoidable, which would save £75m.”

– “Transparency is a defining passion for this Government …”

Comment:

How much influence does Maude really have? Can he persuade permanent secretaries to effect major change? The evidence so far is that departmental officials and Maude have different ideas on what reform means.

In “Yes Minister” civil servants were proud of a new hospital that was the best run and most hygienic in the country, with no medical staff, 500 administrators and no patients.

Maude may also recall that Antony Jay and Jonathan Lynn, the acclaimed writers of Yes Minister, spoke of the Whitehall law of inverse relevance – “the less you intend to do about something, the more you have to keep talking about it”.

Open government? 

Perhaps civil servants are letting Maude get on with talking the talk while they find every way to keep things much as they are. A good example: The Guardian reported yesterday that a key part of the Government’s transparency drive has stalled amid reports of ministry opposition.

The paper’s political editor Patrick Wintour reported that plans to publish regular ‘traffic-light’ progress reports on large, costly and risky IT projects “appear to have been shelved”.

When it comes to IT this could have been the coalition’s most important single reform. It would have given MPs and the public a way of knowing when mega projects such as Universal Credit are failing. Usually we don’t know about a failed IT-related project unless there is a leak to the media, or the National Audit Office finds out and decides, with its limited budget, to do a study.

Sir Bob Kerslake, who is head of the civil service,  had indicated to MP Richard Bacon that “Gateway” review reports on large and risky IT and construction projects may be published in the civil service reform plan which is expected to be released this month.

Gateway reports to go unpublished?

Now it seems that departmental civil servants  have persuaded the Sir Bob not to publish “Gateway” reports. So the secrecy over the progress or otherwise of government mega projects is set to continue.

Yes, civil servants will allow the Cabinet Office to have its way on the publication of data about, say, some government spending. But it’s becoming clear that the civil service will not allow any publication of its reports on the progress or otherwise of major projects. It has been that way since Gateway reviews were introduced in 2001.

Some senior officials – by no means all – say they want a confidential “safe space” to discuss the progress of projects. The reality is that they do not want outsiders – MPs, the media and NAO auditors – meddling in their failing schemes – schemes such as Firecontrol and e-filing at the Ministry of Justice.

Unlike Maude, senior civil servants have what Jay and Lynn call a “flexible approach to open government”. This means in practice that Whitehall will happily release data – but not project reports on which the civil servants themselves can be judged.

Activity is not achievement

Maude’s speeches will give the impression of activity. But activity is the civil service’s substitute for achievement. I quote Jay and Lynn again, in part because their depiction of Whitehall seems to have been taken as serious wisdom by those officials who think Sir Humphrey a character worth living up to.

It’s time Maude and his team got a grip on departments. Until they do, permanent secretaries and their senior officials will regard Maude as trying to get out of situations that don’t need getting out of.

Whitehall to relent on secrecy over mega projects?

The empty hospital – Yes Minister

Government’s transparency drive stalls.

Whitehall to relent on secrecy over mega projects – after 10-year campaign?

By Tony Collins

The Cabinet Office may be about to change its decade-old policy of not publishing reports on  the progress or otherwise of its large, costly and risky IT-based projects.

A change of policy from secrecy to openness would give MPs and the public warning of when a major project is in trouble and needs rescuing or cancelling.

Parliament last to know

For more than a decade campaigners have sought to persuade successive governments to publish “Gateway” reviews, which are short independent audits on the state of big projects.  The secrecy has meant that Parliament is usually the last to know when new national schemes go wrong. IT-related failures have hit many public services including those related to tax, benefits, immigration, passports, the fire service, prisons, schools examinations, student loans, the police and health services.

Now Sir Bob Kerslake, head of the civil service, has hinted to campaigning Conservative MP Richard Bacon that the Cabinet Office may change its policy and publish the “red, amber, green” status of large projects as they are routinely assessed.

Kerslake was replying to Bacon at a hearing of the Public Accounts Committee meeting on transparency. Bacon pointed out at the hearing that the Public Accounts Committee had, years ago, called for Gateway reviews to be published.

Not learning from mistakes

“Something I have always been puzzled by is why government does not learn from its mistakes particularly but not only in the area of IT where things go wrong again and again, again and again,” said Bacon. “I have come to the conclusion government does not learn from its mistakes because it does not have a learning curve. If you don’t have a learning curve you are not going to learn.”

He cited the example of how Ian Watmore, Permanent Secretary at the Cabinet Office, had, at Bacon’s request, arranged for an “Opening Gate” report on Universal Credit to be published in the House of Commons library.

But, said Bacon, when an IT journalist applied to the Department for Work and Pensions, under the FOI Act, for the release of all Gateway reports on Universal Credit, the DWP would not publish any of them  – and even refused an FOI request to release the report Watmore had arranged to be placed in the House of Commons library, which Bacon obtained.  “So there is still a culture of intuitive, instinctive secrecy,”  Bacon said. Kerslake replied:

“Yes, actually we are looking at this specific issue as part of the Civil Service Reform Plan….I cannot say exactly what will be in the plan because we have not finalised it yet, but it is due in June and my expectation is that I am very sympathetic to publication of the RAG [red, amber, green] ratings.”

Bacon pointed out that the Cabinet Office Structural Reform Plan Monthly Implementation Updates had said Gateway reviews would be published.  But the commitment was removed for no apparent reason. When the Cabinet Office was asked why,  it said the Structural Reform Plans were only ever “drafts”.

Bacon asked Kerslake if the Government now plans to publish the Gateway reports.  “The Cabinet Office Structural Reform Plan Monthly Implementation Updates originally said Gateway reviews would be published  and then it somehow got downgraded into a draft; and from what’s publicly available at the moment the position of the government is not to publish Gateway reviews.  You sound as if you’re saying that’s going to change. Is that right?” asked Bacon.

“Watch this space,” replied Kerslake. “I am sympathetic. I generally broadly welcome, in principle, the idea of publishing information but there are lots of risks …”

Peter Gershon introduced Gateway reviews when he was Chief Executive of the Office of Government Commerce, which is now part of the Cabinet Office’s Efficiency and Reform Group. The reviews are carried out at key decision times in a project and are sometimes repeated:

  • Gateway Review 0 – Strategic assessment
  • Gateway Review 1 – Business justification
  • Gateway Review 2 – Procurement strategy
  • Gateway Review 3 – Investment decision
  • Gateway Review 4 – Readiness for service
  • Gateway Review 5 – Benefits realisation

Are Gateway reviews a success?

Gateway reviews are now supplemented by regular assurance audits carried out for the Cabinet Office’s Major Projects Authority. None of the reports is published.

Gateway reviews have not stopped costly failures such as Firecontrol or the NPfIT.  One permanent secretary told an MP that the reviews in his department were considered unimportant by senior responsible owners, for whom the reports are written. This may be because SROs often have charge of many projects; and even their SRO responsibilities are often in addition to their main jobs.

But Gershon had high hopes of Gateway reviews when they were introduced in February 2001. This is evident from the number of times he referred to Gateway reviews at one hearing of the Public Accounts Committee in December 2001.

 “… as the Gateway review process cuts in, which I have referred to on a number of occasions when I have appeared at this Committee …”

“… Through things like the Gateway process we are helping to sharpen the focus on the whole life aspects of these and other forms of complex projects in public sector procurement…”

“ …First, we have the introduction of the Gateway review process…”

“ … The Gateway process is a demonstrable example of how we have introduced a technique to support that whole life approach…”

“… If you look at the guidelines around the Gateway review process that is one of the things that is tested by these independent reviews …”

“… we recognised that that was a problem some time ago, which is why in the Gateway review one of the things that is explicitly tested is things like the skills and capabilities of the team at the design and build stage and that the skills and capabilities of the team at the procurement stage …”

“… in this area with the Gateway review process, from when we first launched it last February, we have been helping the department take a whole life approach to these forms of complex projects …”

“… Part of the Gateway Review process is to get a much sharper insight on to where we see good things happening where we can encourage other clients to replicate them…”

“… Now, with the Gateway Review process, my experience has been because of where we have deliberately focused the attention on the early life of projects where there is the greater scope for management to take corrective action, the accounting officers are paying a lot of attention to the recommendations that are emerging because, much to my surprise, most of them do not seem to like coming here defending what has gone wrong in the past. They seem to welcome the recommendations that we are providing to them to help try to get projects on to much stronger foundations in the future…”

“… With the Gateway Review, my experience has been that the Accounting Officers respond to the recommendations very positively…”

“…Gateway Reviews explicitly test how the department is planning in the pre-contract phase to secure ongoing value for money in the post-contract phase…”

“… Take, firstly, the Gateway Review process. That is testing various points in the life cycle of the project, from the very earliest stage…”

“… I would certainly expect in Gateway Reviews that the review team would be testing what methods were in place to facilitate the ongoing management of the contract…”

“… I think it is encouraging that Sir Ian Byatt thought the Gateway Review process had sufficient value to recommend it in his own review…”

And so forth.

Comment:

We applaud Richard Bacon MP for his persistent call for Gateway reports to be published.

Gateway reviews have defeated expectations that they would stop failures; and the National Audit Office tells us that central departments don’t even request Gateway reviews on some big and risky projects although they are supposed to be mandatory.

But Gateway and other project assurance reports could prove invaluable if they are published. In the public domain the reports would enable Parliament and Francis Maude’s “armchair auditors” to hold officials and SROs to account for projects that are in danger of failing. That would be an incentive for officialdom to fail early and fail cheaply; and Gateway reviewers may take greater care to be neutral in their findings – not too lenient, or too harsh – on the basis that the reports would be open to public scrutiny. SROs would also have to take the review reports seriously – not just put them in a draw because nobody knows about them anyway.

We welcome Kerslake’s comments but hope that he and his colleagues plan to publish more than the RAG (Red/Amber/Green) status of projects. Otherwise they will be missing an opportunity.  Gateway reports and other assurance reviews are expensive. Reviewers can earn up to £1,000 a day. This money  could be well spent if the reviews are to be published; but it will add to public waste if the reports are kept secret and continue to be deemed pointless or unimportant by departments.

It is ironic, incidentally, that the Ministry of Justice, which introduced the FOI Act, gives advice to departments to keep the RAG status of Gateway reviews confidential. In its advice on Gateway reviews and the FOI, the MoJ tells departments that the “working assumption” is that the substance of the Gateway reports should be kept confidential until at least two years have elapsed.

It’s time for a culture change. Maybe the Civil Service Reform Plan next month will be worth reading.

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.