DOC

Example FORMAT FOR PERFORMANCE WORK STATEMENT (PWS)

By Virginia Morris,2014-06-18 09:38
10 views 0
Example FORMAT FOR PERFORMANCE WORK STATEMENT (PWS)

    Example FORMAT FOR PERFORMANCE WORK STATEMENT (PWS)

    1. PROJECT TITLE: Provide a short, descriptive title of the work to be performed.

    2. BACKGROUND: Describe the need for the services, the current environment, and the office’s mission as it relates to this requirement. Provide a brief

    description/summary of the services sought.

3. SCOPE: Indicate which ITES-2S contract task area(s) apply to the work to be

    performed. Include a high- level view of the procurement, its objectives, size, and

    projected outcomes. Do not include anything that won’t contribute to the

    expected result. Do include impacts/implications.

4. APPLICABLE DOCUMENTS: List legal, regulatory, policy, security, etc.

    documents that are relevant. Include publication number, title, version, date,

    where the document can be obtained, etc. If only portions of documents apply, so

    state.

5. PERFORMANCE REQUIREMENTS: Provide a narrative of the specific

    performance requirements or tasks that make up the PWS. Describe the work in

    terms of the required output, i.e., what is expected from the contractor, rather

    than how the work is to be accomplished or the number of hours to be provided.

    Number the tasks sequentially, e.g., Task 1 - Title of Task and description, Task

    2 - Title of Task and description, etc. The requirement must be defined

    sufficiently for the contractor to submit a realistic proposal and for the

    Government to negotiate a meaningful price or estimated cost.

6. PERFORMANCE STANDARDS: Performance standards establish the

    performance levels required by the Government. Examples of performance

    standards:

Quality Standards: Condition, Error rates, Accuracy, Form/Function, Reliability,

    Maintainability

    Quantity Standards: Capacity, Output, Volume, Amount

    Timeliness Standards: Response times, Delivery, Completion times, Milestones

    7. INCENTIVES: Incentives should be used when they will encourage better quality performance. They may be either positive, negative or a combination of

    both. Incentives may be monetary or non-monetary. Incentives do not need to be

    present in every performance-based contract as an additional fee structure. In a

    fixed price contract, the incentives would be embodied in the pricing and the

    contractor could either maximize profit through effective performance or have

    payments reduced because of failure to meet the performance standard.

    Positive Incentives - Actions to take if the work exceeds the standards.

    Standards should be challenging, yet reasonably attainable.

Negative Incentives - Actions to take if work does not meet standards.

8. DELIVERABLES AND DELIVERY SCHEDULE: List all outputs/outcomes with

    specific due dates or time frames. Include media type, quantity, and delivery

    point(s). State due dates in terms of calendar days after task order award.

9. GOVERNMENT-FURNISHED EQUIPMENT AND INFORMATION (GFE/GFI):

    Identify the Government-furnished equipment and information, if any, to be

    provided to the contractor, and identify any limitations on use. Be as specific as

    possible.

    10. PLACE OF PERFORMANCE: Specify whether the work will be performed at the contractor’s site or at a Government site, with exact address if possible.

    Describe any local or long distance travel the contractor will be required to

    perform.

    11. PERIOD OF PERFORMANCE: State in terms of total calendar days after TO award (e.g., 365 calendar days after TO award), or in terms of start and end date

    (e.g., October 1, 20XX through September 30, 20XX).

12. SECURITY: State whether the work will be UNCLASSIFIED,

    CONFIDENTIAL, SECRET TOP SECRET or TOP SECRET SCI. and include

    Contract Security Classification Specification, DD Form 254, as required in

    individual TOs. ITES-2S Contract Section H.8 requires that the level

    of classified access be incorporated into individual TOs as necessary.

13. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP): This portion of

    the PWS explains to the contractor what the Government’s expectations are, how

    (and how often) deliverables or services will be monitored and evaluated, and

    incentives that encourage the contractor to exceed the performance standards

    and that reduce payment or impose other negative incentives when the

    outputs/outcomes are below the performance standards. Attach the QASP to the

    PWS. An example is provided on the next page.

Report this document

For any questions or suggestions please email
cust-service@docsford.com