The jobs statement ( SoW ) is a document that is routinely used in the project management field. It defines project-specific activities, deliverables and timelines for vendors providing services to clients. SOW usually also includes detailed terms and prices, with standard terms and conditions of governance and governance. Often an important accompaniment to major service agreements or request proposals (RFPs).
Video Statement of work
Overview
Many formats and styles of templates of Working Statement documents have been devoted to hardware or software solutions described in Request for Proposals. Many companies create their own specialized SOW versions that are specialized or general to accommodate the general requests and proposals they receive.
Note that in many cases, the Employment Statement is a binding contract. The Master Service Agreement or the Consultant/Training Agreement shall postpone certain specific contractual components of work covered in the individual Employment Statement. The Main Service Agreement serves as a master contract that governs the provisions of multiple SOW potentials. Sometimes it refers to the Scope of work.
Maps Statement of work
The addressed area
A statement of work usually addresses these subjects.
- Goal : Why are we doing this project? The destination statement tries to answer this.
- Work Scope : This describes the work to be performed and determines the hardware and software involved.
- Work Location: This explains where work should be done, including the location of hardware and software and where people will meet to do the work.
- Performance Period : This specifies the time allowed for the project, such as start and end times, billable hours per week or month, where work is to be done and anything else related to scheduling.
- Deliverable Schedule : This section lists and explains what should and when.
- Applicable Standards : This describes any industry-specific standards that must be followed in fulfilling the contract.
- Acceptance Criteria : This determines how buyers or recipients of goods will determine whether a product or service is acceptable, usually with objective criteria. View Acceptance Test.
- Special Requirements : This specifies any specific hardware or software, specific labor requirements, such as a degree or certification for personnel, travel requirements, and anything else not covered by the contract specification.
- Contract Type/Payment Schedule : Project acceptance will depend on whether the available budget will be sufficient to cover the required work. Therefore, the decomposition of payments by whether they are advance or staged will usually be negotiated in the early stages.
- Miscellaneous : Many items that are not part of the main negotiations may be listed as important for the project, and ignoring or forgetting them may pose problems for the project.
United States government contract
For US government service contracts, the use of SOW remains strong, although the Statement of Objectives (SOOs) and Performance Work Statements (PWSs) have become increasingly popular due to their emphasis on performance-based concepts such as desired service outcomes and performance standards. SOW is usually used when tasks are known and can be explained in certain terms. They may be preferred when the government does not want an innovative approach or assume any irregularities in the contractor to process a risk. SOO establishes high-level results and objectives for performance and PWS emphasizes results, desired results, and objectives at a more detailed and measurable level, while the SOW provides explicit statements of the work directions for contractors or offerors to follow.
TABLES are usually full of "contractors should be" mandatory compliance statements (eg, "This task should be done in accordance with Agency xyz Directive, dated mm/dd/yyyy"). In practice, SOW can also be found containing references to desired performance results, performance standards, and metrics, thus obscuring their differences between SOO and PWS. In addition to good practice, there are few government policy guidelines that explicitly regulate how and when to use SOW versus SOO or PWS. While the FAR defines PWS in Section 2 Definitions, and the SOO and PWS references in Section 37.6 Performance-Based Acquisitions, SOW is not discussed.
TOW is usually contained in government requests (RFP or RFQ) and brought forward, as may be negotiated with the offeror, into the final contract. In federal applications and contracts, SOW is incorporated into Section C "Description/Specification" of the Uniform Contract Format, but may also be included as an appendix in Section J. In task orders, SOW may only be included between the terms and conditions of the order itself. SOW is often equipped with technical reference documents and attachments. In developing SOW, it is important to ensure that the employment statement is comprehensive and detailed enough, but the statement does not duplicate other terms and conditions or other provisions elsewhere in the solicitation or contract.
The guidelines at MIL-STD-881 and MIL-HDBK-245 say that the Work Damage Structure should be used in developing SOW. It may use WBS as an outline, where each WBS element (in the same name and numbering) is a sub-section of the SOW 3 section, makes development easier and to improve billing and later tracking. The WBS focuses on intelligently dividing a hierarchy of work elements and defining them then having SOW in suitable sections focusing on describing what to do with that part or how it will be done.
The Employment Statement must be directly related to the items indicated in the CDRL form. This is done by entering each CDRL entry including a reference to the SOW paragraph that generates or uses the item, and the SOW text must be clear where it discusses the sending by using the title or parenthesis of the item number (for example, "[A-001]").
See also
- List of Contract Data Terms (CDRL)
Notes and references
External links
- MIL-STD-881 Work Breakdown Structures for Defense Materiel Items series, the 2.4 link to WBS and IMP/IMS
- MIL-HDBK-245 series Handbook for Preparation of Working Statement (SOW), para 3.6.4, 3.8.1
- DI-MGMT-81606 Item Description Data Specifies the content and structure of SOW when the contractor provides it.
- Employment Statement Writing Guide - A personal guide to developing an RFP Working Statement
- How to write a Working Statement
- Fifty Tips for Your Job Statement, National Contract Management Association
- DPAP: Working Statement
- AcqNotes: Working Statement (SOW)
Source of the article : Wikipedia
0 Comments