Background
ReductoNox and Siemens Energy worked on a first-of-its-kind project integrating a new generation of turbine with an E-C Power Oxidizer. Their commercial and manufacturing license agreement required turbines “suitable for connection” to the oxidizer, but did not define suitable. The project remained developmental, required substantial integration work, and carried a recognized risk of failure.
After the venture failed, ReductoNox pursued contract, fraudulent-inducement, and damages claims in arbitration. The panel issued a detailed award rejecting those claims. ReductoNox petitioned to vacate for manifest disregard of law; Siemens moved to dismiss, and Supreme Court treated that request as one to confirm the award.
The Court’s Holding
The First Department affirmed. Manifest disregard requires clear and convincing proof that arbitrators knew of a governing legal rule, understood that it controlled, and deliberately refused to apply it. It is not an invitation for a court to reinterpret the agreement or reweigh evidence.
The arbitrators acted within their authority by interpreting “suitable” in light of the developmental context. Their findings that problems existed with both technologies, that integration presented independent challenges, and that ReductoNox failed to prove turbine causation were binding. The fraud ruling likewise rested on insufficient proof of who said what, when, and where, as well as a lack of diligence; even a debatable characterization as puffery was not obvious legal defiance.
The panel had cited and applied the reasonably-certain damages standard but found the claimed expenditures inadequately proved. ReductoNox could not shift its proof burden by invoking uncertainty allegedly created by Siemens. Finally, CPLR 7511(e) mandates confirmation when a vacatur or modification request is denied, so a separate cross-petition was unnecessary.
Key Takeaways
- Manifest disregard does not permit judicial correction of arguable contract or factual errors.
- Parties to emerging-technology agreements should define performance benchmarks, integration responsibility, and acceptance testing precisely.
- Denial of vacatur ordinarily leads automatically to confirmation under CPLR 7511(e).
Why It Matters
The decision reinforces New York’s arbitration finality for technology and commercial disputes. A lengthy, reasoned award can be difficult to dislodge when it identifies the correct standards and ties findings to the record.
Counsel should litigate causation, reliance, and damages fully before the arbitrators because judicial review will not provide a second merits hearing. Transactional teams can reduce later uncertainty by translating developmental expectations into objective milestones and allocating the risk that combined systems fail to integrate.
The decision also illustrates the difference between legal error and manifest disregard. An arbitrator may choose among plausible readings, make credibility findings, reject expert calculations, or even commit an ordinary mistake without authorizing vacatur. The demanding standard protects the finality the parties purchased when they chose arbitration. A challenger needs a clearly applicable rule, proof the panel knew it, and an award showing intentional refusal—not simply an unfavorable result.
For research-and-development ventures, the underlying dispute offers a transactional lesson. Terms such as suitable, functional, commercially reasonable, and compatible can conceal different technical expectations. Agreements should specify interface specifications, test protocols, acceptance authority, cure stages, data ownership, cost responsibility, and consequences if both systems contribute to failure. Those provisions make the arbitration record more objective and reduce dependence on retrospective expert narratives.