Category Archives: procurement

Civil servant in charge of £9.3bn IT project is not shown internal review report on scheme’s failings.

By Tony Collins

“If people don’t know what you’re doing, they don’t know what you’re doing wrong” – Sir Arnold Robinson, Cabinet Secretary, Yes Minister, episode 1, Open Government.

Home Office officials kept secret from the man in charge of a £9.3bn project a report that showed the scheme in serious trouble.

The Emergency Services Network is being designed to give police, ambulance crew and firemen voice and data communications to replace existing “Airwave” radios.  The Home Office’s permanent secretary Philip Rutnam describes the network under development as a “mission-critical, safety-critical, safety-of-life service”.

But Home Office officials working on the programme did not show an internal review report on the scheme’s problems to either Rutnam or Stephen Webb, the senior responsible owner. They are the two civil servants accountable to Parliament for the project.

Their unawareness of the report made an early rescue of the Emergency Services Network IT programme less likely. The scheme is now several years behind its original schedule, at least £3.1bn over budget and may never work satisfactorily.

The report’s non circulation raises the question of whether Whitehall’s preoccupation with good news and its suppression of the other side of the story is killing off major government IT-based schemes.

With the Emergency Services Network delayed – it was due to start working in 2017 – police, ambulance and fire services are having to make do with the ageing Airwave system which is poor at handling data.

Meanwhile Motorola – which is Airwave’s monopoly supplier and also a main supplier of the Emergency Services Network – is picking up billions of pounds in extra payments to keep Airwave going.

Motorola may continue to receive large extra payments indefinitely if the Emergency Services Network is never implemented to the satisfaction of he emergency services.

EE is due to deliver the network component of the Emergency Services Network. Motorola is due to supply software and systems and Kellogg Brown & Root is the Home Office’s delivery partner in implementing the scheme.

Has Whitehall secrecy over IT reports become a self-parody?

The hidden report in the case of the Emergency Services Network was written in 2016, a year after the scheme started. It said that dialogue between suppliers, notably EE and Motorola, did not start until after the effective delivery dates. Integration is still the main programme risk.

MP SIr Geoffrey Clifton Brown has told the Public Accounts Committee that the report highlighted an absence of clarity regarding dependency on the interface providers, which caused something of an impasse.

He said the report “alluded to the fact that that [a lack of clarity around integration] remains one of the most serious issues and is not showing any signs of resolution”.

Stephen Webb has been in charge of the project since its start but he is the business owner, the so-called “senior responsible owner” rather than the programme’s IT head.

In the private sector, the IT team would be expected to report routinely to a scheme’s business owner.

But in central government, secrecy over internal assurance reports on the progress or otherwise of major IT-related projects is a Whitehall convention that dates back decades.

Such reports are not published or shared internally except on a “need-to-know” basis. It emerged during legal proceedings over the Universal Credit IT programme that IT project teams kept reports secret because they were “paranoid” and “suspicious” of colleagues who might leak documents that indicated the programme was in trouble.

As a result, IT programme papers were no longer sent electronically and were delivered by hand. Those that were sent were “double-enveloped” and any that needed to be retained were “signed back in”; and Universal Credit programme papers were watermarked.

The secrecy had no positive effect on the Universal Credit programme which is currently running 11 years behind its original schedule.

Webb has told MPs he was “surprised” not to have seen review report on the Emergency Services Network. He discovered the report’s existence almost by accident when he read about it in a different report written a year later by Simon Ricketts, former Rolls Royce CIO.

This month the Public Accounts Committee criticised the “unhealthy good news” culture at the Home Office. The Committee blamed this culture for the report’s not being shown to Webb.

The Home Office says it doesn’t know why Webb was not shown the “Peter Edwards” report. The following was an exchange at the Public Accounts Committee between MP Sir Geoffrey Clifton-Brown, Webb and Rutnam.

Clifton-Brown: When you did that due diligence, were you aware of the Peter Edwards report prepared in the fourth quarter of 2016?

Rutnam: No, I’m afraid I was not. The Peter Edwards report on what exactly, sorry?

Clifton-Brown: Into the problems with ESN [Emergency Services Network], in particular in relation to suppliers.

Rutnam: I do not recall it. It may have been drawn to my attention, but I’m afraid I do not recall it.

Webb: It was an internal report done on the programme. I have not seen it either.

Clifton-Brown: You have not seen it either, Mr Webb—the documents tell us that. Why have you not seen such an important report? As somebody who was in charge of the team—a senior responsible officer—why had you not seen that report?

Webb: I don’t know. I was surprised to read it in Simon’s report. [Simon Ricketts.]

Chair: Who commissioned it?

Webb: The programme leadership at the time.

Chair: That is the board?

Webb: The programme director. It was a report to him about how he should best improve the governance. I think he probably saw it as a bit of an external assurance. It probably would have been better to share it with me, but that was not done at the time.

Clifton-Brown: “Probably would have been better to share it”? That report said that dialogue between suppliers, notably EE and Motorola, only started after the effective delivery dates. The report highlighted that there was not clarity regarding dependency on the interface providers, and that caused something of an impasse. It also alluded to the fact that that remains one of the most serious issues and is not showing any signs of resolution. That was in 2016, in that report. Had that report been disseminated, would we still be in the position that we are today?

Webb: I think that we would have wanted to bring forward the sort of [independent] review that the Home Secretary commissioned, and we would have done it at an earlier date.

Clifton-Brown: Why did you need to? You would not have needed to commission another review. You could have started getting to the root of the problem there and then if you had seen that report.

Webb: Yes.

Comment:

Webb and Rutman seem highly competent civil servants to judge from the open way they answered the questions of MPs on the Public Accounts Committee.

But they did not design the Emergency Services Network scheme which, clearly, had flawed integration plans even before contracts were awarded.

With no effective challenge internally and everything decided in secret, officials involved in the design did what they thought best and nobody knew then whether they were right or wrong. With hindsight it’s easy to see they were wrong.

But doing everything in secret and with no effective challenge is Whitehall’s  systemically flawed way of working on nearly all major government IT contracts and it explains why they fail routinely.

Extraordinary?

It’s extraordinary – and not extraordinary at all – that the two people accountable to Parliament for the £9.3bn Emergency Services Network were not shown a review report that would have provided an early warning the project was in serious trouble.

Now it’s possible, perhaps even likely, the Emergency Services Network will end up being added to the long list of failures of government IT-based programmes over the last 30 years.

Every project on that list has two things in common: Whitehall’s obsession with good news and the simultaneous suppression of all review reports that could sully the good news picture.

But you cannot run a big IT-based project successfully unless you discuss problems openly. IT projects are about solving problems. If you cannot admit that problems exist you cannot solve them.

When officials keep the problems to themselves, they ensure that ministers can be told all is well. Hence, ministers kept telling Parliament all was well with the £10bn National Programme for IT in the NHS  – until the scheme was eventually dismantled in 2011.

Parliament, the media and the public usually discover the truth only when a project is cancelled, ends up in the High Court or is the subject of a National Audit Office report.

With creative flair, senior civil servants will give Parliament, the National Audit Office and information tribunals a host of reasons why review reports on major projects must be kept confidential.

But they know it’s nonsense. The truth is that civil servants want their good news stories to remain uncontradicted by the disclosure of any internal review reports.

Take the smart meters roll-out. Internal review reports are being kept secret while officials give ministers and the Department for Business, Energy and Industrial Strategy the good news only. Thus, the latest Whitehall report on smart meters says,

“Millions of households and small businesses have made the smart choice to get a smart meter with over 12.8 million1 operating in smart mode across Great Britain. This world leading roll out puts consumers firmly in control of their energy use and will bring an end to estimated bills.”

Nothing is said about millions of homes having had “smart” meters installed that are neither smart nor compatible for the second generation of smart meters which have a set of problems of their own.

The answer?

For more than 30 years the National Audit Office and the Public Accounts Committee have published seemingly unique reports that each highlight a different set of problems. But nobody joins the dots.

Sir Arnold, the Cabinet Secretary said in “Yes Minister“, that open government is a contradiction in terms. “You can be open, or you can have government.

This is more than a line in a TV satire.  It is applied thinking in every layer of the top echelons of civil service.

Collective responsibility means civil servants have little to fear from programme failures. But they care about departmental embarrassment. If reviews into the progress or otherwise of IT-enabled programmes are published, civil servants are likely to be motivated to avoid repeating obvious mistakes of the past. They may be motivated to join the dots.

But continue to keep the review reports secret and new sets of civil servants will, unknowingly each time, treat every project as unique. They will repeat the same mistakes of old and be surprised every time the project collapses.

That the civil service will never allow review reports of IT programmes to be published routinely is a given. If the reports were released, their disclosure of problems and risks could undermine the good news stories ministers, supported by the civil service, want to feel free to publish.

For it’s a Whitehall convention that the civil service will support ministerial statements whether they are accurate or not, balanced or not.

Therefore, with review reports being kept secret and the obsession with good news being wholly supported by the civil service, government’s reputation for delivering successful IT-based programmes is likely to remain tarnished.

And taxpayers, no doubt, will continue to lose billions of pounds on failed schemes.  All because governments and the civil service cannot bring themselves to give Parliament and the media – or even those in charge of multi-billion pound programmes –  the other side of the story.

Home Office’s “unhealthy good news culture” blamed for Emergency Services Network Delays – Civil Service World

Emergency Services Network is an emergency now – The Register

Home Office not on top of emergency services programme – Public Accounts Committee report, July 2019

£20bn for the NHS? – not spent like this please

Johnathan Lewis, CEO Capita (right) and Simon Stevens, Chief Executive, NHS England (left) at Monday’s Public Accounts Committee.

By Tony Collins

Capita apologies for working “blind” on NHS outsourcing contract – but no humility from NHS England

Capita’s CEO Johnathan Lewis was contrite and authoritative when he appeared before public accounts MPs in the House of Commons on Monday.

He apologised unreservedly for what the committee chairwoman Meg Hillier called “a shambles”, which was Capita’s £330 seven to ten-year contract to run a range of services for GPs, dentists and ophthalmologists, as well as handle invitations and test results for cervical screening.

Capita’s Primary Care Support Services contract began in 2015 and complaints about the service from medical practitioners began to flow months later.

Capita made mistakes, said Lewis who was supported by his colleague Stephen Sharp, who reports directly to Lewis on public sector contracts. One mistake was that Capita tried to save money too soon by folding the work of 47 local NHS offices with 1650 staff into three offices without fully understanding that each office had a different way of working and a different way of delivering NHS services.

[A similar mistake helped to floor the £10bn National Programme for IT in the NHS (NPfIT), where suppliers and Whitehall officials tried unsuccessfully to use computers to standardise working practices and services in hundreds of hospitals before they fully understood the widely-different approaches of each hospital.]

Lewis told the Public Accounts Committee on Monday,

“This was an extremely complex outsourcing of services that I think both parties would recognise were not fully understood when the work was outsourced – the volumes, the scope, the fact that the service was being delivered in different ways across the different regions that became NHS England. At the same time I recognise the pressure NHS England were under to reduce costs and hence the pressure on them to outsource.”

His colleague Stephen Sharp added,

“I think mistakes were made. During the bid stage, NHS England did say there were some inconsistencies and differences within the various operations. But once Capita got into all the offices and looked at it, the inconsistencies and differences were not inconsequential. It was more or less 45 different services being run from 45 different offices, so the closure programme, which we adhered to and carried on with, we maybe should have stopped. We just made the problem worse as we went along.”

Why didn’t you stop the office closures, asked Conservative MP Anne Marie Morris who added that “even the NHS said, ‘We think you need to stop’.”

Sharp replied,

“We were actually working blind for a period of time. It was only once the service had been running under our control for a few months that complaints started to come in and we started to see visibility that there were bigger issues than we thought there were.”

With hindsight he said he would not have closed offices “until we had got the procedures operating on a national basis”. He conceded that if NHS England and Capita had deferred closing offices, the first two years of savings of about £60m would not have been achieved.

Capita’s losses of £140m

Lewis said that Capita had invested £125m in the contract but, given the loss of profit margin, the losses would be closer to £140m. “We will not make money over the life of this contract,” said Lewis.

An MP asked: why not walk away?

Lewis replied, “Because we made a commitment to deliver this service and reputations depend on that commitment. We see the public sector as a segment of our market that helps us achieve a diversified revenue base. It is a segment where we have services and solutions, where we can create value for the taxpayer and that is why it is an attractive segment.”

Capita is now meeting 41 of the 45 KPIs and, though the company is making good progress against the remaining four KPIs, it doesn’t change the fact that “our initial execution on this contract was not good and for that we apologise unreservedly,” said Lewis.

There were failings on the part of NHS England too. Health officials were so anxious to achieve the savings from closing offices and replacing old IT that couldn’t be relied on that they failed to test new national, standardised working practices and services before they asked a supplier to implement this strategy.

The result was that officials at NHS England had no clear idea of how much work they were outsourcing. They left due diligence to Capita; and Capita admitted at the hearing it did not do enough due diligence at the bid stage. If it had understood how much work was involved it would have bid a higher price or not bid at all.

NHS England also failed to involve most of the potential end-users – GPs, dentists and ophthalmologists in the design and planning of new services that would directly affect them such as pensions and payments.

Lewis said.

“There are other stakeholders that have historically not been brought into this process to the extent that they should have been, such as the BMA [British Medical Association] in how we might implement the digitisation of pension payments and the management of its pensions, or the Confederation of Dental Employers with regard to ophthalmic payments.

“We want to bring them into the process in ways that they have not been historically because we think that that will ultimately lead to a more successful roll out of the technology… They rightly have influence over the process. If we are going to roll out a process for digitising the 20,000 paper documents that cover the process by which you get refunded for an ophthalmic prescription today, surely those people need to be involved in the final roll-out and configuration of that solution.”

Absence of humility?

When MPs questioned the top official at NHS England, Simon Stevens, there was little sign of humility, contrition or regret. He left an impression that the same problems could end up being repeated by a different supplier under a different contract. One Conservative MP Bim Afolami found himself “sticking up for Capita”.

Afolami said,

“Do you feel, Mr Stevens, that criticism of this contract is in any way unfair on Capita? The more I hear, the more I feel that Capita has taken the sharp end of this and NHS England, despite slight reputational difficulty, has saved £60 million. To what extent do you feel that you should take more of the blame here and Capita should take less of it?”

Stevens emphasised the £60m savings but made no mention any of the contract’s specific problems such as the thousands of patient records that went missing, dozens of women left off cancer-screening lists, the qualified GPs who were unable to work for months while the system delayed verifying their entitlement to go onto a “National Performers List”, the GPs who ran short of basic supplies or the GPs and ophthalmologists who suffered financial detriment because of delayed payments.

Said Stevens,

“First, let me say that this has clearly been a rocky road, and the National Audit Office accurately described the bumps along the way, which are regrettable. That should not obscure the fact that, notwithstanding the economic pain that Capita has experienced, the contract has saved taxpayers £60 million in lower administrative costs in the National Health Service over the first two years of its life … that £60 million of savings is not to be sniffed at; it is the equivalent of 30,000 operations.”

Comment:

Campaign4Change has repeatedly criticised Capita’s performance on Barnet’s outsourcing contract, in part because Capita and the council have been markedly defensive – thin-skinned.

It was refreshing, therefore, to hear Capita’s newish CEO Jonathan Lewis being openly contrite over highly-visible failings in the NHS contract. He gave the impression to public accounts MPs of being a CEO who is determined to put right the failings for the sake of Capita’s reputation. The cost of correcting the problems seemed a secondary consideration.

With Lewis at the helm, Capita’s share price has continued to rise in recent weeks.

Less impressive at Monday’s hearing was Simon Stevens, NHS England’s chief executive, who seemed to imply that NHS England had done nothing wrong.  It was a reaction we’ve come to expect from top civil servants after an IT-related programme disaster. It’s never the fault of officialdom.

The reality is that NHS England was almost as culpable as Capita. NHS England rushed the whole outsourcing exercise – which doomed it from the start. It didn’t listen to critics who warned that primary care support services were too locally diverse and inherently problematic to standardise as part of a national  outsourcing deal.

Instead of first piloting and agreeing with GPs, dentists and ophthalmologists fundamental changes in working practices that would be needed across the country, NHS England went ahead with signing a co-called transformation deal with Capita.

NHS England paid only lip service to engagement with the new system’s end-users in the medical professions. By its own admission Capita, because of its own internal shortcomings, went into the contract blind.

What’s worrying is the way civil servants blithely repeat mistakes of the past and later say they did everything right.

The National Programme for IT in the NHS – NPfIT – failed in part because it was rushed, the implications of “ruthless standardisation” were not fully understood at the outset and there was a lack of proper engagement with potential end-users in hospitals and GP practices. All these same mistakes were made by Capita and NHS England on the Primary Care Support Services contract.

When ordinary human beings become senior civil servants there seems to be a requirement that they lose at a cellular level the facility to express humility and contrition. That loss is replaced by an overly prominent complacency. Whatever goes wrong is not their fault.

Stevens said in essence that NHS England did everything right. Through its unpublished project reviews, the Major Projects Authority – now the Infrastructure and Projects Authority –  endorsed NHS England’ s plans. All the so-called experts gave the outsourcing deal what Stevens called a “thumbs-up”.

It would have been surprising if Stevens had said the public sector was in any way to blame.

At least Capita has learned the lessons. It has a financial interest in doing so.

Ministers can learn from Capita’s candid chief executive

NHS England’s management of Primary Care Support Services contract with Capita – National Audit Office report

Monday’s televised Public Accounts Committee hearing with Capita’s Jonathan Lewis and Simon Stevens of NHS England

Capita under fire again over GP support contract – but NHS England praises “improvements”

By Tony Collins

Hundreds of trainee GPs have not received their salaries from Capita, which is under contract to pay them, reports The Guardian.

Some of the trainees have applied for emergency funds from The Cameron Fund, a charity for the prevention of hardship among GPs and their dependents.

Capita administers training grants for GPs under its wide-ranging £1bn contract with NHS England to provide primary care services.

In November 2016 the then Health minister Nicola Blackwood described failings on Capita’s GP support contract as “entirely unacceptable”. 

She said Capita had inadequately prepared for delivering a “complex transition”.

In response,  Capita said it adding the full-time equivalent of 500 extra staff on the contract.

But in February 2017, after continuing complaints,  the Health Secretary Jeremy Hunt said he would be prepared to end Capita’s contract if necessary.

Since then, though, NHS England has praised “improvements” in the contract, according to Pulse.

Yesterday The Guardian reported extracts from a letter the British Medical Association sent to NHS England on 30 October 2017.

It said some GP practices were “having to pay trainees out of already overstretched practice budgets, or trainees are going months without being paid if the practice cannot cover the shortfall”.

Capita confirmed it had outstanding payments to some trainee GPs but was unable to say how many it is responsible for paying, or how many it has not paid.

It said that it had not received all the information it needed to pay salaries from the relevant employers. A Capita spokesperson told The Guardian that the problems were an inevitable part of “a major transformation project to modernise a localised and unstandardised service”.

It added: “We have made significant investment to deliver improvements and these have been recognised by NHS England and demonstrated through improved service performance and improved customer satisfaction.”

The Cameron Fund’s treasurer Dr David Wrigley described the outsourcing of GP support services as a “botched privatisation”.

“NHS England has commissioned out what was a very efficient service run within the NHS, and now Capita runs this contract in what I’d call another botched privatisation.”

One trainee GP went unpaid two consecutive months.  At the end of October she posted on a private message board for GPs: “Anyone know of how I access hardship funds (quickly) to feed children/pay nursery/mortgage (quickly)?”

Her surgery gave her a loan last month to tide her over but did not have enough surplus funds to do the same thing again.

She said that in the last 24 hours partners have stepped forward and have all taken a pay cut to provide a loan “to get me through the month as they were worried about my family”.

An NHS England spokesperson said it was “holding Capita’s feet to the fire on needed improvements”.

It added: “In the meantime, the lead employer for Health Education England or the GP practice are responsible for paying their GP trainee salaries and are subsequently reimbursed for this. Backlogs are being prioritised by Capita.”

The BMA’s letter to the NHS chief executive Simon Stevens criticises Capita.

“We are disappointed at the lack of progress that has been made … These issues have been ongoing since NHS England commissioned Capita … and it is unacceptable that more progress has not been made to getting these resolved …

Wrigley wants the House of Commons’ public accounts committee to investigate the contract.

“NHS England have known about this for a while and the BMA has been putting constant pressure on, and it’s all promises that it’ll get better but it doesn’t.”

New systems for cervical screening and GP payments and pensions that are also contracted out to Capita are due to go live next July. The BMA has told NHS England that it has “no confidence” in Capita’s ability to deliver the services.

Comment

It’s possible to have some sympathy for Capita which has the daunting task of trying to standardize a wide range of systems for supporting disparate GP support services.

But, as Campiagn4Change has reported many times on Barnet Council’s Capita outsourcing contract, it can be difficult if not impossible to make huge savings in the cost of running services (£40m in the case of the GP support contract), deliver an IT-based transformation based on new investment and provide a healthy profit for the supplier’s shareholders while at the same time making internal efficiency savings.

Capita’s share price is relatively low and under continuing pressure but is holding up reasonably well given the company’s varied problems.

Still, we wonder whether the company can afford to put large sums into sorting out problems on the GP support contract, at Barnet Council and on other well-publicised contracts?

The MoD has ended a Capita contract early, the company faces litigation from the Co-op and its staff are staging nine days of strikes over pensions.

Who’s to blame?

If anyone is to blame in this NHS saga it is NHS England for not fully understanding the scale and complexity of the challenges when it outsourced to Capita.

The first rule of outsourcing is: Don’t outsource a problem.

Doctors warned NHS England against signing the contract. Under financial pressure to do so – it needed the promised savings  – NHS England’s public servants signed the deal.

Those public servants will not be held accountable for their decision. In which case, what’s to stop public and civil servants making the wrong decisions time and again?

Two further questions:

Is NHS England too close to Capita to see the faults?

Do public servants have a vested interest in not criticising their outsourcing suppliers, in case opprobrium falls on both parties? 

Thank you to Zara Pradyer for drawing my attention to the Guardian article.

Hundreds of trainee GPs facing hardship as outsourcing firm Capita fails to pay – The Guardian.

 

Does Universal Credit make a mockery of Whitehall business cases?

By Tony Collins

Does Universal Credit make a mockery of this Treasury guidance on business cases?

It’s supposed to be mandatory for Whitehall departments to produce business cases. They show that big projects are “unequivocally” affordable and will work as planned.

But Computer Weekly said yesterday that the Department for Work and Pensions has not yet submitted a full business case for Universal Credit although the programme has been running for six years.

The result is that the Universal Credit IT programme may be the first big government computer project to have reached the original completion date before a full business case has been finalised.

Its absence suggests that the Department for Work and Pensions has not yet been able to produce a convincing case to the Treasury that the IT programme will either work or be affordable when it is due to roll out to millions of claimants.

The absence also raises a question of why the Department for Work and Pensions was able to award contracts and proceed with implementation without having to be accountable to Parliament for milestones, objectives, projected costs and benefits – all things that would have been recorded in the full business case.

If the DWP can proceed for years with project implementation without a full business case, does this mean that other Whitehall department need have no final structured plan to justify spending of billions on projects?

Will Universal Credit work?

By early March 2017, fewer than 500,000 people were on Universal Credit. On completion, the system will be expected to cope with seven million claimants.

Although the rollout of the so-called “digital” system – which can handle all types of claim online – is going well (subject to long delays in payments in some areas and extreme hardship for some), there are uncertainties about whether it will cope with millions of claimants.

Universal Credit campaigner John Slater has been unable to obtain any confirmation from the DWP on whether it is planning to complete the rollout by 2022 – five years later than originally scheduled.

Business cases present arguments that justify the spending of public money. They also provide a “clear audit trail for purposes of public accountability,” says Cabinet Office guidance on business cases.

But hundreds of millions has already been spent on Universal Credit IT, according to the National Audit Office.

Business cases are mandatory … sort of

The Treasury says that production of business cases is a

“mandatory part of planning a public sector spending proposal …”

Yesterday, however, Computer Weekly reported that,

“Amazingly, given the programme has been going since 2011, the full business case for Universal Credit has still not been submitted or signed off by the Treasury – that’s due to take place in September this year.”

The Treasury says that preparation of the Full Business Case is “completed following procurement of the scheme – but prior to contract signature – in most public sector organisations.”

But by March 2013, the Department for Work and Pensions had already spent about £303m on Universal Credit IT, mostly with Accenture (£125m), IBM (£75m), HP (49m) and BT (£16m), according to the National Audit Office.

Why a business case is important

The Treasury sums up the importance of business cases in its guidance to departments,

“… it is vital that capital spending decisions are taken on the basis of highly competent professionally developed spending proposals.

The business case provides a

“structured process for appraising, developing and planning to deliver best public value.”

The full business case, in particular, sets out the

  • contractual arrangements
  • funding and affordability
  • detailed management arrangements
  • plans for successful delivery and post evaluation.

In the absence of a full business case the DWP was able to start the Universal Credit IT programme with little structured control on costs. The National Audit Office found in 2013 that there was

  • Poorly managed and documented financial governance
  • Limited evidence that supplier invoices were properly checked before payments were made.
  • Inadequate challenge of purchase decisions
  • Insufficient information on value for money of contracts before ministers approved them
  • Insufficient challenge of suppliers’ cost changes
  • Over-reliance on performance information from suppliers that the Department for Work and Pensions didn’t validate.
  • No enforcement by the DWP of key parts of the supplier contracts

Comment

Officials at the Department for Work and Pensions have gone to the bank for money for a new business venture – the building of Universal Credit IT – and said in effect,

“We’ll let you have an outline business case that may change a few times and in a few years, perhaps on completion of the programme or thereabouts, we’ll provide a full business case. But we’d like the money now please.”

In response the bank – HM Treasury – has replied in effect,

“You’re supposed to supply a full business plan before we decide on whether to give you the money but we know how important Universal Credit is.

“We’ll tell you what: we’ll let you have a few tens of millions here and there and see how you get on.

“For the time being, without a full business case, you’re restricted to an IT spend of around £300m.

“In terms of the eligibility criteria for the money, you can let us know what this should be when you’re a few years down the road.

“We accept that you’ll be in a much better position to know why you should be given the money once you’ve spent it.”

Does “mandatory” mean anything when there is no sanction against non-compliance?

And when the DWP is able to embark on a multi-billion pound programme without submitting a full business case until after the original completion date (2017), what’s the point of a business case?

The fact that the DWP is six years into implementation of Universal Credit without a full business case suggests that departments make up the rules as they go along.

What if the Treasury rejects the Universal Credit business case when it’s eventually submitted?

Will the DWP wait another few years to submit a case, when an entirely new set of officials will be in place? By then, perhaps, the Universal Credit rollout will have finished (or been aborted) and nobody at that stage could be effectively held to account if the scheme didn’t work or money had been wasted.

If Whitehall routinely waits until an IT-based programme is finished before presenting a full business case for Treasury approval, there’s nothing the Treasury can do if it wants and needs the programme.

Sir Humphrey is all-powerful.  Why should officials worry about presenting full business cases on programmes they know there’s a political imperative to deliver?

Can DWP meet its revised 2022 target for completion of Universal Credit? – Computer Weekly

Treasury guidance on business cases

 

 

Another Whitehall failure: no officials responsible, fluid facts and doubtful ethics. Plus ça change?

By Tony Collins

It’s rare for truth to emerge from the ashes of a failed contract.

The disastrous contract between Siemens and the BBC (the so-called Digital Media Initiative) was a rarity. Various reports provided confidence that the relevant facts had emerged.

It’s more usual for MPs to report that they haven’t got to bottom of what happened after a Whitehall contract failure.

Indeed today’s report by the Public Accounts Committee says of its inquiry into PA Consulting’s contract with the UK Trade and Investment:

“We cannot remember a previous inquiry in which so many witnesses corrected their evidence after a public session.”

UK Trade and Investment, now the Department for International Trade,  helps UK businesses to export more goods and services and encourages overseas organisations to invest in the UK.

It is funded by the Department for Business, Innovation & Skills and the Foreign & Commonwealth Office.

In May 2014, UK Trade and Investment’s  officials entered into a three-year contract with PA Consulting for the supply of consultants in a contract that involved ICT support.

On small example of unclear facts: in its bid, PA stated that cost categories including ICT were “already included in the costings and will not be charged for separately”. This implied that ICT would be included in the consultants’ day rates.  Today’s Public Accounts Committee report says,

“However, there were separate charges in the pricing schedule for HR, ICT,  legal and professional, quality, and knowledge management.”

After the contract had started, officials became concerned about:

  • the way PA had priced the contract
  • PA’s transparency in its communications with Whitehall.

The contractual relationship eventually broke down and officials terminated the contract in January 2016.

The two sides agreed a settlement in which the taxpayer would pay the balance of PA’s outstanding invoices less a £3m reduction. Officials paid £18.8m for the first 11 months of the contract.

Labour MP Meg Hillier, chairman of the Public Accounts Committee, said today (5 April 2017),

“Even now, ten months after the parties reached a settlement and four months after we took oral evidence, our Committee cannot say with confidence that it has got to the bottom of what happened.”

Poor record-keeping

Even the National Audit Office was unable to obtain a full picture. The NAO said in its 2016 report on PA’s contract,

“Understanding exactly what happened in letting and negotiating this contract is difficult due to the lack of proper documentation, the disagreement between parties and, now, the absence of a number of people who were involved on either side.”

MPs on the Public Accounts Committee say that Whitehall officials:

  • did not keep proper records
  • negotiated significant changes to the contract with PA when they should have gone back to the market
  • pushed for a signing of the contract before they had finished negotiations.

For its part, PA “fell well short of the appropriate duty of care that we expect contractors to demonstrate when in receipt of taxpayers’ money”.

According to the Public Accounts Committee, PA

  • took advantage of the department’s poor decision making
  • sold Whitehall a service it is not clear it needed
  • failed to give the fair breakdown of its costs and profit that officials had asked for
  • used the negotiations to pass on costs to Whitehall that it had said in its bid that it would bear
  • increased its profit from the contract while telling officials that its profit had not increased.

PA Consulting obfuscation?

The Committee says in its report,

“PA has not convinced us that it takes full responsibility for its actions. Its many explanations of its charges both at the time and since have been loosely worded, inconsistent and seemingly designed to obfuscate.

“It is unclear to us how such behaviour would be possible in a well managed professional practice.”

The Committee adds,

“Government’s lack of commercial expertise to get the best deals on behalf of the taxpayer has been a regular cause for concern for this Committee.”

In 2015 RSM UK Consulting produced a draft report on the contract. It included a finding that PA had “consistently made incorrect and misleading representations relating to £3.9m of the overheads charged”.

PA disputed RSM’s findings, stating that it had invoiced according to the agreed charging mechanism.

Overly long contract?

The contract was 596 pages – “difficult to read, understand and use, for a relatively simple service”. The Committee adds,

“The contract incorporates the ITT and bid, both of which are focused on the outcomes and how they will be achieved, and not on the way the contract would actually be run and charged for.

“Furthermore, the bid and contract are not clear on important aspects of the pricing and are often self-contradictory.”

[One would have thought that after decades of practice, Whitehall departments would understand how to commission a clear and unambiguous contract.]

Comment:

There is not even any evidence that some key decisions by Whitehall officials were approved by any formal decision-making body.

This and other findings by the National Audit Office and the Public Accounts Committee are astonishing, not because of their momentousness but because of they are almost routine.

There were similar findings after National Audit Office investigations into early spending on the Universal Credit IT programme.

It’s beginning to look as if Whitehall officials can sometimes hand over money to the private sector without any firm controls at all, which could encourage corruption and, at the least, incompetence and waste.

What’s the civil service’s solution?

To make sure that no officials are held responsible. The civil service is all about collective responsibility. In other words no responsibility.

Is the civil service’s message to the private sector now clear: “Get whatever Whitehall business you can because though the terms of the contract may be tough, what we pay you afterwards may be, for us, a matter of indifference.”

PA Consulting’s contract with UK Trade and Investment

 

Large suppliers still dominate government IT

By Tony Collins

In 2012, the then Cabinet Office minister Francis Maude, lamented the high costs of government IT and spoke of an “oligopoly” of large suppliers. He suggested things would change.

“… contracts were consistently awarded to a limited number of very large suppliers on long-term exclusive contracts.

“As a result there was inadequate competition and an abdication of control. The concept of having one supplier, aggregated supply, increased project risk and removed competitive tension.

“The Government repeatedly found itself paying large amounts for systems that were delivered late, over budget and which often did not fully meet the original policy requirement.  If indeed, they were delivered at all. There are plenty of well-documented disasters – such as DH’s now terminated National programme for IT.

“Ultimately, the last Government lost control of IT – it outsourced not only delivery, but its entire strategy and ability to shape the future of our public services.

“At the same time smaller, more 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.

“Procurements took so long only the big companies could absorb the cost – which they naturally passed on to us.

“All in all, we had an approach that was bad for users, bad for the taxpayer and bad for growth.”

Public sector IT spending was up to £20bn a year, he said, adding that “public sector productivity was actually declining”.  He outlined how things were changing.

What has happened since?

A report published today by the National Audit “Digital Transformation in Government” raises a question of how much has changed.

Efforts to boost the SME share of government IT business “have had some impact”, says the National Audit Office, but it adds that “most government procurement with digital and technology suppliers continues to be with large organisations”.

“In 2015-16, 94% of such spending was with large enterprises, a fall of less than one percentage point since 2012-13.”

Today’s NAO report is mainly about the Cabinet Office’s Government Digital Service – GDS. It points out GDS’s strengths and weaknesses but in general does not give any advice on the sensitive point of whether it should have more or less influence on government IT.

On digital transformation, it says that the work of the NAO shows that attempts to transform government have had mixed success.

“Many public services appear increasingly unsustainable. Those responsible for major programmes have continued to exhibit over-optimism and make slow progress towards their objectives.”

It adds,

“Digital transformation has a mixed track record across government. It has not yet provided a level of change that will allow government to further reduce costs while still meeting people’s needs.

“GDS has also struggled to demonstrate the value of its own flagship initiatives such as Verify, or to set out clear priorities between departmental and cross-government objectives.

“GDS’s renewed approach aims to address many of these concerns as it expands and develops into a more established part of government. But there continues to be a risk that GDS is trying to cover too broad a remit with unclear accountabilities.

“To achieve value for money and support transformation across government, GDS needs to be clear about its role and strike a balance between robust assurance and a more consultative approach.”

Comment

The National Audit Office report is strong on facts and quality of research but avoids the big question of how GDS can bring about change when the top brass in departments prefer autonomy to what they see as GDS’s interference.

GDS’s existence goes to the heart of how the civil service runs. It is one part of the civil service trying to bring about change in other parts of the civil service.

And the evidence so far is that the civil service doesn’t like change.

The NAO report disappoints because it doesn’t address how government IT is to change if departments are to continue to run empires unchallenged by GDS or the heads of the civil service. Sir Humphrey is still king.

GDS scrutinises departmental IT spending – spending applications are reviewed by a team of eight people within GDS’s Standards Assurance team – but, much to Sir Humphrey’s delight, GDS’s influence seems to be waning.

When Jack Straw was Justice secretary, he told MPs in 2007 that when he abandoned projects there was a fuss at first and soon nobody noticed the project did not exist.

“There is always the option to abandon things. I did that in the Foreign Office with much complaint that the world might end.

“What happened was that we saved a lot of money and no one ever noticed the fact that that scheme did not exist…it is very frustrating that so many people, including the private sector, are taken in by snake oil salesmen from IT contractor who are not necessarily very competent and make a lot of money out of these things. I am pretty intolerant of this.”

How much has changed? Outsiders including Jack Straw and Francis Maude, together with insiders such as Chris Chant have pointed to the need for major changes in the way departments manage huge IT budgets and there have been some improvements: HMRC’s is breaking up its monolithic “Aspire” contract, citizens may notice that it is possible now to renew passports and driving licences online and GDS has had an impact in making departments think hard about whether they really need to spend the amounts they do on major IT contracts.

But major change in the costs of government IT seems not just a long way off but unattainable while the dominance of Sir Humphrey remains unchallenged.

Digital Transformation in Government – NAO report

A classic “waterfall” IT project disaster – yet officials went by the book

By Tony Collins

Some of those who read “Crash – 10 easy ways to avoid a computer disaster” may remember a warning that buying an IT system on the basis that it works well in another country and can therefore be adapted to the UK’s needs, is flirting with disaster.

First published in 1999, Crash said,

“There are graveyards of computer projects that began life as a simple adaptation of a package used elsewhere in the world.”

One example at that time was the failure of the London Stock Exchange’s Taurus project.

Now a report published today by Audit Scotland on the “i6” project goes into forensic – but lucid – detail on what went wrong and the conflicting views of police and the supplier Accenture.

Says the report,

“The belief that most of the i6 system could be based on an existing IT system proved incorrect.”

It became clear well into project that

“a virtually fully bespoke system was required”.

The plan was for i6 to replace 130 paper-based processes and IT systems but on 1 July 2016, after many well-publicised difficulties and delays, the Scottish Police Authority and Accenture agreed to terminate the i6 contract.

Police in Scotland had chosen Accenture’s bid in 2013 largely because it had successfully implemented a system for Spain’s Guardia Civil police service.

To its credit Accenture refunded all the money the police in Scotland had paid for the i6 system, £11.06m, plus a further £13.56m – but Audit Scotland says the failure of the project …

“means that some of the benefits that should have arisen from implementing it, have been, at best, delayed. There was a need to modernise police ICT systems six years ago when the procurement of i6 began. That need has not been met. Police officers and staff continue to struggle with out-of-date, inefficient and poorly integrated systems.

“This also hinders how Police Scotland interacts and shares information and intelligence with the other parts of the justice system. There is an urgent need to determine what the next steps should be…”

The lessons are clear from the report:

  • Don’t buy an overseas system without realising that it’ll need to be built almost from scratch for the UK. The ideal is for the business processes to be greatly simplified and adapted to fit a tried and tested system, not the other way around. Audit Scotland says the police programme team and Accenture believed that the majority of the i6 system could be based on an existing IT system that Accenture had developed for Spain,  with the remainder being bespoke development work.  But there was an “over-reliance” on Accenture’s work for Guardia Civil”.
  • The “waterfall” systems development contributed to the fact that Police Scotland “only discovered the true extent of problems with the system when it was delivered for testing”.  Waterfall meant that Accenture produced the software in distinct phases, in a sequence resembling a waterfall. Once a phase was complete, the process moved to the next phase – and no turning back. “It meant that all of the design, coding and construction of i6 would be completed before Accenture released it to Police Scotland for testing. Police Scotland would pay for each phase when it was completed.” [Agile, on the other hand, is a “test and see” approach and is far more flexible. It can adapted according to what the end-user needs and wants, and changes in those needs and wants.]
  • Don’t trust the demonstration of a waterfall system. The demo may look great but rolling it out successfully across various regions may be a different story. Accenture had demonstrated i6 but much later, after a period of testing, the i6 programme team reported to the programme board in August 2015 that there were: critical errors in the technical coding, flaws that Accenture was unable to resolve as quickly as expected, serious concerns about the criminal justice module, which did not comply with the Integrated Scottish Criminal Justice Information System data standards, errors in the search and audit modules and “problems around the limited functionality in the administration module”.
  • External assurance reports may tell you that you have complied with good practice and they may give you detailed praise for your attention to detail but they probably haven’t looked at the big question: will the systems ever work? Audit Scotland said external assurance reports such as the Scottish Government’s “Gateway reviews” suggested improvements but “raised no major concerns”.  Throughout the course of the i6 programme, most of the external reviews suggested that delivery confidence was either amber or green.
  • If the plan is for a waterfall development, doing everything by the book before a contract is awarded will not guarantee success, or even make it more likely, if you haven’t asked the big question: Is this ever likely to work given the complexities we don’t yet understand? For officials in Scotland, everything went smoothly before the award of contract: there were even 18 months of pre-contract discussions. But within weeks of the contract’s start, Police Scotland and Accenture disagreed about whether the proposed system would deliver the requirements set out in the contract. Soon there was a “breakdown in relationships and a loss of trust between Police Scotland and Accenture that never fully recovered,” said Audit Scotland.
  • The supplier may be just as optimistic as you. “As the design and development of i6 progressed, it became apparent that Accenture would need to develop significantly more than had been originally anticipated. Despite delays and serious problems throughout the lifetime of the programme, Accenture provided regular assurance, in the face of strong challenge, about their confidence in delivering the i6 system. This assurance proved misplaced.”
  • When planning a waterfall system that has complexities and inter-dependencies that are not fully understood at the outset, expect ever-lengthening delays and projected costs to soar. At one point Police Scotland estimated that the level of effort Accenture would require to complete i6 was around eight times greater than the resources Accenture had estimated when signing the original contract. “The i6 programme team believed that the functionality of Accenture’s solution did not meet the requirements it had agreed in the contract. Accenture maintained that Police Scotland had not specified a detailed description of business requirements. This issue had not emerged during months of pre-award dialogue. Accenture also believed that it had set out clearly what its solution would do and maintained that Police Scotland, as part of procurement process, had accepted its qualified solution. A dispute followed about the interpretation of the contract requirements. Police Scotland argued that, after months of competitive dialogue, the requirements of the i6 system were well-defined, and that in line with the contract, these took precedence. Accenture argued its solution had precedence and that Police Scotland was trying to extend the scope of the programme. Accenture stated that, to meet Police Scotland’s interpretation of requirements, it would require more time and money.”
  • As soon as things start going badly awry, stop and have a re-think. Cancel all existing work if necessary rather than plough on simply because failure isn’t an option. Above all, take politics out of the equation. The Scottish Police Authority was anxious about i6 being seen to be a success after the failure of a previous police ICT project in 2012 – the Common Performance Management Platform. At the same time the i6 programme was “extremely important to Accenture at a global level. “This may have led to misplaced optimism about the prospects of success and unwillingness to consider terminating the programme,” says Audit Scotland.
  • When things start to go wrong, the truth is unlikely to emerge publicly. Even those accountable for the project may be kept in the dark. “Police Scotland were cautious of commercial sensitivities when providing assurances on i6 publicly. The Scottish Parliament’s Justice Sub-Committee on Policing held a number of evidence sessions with the Scottish Police Authority and Police Scotland to explore progress with the i6 programme. In March 2014, the Sub-Committee expressed frustration at the lack of information about the problems with the i6 programme that had been ongoing since August 2013. Police Scotland did not disclose the severity of the issues facing the programme, nor was it overly critical of Accenture. This may have reflected a desire to maintain relationships with Accenture to keep the programme on track or to maintain the commercial confidentiality of the contract.”

Accenture’s response

Accenture said,

“As the report acknowledges, the scope and the complexity of the solution for i6 increased significantly during the project.  This was driven by the client.  There were challenges and issues on both sides, but we worked closely with Police Scotland to review the programme and recommend revised plans to successfully deliver i6.

Despite our best efforts, it was not possible to agree the necessary changes and we mutually agreed to end the project.”

In May 2017 Audit Scotland is due to publish a report that summarises the lessons from a number of public sector ICT projects it has investigated.

Some of what i6 was intended to cover …

Comment

Tis a pity officials in Scotland hadn’t read Crash before they embarked on the i6 project – or if they had, taken more notice of the dangers of assuming a system that works overseas can be tweaked to work in the UK.

We commend Audit Scotland for its expert investigation and a fine report.

Clearly the failure of i6 is not entirely Accenture’s fault.  The project was commissioned on the basis of assumption and when things went wrong politics intervened to prevent a complete stop and a fundamental re-think.

Fatally, perhaps, there appears to have been no discussion about simplifying police administration to make the IT more straightforward. If police administration is so enshrined in law that it cannot be simplified, officials would have to accept before awarding the contract that they were buying an entirely new system.

The UK armed services simplified volumes of rules and practices before it introduced pay and personnel administration systems. It was hard, inglorious work. But simplifying ways of working first can make the difference between IT success and failure.

i6 – a review. Audit Scotland’s report. 

Waterfall approach damns £46m Scottish police system – Government Computing

Another public sector IT disaster – but useful if the lessons are learned.

Central buying of IT and other services is a bit of a shambles – just what Sir Humphrey wants?

By Tony Collins

Cabinet Office entrance

Cabinet Office entrance

Like the Government Digital Service, the Crown Commercial Service was set up as a laudable attempt to cut the huge costs of running central government.

The Cabinet Office under Francis Maude set up the Crown Commercial Service [CCS] in 2014 to cut the costs of buying common products and services for Whitehall and the wider public sector including the NHS and police.

It has a mandate to buy commodity IT, other products and services and whatever can be bought in bulk. It has had some success – for example with negotiating lower prices for software licences needed across Whitehall. The skills and knowledge of its civil servants are well regarded.

But, like the Government Digital Service, CCS has had limited support from permanent secretaries and other senior officials who’d prefer to protect their autonomy.

It has also been hindered by unachievable promises of billions of pounds in savings. Even CCS’s own managers at the time regarded the Cabinet Office’s plans for huge savings as over-optimistic.

Yesterday [13 December 2016] the National Audit Office published a report that questioned whether CCS has paid its way, let alone cut public sector costs beyond what civil and public servants could have achieved without it.

CCS employed 790 full-time equivalent staff in 2015/16 and had operating costs in one year alone of £66.3m

This was the National Audit Office’s conclusion:

“CCS has not achieved value for money. The Cabinet Office underestimated the difficulty of implementing joint buying for government. With no business case or implementation plan CCS ran into difficulties. Net benefits have not been tracked so it cannot be shown that CCS has achieved more than the former Government Procurement Service would have.

“However, the strategic argument for joint buying remains strong and CCS is making significant changes to improve future services.”

Some of the NAO’s detailed findings:

  • The public sector spends £2.5bn directly with CCS – £8bn less than originally forecast.
  • Seven departments buy directly through CCS – 10 fewer than originally forecast
  • The forecast of £3.3bn net benefits from the creation of CCS over the four years to 2017-18 are  unlikely to materialise.
  • The National Audit Office says the actual net benefits of CCS to date are “unknown”.
  • The Cabinet Office did not track the overall benefits of creating CCS.
  • Most of the planned transfers of procurement staff from central departments and the wider public sector to CCS haven’t happened.
  • Where some of the workforce has transferred, some departments have rehired staff to replace those who transferred.
  • Departments continue to manage their own procurement teams, although they use CCS’s frameworks.
  • CCS was set up with the power to force central departments to use its bulk buying services. But that power wasn’t enforced.
  • The National Audit Office says it is “no longer clear whether CCS has a clear mandate that requires all departments to use it for direct buying… it no longer has a clear timetable or expectation that further departments will transfer staff or buying functions to CCS”.

It’s all a far cry from the expectations set by a Cabinet Office announcement in 2013 which said that CCS will “ensure maximum value for the taxpayer is extracted from every commercial relationship”.

The then Cabinet Office minister Francis Maude said at the time,

“The new Crown Commercial Service will ensure a step change in our commercial capability, giving government a much tighter grip on all aspects of its commercial performance, from market engagement through to contract management.”

Comment

Why CCS has failed so far to make much difference to Whitehall’s costs is not clear. It seems to have been hit by a combination of poor management at the outset, a high turnover of senior officials and ludicrously high expectations, combined with a civil service reluctance in central departments and the wider public sector to cede control over procurement to CCS –  even when it comes to common products and services.

The NAO report is a reminder of a fundamental flaw in the way government works: central departments can’t in practice be forced to do anything. They are a power unto themselves. The Cabinet Office has powers to mandate a change of practice and behaviour in central departments – to which Sir Humphrey can shrug his shoulders and change nothing

Even the Prime Minister is, in practice, powerless to force departments to do something they don’t want to do (except in the case of the miscarriage of justice that involved two Chinook pilots who were eventually cleared of gross negligence because the then defence secretary Liam Fox, through a series of manoeuvres, forced the MoD to set the finding aside).

The CCS may be doomed to failure unless the Cabinet Office rigorously enforces its mandate to make government departments use its buying services.

If the Cabinet Office does not enforce its power, Sir Humphrey will always protect his turf by arguing that the products and services his officials buy – including IT in general – are specific and are usually tailored to the department’s unique and complex needs.

Much to the relief of Sir Humphrey, Francis Maude, the battle-hardened enforcer at the Cabinet Office, has left the House of Commons. He has no comparable replacement.

Are all central initiatives aimed at making  a real dent in the costs of running Whitehall now doomed to failure?

Sir Humphrey knows the answer to that; and he’s wearing a knowing grin.

Crown Commercial Service – National Audit Office report

 

Days from taking back outsourced IT, Somerset Council is unsure what it’ll find

By Tony Collins

Facing the TV cameras, officials at Somerset County Council spoke with confidence about the new joint venture company they had set up with the “world-class” IT supplier IBM.

“The contract has to succeed; we will make it succeed, ” a senior official said at the time. Greater choice for residents, more control, sustained improvement of services, improved efficiency, tens of millions in savings and enhanced job prospects for staff.

These were some of the promises in 2007.

Since then, Somerset County Council has been through a costly legal dispute with IBM; projected savings have become losses, and Somerset is days away from taking back the service early.

Now the council faces new IT-related risks to its reputation and finances, warns a team of auditors.

In several audit reports on the exit arrangements, auditors warn of a series of uncertainties about:

  •  what exactly IT assets the council will own as of 1 December 2016, when the joint venture hands back IT and staff.
  • how much software may not be licensed, therefore being used illicitly.
  • how much software is being paid for without being needed or used, wasting council tax money.
  • whether thousands of pieces of hardware have been disposed of securely over the years of the contract, or whether confidential data could later turn up in the public domain.
  • the accuracy of some supplied information. “… the same networking hardware items have the same value associated with them even though one is twelve years old and the other only four” said auditors.

Comment

That Somerset County Council laments setting up the Southwest One joint venture with IBM is not new. What continues to surprise is the extent of the difficulties of ending the joint venture cleanly – despite months, indeed more than a year – of preparatory work.

The realty is that uncertainties and risks abound.

When IT journalists ask leading councillors and officers at the start of outsourcing/joint venture deals whether all the most potentially serious risks have been given proper consideration, the spokespeople inevitably sound supremely confident.

If things go wrong, they are sure the council will be able to take back the service under secure arrangements that have been properly planned and written into the contract.

Yet today some of the most potentially serious risks to Somerset’s finances and reputation come from continuing threats such as the possibility confidential data being found on old hardware not securely disposed of.

Or the council may be paying for unneeded software licences.

In short Somerset County Council is taking back the IT service on 1 December 2016 without being certain what it will find.

In future, therefore, when councillors and officials across the country talk with supreme confidence at the start of an outsourcing deal or joint venture about large savings, sustained efficiencies, and a step-change improvement in services that comes with the benefits of collaborating with a world-class private-sector partner, local residents will have every right to be deeply sceptical.

For the reality is more likely to be that the council and its world-class supplier are about to embark on a journey into the unknown.

Thank you to campaigner Dave Orr for alerting me to the council audit reports that made this post possible.

TV broadcast in 2007 days after the council and IBM signed the Southwest One joint venture deal.

**

Excerpts from reports due to be considered by Somerset County Council’s Audit Committee next week (29 November 2016):

“… laptops, servers, storage devices, networking equipment, etc.) have been disposed of without the correct documentation historically, throughout the term with SWO [Southwest One]. There is a high likelihood that without the documentation to show that SWO were meant to have previously disposed of any specific data baring assets in a compliant manner then subsequent fines and loss of reputation will need to be dealt with by the Council.

“This is being addressed as part of the exit works but initial investigations show an expected lack of documentation.

**

“The quality of asset management and therefore exposure to risk (over and above this inherited risk) is expected to improve significantly once asset management returns to SCC [Somerset County Council).”

**

“Asset locations have been updated and improved though there are still issues regarding all asset details not being recorded accurately in the Asset Register. There is a risk that if wrong details are recorded against an asset then incorrect decisions could be made regarding these assets which may in turn cause the Council financial loss and/or loss of reputation.”

**

“… the same networking hardware items have the same value associated with them even though one is twelve years old and the other only four.”

**

“Software assets are now included in the monthly asset register report though the information collected and lack of correlation to meaningful license information means the original risk is not fully mitigated.

“This continued lack of software asset usage information against licensing proof of entitlement as well as the obvious risk of illegally using non licensed software there is also a risk that the Council is wasting public funds and Council officer’s time to manage unnecessary software. This means the Council will not be able to show “Best Value” in these purchases which could lead to fines being imposed by Central Government and loss of reputation by the inefficiencies being reported in the media.”

**

“I cannot though see evidence of the warranty & support arrangements being recorded or accurate recording of end of life assets. Due to a lack of or incorrect detail on the asset information there is the risk of incorrect decisions being made regarding an asset’s usage which could then lead to loss of money or reputation for the Council.”

Judge orders FOI release of Universal Credit IT reports

By Tony Collins

universal creditA judge has ordered the Department for Work and Pensions to release three Universal Credit IT reports that ministers and their officials have spent public money trying to keep out of the public domain.

Judge Chris Ryan and his FOI tribunal panel went further: they concluded that had the reports in question been disclosed at the time they might have corrected misleading government statements about the robust state of the Universal Credit programme.

In their ruling this week the tribunal said that disclosure of the documents,

“might have corrected a false impression, derived from official government statements by revealing the very considerable difficulties that were beginning to develop around the time when the information requests were submitted.”

Two director-level officials at the Department for Work and Pensions had argued that civil servants needed a “safe space” in the reports in question to be candid in their assessments of risks and problems.

But the FOI tribunal, whose members have project management experience, concluded that it’s in the self interest of officials to be candid and professional about problems and risks rather than be associated with a failed project.

In addition, officials would not wish to be held partly responsible in a later review, such as one carried out by the National Audit Office, for having “failed to draw colleagues’ attention to problems with sufficient clarity to ensure that they were addressed effectively and in good time”.

Civil servants had an “awareness of the importance of candour in support of good decision-making and their professional obligation to assist that process”.

The tribunal said the three reports in question should have been  disclosed at the time they were requested in 2012. It directed the DWP to disclose them.

If the DWP’s barrister can identify good reasons why the tribunal might have made an error, or errors, in law, he can appeal within 28 days, though a tribunal could reject his appeal . The DWP could then appeal this decision.

This cycle of appeals that has already happened once – or the DWP could now decide that it has spent enough public money on fighting the case and release the reports.

dwpDid the DWP mislead?

The reports are expected to throw light on the problems and risks of Universal Credit IT at  a time when DWP’s officials, secretary of state Iain Duncan Smith and his ministers, were giving assurances that all was well with the programme.

An FOI tribunal ordered the reports to be released in 2014 but various DWP appeals led to a re-hearing of the case last month (22 February 2016) at Leicester Magistrates Court.

Now Judge Ryan and two other FOI tribunal panel members have ordered that the DWP release a risk register, issues register and Major Projects Authority project assessment review.

The risk register described risks, the possible impact should they occur, the probability of their occurring, a risk score, a traffic light status, a summary of the planned response if a risk materialised, and a summary of the risk mitigation.

The issues register included a list of problems, the dates they were identified, the mitigating steps required and the dates for review and resolution.

The project assessment review gave a high-level strategic view of the state of UC, its problems, risks and how well or badly it was being managed.

The DWP argued that routine disclosure of such reports could lead to sensationalist headlines that would have a “chilling effect”.  Not wanting to give food to a hostile media, officials writing or contributing to such reports could make them anodyne.

dwpDWP fears “over-stated”

But Judge Ryan said the DWP had “over-stated” its fears. The tribunal suggested that the DWP had not been entirely truthful about the Universal Credit programme.

“We do not accept the Department’s submission that the management of the Universal Credit Programme is already exposed to sufficient public scrutiny and that this dilutes the strength of the arguments in favour of disclosure. On the particular facts of this case it is clear that the true story about the troubles which the Programme team faced only came to light a long time after the event and then showed a markedly different picture than had been portrayed by government statements issued at the time.”

This difference between reality on the UC programme and government statements was a good reason in favour of the disclosure of the reports, said the judge.

Closed session

The DWP’s witness Cath Hamp, a senior DWP official, went into closed session at the latest hearing to argue that her concerns about civil servant behaviour would be more clearly shown by reference to specific items in the withheld documents.

Her closed-session arguments related to the risk of fraud and hacking into the system, relations with commercial organisations, and relations with local government. The tribunal was not convinced by her arguments.

Neither was the panel convinced by the “chilling effect” arguments.

“The evidence on the likelihood of civil servants altering their behaviour in future with regard to their contributions to the preparation of a risk or issues register or to the conduct of a project review was, as Ms Hamp fairly conceded, speculative…”

FOI a benefit more than a “burden”?

The DWP argued that disclosures of the reports would have placed a burden on DWP’s Universal Credit programme executives. They would have been forced to divert their energies and time into correcting media reports about the seriousness of problems and risks. But the tribunal concluded,

“Nor do we accept that resources would be wasted in providing explanations. It is clear from the press releases that we have been shown that the Department has been adept at presenting its case to the public and that it clearly has the specialist staff to carry out that function.”

The tribunal suggested that FOI obligations, rather than cause harm as the DWP had suggested, would be a benefit. The FOI Act had “brought with it an obligation on government to explain itself to a greater extent than had previously been found necessary”.

The tribunal rejected the DWP’s argument that it faced a hostile media which made officials defensive.

“… the evidence before us suggests that, on this issue, the media has adopted a relatively balanced approach to information about the Programme that has come into its possession.”

The judge said that in any event it is a

“perfectly appropriate performance of the media’s role in a modern democracy for it to investigate and comment on the implementation of a major reform involving large sums of public money and a potentially crucial impact on the lives of some of the least fortunate members of society”.

He added: “We do not therefore accept the Department’s submissions on the likelihood of the public misunderstanding the disputed information, or being misled as to its significance by the media”

In its final paragraph the tribunal said,

“… we have concluded that the public interest in maintaining the exemption in respect of each of the withheld documents does not outweigh the public interest in disclosure and that they should therefore have been disclosed when requested. Our decision is unanimous.”

Comment

My thanks to IT projects professional John Slater who has been the main force behind the case in favour of disclosure of the reports.

He made the original request in 2012 for the reports to be published. I requested one of them. He went to the original First Tier Tribunal and to Leicester Magistrates Court last month to cross examine the DWP’s witness. The points he made were quoted by the tribunal in its submission.

It’s campaigners like John Slater (and Dave Orr) who have helped to make FOI legislation more effective than it would otherwise have been.

If the DWP continues to pour money into fighting the disclosure of the reports in question, it will confirm to some of us that, when it comes to its own interest, that is its interest as a bureaucracy,  it may not be a fit authority to manage the spending of public money.

I hope it will release the reports now. It is time it started distinguishing between the public interest and its own.

Universal Credit FOI tribunal ruling – March 2016:  077 110316 Final Open Decision