MIL-HDBK-245D
3.7.1 Use of Contract Data Requirements List (CDRL) Data. The ordering and delivery of data which the Government requires are specified and scheduled through the use of the Contract Data Requirements List (CDRL), DD Form 1423, in conjunction with the appropriate Data Item Description (DID), DD Form 1664. The CDRL is used to order the data required and tailor the DID. The DID's use is to describe the data's format and content requirements. The SOW task(s) that will produce data requirements should be referenced in Block 5 of the CDRL. The SOW author should exercise considerable care and attention to the data delivery implications of the SOW. While data may be inherently generated by a work task, recording and delivering the data in a specific format are cost drivers that must be considered when preparing the SOW and
CDRLs. The CDRL should specify that the contractor's format is acceptable, wherever possible.
3.7.2 Data Item Description (DID). After the need for recording and delivery of data resulting from a work task has been determined, appropriate DIDs should be selected from DoD 5010.12- L, Acquisition Management System and Data Requirements Control List (AMSDL). If certain elements of data are not needed, the DID should be tailored downward noting deletions in CDRL Block 16. When the contractor format for a data product will meet the Government's needs, it should be specified in block 16 of the CDRL if the DID does not already state contractor format is acceptable. The CDRL should only require data specifically generated in a SOW work task. The SOW, and not the DID, must task the contractor to perform work. At the end of each SOW task paragraph, the DIDs that are associated with the effort described in the task may be identified in parentheses.
To understand the relationship of a SOW to the CDRL and DID (see Figure 5), consider the example where the SOW establishes a requirement that, "the contractor shall establish, implement and control a Configuration Management (CM) program". The associated CDRL would order a CM data item and identify due date, distribution and other such parameters while the DID would provide the format and content requirements for that particular CM item, with non-essential references tailored out of the DID.
3.8 SOW Development. Section 4 of this handbook describes how the SOW content may change depending on which acquisition phase it supports. The following paragraphs will describe a general planning and development approach that is applicable to all SOWs regardless of which acquisition phase is to be supported.
3.8.1 Work Breakdown Structure (WBS). A WBS should be used in developing the SOW. MIL- STD-881 may be used for guidance. A WBS provides the framework for a disciplined approach of structuring and defining the total project or program. It is a product-oriented family tree composed of equipment, services, and other items which make up the project or program, and provides the basis for progress reporting, performance and engineering evaluations, and financial data reporting. When preparing the SOW a complete application of a WBS may not be necessary in all programs, however, the underlying philosophy and structured approach can and should be applied. The Contract Line Item Number (CLIN) and the SOW should be constructed to
14
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business