Step 3 | Acquisition Data Call

In Step 3, the acquisition data call should reach all functional areas that support the specific acquisition (e.g., engineering, software engineering, integrated logistics support activities, configuration management, test and evaluation, product assurance, safety, human engineering, and training). The responses to the acquisition data call are critical and provide the basis for the user’s data requirements, becoming contractual requirements. Those requirements will be consolidated and reviewed at several management levels, any one of which may challenge the need for the data.

Each data call participant should identify the data requirements based on the life cycle phase of the program, purposes of the contract, and life cycle program strategies. Data requirements can be specified using a Data Item Description (DID) and the CDRL. Data call participants should refer to the Statement Of Work (SOW) or Performance Work Statement (PWS) or other requirement documents to determine whether a valid contract requirement supports the proposed data requirement.

Lesson Learned - develop an Integrated Product Team to determine the data needs

Click below to proceed to the next step.

Step 4 | Develop the Draft CDRL