Continental Business Enterprises, Inc. v. United States

452 F.2d 1016, 196 Ct. Cl. 627, 1971 U.S. Ct. Cl. LEXIS 25
CourtUnited States Court of Claims
DecidedDecember 10, 1971
DocketNo. 160-69
StatusPublished
Cited by58 cases

This text of 452 F.2d 1016 (Continental Business Enterprises, Inc. v. United States) is published on Counsel Stack Legal Research, covering United States Court of Claims primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Continental Business Enterprises, Inc. v. United States, 452 F.2d 1016, 196 Ct. Cl. 627, 1971 U.S. Ct. Cl. LEXIS 25 (cc 1971).

Opinion

Cowen, Chief Judge,

delivered the opinion of the court: This case comes before the court on defendant’s motion for summary judgment. Plaintiff, Continental Business Enterprises, Inc. (CBE), is seeking to recover the amount it expended in preparing a procurement proposal which it contends was not fairly and honestly considered. We must determine whether there are factual disputes which raise a sufficient inference of arbitrary and capricious action by the [630]*630Government to warrant a trial on the merits. Keco Indus., Inc. v. United States, 192 Ct. Cl. 773, 428 F. 2d 1233 (1970). We have concluded, on the basis of the record before us, that the defendant is not entitled to summary judgment and that the case should be remanded to the trial commissioner.

On February 21, 1968, the Department of the Air Force issued an advance synopsis of its plan to procure a weighing scales system for the Air Force Flight Test Center at Edwards Air Force Base, California. The system was to be used to measure and record the weight supported by the main landing gear of the C-5 A aircraft. A formal Request for Proposals was subsequently issued on March 22, 1968.

The contract contemplated that the successful proposer would design the system as well as fabricate and install it. For that reason, the Government employed performance rather than design specifications. The Request for Proposals also included general provisions applicable to fixed-price research and development contracts. This combination resulted in numerous questions from prospective proposers, and on April 19, 1968, the Government held a pre-proposal conference to discuss the technical aspects of the system. Thirteen firms attended, including OBE. Each paragraph of the specifications was discussed in detail, and no change was made in the specifications, because all technical questions were answered.

The RFP provided that each proposal would first be evaluated on the basis of its technical sufficiency, without regard to price. If a proposal was found to be technically unacceptable, the Government reserved the right to reject it without further discussion. Paragraph nine of the RFP provided:

You are cautioned to carefully review all items, conditions and specifications of this Request for Proposals prior to submission of your proposal. Your proposal should be complete in all details, since evaluation of the proposal will determine whether further consideration will be given to it and whether negotiations will be conducted with you prior to making an award. At his option, the Contracting Officer may consider your original proposal ¡as final without extending the privilege of revising the quotation or conducting any negotiations with any offeror. The term “negotiation” does not imply that [631]*631an opportunity automatically exists to submit revisions to your original proposal at will, nor does it imply that the submission of such revisions on a unilateral basis will be considered in the Air Force evaluation process.

Seven proposals were submitted. Each was evaluated by a team of Air Force engineers, which determined that only the proposal of Railweight, Inc., was technically acceptable. The evaluation team rejected CBE’s proposal because it displayed “a poor engineering approach,” which the evaluators described as follows:

The CBE proposal does not show an acceptable approach to the problem of safety as presented in paragraph 6.4.1 and 6.4.2 on page CBE-12. This is totally unsatisfactory from a safety standpoint since the requirements clearly state that the readout console will be located beneath the fuel laden wing of the C-5A, and that a static discharge could cause an explosion when in a fuel-air environment. The CBE proposal does not give any consideration for temperature stabilization of the electronics equipment and does not shown [sic] how the performance criteria of TR 7.1, 7.2, and 7.3 will be met when the weighing system is subjected to the environmental conditions given in TR 6.3.1 and TR 6.3.2. The CBE qualification test plan as required by Special Instructions 3-0 is unacceptable because it offers the Air Force no assurance that the electronics equipment can operate safely prior to delivery to the AFFTC.1

In accordance with the conclusions of the evaluation team, the contracting officer on May 21, 1968, issued notices of unacceptable proposals to the six rejected firms. Apparently before receipt of this notice, CBE’s representatives went to Edwards Air Force Base on their own initiative for the express purpose of negotiating a contract for the weighing scales system. Upon their arrival, the contracting officer informed them that the CBE proposal had been rejected and that no negotiations were contemplated. However, he decided 'to have the project engineer explain the reasons for the unacceptability of the proposal. In meetings held May 22 and 23, 1968, the contracting officer and the project engineer gave the representatives of CBE a detailed explanation as to why the proposal was considered unacceptable.

[632]*632The contracting officer notified CBE on May 24, 1968, that he was reaffirming his decision to reject its proposal. CBE immediately announced its intention to protest the award, and a formal protest was filed on May 28. Pending resolution of the protest by the General Accounting Office, the contracting officer postponed awarding the contract to Kailweight. However, in August, he informed GAO that he could not further postpone the award because any additional delay would prejudice the entire C-5A program. He subsequently awarded the contract to Railweight on August 21, 1968, at a negotiated price of $205,400.

The protests filed by CBE and two other bidders were considered by the Staff Judge Advocate of the Department of the Air Force. In an opinion of July 1, 1968, he recommended that headquarters technical personnel review the unsuccessful proposals and give an opinion as to whether any of such proposals was so technically inferior as to preclude further negotiations. His opinion stated in part as follows:

3. In the recent IBM case (47 Comp. Gen. 29), the Comptroller General said, “When the application of a mandatory benchmark test requirement results ... in leaving one proposer, and its price is, initially at least, substantially in excess of the price of another proposer we believe the spirit and intent of 10 U.S.C. 2304(g) would not be served without further discussion to determine whether the other proposal can be improved to meet the benchmark requirement.” The facts of the instant case bear striking similarities to the IBM case. In both cases, several contractors submitted proposals, but only one was found to be technically acceptable. Also, in both cases, there was a very considerable difference in price between the sole acceptable proposal (high) and non-acceptable proposals. It is also noteworthy that the technical evaluations in the file, although appearing to be very thorough, nevertheless frequently reach adverse conclusions predicated merely on the failure of the proposers to furnish certain information, and this, on occasion at least, despite the fact that there was no express requirement in the RFP for same. [Pl. Ex. 1]

Such a review was made and the Comptroller was advised that the CBE proposal failed to provide “for temperature [633]

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

Related

Synergy Solutions, Inc. v. United States
133 Fed. Cl. 716 (Federal Claims, 2017)
Securiforce International America, LLC v. United States
125 Fed. Cl. 749 (Federal Claims, 2016)
Tigerswan, Inc. v. United States
118 Fed. Cl. 447 (Federal Claims, 2014)
Clinicomp International, Inc. v. United States
117 Fed. Cl. 722 (Federal Claims, 2014)
Omniplex World Services Corp. v. United States
105 Fed. Cl. 706 (Federal Claims, 2012)
Westech International, Inc. v. United States
79 Fed. Cl. 272 (Federal Claims, 2007)
Beta Analytics International, Inc. v. United States
67 Fed. Cl. 384 (Federal Claims, 2005)
Morganti National, Inc. v. United States
49 Fed. Cl. 110 (Federal Claims, 2001)
Labat-Anderson, Inc. v. United States
42 Fed. Cl. 806 (Federal Claims, 1999)
Hydro Engineering, Inc. v. United States
41 Cont. Cas. Fed. 77,135 (Federal Claims, 1997)
E.W. Bliss Co. v. United States
40 Cont. Cas. Fed. 76,769 (Federal Claims, 1995)
Finley v. United States
39 Cont. Cas. Fed. 76,688 (Federal Claims, 1994)
Mega Construction Co. v. United States
39 Cont. Cas. Fed. 76,564 (Federal Claims, 1993)
Grumman Data Systems Corp. v. United States
39 Cont. Cas. Fed. 76,550 (Federal Claims, 1993)
Tonya, Inc. v. United States
39 Cont. Cas. Fed. 76,544 (Federal Claims, 1993)

Cite This Page — Counsel Stack

Bluebook (online)
452 F.2d 1016, 196 Ct. Cl. 627, 1971 U.S. Ct. Cl. LEXIS 25, Counsel Stack Legal Research, https://law.counselstack.com/opinion/continental-business-enterprises-inc-v-united-states-cc-1971.