Oak Grove Technologies, LLC v. United States

116 F.4th 1364
CourtCourt of Appeals for the Federal Circuit
DecidedSeptember 11, 2024
Docket22-1556
StatusPublished
Cited by18 cases

This text of 116 F.4th 1364 (Oak Grove Technologies, LLC v. United States) is published on Counsel Stack Legal Research, covering Court of Appeals for the Federal Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Oak Grove Technologies, LLC v. United States, 116 F.4th 1364 (Fed. Cir. 2024).

Opinion

Case: 22-1556 Document: 114 Page: 1 Filed: 09/11/2024

United States Court of Appeals for the Federal Circuit ______________________

OAK GROVE TECHNOLOGIES, LLC, Plaintiff-Appellee

v.

UNITED STATES, F3EA, INC., Defendants-Appellants ______________________

2022-1556, 2022-1557 ______________________

Appeals from the United States Court of Federal Claims in No. 1:21-cv-00775-MHS, Judge Matthew H. Sol- omson. ______________________

Decided: September 11, 2024 ______________________

CRAIG HOLMAN, Arnold & Porter Kaye Scholer LLP, Washington, DC, argued for plaintiff-appellee. Also repre- sented by THOMAS PETTIT.

WILLIAM JAMES GRIMALDI, Commercial Litigation Branch, Civil Division, United States Department of Jus- tice, Washington, DC, argued for defendant-appellant United States. Also represented by BRIAN M. BOYNTON, PATRICIA M. MCCARTHY, DOUGLAS K. MICKLE, JOSEPH ALAN PIXLEY; MICHAEL RAY TREGLE, JR., Contract Litigation & Intellectual Property Division, United States Army Legal Services Agency, Fort Belvoir, VA. Case: 22-1556 Document: 114 Page: 2 Filed: 09/11/2024

JOSHUA ALLAN MULLEN, Womble Bond Dickinson (US) LLP, Nashville, TN, argued for defendant-appellant F3EA, Inc. Also represented by RAYMOND BENNETT, Ra- leigh, NC. ______________________

Before PROST, STOLL, and STARK, Circuit Judges. STARK, Circuit Judge. This bid protest action originated with the United States Department of the Army (“Army” or “agency”) awarding a contract to F3EA, Inc. (“F3EA”). Another bid-der, Oak Grove Technologies, LLC (“Oak Grove”), protested the award, including by filing suit in the Court of Federal Claims. The Court of Federal Claims agreed with Oak Grove that the bidding process had gone awry and, there-fore, enjoined the Army from proceeding with its award to F3EA. It further ordered the Army either to begin the pro-curement process anew or reopen it to conduct discussions with, and accept revised final proposals from, multiple of-ferors, including Oak Grove. The trial court also sanc-tioned the government for repeatedly failing to include material evidence in the administrative record. Both F3EA and the government appeal the trial court’s judgment and the injunction. The government additionally appeals the trial court’s sanctions order. We vacate the judgment and the injunction, affirm the sanctions order, and remand for further proceedings. I A The contract at issue here is called “Special Operations Forces Requirements, Analysis, Prototyping, Training, Op-erations and Rehearsal,” or “SOF RAPTOR.” J.A. 2650. As the name implies, SOF RAPTOR is a contract vehicle that the Army uses for procuring training services for its special Case: 22-1556 Document: 114 Page: 3 Filed: 09/11/2024

OAK GROVE TECHNOLOGIES, LLC v. US 3

forces. When the predecessor contract to the one at issue here was set to expire, the Army issued a solicitation (“So- licitation,” “Request for Proposals,” or “RFP”) for SOF RAPTOR IV, a small business set-aside, single-award, in- definite delivery indefinite quantity (“IDIQ”) contract with an order ceiling of $245 million. In the Solicitation, the Army required offerors to include in their proposals four volumes addressing the following factors: (1) capability, (2) past performance, (3) cost/price, and (4) administrative. See J.A. 2764-65. The Solicitation provided that the capa- bility, past performance, and cost/price volumes would be evaluated in that order of importance. See J.A. 2778. The Solicitation did not include any criteria for evaluating the “administrative” volume. The government indicated that, in evaluating proposals, it “may use information other than that provided by Offeror in its evaluation . . . includ[ing] DCAA [Defense Contract Audit Agency], DCMA [Defense Contract Management Agency], Government Databases and past performance questionnaires.” J.A. 2777. The Solicitation explained that the capability factor in- cluded three technical subfactors, and that a rating of “un- acceptable” or “marginal” in any of the three subfactors would result in an “unacceptable” or “marginal” rating for the overall capability factor, rendering a proposal “una- wardable.” J.A. 3547-48. The “program management sub- factor” required the offeror to demonstrate the ability to address, among other things, “[m]anagement [s]tructure,” J.A. 2766, 2778. In connection with “[m]anagement [s]tructure,” an offeror was required to “identify all team- ing arrangements, partnerships, joint venture ownership and contingencies, as applicable, within this description.” Id. Relatedly, the Solicitation required offerors to submit “all executed teaming arrangements” and provided that “any previous teaming arrangements . . . that [are] refer- enced within the proposal shall be included as attachments in the admin volume as supporting documentation.” Case: 22-1556 Document: 114 Page: 4 Filed: 09/11/2024

J.A. 2775. The Solicitation also stated that “any modifica- tions to a teaming arrangement must be reviewed by the Contracting Officer before the effective date of such modi- fication in order to ensure that there [are] no negative im- pacts on contract performance, in accordance with FAR [Federal Acquisition Regulation] 9.603.” J.A. 2771. As rel- evant here, FAR § 9.603 provides that “[t]he Government will recognize the integrity and validity of contractor team arrangements; provided, the arrangements are identified and company relationships are fully disclosed in an offer or, for arrangements entered into after submission of an offer, before the arrangement becomes effective.” Past performance was evaluated for relevancy (i.e., “Very Relevant,” “Relevant,” “Somewhat Relevant,” or “Not Relevant”) and confidence (i.e., “Substantial Confidence,” “Satisfactory Confidence,” “Neutral Confidence,” “Limited Confidence,” or “No Confidence”). J.A. 2784-85. For Cost/Price factor, the Solicitation specified that the “DCAA will be requested to perform a Financial Capability Risk Assessment for the Prime offeror” and that “[t]he Prime of- feror must be deemed financially responsible by the Con- tracting Officer based on the Financial Capability Risk Assessment.” J.A. 2783. As relevant here, FAR § 9.103(a) provides that “[p]urchases shall be made from, and con- tracts shall be awarded to, responsible prospective contrac- tors only.” Because SOF RAPTOR IV is a small business set-aside contract, FAR § 9.105-2(a)(2) also requires that “[i]f the contracting officer determines that a responsive small business lacks certain elements of responsibility,” the contracting officer shall “[r]efer the matter to the cog- nizant SBA [Small Business Administration],” FAR § 19.602-1(a)(2). Once the SBA assesses the financial re- sponsibility of the small business, FAR § 9.105-2(a)(2) re- quires “the contracting officer [to] accept the Small Business Administration’s decision to issue a Certificate of Competency and award the contract to the concern.” Case: 22-1556 Document: 114 Page: 5 Filed: 09/11/2024

OAK GROVE TECHNOLOGIES, LLC v. US 5

B Oak Grove, F3EA, and Lukos-VATC III, LLC (“Lukos”) were among the ten offerors that timely submitted pro- posals to be awarded the SOF RAPTOR IV contract. Oak Grove and F3EA were both members of Raptor Training Services, LLC, a joint venture that had been awarded the predecessor contract, SOF RAPTOR III. The Army initially screened proposals to ensure that all necessary information was submitted. Later, source se- lection evaluation board (“SSEB”) teams were assigned to evaluate and rate proposals. A person identified as “RM” was the chairperson of the overall SSEB and, in that ca- pacity, RM received all reports from various teams within the SSEB. See J.A. 2700 (showing source selection team structure); J.A. 2690-91 (outlining roles and responsibili- ties of SSEB).

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
116 F.4th 1364, Counsel Stack Legal Research, https://law.counselstack.com/opinion/oak-grove-technologies-llc-v-united-states-cafc-2024.