CA Inc v Independent Systems Integrators Pty Ltd (No 3)

Link copied
Case Copied 7 min read

FEDERAL COURT OF AUSTRALIA

CA Inc v Independent Systems Integrators Pty Ltd (No 3) [2009] FCA 1176

CA INC and CA (PACIFIC) PTY LIMITED v INDEPENDENT SYSTEMS INTEGRATORS PTY LTD

NSD 1572 of 2008

PERRAM J
16 OCTOBER 2009
SYDNEY


IN THE FEDERAL COURT OF AUSTRALIA

NEW SOUTH WALES DISTRICT REGISTRY

GENERAL DIVISION

NSD 1572 of 2008

BETWEEN:

CA INC
First Applicant

CA (PACIFIC) PTY LIMITED
Second Applicant

AND:

INDEPENDENT SYSTEMS INTEGRATORS PTY LTD
Respondent

JUDGE:

PERRAM J

DATE OF ORDER:

16 OCTOBER 2009

WHERE MADE:

SYDNEY

THE COURT ORDERS THAT:

1.The motion is dismissed.

2.Macquarie Bank Limited is to pay the Respondent’s costs of the motion.

Note:Settlement and entry of orders is dealt with in Order 36 of the Federal Court Rules.


The text of entered orders can be located using eSearch on the Court’s website.


IN THE FEDERAL COURT OF AUSTRALIA

NEW SOUTH WALES DISTRICT REGISTRY

GENERAL DIVISION

NSD 1572 of 2008

BETWEEN:

CA INC
First Applicant

CA (PACIFIC) PTY LIMITED
Second Applicant

AND:

INDEPENDENT SYSTEMS INTEGRATORS PTY LTD
Respondent

JUDGE:

PERRAM J

DATE:

16 OCTOBER 2009

PLACE:

SYDNEY

REASONS FOR JUDGMENT

Background

  1. On 7 September 2009 I ordered the respondent (“ISI”) to provide preliminary discovery to the applicants (together “CA”).  The reasons which explain why those orders were made were delivered by me on 18 August 2009, sub nom CA Inc v Independent Systems Integrators Pty Ltd (No 2) [2009] FCA 900. Macquarie Bank Limited (“MBL”), who was not a party to those proceedings, now applies to be joined as a party, to be granted leave to make submissions regarding the withdrawal or reconsideration of my reasons for judgment and for the provision by ISI of further preliminary discovery.

    Argument

  2. MBL’s basic complaint is that it has been adversely referred to in CA Inc (No 2) without having been given an opportunity to put its position.  In my previous decision, I concluded that there was reason to suppose that CA had, or might have, a right to obtain damages for infringement of copyright by ISI or MBL.  More particularly, I concluded that since Mr Richards (of ISI) had worked for MBL at the relevant time it was possible, indeed on a preliminary basis probable, that CA’s software had been directly copied by Mr Richards to produce 2BDB2, its manuals used to the same effect or its software reverse engineered.

  3. Since Mr Richards worked for MBL at the relevant time, I concluded that such a case might exist against MBL.

    Consideration

  4. I do not think that it is necessary to consider the nature of the procedural right infringed by adverse comment in a judgment on preliminary discovery.  I proceed on the assumption that a sufficient interest is shown. 

  5. It seems to me that MBL has been adversely named without having been heard.  In that circumstance it is entitled to be heard to put its side of the matter.  On the present application MBL led evidence which established the following two propositions:

    (a)the software ultimately sold by ISI…

CaseChat AU logo

Keep reading for free

Create a free CaseChat account to read CA Inc v Independent Systems Integrators Pty Ltd (No 3) and more:

  • Read every judgment in full
  • Ask AI and get answers linked to paragraphs
  • See how each paragraph was cited in later cases
  • Download judgments as PDF or Word
Continue with Google

One click creates your free account or signs you in.

By continuing you agree to the Terms and Privacy Policy.

Details
Case
[2009] FCA 1176
Decision Date

CaseChat Overview and Summary

The case of CA Inc v Independent Systems Integrators Pty Ltd (No 3) involved CA Inc as the plaintiff, Macquarie Bank Limited (MBL) as an intervener, and Independent Systems Integrators Pty Ltd (ISI) as the defendant. The dispute revolved around the ownership and development of certain software, specifically whether ISI had unlawfully used or replicated CA's software in its operations. The matter was heard in a lower court, where preliminary discovery orders were sought by CA against ISI and MBL.

The primary legal issues that the court needed to address were whether MBL had a sufficient interest in the proceedings to intervene and whether the software ISI developed was substantially different from that of MBL. Additionally, the court had to determine whether MBL's software development process involved any unlawful copying or reverse engineering of CA's software. The court examined evidence presented by MBL, which included an explanation of the technical differences between the software developed by MBL and ISI, and the process by which MBL created its software.

After considering the evidence and arguments presented, the court found that MBL had a legitimate interest in the proceedings, as it had been adversely named without an opportunity to be heard. However, the court did not find sufficient grounds to alter its previous conclusions regarding the differences between the software developed by MBL and ISI. The court accepted MBL's evidence that its software development process did not involve reviewing, disassembling, or reverse engineering CA’s software. Consequently, the court dismissed the motion for preliminary discovery against MBL and ordered MBL to pay the respondent's costs of the motion.

The final orders of the court were that the motion was dismissed and that MBL was to pay the respondent’s costs of the motion. This decision underscored the importance of providing parties with an opportunity to be heard and the need for clear evidence to support claims of software infringement.

Orders

Orders of the court

1. The motion is dismissed.

2. Macquarie Bank Limited is to pay the Respondent’s costs of the motion.

Note:

Background

Background to the litigation

Full text does not contain this section.

Evidence

Evidence Before The Court

Full text does not contain this section.

Decision

Reasons for decision

PERRAM J

Full text does not contain this section.

Ratio Decidendi

Legal Principle Established

Established by: PERRAM J

Since Mr Richards worked for MBL at the relevant time, I concluded that such a case might exist against MBL.Consideration I do not think that it is necessary to consider the nature of the procedural right infringed by adverse comment in a judgment on preliminary discovery. I proceed on the assumption that a sufficient interest is shown. It seems to me that MBL has been adversely named without having been heard. In that circumstance it is entitled to be heard to put its side of the matter. On the present application MBL led evidence which established the following two propositions:(a)the software ultimately sold by ISI was not the same software originally developed by MBL; and(b)the process of development by which MBL created its software did not involve a review of CA’s software or any attempt to disassemble or reverse engineer it. Proposition (a) was borne out by a fee dispute which arose between ISI and MBL. In CA (No 2) I explained that initially MBL licensed its software to ISI and then subsequently assigned that software to ISI. It now appears from the evidence prepared by MBL that ISI contested MBL’s entitlement to the license fee due under that license. It did so because ISI contended that the software it was distributing was different to MBL’s software, with the consequence that no fee was due. That dispute was eventually resolved with MBL’s assignment of the rights in the software to ISI. This evidence does not lead me to alter my previous conclusions. It does not disclose the way in which MBL’s software differed from ISI’s software, save that one was written in a language known as PL/1 code, and the other in a language known as Assembler. For myself, the fact that the two programs were written in different languages shows little. For all one knows, one may have been compiled from the other. Further, the explication given by MBL of how it had generated the code remains, at least to me, opaque. An officer of MBL, Mr McLennan, explained the matter this way: I recall that there was a layer of software sitting between the application programming code and the underlying database (the Intermediate Layer), in this case, Datacom. In a simplistic sense, the Intermediate Layer was a set of application calls or commands, known as API’s, which could be rewritten to communicate with any database (in this case DB2).The Conversion Software developed by the project team functioned by changing the Intermediate Layer to communicate with DB2 instead of Datacom. It did this by changing the Datacom commands (API calls) in the Intermediate Layer to now interact with DB2. The Conversion Software performed in the Intermediate Layer, rather than interacting directly with Datacom APIs.Because the conversion was performed through the Intermediate Layer, there was, to the best of my recollection and understanding, no need to review, disassemble, reverse engineer, or copy the underlying Datacom source code nor access it. I did not engage in any review, reverse engineering or copying of the underlying Datacom source code, nor did I observe any other member of the project team do any such acts.