Johnson Controls Government Systems, LLC v. United States

125 Fed. Cl. 289, 2016 U.S. Claims LEXIS 97, 2016 WL 690843
CourtUnited States Court of Federal Claims
DecidedFebruary 19, 2016
Docket15-1440C
StatusPublished
Cited by3 cases

This text of 125 Fed. Cl. 289 (Johnson Controls Government Systems, LLC 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
Johnson Controls Government Systems, LLC v. United States, 125 Fed. Cl. 289, 2016 U.S. Claims LEXIS 97, 2016 WL 690843 (uscfc 2016).

Opinion

Pre-award Bid Protest; Late Submittal of Proposal; FedConnect Electronic Filing System; FAR 52.215-1.

OPINION AND ORDER

WHEELER, Judge.

In this pre-award bid protest, Plaintiff Johnson Controls Government Systems, LLC (“Johnson Controls”) challenges a decision by the U.S. Department of Energy (“DOE”) that Plaintiffs proposal should be rejected as late. Johnson Controls requests the Court to overturn DOE’s action as unreasonable and to compel DOE to evaluate Plaintiffs proposal before award. After full briefing and oral argument, the Court finds that DOE acted reasonably in rejecting Johnson Controls’ proposal as untimely, and the protest is DENIED.

Factual Background

DOE issued Solicitation No. DE-SOL-0006380 on March 23, 2015, seeking proposals for indefinite delivery, indefinite quantity (“IDIQ”) Energy Savings Performance Contracts, under which individual projects would be awarded by task orders. Administrative Record (“AR”) 115. The Instructions to Of-ferors provided specifically that proposals were required to be submitted through the “FedConnect Responses” web portal:

Submission of Proposals. Proposals shall only be accepted through FedConnect. It is imperative that the Offeror read and understand how to submit its quote using the FedConnect web portal by going to www.fedconnect.net. All proposal documents required by this solicitation must be uploaded and received in their entirety in the FedConnect Responses web portal no later than April 29, 2015.[ 1 ] Proposals submitted via hardcopy, email, or the Fed-Connect Message Center shall not be accepted or considered. Failure to submit a response that is received through the Fed-Connect Responses web portal by the stat *291 ed time and date may result in the proposal not being considered. By submitting a proposal, the Offeror agrees to comply with all terms and conditions as set forth in this solicitation.

AR 393. The Solicitation Instructions also referenced Federal Acquisition Regulation (“FAR”) 52.215-1 “for rules concerning submission of offers and late proposals.” AR 392.

The Solicitation Instructions do not explain that FedConnect is a privately owned and maintained portal which interfaces with a variety of federal agencies including DOE. AR 461. This information is contained in the guide found at fedconnect.net, FedConnect, Ready, Set, Go!, AR 446-498, which describes how FedConnect enables federal agency contracting officials to post solicitations, receive proposals, and otherwise communicate with prospective vendors. A review of the AR reveals that, like the other participating agencies, DOE contracting officials do not have login rights or other direct access to FedConnect. Rather, all DOE access to documents submitted by potential vendors comes after they are imported through FedConnect into DOE’s own procurement system, the Strategic Integrated Procurement Enterprise System known as “STRIPES.” The offeror completely controls the proposal submittal process and must follow the proper submission procedures. AR 30-31. As explained in the Fed-Connect guide, the recorded date and time of a vendor’s submission is the date and time the vendor clicked the “submit” button in FedConnect, at which time the vendor receives a confirmation. AR487. Until the “submit” button is clicked, the agency has no knowledge of the submission, and the vendor can access its proposal for modification or withdrawal at any time. AR486.

On May 11 and 12, 2015, a Johnson Controls employee uploaded the complete proposal to the FedConnect Responses web portal. The portal then indicated to the employee that the volumes of the proposal were “In Progress.” The employee took no further action to deliver the proposal at that time. On the due date, May 13, 2015, Johnson Controls sent an email message through FedConnect to the DOE Contracting Officer requesting confirmation that the proposal had been received. The Contracting Officer responded the same day that DOE had not received the proposal; however, the employee did not receive this message. AR 894. On May 18, 2013, five days after the due date, Johnson Controls inquired again as to DOE’s receipt of the proposal. This time the employee received a DOE response that the agency had not received the proposal. Johnson Controls then sought advice from the Help Desk at FedConnect and learned that although the proposal was in the Fed-Connect system, the employee should have clicked the “submit” link in order to complete proposal delivery. Johnson Controls completed this step on May 18, 2013, and as the proposal moved into DOE’s STRIPES system, the status of the proposal volumes changed from “In Progress” to “Submitted.” AR 818.

Johnson Controls then wrote to the Contracting Officer requesting that its offer be treated as timely, describing the events that delayed submission of the proposal. Johnson Controls also argued that even if the proposal were not considered timely, it could nevertheless be accepted under the exceptions described in the FAR provisions on timing of offers, FAR 52.215-1, which had been incorporated into the Solicitation. AR 417. DOE’s July 27, 2015 response denied the request, stating that the proposal was submitted late and would not be evaluated. AR 427. Johnson Controls then filed an agency-level protest of that decision, which was unsuccessful. AR 512, 583. Next came a protest filed with the Government Accountability Office, which was denied on November 24, 2015. AR 1-5, Johnson Controls Government Systems, LLC, B-411862.2, Nov. 24, 2015, 2015 CPD ¶ 357.

Johnson Controls filed its complaint in this Court on December 1, 2015. Defendant submitted the certified administrative record on December 16, 2015. The parties filed cross-motions for judgment on the administrative record, and the Court heard oral argument on February 11,2016.

*292 Standard of Review

In a bid protest, this Court reviews an agency’s decision pursuant to the standards set forth in the Administrative Procedure Act (“APA”). 5 U.S.C. §§.701-706 (2000); see also Impresa Construzioni Geom. Domenic Garufi v. United States, 238 F.3d 1324, 1332 (Fed.Cir.2001) (stating that the APA standard of review shall apply in all procurement protests in the Court of Federal Claims). Under the APA, a reviewing court shall set aside an agency action if it is “arbitrary, capricious, an abuse of discretion, or otherwise not in accordance with law.” 5 U.S.C. § 706(2)(A).

The APA standard allows this Court to set aside an agency’s procurement decision if it lacked a rational basis or if the agency’s decision-making involved a violation of regulation or procedure. Impresa, 238 F.3d at 1332. When evaluating a challenge on the first ground, a court “must determine “whether the contracting agency provided a coherent and reasonable explanation of its exercise of discretion. When a challenge is brought on the second ground, the disappointed bidder must show a clear and prejudicial violation of applicable statutes or regulations.’ ” Axiom Res. Mgmt., Inc. v. United States,

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

Related

The Informatics Applications Group, Inc. v. United States
132 Fed. Cl. 519 (Federal Claims, 2017)
Progressive Industries, Inc. v. United States
129 Fed. Cl. 457 (Federal Claims, 2016)

Cite This Page — Counsel Stack

Bluebook (online)
125 Fed. Cl. 289, 2016 U.S. Claims LEXIS 97, 2016 WL 690843, Counsel Stack Legal Research, https://law.counselstack.com/opinion/johnson-controls-government-systems-llc-v-united-states-uscfc-2016.