D.C. Mun. Regs. r. 27-1630

Current through Register Vol. 71, No. 24, June 14, 2024
Rule 27-1630 - PROPOSAL EVALUATION
1630.1

The contacting officer shall evaluate each proposal using only the evaluation criteria stated in the RFP and in accordance with the weightings provided in the RFP.

1630.2

The contracting officer shall evaluate the cost or price to determine reasonableness.

1630.3

If any technical evaluation is necessary beyond ensuring that the proposal meets the minimum requirements in the solicitation, the contracting officer shall forward the proposals to the appropriate technical official for technical evaluation.

1630.4

If a technical evaluation is done, a technical evaluation report shall be prepared by the technical official and shall contain the following:

(a) The basis for evaluation;
(b) An analysis of the technically acceptable and unacceptable proposals, including an assessment of each offeror's ability to accomplish the technical requirements;
(c) A summary, matrix, or quantitative ranking of each technical proposal in relation to the best rating possible; and
(d) A summary of findings.
1630.5

When evaluating a cost-reimbursement contract, the cost proposal shall not be controlling. The contracting officer shall consider which offeror can perform the contract in a manner most advantageous to the District as determined by evaluation of proposals according to the established evaluation criteria.

1630.6

The contracting officer may reject all proposals received in response to a solicitation by a written determination that to do so would be in the best interest of the District. The contracting officer's determination shall be approved by the Director.

1630.7

The reasons given for rejection may include, but are not limited to, the following:

(a) All otherwise acceptable proposals received are at unreasonable prices; or
(b) The proposals were not independently arrived at in open competition, were collusive or were submitted in bad faith.
1630.8

When all proposals are rejected and no award will be made as a result of the RFP, the contracting officer shall cancel the RFP.

1630.9

The contracting officer shall prepare supporting documentation for the selection decision that shows the relative differences among the proposals and their strengths, weaknesses, and risks in terms of the evaluation factors. The supporting documentation shall include the basis for the selection.

D.C. Mun. Regs. r. 27-1630

Final Rulemaking published at 35 DCR 1464 (February 26, 1988); as amended by Notice of Emergency and Proposed Rulemaking published at 58 DCR 150 (January 7, 2011)[EXPIRED]; as amended by Notice of Emergency Rulemaking published at 58 DCR 4039 (May 6, 2011)[EXPIRED]; as amended by Notice of Emergency and proposed Rulemaking published at 58 DCR 8080 (September 16, 2011)[EXPIRED]; as amended by Notice of Final Rulemaking published at 58 DCR 9826 (November 18, 2011); as amended by Final Rulemaking published at 60 DCR 1136 (February 1, 2013); as Amended by Final Rulemaking published at 61 DCR 11164 (October 24, 2014)
Authority: The Chief Procurement Officer of the District of Columbia (CPO), pursuant to the authority set forth in sections 204 and 1106 of the Procurement Practices Reform Act of 2010, effective April 8, 2011 (D.C. Law 18-371; D.C. Official Code §§ 2-352.04 and 2-361.06 )(2011 Repl.)) (Act).