Wonderworks Pte. v. Hewlett-Packard CA6

CourtCalifornia Court of Appeal
DecidedMay 16, 2016
DocketH042330
StatusUnpublished

This text of Wonderworks Pte. v. Hewlett-Packard CA6 (Wonderworks Pte. v. Hewlett-Packard CA6) is published on Counsel Stack Legal Research, covering California Court of Appeal primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Wonderworks Pte. v. Hewlett-Packard CA6, (Cal. Ct. App. 2016).

Opinion

Filed 5/16/16 Wonderworks Pte. V. Hewlett-Packard CA6 NOT TO BE PUBLISHED IN OFFICIAL REPORTS California Rules of Court, rule 8.1115(a), prohibits courts and parties from citing or relying on opinions not certified for publication or ordered published, except as specified by rule 8.1115(b). This opinion has not been certified for publication or ordered published for purposes of rule 8.1115.

IN THE COURT OF APPEAL OF THE STATE OF CALIFORNIA

SIXTH APPELLATE DISTRICT

WONDERWORKS PTE. LTD., H042330 (Santa Clara County Plaintiff and Appellant, Super. Ct. No. 1-14-CV-273632)

v.

HEWLETT-PACKARD COMPANY, et. al.,

Defendants and Respondents.

In this action against Hewlett-Packard Company and two related entities, the court granted defendants’ motion to stay the action pending its adjudication in Malaysia. Plaintiff WonderWorks appeals, contending that the doctrine of forum non conveniens should not have been applied, as the public and private interests underlying the litigation did not warrant depriving WonderWorks of its chosen forum. We agree that on the particular facts before us, the stay constituted an abuse of discretion and requires reversal. Background The following factual summary is derived from WonderWorks’s first amended complaint, supplemented by declarations and accompanying evidence submitted by the parties. WonderWorks was “incorporated” in Singapore but was wholly owned and managed by Sri Rajan, a California resident. Defendant Hewlett-Packard Company (HP Co.) was a Delaware corporation with its principal place of business in Palo Alto. Defendant Hewlett-Packard Enterprise Services, LLC (HPES) was a wholly owned subsidiary of HP Co. which identified its principal office as being in Texas; according to

1 WonderWorks, however, Palo Alto was the place where HPES employees conducted “significant business . . . with respect to the subject matter of this case.” Like HPES, Hewlett-Packard Malaysia (HPM) was a wholly owned subsidiary of HP Co., incorporated and operating in Malaysia. According to the 2015 complaint, HPES and HPM were agents or, alternatively, alter egos of HP Co., which commingled funds and interchanged employees among the three entities. HP Co. “instructed and controlled” HPES and HPM, using these subsidiaries “as a mere conduit for the affairs of HP Co., including by directing HPES and HPM to carry out the acts alleged in this complaint, for the benefit of HP Co.” The complaint referred to the HP entities collectively as “HP.” In late 2009 or early 2010, HPM sought to procure a contract with Bank Negara Malaysia (BNM), the central bank of Malaysia. According to Bee Wah Lim (Lim), the “Country General Manager” of HPM, “BNM was looking for a company to develop an Integrated Statistical System (‘ISS’) that BNM could use to help manage and monitor the reporting activity and filings made by Malaysian financial institutions and other regulated Malaysian entities.” In April 2011, BNM awarded the contract to HPM. In its complaint WonderWorks alleged that defendants had induced it to join them on a bid for the BNM contract. WonderWorks’s role, it was told, would be to sell its software to thousands of businesses in Malaysia that would be required to use the software in filing its financial reports to BNM. According to the complaint, “The Defendants told Plaintiff that after the system was in place in Malaysia, it would be replicated on the cloud for other customers worldwide. Defendants promised Plaintiff extraordinary profits if it would join this venture.” WonderWorks spent “millions of dollars” in preparation and then “performed admirably. However, Defendants botched the project and in the end did not pay Plaintiff for most of the work they had contracted to Plaintiff. Defendants also coerced Plaintiff to perform work outside the contract for which they did not pay. Ultimately, Defendants abandoned the project due to their own ineptitude and misconduct in order to cut their own losses, which eliminated the promised

2 sales of Plaintiff’s software. Defendants also told Plaintiff that the worldwide cloud replication that had been promised had not actually been a reality.” WonderWorks elaborated on these allegations by identifying HPM as the entity that had represented that WonderWorks would eventually earn “many millions of dollars in profit” once the BNM system was installed; meanwhile, WonderWorks would be “fully paid for all of its work and [its] software.” HPM had also represented to WonderWorks that “HP would partner with WonderWorks on an exclusive basis to replicate the BNM System on a revolutionary cloud-based system” which could be used by “regulators and reporting entities throughout the world.” HP Co., according to the complaint, “was an integral part of the contractual arrangement with WonderWorks.” HPM assured plaintiff that HP Co. was “committed to funding this Cloud System, and that it was on the agenda of the parent company’s highest executives, including CEO Leo Apotheker of HP Co. in Palo Alto, California.” HP Co. and HPES accordingly “approved all material aspects of HPM[‘s] putting together this deal with Plaintiff for the BNM System, and thereafter monitored and/or managed it closely until . . . HP Co. and HPES employees themselves took direct hands-on control of and/or significantly influenced, reviewed, and approved commercial, legal, risk, and technical aspects of the project.” The eventual agreement between HP and WonderWorks contemplated that WonderWorks would provide its software components and services to the BNM system. HP also agreed to pay license fees for WonderWorks software that was later installed on servers at HP and BNM. The two components of the integrated agreement were a Statement of Work (SOW) and a “Global Supply Chain Services – Standard Terms and

3 Conditions for Services and Software” (GSCS).1 By July of 2011 HPM began issuing purchase orders that carried their own conditions as well as being subject to the GSCS. WonderWorks then expended more than $8 million in hiring independent contractor programmers to fulfill its contractual obligations. After HP obtained WonderWorks’s proprietary software specifications and learned how WonderWorks components should be integrated, “HP began to engage in serious misconduct.” Among WonderWorks’s allegations were HP’s (1) intentionally failing to disclose all of the hardware on which WonderWorks’s software had to be installed, resulting in its failure to pay “millions of dollars” in license fees to WonderWorks; (2) failing to pay millions of dollars on invoices submitted by WonderWorks; (3) inducing WonderWorks to continue the work and provide additional licenses while promising to pay the outstanding fees and invoices; (4) forcing WonderWorks to make modifications to components HP had acquired for the BNM system in order to avoid additional fees payable to BNM, even though such modifications were outside the scope of WonderWorks’s contract, by threatening to remove WonderWorks from the BNM system and cloud system projects; (5) blaming WonderWorks for HP’s own misguided decision to use a faulty, end-of-life component, thereby damaging WonderWorks’s reputation and causing its loss of profit; (6) unjustly blaming WonderWorks for HPM’s own failure to deliver the BNM system on time; and (7) imposing economic duress on WonderWorks by canceling payments on already approved invoices. WonderWorks also alleged that HP had led WonderWorks to believe that they would be partners in the worldwide cloud system; yet HP never intended to partner with WonderWorks on the system and failed to fund it. WonderWorks asserted that “HP’s true intent was to obtain [WonderWorks’s] expertise, incorporate WonderWorks software into HP’s offering for the BNM System without properly

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Gulf Oil Corp. v. Gilbert
330 U.S. 501 (Supreme Court, 1947)
Koster v. (American) Lumbermens Mutual Casualty Co.
330 U.S. 518 (Supreme Court, 1947)
Piper Aircraft Co. v. Reyno
454 U.S. 235 (Supreme Court, 1982)
Manu International, S.A. v. Avon Products, Inc.
641 F.2d 62 (Second Circuit, 1981)
Adolf Lony v. E.I. Du Pont De Nemours & Company
886 F.2d 628 (Third Circuit, 1989)
National Football League v. Fireman's Fund Insurance
216 Cal. App. 4th 902 (California Court of Appeal, 2013)
Stangvik v. Shiley Inc.
819 P.2d 14 (California Supreme Court, 1991)
Cal-State Business Products & Services, Inc. v. Ricoh
12 Cal. App. 4th 1666 (California Court of Appeal, 1993)
American Cemwood Corp. v. American Home Assurance Co.
104 Cal. Rptr. 2d 670 (California Court of Appeal, 2001)
Guimei v. General Electric Co.
172 Cal. App. 4th 689 (California Court of Appeal, 2009)
Morris v. AGFA CORP.
51 Cal. Rptr. 3d 301 (California Court of Appeal, 2006)
Campbell v. Parker-Hannifin Corp.
82 Cal. Rptr. 2d 202 (California Court of Appeal, 1999)
Shiley Inc. v. Superior Court
4 Cal. App. 4th 126 (California Court of Appeal, 1992)
Boaz v. Boyle & Co.
40 Cal. App. 4th 700 (California Court of Appeal, 1995)
Investors Equity Life holding Co. v. Schmidt CA4/3
233 Cal. App. 4th 1363 (California Court of Appeal, 2015)
Investors Equity Life Holding Co. v. Schmidt
195 Cal. App. 4th 1519 (California Court of Appeal, 2011)
Ravelo Monegro v. Rosa
211 F.3d 509 (Ninth Circuit, 2000)
Carijano v. Occidental Petroleum Corp.
643 F.3d 1216 (Ninth Circuit, 2011)

Cite This Page — Counsel Stack

Bluebook (online)
Wonderworks Pte. v. Hewlett-Packard CA6, Counsel Stack Legal Research, https://law.counselstack.com/opinion/wonderworks-pte-v-hewlett-packard-ca6-calctapp-2016.