R0 Technology Refresh – Item 6 of the Updated Schedule of Loss
R0 Technology Refresh – Item 6 of the Updated Schedule of Loss
The Updated Schedule of Loss states that these sums are ‘to be assessed, estimated at £15,517,357’. The costs relate to the work undertaken at DBS’s cost to refresh the legacy R0 systems, including making changes to the WAN, switches, virtualisation, internal networks and internet gateway. None of the costs, either external or internal, relate to the only period for which a claim would be valid.
I add that this element of the claim also demonstrates the difficulty with DBS’s approach at trial to paint these costs as ‘delay’ costs rather than costs attributable (as indeed its pleading describes) to non-delivery of R1-D. This is because, as a matter of causation, these costs were in fact incurred in an environment where DBS’s business strategy was to ensure the R0 infrastructure was maintained for a considerable period into the future, allowing it breathing space to find a new supplier and develop its bigger project of ‘disaggregation’ (i.e. to reduce dependence upon a single supplier). Implicit in the claim that these are costs caused by delayed delivery includes the necessary assumption that the same decisions in terms of what technology refresh to implement would have been made in circumstances where R1-D was going to be delivered, but merely delivered late, rather than not delivered at all. It is an entirely false assumption. Completely different decisions may have been made about what ‘investment’ was required in R0 if the only issue was ongoing delay to the delivery, rather than in the situation driven by DBS’s own strategy where R1-D was not to be delivered at all by TCS, and not delivered by anyone else to any foreseeable timetable. The pleading’s description of these costs – as relating to the non-delivery of R1-D – is therefore correct, and the characterisation in submission of these costs as caused by ‘delay’ is wrong. Even if, therefore, DBS is correct that (contrary to the factual reality) one should characterise the period beyond 19 September 2019 as ongoing delay to the delivery of R1-D (because its Partial Termination was legally ineffective), it would not follow that these costs could be characterised as ‘delay’ costs. Such a conclusion would involve a leap of both fact and logic.
This claim fails.
- 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)