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

4   DETAIL REQUIREMENTS

4.1 SOW Phasing and Results. All  programs, including highly classified programs, should accomplish certain core activities.  These activities must be tailored to satisfy an identified need using common sense and sound business practices.  The acquisition process is structured in logical phases separated by major decision points called milestones.  Each milestone is an opportunity for a review to determine if the program should continue.  The decision to enter the next phase or not is based on results obtained in the acquisition phase preceding that milestone. SOW requirements are tailored to support the acquisition of information, hardware, software, technical data and the logistic support required during any particular life cycle phase.

4.1.1 Determining Mission Needs and Identifying Deficiencies.   All acquisition programs are based on identified, documented, and validated mission needs.  Mission needs result from assessments of current and projected capability requirements.  Mission needs may establish a new operational capability, improve an existing capability, or exploit an opportunity to reduce costs or enhance performance.  If the potential solution results in a new program, an appropriate level review should be held to document its validity and joint potential, and confirm that the requirements have been met or considered.

4.1.1.1 Elements of Information.  Where preliminary studies involving systems analyses, preliminary cost effectiveness, or trade-off studies are to be contracted, there are certain distinctive elements of information to be included in the SOW.  These can be included in either the introduction or background descriptions of the Scope in Section 1.

These areas are as follows:

a. Statement of the problem(s).  A brief description and background of the problem(s) to be solved, and a succinct discussion of the need giving rise to this requirement.

b. System description.  A short functional description of the overall system.  If

practicable, a pictorial representation that will quickly orient the reader to the desired system and the proposed use should be considered for inclusion in this Section of the SOW.

c. Major milestones.  A graphic display of major program milestones should be included in the background information.

4.1.1.2  Requirements. The Section 3 paragraphs will establish what the contractor shall do, and may properly contain discussions of the following requirements and conditions:

a. Component and subsystem relationships.  A functional flow diagram, explaining what is visualized as possible or practical at this time and showing the  system and each associated subsystem (or major component).

20