Information Technology & Applications Corporation v. United States, and Rs Information Systems, Inc.

316 F.3d 1312, 2003 U.S. App. LEXIS 404
CourtCourt of Appeals for the Federal Circuit
DecidedJanuary 10, 2003
Docket11-5001
StatusPublished
Cited by639 cases

This text of 316 F.3d 1312 (Information Technology & Applications Corporation v. United States, and Rs Information Systems, Inc.) 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
Information Technology & Applications Corporation v. United States, and Rs Information Systems, Inc., 316 F.3d 1312, 2003 U.S. App. LEXIS 404 (Fed. Cir. 2003).

Opinions

DYK, Circuit Judge.

This case involves the distinction between “clarifications” and “discussions” under the 1997 revision to Subpart 15.3 of the Federal Acquisition Regulations. 48 C.F.R. §§ 15.300-08 (2002). Information Technology and Applications Corporation (“ITAC”) appeals the decision of the United States Court of Federal Claims denying its bid protest and granting the United States motion for summary judgment on the administrative record. Info. Tech. & Applications Corp. v. United States, 51 Fed.Cl. 340 (Fed.Cl.2001). Because we have determined that the Air Force’s contacts with appellee RS Information Systems, Inc. (“RSIS”) were allowable requests for “clarification” of its proposal and did not constitute “discussions,” and because the appellant’s other asserted grounds for reversing the decision of the Court of Federal Claims are without merit, we affirm.

BACKGROUND

On March 19, 2001, the Air Force issued Solicitation and Request for Proposals No. FA2550-01-R-0001 (“RFP”) to obtain a contract for professional services in support of its Space Warfare Center. The winning contractor was to examine, assess and develop means of integrating national intelligence assets with the Department of Defense space systems, in order to enhance combat and research and development capabilities at the Space Warfare Center. The Air Force intended to make an award to one lead contractor, which would perform overall program management and integration, operations support, systems engineering and analysis, and other work related to the Space Warfare Center. The term of performance was to be twelve months, beginning on October 1, 2001, with seven one-year options.

Under the RFP, the contract was to be awarded “to an offeror who gives the Government the greatest confidence that it will best meet [the] requirements afford-ably.” RFP at 81. In accordance with 10 [1316]*1316U.S.C. § 2305(a)(2)(A) and 41 U.S.C. § 253a(b)(l), the RFP also disclosed “all the significant factors and significant sub-factors” that the agency “reasonably expected] to consider,” and their relative importance. 10 U.S.C. § 2305(a)(2)(A) (2000); 41 U.S.C. § 253a(b)(l) (2000); RFP at 81-85.

ITAC, RSIS and a third offeror submitted timely proposals in response to the RFP. All three proposals anticipated that some of the work would be performed by subcontractors. RSIS’s proposal relied heavily on the role of its subcontractors, which were to perform at least 75% of the work on the contract.

The Air Force sent various “evaluation notices” (“ENs”) to all three offerors. These evaluation notices were brief letters to the offerors requesting additional information regarding their proposals. The Air Force sent three ENs to ITAC, five ENs to RSIS, and three ENs to the third offer- or. At .issue in this case are ENs Nos. 0001, 0002 and 0002a, which the Air Force sent to RSIS after the offerors had submitted “past performance” information, but before the due date for the other parts of the proposals. The ENs at issue sought “additional information ... to verify relevant past performance for [the] lead and support roles” of at least ten subcontractors that RSIS listed in its proposal. EN No. 0002. The Air Force sent ENs to the other bidders requesting additional information on their subcontractors as well.1 The disputed ENs were labeled “FAR 15.306(a) Clarification[s]” and included the notice, “Please note that this clarification does not constitute oral discussions with the offeror.” EN 0002, referring to 48 C.F.R. § 15.306(a).

RSIS responded to the ENs on May 1, 2001, explaining which parts of the project each subcontractor would support and detailing the subcontractors’ relevant experience with regard to those tasks. For example, in response to EN 0002, RSIS responded, “[subcontractor] Aerojet has developed and integrated the CTPP/ ALERT and the JTAGS IR missile warning processing systems into the tactical missile warning C2 operational architecture, (Similarities to [contract] Requirements, V-67, and V-59).” (RSIS Response to Evaluation Notice.)

The Air Force gave both ITAC and RSIS an “overall exceptional rating” for their “past performance” experience. (Proposal Analysis Report for RFP # FA2550-01-R-0001, July 11, 2001). The Air Force determined that prior contracts of RSIS and its subcontractors were relevant to their ability to perform the Space Warfare Center contract.

The Air Force performed an independent “Most Probable Cost analysis” on the proposals submitted by RSIS and the third bidder. The “Most Probable Cost analysis” was an independent analysis of the bidder’s estimated cost for “reasonableness” and “realism.” RFP at 85. The Air Force “assessed] the compatibility of the overall proposed costs with the scope of effort to be performed.” Id. The Air

[1317]*1317Force did not perform a “Most Probable Cost analysis” on ITAC’s proposal, because its evaluation team found that ITAC’s proposed hours were so minimal and unrealistic that it was infeasible to perform an adequate analysis. (Source Selection Decision Document at 4.) As a result of this independent analysis performed with respect to RSIS and the third bidder, the Air Force increased the estimated labor hours for RSIS and the third bidder, after determining “that additional hours were required in each labor category to successfully perform the effort.” Info. Tech. & Applications Corp. v. United States, No. 01-637 C, slip op. at 9 n. 15 (Fed.Cl. Dec. 7, 2001). There is no suggestion that these adjustments resulted from RSIS’s responses to the disputed ENs.

On July 23, 2001, the Air Force announced its decision to award the contract to RSIS. In its Source Selection Decision Document, the Air Force explained that all three proposals were rated equally for “Program Management and Integration” and for “Past Performance” (which was the subject of the disputed ENs), and that these were not, therefore, “discriminating factors.” (Source Selection Decision Document at 2.) The Air Force determined that although “[a]ll Offerors provided proposals which met minimum contract requirements,” and “all proposals were fundamentally sound,” “key discriminators were made in Mission Capability ..., Proposal Risk, and CosVPrice.” Id. at 1. RSIS performed higher than ITAC in the categories of “Mission Capability” and “Proposal Risk.” Id. at 2-4. In the area of “Cost/Price,” the Air Force found, “RSIS provided the lowest overall price for the written Task Order and provided the best overall price to the Government.” Id. at 5. The Air Force concluded:

In summary, RSIS offered an excellent proposal with lower risk and several innovative approaches to improve efficiency of SWC operations that were deemed to be beneficial to the Government. As a result, the RSIS proposal provided the overall best .value to the Government. Based on my integrated assessment that the RSIS proposal provided a better technical and lower risk offer, I direct the award to RS Information Systems.

Id.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
316 F.3d 1312, 2003 U.S. App. LEXIS 404, Counsel Stack Legal Research, https://law.counselstack.com/opinion/information-technology-applications-corporation-v-united-states-and-rs-cafc-2003.