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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

MIL-HDBK-29612-1A4.8.2 Cost evaluation. The contracting <strong>of</strong>ficer ensures cost evaluation is per<strong>for</strong>med. Thecost evaluation is usually per<strong>for</strong>med by a trained cost analyst. The cost evaluation will addresslife cycle costs, cost realism and, when appropriate, "should cost" analysis. The technicalevaluation team should not have access to cost data prior to conducting the technical evaluation.This in<strong>for</strong>mation could influence a team member’s objectivity.4.8.3 Correction <strong>of</strong> minor proposal errors. Proposals which are basically sound but havesome minor technical or cost errors do not need to be eliminated. Provide contractors theopportunity to correct minor proposal errors when the proposal is otherwise competitive.4.8.4 Evaluation reports. Evaluation reports are generated as a result <strong>of</strong> the technical andcost evaluations. The evaluation reports are key documents in the final source selection andcontract award. It is critical, there<strong>for</strong>e that they be clear, concise, and objective.4.9 Source selection and contract award. The contracting <strong>of</strong>ficer reviews the evaluationreports, and starts the final source selection and contract award process. The contracting <strong>of</strong>ficerdetermines which <strong>of</strong>ferors are in the competitive range based upon the results <strong>of</strong> the technicaland cost evaluations. Based upon evaluation <strong>of</strong> the remaining competitive <strong>of</strong>ferors, the sourceselection authority selects the successful contractor.4.10 Types <strong>of</strong> contracts. The <strong>acquisition</strong>/program manager should know the different types<strong>of</strong> contracts available to use in training <strong>acquisition</strong>s and basic differences between them. Theprogram manager should work closely with the contracting <strong>of</strong>ficer to determine the type <strong>of</strong>contract most appropriate <strong>for</strong> a particular <strong>acquisition</strong>.5. DETAILED RFP GUIDANCE FOR TRAINING DATA PRODUCT REQUIREMENTS5.1 Detailed <strong>guidance</strong>. This section provides in<strong>for</strong>mation and suggested <strong>guidance</strong> <strong>for</strong>training data products to be used in the preparation <strong>of</strong> RFPs. The <strong>guidance</strong> contained in thissection includes the application, tailoring, and interfaces among MIL-PRF-29612 and relatedDIDs, and an RFP. See Appendix A <strong>for</strong> a cross-reference listing that provides the relationshipsamong the DIDs, specification and <strong>handbook</strong> paragraphs. In<strong>for</strong>mation and <strong>guidance</strong> contained inthis section covers all training data products, page-based as well as standard digital data. (See,5.2 through 5.2.4) <strong>for</strong> additional <strong>guidance</strong> specifically concerning tailoring <strong>of</strong> standard digitaldata training data product requirements. Depending on the scope <strong>of</strong> the procurement and dataproduct requirements, the <strong>guidance</strong> contained in this section should be selectively applied.Tailoring <strong>guidance</strong> <strong>for</strong> specific training data products is as follows:5.1.1 Training situation document. The purpose <strong>of</strong> the training situation document is toprovide in<strong>for</strong>mation concerning the efficiency and effectiveness <strong>of</strong> a training system to meet28

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

Saved successfully!

Ooh no, something went wrong!