5. Attachment 5 Step 2 Contractor SOW_PWS Format.pdf

ATTACHMENT 5: STEP 2

STATEMENT OF WORK (SOW) / PERFORMANCE WORK STATEMENT (PWS)

FORMAT

A SOW/PWS must be included with the full proposal as part of the Step 2 submission. The SOW/PWS should not exceed 20 pages in length and must be a separate and distinct document suitable for incorporation into the procurement instrument. DO NOT INCLUDE ANY PROPRIETARY INFORMATION IN THE SOW/PWS. Pages should be numbered, and the initial page should have a date (document current as of date) shown under the title.

The proposed SOW/PWS must accurately describe the work to be performed. The proposed SOW/PWS must also contain a summary description of the technical methodology as well as the task description, but not in so much detail as to make the SOW/PWS inflexible. The SOW/PWS should include the following sections and specifically respond to the Request for Proposal

(RFP):

1.0 OBJECTIVE. This section is intended to give a brief overview of the project and should describe why the work is being pursued and what the Offeror intends to accomplish.

2.0 SCOPE. This section includes a statement of what the SOW/PWS covers. This should describe the capability area (CSO AOI topic) to be investigated, goals, and milestones for the effort. Provide a detailed project schedule that outlines the various phases of work to be accomplished within the proposed period of performance.

3.0 BACKGROUND. The Offeror must identify appropriate documents that are applicable to the effort to be performed. This section includes any information, explanations, or constraints that are necessary to understand the project tasks and requirements. This section should describe the effort’s relationship to previous and ongoing efforts.

4.0 SOLUTION-SPECIFIC OBJECTIVES, TASKS, AND TECHNICAL REQUIREMENTS.

This section contains the detailed description of objectives and tasks that are necessary to perform the proposed work. These objectives/tasks will represent the work to be performed in any potential contract award, and, thus, shall be considered contractually binding. This section should be developed in an orderly progression and presented in sufficient detail to establish the feasibility of accomplishing the overall program goals. This section should clearly distinguish base period tasks from option tasks. The sequence of performance must be presented by fiscal year and task order, as in Section IV of the Technical Proposal. The SOW/PWS must contain every task to be accomplished and expected outcome. Note that the Government reserves the right to modify and negotiate the language in the SOW/PWS prior to any potential contract award.

4.1 Objective and Task descriptions must be definite, realistic, and clearly stated.

4.1.1 Use the phrase “the contractor shall” whenever the work statement expresses a provision that is binding.

4.1.2 Use “should” or “may” whenever it is necessary to express a declaration of purpose.

4.1.3 Use “will” in cases where no Offeror requirement is involved (e.g., power will be supplied by the Government.

4.1.4 Use active voice in describing work to be performed.

4.2 Do not use acronyms or abbreviations without first defining them.

4.2.1 Place abbreviations and acronyms in parentheses following the first usage of the spelled-out phrase.

4.3 If presentations and meetings are identified in the Offeror’s schedule, the Offeror must include the following statement in the SOW/PWS: “Conduct presentations and meetings sat times and places specified in the contract schedule.”

4.4 The desired project structure consists of base period tasks, focused on demonstrating the feasibility of the technology, and option tasks, which cover design, fabrication, testing, and evaluation of the final product. Execution of option tasks will be dependent upon and determined by the contractor’s performance during and the results produced from the base period tasks.