ICA 2013
ICA 2013
The ICA and associated agreements were signed by Mr Rockmann and Mr Rastall of Winsopia in August 2013. Nicola Bushnell of IBM returned signed copies of the agreements directly to Mr Rastall at Winsopia. In response to a request by Ms Bushnell, Mr Rastall stated that the type of business undertaken by Winsopia was information technology.
On 21 August 2013 Nick Dowling of IBM emailed Mr Rastall about creating a customer number for Winsopia:
“I’m trying to create a customer number for Winsopia on behalf of Nicola - but the request has been rejected due to an invalid VAT number. Nicola gave me the number VAT ID: CHE-164.625.611 MWST but the number should be in the following format …
I’ve tried just using the numerals in CHE-164.625.611 MWST but that is not valid. Can you please check and send me the correct number?”
Mr Rastall responded by return with the correct VAT number for Winsopia, apologising for the confusion.
Ian Lyon, the First Line Sales Manager of Systems business at IBM confirmed in cross-examination that IBM kept customer records in a database at the time:
“Q. … Now, having seen this description of the customer master record database, does that jog your memory at all in relation to the existence of such a database?
A. I recognise a number of the terms in here which – that we would hold against customer records, yes.
Q. And they're all sensible things that you'd need to know. You'd need to know who the client was you were with, what the legal structure of the client was, what industry they were in, who was dealing with them and so forth, yes?
A. That's pretty much accurate, yes.
Q. And without that, you'd be flying blind if you tried to do any sales, wouldn't you?
A. So in terms of the sales process, it's actually unusual for sellers to use that data. But it's clearly helpful data.”
Mr Lyon’s evidence was that in the case of a new customer, he would not expect a seller at IBM to undertake due diligence about a customer’s corporate structure or shareholding. Mr Lyon stated that if a customer wanted to purchase equipment using credit, the Global Finance team at IBM, a separate part of the IBM Group, might ask a seller to obtain certain documents or provide information but this would not extend to any analysis by the sales member. As a result, he would not expect members of the sales team actively to look for red flags when engaging with new or existing customers.
The defendants submit that the above exchange shows that IBM must have been aware of LzLabs because the VAT number originally obtained by Ms Bushell was the Swiss VAT number for LzLabs. It is said that the only reasonable inference for the court to draw is that as part of the registration process IBM became aware that LzLabs was linked to Winsopia (most likely as a result of checking Companies House which recorded LzLabs as the parent of Winsopia or carrying out searches in relation to Mr Rockmann) and had carried out checks in relation to LzLabs itself (hence IBM had LzLabs’ VAT and Commercial Registration Numbers).
The inference which the defendants invite the court to draw is a stretch given the circumstances of the exchange. The source of the LzLabs’ VAT reference obtained by IBM is not obvious; it could have been provided erroneously by RSM or Winsopia; hence Mr Rastall’s apology for the confusion. There is no evidence that IBM carried out any search at Companies House that would have disclosed Winsopia’s parent company as LzLabs. For the reasons explained by Mr Lyon, such due diligence would only be conducted where the issue of Winsopia’s credit standing was an issue, for example, if it wished to lease the equipment or purchase using credit finance. As Winsopia decided not to purchase equipment from IBM using such terms, it did not prove necessary for IBM Global Finance to carry out any checks.
- 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)