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-1A4.4.6 Data management. Proper tailoring and scheduling <strong>of</strong> training data productsubmission requires particular attention by the SOW preparers. Data costs can be minimized byselectively eliminating unnecessary reports and requiring appropriately phased submissions. Areview <strong>of</strong> anticipated data requirements should there<strong>for</strong>e include definition <strong>of</strong> a time line <strong>for</strong> datasubmission. The contractor’s <strong>for</strong>mat may be acceptable <strong>for</strong> submission <strong>of</strong> data products. TheSOW preparer should make every ef<strong>for</strong>t to ensure that the CDRL(s) and DIDs reflect theminimum data required by the Government.4.4.6.1 Data Item Description (DID). The DID is a completed DD Form 1664 that definesthe data required <strong>of</strong> a contractor. The <strong>for</strong>m specifically defines the content, preparationinstructions, <strong>for</strong>mat, and intended use <strong>of</strong> the data. Data is in<strong>for</strong>mation inherently developedduring completion <strong>of</strong> work tasks in the SOW and required <strong>for</strong> retention. DIDs do not prescribework tasks or per<strong>for</strong>mance methods. After the need <strong>for</strong> delivery <strong>of</strong> data resulting from a worktask has been determined, appropriate DIDs should be selected by the preparer <strong>of</strong> the SOW. TheDoD Acquisition Management Systems and Data Requirements Control List (AMSDL), DoD5010.12-L, lists all published DIDs.4.4.6.2 Data requirements tailoring. Acquisition managers should tailor requirementsspecified in MIL-PRF-29612 and associated DIDs to ensure that unnecessary data is notprocured. This tailoring process should result in a clear understanding by the Government andthe contractor <strong>of</strong> what is required, and the specific measurable criteria by which the data productis to be examined and evaluated. When applying deletion tailoring to DID requirements the<strong>acquisition</strong> manager should delete corresponding MIL-PRF-29612 verification requirementsfrom the RFP.4.4.6.3 Per<strong>for</strong>mance specification tailoring. MIL-PRF-29612, Section 3 containsper<strong>for</strong>mance requirements <strong>for</strong> training data products. Section 4 contains data product verificationcriteria. Both the per<strong>for</strong>mance requirements and verification criteria may be cited in a RFP orcontract. It is not mandatory <strong>for</strong> the specification to be cited in either an RFP or a contract. If itis not cited then data product per<strong>for</strong>mance and verification requirements should be developed andprovided in its place. Specific tailoring <strong>guidance</strong> <strong>for</strong> MIL-PRF-29612 is provided herein (SeeSection 5). The following is provided as general per<strong>for</strong>mance specification tailoring <strong>guidance</strong>:a. In cases where MIL-PRF-29612 is cited, it should be tailored to match the requirements<strong>of</strong> the tailored DID. Once all DIDs have been tailored to the specific requirement, thecorresponding parts <strong>of</strong> MIL-PRF-29612, Sections 3 and 4, should be tailored accordingly.b. MIL-PRF-29612 may be tailored by deletion and the addition <strong>of</strong> verification criteria.c. Specific program unique requirements and verification criteria that are not listed in MIL-PRF-29612 may be needed in some instances. In those instances, the requirements and17

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

Saved successfully!

Ooh no, something went wrong!