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

5 STATEMENT OF OBJECTIVES (SOO) METHOD

5.1 SOO Introduction. The SOO is a Government prepared document incorporated into the RFP that states the overall solicitation objectives. It can be used in those solicitations where the intent is to provide the maximum flexibility to each offeror to propose an innovative

development approach. Offerors use the RFP, product performance requirements, and SOO as a basis for preparing their proposals including a SOW and CDRL. Note: The SOO is not retained as a contract compliance item.

5.1.1 SOO Purpose. The program SOO should provide the basic, top level objectives of the acquisition and is provided in the RFP in lieu of a Government written SOW. This approach provides potential offerors the flexibility to develop cost effective solutions and the opportunity to propose innovative alternatives meeting the stated objectives. It also presents the

Government with an opportunity to assess the offeror's understanding of all aspects of the effort to be performed, by eliminating the 'how to' instructions to accomplish the required effort normally contained in the SOW the Government provides to prospective offerors.

5.2 SOO Content. The Government may include a SOO as part of the RFP, listed in Section J, attached at the end of the RFP, or referenced in Section L and/or M, defining the top level program objectives. Alternatively, the SOO may be placed in Section L of the RFP (e.g., as an annex). Figure 8 provides a notional SOO format. It is developed to be compatible with the mission need statement (MNS); operational requirements document (ORD), technical requirements from the system requirements document (SRD)/systems specification; and the draft work breakdown structure (WBS)/dictionary. The SOO should address product oriented goals

rather than performance requirements. SOOs are normally in the 2-4 page range. The SOO is not a one for one replacement of the SOW. Sections L and M should logically follow with instructions to the offerors asking for proposal information supporting the objectives and evaluation criteria that clearly identify how the offerors' responses will be evaluated. Each portion of the RFP must support one another. The key is to keep the SOO clear and concise and to provide potential offerors with enough information and detail to structure a sound program, designed to be executable and satisfy government objectives. The SOO is used, along with other information and instructions in the RFP, by offerors, to develop the contract work breakdown structure, statement of work, and other documents supporting and defining the offerors proposed effort. SOO content depends both on the type of program and on the program phase. It is possible that a 'mature' program, such as one which has been fielded for some time, could require slightly more detail in the SOO to properly integrate with other, ongoing parts of the program.

The SOO is replaced at contract award in the contract by the proposed SOW.