Mr Knight - 2017
Mr Knight - 2017
Paul Knight was the sales manager responsible for the Winsopia account. His main point of contact at Winsopia was Mr Rastall. On 17 May 2017 Mr Knight contacted Mr Rastall by email regarding the potential purchase of a mainframe by Winsopia. Mr Knight explained in the email that if the equipment were to be leased from IBM, IBM Global Finance would require Winsopia to provide financial information:
“For us to provide you with a firm lease price we would require full year 2016 annual accounts for WINSOPIA LTD and full year 2016 consolidated figures for top parent LzLabs GmbH to be able to make a credit decision. ”
This email shows that Mr Knight must have been aware that LzLabs was Winsopia’s parent company; but it does not follow that he must have been aware of Winsopia’s role in development of the SDM. Mr Knight explained in cross-examination that, when he wanted to offer a lease arrangement to a client, he would first go to IBM Global Finance, who would identify what information was required in respect of the corporate entities. He stated that but for the request from IBM Global Finance, he would not have known that LzLabs was the parent of Winsopia and he otherwise knew nothing about LzLabs.
In cross-examination, Mr Knight stated that he was unaware of all categories of information entered in the IBM database in respect of customers and did not consider it reliable:
“Q. And you would have looked at the records kept by IBM in order to see who the customers were, what equipment they'd got and so on and so forth; correct?
A. Yes.
Q. And there would have been a database in existence at that time, at the beginning of 2013, which held that information; correct?
A. Yes. Yes.
Q. And can you recollect that on that database there were fields which allowed you to see what sector the company was operating in?
A. Perhaps, yeah.
Q. What the legal structure of the company was?
A. Not so sure about that.
Q. Who the parent was?
A. Not sure about that.
…
Q. You haven't looked, have you, at the company database?
A. If I'm brutally honest about IBM's database at the time, it was absolutely hopeless.”
On 18 May 2017, Mr Rastall replied to Mr Knight, informing him that Winsopia wanted to purchase the equipment outright, without finance. As a result, Mr Knight did not make any further inquiries into LzLabs or make any other inquiries regarding Winsopia’s credit worthiness. Such limited reference to LzLabs was not sufficient to put Mr Knight, let alone IBM, on notice that Winsopia might have involvement in LzLabs’ development of the SDM.
The defendants submit that the link between Winsopia and LzLabs was known by IBM and was in the public domain; the link was discoverable on the Companies House website from July 2013 and Mr Rockmann and Mr Cresswell were publicly listed as directors of both companies. However, Mr Knight’s evidence was that prior to the request from IBM Global Finance, he had never previously heard of LzLabs and did not know anything about its business or products. Further, he did not know about the SDM or that LzLabs was developing any product that might be considered competitive to IBM. Because Mr Rastall promptly indicated that he did not wish to pursue any leasing arrangement, no further inquiries were made as to Winsopia’s corporate structure or financial standing. Therefore, there was nothing to put IBM on notice that it should carry out a search on the Companies House website or otherwise investigate the legal structure of Winsopia and its parent company.
- 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)