LzLabs UK
LzLabs UK
The pleaded case is that LzLabs UK assisted LzLabs in procuring breaches of the ICA by Winsopia. It is recognised that assisting in a breach of contract can amount to inducement where the defendant joins in with the conduct of the primary contract-breaker so as to make him an accessory to the breaking of the contract: Kawasaki per Popplewell LJ at [23]. The difficulty in this case is that there is very little evidence as to the activity of LzLabs UK in connection with the established technical breaches.
LzLabs UK was incorporated in September 2015 as a wholly owned subsidiary of LzLabs to provide a UK-based LzLabs QA team. Mr Cresswell and Mr Rockmann were appointed as directors. Mr Cresswell explained that there were three teams at LzLabs UK: the sales team, headed up by Mr Gray; the marketing team headed by Dale Vecchio; and the QA team, headed up by Graeme Hollinger. Mr Hollinger reported to Mr Durand, who was based in France, and Mr Durand reported to Mr Cresswell.
The role of the QA team at LzLabs UK was to identify the aspects of the SDM that needed to be tested, write the appropriate tests, supervise their execution and track progress of the same. Initially, LzLabs UK was housed in the same office as Winsopia. Subsequently, LzLabs UK employees were permitted to visit Winsopia’s premises. Although there was a separate office at Winsopia, consisting of meeting rooms which were set aside for LzLabs UK employees, accessed via a separate entrance, there was a common toilet facility that was shared by both companies, as was the common room and coffee station.
There is evidence that strict separation between LzLabs UK and Winsopia was not maintained. On 31 January 2017, in the course of a discussion regarding a response to DR2199 and Mr Bray’s explanation that he did not know how to test the program in question, Mr Viebrock, then a QA engineer at LzLabs UK, stated:
“May have one of the guys slide over and just do a cursory look (over someone's shoulder, of course).”
It is clear from this conversation that Mr Viebrock was aware that it was not permitted for the LzLabs UK employee to work on the Winsopia side but intended to circumvent the rules by looking over the Winsopia employee’s shoulder.
This approach, whereby the distinction between QA staff and developers was not adhered to in practice, was referred to by Mr Bleach of LzLabs UK in his email dated 4 December 2019:
“My understanding of the important - vital - divide between Development and QA is that we in QA never write code which becomes part of SDM. This is what enables me to visit Winsopia every week, enables me to talk them through any problematic DRs (no Legal representative present!), to look over their shoulders as the use z/OS.”
This was echoed by Christian Wehrli of LzLabs, who stated in an e-mail dated 29 March 2019:
“Unfortunately we can't have access to the Winsopia mainframe. And even accessing customer mainframes is a bit tricky. So far the only solution is on site education at customers (that's also how I learnt it BTW), sitting next to the customer and looking over the shoulder.
For educational purposes it's possible to visit Winsopia and have somebody walk through it, you can't just use the mainframe.”
The above exchanges undermine the defendants’ case that there was compliance with the clean room procedures. However, it does not provide support for IBM’s allegation that LzLabs UK induced any breach of contract by Winsopia. Direct communications between LzLabs UK and Winsopia, or looking over the shoulder of Winsopia’s employees whilst they were working, do not without more amount to a breach of the ICA. There are references to LzLabs UK employees, such as Mr Althen and Mr Vitale, in the email exchanges concerning identified scrubbing failures but their role appears to have been concerned to stop the practice, rather than facilitating or intending any breach. I note that a number of the original allegations relating to third party access to the mainframe (including by LzLabs UK QA engineers) were abandoned by IBM or not supported by the factual/expert evidence.
As a result, there is insufficient evidence on which to make a finding that there was persuasion, encouragement or assistance by LzLabs UK which had any causative effect on Winsopia breaching the terms of the ICA. Thus, IBM has failed to establish the required elements of inducement or intention.
- Heading
- Mrs Justice O’Farrell
- Section II - Background to the dispute
- The SDM
- Hercules
- Neon litigation
- Formation of LzLabs and Winsopia
- The ICA
- SDM development and the clean room procedures
- Launch of the SDM
- Project Eiger
- Further development of the SDM
- Audit request and termination
- Section III - The proceedings
- The Issues
- The factual witnesses
- Section IV - Construction of the ICA
- Approach to construction of the ICA
- Scope of licence
- The ICA Programs
- Customer applications
- Licensed Program Specifications
- Independent software vendors (ISVs)
- Debugging tools
- Restrictions on use of ICA Programs
- Legislative framework
- Berne Convention
- TRIPS
- WIPO
- Software Directive
- Copyright, Designs and Patents Act 1988 (CDPA)
- Applicable legal principles
- Conclusions on ICA
- Section V - Alleged breaches of the ICA
- Disassembly, decompilation and translation
- Item 2: Load Module Decompiler (“the LMD”) (Paragraph 11.2 of the Technical Particulars)
- Item 3: CICS Control Blocks Document (Paragraph 11.3 of the Technical Particulars)
- Item 4: EXEC DLI (Paragraphs 27.18 & 28.19 of RRRAPOC)
- Item 5: IBM Binder Software (Paragraph 11.4 of the Technical Particulars)
- Compiler listings – summary of the dispute
- Item 6: IGZCIVL COBOL runtime module (Paragraph 11.6 of the Technical Particulars)
- Item 7: CICS Translators (Paragraph 20.1-2 of the Technical Particulars)
- Item 8: Floating point rounding rules (Paragraph 20.3 of the Technical Particulars)
- Item 9: IBM PL/1 compiler (Paragraph 20.4 of the Technical Particulars & Paragraph 27 of the POC)
- Item 10: XML Parse statements (Paragraphs 33-38 of the Technical Particulars)
- Item 11: COBOL initialisation, branching and I/O declaratives (Paragraphs 27.4&27.5 RRRAPOC)
- Item 12: PL/I Condition handling (Paragraphs 27.10-27.12 of RRRAPOC)
- Reverse engineering through the systematic use of traces, dumps, slip traps, packet sniffing and other debugging tools techniques – summary of the dispute
- Item 13: CICS-to-CICS communications (Paragraph 28.1 of the Technical Particulars)
- Item 14: AMBLIST analysis of CICS Stubs (Paragraph 28.2 of the Technical Particulars)
- Item 15: Colesoft z/XDC and COBOL initialisation (Paragraph 28.3 of the Technical Particulars)
- Item 16: XDC and IMS (Paragraph 28.4 of the Technical Particulars)
- Additional examples
- Item 17: SLIP Traps and CICS (Paragraph 28.5 of the Technical Particulars)
- Item 18: SLIP Traps and COBOL (Paragraph 28.6 of the Technical Particulars)
- Macros and Copybooks - introduction
- Macros (Paragraphs 32.1-32.9 of the Technical Particulars) – summary of the dispute
- Item 19: DR-3246 (Paragraph 32.1 of the Technical Particulars)
- Item 20: DR-10237 (Paragraph 32.2 of the Technical Particulars)
- Item 21: DR-2753 (Paragraph 32.3 of the Technical Particulars)
- Item 22: DR-2771 (Paragraph 32.4 of the Technical Particulars)
- Item 23: DR-2796 (Paragraph 32.5 of the Technical Particulars)
- Item 24: DR-3280 (Paragraph 32.6 of the Technical Particulars)
- Item 25: DR-4281 (Paragraph 32.7 of the Technical Particulars)
- Item 26: DR-4322 (Paragraph 32.8 of the Technical Particulars)
- Item 27: DR-0847 (Paragraph 32.9 of the Technical Particulars)
- Macros - discussion
- Copybooks (Paragraphs 2.1.1.3 and 32.10-32.12 of the Technical Particulars) – nature of the dispute
- Item 28: DR-715 (Paragraph 32.10 of the Technical Particulars)
- Item 29: DR-753 (Paragraph 32.11 of the Technical Particulars)
- Item 30: DR-756 (Paragraph 2.1.1.3 of the Technical Particulars)
- Copybooks - discussion
- Transferring “unscrubbed” materials
- Item 31:Epiphany
- Item 32: Db2 Catalog table metadata
- Item 33: DSS dump
- Item 34: Kednos
- Item 35: CSECTs deliberately omitted from scrubbing
- Items 36 and 42: Unscrubbed CSECTs
- Items 37 and 40: IMS PROCLIB & DLIBATCH
- Item 38: DFHEI1 module
- Item 39: IGZXANE
- Item 41: IGZXNE3N
- Item 43: CEEBETBL, CEEBLLST, IBMPINPL & CEESG*
- Item 44: DR-4617
- Item 45: DR-171
- Item 46: Scrubbing failures
- Item 47: @@TRGLOC CSECT
- Item 48: PARMLIB & PROCLIB
- Use outside Enterprise and beyond Designated Machine
- Item 49: Brad Taylor (Paragraph 44.2 of the Technical Particulars)
- Item 50: Winsopia Pizzabox (Paragraph 44.5 of the Technical Particulars)
- Item 51: Justin Bendich (Paragraph 44.6 of the Technical Particulars)
- Conclusions on technical breaches
- Section VI - Wrongful procurement of breach
- Applicable legal principles
- LzLabs
- LzLabs UK
- Claims against the directors
- Mr Moores
- Summary on unlawful procurement
- Section VII - Unlawful means conspiracy
- Applicable legal principles
- Knowledge of unlawfulness
- Summary on unlawful means conspiracy
- Section VIII – Audit and Termination
- Validity of audit request
- Validity of termination
- Section IX - Limitation
- Contractual limitation
- Statutory Limitation
- Deliberate concealment
- Finding - section 32(1)(b)
- Finding - Section 32(2)
- Actual or constructive knowledge – legal principles
- Date of knowledge issues
- ICA 2013
- Mr Knight - 2017
- Mr Anzani - 2018
- Conclusions
![HT-2021-000363 - [2025] EWHC 532 (TCC)](https://backend.juristeca.com/files/emisores/logo_yJUntHA.png)