DGS Contract Service, Inc. v. United States

43 Fed. Cl. 227, 1999 U.S. Claims LEXIS 44, 1999 WL 147922
CourtUnited States Court of Federal Claims
DecidedMarch 8, 1999
DocketNo. 98-891C
StatusPublished
Cited by38 cases

This text of 43 Fed. Cl. 227 (DGS Contract Service, 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
DGS Contract Service, Inc. v. United States, 43 Fed. Cl. 227, 1999 U.S. Claims LEXIS 44, 1999 WL 147922 (uscfc 1999).

Opinion

OPINION

FUTEY, Judge.

This post-award bid protest action is before the court on the parties’ cross-motions for summary judgment on the administrative record. Plaintiff also requests a permanent injunction. Plaintiff maintains that the discussions held by the Internal Revenue Service (IRS) with offerors in the competitive range violated the Procurement Integrity Act, 41 U.S.C. § 423 (Supp. II 1996) and several procurement regulations, and thus it is entitled to judgment as a matter of law. Conversely, defendant avers that its actions during the procurement process complied with the Procurement Integrity Act and procurement regulations, and therefore it is entitled to judgment as a matter of law.

Factual Background

On May 20, 1998, defendant, through the IRS’s Midstates Procurement Office, issued solicitation number TIRMS-98-R-00019 (the solicitation), seeking offers for a five-year contract for guard services at its Ogden Service Center in Ogden, Utah. The solicitation sought a contractor to provide “all management, supervision, labor, materials, supplies and vehicles for armed security guard service.” 2 The procurement is a small business set-aside, set up in accordance with the Department of Treasury Acquisition Regulation (DTAR) 1019.503 and Federal Acquisition Regulation (FAR) Part 19, Small Business Programs. Plaintiff currently provides these services as the incumbent contractor under contract number TIR-93-SW-010.

The IRS conducted the procurement process under the negotiated contract method. Pursuant to 48 C.F.R. § 15.304, the solicitation incorporates a source selection technique that includes a Source Selection Plan and a Technical Evaluation Plan (TEP).3 The TEP states that “the offeror’s proposals are influenced by three major sections of the solicitation: (1) Section C — Description/ Specifications/ Work Statement; (2) Section L — Instructions, Conditions, and Notice to Offerors; and (3) Section M — Evaluation Factors for Award.”4 Section L requires that proposals contain two separate parts: one part entitled “price proposal” and the other part entitled “technical proposal.”

With respect to price, the solicitation provides that the “[p]rice [p]roposal shall be submitted on Section LB, completely separate from [the][t]echnical [p]roposal, and consist of all information relevant to price of the [230]*230contract line items.”5 It further states that “[a]n additional price proposal reflecting the individual elements of the pricing may be requested by the Contracting Officer, if considered appropriate.”6 The solicitation requires that the technical proposal:

shall not make reference to cost or price data, so that a technical evaluation may be made on the basis of technical merit alone. The technical portion of the proposal will be an important consideration in the award of this contract, and therefore, Offeror should provide all the information requested under Section L of the solicitation, as complete and specific as possible.7

Pursuant to the solicitation, the IRS established a Technical Evaluation Team (TET) to evaluate proposals consistent with sections L and M of the solicitation, and the TEP. Each technical proposal would be reviewed by all the TET members.8 In order for a technical proposal to be acceptable and eligible for evaluation, it had to be “prepared in accordance with and comply with the instructions given in [the] solicitation document, and ... meet all the requirements set forth in the solicitation.”9 The solicitation requires the TET to evaluate technical proposals based upon four factors. Listed in order of importance, these factors include: (1) Past Performance/Experience; (2) Approach; (3) Quality Control; and (4) Contingency Plan.10 The solicitation further provides that each of the four factors would be rated using an “adjectival scoring methodology,” rating each factor as either “exceptional,” “acceptable,” “marginal,” or “unacceptable.”11

The solicitation specifically addresses the basis upon which defendant must award the contract:

The Government will make award to the responsible Offeror whose offer conforms to the requirements of the solicitation and is evaluated as being the most advantageous to the Government, price and other factors considered. For this solicitation, technical merit is significantly more important than price. Award will not be automatically determined by formula relationship between price and technical merit. As technical merit of the Offerors’ proposals become more equal, the price may become the determining factor. The Contracting Officer shall determine what trade-off between technical merit and price promises the greatest value to the Government, price and other factors considered.12

Plaintiff timely submitted its price and technical proposals on June 30, 1998. Plaintiffs price proposal amounted to [* *]. On that same day, Mike Garcia Merchant Security, Inc. (MGM) submitted proposals, with its price proposal amounting to [* *]. Twelve other offerors also submitted proposals.

The TET evaluated fourteen technical proposals between July 6, 1998 and July 10, 1998. Of the fourteen proposals received, two were deemed “exceptional,” one of which was MGM’s. Plaintiffs proposal, along with the technical proposals of three other offer-ors, was rated as “acceptable.” Of the remaining technical proposals, six were rated as “marginal,” and two were rated as “unacceptable.” The IRS removed the proposals that were rated lower than “acceptable” from the competitive range.

After establishing the competitive range, Ms. Vica Mowery, the contracting officer (CO), conducted written discussions with the offerors within the competitive range. According to defendant, the CO developed questions “to identify price increases, if any, and technical weaknesses identified by the TET.”13 Additionally, defendant maintains that it asked all the offerors the same set of questions. The CO mailed these questions to [231]*231the offerors on July 24, 1998, wherein the offerors responded by July 30, 1998. The TET then evaluated the responses given by each offeror concerning its technical proposals. Based upon the responses received, the TET decided not to raise the technical score for either plaintiff or for MGM.

On August 14, 1998, the CO removed two more offerors from the competitive range, reducing the total number of offerors to four. The remaining offerors included MGM, Unlimited Security, Inc. (Unlimited), Southwestern Security Services, Inc. (Southwestern), and plaintiff. In a telephonic conference held on August 16, 1998, between MGM and IRS officials, MGM responded to the IRS’s questions and explained its reasons for including certain price estimates in its proposal.14

On August 17, 1998, IRS officials held a telephonic conference with plaintiff, in which plaintiff responded to questions concerning the inclusion of certain price elements in its proposal.15 Significantly, the CO notified Mr.

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

Related

American Sanitary Products, Inc. v. United States
133 Fed. Cl. 327 (Federal Claims, 2017)
Jacobs Technology Inc. v. United States
131 Fed. Cl. 430 (Federal Claims, 2017)
Sos International LLC v. United States
127 Fed. Cl. 576 (Federal Claims, 2016)
Square One Armoring Service, Inc. v. United States
123 Fed. Cl. 309 (Federal Claims, 2015)
Whr Group, Inc. v. United States
115 Fed. Cl. 386 (Federal Claims, 2014)
Manus Medical, LLC v. United States
115 Fed. Cl. 187 (Federal Claims, 2014)
Amazon Web Services, Inc. v. United States
113 Fed. Cl. 102 (Federal Claims, 2013)
Chameleon Integrated Services, Inc. v. United States
111 Fed. Cl. 564 (Federal Claims, 2013)
Reema Consulting Services, Inc. v. United States
107 Fed. Cl. 519 (Federal Claims, 2012)
Sierra Nevada Corp. v. United States
107 Fed. Cl. 735 (Federal Claims, 2012)
Wildflower International, Ltd. v. United States
105 Fed. Cl. 362 (Federal Claims, 2012)
Systems Application & Technologies, Inc. v. United States
100 Fed. Cl. 687 (Federal Claims, 2011)
Sheridan Corp. v. United States
95 Fed. Cl. 141 (Federal Claims, 2010)
SP Systems, Inc. v. United States
86 Fed. Cl. 1 (Federal Claims, 2009)
Carahsoft Technology Corp. v. United States
86 Fed. Cl. 325 (Federal Claims, 2009)

Cite This Page — Counsel Stack

Bluebook (online)
43 Fed. Cl. 227, 1999 U.S. Claims LEXIS 44, 1999 WL 147922, Counsel Stack Legal Research, https://law.counselstack.com/opinion/dgs-contract-service-inc-v-united-states-uscfc-1999.