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-1Ac. Cites only the minimal applicable per<strong>for</strong>mance requirements <strong>of</strong> MIL-PRF-29612, inwhole or in part, and is tailored to limit cost drivers. Selectively invokes other documentsonly to the extent required to satisfy the existing requirements.d. Cites verification requirements that the Government will impose on the <strong>of</strong>feror.e. Includes proposal evaluation criteria.4.4.5.3 RFP language. RFP requirements should be written in a language style, clearlyunderstandable to all potential <strong>of</strong>ferors. The writing style should be brief and concise, andsentences should be short. Requirements must be stated explicitly, and should be logical, inchronological order, and avoid using words that allow <strong>for</strong> multiple interpretations.4.4.5.4 Considerations <strong>for</strong> the RFP preparer(s). The <strong>acquisition</strong> manager should <strong>for</strong>m anIntegrated Product Team (IPT) and:a. Select an IPT leader who is experienced in <strong>acquisition</strong> and RFP development. The IPTleader should include as part <strong>of</strong> the team individuals experienced in areas such as<strong>acquisition</strong>, training and contracts. Depending upon the scope <strong>of</strong> the RFP objectives,specific personnel such as Subject Matter Experts (SMEs), engineers, cost analysts, etc.may be assigned to the team.b. Specify that the <strong>of</strong>feror's <strong>for</strong>mat will be acceptable <strong>for</strong> a training data product when<strong>for</strong>mat is not critical to product per<strong>for</strong>mance.c. State requirements in terms <strong>of</strong> training data product per<strong>for</strong>mance requirements instead <strong>of</strong>specifying a process.d. Invoke specifications and standards only when necessary. If invoked, explicitly definethe part, section, or paragraph applicable to the procurement.e. Handbooks, service regulations, and technical orders are not written in language suitable<strong>for</strong> contract application. The RFP should state that these references are provided <strong>for</strong><strong>guidance</strong> only, and not contract compliance.f. Clearly state in the RFP what criteria will be used in evaluating proposals. The writer <strong>of</strong>the RFP must create specific measurable proposal evaluation criteria to fit the training<strong>acquisition</strong>. The criteria should be stated in “Section M -- Evaluation Factors ForAward“ <strong>of</strong> the RFP. Some examples <strong>of</strong> proposal evaluation criteria are as follows:(1) The <strong>of</strong>feror’s proposed approach demonstrates an understanding <strong>of</strong> the scope <strong>of</strong> thespecified requirement.(2) The <strong>of</strong>feror's past per<strong>for</strong>mance demonstrates the capability <strong>for</strong> successfulper<strong>for</strong>mance <strong>of</strong> the specific requirement.(3) The <strong>of</strong>feror’s proposed technical approach demonstrates a plan <strong>for</strong> the re-use <strong>of</strong>existing data.(4) The <strong>of</strong>feror’s proposed technical approach demonstrates an emphasis on reducingcosts and promoting commercial training data products and practices.16

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

Saved successfully!

Ooh no, something went wrong!