Submit Article
Legal Analysis. Regulatory Intelligence. Jurisprudence.
Search articles, case studies, legal topics...
Singapore

SIEMENS INDUSTRY SOFTWARE INC. v INZIGN PTE LTD

question which this suit raises is whether the Defendant may be held liable (either directly or vicariously) for Mr Win’s actions and, if so, what the appropriate quantum of damages should be. Facts The parties 3 The Plaintiff is an American company which is part of the Siemens corporate group.

300 wpm
0%
Chunk
Theme
Font
"In sum, I find the Defendant vicariously liable for the acts of copyright infringement committed by its employee, Mr Win, and assess damages at $30,574 to be paid by the Defendant to the Plaintiff." — Per Dedar Singh Gill J, Para 78

Case Information

  • Citation: [2023] SGHC 50 (Para 0)
  • Court: General Division of the High Court of the Republic of Singapore (Para 0)
  • Date: 1 March 2023 (Para 0)
  • Coram: Dedar Singh Gill J (Para 0)
  • Case Number: Suit No 746 of 2021 (Para 0)
  • Area of Law: Intellectual Property; Copyright; Infringement; Damages (Para 0)
  • Counsel for the Plaintiff: Sivagnanaratnam Sivananthan, Mok Ho Fai and Loy Ming Chuen, Brendan (Bird & Bird ATMD LLP) (Para 0)
  • Counsel for the Defendant: Jevon Louis, Tan Jing Han, Alvin and Chong Kar Yee Cristel (Shook Lin & Bok LLP) (Para 0)
  • Judgment Length: Not stated in the extraction (Para 0)

The court identified the dispute as one about whether the defendant could be held liable for the acts of its employee, Mr Win, and, if liability was established, what damages should follow. The plaintiff’s case was not confined to a single theory of liability: it advanced both primary liability and vicarious liability, and also sought damages and further relief. The court framed the matter as a structured inquiry into liability, quantum, and additional remedies. (Para 2)

The judgment’s opening framing is important because it shows that the court was not simply deciding whether infringement occurred in the abstract. Rather, the real issue was attribution: whether the employee’s unauthorised use of NX software could be legally connected to the employer in a way that would make the employer answerable in damages. That framing also explains why the court spent substantial time on agency, authorisation, and the modern doctrine of vicarious liability. (Para 2)

"The primary question which this suit raises is whether the Defendant may be held liable (either directly or vicariously) for Mr Win’s actions and, if so, what the appropriate quantum of damages should be." — Per Dedar Singh Gill J, Para 2

The court then expressly divided the case into four issues: primary liability, vicarious liability, damages, and additional damages or other reliefs. That structure governed the rest of the judgment and is the best roadmap for understanding the reasoning. (Para 19)

"Accordingly, there are four issues which arise for my determination: (a) Whether the Defendant is primarily liable for Mr Win’s actions; (b) Whether the Defendant is vicariously liable for Mr Win’s actions; (c) If the Defendant is found liable, what quantum of damages should be awarded; and (d) Whether additional damages and the other reliefs sought should be awarded." — Per Dedar Singh Gill J, Para 19

How did the court describe the facts surrounding the infringing NX software installation?

The factual narrative was straightforward but legally significant. Mr Win was an employee of the defendant. He found a Lenovo laptop at work, and the court accepted that there were no administrative controls preventing him from using it as he did. He then downloaded and installed infringing NX software on that laptop and used it repeatedly over a period of months. The court recorded that he used the software on at least 15 different occasions between December 2020 and April 2021. (Para 6)

The infringement was not discovered through a complaint by a competitor or a manual audit. Instead, it was detected through the software’s automatic reporting function. Once the defendant became aware of the issue, it investigated and uninstalled the software. Those facts mattered because they shaped both the liability analysis and the damages discussion: they showed that the infringement was real, but also that it had been uncovered through a technical reporting mechanism rather than through any deliberate disclosure by the defendant. (Para 6)

"He took the Lenovo Laptop and, discovering that there were no administrative controls, downloaded and installed the infringing NX Software on it. He used the NX Software on at least 15 different occasions between December 2020 and April 2021." — Per Dedar Singh Gill J, Para 6

The court’s factual findings also included the broader employment context. Mr Win’s role had evolved so that he had programming responsibilities requiring use of NX software. That employment context was central to the later vicarious liability analysis because it linked the infringing conduct to the work environment and to the defendant’s management of its staff and assets. (Para 6)

Why did the court reject primary liability against the defendant?

The plaintiff argued that the defendant should be found primarily liable for copyright infringement, but the court rejected that submission. The court began from the statutory language of s 31(1) of the Copyright Act, which treats infringement as occurring where a person who neither owns nor licenses the copyright does, or authorises the doing of, any act comprised in the copyright. The court then examined whether Mr Win’s conduct could be attributed to the defendant through agency or some other attribution principle. (Para 20)

"The starting point of the analysis is s 31(1) of the Copyright Act 1987 (2006 Rev Ed) (“Copyright Act”), which states that the copyright in a work is infringed if a person, who neither owns nor licenses the copyright, does or authorises the doing of any act comprised in the copyright." — Per Dedar Singh Gill J, Para 20

The court held that Mr Win’s infringing acts could not be attributed to the defendant. It reasoned that the defendant had not authorised the acts, and the employee was not acting as the defendant’s agent in a way that would make the company directly responsible for the infringement. The court therefore concluded that the primary-liability route failed at the threshold level of attribution. (Para 22)

"For these reasons, I am satisfied that Mr Win’s infringing acts cannot be attributed to the Defendant." — Per Dedar Singh Gill J, Para 22

In reaching that conclusion, the court considered the plaintiff’s reliance on the law of authorisation. It noted the four factors identified in RecordTV for determining whether authorisation liability should be imposed, and it also referred to earlier authorities on the meaning of authorisation. But the court ultimately did not accept that the defendant had sanctioned, approved, or countenanced the infringement merely because the employee had access to the laptop and the workplace environment. The absence of attribution was decisive. (Para 23)

"The CA in RecordTV Pte Ltd v MediaCorp TV Singapore Pte Ltd [2011] 1 SLR 830 at [50] specified four factors which the courts ought to take into account in determining if authorisation liability should be imposed" — Per Dedar Singh Gill J, Para 23

What did the court say about authorisation and the limits of direct infringement liability?

The court’s treatment of authorisation was careful and doctrinally grounded. It referred to the established understanding that authorisation involves sanctioning, approving, or countenancing the infringing act, and it used the RecordTV framework as the analytical starting point. That framework directs attention to control, the relationship between the parties, reasonable steps, and knowledge. The court’s use of those authorities shows that it treated authorisation as a distinct basis of liability, not as a loose synonym for employment or workplace proximity. (Para 23)

However, the court did not find the necessary elements on the facts. The employee’s unilateral decision to install and use infringing software on the Lenovo laptop was not transformed into the defendant’s own act simply because the laptop was found at work or because the employee was employed by the defendant. The court’s reasoning therefore preserved the doctrinal boundary between direct infringement and secondary or vicarious responsibility. (Para 22)

"The Defendant submits that it should not be found primarily liable for copyright infringement because Mr Win was not acting in the capacity of an agent of the Defendant." — Per Dedar Singh Gill J, Para 13

That conclusion also explains why the court moved quickly from primary liability to vicarious liability. Once attribution failed, the real question became whether the law of vicarious liability could bridge the gap between the employee’s wrongdoing and the employer’s responsibility. The court answered that question in the affirmative. (Para 22, Para 35)

The court held that the doctrine of vicarious liability, as developed in Singapore, may extend to copyright infringement. This was a significant step because it confirmed that copyright infringement is not insulated from the general law of tortious responsibility merely because it arises under statute. The court expressly stated that it was satisfied the doctrine could be applied in this field. (Para 35)

"I am satisfied that the doctrine of vicarious liability, as it has developed in our local jurisprudence, may be extended to copyright infringement." — Per Dedar Singh Gill J, Para 35

To reach that conclusion, the court relied on the general two-step inquiry from Ng Huat Seng. The first inquiry asks whether there is a special relationship between the tortfeasor and the defendant. The second asks whether there is a sufficient connection between that relationship and the tort. The court treated those inquiries as the governing framework for deciding whether the employer should bear responsibility for the employee’s infringing acts. (Para 36)

"There must be a special relationship between the tortfeasor and the defendant (“the First Inquiry”); and (b) There must be a sufficient connection between the defendant and the tortfeasor on the one hand, and the commission of the tort on the other (“the Second Inquiry”)." — Per Dedar Singh Gill J, Para 36

The court also drew on policy considerations from the authorities it cited, including the idea that vicarious liability responds to risks created by the defendant’s enterprise and to the need for compensation and deterrence. Those considerations mattered because the defendant’s management of staff and assets had created the setting in which the infringement occurred. The court therefore treated the employment relationship not as a mere formal label, but as a practical source of risk. (Para 35, Para 41)

Why did the court find a sufficient connection between employment and the infringement?

The court found that there was a sufficient connection between the employment relationship and Mr Win’s infringing acts. It reasoned that the defendant’s employment arrangements, together with the way it managed staff and assets, created and enhanced the risk of infringement. The infringing conduct was not a random act by a stranger; it occurred in the workplace, using a laptop found there, and in the context of duties that involved NX software. (Para 41)

"For these reasons, I find that there is a sufficient connection between the relationship of employment and Mr Win’s infringing acts." — Per Dedar Singh Gill J, Para 41

The court’s reasoning was not limited to the fact of employment alone. It considered the broader circumstances: the defendant’s management of the laptop, the absence of administrative controls, and the fact that the employee’s role required use of NX software. Those features made the infringement sufficiently connected to the employment relationship to justify vicarious liability. The court thus treated the employer’s operational choices as part of the causal and normative basis for liability. (Para 6, Para 41)

This part of the judgment is important because it shows how Singapore law can impose responsibility even where the employer did not direct or authorise the specific wrongful act. The court’s focus was on risk creation and connection, not on formal approval. That approach is consistent with the policy rationale the court drew from the vicarious liability authorities it cited. (Para 35, Para 36, Para 41)

What evidence did the court rely on, and why did it reject the Hitachi quotations?

The court considered a range of evidence, including Mr Win’s acknowledgments of the anti-piracy policy, the history of the Lenovo laptop, the automatic reporting function that exposed the infringement, and the parties’ evidence on licence fees. That evidential record was used both to establish the infringement and to assess the appropriate damages methodology. (Para 6, Para 69)

One evidential issue concerned quotations from Hitachi. The court found that the defendant’s decision to omit the parameters within which those quotations were sought was inadequately explained, and that this omission cast substantial doubt on their reliability. The court therefore held that there was insufficient evidence to show that the safeguards in place made the Hitachi quotations reliable and objective. This affected the damages analysis because the court was unwilling to rely on those quotations as a dependable benchmark. (Para 69)

"The Defendant’s inadequately explained decision to leave out the parameters within which the quotations from Hitachi were sought casts substantial doubt on their reliability. I am therefore of the view that there is insufficient evidence to show that there were safeguards in place to ensure the Hitachi quotations were reliable and objective." — Per Dedar Singh Gill J, Para 69

The court’s treatment of the evidence shows a careful distinction between proof of infringement and proof of value. Even where infringement is established, the quantum of damages still depends on reliable evidence of what a lawful licence would have cost or what a reasonable bargain would have looked like. The court was not prepared to accept speculative or inadequately supported quotations as a substitute for that analysis. (Para 69, Para 71)

How did the court calculate damages, and why did it reject the plaintiff’s higher figure?

The court adopted the hypothetical bargain approach to damages. It rejected the plaintiff’s claim for $259,511 and instead assessed damages at $30,574. The court’s task was to determine the cost of the licences that would have been required had the defendant lawfully obtained permission to use the software in the relevant manner. (Para 71)

"I therefore find the appropriate measure of damages to be $30,574 (being the cost of perpetual node-locked licences for the CAD/CAM 3 Axis Milling Foundation and the Wire EDM Add-on without maintenance)" — Per Dedar Singh Gill J, Para 71

The court explained that the relevant licences were perpetual node-locked licences without maintenance. It also noted a 25 per cent downward adjustment from the plaintiff’s price book. That adjustment was part of the court’s effort to identify a realistic and legally appropriate measure of the plaintiff’s loss or the defendant’s gain in the hypothetical lawful world. (Para 71)

The court’s approach was informed by authorities on damages such as General Tire, Stoke-on-Trent, Henderson, and Reformation Publishing. Those cases were used to support the idea that damages in intellectual property cases may be assessed by reference to a reasonable royalty or hypothetical bargain, especially where direct proof of lost sales is difficult. The court therefore did not simply accept the plaintiff’s asserted figure; it tested the evidence against the legal principles governing valuation. (Para 71)

Why did the court refuse additional damages and what relief did it grant instead?

The court declined to award additional damages. It referred to the statutory provision on additional damages and to the purpose of such awards, but it ultimately made no order imposing them. The judgment indicates that the court was not persuaded that the circumstances justified a punitive or deterrent uplift beyond the compensatory damages already assessed. (Para 73, Para 78)

"I also grant a permanent injunction restraining the Defendant from further infringements of the Plaintiff’s copyright subsisting in the NX Software. I make no order imposing additional damages on the Defendant." — Per Dedar Singh Gill J, Para 78

The court did, however, grant a permanent injunction restraining further infringement. That remedy is significant because it shows that even where the infringing conduct had ceased and damages had been quantified, the court still considered prospective relief necessary to protect the plaintiff’s copyright. The injunction therefore complemented the damages award by preventing recurrence. (Para 78)

The court also stated that it would hear parties separately on interest and costs. That meant the judgment resolved liability and principal damages, but left the ancillary financial consequences for later determination. (Para 79)

"I will hear parties on interest and costs separately." — Per Dedar Singh Gill J, Para 79

The court began with s 31(1) of the Copyright Act 1987 (2006 Rev Ed), which it quoted as the starting point for infringement analysis. It also referred to s 119(4) of the Copyright Act in the context of additional damages. These provisions anchored the court’s analysis in the statutory framework governing copyright infringement and remedies. (Para 20, Para 73)

"section 119(4) of the Copyright Act provides that:" — Per Dedar Singh Gill J, Para 73

Beyond the Copyright Act, the court referred to the Evidence Act 1893, including s 32(1)(b)(iii), s 32(3), s 47(1), and s 47(4). Those provisions were relevant to the treatment of evidence, including business records and the admissibility or reliability of certain materials. The court’s reliance on those sections shows that the damages and evidential issues were closely intertwined. (Para 0)

The court also relied on the general law of vicarious liability as articulated in Ng Huat Seng, and on the law of authorisation as discussed in RecordTV and earlier copyright cases. In addition, it drew on comparative authorities from England, Australia, and Canada to support the proposition that vicarious liability can extend to copyright infringement and that damages may be assessed by reference to a hypothetical bargain. (Para 23, Para 35, Para 71)

The court’s reasoning was built on a combination of local and comparative authorities. It referred to MCA Records, Red Star Marine, and RecordTV on attribution and authorisation, and to Ng Huat Seng and Skandinaviska on the structure and policy of vicarious liability. It also cited Roman Catholic Episcopal Corporation of St George’s as part of the policy discussion on risk creation. (Para 23, Para 35, Para 36)

On the copyright side, the court noted that copyright infringement is a statutory tort, citing Rank Film Distributors. It also referred to Al-Hasani, Australasian Performing Right Association v Miles, and Roadshow Films v iiNet as comparative support for the proposition that vicarious liability may be available in copyright cases. Those authorities helped the court situate Singapore law within a broader common-law pattern. (Para 35)

"The CA in RecordTV Pte Ltd v MediaCorp TV Singapore Pte Ltd [2011] 1 SLR 830 at [50] specified four factors which the courts ought to take into account in determining if authorisation liability should be imposed" — Per Dedar Singh Gill J, Para 23

For damages, the court relied on General Tire, Stoke-on-Trent, Henderson, and Reformation Publishing to justify the hypothetical bargain approach. It also referred to Gimpex on evidential reliability and to Wing Joo Loong on the discretionary nature of declaratory relief. The result was a judgment that was doctrinally layered: it combined copyright, tort, evidence, and remedial principles in a single analysis. (Para 69, Para 71, Para 78)

What did the court say about the relationship between employment, risk creation, and liability?

The court’s vicarious liability analysis turned on the idea that the employment relationship created and enhanced the risk of infringement. That is why the court did not require proof that the defendant expressly directed the infringing conduct. Instead, it asked whether the employment setting made the wrongdoing sufficiently connected to the defendant’s enterprise. (Para 35, Para 41)

"For these reasons, I find that there is a sufficient connection between the relationship of employment and Mr Win’s infringing acts." — Per Dedar Singh Gill J, Para 41

This approach is practically important for employers. The judgment shows that lax supervision, poor asset control, and the use of work equipment can all contribute to a finding that the employer should bear responsibility for an employee’s infringement. The court’s reasoning therefore encourages employers to implement meaningful controls over software, devices, and access rights. (Para 6, Para 41)

At the same time, the court’s refusal to impose primary liability preserves a doctrinal distinction. The employer was not treated as the direct infringer merely because the infringement happened at work. Liability arose only after the court found the necessary special relationship and sufficient connection under the vicarious liability framework. (Para 22, Para 36, Para 41)

This case matters because it confirms that vicarious liability can apply to copyright infringement in Singapore. That is a significant development for rights holders, because it expands the range of defendants who may be held responsible when infringement is committed by employees in the course of work-related activity. The court expressly endorsed that doctrinal extension. (Para 35)

"I am satisfied that the doctrine of vicarious liability, as it has developed in our local jurisprudence, may be extended to copyright infringement." — Per Dedar Singh Gill J, Para 35

The case also matters for damages methodology. Where direct royalty evidence is weak or contested, the court may use a hypothetical bargain approach and scrutinise the reliability of quotations and pricing evidence. That has practical implications for both plaintiffs and defendants in software infringement cases, especially where the dispute concerns enterprise licences, node-locked licences, or maintenance components. (Para 69, Para 71)

Finally, the case is a reminder that injunctive relief may still be granted even after infringement has been discovered and stopped. The permanent injunction underscores the court’s willingness to protect copyright prospectively, while the refusal of additional damages shows that punitive relief is not automatic. Together, those remedies reflect a balanced approach to enforcement. (Para 78)

Cases Referred To

Case Name Citation How Used Key Proposition
MCA Records Inc and anor v Charly Records Ltd and ors [2000] EMLR 743 Used on whether acts can be attributed to a principal through agency Agent acts within course of duties may be attributed. (Para 23)
Red Star Marine Consultants Pte Ltd v Personal Representatives of Satwant Kaur d/o Sardara Singh, deceased and anor [2020] 1 SLR 115 Used on attribution through company constitution/general company law Acts may be sanctioned by corporate powers. (Para 23)
Ong Seow Pheng and ors v Lotus Development Corp and anor [1997] 2 SLR(R) 113 Used on meaning of authorisation and later on damages Authorisation means sanctioning, approving, or countenancing; also cited for damages burden. (Para 23, Para 71)
RecordTV Pte Ltd v MediaCorp TV Singapore Pte Ltd [2011] 1 SLR 830 Used for four-factor authorisation test Control, relationship, reasonable steps, knowledge. (Para 23)
Ng Huat Seng v Munib Mohammad Madni [2017] 2 SLR 1074 Used for vicarious liability test Two-step inquiry: special relationship and sufficient connection. (Para 36)
Skandinaviska Enskilda Banken AB (Publ), Singapore Branch v Asia Pacific Breweries (Singapore) Pte Ltd and anor [2011] 3 SLR 540 Used for vicarious liability principles and policy considerations Risk creation, close connection, compensation, deterrence. (Para 35)
Roman Catholic Episcopal Corporation of St George’s v John Doe (a pseudonym) and John Doe (a pseudonym) [2004] 1 SCR 436 Cited within Skandinaviska on policy rationale Risk-creation rationale for vicarious liability. (Para 35)
Rank Film Distributors Ltd v Video Information Centre (a firm) [1982] 1 AC 380 Used to characterise copyright infringement as a statutory tort Copyright infringement is a statutory tort. (Para 35)
Al-Hasani v Nettler and anor [2019] EWHC 640 (Ch) Used as comparative authority on vicarious liability for copyright infringement Potential vicarious liability in copyright claims. (Para 35)
Australasian Performing Right Association Ltd v Miles and ors [1961] 3 FLR 146 Used as comparative authority Suggested vicarious liability for copyright infringement. (Para 35)
Roadshow Films Pty Ltd v iiNet Ltd [2012] HCA 16 Used to show Australian support for vicarious liability in copyright Cited APRA v Miles as support. (Para 35)
General Tire and Rubber Co v Firestone Tyre and Rubber Co Ltd [1975] 1 WLR 819 Used for damages approaches Loss of profit, established royalty, hypothetical bargain. (Para 71)
Stoke-on-Trent City Council v W & J Wass Ltd [1988] 1 WLR 1406 Used for user principle in damages Wrongful use may require reasonable sum. (Para 71)
Henderson v All Around the World Recordings Ltd [2014] EWHC 3087 (IPEC) Used on hypothetical bargain assessment Consider circumstances, bargaining positions, commercial context. (Para 71)
Reformation Publishing Company Ltd v Cruiseco Ltd and anor [2018] EWHC 2761 (Ch) Used on valuing benefit gained by infringer Hypothetical bargain values benefit to infringer. (Para 71)
Gimpex Ltd v Unity Holdings Business Ltd and ors [2015] 2 SLR 686 Used on hearsay exception and exclusion discretion Business records and reliability/justice discretion. (Para 69)
Wing Joo Loong Ginseng Hong (Singapore) Co Pte Ltd v Qinghai Xinyuan Foreign Trade Co Ltd and anor [2009] 2 SLR(R) 814 Used on declaratory relief discretion Declaration is discretionary. (Para 78)
Lotus Development Corp and anor v Ong Seow Pheng and ors [1996] 2 SLR(R) 514 Used on additional damages purpose Punishment and deterrence. (Para 73)

Legislation Referenced

Source Documents

This article analyses [2023] SGHC 50 for legal research and educational purposes. It does not constitute legal advice. Readers should consult the full judgment for the Court's complete reasoning.

Written by Sushant Shukla
1.5×

More in

Legal Wires

Legal Wires

Stay ahead of the legal curve. Get expert analysis and regulatory updates natively delivered to your inbox.

Success! Please check your inbox and click the link to confirm your subscription.