The content of THE SOOs should be adapted to the type and phase of the programme. The key is to keep the SOO clear and concise, and to provide potential suppliers with enough information and detail to structure a robust program designed to be executable and achieve government objectives. The SOO in the context of tendering or tendering has value for both industry and government. [1] The SOO is a document prepared by the government that sets out the fundamental and overarching objectives of the acquisition. It is provided in the application instead of a written statement of work from the government. In this approach, contractors` proposals include their service descriptions and performance measures and measures (based on proposed solutions). The Statement of Objectives (SOS) identifies the general, fundamental and overall objectives of an acquisition or procurement and is used as a reference tool for the government and the supplier. In a competitive source selection environment, an SOO is an integral part of the streamlined request for proposal development process. An SOO complements a requirements document (CIM, CDD, performance-based government requirements document) and is developed after conducting a risk assessment that highlights the high and moderate risks in the business units, programmatically and technically, identified in the program from the requirements document. [1] The PWS clearly describes the objectives and performance standards expected by the contractor. Completing the requirements roadmap provides the best structure for writing the PWS. The introduction and context provide an opportunity to describe the mission of the organization and how this requirement contributes to the overall success of the mission.

There is no default template or plan for a PWS. The federal procurement regulations only require agencies, as far as possible: an SOO is developed in such a way as to be compatible with; Initial Capabilities Document (CIM); the programmatic direction of the Acquisition Decision Memorandum (ADM), acquisition strategy and acquisition plan; the technical requirements of the system specifications; and the design of the Work Breakdown Structure (WBS) and dictionary. The SOO is then used by the supplier to develop the Contractor`s Statement of Work (CSOW), Contract Work Allocation Structure (CWBS), Integrated Master Schedule (IMS) and other documents that support and define the contractor`s proposed effort. [1] Below are some examples of SOOs related to software that can be used. [1] Watch the video to discuss the key elements of a PWS and SOO. Here are the steps that are integral to SOO development: [1]. There are a number of misconceptions related to SOO, which are discussed below:. .