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

validate the manufacturing or production process; and to demonstrate system capabilities through testing.

4.1.4.1 Detailed Requirements. The Engineering and Manufacturing Development phase SOW efforts include verification that adequate resources have been programmed to support production, deployment, and logistics support of the operational system; verification of the system's

software design, coding, integration and tests.

4.1.5 Phase III: Production, Deployment, and Operational Support. In the Production, Deployment, and Operational Support Phase, the system developed in the previous phases is produced and installed and any support required for operational use is provided. All tasks which were deferred until the Production Phase are addressed and action is initiated for their

completion. These include efforts deferred in support areas such as, supply support (provisioning), technical publications and training. Systems engineering management will ensure on a continuing basis that the design is feasible and sound. Additionally, they will initiate, evaluate and integrate engineering changes throughout the Production Phase to provide the capability for continued support after the system is deployed. The evaluation of system Engineering Change Proposals (ECPs) and value engineering changes, and the preparation for turnover of system operation to the using service are important tasks to be accomplished during this phase. The need for continued system effectiveness and product assurance work as well as CM work will be based on the impact of engineering changes. Operation and Maintenance manuals, and supply support documents, are updated during this Phase and the finished system is tested and approved for DoD use.

4.1.5.1 Product Specifications. The product specification is the primary procurement control document used during the production phase to determine the product baseline, control design, and establish system performance. The content of the specifications is limited to requirements intended to control design and establish performance requirement of the purchased product. The SOW should not conflict with the product specification. Typical SOW requirements which should be tailored to the minimal Production Phase needs are: ILS, CM, technical manuals and publications, training, quality program requirements, calibration and instrumentation, reliability, maintainability, human factors, safety, Planned Maintenance Subsystem (PMS) and other contractor provided services needed in conjunction with the production buy. Many of these

areas have already been addressed during the development phases and should now be well defined and documented. Some SOW tasks are no longer required, while others require continued effort

or the introduction of new tasks compatible with the Production Phase.

4.1.6 Examples. Figure 7 provides a standard SOW format, and Appendix D illustrates an example of SOWs for both products and services. The example SOWs are intentionally incomplete in the interest of brevity.

4.2 Services (Non-personal). The product of a non-personal services SOW (Appendix D2) is the result of some work task being performed. The requirements that establish the work must be