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   GENERAL DESCRIPTION

3.1  Purpose.  The SOW should specify in clear, understandable terms the  work to be done in developing or producing the goods to be delivered or services to be performed by a contractor. Preparation of an effective SOW requires both an understanding of the goods or services that are needed to satisfy a particular requirement and an ability to define what is required in specific, performance-based, quantitative terms.  A SOW prepared in explicit terms will enable offerors to clearly understand the government's needs.  This facilitates the preparation of responsive proposals and delivery of the required goods or services.  A well-written SOW also aids the Government in conduct of the source selection and contract administration after award.  A Data Requirements Review Board (DRRB) may review each SOW to ensure compliance with the policy, guidance and procedures contained in this handbook (see DoD 5010.12-M for requirements for conducting the DRRB).  The SOW is aligned with the acquisition milestones and phases discussed in detail in Section 4.

3.2  Relationship between Statement Of Work and Specification.  The SOW defines (either directly or by reference to other documents) all work (non-specification) performance requirements for contractor effort.  Qualitative and quantitative design and performance requirements are contained in specifications developed according to MIL-STD-961.  Such specifications are typically referenced in the SOW, but the specific qualitative or quantitative technical requirements should not be spelled out in the SOW.  For example, the referenced specification may cite reliability and maintainability requirements in terms of quantifiable mean-time-between failures (MTBF) and mean-time-to-repair (MTTR); the SOW should task the contractor to establish, implement and control a reliability and maintainability program.

3.3  Relationship Between the SOW and Contract.  The SOW should be compatible with these provisions:

Requirements that are mandated by law, established DoD policy or necessary for effective management of its acquisition, operation, or support.

At the outset of development, system-level requirements should be specified in terms of mission-performance, operational effectiveness, and operational suitability.

During all acquisition phases, solicitations and contracts, the SOW should state management requirements in terms of results needed rather than "how to manage" procedures for achieving those results.

DFAR 252.211-7000, Acquisition Streamlining, is required in all solicitations and contracts for systems acquisition programs.  This enables a contractor to effectively evaluate and recommend the tailored application of management systems and specifications and standards for use in the appropriate phase of the program life cycle.

4