Section VI - Wrongful procurement of breach
Section VI - Wrongful procurement of breach
The pleaded case is that LzLabs, LzLabs UK, Mr Cresswell, Mr Rockmann and/or Mr Moores procured the breaches of the ICA. It is alleged that each and every breach by Winsopia of the ICA was undertaken at the direction, instruction or request of LzLabs (with the assistance of LzLabs UK), Mr Cresswell, Mr Rockmann and/or Mr Moores, each of whom knew and intended that the breaches should occur, or were reckless as to the same.
It is alleged that Mr Cresswell and Mr Rockmann are liable for procuring breaches of the ICA by virtue of their capacity as directors of Winsopia. It is said that they knew that Winsopia had acquired an IBM mainframe and entered into the ICA for the purposes of developing and operating the SDM and that Winsopia intended to reverse assemble, reverse compile or otherwise reverse engineer parts of the software or to allow others to do so. It is alleged that it is inconceivable that they did not review the terms of the ICA and appreciate that the proposed activities amounted or would give rise to breach of its obligations, or they were reckless in respect of the same.
Further, it is alleged that Mr Moores, the ultimate beneficial owner of LzLabs, Winsopia and LzLabs UK, exerted control over the corporate defendants, so that they followed his instructions in relation to the development of the SDM. It is said that Mr Moores directed and coordinated the development of the SDM, participating in the detail of its development, testing and marketing. In so doing, Mr Moores gave instructions and took steps that knowingly and intentionally induced and/or facilitated breaches of the ICA.
The allegations of wrongful procurement of breach of the ICA are denied. The defendants’ case is that Winsopia and LzLabs went to considerable lengths to maintain operational separation, to establish and follow formal processes for the exchange of information and documents and to monitor and segregate communications between them, in order to ensure that the provision of services by Winsopia to LzLabs was at all times fully compliant with the ICA.
Reliance is placed by the defendants on the clean room process. The Services Agreement between LzLabs and Winsopia provided that the Codes of Conduct would prevail in all cases and must be complied with by both parties at all times. The Codes of Conduct imposed restrictions to ensure separation of the work by LzLabs and Winsopia and respect for third party intellectual property rights, including restrictions on communications between Winsopia staff and LzLabs, restrictions on access by LzLabs to Winsopia’s premises and the mainframe, and external legal oversight. Pursuant to the DR procedure, a request from an LzLabs developer for information or documents from Winsopia could only be made and responded to via a supervised response procedure. Any response given by Winsopia to such requests was stored and processed in an electronic DR system. Pending review by external lawyers, responses were redacted as necessary, to ensure that they did not contain any materials whose supply to LzLabs would be prohibited by the Code of Conduct, including any ICA Program or part thereof.
The defendants’ case is that they relied reasonably and in good faith on the clean room processes and thereby believed that Winsopia would not breach any of its obligations under the ICA. LzLabs UK did not exist until 23 September 2015 and did not assist Winsopia in relation to the acts giving rise to breach of the ICA. Mr Cresswell believed at all material times that all activities undertaken by Winsopia complied with the terms of the ICA and there was never any activity of which he was aware which he thought might have breached the ICA. Mr Rockmann did not in his capacity as a director and executive officer of Winsopia ever direct, instruct or request Winsopia or any of its employees to engage in any activities that amounted to or gave rise to breaches of the ICA. Mr Moores did not know of or intend any breach of the ICA to occur nor was he reckless about any such breach. He did not instruct or take steps that knowingly and intentionally induced and/or facilitated breaches of the ICA. At all times, Mr Moores understood Winsopia to be acting in compliance with the ICA and the applicable law.
Further, Mr Cresswell and Mr Rockmann each rely by way of defence on the principle in Said v Butt [1920] 3 KB 497, namely: (i) they were officers and/or employees of Winsopia; (ii) they were acting in good faith in the performance of their duties to Winsopia; and (iii) they were acting within the scope of their authority in respect of the activities of Winsopia about which complaint is made.
- 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)