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

1.0   Program Objectives

(a)  multi-phased program

(b)  one program, multi-contractor

(c)  one phase contract

2.0   Contract Objectives (WBS 00000)

(a)  Objectives in paragraph 2.0 are traceable to Level 0 WBS

(b)  For multi-phase programs, describe objectives for each phase in

a format similar to an indentured list (clearly indicate which phases are part of the anticipated contract and any phases that will involve separate contracts).

Note:  The SOO should not address each WBS element, but each WBS element should be traceable to something in the SOO.  For example, a SOO may instruct the bidder to address his engineering approach.  That is not a particular WBS element, but several WBS elements might be created to breakout the engineering tasks.  Generally, a broad and sweeping objective statement will trace to more WBS elements than would be the case for a very narrowly focused objective statement.

FIGURE 8.  Notional Statement of objectives (SOO) format.

5.3  SOO Development Approach.  A systematic process is essential for SOO development. The following steps are an integral part of that process:

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

b.  Review the requirement documents which authorize the program and define its basic objectives.  Complete a risk assessment and expound the basic objectives of the program to incorporate the major technical and programmatic risks.

c.  Review the various DoD/services/joint services requirements documents for program management, acquisition and control impact.

28