Section 95


It is clear that in neither of its responses was TCS suggesting that knowledge transfer would not take place, but rather that planning in detail at that point would be subject to charges, on the basis that Clause 3.2.7 expressly entitled TCS to charge at rates agreed between the parties in respect of the provision of planning. At that time, on any view, the comment made placed the ball firmly in DBS’s court and, pursuant to Clause 3.1 of Schedule 2-11, it was for the parties together to resolve the comment.
Mr Padannayi’s evidence in cross-examination was consistent with this. He accepted that the sort of knowledge transfer plan ultimately produced in October 2019, after the notice of intended transfer had been given and when DBS had provided their document ‘TCS Exit Services Requirements’ had been issued, could have been produced earlier, but that DBS did not request this. Indeed, it is clear from the comments DBS themselves advanced that they were not at this point seeking the sort of comprehensive training programme ultimately included in v0.18. The comments at 3.2.7 suggested that DBS was anticipating that (for example) the STP record that TCS would in the future undertake an analysis of training needs with DBS and/or replacement contractor i.e. during the transition stage when the replacement contractor had been identified. When questioned about the ability to have produced his comprehensive plan sooner, he accepted that this was technically feasible, but he gave the following evidence, which I accept (Day 5/9):
So I think you told us this is a document you
produced without any input from DBS. So would it be
right to understand that if you'd been asked to produce
this much earlier in the project, you would have been
able to do so?
A. I mean, I wasn't asked to produce it, definitely, and
I wasn't even in that role of doing this. Yeah, if
there was an ask from DBS to produce this specifically
-- I mean, I don't think there was anything technically
preventing us from doing this.
Q. So something like this, this kind of information and
detail could have been provided much earlier in
the project if there had been an ask for it?
A. Specific to the knowledge transfer, could have been.
Could have been provided, yeah.
Q. So it would have been possible to break down each one of
the workstreams and identify the kind of information you
need to know about those workstreams and the kind of
information that a new supplier would need to be fed in
terms of information at a much earlier stage than end of
Have I understood that right?
A. Can I just clarify something on that? You have to also
understand, as you showed in the previous statement,
the process it took me, the time it took me and
the people it took me to do this.
Q. Yes.
A. So here, we were officially into the transition stage
and I had access to those dedicated people, the process
I explained where I went to Mr Kuncheria and he
supported me. So, I don't know -- I don't want to
speculate now would it have been possible in the absence
of that official service transition window, because
I don't know if I would have got dedicated time from so
many experts to put this together. So -- so purely at
that technical level -- sorry, purely at the technical
level, it would have been feasible, but provided all
these people could have been dedicated for this activity
at that stage.
Q. So, if it had been appropriate to put something like
this kind of detail, or at least some parts of this
detail into a Service Transfer Plan at an earlier stage,
your evidence is that would have been possible so long
as enough people were available to engage with providing
the information; is that right?
A. That is correct, yeah.
The reality lies somewhere in the middle of both parties’ positions. The sort of details of how knowledge transfer would take place identifying a minimum level of provision, as suggested in the type of relatively high level comments on v0.9, would be required if the STP was to be regarded as compliant with Schedule 2-11. As accepted by Mr Britton in cross-examination, most of the additional detail in v0.18 in respect of knowledge transfer (and other matters) was not reliant on selection of a replacement contractor. To this extent, I regard the STP as having fallen short of contractual requirements. I reject the submission, however, that the detailed planning undertaken by Mr Padannayi (and alluded to in the first general comment within the v0.9 comment spreadsheet), which was a very significant piece of work detailing 253 sessions and delivery metrics, was something which ought to have been provided as part of the STP, unless DBS were prepared to pay for it pursuant to Clause 3.2.7 at that point. There is no suggestion that DBS responded to TCS in this regard. I also accept Mr Britton’s evidence that it is difficult to see how this level of detailed planning in respect of knowledge transfer (rather than in general principles) would be important to know in advance of the identification of the replacement contractor(s) and nature of the transfer. Finally, it does not follow that TCS should simply have adopted all the suggestions of DBS in respect of Clause 3.2.7 identified in the extract above, even though it gives an indication of the relatively high level information to be provided. I can understand, for example, the reticence of providing an STP which said barely, ‘Delivery of training to suit the needs of DBS’, even if that training was to be on a paid basis.
I conclude, therefore, that v0.9 did not comply with Clause 3.2.7 of Schedule 2-11, although TCS would not have had to produce something significantly different to the high level ‘outline’ identified by DBS’s own comments in relation to 3.2.7 in order for the document to be contractually compliant. That would be significantly less detail that that which TCS was ultimately able to include in v0.18 which followed Mr Padannayi’s comprehensive planning exercise once notice of transfer had been given.
- 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)