Attachment 9 - PWS Template.doc

HC1028-10-R-2001

Attachment 9

PERFORMANCE WORK STATEMENT (PWS)

as of dd/mmm/yyyy

(The PWS must have an “as of” date. When a PWS is revised for modifications (after award) each revised PWS will have a new “as of” date.)

(REMEMBER to delete all italicized text, contained within parentheses herein when completing your PWS.

It is shown here for instructional purposes only and must not remain part of the final document.)

1. Contracting Officer Representative (COR) or Task Monitors (TMs). (Identify the individuals who will act as the Primary and Alternate COR or TMs. See the DISA Acquisition Regulation Supplement (DARS( http://www.ditco.disa.mil/hq/aqinfo.asp) 1.602-2-90(a)(S-90)(1) & (2) for definitions of COR and TM).

MANDATORY - ALL REQUESTED INFORMATION MUST BE COMPLETED

a. Primary COR or TM.

Name:

Organization:

Department of Defense Activity Address Code (DODAAC):

(refer to the DODAAC web site at https://dodaac.wpafb.af.mil or https://www.daas.dla.mil/daasinq/dodaac.asp?cu=d for additional information)

Phone Number:

Fax Number:

E-Mail Address:

b. Alternate COR or TM.

Name:

Organization:

Phone Number:

Fax Number:

E-Mail Address:

2. Contract or Task Order Title. (Provide a short, descriptive title of the work to be performed)

3. Background. (Reasons why this effort is required. Describe any parallel efforts to current contracts or any prior contracts, procurements, task orders, other agency activities and/or industry efforts. State if the requested work relates to work already accomplished or ongoing through other vehicles. Note: If an Acquisition Strategy and/or Acquisition Plan has been prepared for this requirement, use the background from those documents, i.e., do not create a new background statement.)

4. Objectives: (Provide a concise overview of the goals and expectations of this contract/TO. This overview must describe how the work to be accomplished in the contract/TO will support the agency’s mission. Describe how the tasks are compliant with any applicable DOD architectures, guidelines, and standards. Note: If an Acquisition Strategy and/or Acquisition Plan has been prepared for this requirement, use the objective from those documents, i.e., do not create a new objective statement.)

5. Scope. (Provide a general description of the work required to accomplish your objectives.)

6. Performance Requirements. (Provide a narrative of the specific performance requirements or tasks that make up the PWS. Number the tasks sequentially, e.g., Task 1 - Title of Task and description, Task 2 - Title of Task and description, etc. Describe in clear terms, using active language, what work will be performed. 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. A PWS must be “outcome-based,” i.e., they must include the development and delivery of actual products (e.g., assessment report, migration strategy, implementation plan, etc.) Agencies also should not include detailed procedures in the PWS that dictate how work is to be accomplished. Instead, they should structure the PWS around the purpose of the work to be performed, i.e., what is to be performed, rather than how to perform it. The services acquired must not fall into the category of ”personal services.” Personal services are those contracted efforts that, by express terms, or as administered, make contractor personnel appear, in effect, as Government employees. See FAR Part 37.102 for a detailed discussion of personal services. Unfunded tasks are not allowed unless the requirement is subject to availability of funds (SAF) or is going to be incrementally funded). Tasks that cannot be pursued either because funding is not currently available or because a decision point will precede initiation of a task must not be included. If it is necessary or desirable to advise the contractor that a potential exists for follow-on work (either through a modification to this contract/TO or through a separate contract/TO), include this information in Paragraph 14, below).

For each requirement, there should be a corresponding standard(s), a statement of the maximum allowable degree of deviation from the standard, the method of surveillance to determine whether the standard is met, and a positive and/or negative incentive based on adherence to the standard.

6.1 Task 1 - Enterprise Management Controls. (Example)

6.1.1 Subtask 1 - Integration Management Control Planning. Provide the technical and functional activities at the required for integration of all tasks specified within this PWS. Include productivity and management methods such as quality assurance, progress/status reporting and program reviews. Provide the centralized administrative, clerical, documentation and related functions.

6.1.2 Subtask 2 - Task Order Management. Prepare a Task Order Management Plan describing the technical approach, organizational resources and management controls to be employed to meet the cost, performance and schedule requirements throughout TO execution. Provide a monthly status report monitoring the quality assurance, progress/status reporting and program reviews applied to the TO.

Deliverables:

Task Order Management Plan (Example) Monthly Status Report

6.2 Task 2. (Description)

6.2.1 Subtask 1. (Description)

6.2.2 Subtask 2. (Description)

Deliverables:

Test Plan (List the deliverables associated with each task.)

Software Release Report

7. Performance Standards. (Performance standards establish the performance levels required by the Government. These standards are driven by the application systems being converted or developed. The agency should ensure that each standard is necessary, carefully chosen and not unduly burdensome. Agencies should identify only those outputs that are essential and should express the outputs in clear, concise, commonly used, easily understood, measurable terms. Agencies should not repeat material in the PWS that is already included in other parts of the contract. Agencies also should not include detailed procedures in the PWS that dictate how work is to be accomplished. Instead, they should structure the PWS around the purpose of the work to be performed, i.e., what is to be performed, rather than how to perform it. For example, instead of requiring that the lawn be mowed weekly, or that trees be pruned each Fall, state that the lawn must be maintained between 2-3” or that tree limbs not touch utility wires or buildings.).

8. Incentives. (Incentives should be used to encourage better quality performance and may be either positive, negative or a combination of both; however, they 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.

The definitions of standard performance, maximum positive and negative performance incentives, and the units of measurement should be established in the solicitation. They will vary from contract to contract and are subject to discussion during a source selection. It is necessary to balance value to the Government and meaningful incentives to the contractor. Incentives should correlate with results. Follow-up is necessary to ensure that desired results are realized, i.e., ensure that incentives actually encourage good performance and discourage unsatisfactory performance.)

9. Place of Performance. (Specify whether the work will be performed at the contractor’s site or at a Government site. Describe any local or long distance travel the contractor will be required to perform. Identify the to/from locations of the trips, number of travelers and number and duration of the trips.).

IMPORTANT NOTE: For internal DISA contract users, you are highly discouraged from specifying that work must be performed within Government facilities, unless absolutely necessary. If work must be performed in Government spaces, a written waiver request must be submitted and approved by MPS7. Contact Ms. Jeanette Boyd for further information regarding waiver format and procedures at (703) 607-4419.

The following paragraph is required when the contractor performs work on-site at a government facility.

Alternate Place of Performance - Contingency Only. Contractor employees may be required to work at home, another approved activity within the local travel area or at the contractor's facility in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, etc.). Any equipment such as laptops or phones provided to Contractor personnel shall be returned at the termination of the engagement or at another time mutually agreeable to both parties. Contracting Officer Representative (COR)/Task Monitor (TM) approval is required. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. To the extent possible, the contractor shall use best efforts to provide the same level of support as stated in the SOW/PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer or the contractor may request an equitable adjustment.

10. Period of Performance. (State in terms of total calendar days after contract/TO award (e.g., 365 calendar days after TO award). The period of performance is limited to the period of time between contract/TO award and the funds expiration date on the funding document. The use of “calendar days” is important because it provides an accurate understanding of the actual length of the contract/TO and allows the actual dates of performance to be set at the time of contract/TO award.). As directed by the TM/COR, the contractor shall continue performance in emergency or mission essential conditions. Additionally, the contractor may be required to account for the whereabouts of their personnel should this information be requested by the TM/COR.

11 Delivery Schedule. (Describe precisely the items to be delivered, both during the period of performance (i.e., relating to the specific tasks described in paragraph 6. above) and at completion of the contract/TO. Describe the schedule either in terms of calendar days from the date of contract/TO Award or in calendar days when other projects or program elements are dependent on the delivery, e.g. “10 calendar days after draft plan approved.” The required table format is as follows:)

Final – 30

(allowable if desired)

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR or TM

Explanation of Terms:

PWS Task# - State the task from Paragraph 6 of the PWS that requires this deliverable.

Deliverable Title - State the title of the deliverable (e.g., Assessment Report, Integration Plan, etc.).

Format - You may either provide Government-specified format or contractor-determined format. It is the customer’s option to either specify an existing Data Item Description (DID) for each deliverable OR allow the contractor to deliver in contractor-determined format. If no DID is specified for a deliverable, that item will be delivered in contractor-determined format. If you require a deliverable format, specify in this column (e.g., “one electronic copy in Microsoft Word 97 and one hard copy”).

Due Date - Self-explanatory (It is NOT allowable to use “as required” as a deliverable due date) .

Frequency & Remarks: For items that have a frequency, state the appropriate frequency (e.g., “monthly on the 10th work day,” etc. It is NOT allowable to use “as required” ).

12. Security. (State whether the work will be UNCLASSIFIED, CONFIDENTIAL, SECRET or TOP SECRET, based on your knowledge of the requirement. Include a Contract Security Classification Specification, DD Form 254, if appropriate. Include the DD Form 254 in Microsoft Word Office 2000 Version or lower, titled DD Form 254.doc, with your requirements package. A Word version of the DD Form 254 can be found on the Ordering Website at Enclosure 13. Processing a DD Form 254 for unique security requirements may extend the timeline to award the TO. REMINDER - the PWS itself must be UNCLASSIFIED.)

13. Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI). (Identify any GFE and/or GFI, and any limitations that will be provided to the contractor. For GFE, provide serial numbers and all identifying information. (Note: If GFE is a sizable list, indicate for example, “50 PC Pentium IVs,” and state that serial numbers will be provided at contract/TO award, along with location and delivery method.) For GFI, list by document number and title, date, etc. Include standards, specifications, and other reference material required to perform the contract/TO. Include any facilities the Government may need to provide to contractor personnel for project performance)

14. Other Pertinent Information or Special Considerations. (Include any special considerations or unique requirements necessary to accomplish the contract/TO (e.g., “specialized experience with UNIX”) and/or any additional information that will be helpful in determining reasonable approaches and cost estimates for the contract/TO. As appropriate, this section needs to contain:)

a. Identification of Possible Follow-on Work. (Any additional work that may result from completion of this contract/TO, which may be added at a later date as a modification, or that may be helpful to the contractor in determining the best overall approach for the contract/TO)

b. Identification of Potential Conflicts of Interest (COI). (Any situation that may influence which contractor should be awarded the contract/TO. FAR Part 9.501 defines “organizational COI” as a situation where because of other relationships or activities a person (company) is unable or potentially unable to render impartial assistance or advice to the Government or cannot objectively perform contract work or has an unfair competitive advantage. FAR 9.502 states that “an organization COI may result when factors create an actual or potential conflict of interest on an instant contract, or when the nature of the work to be performed on the instant contract creates an actual or potential COI on a future acquisition.” An “organizational COI” exists when the nature of the work to be performed may, without some restriction on future activities, (1) result in an unfair competitive advantage to the contractor on other contracts or (2) impair the contractor’s objectivity in performing the contract work. The primary burden is on the contractor to identify any organizational COI, however, the Government has the responsibility to identify and evaluate such conflicts. The KO is charged with avoiding, neutralizing or mitigating such potential conflicts. The customer must make a determination that no COI exist, or identify any potential COI that may exist for the execution of this contract/TO.

c. Identification of Non-Disclosure Requirements. (Your PWS must identify any sensitive or proprietary information to which the contractor will have access during contract/TO execution so the non-disclosure agreements can be signed by the time the contract/TO is awarded.)

d. Packaging, Packing and Shipping Instructions. (Provide any specific requirements.)

e. Inspection and Acceptance Criteria. (Provide any specific requirements.)

15. Section 508 Accessibility Standards. The following Section 508 Accessibility Standard(s) (Technical Standards and Functional Performance Criteria) are applicable (if box is checked) to this acquisition.

Technical Standards

FORMCHECKBOX

1194.21 - Software Applications and Operating Systems

FORMCHECKBOX

1194.22 - Web Based Intranet and Internet Information and Applications

FORMCHECKBOX

1194.23 - Telecommunications Products

FORMCHECKBOX

1194.24 - Video and Multimedia Products

FORMCHECKBOX

1194.25 - Self-Contained, Closed Products

FORMCHECKBOX

1194.26 - Desktop and Portable Computers

FORMCHECKBOX

1194.41 - Information, Documentation and Support

The Technical Standards above facilitate the assurance that the maximum technical standards are provided to the Offerors. Functional Performance Criteria is the minimally acceptable standards to ensure Section 508 compliance. This block is checked to ensure that the minimally acceptable electronic and information technology (E&IT) products are proposed.

Functional Performance Criteria

FORMCHECKBOX

1194.31 - Functional Performance Criteria

PAGE