Reference

More Resources

 

Section 315.305: Proposal evaluation.

(a)(1) Cost or price evaluation.

(i) The Contracting Officer shall evaluate proposals in accordance with the FAR 15.404. The extent of cost or price analysis in each case depends on the availability of competition, contract type, the proposed amount, and technical complexity.

(A) For competitive firm-fixed-price and fixed price with economic price adjustment contracts, price analysis should be sufficient to determine price fairness and reasonableness.

(B) When competition is not adequate for the above contract types, and for cost-reimbursement and time and materials contracts, cost analysis may be required. In such cases, the Contracting Officer shall request the Project Officer's assistance in analyzing the following cost elements, if applicable, to determine if the proposed amounts are necessary and reasonable for efficient contract performance:

(1) The number and mix of proposed labor hours relative to the technical requirements.

(2) Types, numbers and hours/days of proposed consultants.

(3) The kinds and quantities of material, equipment, supplies, and services.

(4) Kinds and quantities of IT.

(5) Logic of proposed subcontracting.

(6) Travel proposed, including number of trips, locations, purpose, and travelers.

(7) Other direct costs not specified above.

(ii) The Project Officer shall provide written comments, including the rationale for any exceptions to the cost elements. The Contracting Officer shall consider the Project Officer's comments for negotiations or to support award without discussions. The Contracting Officer shall also request assistance of a cost/price analyst, when necessary.

(2) Past performance evaluation. When evaluating past performance, the Contracting Officer shall check references to obtain information concerning the performance history of offerors in compliance with FAR 42.1502. The Contracting Officer may require the assistance of the Project Officer as well as other Government technical personnel in performing this function.

(3) Technical evaluation.

(i) Technical evaluation plan.

(A) The Contracting Officer shall require a technical evaluation plan if the proposed acquisition either requires preparation of an AP- see 307.71 or is otherwise sufficiently complex.

(B) The technical evaluation plan shall include, at a minimum, the following elements:

(1) A list of recommended technical evaluation panel members, their organizations, a list of their major consulting clients (if applicable), their qualifications, and curricula vitae (if applicable).

(2) A statement that the technical evaluation panel will include non-Federal technical proposal evaluators, if applicable, and a determination that sufficient Federal technical proposal evaluators are unavailable- see FAR 37.204. A determination to use non-Federal proposal evaluators shall be signed at a level no lower than the HCA. A determination is not required, however, if non-Federal evaluators will be used in accordance with 315.303-70(a).

(3) A statement that there is no apparent or actual conflict of interest regarding any recommended panel member.

(4) A copy of each rating sheet, approved by the Contracting Officer, to ensure consistency with the evaluation criteria.

(5) A brief description of the general evaluation approach.

(6) A description of the methodology for evaluating key elements in the technical evaluation plan, including any solicitation evaluation factor involving the acquisition of EIT products and services subject to Section 508.

(C) Except as provided in OPDIV procedures, a program office official at least one level above the Project Officer shall approve the technical evaluation plan.

(D) The Project Officer shall provide the technical evaluation plan to the Contracting Officer for review and approval before the solicitation is issued. The Contracting Officer shall ensure that the evaluation criteria reflect the significant factors and subfactors relating to the evaluation when conducting the review of the plan.

(ii) Technical evaluation panel.

(A) General.

(1) A technical evaluation panel is required for all acquisitions subject to this subpart that require preparation of an AP. The Contracting Officer may require a technical evaluation panel for acquisitions that do not require preparation of an AP, based on the complexity of the acquisition and the role that the technical evaluation will have in the award decision.

(2) The technical evaluation process requires careful consideration regarding the size, composition, expertise, and function of the technical evaluation panel. The panel's efforts will influence the success or failure of the acquisition.

( 3 ) At least 50 percent of the HHS personnel on a technical evaluation panel shall have successfully completed HHS University's “Basic Contracting Officer's Technical Representative” course or an equivalent course within 4 years before assuming their designated role. This training requirement applies to evaluators performing the initial technical evaluation and any subsequent technical evaluations, but does not apply to peer review panel members. The Contracting Officer may waive this training requirement in exigent circumstances if documented in writing and approved by the Head of Contracting Activity. This training requirement applies to evaluators performing the initial technical evaluation and any subsequent technical evaluations. However, this training requirement does not apply to peer review panel members.

(B) Role of the Project Officer.

(1) The Project Officer provides guidance, information, and assistance to the Contracting Officer on all technical aspects of a proposed acquisition- see 302.101. The Project Officer may be a voting member of the technical evaluation panel and may serve as the chairperson of the panel unless prohibited by law or contracting activity procedures.

(2) The Project Officer shall recommend panel members who have sufficient expertise in the technical aspects of the acquisition to be able to evaluate strengths and weaknesses in proposals.

(3) The Project Officer shall ensure that persons possessing expertise and experience in addressing issues relative to sex, race, national origin, and disability are included as panel members for acquisitions to which such issues apply.

(4) The Project Officer shall submit a list of recommended panel members to a program office official at least one level higher than him/herself. This official shall review the list and select the chairperson.

(5) The Project Officer shall arrange for adequate and secure working space for the panel.

(C) Role of the Contracting Officer.

(1) The term “Contracting Officer,” as used in this subpart, may be the Contracting Officer or a Contract Specialist possessing an appropriate FAC-C certification.

(2) The Contracting Officer shall not serve as a member of the technical evaluation panel, but shall-

(i) Address the initial meeting of the technical evaluation panel;

(ii) Provide assistance to the evaluators as required; and

(iii) Ensure that the scores adequately reflect the written technical report comments.

(D) Conflict of interest.

(1) If a panel member has an actual or apparent conflict of interest related to a proposal under evaluation, the individual cannot serve on the panel. If a suitable replacement is not available, the panel shall perform the review without a replacement.

(2) For the purposes of this subpart, conflicts of interest are defined in the Standards of Ethical Conduct for Employees of the Executive Branch (5 CFR part 2635), Supplemental Standards of Ethical Conduct for Employees of the Department of Health and Human Services (5 CFR part 5501), and the Procurement Integrity Act. For outside evaluators serving on the technical evaluation panel, see paragraph (a)(3)(ii)(F) of this section.

(E) Continuity of evaluation process.

(1) The technical evaluation panel shall evaluate all original proposals; make recommendations to the chairperson regarding strengths and weaknesses of proposals; if required by the Contracting Officer, assist the Contracting Officer during communications and discussions; and review supplemental, revised or final proposal revisions. To the extent possible, the same evaluators shall be available throughout the entire evaluation and selection process to ensure continuity and consistency in the treatment of proposals. The following are examples of circumstances when it would not be necessary for the technical evaluation panel to evaluate revised proposals submitted during the acquisition:

(i) The answers to questions do not have a substantial impact on the proposal.

(ii) Final proposal revisions are not materially different from the original proposals.

(iii) Revisions to the proposals are relatively minor and do not affect the rankings of the offerors.

(2) The Contracting Officer, with the written concurrence of the technical evaluation panel chairperson, may decide not to have the panel evaluate the revised proposals. The Contracting Officer shall fully document such a decision in the contract file.

(3) When the Contracting Officer considers technical evaluation panel meetings necessary, the attendance of evaluators is mandatory. When the chairperson determines that an evaluator's failure to attend the meetings is prejudicial to the evaluation, the chairperson shall remove or replace the individual after discussing the situation with the Contracting Officer and obtaining the Contracting Officer's concurrence and the approval of the official responsible for appointing the panel members.

(4) When continuity of the evaluation process is not possible, and new evaluators are selected or the size of the evaluation panel is reduced, each panel member shall review all proposals at the current stage of the acquisition- i.e., initial proposal, final proposal revisions, etc. Also, the Contracting Officer shall provide guidance concerning what steps to take if an unusually large number of proposals is received, including how to determine what constitutes an unusually large number of proposals.

(F) Use of outside evaluators.

(1) Except when peer review is required by statute as provided in 315.303-70 (a), decisions to disclose proposals to evaluators outside of the Government shall be made by the official responsible for appointing panel members in accordance with OPDIV procedures. The avoidance of organization conflict of interest and competitive relationships must be taken into consideration when making the decision to use outside evaluators.

(2) When a solicited proposal will be disclosed outside the Government for evaluation purposes, the following or similar conditions shall be part of the written agreement with the evaluator(s) prior to disclosure:

Conditions for Evaluating Proposals

The evaluator agrees to use the data (trade secrets, business data, and technical data) contained in the proposal for evaluation purposes only. The foregoing requirement does not apply to data obtained from another source without restriction. Any notice or legend placed on the proposal by either HHS or the submitter of the proposal shall be applied to any reproduction or abstract provided to the evaluator or made by the evaluator. Upon completion of the evaluation, the evaluator shall return to the Government the furnished copy of the proposal or abstract, and all copies thereof, to the HHS office which initially furnished the proposal for evaluation. Unless authorized by the HHS initiating office, the evaluator shall not contact the submitter of the proposal concerning any aspects of its contents. The evaluator's employees and subcontractors shall abide by these conditions.

(iii) Receipt of proposals.

(A) After the closing date for the receipt of proposals set in the solicitation, the Contracting Officer shall forward the technical proposals, by memorandum, to the Project Officer or chairperson for evaluation. The Contracting Officer shall retain the business proposals for evaluation.

(B) The transmittal memorandum shall include at least the following elements:

(1) A list of the names of the organizations submitting proposals.

(2) A reference to the need to preserve the integrity of the source selection process.

(3) A statement that only the Contracting Officer is authorized to conduct discussions.

(4) A requirement for a technical evaluation report in accordance with paragraph (a)(3)(vi) of this section.

(5) The establishment of a date for receipt of the technical evaluation report.

(iv) Convening the technical evaluation panel.

(A) Normally, the technical evaluation panel convenes to evaluate proposals. However, there may be situations when the panel chairperson determines that it is not feasible for the panel to convene. Whenever the panel does not convene, the panel chairperson shall closely monitor the technical review to produce acceptable results.

(B) When a panel convenes, the chairperson shall control the technical proposals provided by the Contracting Officer for use during the evaluation process. The chairperson normally distributes the technical proposals prior to the initial panel meeting and establishes procedures for securing the proposals whenever they are not being evaluated to ensure their confidentiality. After an evaluation is completed, the chairperson shall return all proposals to the Contracting Officer.

(C) The Contracting Officer shall address the initial meeting of the panel and state the basic rules for conducting the evaluation. The Contracting Officer shall provide written guidance to the panel, if the Contracting Officer cannot attend the initial panel meeting. The guidance shall include the following elements:

(1) An explanation of the evaluation process and the role of evaluators throughout the process.

(2) The need for evaluators to read and understand the solicitation, especially the SOW/PWS and evaluation criteria, prior to reading the proposals.

(3) The need for evaluators to restrict the review to only the SOW/PWS, the evaluation criteria, and the contents of the technical proposals.

(4) The need for each evaluator to review all of the proposals.

(5) The need for evaluators to identify ambiguities, inconsistencies, errors, and deficiencies.

(6) The need for the evaluators to provide complete written documentation of the individual strengths and weaknesses for each proposal.

(7) An instruction specifying that, until an award is made, they may not disclose information concerning the acquisition to any person not directly involved in the evaluation process.

(8) An explanation of conflicts of interest.

(v) Rating and ranking of proposals. The evaluators shall individually read each proposal, describe tentative strengths and weaknesses, and independently assign preliminary scores in relation to each evaluation factor set forth in the solicitation. The evaluators may then discuss in detail the individual strengths and weaknesses described by each evaluator and, if possible, arrive at a common understanding of the major strengths and weaknesses and the potential for correcting each offeror's weakness(es). Each evaluator shall assign a final score to each proposal, and the technical evaluation panel shall collectively rank the proposals. Normally, ranking is the result of adding the numerical scores assigned to the evaluation factors and determining the average for each offeror. The evaluators shall then identify whether each proposal is acceptable or unacceptable. The technical evaluation panel shall not employ predetermined cutoff scores.

(vi) Technical evaluation report. The chairperson shall prepare a technical evaluation report and provide it to the Contracting Officer, who shall maintain it as a permanent record in the contract file. The report shall reflect the ranking of the proposals and identify each proposal as acceptable or unacceptable. The report shall also include a narrative evaluation specifying the strengths and weaknesses of each proposal, and any reservations, qualifications, or areas to be addressed that might bear upon the selection of sources for negotiation and award. The report shall include concrete technical reasons supporting any determination of unacceptability of a proposal and, for acceptable proposals, include specific points and questions for discussions or negotiations. The technical evaluation report shall also include a copy of each signed rating sheet, unless the Contracting Officer determines, in accordance with FAR 15.305(a)(3)(ii), and 315.305(a)(3)(vi), that the technical evaluation report includes appropriate and sufficiently detailed supporting narrative (with specific references to particular portions of offerors' proposals) to (1) fully and reasonably explain the basis for the technical evaluation panel's assessments of each proposal, including an evaluation rating of “acceptable” or “unacceptable; and (2) support any recommendation to include or not include a proposal in the competitive range. However, when peer review of proposals is required as provided in 315.303-70(a), OPDIVs shall follow applicable peer review guidelines and practices regarding the submission, maintenance, and disposal of reviewer rating sheets.

[74 FR 62398, Nov. 27, 2009, as amended at 75 FR 21510, Apr. 26, 2010]




Warning: require(/home/simplyauto/www/includes/site_footer.php): failed to open stream: Permission denied in /home/simplyauto/www/regs/fars/section.php on line 347

Fatal error: require(): Failed opening required '../../includes/site_footer.php' (include_path='.:/usr/local/lib/php') in /home/simplyauto/www/regs/fars/section.php on line 347