Client Network Services, Inc. v. United States

64 Fed. Cl. 784, 2005 U.S. Claims LEXIS 92, 2005 WL 834638
CourtUnited States Court of Federal Claims
DecidedApril 6, 2005
DocketNo. 05-377C
StatusPublished
Cited by7 cases

This text of 64 Fed. Cl. 784 (Client Network Services, 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
Client Network Services, Inc. v. United States, 64 Fed. Cl. 784, 2005 U.S. Claims LEXIS 92, 2005 WL 834638 (uscfc 2005).

Opinion

OPINION

SMITH, Senior Judge.

INTRODUCTION

This case pits the needs of any administrative system against an apparent unfair loss of a contract. Plaintiff was awarded a contract by the Department of Energy (DOE) as qualified under Small Business Administration (SBA) rules. A disappointed bidder filed a challenge with the SBA that Plaintiff did not meet the small business criteria of the agency and its regulations. SBA initially determined that indeed Plaintiff did not meet that criteria and DOE withdrew the contract from Plaintiff, eventually awarding it to the challenger, who is the Intervenor here. Three days after the contract was re-awarded, but before contract performance began, the appellate level of SBA (OHA) overturned the determination that Plaintiff was not a small business and remanded to the initial SBA decision-maker. If this appellate rever[786]*786sal had occurred before DOE re-awarded, the CO would have reinstated the contract to Plaintiff. However, the 3 day gap made his decision discretionary under SBA regulations. DOE regulations say nothing on this point. The CO, in any event, refused to exercise his discretion to reinstate the contract to the original awardee (Plaintiff here).

Several things are apparent here. First, there is a presumption that the original award was in the best interest of the Government at the time it was accepted. Second, Congress fully contemplated the potential for this type of dispute when it inserted the SBA into the procurement process. Third, the Government has a legitimate interest in administrative certainty when awarding contracts. Fourth, the Court, and historically other fora, have been given jurisdiction over this type of case in order to ensure fairness to the individual bidder, the integrity of the procurement process, and that the Government makes the best procurement decisions for the tax payer. These interests clash in this case.

If the initial SBA size determination was wrong, then Plaintiff has lost a valuable contract by reason of a Government misjudgment. The taxpayer has also been denied the best deal. However, this problem is inherent where the SBA has a role in government procurement. Of course, Congress found this role to be based on an important national concern; fostering small business. The Court is thus faced with 3 questions it must answer. First, does it have subject matter jurisdiction? Second, does the complaint state a cause upon which this Court has the power to grant relief? And third, did the CO abuse his discretion when he refused to re-award the contract to Plaintiff? The Court believes the first 2 questions should be answered in the affirmative. This means the 12(b)(1) and (6) motions must be DENIED.

The third question is the hardest to answer because the mandates from Congress clash. In order to find that the CO abused his discretion the court must determine that the CO either acted in bad faith (for which there appears to be no evidence) or that his action is so inconsistent with DOE’s actual need for certainty that it can not be justified in light of Plaintiffs small business status at the time of the OHA reversal. This is a tough standard to meet. The Court has not heard specific argument on this point, however, it has some preliminary views that may help the parties. So far, the description of the CO’s decision does sound reasonable. The DOE in this case is faced with a real need for computer services. Reissuing the contract to Plaintiff would add an additional level of uncertainty to the process. If the contract was returned to Plaintiff and the ongoing OHA remand ultimately finds that CNSI was not an 8(a) small business, then DOE would yet again have to terminate the contract with Plaintiff, and presumably the Intervenor would again be given the contract a second time. Thus, after one award and three re-awards the Government would only then get its IT network. The systemic interest in preventing this seems strong indeed.

This would be a harsh result to CNSI if indeed they ultimately prevail in their SBA classification. However, justice is not a free good, as the economists say. In this case it takes time and imposes costs. Unfortunately there is no way to instantly determine the “correct” answer to the SBA dispute. In fact there may be no “correct” answer, just a matter of conflicting regulatory determinations. In light of this situation, the Court is inclined to deny Plaintiff relief on the merits. However, Plaintiff and Defendants should be given an opportunity to focus on this specific issue. The Court is open to their arguments or evidence.

After full briefing and oral arguments, the Court DENIES Defendant’s 12(b)(1) Motion to Dismiss for Lack of Subject Matter Jurisdiction and DENIES Defendant-Intervenor’s 12(b)(1), or alternatively 12(b)(6) Motion to Dismiss.

FACTUAL BACKGROUND

Client Network Services, Inc. (CNSI) is an information technology company, which is a participant in the Small Business Administration’s 8(a) Business Development Program, for purposes of federal government contract set-asides. Complaint ¶14. When its Yucca Mountain Project Office of Civilian Radioactive Waste Management needed new [787]*787computer network services, the Department of Energy (DOE) solicited a handful of such small businesses through a Request for Quotations (RFQ)1. The August 6, 2004 RFQ echoed regulatory competition criteria, that DOE would award the contract to the “responsible offeror” whose conforming offer would be “most advantageous” to the Government from among the participating vendors. Pl. Appendix Tab 1, pg. 65. It also contemplated written submission of a 30 day phase-in plan, detailing and ensuring smooth transition from the then existing IT team. Complaint ¶ 11. The solicited vendors had under three weeks to submit them responsive offers, with bids due August 24, 2004. Complaint ¶6. After a month’s deliberation, on September 24, 2004 DOE notified the vendors that it had selected CNSI for contract DE-RQ28-04RW1297.

PROCEDURAL HISTORY

Within a week of DOE’s award to CNSI, disappointed bidder Catapult challenged CNSI’s size eligibility with the SBA, arguing the North American Industry Classification System (NAICS) schedule applied. Complaint ¶16. On October 28, 2004, the SBA Philadelphia Area Director concluded that CNSI was other than a small business concern under that standard. Complaint 1123. Seven days later, on November 4, 2004 CNSI exercised its administrative right to appeal that adverse size determination, filing with the OHA. Id. Now operating under the Area Office ruling, on November 8, 2004 DOE terminated it’s award of the Yucca Mountain IT contract with CNSI. While the OHA was considering CNSI’s appeal, DOE then re-awarded the contract to Catapult on February 8, 2005. Three days later, OHA issued its order of remand, vacating the Area Office’s October size determination. Complaint ¶25. After discovering that DOE would stand by its re-award to Catapult even in light of the OHA remand, CNSI lodged a protest first with the agency, and then with GAO on February 17, 2005. Complaint ¶ 27. On March 3, 2005 GAO dismissed CNSI’s protest, finding that DOE had discretion not to abide by an after-award OHA decision correcting an SBA size ruling. Complaint ¶28. On March 18, 2005 Plaintiff CNSI filed in this Court asking us to declare DOE’s decision not to reinstate CNSI as successful bidder as arbitrary and capricious, and to permanently enjoin the Government from performance of the task order under the RFQ awarded to Catapult on February 8, 2005.

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

Related

Mvs USA, Inc. v. United States
111 Fed. Cl. 639 (Federal Claims, 2013)
Castle-Rose, Inc. v. United States
99 Fed. Cl. 517 (Federal Claims, 2011)
Microdyne Outsourcing, Inc. v. United States
72 Fed. Cl. 230 (Federal Claims, 2006)
Acceptance Insurance Companies, Inc. v. United States
72 Fed. Cl. 299 (Federal Claims, 2006)
Chapman Law Firm Co. v. United States
71 Fed. Cl. 124 (Federal Claims, 2006)
Night Vision Corp. v. United States
68 Fed. Cl. 368 (Federal Claims, 2005)

Cite This Page — Counsel Stack

Bluebook (online)
64 Fed. Cl. 784, 2005 U.S. Claims LEXIS 92, 2005 WL 834638, Counsel Stack Legal Research, https://law.counselstack.com/opinion/client-network-services-inc-v-united-states-uscfc-2005.