Select Committee on Work and Pensions Third Report


3 DWP and Suppliers

61. In this section we consider a number of issues concerning DWP's relationships with its IT suppliers, examining in particular the role of PFI, competition, innovation and accountability.

What was wrong with using PFI?

62. In July 2003, the government quietly reversed its policy on the use of the Private Finance Initiative (PFI) for new computerisation projects and concluded that there should be a "strong presumption against PFI for IT projects".[113] Although PFI may have benefits for other capital projects, its use for IT contracts has created problems. We consider some of the major difficulties below.

Discouraged suppliers

63. We have established that PFI discouraged some large IT suppliers, such as IBM, from competing for the lead in IT business. IBM told us that they were discouraged by the long term nature of the deals and the unacceptable risk and reward profile of PFI deals. In written evidence, IBM stated:

The principal reason for this is that the asset is generally intellectual property and that this changes as projects progress. Taking a risk on tangible assets such as buildings which can have a predictable financial recovery stream is a great deal different from funding business processes which are the subject of both internal and external change. Essentially, it is difficult to manage the risks as a supplier when the control points (Governance and management systems) for managing risk are not with the supplier.[114]

Nick Kalisperas told us that within the IT industry PFI was never popular; "it was an ill-considered concept to apply to the IT industry. "[115]

64. On the other hand, other contractors, such as EDS (with 85% of DWP's contracts) were not discouraged. Tom Warsop (EDS) told us:

PFI was very difficult and is very difficult, because we still have contracts that are under the PFI framework.......What we did was we put in very significant risk mitigation strategies, because we knew that there were unique risks because of PFI. So we put in risk mitigation strategies and, from a big picture perspective, I think it has worked out OK. We have certainly had some challenges.[116]

65. Since ending the presumption in favour of PFI for IT systems, more suppliers are likely to become interested in bidding for Government IT business. This applies both to large companies such as IBM, and smaller suppliers who were put off by PFI.

Not amenable to best practice

66. Another weakness of PFI was that it did not allow much opportunity for success. John Cross (DWP) told us that the way some deals were structured meant that,

the projects started out with their hands tied behind their back, in the knowledge of what we would regard as best practice. I think it is this notion that the risk is being transferred over to the supplier in a rather complete way, which is all right for "set piece" projects - you can build something like a bridge or a hospital in such clearer definitional terms. A systems project is a much more dynamic process, especially over a multiple year period.[117]

John Cross went on to say that IT projects "were not amenable to best practice." [118] He added that this had since changed and that DWP was,

no longer operating within the PFI construct, the rules of the game of how you address best practice are all amenable to us now, and that is why I think the IS strategy we now have around us […], certainly has all the major components of what I would expect to see in best practice, and gives me significant comfort.. [119]

The illusion of risk transfer

67. Ms Whittaker (EDS) told us that "when projects do go wrong, usually it is attributable to two things. One is the management of risk on the project and the other is the governance structure. When we get those things right, we are successful. " [120]

68. The Secretary of State told us that alongside the IS/IT structures, DWP has put in place "robust risk management processes."[121] However, our evidence indicates that there is insufficient compliance with good practice, suggesting that management of risk and governance, especially project planning, are still under-developed. We are unable to know the extent of the problem within DWP because of non-publication of key documents, such as business cases and Gateway Reviews, which we discuss later. But on the basis that adherence to best practice by departments remains patchy, we remain concerned that deals are being signed and projects are being managed that do not follow best practice.

69. The Treasury has had a long-standing requirement that PFI deals should involve a genuine transfer of risk.[122] Identification of risk and its efficient management is something that runs through much of the evidence. However, identifying and transferring risk can create problems. A number of witnesses made the point that in addition to identifying the political and normal commercial risks, it was important that risks be transferred to the partners with the capability and authority to manage it.[123] But before this can happen, business requirements needed to be fully understood, agreed and priced accordingly. Tom Warsop (EDS) told us that departments cannot transfer all of the operational risk; they can transfer a certain amount of financial risk and certain other risk, but not operational risk.[124] Clearly, some risks cannot be transferred to the IT supplier, especially when systems involve social security benefits. According to Professor Collins, it is only the financial risk that is typically considered and transferred.[125] PCS said that it was not aware of the details of the contractual penalties that may be applied to EDS for the under-performance of CS2, but "from the outside it would appear that any risk transfer is purely financial. "[126] Mr Michael Hartley told us that "in a lot of programmes the expectation is that if you apply some financial inducement to an organisation to take that risk on that they are also capable of managing, and I do not think that is always the case. "[127] In the event of a failure of an IT supplier contracted to provide benefits, the DWP would have little alternative to intervening directly to absorb the risk (cost) itself by providing the service or bailing the supplier out. In this way, the transfer of such operational risks to the supplier would prove as illusory as the government seeking to transfer risk in, say, the civil nuclear industry; if the business goes belly up, the government has to intervene. Michael Hartley confirmed this when he told us that in the event of a failed IT system, the IT supplier would not be able to "get their calculators out and make decisions on how much somebody was going to be paid, that is very much the job of the CSA organisation and therefore there is a limit on the amount of risk that can be transferred. "[128] In short, by forcing an inappropriate transfer of risk onto a supplier, DWP may find that business risks simply get bounced back to be absorbed by the department.

70. Nick Kalisperas (Intellect) told us that his members had indicated that the public sector is quite comfortable transferring risk to suppliers but, because of the political risks involved, is not as comfortable transferring control of projects to suppliers. [129]

71. In written evidence, DWP identified key risks that relate to a project and those that are appropriate to be transferred to the supplier.[130] For example, DWP told us that it seeks to achieve effective transfer of appropriate risks by contracting for outputs, not inputs; agreeing a firm/fixed price at the outset; linking payments to the quality of service received and making payments only when service is received. If delays have a material effect on the Department, then it may seek compensation/damages from suppliers, including the right to terminate for failure to deliver, or for continuously poor performance. DWP described how in 2002 it applied a new model of governance to its major IT projects to improve the management of risk through more robust accountability and stewardship. According to DWP, the governance model used encourages decision-making at the most appropriate levels and a gated review process. DWP also described the Departmental Change Board, chaired by the Permanent Secretary of the Department with Senior Responsible Owners, which has responsibility for reviewing the progress of the Department's "mission critical" IT programmes and authorising key milestones, such as the launch of new public services. EDS argued that, "in all cases, DWP retains overall accountability for business outcomes." Garter stated: "The risk transfer statements we have seen are those associated with delivery and operation of IT solutions and not the broader business solutions. "[131] EDS also pointed out that evaluation of risk was made more difficult when fixed price contracts and risk transfer required before the business specifications are understood and agreed.[132] PCS expressed concern that, for the CSA reform, contractors faced insufficient incentives to improve their performance.[133]

72. According to the Treasury, PFI was an unsuitable vehicle for IT projects for a number of reasons. The Treasury stated:

The concern raised by [...] research is that expectations in the IT industry and among public sector procurers are set too low. But more importantly it demonstrates that the qualitative differences between PFI in IT and PFI in other sectors have a significant impact on the way that IT PFI has been delivering. The difficulties with achieving appropriate risk transfer in IT PFI, because of the need for significantly greater flexibility than in other sectors, the high degree of integration into the other business operations of the procuring authority, and the lack of third party finance, mean that it may not be the appropriate value for money procurement route for IT.[134]

73. Currently, there are no PFI projects within Jobcentre Plus.[135] We also heard that Pension Credit, which adheres to best practice principles throughout, is also not a PFI project. The Secretary of State told us:

Clearly there are important lessons to be learned from the earlier requirements that you should do everything by PFI if at all possible. We have learned from the experience, as indeed the Treasury guidance has informed us, that in IT cases that may not be appropriate, it may not be the best or even the most timely way, or the most cost-effective way of securing the services we want. Those lessons have been learned and that is why we are applying a new framework for procurement for the future.[136]

74. We welcome the Government's reversal of its policy, but are concerned that it has taken it so long to recognise the unsuitability of using PFI for IT projects, especially when it was well known that PFI was generally disliked by the IT industry. We are concerned that a number of important projects, such as CS2 and the pension forecasting project, remain as PFI projects, although in the latter case officials told us that it is now much closer to best practice.[137] In our view, the continuing existence of the remaining PFI IT projects suggests that the Department has only partially learnt the lessons about the unsuitability of PFI contracts. We are concerned that the PFI nature of the contracts continues to create a number of problems, including an ambiguous risk transfer and lack of incentives for suppliers. We appreciate that in some cases, a PFI deal can succeed. For example, we heard that the IT for Oyster cards, which is a PFI deal, on Transport for London is working very well.[138] However, the overwhelming evidence is that PFI is generally unsuitable for IT projects and that principle should apply to existing deals as well as new deals. We recommend that the Government makes an early statement of policy on how it proposes to proceed with all IT projects that continue to operate under PFI rules.

How competitive is the market?

75. In our call for evidence, we asked if there was an effective competitive process in the awarding of IT contracts by DWP. This question arises in the light of the degree to which Government IT business is concentrated in the hands of very few IT suppliers, and in the case of DWP, one dominant supplier: EDS. Although there is a large amount of sub-contracting of DWP contracts, we established that EDS had been awarded contracts to the value of some £4.5bn, or 85% of DWP IT business by value,[139] over 40% of which comprises continuing operational and service delivery functions.[140] Across central Government as a whole, EDS, which is ranked as the second largest IT supplier in the world, has captured 54% of the share of the central civil government IT services market. The following table provides the various rankings.






Table 1: Comparative ranking of major IT service companies in global and UK markets 2002-03
Rank Company Share of global IT services market

%

Share of UK IT services market

%

Rank in UK central civil government market for IT

services

Share of central civil government IT services market%
1IBM 7.011.2 14Less than 1*
2EDS 3.112.6 154
3Accenture 2.06.3 62
4HP 1.84.2 N/AN/A
5CSC 1.75.3 101
6Cap Gemini Ernst &Young 1.24.0 N/AN/A
7Getronics 0.60.6 N/AN/A
8Atos Origin 0.40.8 N/AN/A
9Fujitsu Services 0.35.5 213
10LogicaCMG 0.23.6 52

Source: Increasing Competition and Improving Long-term Capacity Planning, OGC, December 2003, page 15

76. The figures on market share clearly reveal an exceptionally high dependency by DWP on EDS. The 2003 study by the OGC which pointed out that only some of the world's largest IT companies have been active in the UK government market - with EDS a particularly prominent player - recommended that, "Departments should systematically pool market intelligence and share strategic information about future programmes and current projects, with a view to better understanding the totality of the public sector's likely demands on industry and the nature of the market necessary to meet those demands. "[141]

77. In assessing how competitive the procurement process is, it is useful to briefly outline the relationships that DWP has with three consortia (Affinity, Arcway, and Accord) as well as the 10 year strategic partnership relationship (IT Partnership Agreement (ITPA)) with EDS.[142] For the Employment Service, EDS was contracted to deliver all IT services, although it employed sub-contractors for some of then.[143] In an agreement signed in 2000 with the Affinity consortium, led by EDS, DSS agreed to the creation of a largely single-supplier environment, based on a partnering relationship.[144] The benefit of a partnering relationship is that it allows a closer relationship to develop between supplier and client throughout the life of the programme, which is expected to improve the chance of success when framing project specifications or resolving other issues, such as training.[145] By entering into consortia, IT suppliers provide sufficient capacity in a more managed fashion in order to deliver large government IT programmes. The potential advantage of consortia to the Department is that they are less risky than relying on a single contractor.[146] We heard that the Department used organisations such as Gartner to help assess suppliers' proposals and the value for money of projects. Gartner told us that these assessments delivered three types of conclusion:

The supplier proposals are satisfactory and pass the procurement test;

The supplier proposals appear to have been overpriced and cannot be justified, areas of challenge have been provided to the Department and these have been used to assist them in their commercial negotiations; and

The supplier proposals appear to be overpriced and there may be a risk of failure to deliver.[147]

78. EDS told us that the competitive environment for DWP work was "healthy and hungry, " but accepted that the procurement processes could be improved by focusing on the total value for money rather than only lowest price.[148] Indeed, OGC guidance is very clear that this is the right approach, so we are concerned that DWP's main supplier sees the Department as focussed on lowest price.[149] IBM stated:

Our experience is that there is effective competition in the award of IT contracts with the DWP. Competition is achieved in the early stage, through the award of a framework contract after a competition. Subsequent to the award of the framework, individual contracts for the provision of specific services are issued to the supplier who was successful in winning the framework contract. We believe that the use of competition at the framework stages as opposed to at the stage of individual contract awards is effective since it reduces the time cost and financial cost of repeated, smaller competitions without removing the benefits of competition in ensuring value for money. It is important to note that the time and financial costs of competition fall on the Department as well as on suppliers.

The DWP has used third party expert organisations to undertake an independent review of value for money using benchmarking techniques at these stages and IBM believes this is appropriate.[150]

79. In written evidence, Gartner concluded that the process is competitive to some extent, but recognised that "there are limitations on its effectiveness where a small number of suppliers have an almost monopolistic position in terms of knowledge of the existing IT environment and operational control of that environment. "[151] But Gartner also considered that, for long term partnerships, price competition was less important and the "lack of a strong competitive process should not be considered a failure. "[152] In oral evidence, Michael Hartley (Gartner) told us that the value for money question was about more than just price; it was also about being able to deliver the solution and working in a long term relationship where technical capability of organisations changes over time.[153] He added:

The organisation itself may change shape; its technical priorities may change; the needs of the organisation acquiring the technology will change; and therefore you have to have a degree of flexibility in the way that organisations are allowed to work to bring in new unique capability and to swap out certain capabilities. [154]

80. In written evidence, Computer Sciences Corporation (CSC) made the point that all contracts let by DWP should be subject to public procurement rules.[155] It also argued that a supplier, such as EDS, which had been chosen to supply a significant proportion of the service should continue to be part of the procurement process. It stated that it would be unwise not to consider the dominant supplier in all procurements that might affect the scope of that service.[156] Some witnesses were less convinced about the degree of competition. PCS stated that the competitive process lacked commercial transparency and criticised the decision to award CS2 to Affinity/EDS as a result of an existing arrangement between the Department and Affinity.[157] The Treasury also pointed to the difficulty of substituting suppliers if a contractor failed to meet its obligations.[158] Avi Silverman (Kable Ltd) told us that the lack of competition allowed IT suppliers to have government officials "over a barrel. "[159] However, it was recognised that departments faced a dilemma when wanting to exchange views with IT suppliers without providing them with an undue advantage.[160] In written evidence, Aqera, a software development company, criticised its lack of access to officials, despite its expertise in developing internet based software for pension forecasts and online retirement planning.[161]

81. Competition can also be affected by an incumbent supplier. CSC told us that the presence of an incumbent supplier tended to act as a barrier to entry, although large companies could overcome this by "building relationships over the long term and gradually eroding the likely (or actual) scope of the major supplier. "[162] Of course, this is likely to exclude small and medium sized suppliers who, unable to mobilise the time and money, would be effectively barred from competing against the dominant supplier.[163] CSC stated that it was not clear how DWP ensured that small-medium sized enterprises (SMEs) were included in procurement or whether DWP actively challenged their large suppliers to forge partnerships with smaller organisations.[164] We recommend that the Department should by 1 April 2005 publish detailed plans on how it proposes to increase involvement of SMEs in the IT procurement process in future.

Is competition increasing?

82. Competition is increasing, not least because of the Government's decision to abandon PFI for IT projects. But there are ways in which the competitive process could be improved. Firstly, the number of supply routes could be increased. We were pleased to see that the Department has recently sought to do this. For example, in November 2003 the DWP advertised new framework deals with the aim of providing "additional supply routes, including re-letting existing contracts as they come to an end. "[165] The potential gains from this approach are that it generates smaller discrete contracts, to the potential benefit of smaller businesses and reduces the dominance of the major IT supplier. The obvious potential problem for the Department, however, is the multiplicity of suppliers and projects and the pressure this places on the Department's in-house programme management team as they try to keep a handle on the projects, or the IT suppliers. Secondly, the procurement process should allow the dominant supplier to innovate or collaborate more with other suppliers in dealing with changing business needs. EDS told us that supplier lock-in should be avoided and that flexibility must be built into the contracting of large complex programmes. According to EDS, this flexibility would provide mechanisms for dealing with the inevitable changes in requirements.[166]

83. Thirdly, competition could be improved by encouraging the number of bidders, especially from the SME sector, by offering financial assistance. As noted above, when contracts are up for renewal, the incumbent supplier is likely to be in a very strong position, especially when bidding costs are high. Sarah Arnott (Computing) told us that smaller businesses were prohibited by the high bidding costs from competing for contracts and added that "suppliers routinely spend millions of pounds and delegate hundreds of staff to work on major public sector bids, and the process often takes as long as two years to complete."[167] The high bidding costs associated with public sector contracts discourage suppliers from competing in re-tendering processes.[168] With such high costs, the public sector is disadvantaged compared with the private sector. We were told that there have been two notable examples (Inland Revenue and the Driver and Vehicle Licensing Agency) where an incumbent supplier of 10 years, in both examples EDS, had failed to win the competition. Sir Peter Gershon told us that the two cases showed that "where there have been re-competes, there is not a pattern that the incumbent wins. "[169] He also pointed out that in the case of the Inland Revenue re-compete, it had to make a contribution of some £33 million towards the bidders' costs as a way of encouraging bidders, but in the context of total value for money this was apparently regarded by the Inland Revenue as justified.[170] We also heard that the Government was becoming more robust in writing into the deal the principle that: "if you do not do what you say you are going to do we are going to throw you out."[171]

84. We understand that the procurement process can be more streamlined, including using standardised basic terms and conditions across Whitehall, while also allowing individual departments to focus on those areas specific to their project.[172] We understand that OGC is piloting a new procurement process which requires less information from suppliers at the pre-qualification stage.[173] We look forward to seeing how this streamlining develops.

85. Self-evidently, the Department's high dependency on one dominant supplier is unhealthy. We welcome the Department's attempts to diversify its range of IT suppliers. We expect to see competition for DWP contracts become more intense with the ending of PFI for IT projects and as the number of re-competes increases.. We recommend that the DWP investigates ways of helping bidders with their tender costs incurred when competing for contracts.

Is there scope for innovation?

86. One area where organisations may be able to make a mark in IT is by being innovative. During our inquiry we heard details of the pioneering work that Citizens Advice (CA) is undertaking to become an e-intermediary so that it can act as a trusted partner for using DWP's computer systems directly. CA told us that by providing secure direct access to DWP's systems, it would improve the support it could provide to its clients. CA also supplied us with details of an innovative system in Woking where it is working in partnership with the local authority as an e-intermediary.[174] We note that CA was awarded a £20 million grant to develop its role as an e-intermediary. In our view, it is important that DWP continues to support such innovative partnerships. We recommend that the DWP actively explores using the services of organisations like the CA to improve the delivery of services.

87. For too long, full accessibility for disabled users has been a neglected area of the design and implementation of IT programmes. In written evidence, the Royal National Institute of the Blind (RNIB) emphasised the importance of specifying accessibility criteria in project design so that disabled staff and users could benefit from IT programmes.[175] RNIB made the point that, "most IT project managers, procurers, developers and contractors have little awareness of the importance of accessibility to software users, whether disabled or not."[176] RNIB stated that as an employer and service provider, the DWP is

"in danger of failing to meet its duties under the Disability Discrimination Act and needs to look carefully at how it administers IT projects in the future particularly with reference to; the views of the DWP Accessibility Solutions Team regarding new standards based on ISO/TS16071; the E-Envoy's Web guidelines; future guidance from the OGC relating to implementation of the EU Public Procurement Directive; and the likely introduction and enactment of a Disability Bill containing provisions for a duty on public authorities to eliminate discrimination against disabled people and to promote equality of opportunity.[177]

88. We call upon the Department to set out how it will ensure that its IT projects are fully in line with the highest standards of accessibility and to provide reassurance that it will fully meet its duties under the Disability Discrimination Act.

89. We also received some material on Cùram, a successful commercial off-the-shelf piece of software that is used in social security systems in a number of countries. Cùram has been developed by an Irish SME.[178] Members of the sub-committee were invited to attend a demonstration of Cùram at the IBM offices in London. The demonstration was helpful in illustrating some of the benefits that such software offered to departments over a bespoke system: it is tried and tested; has scalability, which means that it is sufficiently flexible to be expanded to include a range of functions; and, perhaps, most importantly, it allows departments to switch IT suppliers if necessary without wasting the investment already committed to the bespoke software. A specific example of this increased flexibility was demonstrated when the DWP decided to appoint IBM as a major contractor for building the CMS project within Jobcentre Plus while EDS help the Department with testing and implementing.[179] This example provides some basis for optimism. In addition, we are hopeful that the revised IS/IT strategy should encourage more use of COTS software and should lead to greater opportunities for SMEs to become involved.

Is there proper accountability?

90. In our call for evidence, we asked whether commercial confidentiality was, at times, used unnecessarily to obscure proper transparency and accountability. We received some interesting responses. Written submissions generally interpreted commercial confidentiality in two ways. DWP interpreted the term widely to mean the public release of information and stated that the key test in determining whether information should be publicly disclosed was the possible effect publication might have on the "Department's ability to compete in business or negotiate its contracts effectively in future."[180] In PCS's view, more information, such as the cost of the contract and penalties for delay, should be put into the public domain.[181] We agree. We recommend that more information, such as the cost of the contract and penalties for delay, should be put into the public domain. As PCS told us: "There appears to be a lack of accountability for EDS, despite the large amounts of public money that they are receiving from the taxpayer. "[182] Suppliers, on the other hand, discussed confidentiality in terms of the relationship between themselves and the Department. For example, IBM said that sensitive information such as that relating to its internal cost and therefore internal margin (profit) was necessary for the organisation to monitor its internal efficiency, but not required to measure the effectiveness with which it delivers the external contract to its client and so should not be disclosed.[183] CSC stated that commercial confidentiality was normally a legislative or regulatory matter and that suppliers would not be allowed to share certain information with customers, although it did recognise that a fair contract should allow sharing of information under some circumstances, such as for auditing purposes.[184] In written evidence, EDS stated:

Commercial confidentiality has its place. That said, relationships are built on trust, with common objectives, and do rely on transparency to ensure progress and continued constructive intent. Within sensible commercial parameters, transparency should be maintained to the greatest possible extent on highly complex programmes such as those undertaken by the DWP.[185]

91. Gartner also focused on confidentiality between the Department and suppliers, saying "commercial confidentiality exists in many guises in the relationships between the Department and its suppliers. There is a tendency on the part of many suppliers to use the term as a means of limiting the exposure to the Department of the true nature of many aspects of their relationship, including: costs of resources provided by the suppliers, numbers of resources deployed by the suppliers; and internal processes employed by the suppliers." [186]

92. We mainly consider the release of information to Parliament and into the public domain. We recognise that IT suppliers may be very sensitive about disclosing certain information about internal costs and profit data. However, in our view there is a great deal of other information concerning service delivery and reliability that is not directly commercially sensitive, but which would help Parliamentarians to ensure that public funds are well spent and projects are managed effectively. It is the lack of this information that is of most concern to us. We heard a number of examples of commercial confidentiality used to deny legitimate inquiry. For example, Avi Silverman told us that the specification for integrated care records for the NHS IT programme was not published on the grounds of commercial confidentiality with the suppliers. He added, however, that when it was eventually published "there was nothing in that specification that was commercially confidential, that you could possibly say was commercially sensitive. There was a lot in it about the programme that they were going to do and a lot of detail about their ideas for care records, which you could say are in the public interest. "[187] Tony Collins, (Computer Weekly), told us that whereas departments and IT suppliers could be very open with each other, they were unduly secretive when dealing with the media.[188] He told us he had had difficulties obtaining information from CSA. He said:

I have quoted to them things that have been in the public domain which your committee has discussed with them and I have asked them, "Is that still the case? " They have quoted commercial confidentiality back at me.[189]

93. Sarah Arnott, also told us that sometimes commercial confidentiality was used to prevent crucial information from being put into the public domain and "was certainly used as a smokescreen at times. "[190] We agree. She said that in the case of an IT contract that had recently been signed that had "blatantly ignored a whole raft of best practice, " commercial confidentiality had made it difficult to find out from official sources whether the reports were true.[191] The lack of proper Parliamentary scrutiny was demonstrated by the problem we had during the course of this inquiry. We made a number of requests to the Department for documents relating to CSA, such as the contract, OGC reviews, recovery plan and a review of the recovery plan by Gartner. We were disappointed that our requests were refused or, as in the case of the CSA contract, such documents were provided with so much black-lining, as to be incomprehensible. Of course, we understand the need to protect genuine "commercial confidentiality" in the narrowest sense, but we felt that on occasions the secretive approach adopted by the Department and the Government, in the form of the OGC, had little to do with commercial confidentiality and more to do with departments using it as an excuse to withhold information that rightly belonged in the public domain, but which might embarrass the Department if released publicly. In our view, the lack of parliamentary accountability is part of the reason for the relatively high number of defective IT projects.

94. During the course of our inquiry we were struck by how open IT suppliers seemed prepared to be in contrast with the tendency of officials to invoke commercial confidentiality. We have heard a lot of evidence justifying commercial confidentiality, most of it from Government departments. But in oral evidence, the Secretary of State made an offer of the categories of information that he thought (a) could be disclosed in public, (b) could be shown in private to the committee and (c) would not be in the public interest to divulge at all.[192] For example, he said that he would be happy to publish the following information: material on suppliers chosen; the amount paid to date to a particular supplier under a particular contract; the amount paid out to a company as a whole across a number of contracts; the broad outline of provisions in contracts; the fact that the contracts have either led to a reduced payment or withholding of payments; an outline of the circumstances where those reductions might be applied, the types of circumstances where termination might be considered, and the types of circumstances where compensation to DWP might be considered. The information that he said he would make available to the Committee, sometimes under restrictive terms if aspects related to commercially sensitive matters, included: the overall value and time period of the contract; the details of service levels which are agreed and required; the proportion of payments withheld and that they have been withheld; amounts paid to DWP on account of supplier non-performance. The Secretary of State said that the following items were unlikely to be published: unacceptable suppliers; the level of acceptable fault; financial model and operational capacity models and correspondence relating to alleged breaches or possible litigation.[193]The details are set out in a memorandum.[194]

95. The Secretary of State also said that it would be helpful if the Department and the Committee could develop a joint approach to this issue. We welcome this offer from the Secretary of State, which we understand is the first time a government Minister has set out formal proposals for making information on IT contracts publicly available.[195] We too are interested in developing a mutually acceptable protocol for the exchange of information that respects genuine commercial confidentiality while at the same time allowing Parliament to scrutinise the executive effectively. We acknowledge that the range of information on offer would represent an increase compared with what is currently available to Parliament, and in that sense it is a good starting point. We expect that guidelines will need to be produced by OGC in collaboration with bodies such as Intellect. We welcome the offer to develop a set of guidelines to cover increased access to information on IT contracts and agree that the proposals put forward by the Secretary of State do provide the basis for further consideration.

96. In the next section we consider some options for increasing the success rate of IT projects, focussing in particular on the need to make them more open and accountable.


113   Ev 129. In drawing up the replacement for PFI in IT projects, the OGC, amongst others, was consulted. Back

114   Ev 155 Back

115   Q 128 Back

116   Q 491 Back

117   Q 318 Back

118   Q 466 Back

119   Q 320 Back

120   Q 466 Back

121   Q 569 Back

122   For example, see,: "More Private Finance Initiative: Deals Expected As Clarity Of Accounting Standards Is Resolved" - Alan Milburn, Press release, HM Treasury, 24 June 1999  Back

123   For examples, EDS (Ev 95), Professor Collins (Q 130), Gartner (EV 135), and IBM (Ev 150-1) Back

124   Q 492 Back

125   Qq 123-4 Back

126   Ev 120 . This issue of imposing financial penalties in the case of CS2 is discussed in section six. Back

127   Q 126 Back

128   Q 129 Back

129   Q 127 Back

130   Ev 108 Back

131   Ev 135 Back

132   Ev 97 Back

133   Ev 121 Back

134   "PFI: meeting the investment challenge", HM Treasury, July 2003 Back

135   Q 322 Back

136   Q 558 Back

137   Q 322 Back

138   Q 491 Back

139   Q 351 Back

140   Ev 224 Back

141   Increasing Competition and Improving Long-term Capacity Planning, December 2003  Back

142   Details of the membership of the various consortia are set out in EV 197 Back

143   EDS being required to obtain prior agreement to the appointment of sub-contractors. Back

144   Ev 158Further details on consortia are in Ev 105 Back

145   Ev 157-8. IBM identifies a number of strong advantages of close collaboration and partnering between departments and IT suppliers. Back

146   Ev 157 Back

147   Ev 135 Back

148   Ev 95 Back

149   For example, see OGC'sleaflet on Value for Money  Back

150   Ev 150 Back

151   Ev 135 Back

152   Ev 135 Back

153   Q 171 Back

154   Q 171 Back

155   Ev 101 Back

156   Ev 101 Back

157   Ev 120 Back

158   See revised Treasury guidance on the delivery of IT contracts in the civil service: "PFI Meeting the Investment Challenge" July 2003 Back

159   Q 211 Back

160   Q 212 Back

161   Ev 99-100 Back

162   Ev 101 Back

163   The Office of Fair Trading launched a study following recommendations from the Better Regulation Taskforce warning that smaller suppliers are being shut out of government procurement, including technology procurement.  Back

164   Ev 102 Back

165   Ev 158 Back

166   Ev 96 Back

167   Ev 158 Back

168   According to Sarah Arnott, the DVLA accounts listed costs of £33m associated with changing suppliers. Back

169   Q 55 Back

170   The Inland Revenue recently signed contracts with a new technology supplier, Cap Gemini Ernst & Young, in a ten year partnership. This partnership will replace their previous partnership with EDS/Accenture. Back

171   Q 214 Back

172   Ev 158. We understand that the government and industry are consulting on the first draft clauses. Back

173   Ev 158 Back

174   Q 460 Back

175   Ev 162 Back

176   Ev 163 Back

177   Ev 164 Back

178   Cùram is the Irish Gaelic for "care and protection". Back

179   Q 372 Back

180   DWP also commented that its contracts protected from public disclosure the Supplier's Intellectual Property Rights. Back

181   Ev 121 Back

182   Ev 120 Back

183   Ev 152 Back

184   Ev 102 Back

185   Ev 95 Back

186   Ev 135 Back

187   Ev 162 Back

188   Ev 142 Back

189   Q 196 Back

190   Q 201 Back

191   Q 197-9 Back

192   Q 580 Back

193   Q 580 Back

194   Ev 233-4 Back

195   "Minister opens up on contracts", Computer Weekly, 27 Tuesday April 2004 Back


 
previous page contents next page

House of Commons home page Parliament home page House of Lords home page search page enquiries index

© Parliamentary copyright 2004
Prepared 22 July 2004