design requirements contained in specifications, but also data deliverables contained in Contract Data Requirements Lists CDRLs. The Federal Acquisition Regulations FAR and Defense Federal Acquisition Regulation Supplements DFARS discuss the essentiality of the SOW for sound contracting. Ab offeror submits a proposal based on his perception of the Governments needs as defined in the RFP.

Pages 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16 - 17 - 18 - 19 - 20 - 21 - 22 - 23 - 24 - 25 - 26 - 27 - 28 - 29 - 30 - 31 - 32 - 33 - 34 - 35 - 36 - 37 - 38 - 39 - 40 - 41 - 42 - 43 - 44 - 45 - 46 - 47 - 48 - 49 - 50 - 51 - 52 - 53

MIL-HDBK-245D

k. Utilize the SOW and WBS in preparing the corresponding CDRL, Section L Instructions to Offerors, Section M Evaluation Factors for Award, and other parts of the RFP/contract following DFARS.

3.8.3 Non-Complex SOW Development. It is essential to establish a SOW outline for non-complex acquisitions which do not lend themselves to utilization of a WBS.

a. Define end items (line items) to be acquired, such as hardware, software, engineering analysis, software validation or simulation, etc.

b. Establish the requirements which apply to each end item and, as a minimum, develop a bibliography as described in 3.8.2.e above.

c. Determine what services or data will be needed to support each end item after delivery to the Government.

d. Identify all participants (see 3.8.2.h)

e. Prepare the SOW following the guidelines of this handbook.