Statements of work handbook

Front Cover
U.S. National Aeronautics and Space Administration, 1975 - 31 pages
 

What people are saying - Write a review

We haven't found any reviews in the usual places.

Other editions - View all

Common terms and phrases

Popular passages

Page 8 - For every piece of deliverable hardware, for every report, for every immediate action, do not specify that something be done "as necessary". Rather, specify whether the judgment is to be made by the contractor or by the Government. Be aware that these types of contingent actions may have an impact on price as well as schedule. Where expensive services, such as technical liaison, are to be furnished, do not say as required.
Page 8 - ... have an impact on price as well as schedule. Where expensive services, such as technical liaison, are to be furnished, do not say as required. Provide a ceiling on the extent of such services, or work out a procedure (eg, a level of effort, pool of man-hours) that will ensure adequate control.
Page 8 - ... abbreviation or acronym in parentheses following the word or words. • When it is important to define a division of responsibilities between the contractor, other agencies, etc., a separate section of the SOW (in an appropriate location) should be included to delineate such responsibilities. • Include procedures. When immediate decisions cannot be made, it may be possible to include a procedure for making them (eg, "as approved by the contracting officer," or "the contractor shall submit a...
Page 9 - ... may add unnecessary cost. Data requirements are common examples of problems in this area. Screen out unnecessary data requirements and specify only what is essential and when. It is recommended that data requirements be specified separately in a Data Requirements Appendix or equivalent. 8 12.
Page 8 - When immediate decisions cannot be made, it may be possible to include a procedure for making them (eg "as approved by the contracting officer," or "the contractor shall submit a report each time a category B failure occurs"). 9. Do not overspecify. Depending upon the nature of the work and the type of contract the ideal situation may be to specify results required or end items to be delivered and let the contractor propose his best method.
Page 9 - Have headings been checked for format and grammar? Are subheadings comparable? Is the text compatible with the title? Is a multidecimal or alpha-numeric numbering system used in the SOW? Can it be cross-referenced with the CWBS?
Page 9 - Have Part 3, Subpart 5 and other appropriate portions of the NASA Procurement Regulation been followed? 11. Has extraneous material been eliminated? 12. Can SOW task/contract line items and configuration item breakouts at lower levels be identified and defined in sufficient detail so they can be summarized to discreet third level CWBS elements?
Page 9 - When it is necessary to reference other documents, is the proper reference document described? Is it properly cited? Is all of it really pertinent to the task, or should only portions be referenced? Is it cross-referenced to the applicable SOW task element?
Page 7 - He must assure that these schedules are compatible with the schedule for the request for proposal (RFP) issuance. The statement of work should be prepared sufficiently early to permit full project coordination and to ensure that all project requirements are included. It should be completed in advance of RFP preparation. SOW preparation manuals also contain guides for editors and...
Page 8 - Say the contractor shall conduct a test rather than a test should be conducted. In other words, when a firm requirement is intended, use the mandatory term "shall" rather than the permissive term "should".

Bibliographic information