MIL-HDBK-245 Preparation Of Statement Of Work SowThis handbook applies to the preparation of Statements of Work SOWs for projects and programs that have deliverables and /or services performed. It is written to implement the acquisition policies established in DODD 5000.1. It covers the preparation of SOWs which correlate to the acquisition such as DoDI 5000.2. This handbook is for SOWs in DoD solicitations and contracts and covers work requirements , in conjunction with applicable performance/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

(The tailoring of reference document requirements should result in a reduction to the overall costs otherwise incurred if all requirements stated in a document are invoked).

e.  Separates general information from direction so that background information and suggested procedures are clearly distinguishable from contractor responsibilities.

f.  Avoids directing how tasks are to be performed and states only what results are required.

3.6.4  SOW Do's and Don'ts. a.  Do's:

·   Select a competent team with an experienced team leader.

·   Exclude "how to" requirements since the offeror should be tasked to provide the deliverables under the contract in the most cost effective manner.

·   Use the program Work Breakdown Structure (WBS), as discussed in paragraph

3.8.1 in this handbook to outline the required work effort.

·   Set SOW objectives in support of the Acquisition Plan (AP), if applicable.

·   Explicitly define the tailored limitations of all standards and specifications cited.

·   Exclude design control or hardware performance parameters because these requirements should be covered in a specification.

·   Educate personnel with respect to acquisition streamlining.  (DFARS 211.002-

70 Contract Clause).

·   Give priority to commercial items over specification items when the former satisfies military requirements.

·   Give priority to commercial practices as a means of acquisition (DFARS 212

Acquisition of Commercial Items - General). b.  Don'ts:

·   Order, describe, or discuss Contract Data Requirements List (CDRL) data.

·   Invoke, cite, or discuss a Data Item Description (DID).  Although the text of the SOW should not include the data format and content preparation instructions

9