IntroductiON
IntroductiON
The Disclosure and Barring Service (‘DBS’) is a non-departmental public body. It was formed in 2012 through the merger of the Criminal Records Bureau and Independent Safeguarding Authority. Its stated aim is to help employers make safer recruitment decisions each year by processing and issuing DBS checks for England, Wales, the Channel Islands and the Isle of Man. It also maintains the Adults’ and Children’s Barred Lists, making decisions as to whether an individual should be included on one or both of these lists and barred from engaging in regulated activity. Tata Consultancy Services Limited (‘TCS’) is a company supplying business process outsourcing and IT services. By an Agreement (‘the Agreement’) dated 4 December 2012, TCS was retained by DBS to take over the manually intensive business-as-usual (‘BAU’) Disclosure and Barring processes (referred to as ‘R0’ in the Agreement) from the incumbent supplier, Capita, whilst building a new system to modernise DBS’ processes and replace its previous paper-based processes with digital ones in parallel (the new ‘R1’ software). The Agreement expired through effluxion of time in 2020.
The modernisation project did not go well. There were immediate challenges with transition, leading to delay and revision of Milestones. The responsibility for delays up to November 2015 is not in dispute. By early 2016, the parties had agreed new Go-Live dates for the different parts of the R1 software: R1 Barring on 15 September 2016, R1 Disclosure (‘R1-D’) on 28 November 2016; and R1 Basics on 1 January 2017. Ultimately, R1 Barring and Basics (referred to compendiously below as ‘R1-B&B’) went live together on 7 September 2017. DBS contend that, upon going live, it suffered from serious defects.
R1-D was removed from the scope of the Agreement by what DBS contends was a lawful Partial Termination on 19 September 2018, an act TCS contends was in fact an unlawful repudiatory breach, albeit one which was not accepted. Responsibility for the delays lies at the heart of TCS’s claim and a large part of DBS’s counterclaim: TCS contends that its attempts to progress and Go-Live with the modernised systems were frustrated by DBS through mismanagement of its IT hosting provider, Hewlett Packard Enterprises (‘HPE’; later known as DXC), and later by the (strategic) decision to abandon part of the modernisation project, a decision it says was made but hidden from it for many months. By contrast, DBS contends that the availability of technical infrastructure and conduct of HPE did not cause any critical delay. Instead, it says the true cause of delay was that TCS’ software was not ready to be deployed on the infrastructure. The delivery dates were missed, DBS contends, due to problems with TCS’ own development and testing of the software.
TCS’s loss said to be caused by DBS’s breaches of the Agreement is pleaded in the sum of £110,229.124, together with a claim for £14,373,099 claimed as an underpayment of Volume Based Service Charges. DBS counterclaims for losses arising from the delays and defects in the pleaded sum of £108,705,984, although certain of these claims were abandoned prior to or at trial.
- Heading
- CONTENTS
- IntroductiON
- The Factual Witnesses
- Expert Evidence
- Programming Experts
- Forensic Accounts
- The Parties Submissions
- Principles Applicable to Issues of Construction
- The Defendant’s Obligations and Responsibilities
- Clause 15
- Clause 9.5 which states
- Clause 14.5 of Schedule 2-6 which states
- The Delay and Notice Provisions
- Clause 7
- Conditions Precedent: Clauses 5 and 6
- Conditions Precedent: the authorities
- Clause 5.6
- Clause 6
- Clause 8
- Limitations of Liability
- A single or multiple caps?
- The Delay Damages cap under Clause 52.2.5
- Is TCS’s claim for loss of anticipated costs savings excluded by Clause 52?
- Compliance with Clause 5.3, Agreement and Estoppel Introduction
- Express Agreement
- Estoppel
- Introduction
- R1 B&B Delays
- Mr Britton’s First Analysis
- Mr Britton’s Second Analysis
- Conclusion on Mr Britton’s Analyses
- TCS’s submission based upon Mr Jardine’s analysis
- Responsibilities for Delay on the ‘Infrastructure’ Critical Path
- R1-D
- Compliance with Notice Provisions
- Analysis of Delays
- Up to August 2017
- From August 2017 to 19 September 2018
- Analysis
- Failed to confirm its desired functional scope of R1 Disclosure in relation to the Customer-to-Business portal and Accountable Officer’s Update Service functionality. Such confirmation was a prerequis
- Failed to make available an end-to-end test environment for the Interactive Voice Response system
- Failed to agree upon a data migration approach, without which the Claimant could not complete the build of a data migration environment so that anonymised data could be made available for testing
- Failed to ensure that relevant external stakeholders were available to participate in Final Systems Integration Testing
- Partial Termination
- TCS’s Claims
- Non-Manpower Costs
- Anticipated Cost Savings
- Summary of TCS’s Delay Claim Recovery
- DBS’s Claims
- Delay Payments
- R1-B&B Delay
- Disclosure Scotland Extension Costs – Item 1 of the Updated Schedule of Loss
- Loss of Anticipated Savings – Item 3 of the Updated Schedule of Loss
- R1-D Delay
- R0 Licence Costs – Item 4 of the Updated Schedule of Loss
- R0 Hosting and Infrastructure Costs - Item 5 of the Updated Schedule of Loss
- R0 Technology Refresh – Item 6 of the Updated Schedule of Loss
- R0 N-1 Sustainment Costs – Item 7 of the Updated Schedule of Loss
- R0 Maintenance Costs – Item 8 of the Updated Schedule of Loss
- Savings
- Introduction
- Quality-related Obligations
- Good Industry Practice and Defects
- Digital by Default Standards
- Section 71
- The Basics Portal
- Section 73
- The Barring Portal
- Section 75
- Section 76
- Barring Portal: Loss of productivity - Item 11 of the Updated Schedule of Loss
- LPF Portal
- Siebel Useability Issues
- Redaction
- Document naming, bundle creation and performance
- Adobe Licence (Item 20)
- Document Storage (Item 21)
- Other B1 Barring Quality Issues
- Scan on Demand
- Special Characters
- Letters
- Item 24 : Loss of Efficiency Claims arising out of R1 Barring Quality/Useability Issues
- N-1 Sustainment Costs
- Causation and Loss
- Exit/Service Transfer
- Identification of all services (3.2.2)
- Knowledge Transfer (3.2.6 and 3.2.7)
- Section 95
- Providing all documentation to a replacement contractor (3.2.1 and 3.2.10)
- The identification of all leases, maintenance agreement and support agreements in connection with the provision of the services (3.2.3)
- Providing any other information or assistance reasonably required by a replacement contractor (3.2.14)
- Causation and Loss
- The Security Incidents
- The Charges Variation Dispute Introduction
- Issue 1: How the amount of an ‘over-recovery of the Forecast Revenue’ (Clause 2.8.4) or ‘under-recovery of the Forecast Revenue’ (Clause 2.8.5) is to be measured
- Section 104
- Issue 4: How Clause 2.8.5 of Schedule 2-3 applied to Volume Based Service Charges in Service Year 5
- Issue 2: Whether the Predicted Volumes for Basics in Service Year 4 were 1,000,000 (TCS’s case) or 320,374 (DBS’s case)
- Conclusion on Volume Based Service Charge
- Conclusions
![HT-2020-000448 - [2024] EWHC 1185 (TCC)](https://backend.juristeca.com/files/emisores/logo_yJUntHA.png)