Muskegon Central Dispatch 911 v. Tiburon, Inc.

652 F. Supp. 2d 862, 2009 U.S. Dist. LEXIS 76252, 2009 WL 2741041
CourtDistrict Court, W.D. Michigan
DecidedAugust 26, 2009
DocketCase 1:08-CV-550
StatusPublished
Cited by1 cases

This text of 652 F. Supp. 2d 862 (Muskegon Central Dispatch 911 v. Tiburon, Inc.) is published on Counsel Stack Legal Research, covering District Court, W.D. Michigan primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Muskegon Central Dispatch 911 v. Tiburon, Inc., 652 F. Supp. 2d 862, 2009 U.S. Dist. LEXIS 76252, 2009 WL 2741041 (W.D. Mich. 2009).

Opinion

OPINION

ROBERT J. JONKER, District Judge.

This case arises out of an arbitration decision in a software contract dispute. In the underlying arbitration, Muskegon Central Dispatch 911 (“MCD”) 1 claimed that Tiburón, Inc. (“Tiburón”) had materially breached a System Implementation Agreement (“SIA”) between the parties, and MCD sought damages for the alleged *864 breach. Tiburón denied that it had breached the SIA. Instead, Tiburón asserted that MCD had terminated the SIA without cause, and claimed damages under a provision of the SIA governing termination for convenience. The Arbitrator decided the dispute in favor of Tiburón based on his conclusion that MCD failed to follow the contract’s dispute resolution procedure. The Arbitrator never reached the merits of the parties’ substantive disputes, but he denied all MCD’s claims for damages, and awarded against MCD essentially all the damages Tiburón requested. Through cross-motions, MCD now seeks vacatur of the Arbitrator’s decision, while Tiburón seeks confirmation of the Arbitrator’s decision. (See docket # 27, 35.)

Background

1. The parties enter into the System Implementation Agreement.

On December 30, 2003, MCD and Tiburón entered into the SIA, under which Tiburón was to create and implement for MCD an integrated automated public safety system that would include, among other things, a computer-aided emergency dispatch system, police and other records management systems, and connection to the Law Enforcement Information Network. (Br. in Supp. of Mot. to Vacate Arbitration Award, docket # 36, at 3.) The SIA includes a detailed, multi-step process for the informal resolution of disputes between the parties (the “DRP”), providing as follows:

12. Informal Dispute Resolution
12.1. The parties to this Agreement shall exercise their best efforts to negotiate and settle promptly any dispute that may arise with respect to this Agreement in accordance with the provisions set forth in this Section 12.1.
(a) If either party (the “Disputing Party”) disputes any provision of this Agreement, or the interpretation thereof, or any conduct by the other party under this Agreement, that party shall bring the matter to the attention of the other party at the earliest possible time in order to resolve such dispute.
(b) If such dispute is not resolved by the employees responsible for the subject matter of the dispute within ten (10) business days, the Disputing Party shall deliver to the first level of representatives below a written statement (a “Dispute Notice”) describing the dispute in detail, including any time commitment and any fees or other costs involved.
(c) Receipt by the first level of representatives of a Dispute Notice shall commence a time period within which the respective representatives must exercise their best effort to resolve the dispute. If the respective representatives cannot resolve the dispute within the given time period, the dispute shall be escalated to the next higher level of representatives in the sequence as set forth below.
(d) If the parties are unable to resolve the dispute in connection with the escalation procedures set forth below, the parties may assert their rights under this Agreement.
Escalation Timetable Business Days
Tiburón Representative
Client Representative
0 to 5th
Project Manager
Project Manager
6th to 10th
Operations Manager
COPS Coordinating Committee Chair
11th to 15th
Executive Officer
Chairman of COPS Board

(Id., Ex. 4, SIA, at § 12.)

The SIA provides two means of terminating the contract, one for cause, the other without cause. (Id. at §§ 13.1, 13.2.) *865 Section 13. 1, concerning termination for cause, provides:

Subject to completion of the dispute resolution procedure set forth in Section 12.1 hereof, in the event that either party hereto materially defaults in the performance of any of its obligations hereunder, the other party may, at its option, terminate this Agreement by providing the defaulting party thirty (30) days’ prior written notice of termination.

Section 13.2, concerning termination without cause, provides that “[t]he Client may terminate this Agreement without cause by providing Tiburón at least thirty (30) days’ prior written notice of termination delivered in accordance with Section 33 hereof.” Section 13.2 details consequences of termination. Among other things, it provides that if MCD terminates the SIA without cause, MCD must pay Tiburón “for all outstanding invoices submitted ... prior to the effective date of the termination and for all costs and expenses incurred prior to the effective date of the termination.” (Id. at § 13.2.) Nothing in Section 13 of the SIA treats these termination provisions as exclusive remedies. Indeed, the parties’ own agreement acknowledges this. (See id. at § 13.5.)

2. Conflicts arise between the parties and elude resolution.

According to MCD, delays and other performance problems arose soon after Tiburón started work on the project and worsened over the course of approximately two and a half years. (Br. in Supp. of Mot. to Vacate Arbitration Award, docket # 36, at 6-18.) MCD states that Tiburón postponed the implementation dates of key system features multiple times without MCD’s consent and that Tiburón was unable to deliver several fundamental system functions it had agreed to provide. (Id. at 7-10, 14-17.) MCD contacted Tiburón repeatedly to express concern about project delays, turnover among project managers, a perceived lack of responsiveness, and unavailable system functions. (Id. at Exs. 9, 10, 11, 14, 16, 29.) In correspondence with MCD via electronic mail dated August 18, 2005, the Tiburón project manager then in charge of the project acknowledged that “the progress of the implementation has been very slow if any,” and stated that “the resources will be allocated to getting [the MCD project] back on track and bring [sic] closure to the [SIA] and new system.” (Id. at Ex. 9.) However, MCD asserts, the situation did not improve. Indeed, in an internal electronic mail dated August 4, 2006, a Tiburón project manager newly assigned to the MCD project outlined a series of MCD’s concerns and stated, “[i]n reviewing the contract [with MCD], we are clearly in material default.” (Id. at Ex. 32.)

On August 25, 2006, MCD through counsel notified Tiburón that it was terminating the SIA for cause. (Id. at Ex.

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

Related

Muskegon Central Dispatch 911 v. Tiburon, Inc.
462 F. App'x 517 (Sixth Circuit, 2012)

Cite This Page — Counsel Stack

Bluebook (online)
652 F. Supp. 2d 862, 2009 U.S. Dist. LEXIS 76252, 2009 WL 2741041, Counsel Stack Legal Research, https://law.counselstack.com/opinion/muskegon-central-dispatch-911-v-tiburon-inc-miwd-2009.