10.07.2015 Views

department of defense handbook guidance for acquisition ... - NAVAIR

department of defense handbook guidance for acquisition ... - NAVAIR

department of defense handbook guidance for acquisition ... - NAVAIR

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

MIL-HDBK-29612-1A(1) Develop or identify interested sources.(2) Request preliminary in<strong>for</strong>mation based upon a general description <strong>of</strong> theGovernment's requirements.(3) Explain complex specifications and requirements not easily communicated througha written document.(4) Aid prospective <strong>of</strong>ferors in later submitting responsive proposals without undue use<strong>of</strong> ef<strong>for</strong>t, time and money.c. The <strong>acquisition</strong>/program manager should assist the contracting <strong>of</strong>ficer with the conduct <strong>of</strong>the pre-RFP conference. The manager explains and clarifies Government requirements.The manager should understand the purpose <strong>of</strong> these conferences and recognize when apre-RFP conference would benefit the <strong>acquisition</strong> process.4.7.4 Pre-proposal conference. When a pre-proposal conference is required, the contracting<strong>of</strong>ficer notifies all prospective <strong>of</strong>ferors. The purpose <strong>of</strong> the pre-proposal conference is to discussrequirements with contractors after they study the package. The use <strong>of</strong> pre-proposal conferencesis normally a good strategy. The conference allows you to discuss actual requirements with thecontractors and explain specific proposal package content and <strong>for</strong>mat requirements. It alsoprovides an opportunity to ensure the prospective <strong>of</strong>ferors are aware <strong>of</strong> specific contract clauses.The <strong>acquisition</strong>/program manager should:a. Be prepared to discuss all requirements identified in Section C <strong>of</strong> the RFP package,including; delivery schedules, proposal <strong>for</strong>mats, evaluation factors and criteria, and otherareas. Also be prepared to discuss any RFP Section which is not the specificresponsibility <strong>of</strong> the contracting <strong>of</strong>ficer. It may, there<strong>for</strong>e, be wise to have arepresentative from the technical activity also attend the conference.b. Discuss source selection in<strong>for</strong>mation included in Section M <strong>of</strong> the RFP only in generalterms. Carefully avoid discussing specific values assigned to evaluation factors andsignificant subfactors.4.7.5 Amending the RFP. When the Government changes, relaxes, increases, clarifies orotherwise modifies its requirements, the contracting <strong>of</strong>ficer issues a written amendment to theRFP. The contracting <strong>of</strong>ficer issues amendments using a SF 30, Amendment toSolicitation/Modification <strong>of</strong> Contract. The contracting <strong>of</strong>ficer can issue RFP amendments bothbe<strong>for</strong>e and after receipt <strong>of</strong> proposals.4.8 Proposal evaluation. Evaluate contractor proposals following the procedures in thesource selection plan.4.8.1 Technical evaluation. Technical proposals are evaluated according to the technicalevaluation plan which should be developed as part <strong>of</strong> the source selection plan.27

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!