(c)(6)
(A) Except for acquisitions described in 1815.300-70(b) contracting officers shall issue draft requests for proposals (DRFPs) for all competitive negotiated acquisitions expected to exceed $10,000,000 (including all options or later phases of the same project). DRFPs shall invite comments from potential offerors on all aspects of the draft solicitation, including the requirements, schedules, proposal instructions, and evaluation approaches. Potential offerors should be specifically requested to identify unnecessary or inefficient requirements. If the DRFP contains Government-unique standards, potential offerors should be invited to identify voluntary consensus standards that meet the Government's requirements as alternatives to Government-unique standards cited as requirements, in accordance with
FAR 11.101 and
OMB Circular A-119. Comments should also be requested on any perceived safety, occupational health, security (including information technology security), environmental, export control, and/or other programmatic risk issues associated with performance of the work. When considered appropriate, the statement of work or the specifications may be issued in advance of other solicitation sections.
(B) Contracting officers shall plan the acquisition schedule to include adequate time for issuance of the DRFP, potential offeror review and comment, and NASA evaluation and disposition of the comments.
(C) When issuing DRFPs, potential offerors should be advised that the DRFP is not a solicitation and NASA is not requesting proposals.
(D) Whenever feasible, contracting officers should include a summary of the disposition of significant DRFP comments with the final RFP.
(E) If performance-based payments are planned to be used in a competitive negotiated acquisition, the DRFP shall request potential offerors to suggest terms, including performance events or payment criteria. Contracting officers shall use that information to establish a common set of performance-based payments parameters in the formal RFP when practicable.
(F) The procurement officer may waive the requirement for a DRFP upon written determination that the expected benefits will not be realized given the nature of the supply or service being acquired. The DRFP shall not be waived because of poor or inadequate planning.
(f)
(i) Upon release of the formal RFP, the contracting officer shall direct all personnel associated with the acquisition to refrain from communicating with prospective offerors and to refer all inquiries to the contracting officer or other authorized representative. This procedure is commonly known as a "blackout notice" and shall not be imposed before release of the RFP. The notice may be issued in any format (e.g., letter or electronic) appropriate to the complexity of the acquisition.
(ii) Blackout notices are not intended to terminate all communication with offerors. Contracting officers should continue to provide information as long as it does not create an unfair competitive advantage or reveal proprietary data.
