SOWs are generally subject to “contracting” declarations on mandatory compliance (z.B. “This task is carried out in accordance with the Agency`s Xyz Directive, date mm/dd/yyyy). In practice, SOWs can also include references to desired performance results, performance standards and metrics, thus bridging the distinction between SOOs and PWS. Apart from good practice, there are few government guidelines that clearly state how and when SOWs are used in relation to SOOs or PWS. While the FAR PWS defines the definitions in Part 2 and refers to SOOs and PWS in Part 37.6 Performance Based Acquisition, SOWs are not addressed. The work statement must be directly related to the benefits listed in the CDRL form. This is done by reference to the SOW paragraphs that create or use the item, and the SOW text should be clear when discussing a delivery item using the title or sticking the item number (z.B ” [A-001]. When you say that kind of thing, it means that they know it is not really included in the scope of the project, and you have to remind them. Refer to the work instruction and help them understand that what they are asking for was not included. You need to find the balance to ensure that the work statement is quickly signed, while making sure to raise the issues and cover potential problem areas.
For most projects, your work instruction must be made up of two distinct parts. The first section describes general project information (which you can often borrow from a previous project); In the second section, the details of each phase of the project are defined. There is a lot of work, but it`s not necessarily a bad thing, as it will help refine your approach. If you create a work statement, you`ll probably adjust your estimate and timeline if you remember things you`d added but forgotten. The work account is the project contract and sets and sets expectations. It provides general information on high-level projects and defines detailed results, standards, criteria and requirements for each phase.