Blackboard Inc. v. International Business Machines Corporation

CourtDistrict Court, S.D. New York
DecidedJune 2, 2022
Docket1:21-cv-07165
StatusUnknown

This text of Blackboard Inc. v. International Business Machines Corporation (Blackboard Inc. v. International Business Machines Corporation) is published on Counsel Stack Legal Research, covering District Court, S.D. New York primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Blackboard Inc. v. International Business Machines Corporation, (S.D.N.Y. 2022).

Opinion

UNITED STATES DISTRICT COURT SOUTHERN DISTRICT OF NEW YORK -- ---------------------------------------------------------- X : BLACKBOARD INC., : Petitioner, : 21 Civ. 7165 (LGS) -against- : : OPINION AND ORDER INTERNATIONAL BUSINESS MACHINES : CORPORATION, : Respondent. : : ------------------------------------------------------------ X

LORNA G. SCHOFIELD, District Judge: This case arises from an arbitration award issued in a dispute between Petitioner Blackboard Inc. and Respondent International Business Machines Corporation. Petitioner moves to vacate or modify in part, and confirm in part, a May 27, 2021, arbitration award (the “Award”) rendered in favor of Respondent. Respondent opposes the motion and moves for attorneys’ fees and costs. For the reasons below, the Petition to vacate or modify the Award is denied, the Award is confirmed and Respondent’s motion for attorneys’ fees and costs is denied. BACKGROUND A. The Agreement The following facts are taken from the sworn declarations of the parties’ counsel and attached exhibits, including the Award, as well as the docket in this case. On June 9, 2016, Petitioner and Respondent executed the Master Professional Services Agreement (the “Agreement”). Under the Agreement, Respondent agreed to: (1) operate and manage Petitioner’s existing data centers (the “legacy” centers); (2) migrate Petitioner’s products from the legacy centers to the cloud environment and (3) manage Petitioner’s new cloud environment. The Agreement also stated that third-party Amazon Web Services (“AWS”) would provide the cloud platform. Schedule D to the contract set forth the pricing terms, and Attachment D.1 to Schedule D set forth the dollar amounts associated with those terms. Under Section 6 of Schedule D,

Petitioner agreed to pay Cloud Hosting Licensing Services Fees to AWS at the AWS commercial price, less a discount. AWS invoiced Respondent for these fees, and Respondent then invoiced Petitioner for the fee amounts. Under the original contract, if Petitioner’s actual monthly AWS fees exceeded the estimates in Attachment D.1, Respondent invoiced Petitioner a “true-up” for the difference. In late April 2017, the parties signed an amendment to the Agreement (“Amendment 15”), which impacted three sections of the Agreement: “Section 5: Management fees,” “Section 6: Cloud hosting and licensing fees (AWS)” and “Section 7.2: Reasonable equivalency clause (REC).” On May 31, 2017, the parties signed a further amendment, replacing Attachment D.1 with Attachment D.1-16. These amendments abandoned the “true-up” process, and

Petitioner instead agreed to pay Respondent for its “actual consumption” in the AWS Cloud at AWS commercial prices, less a discount. Petitioner also agreed to pay Respondent to manage Petitioner’s legacy and cloud environments. The resulting management fees were based on Resource Units and Resource Baselines, which allowed the management fees to be adjusted each month.1 If Petitioner consumed more Resource Units than estimated in the Resource Baseline, Petitioner agreed to pay Additional Resource Charges (“ARCs”). If Petitioner consumed fewer

1 The Agreement defines a Resource Unit as “a measurable device, unit of consumption, staffing level, or other resource defined in Attachment D.l that is associated with the Services and for which distinct volumes are measured and charging rates or other charging mechanisms apply.” (Emphasis in original). Resource Units than estimated, Respondent agreed to give Petitioner Reduced Resource Credits (“RRCs”). Central to the instant dispute is the Agreement’s “Reasonable Equivalency Clause” (“REC”), which provides, in its entirety:

As Virtual Machine Instances and associated Server Storage GBs are migrated from the Blackboard Legacy Data Center environment to a reasonable equivalent architectural configuration from a technology, capacity and performance perspective in the Cloud Provider’s environment, the sum of the RRCs for such Virtual Machine Instances, associated Server Storage GBs and any other applicable Resource Units in Blackboard’s Legacy Data Center environment resulting from such migration shall not be less than the sum of the ARCs for the addition in Cloud Provider’s environment of the reasonably equivalent elements (including any charges for Virtual Machine Instances, associated Server Storage GBs, routers, load balancers, and other network resources, along with usage charges) representing such reasonably equivalent architectural configuration (i.e., at a minimum a net zero change in the Charges). The Parties acknowledge and agree that the additional ARCs and RRCs will apply to additional AWS services selected by Blackboard users (or as Blackboard directs Service Provider). For the avoidance of doubt, the determination of reasonable equivalency must take into account seasonality, since migrations will often occur during the Summer or between academic terms, when volumes are likely to be lower.

(Emphasis added.) B. Post-Contract Dealings In March 2017, the parties started working together to measure technical aspects of equivalency under the Agreement. After Petitioner’s VP of Cloud Services left the company in June 2017, Petitioner’s finance group began leading the equivalency discussions and argued that equivalency should be based on client experience. Respondent disagreed, contending that the REC called for a tripartite test to determine equivalency. In August 2017, Petitioner began withholding reasonable equivalency credits from payments due to Respondent and holding those payments in escrow pending resolution of the dispute. In calculating the amount to be withheld, Petitioner did not conduct the tripartite test under the REC but instead assumed that the legacy and cloud environments were equivalent. Between January 1, 2018, and June 30, 2019, Respondent invoiced Petitioner $89,001,008.79. Petitioner withheld $26,650,148.37 as reasonable equivalency credits -- all consisting of AWS Cloud Hosting Licensing Fees.2

On June 28, 2019, the parties entered into a Settlement Agreement in which the parties agreed to terminate the Agreement effective June 30, 2019. The Settlement Agreement included a provision that the parties would arbitrate their remaining disputes and set forth the arbitration process. On September 27, 2019, Petitioner filed its Demand for Arbitration, seeking $41 million, including the $26,650,148 that Petitioner withheld under the REC, and pre- and post-judgment interest. Respondent counterclaimed for the same $26,650,148 and requested pre- and post- judgment interest. C. The Arbitration and Award The parties presented their case to a panel of three arbitrators (the “Panel”) in March

2021. According to the Award, the proceeding involved “11 bankers’ boxes of exhibits sent to each Panel member; 10 hearing days; 1 oral day of summing-up; and final written briefing from each side.” The Panel heard fifteen live witnesses, watched twelve hours of deposition videos and admitted 278 exhibits into evidence. On May 27, 2021, the Panel issued a unanimous, sixteen-page opinion denying Petitioner’s claims and granting Respondent’s counterclaims. The Award rejected Petitioner’s

2 The Agreement defines the “Cloud Hosting Licensing Services Charges” as “the fixed charges to Blackboard for Service Provider’s hosting of various categories of Virtual Machine Instances, Server Storage GBs and other available items in the public cloud environment operated by Amazon Web Services, a Subcontractor to Service Provider.” Petitioner also withheld $3,143,101 as Service Level Agreement credits, which are not at issue here.

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

Related

West Virginia v. United States
479 U.S. 305 (Supreme Court, 1987)
Hall Street Associates, L. L. C. v. Mattel, Inc.
552 U.S. 576 (Supreme Court, 2008)
Graham v. James
144 F.3d 229 (Second Circuit, 1998)
Oxford Health Plans LLC v. Sutter
133 S. Ct. 2064 (Supreme Court, 2013)
Fellus v. Sterne, Agee & Leach, Inc.
783 F. Supp. 2d 612 (S.D. New York, 2011)
Zurich American Insurnce v. Team Tankers A.S.
811 F.3d 584 (Second Circuit, 2016)
Beijing Shougang Mining v. Mongolia
11 F.4th 144 (Second Circuit, 2021)
Nomura Home Equity Loan, Inc. v. Nomura Credit & Capital, Inc.
92 N.E.3d 743 (Court for the Trial of Impeachments and Correction of Errors, 2017)

Cite This Page — Counsel Stack

Bluebook (online)
Blackboard Inc. v. International Business Machines Corporation, Counsel Stack Legal Research, https://law.counselstack.com/opinion/blackboard-inc-v-international-business-machines-corporation-nysd-2022.