FA8051-22-S-0001 Appendix A.docx

PERFORMANCE WORK STATEMENT (PWS)

TEMPLATE

FA8051-22-S-0001 Appendix A.

To assist the Government in the preparation of the contractual Performance Work Statement (PWS) potential offerors are required to submit a proposed PWS which accurately describes the work to be performed, is enforceable and void of inconsistencies, but is not in so much detail as to make the PWS inflexible. A sample template has been drafted below:

I. PERFORMANCE WORK STATEMENT FOR (INSERT TITLE OF PROPOSAL)

II. TABLE OF CONTENTS

1.0 OBJECTIVE. The objective of this effort is to…

- Objective is a brief overview

- Description of why this is being procured

- What are you trying to accomplish

2.0 SCOPE. The scope of this effort is to…

- Scope is an overall concise picture of the required work to be accomplished and the desired end result. The scope puts a framework around the work contemplated by the parties as a means to determine whether future work must be competed.

- Outlines the various major requirements of the effort. For example, “Design, develop, implement, test and deliver” or “Study, analyze, determine and document in a final report”

- Must be consistent with Section 4.0 of the PWS.

3.0 BACKGROUND.

- Background includes information, explanations or constraints

- Who, what, where, when and why this effort is needed

- Helps all readers understand the need for this effort

- Can include applicable documents (which must be included in Section 4.0) and reference documents

4.0 TECHNICAL REQUIREMENTS. The Contractor shall accomplish the following:

- Defines the work to be accomplished

- Should reflect what is to be accomplished/researched/tested by the Contractor

SAMPLE LANGUAGE FOR PWS SECTION 4.0 PARAGRAPHS

INSTRUCTIONAL TEXT IS SHOWN IN “BOLD ITALICS”

1.0 Typical Common Program Management Paragraphs

Interim and/or Final Report:

Document all technical work accomplished and information gained during the performance of this acquisition. Include all pertinent observations, nature of problems, positive as well as negative results, and design criteria established, where applicable: also procedures followed, processes developed, “Lesson Learned", etc. Document the details of all technical work to permit full understanding of the techniques and procedures used in evolving technology or processes developed. Separate design, engineering, or process specifications delivered during this acquisition shall be cross-referenced to permit a full understanding of the total acquisition. (See CDRL, A00X)

2.0 Typical Common Software (Hardware) Delivery Paragraphs

SOFTWARE:

Software. Deliver all software (hardware) developed, assembled, or acquired in accordance with the contract schedule and the following:

Developed software under this effort is to be completely maintainable and modifiable with no reliance on any non-delivered computer programs or documentation.

Software Delivery:

Deliver all software developed under this effort as source and object (executable) code. Include the commented source listings and source code. (See CDRL, A00X) Development and deliver software documentation:

Provide complete software documentation to include: Installation, User, and Maintenance Instructions, Software User Manual (SUM), Software Design Document (SDD). (See CDRL, A00X) Potential for Off-the-Shelf, Reusable or Government-Furnished is to be considered:

Consider the use of non-developmental software (i.e., commercial off-the-shelf (COTS), reusable, or Government-furnished) to ensure that all PWS requirements are met. Evaluate the software to determine whether the software performs as documented prior to incorporating acquired software into software being developed under this effort. Determine if the non-developmental software performs as documented and is adequately documented for the intended purpose.

COMMERICAL OFF THE SHELF (COTS):

Used when COTS is purchased with Government Funds and is used in the delivered software:

Transfer all purchased or licensed software used during development or as a component for this effort upon completion; include licensing and maintenance agreements and original media software and documentation. (See CDRL, A00X) Used if Commercial Hardware and Software are acquired as part of the “System”: (NOTE: CO must approve the purchase) If any commercial off-the-shelf hardware and software acquired for use during the development or as a component of the end product, has licenses and/or maintenance agreements with them, transfer them to the Government upon completion of the effort. Include any ancillary cabling required. (See CDRL, A00X) Hardware Delivery:

Deliver all developed, assembled and acquired hardware (i.e. chips, radios, cell phones, or exploratory model) to the Government at the completion of this effort.

Deliver, install and demonstrate the hardware system in the XYZ lab at AFCEC. Include as part of the installation all necessary equipment and/or hardware to fully demonstrate the system. Conduct the demonstration in accordance with the Government reviewed Demonstration Plan. (See CDRL, A00X)

3.0 Safety Words when working at AFCEC facilities.

4.0 Testing/Demonstration

Simple Testing:

Conduct testing of XXX to verify the fulfillment of the contract requirements. All testing shall be in accordance with the Government reviewed Test Plan. (See CDRL, A00X) Simple Demonstration:

Conduct a demonstration of the XXX in order to verify the results of this effort. Conduct the demonstration at such a time and place as specified in the contract schedule. The demonstration shall be in accordance with the Government-reviewed demonstration plan. (See CDRL, A00X)