Joint Venture of Comint Systems Corp. v. United States

102 Fed. Cl. 235, 2011 U.S. Claims LEXIS 2363, 2011 WL 6370159
United States Court of Federal Claims·Decided December 2, 2011·No. Nos. 11-400 C, 11-416 C·Published·Cited by 6 cases

Opinion

OPINION AND ORDER

SWEENEY, Judge.

Plaintiffs Comint and NetServices protest awards issued by the United States Departs ment of Defense (“Defense Department”) during its Net-Centric Integrated Enterprise Information Technology Solutions (“NIEITS”) acquisition of information technology (“IT”) services and seek various forms of declaratory and injunctive relief. NetCentries Corporation (“NetCentries”), Digital Management, Inc. (“DMI”), and PowerTek Corporation (“PowerTek”), the three contract awardees, intervened in defense of the award. Currently pending before the court are plaintiffs’ motions for judgment upon the administrative record and for declaratory and injunctive relief, defendant’s motions to dismiss, and defendant-intervenors’ motions to dismiss and cross-motions for judgment upon the administrative record. For the reasons set forth below, the court determines that plaintiffs fail to establish standing to bring their protests. Accordingly, the court denies plaintiffs’ motions for judgment upon the administrative record and for declaratory and injunctive relief, grants defendant’s motions to dismiss plaintiffs’ second amended complaints, grants in part and denies in part as moot NetCentries’ combined motion to dismiss plaintiffs’ second amended complaint and for judgment upon the administrative record, grants DMI’s motions to dismiss plaintiffs’ second amended complaints, denies as moot DMI’s cross-motions for judgment upon the administrative record, grants PowerTek’s motions to dismiss plaintiffs’ second amended complaints, and denies as moot PowerTek’s cross-motions for judgment upon the administrative record.

I. FACTUAL BACKGROUND1

A. Agency Structure

The NIEITS acquisition represented a Defense Department effort to obtain IT services [237] to support the Office of the Secretary of Defense (“OSD”), the Washington Headquarters Services (“WHS”), and the Pentagon Force Protection Agency (“PFPA”).2 AR 342. For purposes of the NIEITS acquisition, the OSD, the WHS, and the PFPA, among other entities, were considered part of the Director of Administration and Management (“DA & M”) IT community. Id. at 6.

The DA & M IT community contracted with approximately thirteen different companies for IT help desk, server, network, and applications support services. Id. at 7, 352. These various contracts resulted in uncoordinated purchasing of equipment and services. Id. at 7. In response, the WHS determined that combining the existing contracts “to obtain a full range of integrated enterprise net-centric IT supplies and services,” id. at 343, would achieve numerous organizational goals, see id. at 343-44; see also id. at 6 (indicating that the WHS sought “seamless, reliable, and responsive enterprise solutions for IT services ... that improve existing services resulting in a stable and secure enterprise IT network”). The WHS considered five different methods by which to achieve these objectives and ultimately selected a multiple award, indefinite delivery/indefinite quantity (“ID/IQ”) contract vehicle for small businesses with a size standard of $25 million. Id. at 8-9, 239.

B. The Solicitation

On August 2, 2010, the WHS issued solicitation No. HQ0034-10-R-0046 to award a minimum of two ID/IQ contracts that “provide[d IT] solutions through performance of a broad range of services which include[d] the integration of various types of support critical to the services being acquired.” Id. at 247. The contract awardees were to “provide labor, hardware/software, and other equipment and materials required to provide a wide range of net-centric integrated IT support, services, and supplies for customers and organizations to support IT systems and customers in the DA & M IT community.... ” Id. at 344.

The solicitation was comprised of three elements: (1) a Basic Contract; (2) Task Order 1, Enterprise IT Operations Services (“Task Order 1”); and (3) Task Order 2, Enterprise IT Engineering Support Services (“Task Order 2”).3 Id. at 159. The Basic Contract consisted of a twenty-four-month base period and three twelve-month option periods. Id. at 247, 6783. The total minimum guaranteed by the government for the base period was $2,500 for each awardee, and the total maximum quantity of all supplies and services, including all option periods, under the Basie Contract could not exceed $495 million. Id. The solicitation authorized three types of task orders: firm-fixed-price;4 firm-fixed-price, level-of-effort term;5 and cost-reimbursement.[238] 6 Id. at 249, 6783. An individual task order could relate to one major task area or involve functions from multiple task areas.7 Id. at 345.

1. Solicitation Elements

The Basie Contract consisted of a schedule of labor rates for workers in specified categories. Task Order 1 identified eight functional areas of contract performance.8 Id. at 6363. The contractor’s performance goal under Task Order 1 was to “[pjrovide seamless, reliable, and responsible enterprise solutions” for IT services. Id. at 6382. Performance standards included creating a stable and secure enterprise IT network that (1) met functionality, speed, and capacity expectations of OSD end users and (2) complied with Defense Department and federal rules and regulations. Id.

Task Order 2 identified six areas of contractor support through which the Defense Department would acquire advisory and assistance services to support and improve IT operations.9 Id. at 6390. Task Order 2 enumerated ten individual tasks, five of which were optional. See id. at 6393^413. The contractor was not required to perform inherently governmental functions under Task Order 2. Id. at 6390. Activities and deliverables were specified by the government, and the method and manner of performance were determined by the contractor. Id.

2. Evaluation of Proposals

The government intended to award contracts to responsible offerors with proposals that (1) complied with the solicitation’s provisions, (2) were responsive to the solicitation’s requirements, (3) demonstrated the offeror’s ability to perform the breadth and scope of the requirements, (4) set forth a price that was determined by the contracting officer to be fair and reasonable, and (5) represented the overall best value to the government. Id. at 335. Offerors were required to propose on each element of the solicitation. Id. The government intended to make awards without discussions, but it reserved the right to conduct discussions if they were deemed necessary by the contracting officer. Id. at 144.

a. Offeror Eligibility

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

Joint Venture of Comint Systems Corp. v. United States, 102 Fed. Cl. 235, 2011 U.S. Claims LEXIS 2363, 2011 WL 6370159 (uscfc 2011).

102 Fed. Cl. 235 (Joint Venture of Comint Systems Corp. v. United States) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related