Atch E - CSOWprep 6-15-09.doc

BROAD AGENCY ANNOUNCEMENT

BAA 09-RD-03

HIGH ENERGY LASER – JOINT TECHNOLOGY OFFICE (HEL-JTO)

CONTRACTOR STATEMENT OF WORK (CSOW) PREPARATION

Attachment E

a. The offeror’s SOW must be a separate and distinct document submitted on the same CD-R as Part C of the Full Proposal submission. The government intends to incorporate the offeror’s SOW into the proposed Year 1 Task Order 0001 award document. This will occur only if the offeror’s SOW accurately describes the work to be performed, is enforceable, and is void of inconsistencies. The offeror’s SOW must describe the technical methodology as well as the task description, but not in so much detail as to make the SOW inflexible. A CSOW is required only for the proposed Task Order 0001.

The SOW should specify in clear, understandable terms the work to be done in developing or producing the goods to be delivered or services to be performed by a contractor.

b. Although there is no page limit for the offeror’s SOW, it is anticipated that the Year 1 effort CSOW would not exceed five (5) pages.

c. Page Format:

(1) Paper Size – 8.5 inch x 11 inch

(2) Margins - one-inch on each page

(3) Font – Arial 11 pitch font or equivalent

(4) Single space. (Double space between paragraphs)

(5) Each printed side of a sheet counts as a page.

d. DO NOT INCLUDE ANY PROPRIETARY OR EXPORT CONTROLLED INFORMATION IN THE SOW. Contractors may request copies of our contracts under the Freedom of Information Act; consequently, no company-sensitive information should be included in the CSOW.

e. Do NOT include technical proposal information, tables, diagrams, graphs/charts, formulas, pictures, etc., in the SOW.

The following guidance is offered relative to the SOW content:

A recommended template for the offeror’s SOW:

Statement of Work

BAA Number: 09-RD-03 Technical Topic Area ____: (title) Sub-Topic Area: (title)

HEL-JTO Tracking Number: _________ PROJECT TITLE: (title)

Contract Number: (government will enter) Task Order 0001

(date)

1.0 SCOPE. This section includes the technology area to be investigated, objectives/goals, and major milestones for the effort. All work is anticipated for accomplishment under a cost plus fixed fee (completion) contract.

2.0 OBJECTIVE. The objective of this task order is to ________________________.

(example: “demonstrate …..”; develop ……”; develop and test…….”)

This section is intended to give a brief overview of the technology development effort and should describe why it is being pursued, what is intended to be accomplished, and what aspect of “Statement of Objectives and Proposed Approach” from the White Paper Technical/Management Section is being addressed.

3.0 BACKGROUND. (Brief statement as to why this is an effort worthy of the research.)

This section includes any information, explanations, or constraints that are necessary in order to understand the technical requirements presented in the SOW. It may include techniques previously tried and found ineffective. The offeror shall identify appropriate specifications, standards, and other documents that are applicable to the effort to be performed.

4.0 TECHNICAL TASK REQUIREMENTS.

A detailed description of tasks which represent the work to be performed. If an award is made, these tasks will become contractually binding. Thus, this portion of the SOW should be developed in an orderly progression and in enough detail to establish the feasibility of accomplishing the overall program goals. The SOW must contain every task. The tasks must be definitive, realistic, and clearly stated. Use “shall” whenever the work statement expresses a provision that is binding. Use “should” or “may” whenever it is necessary to express a declaration of purpose. Use “will” in cases where no offeror requirement is involved. Use active voice in describing projected work. ALL TASKS SHALL MATCH THOSE SET FORTH AND PRICED IN THE ORAL PRESENTATION AND THE COST PROPOSAL.

4.1 Segregate the work effort into major tasks and identify the tasks in separately numbered paragraphs. Delineate each numbered major task by subtask, the work to be performed, deliverables and CDRL items.

4.2 If a phased approach is proposed, specify such and present specific tasks with each phase.

4.3 If parallel performance of several broad but definable tasks is proposed, describe them and develop specific task statements for each.

4.4 If the proposed work involves use of government-developed technologies, concepts, or facilities, the effort/teaming must be described in the SOW. The SOW must clearly indicate which task(s) are to be performed by the offeror and which task(s) are to be performed by the government.

4.5 Include the following paragraphs, as applicable (these are representative only):

· System Requirements Generation

The contractor shall utilize a Systems Engineering approach to capture all top-level customer requirements and flow them to appropriate lower level documentation. This shall include implied requirements such as statutory regulations, not explicitly stated in the task order. The contractor shall include top-level performance specifications in this process.

· Trade Study and Analysis of Implementation Concepts

Contractor engineering subject matter professionals shall perform trade studies, generate hardware models, and analyze a variety of implementation methodologies to assess the most viable concept to address the requirements generated above. One output of this effort is _____________ as a function of __________________.

· Design. The contractor shall design (study, develop, …) _____________

· Fabrication (only if applicable)

· Test and Integrate Hardware/Software. The contractor shall perform final system integration, assembly and test.

· Data Collection/Analysis

4.6 PROGRAM MANAGEMENT. The contractor shall provide oversight of all development activities to ensure cost and schedule compliance in accordance with the basic contract.

4.6.1 The contractor shall be prepared to support a kickoff meeting at the contractor’s facility after submission and review of the Program Plan.

4.6.2 The contractor shall include a status brief/proposed second year effort near the end of the initial task order to be held in Albuquerque, NM, (November or December 2010 (1 trip)) as well as the HEL-JTO Annual Review to be held in Albuquerque, NM, May 2011.

5.0. EXIT CRITERIA & DELIVERABLES

5.1 CRITERIA: Specify government acceptance criteria for each deliverable, product or tangible end result that you expect from each task, phase or area of work at contract completion. Propose criteria for establishing or indicating that a specific milestone or phase has been completed.

5.2 DATA When proposing, indicate the appropriate CDRLs for your effort in the CSOW, and the applicable CSOW paragraph in Block 5 of the associated CDRL. Although the cost to prepare CDRL materials is included in the basic price, provide an estimate cost specific for each CDRL proposed. Complete Blocks 17 and 18 of each CDRL. Items 5.2.1 through 5.2.4 below are required for all efforts, 5.2.5 through 5.2.9 are “as required.”

5.2.1 The contractor shall submit a (Program Plan) for the task order. (CDRL A001)

5.2.2 The contractor shall submit Presentation materials from the kickoff meeting and annual status review. (CDRL A002)

5.2.3 The contractor shall submit monthly status reports. (CDRL A003)

5.2.4 Final Technical Report. The report shall be a thorough analysis report. (CDRL A004 or A007) (as set forth on individual task orders)

5.2.6 Software data (CDRL A005) (as set forth on individual task orders)

5.2.7 Bar Code Identification Report (CDRL A006)

5.2.8 Software Requirements Specifications (CDRL A008)

5.2.9 Software Development Plan (SDP) (CDRL A009)

5.3 HARDWARE. (Identify any specific hardware to be delivered as a result of the research)

PAGE