Compubahn, Inc. v. United States

40 Cont. Cas. Fed. 76,804, 33 Fed. Cl. 677, 1995 U.S. Claims LEXIS 141, 1995 WL 429450
CourtUnited States Court of Federal Claims
DecidedJuly 21, 1995
DocketNo. 94-781C
StatusPublished
Cited by26 cases

This text of 40 Cont. Cas. Fed. 76,804 (Compubahn, 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
Compubahn, Inc. v. United States, 40 Cont. Cas. Fed. 76,804, 33 Fed. Cl. 677, 1995 U.S. Claims LEXIS 141, 1995 WL 429450 (uscfc 1995).

Opinion

ORDER

MOODY R. TIDWELL, III, Judge:

This case is before the court on the parties’ cross motions for summary judgment pursuant to RCFC 56. For the reasons set forth below, the court grants defendant’s motion and denies plaintiffs motion.

FACTS

The material facts of this case are not in dispute, and are summarized below. Plaintiff is a disappointed bidder for a Government contract with the Department of Defense.

I. Background

In May 1998, the Advanced Research Project Agency of the Department of Defense (DARPA) published and mailed a solicitation of proposals to over 50,000 small businesses, as part of its Small Business Innovation Research (SBIR) program. The SBIR program represented a portion of the activities of DARPA’s Technology Reinvestment Project (TRP), the name given to a cooperative effort of federal government agencies to implement parts of the Defense Conversion, Reinvestment, and Transition Assistance Act of 1992.1 10 U.S.C. §§ 2511-13, 2522-24 & 2196-97. Over $500 million was appropriated by the Congress to fund projects such as the TRP. Id. DARPA, the Department of Energy, the Department of Commerce, the National Aeronautics and Space Administration (NASA), the National Science Foundation (NSF), and the Department of Transportation collaborated to form the Defense Technology Conversion Committee (DTCC), the administrative body of the joint program solicitation.

The TRP SBIR solicitation covered three phases of potential funding. The DTTC anticipated that it would award approximately 72 Phase I contracts, each with a funding total not to exceed $100,000. Businesses awarded Phase I contracts would become candidates for Phase II funding, not to exceed $375,000 per contract. Likewise, Phase III contracts would be awarded to meritorious Phase II participants. The solicitation further stated that the DTTC was not obligated to make awards under either Phase I, II, or III, and would not be responsible for monies expended by the proposer before award of any contract.

Between May and September 1993, the DTTC received 2,453 proposals from a variety of qualified small businesses. Each proposal was earmarked for one of 28 topic categories. Plaintiff submitted a proposal under the “Software Development Methods, Tools, and Environments” category, numbered TRP 93-003. Plaintiffs proposal was one of 101 proposals submitted under category TRP 93-003.

II. Evaluation of Proposals

The solicitation detailed the method of selection and evaluation criteria for the proposals. Proposals would be evaluated first on their relevance to the chosen topic, and then on the following four criteria:

(1) the soundness and technical merit of the proposed innovative approach and its potential contribution toward topic solution; (2) the potential for commercial (government or private sector) application and the benefits expected to accrue from this commercialization; (3) the adequacy of the proposed effort for the fulfillment of requirements of the research topic; and (4) the qualifications of the proposed principal investigators, supporting staff, and consultants.

The solicitation also stated that were technical evaluations equal in merit, cost to the government would be considered in determining a successful offeror. It warned that technical reviewers would base their conclusions only on information contained in the proposal, and that no assumption could be made that its reviewers would be acquainted with any referenced experiments.

[680]*680III. Plaintiffs Proposal

Between September 1993 and March 1994, the DTTC evaluated plaintiffs proposal. A panel of five evaluators was assigned to judge plaintiffs proposal and those of other competitors under category TRP 93-003. The evaluators included the program director for the Software Engineering Program at the NSF, the chief of the Advanced Processing Branch at the U.S. Army Space and Strategic Defense Command, the manager of the Information Science and Technology Office at the Ballistic Missile Defense Organization, a software engineer at the U.S. Air Force Phillips Laboratory, and an electrical engineer at the Advanced Technology Directorate of the U.S. Army Space and Strategic Defense Command. All five evaluators had previous experiences in evaluating technical SBIR proposals and were chosen by their respective agencies on the request of the DTTC that each agency select only highly qualified personnel to evaluate the proposals submitted under the TRP SBIR.

Each evaluator filled out a written evaluation form for .plaintiffs proposal to be submitted to the TRP SBIR review panel. Each form was one page in length and contained five questions to be used as guidelines for evaluators. A small space was left below each question for evaluators to insert comments. Three evaluators commented below each question on their respective forms, and two gave only sporadic comments. Evaluators could either recommend funding for the proposal, not recommend, or recommend with condition. Of the five evaluation forms submitted, plaintiffs proposal received no outright recommendations to fund. Two evaluators gave conditional recommendations.

Subsequently, plaintiffs proposal and the five evaluations were submitted to TRP SBIR review panel for further discussion and consideration. The review panel made recommendations to its chairman, who in turn made recommendations to the TRP working group. Final recommendations were made by the DARPA Deputy Director for Management, who made decisions consistent with the recommendations of the TRP working group and subsequent DTTC deliberations. Of the 2,453 proposals received, a total of 144 Phase I contracts were awarded. No proposals submitted under category TRP 93-003 were recommended for a Phase I award.

IV. Plaintiffs Claim

After receiving notice from DARPA that its proposal had not been selected for a Phase I contract, plaintiff filed suit in this court seeking damages for breach of implied contract and breach of implied covenant of good faith and fair dealing. Plaintiff also sought declaratory and injunctive relief.

Plaintiff alleged that there existed an implied contract between plaintiff and defendant by virtue of defendant’s solicitation for candidates to submit a proposal for the development of the software process technology and plaintiffs submission of a proposal in reply. Plaintiff alleged that in return for its submission of a proposal, defendant had a duty to employ individuals knowledgeable in the particular software process area to evaluate its proposal, and that defendant breached the implied contract by failing to do so and by arbitrarily and capriciously rejecting plaintiffs proposal. Plaintiff sought damages for loss of future earnings, strategic business damage, expenses in preparing the proposal, and attorney’s fees.

DISCUSSION

I. Summary Judgment

Summary judgment is appropriate only when there is no genuine issue as to any material fact and the moving party is entitled to judgment as a matter of law. RCFC 56(c). RCFC 56 is patterned after Rule 56 of the

Related

Caddell Construction Co., Inc. v. United States
111 Fed. Cl. 49 (Federal Claims, 2013)
One Largo Metro, Llc v. United States
109 Fed. Cl. 39 (Federal Claims, 2013)
Glenn Defense Marine (Asia), PTE Ltd. v. States
105 Fed. Cl. 541 (Federal Claims, 2012)
Metropolitan Van & Storage, Inc. v. United States
92 Fed. Cl. 232 (Federal Claims, 2010)
Academy Facilities Management v. United States
87 Fed. Cl. 441 (Federal Claims, 2009)
Savantage Financial Services, Inc. v. United States
86 Fed. Cl. 700 (Federal Claims, 2009)
Labatt Food Service, Inc. v. United States
84 Fed. Cl. 50 (Federal Claims, 2008)
Career Training Concepts, Inc. v. United States
83 Fed. Cl. 215 (Federal Claims, 2008)
R & D Dynamics Corp. v. United States
80 Fed. Cl. 715 (Federal Claims, 2007)
Chant Engineering Co. v. United States
75 Fed. Cl. 62 (Federal Claims, 2007)
KSD, Inc. v. United States
72 Fed. Cl. 236 (Federal Claims, 2006)
Avtel Services, Inc. v. Unites States
70 Fed. Cl. 173 (Federal Claims, 2005)
CSE Construction Co. v. United States
58 Fed. Cl. 230 (Federal Claims, 2003)
Vantage Associates, Inc. v. United States
59 Fed. Cl. 1 (Federal Claims, 2003)
Halter Marine, Inc. v. United States
56 Fed. Cl. 144 (Federal Claims, 2003)
Maintenance Engineers v. United States
50 Fed. Cl. 399 (Federal Claims, 2001)
Mangi Environmental Group, Inc. v. United States
47 Fed. Cl. 10 (Federal Claims, 2000)
Cube Corp. v. United States
46 Fed. Cl. 368 (Federal Claims, 2000)

Cite This Page — Counsel Stack

Bluebook (online)
40 Cont. Cas. Fed. 76,804, 33 Fed. Cl. 677, 1995 U.S. Claims LEXIS 141, 1995 WL 429450, Counsel Stack Legal Research, https://law.counselstack.com/opinion/compubahn-inc-v-united-states-uscfc-1995.