1、c _. - MIL-HDBK-245D 9999970 0230725 841 NOT MEASIREMEbT I SENSITIE MIL-HDBK-2JSD 3 APRIL 1996 SUPERSEDING 10 SEP 1991 MIL-HDBK-24SC DEPARTMENT OF DEFENSE HANDBOOK FOR PREPARATION OF STATEMENT OF WORK (SOW) This handbook is for guidance only. Do not cite this document as a requirement. AMSC NIA AREA
2、 MISC USTRIBUTION STATWENT A. Approved for public release; distribution is unlimited. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-245D 9999970 O230726 788 W MIL-HDBK-245D FOREU-ORD 1. This handbook is appro.ed for use by all Departments
3、and Agencies of the Department of Defense. 2. This handbook is for guidance only and cannot be cited as a requirement in any DoD contract. Contractors mal at their option. utilize this document for guidance in preparing responses to Government requests for proposals. 3. This handbook provides guidan
4、ce to enable personnel to create a completed contract Statement Of Work (Sob) applicable to any material acquisition life-cycle phase. It also covers the SOW preparation for non-personal semices contracts. 4. Modem M-eapon systems have traditionally contained many more specifications and greater det
5、ailed SOWs than those of the past. Contrast the Army Signal Corps SOU for the Wright Brothers heavier-than-air flying machine in 1908 to the Air Force SO for the Advanced Tactical Fighter in 1986. Requirements in the 1908 SOW (e.g be easily taken apart for transport in Army wagons and be capable of
6、being reassembled for operation in an hour. carry 350 pounds for 125 miles. and maintain 40 miles per hours in still air) and other contract conditions were specified on one pape. The requirements section in the 1986 SOW for the Air Force Advanced Tactical Fighter is 85 pages long with 300 paragraph
7、s of requirements. Todays SOWs are much more complex requiring greater attention to detail. 5. The handbook is organized so that the SOW writer after reviewing Section 3. General Description, can proceed to that portion of Section 4, Detailed Requirements. that pertains to the type of SOW required.
8、Each portion of Section 4 has detailed instructions on the specific requirements for each type of SOW tailored to specific needs. The specific instructions provide techniques for defining task elements, and a method for organizing these e!ements into a comprehensive SOW. Sample outlines and signific
9、ant DOS and DONTS are provided. 6. The tendency of SOW writers is to include requirements which belong in other parts of a government contract. Contract requirements should be specified in Sections A - M and should not be restated in other parts of the contract. Quantitative technical requirements s
10、hould be specified in the specification and not be restated in other parts of the contract. Work requirements should be specified in the SOW, and all data requirements for delivery, format. and content should be in the Contract Data Requirements List (CDRL) in conjunction with the appropriate Data I
11、tem Description (DID) respectively, with none of the requirements restated in other parts of the contract. Redundancy invites conflict. 7. This handbook provides guidance, following DoD direction, that will enable SOW writers to rely on commercial contracting practices. The new SOW will specify what
12、 tasks need to be accomplished but leave “how to“ accomplish those tasks up to the contractor. * 8. Beneficial comments (recommendations. additions, deletions) and any pertinent data which may be of use in improving this document should be addressed to: Commander. Space and Provided by IHSNot for Re
13、saleNo reproduction or networking permitted without license from IHS-,-,- MIL-HDBK-245D = 9999970 0230727 h14 hlIL-HDBK-245D Na-al U,*arfare Systems Command. Atm.: SP.4WAR 05L1. 245 1 Cr,stal Dri1.e. .4rlingnn. V.4 22245-5200 b) using the Standardization Document Improvement Proposal (DoD Form 1326)
14、 appearing at the end of this Handbook. . 111 . Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-245D = 9999970 0230728 550 M MIL-HDBK-245D CONTENTS SectionRara. 1 1.1 1.2 1.3 2 2.1 2.2 2.2.1 2.3 3 3.1 3.2 3.3 3.4 3.5 3.6 3.6.1 3.6.2 3.6.3 3.
15、6.4 3.6.5 3.6.6 3.6.7 3.7 3.7.1 3.7.2 3.8 .3.8.1 3.8.2 3.8.3 4 4.1 4.1.1 SCOPE Background Importance of SO Introduction of Statement of Objectives (SOO) APPLICABLE DOCUMENTS General Government Documents Specifications. standards. and handbooks Other Government Documents, Drawings and Publications GE
16、NERAL DESCRIPTION Purpose Relationship between Statement Of Work and Specification Relationship Between the SOW and Contract SOW and Contractor Performance Relationship of Contract Sections Standard Format SOW Section 1 - Scope SOW Section 2 - Applicable Documents SOW Section 3 - Requirements SOW Do
17、s and Donts Title Page and Table of Contents Paragraph Numbering and Identification Language Style Data Management Use of Contract Data Requirements List (CDRL) Data Data Item Description (DID) SOW Development Work Breakdown Structure (WBS) Development Approach Non-Complex SOW Development DETAIL REQ
18、UIREMENTS SOW Phasing and Results Determining Mission Needs and Identifying Deficiencies 4.1.1.1 Elements of Information 4.1.1.2 Requirements 4.1.2 Phase O: Concept Exploration 4.1.2.1 Detailed Requirements 4.1.3 Phase I: Program Definition and Risk Reduction 4.1.3.1 Detailed Requirements 4.1.4 Phas
19、e II: Engineering and Manufacturing Development 4.1.4.1 Detailed Requirements iv Page 1 1 1 1 2 2 2 2 4 4 4 4 4 5 7 7 8 8 9 10 10 13 13 13 14 14 14 16 18 19 19 19 19 19 20 20 20 20 20 21 3 - Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-A 1 MIL-HDB
20、K-245D 9999970 0210729 497 = 4.1.5 Phase III: Production. Deplo!rment. and Operational Support 4.1.5.1 Product Specifications 4.1.6 Examples 4.2 Services (?ion-personal) 4.2.1 Product Definition 4.2.2 Terminolog. 4.2.3 Word Usage 5 STATEMENT OF OBJECTIVES (SOO) METHOD 5.1 SOO Introduction 5.1.1 SOO
21、PLrpose 5.2 SOO Content 5.3 SOO Development Approach 5.4 SOO-RFP Relationships 6 NOTES 6.1 Subject term (key word) listing 6.2 Changes APPENDIX A APPENDIX B APPENDIX C APPENDIX Dl APPENDIX D:! APPENDIX E Figure 1. Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 from previous issue APP
22、ENDICES ACRONYMS WORK WORDS/PRODUCT WORDS PHRASES HAVING MULTIPLE MEANINGS EXAMPLE SOW FOR PRODUCTS EXAMPLE SOU FOR SERVICES EXAMPLE SOO FIGURES Relationship of Government solicitation/contract sections to SOb/SOO Cross reference matrix Sample Title Page Sample Table of Contents SPEC-SOW-CDFX-DID Re
23、lationship Systematic approach to SOW preparation SOW format Notional Statement of objectives (SOO) format 21 31 31 21 23 23 24 25 25 25 25 26 27 29 29 29 30 31 34 37 40 42 6 7 11 12 15 17 22 26 V Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- MIL-
24、HDBK-245D m 9999970 0210730 109 m R.IIL-HDBK-745D 1 SCOPE 1.1 Background. This handbook applies to the preparation of Statements of Mork (S01.s) for projects and programs that ha1.e deli.erables and/or sen,ices performed. It is +ritten to implement the acquisition policies established in DoDD 5000.1
25、. It co.ers the preparation of SOWs which correlate to the acquisition life cycle phases identified in Department of Defense (DoD) Acquisition Instructions such as DoDI 5000.2. This handbook is for SOWs in DoD solicitations and contracts and covers work requirements. in conjunction vith applicable p
26、erfonnance/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 essentialit!. of the SOW for sound contra
27、cting. An offeror submits a proposal based on his perception of the Governments needs as defined in the RFP. Precisely stated requirements will enable the offeror and the Go#ernment to negotiate a fair price for the deliverables and/or services to be provided. This handbook has been developed as a f
28、ramework to assist the responsible manager in propiding a consistent. orderly. and complete description of work required. 1.2 hportance of SO. The majority of government contracts include a SOW which forms the basis for successful performance by the contractor and effective administration of the con
29、tract by the government. A well-written SOU enhances the opportunity for all potential offerors to compete equally for Government contracts and serves as the standard for determining if the contractor meets the stated performance requirements. 1.3 btroduction of Statement of Objectives CSOO). This d
30、ocument introduces a new concept called the SOO which shifts the responsibility for preparing the SOW from the government to the solicitation respondents. Following recent DoD direction to lower Government costs by encouraging innovative contract options and flexible design solutions. the SOO captur
31、es the top level objectives of a solicitation and allows the offerors complete freedom in the structure and definition of SOW tasks as they apply to the proposed approach. However. the requirement. content and purpose of the SOW in the contract remain unchanged. The SOO concept is explained in detai
32、l in Section 5. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-245D 9999970 0230733 045 M MIL-HDBK-235D 2 APPLICABLE DOCLTMENTS 2.1 General. The documents listed below are not necessarily all of the documents referenced herein. but are the
33、ones that are needed in order to fully understand the information proi*ided b!. this handbook. 2.2 Government documents, 2.2.1 SDecifications. standards. and handbooks. The following specifications. standards. and handbooks form a part of this document to the extent specified herein. Unless othewise
34、 specified: the issues of these documents are those listed in the latest issue of the Department of Defense Index of Specifications and Standards (DoDISS) and supplement thereto. STANDARDS DEPARTMENT OF DEFENSE MIL-STD-88 1 Work Breakdown Structures for Defense Material Items Defense Specifications
35、MIL-STD-961 Department of Defense Standard Practice for HANDBOOKS DEPARTMENT OF DEFENSE MIL-HDBK-248 Acquisition Streamlining 2.3 Qther Government Documents. Drawings and Publlcatlons . The following Government documents. drawings. and publications form a part of this handbook to the extent specifie
36、d herein: REGULATION FEDERAL ACQUISITION REGULATION FAR 52.215-33 Order of Precedence DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENTS DFARS 2 1 1 Describing Agency Needs DFARS 212 Acquisition of Commercial Items - General DFARS 227.71 Rights in Technical Data DFARS 237.1 O4 Personal Services Cont
37、racts DFARS 252.2 1 1-7000 Acquisition Streamlining 2 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-2Q5D m 9999970 0220732 T81 hlIL-HDBK-245D DEPARTMEKT OF DEFENSE DoD SO1 O. 12-L Acquisition Management Slstem and Data Requirements Control
38、 List (AMSDL) of Technical Data DoD 501 O. 12“ Procedures for the Acquisition and Management DIRECTIVES DEPARTMENT OF DEFENSE DoDD 5000.1 Defense Acquisition DoDI 5000.2 Defense Acquisition Management Policies and Procedures DEPARThlENT OF DEFENSE DD Form 1323 Contract Data Requirements List (CDRL)
39、DD Form 1664 Data Item Description (DID) (Unless otherwise indicated. copies of the above specifications. standards. handbooks. or publications are ajsailable from the Standardization Document Order Desk. 700 Robbins .4venue, Building 4D. Philadelphia. PA 19 1 1 1-5094. Any documents required by man
40、ufacturers in connection with specific acquisition functions should be obtained from the contracting activity or as directed by the contracting officer.) Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-245D M 9999970 0230733 938 M MIL-HDBK-2
41、45D 3 GENERAL DESCRIPTlOV 3.1 Purpose. The SOl should specify in clear. understandable terms the work to be done in developing or producing the goods to be delivered or senices to be performed by a contractor. Preparation of an effective SOW requires both an understanding of the goods or senices tha
42、t are needed to satisfi 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 governments needs. This facilitates the preparation of responsive proposals a
43、nd delivery of the required goods or services. A well-uritten SOW also aids the Government in conduct of the source selection and contract administration after award. A Data Requirements Review Board (Dm) may review each SOW to ensure compliance with the policy. guidance and procedures contained in
44、this handbook (see DoD 501 O. 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 Relatiohp between Statement Of Work and Specificath. The SOW defines (either directly or by reference to other documents)
45、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 q
46、uantitative 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 es
47、tablish, implement and control a reliability and maintainability program. 3.3 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 suppor
48、t. 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
49、rather than “how to manage“ procedures for achieving those results. DFAR 252.21 1-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
