Category Archives: Legacy ICT

DWP “evasive” and “selective” with information on Universal Credit programme

By Tony Collins

Has the Department for Work and Pensions put itself, to some extent, beyond the scrutiny  of Parliament on the Universal Credit IT programme?

Today’s report of the Public Accounts Committee Universal Credit progress update was drafted by the National Audit Office. All of the committee’s reports are effectively more strongly-worded NAO reports.

If the Department for Work and Pensions cannot be open with its own auditors – the National Audit Office audits the department’s annual accounts – are the DWP’s most senior officials in the happy position of being accountable to nobody on the Universal Credit IT programme?

The National Audit Office and the committee found the Department for Work and Pensions “selective or even inaccurate” when giving some information to the committee.

In answering some questions, the committee found officials “evasive”.

Today’s PAC report says:

“We remain disappointed by the persistent lack of clarity and evasive responses by the Department to our inquiries, particularly about the extent and impact of delays. The Department’s response to the previous Committee’s recommendations in the February 2015 report Universal Credit: progress update do not convince us that it is committed to improving transparency about the programme’s progress.”

On the basis of the limited information supplied by the DWP to Parliament the committee’s MPs believe that the Universal Credit has stabilised and made progress since the committee first reported on the programme in 2013, but there “remains a long way to go”.

So far the roll-out has largely involved the simplest of cases, and the ineligibility list for potential UC claimants is long.  By 10 December 2015, fewer than 200,000 people were on the DWP’s UC “caseload” list.

The actual number could be far fewer because the exact number recorded by the DWP by 10 December 2015 (175, 505)  does not include people whose claims have terminated because they have become ineligible by for example having capital more than £16,000 or earning more so that their benefits are reduced to zero.

The plan is to have more than seven million on the benefit, and the timetable for completion of the roll-out has stretched from 2017 originally to 2021,  although some independent experts believe the roll-out will not complete before 2023.

Meanwhile the DWP appears to be controlling carefully the information it gives to Parliament on progress. The committee accuses the DWP in today’s report of making it difficult for Parliament and taxpayers to hold the department to account. Says the report,

“The programme’s lack of clear and specific milestones creates uncertainty for claimants, advisers, and local authorities, and makes it difficult for Parliament and taxpayers to hold the Department to account.”

These are more excerpts from the report:

“In February 2015 the previous Committee of Public Accounts published Universal Credit: progress update … The Department accepted the Committee’s recommendations.

“However, we felt that the Department’s responses were rather weak and lacked specifics, and we were not convinced that it is committed to ensuring there is real clarity on this important programme’s progress.

“As a result, we recalled both the Department and HM Treasury to discuss a number of issues that concerned us, particularly around the business case, the continuing risks of delay, and the lack of transparency and clear milestones.

“Recommendation: The Department should set out clearly how it is tracking the costs of continuing delays, and who is responsible for ensuring benefits are maximised.

“The Department does not publish accessible information about plans and milestones and we are concerned by the lack of detail in the public domain about its expected progress.

“For proper accountability, this information should be published so that the Committee, the National Audit Office and the general public can be clear about progress…

“… the Department did not acknowledge that the slower roll-out affects two other milestones, because it delays the date when existing claimants start to be moved onto Universal Credit and reduces the number of Universal Credit claimants at the end of 2019.

“The flexible adaptation of milestones to circumstances is sensible, but the Department should be open about when this occurs and what the effects are. Instead, the Department’s continued lack of transparency makes it very difficult for us and the public to understand precisely how its plans are shifting.

“Claimants need to know more than just their benefits will change ‘soon’; local authorities need time to prepare additional support; and advisers need to be able to help people that come to them with concerns…

“Recommendation: By May 2016, the Department should set out and report publicly against a wider set of clearly stated milestones, based on ones it currently uses as internal measures, including plans for different claimant groups, local authority areas and for the development and use of new systems. We have set out the areas we expect these milestones to cover in an appendix to this report…

“The Department was selective or even inaccurate when highlighting the findings of its evaluation to us.”

The DWP has two IT projects to deliver UC, one based on its existing major suppliers delivering systems that integrate the simplest of new claims with legacy IT.

The other and more promising solution is a far cheaper “digital service” that is based on agile principles and is, in effect, entirely new IT that could eventually replace legacy systems. It is on trial in a small number of jobcentres.

The DWP’s slowly slowly approach to roll-out means it is reluctant to publish milestones, and it has reached only an early stage of the business case. The final business case is not expected before 2017 and could be later.

The committee has asked the DWP to be more transparent over the business case. It wants detail on:

  • Projected spending, including both investment and running costs for:
  • Live service (split between ‘staff and non staff costs’ and ‘external supplier costs’)
  • Digital service (split between ‘staff and non staff costs’ and ‘external supplier costs’)
  • Rest of programme (split between ‘staff and non staff costs’ and ‘External supplier costs’)
  • Net benefits realised versus forecasts.

Meanwhile the DWP’s response to those who criticise the slow roll-out is to give impressive statistics on the number of jobcentres now processing UC claims, without acknowledging that nearly all of them are processing only the simplest of claims.

Comment

To whom is the DWP accountable on the Universal Credit IT programme? To judge from today’s report it is not the all-party Public Accounts Committee or its own auditors the National Audit Office.

No government has been willing to force Whitehall departments to be properly accountable for their major IT-enabled projects or programmes. Sir Humphrey remains in control.

The last government with Francis Maude at the helm at the Cabinet Office came close to introducing real reforms (his campaign began too forcefully but settled into a good strategy of pragmatic compromise) but his departure has meant that open government and greater accountability for central departments have drifted into the shadows.

The DWP is not only beyond the ability of Parliament to hold it accountable it is spending undisclosed of public money sums on an FOI case to stop three ageing reports on the Universal Credit IT programme being published. The reports are nearly four years old.

Would that senior officials at the DWP could begin to understand a connection between openness and Lincoln’s famous phrase “government of the people, by the people, for the people”.

Public Accounts Committee report Universal Credit, progress update

DWP gives out “selective” information on welfare reform even to its auditors (a similar story in 2015)

Department for Work and Pensions “evasive” – Civil Service World (This article is aimed at its readers who are mostly civil servants. It is likely it will find favour with senior DWP IT staff who will probably mostly agree with the Public Accounts Committee’s view that the DWP hierarchy is, perhaps because of culture, evasive and selective with the information it gives to Parliament and the public.)

 

Is HMRC spending enough for help to replace £10.4bn Aspire contract?

By Tony Collins

Government Computing reports that HM Revenue and Customs is seeking a partner for a two-year contract, worth £5m to £20m, to help the department replace the Aspire deal which expires in 2017.

HMRC is leading the way for central government by seeking to move away from a 13-year monopolistic IT supply contract, Aspire, which is expected to cost £10.4bn up to 2017.

Aspire’s main supplier is Capgemini.  Fujitsu and Accenture are the main subcontractors.

HMRC says it wants its IT services to be designed around taxpayers rather than its own operations. Its plan is to give every UK taxpayer a personalised digital tax account – built on agile principles – that allows interactions in real-time.

This will require major changes in its IT,  new organisational skills and changes to existing jobs.

HMRC’s officials want to comply with the government’s policy of ending large technology contracts in favour of smaller and shorter ones.

Now the department is advertising for a partner to help prepare for the end of the Aspire contract. The partner will need to help bring about a “culture and people transformation”.

The contract will be worth £5m to £20m, the closing date for bids is 6 July, and the contract start date is 1 September.  A “supplier event” will be held next week.

But is £5m to £20m enough for HMRC to spend on help to replace a £10.4bn contract?

This is the HMRC advert:

“HMRC/CDIO [Chief Digital Information Officer, Mark Dearnley] needs an injection of strategic-level experience and capacity to support people and culture transformation.
“The successful Partner must have experience of managing large post-merger work force integrations, and the significant people and cultural issues that arise. HMRC will require the supplier to provide strategic input to the planning of this activity and for support for senior line managers in delivering it.
“HMRC/CDIO needs an injection of strategic level experience and capacity to help manage the exit from a large scale outsourced arrangement that has been in place for 20+ years.
“HMRC is dependent on its IT services to collect £505bn in tax and to administer £43bn in benefits each year. The successful supplier must have proven experience of working in a multi-supplier environment, working with internal and external legal teams and suppliers and must have a proven track record of understanding large IT business operations.
“HMRC/CDIO needs an injection of strategic level experience and capacity to help HMRC Process Re-engineer and ‘Lean’ its IT operation. HMRC/CDIO requires a Programme Management Office (PMO) to undertake the management aspects of the programme.
“It is envisaged that the Lead Transformation Partner will provide leadership of the PMO and work alongside HMRC employees. The leadership must have significant experience of working in large, dynamic, multi-faceted programmes working in organisations that are of national/international scale and importance including major transformation…”

Replacing Aspire with smaller short-term contracts will require a transfer of more than 2,000 Capgemini staff to possibly a variety of SMEs or other companies, as well as big changes in HMRC’s ageing technologies.

It would be much easier for HMRC’s executives to replace Aspire with another long-term costly contract with a major supplier but officials are committed to fundamental change.

The need for change was set out by the National Audit Office in a report “Managing and replacing the Aspire contract”  in 2014. The NAO found that Capgemini has, in general,  kept the tax systems running fairly well and successfully delivered a plethora of projects. But at a cost.

The NAO report said Aspire was “holding back innovation” in HMRC’s business operations”.

Aspire had made it difficult for HMRC to “get direction or control of its ICT; there was little flexibility to get things done with the right supplier quickly or make greater use of cross-government shared infrastructure and services”. And exclusivity clauses “prevented competition and stifled new ideas”.

Capgemini and Fujitsu made a combined profit of £1.2bn, more than double the £500m envisaged in the original business plan. Profit margins averaged 16 per cent to March 2014, also higher than the original 2004 plan.

HMRC was “overly dependent on the technical capability of the Aspire suppliers”. The NAO also found that HMRC competed only 14 contracts outside Aspire, worth £22m, or 3 per cent of Aspire’s cost.

Although generally pleased with Capgemini,  HMRC raised with Capgemini, during a contract renegotiation, several claimed contract breaches for the supplier’s performance and overall responsiveness.

When benchmarking the price of Aspire services and projects on several occasions, HMRC has found that it has often “paid above-market rates”.

HMRC did not consider that its Fujitsu-run data centres were value for money.

Comment

HMRC deserves credit for seeking to replace Aspire with smaller, short-term contracts. But is it possible that HMRC is spending far too little on help with making the switch?

HMRC doesn’t have a reputation for caution when it comes to IT-related spending.  The total cost of Aspire is expected to rise to £10.4bn by 2017 from an original expected spend of £4.1bn. [The £10.4bn includes an extra £2.3bn for a 3-year contract extension.]

Therefore a spend of £5m to £20m for help to replace Aspire seems ridiculously low given the risks of getting it wrong, the complexities, the number of staff changes involved, the changes in IT architecture, and the legal, commercial and technical capabilities required.

The risks are worth taking, for HMRC to regain full control over ICT and performance of its operations.

If all goes wrong with the replacement of Aspire, costs will continue to spiral. The Aspire contract lets both parties extend it by agreement for up to eight years. HMRC says it does not intend to extend Aspire further. But an overrun could force HMRC to negotiate an extension.

As the NAO has said, an extension would not be value for money, since there would continue to be no competitive pressure.

Campaign4Change has never before accused a government department of allocating too little for IT-related change. There’s always a first time.

Government Computing article

 

HMRC seeks smaller IT contracts – a big risk, but worth taking?

By Tony Collins

Public Accounts Committee MPs today criticise HM Revenue and Customs for not preparing well or quickly enough for a planned switch from one main long-term IT contract to a new model of many short-duration contracts with multiple suppliers.

It’s a big and risky change in IT strategy for HMRC that could put the safe collection of the nation’s taxes at risk, say the MPs in a report “Managing and replacing the Aspire contract”.

But the Committee doesn’t much consider the benefits of switching from one large contract to smaller ones, potentially with SMEs.

Is the risk of breaking up the huge “Aspire” contract with Capgemini, and its subcontractors Fujitsu and Accenture, worth taking?

Suppliers “outmanoeuvre” HMRC

The PAC’s report makes some important points. It says that HMRC has been “outmanoeuvred by suppliers at key moments in the Aspire contract, hindering its ability to get long term value for money”.

The costs of the Aspire deal have soared, in part because of extra work. Before it merged with Customs and Excise, Inland Revenue spent about £200m a year on its IT outsourcing contract with EDS, now HP.  Customs and Excise’s contract with Fujitsu cost about £100m a year.

After the Revenue and Customs merged, and a new deal was signed with Capgemini, the money spent on IT services soared to about £800m a year – arguably out of control.

HM Revenue and Customs spent £7.9bn on the Aspire contract from July 2004 to March 2014, giving a combined profit to Capgemini and Fujitsu of £1.2bn, equal to 16% of the contract value paid to these suppliers.

HMRC considers the contract to have been expensive,  and pressure to find cost savings in the short-term led it to trade away important value for money controls, says the PAC report.

“For example, in a series of disastrous concessions, HMRC  conceded its rights to withdraw activities from Aspire, to benchmark the contract prices against the market to determine whether they were reasonable,” says the report.

“It also gave up  its right to share in any excess profits. In 2007, HMRC negotiated a three-year  extension to the Aspire contract just three years after the contract was let, extending the end of the contract from 2014 to 2017.

“The Department has still not renegotiated the terms of the contract in line with a memorandum of agreement it signed in 2012 designed to separate Capgemini’s role in service provision from its role as service integrator and introduce more competition.”

Big or small IT suppliers?

The Aspire contract between HMRC and Capgemini is the government’s largest
technology contract.  It accounts for for 84% of HMRC’s total spend on ICT.

Today’s report says that Aspire has delivered certainty and continuity over the past decade but HMRC now plans a change in IT strategy in line with the Cabinet Office’s plan to break up monopolistic contracts.

In 2010, the Cabinet Office announced that long-term contracts with one main supplier do not deliver optimal levels of innovation, value for money or pace of change.

In 2014, it announced new rules to limit the value, length and structure of ICT contracts. No contract should exceed £100m and no single supplier should provide both services and systems integration to the same area of government. Existing contracts should not be extended without a compelling case.

The Cabinet Office says that smaller contracts should allow many more companies to bid, including SMEs, and provide an increase in competition.

HMRC agrees. So it doesn’t plan to appoint a single main supplier when Aspire expires in 2017.  But PAC members are worried that the switch to smaller contracts could jeopardize the collection of taxes. Says the PAC report:

“HMRC has made little progress in defining its needs and has still not presented a business case to government. Once funding is agreed, it will have only two years to recruit the skills and procure the services it will need.

“Moreover, HMRC’s record in managing the Aspire contract and other IT contractors gives us little confidence that HMRC can successfully achieve this transition or that it can manage the proposed model effectively to maximise value for money.

“HMRC also demonstrates little appreciation of the scale of the challenge it faces or the substantial risks to tax collection if the transition fails. Failure to collect taxes efficiently would create havoc with the public finances.”

The PAC recommends that HMRC “move quickly to develop a coherent business case, setting out the commercial and operational model it intends to put in place to replace the Aspire contract. This should include a robust transition plan and budget”.

Richard Bacon, a long-standing member of the PAC, said HMRC has yet to produce a detailed business case for the change in IT strategy.

“HMRC faces an enormous challenge in moving to a new contracting model by 2017, with many short-duration contracts with multiple suppliers, and appears complacent given the scale of the transformation required.

“Moreover, HMRC’s record in managing IT contractors gives us little confidence that HMRC can successfully achieve this transition or that it can manage the proposed model effectively to maximise value for money.”

Comment

The PAC has a duty to express its concerns. HMRC needs stable and proven systems to do its main job of collecting taxes. A switch from a single, safe contract with a big supplier to multiple, smaller contracts could be destablizing.

But it needn’t be. The Department for Work and Pensions is making huge IT – and organisational – changes in bringing in Universal Credit. That is a high-risk programme. And at one time it was badly managed, according to the National Audit Office. But the gradual introduction of new systems hasn’t hit the stability of payments to existing DWP claimants.

This is, perhaps,  because the DWP is doing 4 things at once: running existing benefit systems, building something entirely new (the so-called digital service), introducing hybrid legacy/new systems to pay some new claimants Universal Credit, and is asking its staff to do some things manually to calculate UC payments. Expensive – but safe.

The DWP’s mostly vulnerable claimants should continue to be paid whatever happens with the new IT. So the risks of major change within the department are financial. The DWP has written off tens of millions of pounds on the UC programme so far, says the NAO. Many more tens of millions may yet be wasted.

But many regard the risks as worth taking to simplify the benefits system. It could work out a lot cheaper in the end.

At HMRC the potential benefits of a major change in IT strategy are enormous too. Billions more than expected has already been spent on having one main supplier tied into the long-term Aspire contract (13 years).  Isn’t it worth spending a few tens of millions extra running parallel processes and systems during the transition from Aspire to smaller multiple contracts?

It could end up costing much less in the end. And running parallel new and existing systems and processes should ensure the safe collection of taxes.

If government departments are not prepared to take risks they’ll never change – and monolithic contracts and out-of-control costs will continue. Is there anything more risky than for HMRC to stay as it is, locked into Aspire, or a similar long-term commitment?

HMRC not ready to replace £10bn Aspire contract, MPs warn – Computerworld

Taxpayers face havoc from HMRC computer changes – Telegraph

Universal Credit full business case “a long way from Treasury approval”

By Tony Collins

Yesterday in Parliament Iain Duncan Smith gave a statement on Universal Credit – then MPs asked him questions.  Conservative MP Nigel Mills asked IDS a straightforward question:

“Can the secretary of state confirm that the Treasury has now signed off the whole business case and laid to rest that fear that they were not going to do that?”

IDS gave a clear reply: “That is exactly what was being asked before the summer break and the answer is they have …”

But the UC programme has not received Treasury approval for the full business case, nor even the outline business case. Today’s National Audit Office report “Universal Credit: progress update” says that the UC programme received approval in September 2014 for the “strategic outline business case” only.

An NAO official says this is a “long way from Treasury approval” of the full business case.

Until the full business case is approved, UC has no formal funding beyond the current spending review. Meanwhile the Treasury has been funding UC in “small increments” according to the NAO.

The Department of Work and Pensions is due to produce the outline business case next summer, before the next government’s spending review.

The “outline” business case is supposed to set out how the programme is affordable and will be successfully delivered. It summarises the results so far and sets out the case for proceeding to a formal procurement phase.

The “full” business case documents the contractual arrangements,
confirms funding and affordability and sets out the detailed management
arrangements and plans for successful delivery and post evaluation.

The absence of approval for the outline or full business case underlines the uncertainties still in the UC programme. Indeed the latest NAO report says it’s too early to tell whether UC will prove value for money.

But the DWP has reduced risks by extending the roll-out. The programme is now not expected to be completed before 2020. The original completion date was 2017.

The DWP has a twin-track approach to the UC IT programme. It is paying its existing main IT suppliers to support the introduction of UC – the so-called “live” service – while an agile team develops a fully-automated “digital” service that is designed to do all that the “live” service cannot do without manual intervention.

The agile system has yet to be tested – but it has cost only about £8m compared with more than £90m spent on the “live service”.

Porkies?

Labour MP Glenda Jackson, who is a member of the Work and Pensions committee, suggested to IDS yesterday that his promises to MPs on Universal Credit’s roll-out have all been broken and that he has told the House of Commons “porky pies”.

IDS replied that his intention is to ensure that UC is rolled out in a safe and secure way.

Comment:

You’d never know from IDS’s replies to MPs yesterday that the Universal Credit programme doesn’t yet have either outline business case approval or full business case approval.

In other words, the Treasury has yet to be convinced the UC programme is feasible or affordable. It is paying for the programme in increments.

IDS told MPs the programme has business case approval. He did not make it  clear that the programme has the early-stage strategic outline business case approval.

His comments reinforce the need for the National Audit Office to scrutinise the Universal Credit programme. Left to the Department for Work and Pensions, the facts about the programme’s progress, problems and challenges would probably not emerge, not in the House of Commons at least.

Some MPs have said for years that Parliament is the last place to look for the truth.

IDS also said yesterday that the original deadline for completion of UC by 2017 was “artificial” – though he has quoted the 2017 date to MPs on several occasions.

Will UC succeed?

UC as an IT-based programme is not doing too badly, to judge from today’s NAO report.

Indeed it seems that the Department for Work and Pensions, when under intense scrutiny, can start to get things right.

Though existing systems from major suppliers look increasingly unlikely to be able to handle the predicted volumes without a large and expensive amount of manual intervention, the agile digital system, though delayed by 6 months, looks promising, at a fraction of the cost of the conventional “live” system.

Scrutiny

The NAO is scrutinising the programme. The DWP’s own auditors seem to be doing a good job. The Cabinet Office’s Major Projects Authority is making useful recommendations. And the programme has an independently-chaired board. [The NAO says the programme board has been hampered by limited information and suggests this is because the DWP gives the board “good news” statements rather than facts.]

All this scrutiny is powering the programme in the right direction, though the uncertainties remain massive. As Campaign4Change predicted, the programme will not be complete before 2020. But who cares, if it works well in the end and losses are minimised?

DWP officials are learning lessons – and UC could end up as a template for big government IT-enabled programmes  The twin-track approach of using existing suppliers to deliver support for major business changes that yield problems and lessons  that then feed into an entirely new agile-based system is not a cheap way to develop government IT –  but it may work.

What DWP officials have yet to learn is how to be open and truthful to Parliament, the media – and even its own programme board.

Universal Credit: progress update

Some highlights of today’s NAO report

NAO warns over costs of further Universal Credit digital delay

Universal Credit: watchdog warns of costs of further delays

Government may have to write off more than £200m invested in IT on Universal Credit

A welcome boost for agile in government

By Tony Collins

David Wilks, Digital Performance Manager at Government Digital Service, which is part of the Cabinet Office, says there has been “incredible” interest in clarified guidance that makes it easier for departments to obtain funding for agile projects.

The guidance applies to major projects.

Wilks says on the GDS blog that the guidance will “cut bureaucracy and encourage innovation, making digital transformation easier across government”.

It means that, in most cases, government organisations can spend up to £750,000 on the first two phases of a government agile project, discovery and alpha, on the basis of Cabinet Office spending controls – without needing an HM Treasury business case.

The guidance means:

  • more use of “light-touch” Programme Business Cases
  • using agile discovery to replace the Strategic Outline Case in most cases
  • avoiding the need for a separate Full Business Case stage where procurement uses a pre-competed arrangement such as the Digital Services Framework

“For agile and finance teams in government departments, this guidance clarification has produced incredible interest,” says Wilks.

Comment

It seems fashionable to criticise the use of agile in government, perhaps because agile requires a mindset and culture that may be alien in parts of the civil service. But done well agile could help to modernise and reform central government administration.  It’s not a cure for all the problems of bloated government IT and it has risks, among them:

–  Zeno’s paradox where a project is perpetually on the point of delivering successfully but never actually does, as with the BBC’s Digital Media Initiative.

–  A so-called agile project that combines waterfall and agile approaches. It’s either waterfall or agile. It’s difficult to see how a project can be both. Those projects where there has been a hybrid agile-waterfall approach have not been successful: Universal Credit, the BBC’s DMI and an Oracle IT-related project disaster in Oregon.

That said, investigators of the “Cover Oregon” failure seem now to advocate a purer form of agile as one solution. A highly critical official report into the failure has some positive comments on agile:

“Since September 2013, CO [Cover Oregon] has been utilizing a home grown development process which is based upon agile methodologies. There are seven functional areas within the process, referred to as tables, with each table having a dedicated table lead (a mini project manager) and a dedicated business analyst. This process appears to be well orchestrated.

“Each morning there are daily “scrum” meetings for the different functional areas. While not rigidly adhering to the formal agile scrum format, these meetings serve a valuable purpose in providing a regular opportunity for various parties from a functional area to provide the latest updates on the progress across the outstanding major defects/issues …”

 

With some reservations the Cabinet Office’s initiative to cut bureaucracy and make it easier for departments to adopt agile is welcome.

 

Whitehall’s legacy ICT here to stay?

By Tony Collins

Well done to the National Audit Office for reporting in detail on some of central government’s legacy ICT. It’s clear the NAO found the research difficult, in part because some of the system performance information it was seeking had to come from suppliers because it was not held by departments.

This gives a hint of the extent to which departments such as HMRC and the Department for Work and Pensions are in the hands of IT companies.

The NAO report Managing the risks of legacy ICT to public service delivery suggests, but doesn’t say explicitly, that legacy ICT contracts are here to stay.

Attempts by the Cabinet Office to make large cuts in the costs of central government IT will be thwarted to some extent by the reliance of departments on big suppliers and big systems. Says the NAO

“A particular risk is that departments dependent on legacy ICT will find it more challenging to achieve the business transformation envisaged by the Government in its digital strategy.”

[But there appears to be little anyone can do about it.]

The NAO report says that major change that involves underlying ICT will “create a new set of risks which will increase as the degree of system change increases”.

HMRC and the Department for Work and Pensions still rely on Fujitsu mainframes with the VME operating system, which was originally developed in the 1970s to run ICL mainframes.

These are some of the NAO’s other findings:

– “We estimate that in 2011-12 at least £480bn of the government’s operating revenues and at least £210bn of non-staff expenditure such as pensions and entitlements were reliant to some extent on legacy ICT.”

– “Managing the risk of legacy ICT has also prevented some government bodies from reducing their dependency on a few large ICT suppliers, reducing competition and increasing the risk to value for money.”

– “Departments with the largest legacy ICT estates have found it challenging to achieve value for money and improve customer service. For example:

• In 2009, HMRC described its 600 systems as “complex, ageing and costly”… By the end of 2011-12, HMRC had switched off 65 legacy applications…”

• Within DWP, we have previously found that administrative errors within the benefits system were, in part, caused by poor communication between its network of some 140 systems.  However, the Department is now rationalising its ICT estate with a view to reducing the number of ICT applications by 2017.

– “The administration cost involved in using legacy ICT can be considerable. The cost of operating HMRC’s VAT collection service is £430m per annum and the cost of the DWP pension payment service is £385m per annum.”

Eight key legacy ICT risks are:

• Disruption to service continuity. Legacy ICT infrastructure or applications are prone to instability due to failing components, disrupting the overall service. Failure of the legacy ICT may be more difficult to rectify due to the complexity or shortage of components.

• Security vulnerabilities. Older systems may be unsupported by their suppliers, meaning the software no longer receives bug fixes or patches that address security weaknesses. The system may not therefore be able to adapt to cyber threats.

• Vendor lock-in. Legacy ICT systems are often bespoke and have developed more complexity over time to the extent that only the original supplier will have the knowledge to support them.

• Skills gaps. Specific skills in old programming languages may be required that are not widely available. Staff working with legacy ICT over a long period will have often developed a depth of understanding of the system that is difficult to replace.

• Manual workarounds. More manual processing can be required due to the lack of functionality within the system or its inability to interface with other systems. Examples of workarounds include performing detailed calculations outside the system on spreadsheets; re-entering data on to other systems or having to manually check for processing and input errors.

• Limited adaptability. New business requirements may not be supported by the legacy ICT. These may include requirements such as the provision of digital channels, the provision of real-time information and not being able to process transactions in a new way.

• Hidden costs. The true cost of operating the system may not be known. Workarounds to the system and the cost of the additional manual processes may not be recorded. By not having all the information available at the right time, legacy ICT may not be able to provide real-time performance information which could lead to poor decision-making.

• Business change. Due to the complexity or the limited availability of the skills required, change may be difficult, lengthy to implement and costly. This makes it difficult for the business to be responsive and changes may have to be prioritised.

–  “A potential ninth risk is that legacy ICT may be less energy efficient than modern systems.”

VME

-“ The legacy ICT we reviewed in DWP and HMRC both have origins that predate the internet and use technology based on Fujitsu’s Virtual Machine Environment (VME) operating system. Some of the applications using VME process the data in batches. Jobs are set serially such as checking the credibility of the amounts declared on VAT returns. Such a mode of operation would be incompatible with a fully digital service and so these applications may require replacement or modification. A fully digital service would then enable online end-to-end processes with systems that respond in real-time.

– “The current supplier of VME, Fujitsu, has announced that it will support the current version of VME until 2020. After this, organisations have the choice of moving to alternatives or extending VME applications by using Fujitsu’s planned managed service.”

Can legacy ICT be replaced?

–  “The scale and importance of both services, combined with the materiality of the public money they administer, have deterred both departments from replacing these systems. Neither department [HMRC or DWP] had considered replacing their legacy ICT with a completely new end-to-end service. Instead they built new functionality around existing processes or systems, replacing an existing paper-based system

“In both organisations we found that the ICT and business functions could have worked more closely together to develop a longer-term strategy for a complete end-to-end service. In addition, we found a lack of data that would enable management to assess the full cost of service and performance.”

Supplier lock-in?

– “HMRC has found it challenging achieving a ‘whole customer’ view, as its customer data is stored across a number of legacy ICT systems. Perpetuating the use of older systems creates challenges for sustaining the right technical skills, for improving customer service.”

–  “The scale, age and complexity of DWP and HMRC legacy ICT has meant that only a small number of large ICT suppliers are able to support them as they are far too complex for a small- or medium-sized business to maintain. This will be an important consideration when preparing for contract end points, even more than the age of the technology. The government has recognised the issue of vendor lock-in by announcing plans for the creation of common ICT infrastructure. Through greater separation of the business application from the physical hardware, the aim is to reduce reliance on individual vendors.”

Lack of data?

– The average number of major faults in the system is the number logged as severity 1 or 2 meaning that 10 per cent of users are unable to access the service or there is a failure of overnight processing or an inability to produce printed output for the public. DWP monitors the performance of its system on a four- or five-week period rather than calendar months. It was unable to provide us with detailed performance reports for the period under review but obtained the average quoted above from the supplier.

–  “Determining whether the management of legacy ICT within DWP and HMRC incurs hidden costs has proved challenging. DWP’s financial data was comprehensive but it lacked effective measures to assess overall service performance, quality of process activity and the reliability of its legacy ICT. This will make it difficult for DWP to robustly plan for the longer term.”

– “HMRC was still providing us with data in the very late stages of finalising this report and several months after it had originally been requested. For financial data, the late provision of data has prevented us from verifying that costs are on a consistent basis with other departments and forming clear conclusions. For performance information, we saw indications that HMRC has a good set of data that it uses in its day-to-day management. However, we were unable to fully confirm this finding or obtain sufficient data to allow us to conclude on the performance of the VAT service. The challenges we faced in obtaining data from HMRC suggest that it may face challenges in planning for the longer term robustly.”

NAO report: Managing the risks of ICT legacy to public service delivery