Bearingpoint, Inc. v. United States

77 Fed. Cl. 189, 2007 U.S. Claims LEXIS 129, 2007 WL 1276912
CourtUnited States Court of Federal Claims
DecidedApril 30, 2007
DocketNo. 06-675C
StatusPublished
Cited by22 cases

This text of 77 Fed. Cl. 189 (Bearingpoint, Inc. v. United States) is published on Counsel Stack Legal Research, covering United States Court of Federal Claims primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Bearingpoint, Inc. v. United States, 77 Fed. Cl. 189, 2007 U.S. Claims LEXIS 129, 2007 WL 1276912 (uscfc 2007).

Opinion

OPINION AND ORDER ON MOTION TO DISMISS

WHEELER, Judge.

This ease is before the Court on Plaintiff BearingPoint’s motion to dismiss for lack of subject matter jurisdiction, pursuant to Rule 12(b)(1) of the Rules of the Court of Federal Claims (“RCFC”). In its September 26, 2006 Complaint, BearingPoint requested a timely review under the Contract Disputes Act, 41 U.S.C. § 601 et seq., of two default terminations issued by a Department of Interior (“DOI”) Contracting Officer. BearingPoint now asserts in its motion to dismiss that the DOI lacked authority to issue such termination notices. The case involves Bearing-Point’s Multiple Award Schedule contract with the General Services Administration (“GSA”), and a Blanket Purchase Agreement (“BPA”) and Task Order issued by the DOI. The DOI Contracting Officer purported to terminate the Task Order and the BPA for default on September 29, 2005 and October 27, 2005 respectively. BearingPoint contends that, under the applicable contract provisions, only the GSA Contracting Officer had authority to issue default terminations where BearingPoint alleged excusable delay as a defense.

Defendant asserts that an amendment to the Federal Acquisition Regulations (“FAR”), enacted after the award of the BPA but before the award of the Task Order, authorized the DOI Contracting Officer to terminate these agreements. Defendant argues that a contracting officer’s authority to bind the Government is determined by stat[190]*190ute, regulation, and internal agency procedure, not by contract provisions.

The question presented is whether a FAR amendment effective after a government contract is executed should nonetheless govern the contract, and take precedence over a conflicting contract provision. The competing terms are in FAR §§ 8.406-4 and 8.406-6,1 and in Federal Supply Schedule clause I-FSS-249-B, “Default.” If the FAR amendment governs, then the DOI Contracting Officer was authorized to issue the default terminations. If the contract provision governs, only the GSA Contracting Officer could issue the default terminations.

For the reasons explained below, the Court concludes that it does not have jurisdiction over this matter. The contract language in BearingPoint’s Schedule Contract granted exclusive authority to the GSA Contracting Officer to issue a default termination where the contractor alleged excusable delay as a defense. This language also governed the administration of the BPA and the Task Order. The GSA could have incorporated the FAR amendment into the Schedule Contract as a modification, but it did not. Instead, the GSA reaffirmed the application of its standard clause, I-FSS-249-B, after the FAR amendment had been issued. The Complaint therefore is dismissed without prejudice, and the DOI default terminations are to be treated as a legal nullity.

Factual Background 2

On January 29, 2003, Plaintiff, Bearing-Point, Inc., entered into Multiple Award Schedule (“MAS” or “Schedule”) Contract No. GS-35F-4338D with the GSA. Through this “Schedule 70” contract, BearingPoint provides information technology and system integration services to federal agencies. On August 7, 2003, the DOI issued Request for Quotations No. 73873 to holders of GSA Schedule 70 contracts. (Deft’s Exh. A). This solicitation sought technical proposals to implement the DOI’s Financial and Business Management System (“FBMS”) Project. The FBMS is a multi-phased, department-wide information technology system intended to replace older, disparate software systems. The new system will provide a platform for DOI business functions such as travel, accounting, procurement, and personnel management. The solicitation informed offerors that DOI intended to award a single BPA to the offeror that submitted the best value proposal conforming to the solicitation requirements.

The DOI determined BearingPoint’s proposal to be the best value, and on January 5, 2004, awarded BPA No. 73873 to Bearing-Point under the MAS Contract. (Pltfs Exh. A). The DOI estimated that the value of the purchases through the BPA would total $20 million between the date of award and September 2013. Id. at 2. The BPA, and all task orders placed under it, incorporated the terms and conditions of the MAS Contract, including Modification No. 6 thereto, dated January 29, 2003. (Pltfs Exh. B, HH 4.6.1, 4.6.7).

As contemplated by the BPA, the DOI began awarding task orders to BearingPoint. On September 20, 2004, the DOI awarded Task Order 3 (Order No. 0404D037408) to BearingPoint in accordance with the terms and conditions of the BPA and the MAS Contract. (Pltfs Exh. C). Task Order 3 required BearingPoint to implement certain functions of the FBMS in three offices of the DOI—the Minerals Management Service, the Office of Surface Mining, Reclamation, and Enforcement, and the Bureau of Land Management.

In the Spring of 2005, BearingPoint began to fall behind schedule in the performance of Task Order 3. A dispute developed between the parties regarding the responsibility for the delays. On August 23, 2005, the DOI’s Contracting Officer, Ms. Aprell Joyce, issued a Cure Notice to BearingPoint regarding [191]*191Task Order 3. (Deft’s Response at 5). Ms. Joyce sent a copy of the Cure Notice to the GSA’s Contracting Officer, Ms. Jacqulin Draughn. Id. With the DOI threatening to terminate Task Order 3 and the BPA for cause, BearingPoint alleged that the performance delays were excusable because they were caused by DOI. (Deft’s Exh. I). Bear-ingPoint notified the DOI that the dispute should be referred to and resolved by the GSA Contracting Officer, and that the DOI Contracting Officer lacked authority to issue a default termination where the contractor alleged excusable delay. Id.

On September 9, 2005, Ms. Joyce sent an e-mail message to Ms. Draughn, in which she stated:

I was hoping to hear from you or GSA attorney today regarding the clause in Schedule 70 contract I-FSS-249-B (Default).
I understand that you are researching this and attempting to contact the attorney, but in addition to the questions that I have previously asked, I would like to add the following:
Is it possible for you as the Contracting Officer or GSA to delegate the authority of making the determination on whether the failure is excusable? [Can you please get] back to me? I can submit the request via a formal letter if needed.
Thank you and I look forward to talking with you soon.

(Deft’s Exh. F). On September 12, 2005, Ms. Draughn responded by e-mail message to Ms. Joyce, stating as follows:

Generally, when a dispute arises that relates solely to the task order (i.e., does not impact the schedule contract), the contracting officer responsible for issuing a final decision is the task order CO. If, however, there is a dispute that goes to the terms and conditions of the schedule contract, the matter must be referred to the schedule contracting officer for resolution. Late delivery seems like a performance issue, a matter for resolution at the task order level. Also, note that FAR 8.406-4 governs terminations for cause under the schedules program. Although it requires compliance with FAR 12.403, it is important to start with and follow the 8.4 procedures.

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

Related

Melson v. United States
Federal Claims, 2017
Call Henry, Inc. v. United States
855 F.3d 1348 (Federal Circuit, 2017)
Bondyopadhyay v. United States
Federal Claims, 2015
Delaware Cornerstone Builders, Inc. v. United States
117 Fed. Cl. 539 (Federal Claims, 2014)
K-Con Building Systems, Inc. v. United States
114 Fed. Cl. 722 (Federal Claims, 2014)
Kenney v. United States
Federal Claims, 2014
Davita, Inc. v. United States
110 Fed. Cl. 71 (Federal Claims, 2013)
Sharp Electronics Corporation v. Army
707 F.3d 1367 (Federal Circuit, 2013)
Stephen J. Rogers v. United States
109 Fed. Cl. 280 (Federal Claims, 2013)
AAA Pharmacy, Inc. v. United States
108 Fed. Cl. 321 (Federal Claims, 2012)
Stuart v. United States
100 Fed. Cl. 74 (Federal Claims, 2011)
Rogers v. United States
95 Fed. Cl. 513 (Federal Claims, 2010)
120 Delaware Avenue, LLC v. United States
95 Fed. Cl. 627 (Federal Claims, 2010)
De Maio v. United States
93 Fed. Cl. 205 (Federal Claims, 2010)
Brown v. United States
89 Fed. Cl. 145 (Federal Claims, 2009)
Watson v. United States
86 Fed. Cl. 399 (Federal Claims, 2009)
Hyde v. United States
85 Fed. Cl. 354 (Federal Claims, 2008)
Bearingpoint, Inc. v. United States
82 Fed. Cl. 181 (Federal Claims, 2008)

Cite This Page — Counsel Stack

Bluebook (online)
77 Fed. Cl. 189, 2007 U.S. Claims LEXIS 129, 2007 WL 1276912, Counsel Stack Legal Research, https://law.counselstack.com/opinion/bearingpoint-inc-v-united-states-uscfc-2007.