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

STATEMENT  OF  WORK  FORMAT

1   Scope.   Include a statement about what this SOW covers.   Some background information may be helpful to clarify the needs of the procurement.

1.1  Background.  Do not discuss work tasks in Section 1.

2   Applicable Documents.   All documents invoked in the requirements section of the SOW must be listed in this section by document number and title.   These documents may include Standards, Specifications and other reference documents needed to identify and clarify the work task or

deliverable product. However, DoD and Departmental Instructions are provided to control in-house

work effort and should not be used in the SOW to control contractor effort.   Also, any document listed in this section must be invoked and selectively tailored to meet minimal needs of the planned procurement in the requirements section.   The exact version of any document cited in the SOW should be specified in this section.

2.1    Department of Defense specifications.

2.2   Department of Defense standards.

2.3    Other Government documents.

2.4   Industry documents.

3    Requirements.   The arrangement of technical tasks and subtasks within the Requirements section will be dictated by program requirements. If a WBS is being used in the program, tasks should be arranged in accordance with that WBS.   It may be helpful to have a general task to orient the

planning and use of the subsequent subtasks.  The following outline is a generalization.  Care should be

exercised to scope the program tasks to meet only the minimal needs for the phase SOW or requirements.

3.1   General.

3.2   Detail tasks.

3.2.1 System engineering.

a. Technical studies - including life cycle costs.

b. System effectiveness planning, for example, reliability, maintainability, and human factors.

FIGURE 7. SOW format.

24