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

3.8.2  Development Approach.  A systematic process is essential for SOW development.  Select a competent team (expert in managerial, technical and contractual fields) with a team leader who

is experienced in systems acquisition and SOW development.  The SOW preparer and all contract section authors must first understand all program requirements to be supported. Following the systematic process shown on figure 6, the team should:

a.  Ensure that only those tasks which add value to the product, whether a management system or technical requirement, are included in the SOW.  (See DFAR 211.002 policy.)

b.  Conduct market research to determine whether commercial items or nondevelopmental items are available to meet program requirements.

c.  Review the requirements documents which authorize the program and define its basic objectives.

d.  Review the various DoD/Services/Joint Services requirements documents for program management, acquisition and control impact.

e.  Prepare a bibliography citing the specific portions of all applicable governing instructions, directives, specifications, and standards with which the program must comply.  Keep these requirements to the absolute minimum and do not include citings that direct "how" work is to be performed.

f.  Categorize the work described by the program WBS into that which will be done in-house and that which needs to be contracted.

g.  Compile all work that needs to be contracted into an Acquisition Plan (if applicable)

which will identify the various RFPs/contracts required, type of contract, the

time-phasing, estimated cost, method of contractor selection/award, and period of performance among other things.  For each RFP/contract so identified, a SOW  must be prepared covering all of the WBS work elements included in that RFP/contract.

h.  Identify all organizations and persons who will participate in preparing the SOW, and determine the participants' areas of responsibility.

i.  Prepare the SOW following the guidelines of this handbook.  For each WBS work element, identify tasks that define the scope of the work effort to satisfy the minimal needs of the program and identify required data deliverables.

j.  Ensure that the specifications are consistent with the SOW.  Ensure technical performance requirements are properly contained in the system specification and not in the SOW.

17