Attachment_2_-_HR001119S0070_-_SOW_Template.docx

Statement of Work Template Guide Proposers are required to submit a Statement of Work (SOW) that provides a clear, concise outline of the work performed during the proposed effort, the milestones, and the deliverables to be agreed upon between DARPA and the proposer. Proposers are strongly encouraged to use this template as it highlights the technical areas and requirements described in the BAA, aligns to the budget template, and is organized to include the appropriate level of detail over three hierarchical levels: Categories, Tasks, and Subtasks.

Categories should consist of Technical Areas (TA), Platform Integration, and IV&V Preparation. Each of these Categories will be comprised of high-level Tasks that are required to accomplish Category goals. Each Task will be comprised of Subtasks that describe the specific, technical work performed to accomplish Task goals. It is the proposers’ responsibility to identify the appropriate number of Tasks and Subtasks that are necessary to meet the goals of the program.

All Tasks and Subtasks must include start and end months in relation to the beginning of the program. For example, a task or subtask with a six-month duration beginning the first day of the effort should be labeled “Start: Month 1, End: Month 6.”

Instructions for Section C Section C should be written in a concise manner and must not exceed 20 pages (Times New Roman, 12-pt font, single-spaced, normal margins). Do NOT use any pronouns. Refer to your institution and subs collectively as “the contractor.” Identify all tasking containing human or animal subject research with “This task contains Human subject research” or “This task contains animal subject research.” Colors should be removed from final submission, as well as these instructions.

Human Subjects Research Institutions awarded funding for research involving human subjects must provide documentation of a current Assurance of Compliance with federal regulations for human subjects protection, such as a Department of Health and Human Services, Office of Human Research Protection Federal Wide Assurance (http://www.hhs.gov/ohrp). All institutions engaged in human subjects research, to include subcontractors, must also hold a valid assurance. In addition, all personnel involved in human subjects research must provide documentation of completion of human subjects research training.

The time required to complete the IRB review/approval process varies depending on the complexity of the research and the level of risk involved with the study. The IRB approval process can last between one and three months, followed by a DoD review that could last between three and six months. Ample time should be allotted to complete the approval process. DoD/DARPA funding cannot be used toward human subjects research until ALL approvals are granted.

See Section 4.2.3 (beginning on page 17) of the BAA for additional details.

Animal Use For projects anticipating animal use, proposals should briefly describe plans for Institutional Animal Care and Use Committee (IACUC) review and approval. Animal studies in the program will be expected to comply with the Public Health Service (PHS) Policy on Humane Care and Use of Laboratory Animals, available at http://grants.nih.gov/grants/olaw/olaw.htm.

All award recipients must receive approval by a DoD-certified veterinarian, in addition to an IACUC approval. No animal studies may be conducted using DoD/DARPA funding until the United States Army Medical Research and Materiel Command (USAMRMC) Animal Care and Use Review Office (ACURO) or other appropriate DoD veterinary office(s) grant approval. As a part of this secondary review process, the award recipient will be required to complete and submit an ACURO Animal Use Appendix, which may be found at http://mrmc.amedd.army.mil/index.cfm?pageid=research_protections.acuro_animalappendix.

See Section 4.2.3 (beginning on page 17) of the BAA for additional details.

STATEMENT OF WORK

<<insert Proposer Organization>> <<insert PI name>> <<insert BAA control number>>

STATEMENT OF WORK

Title – <<Insert Proposal Title>>

A. SCOPE

Provide draft language with the expectation that it will be finalized by DARPA and proposer during contract negotiations. This section should:

1. Describe the overarching goal of the project (1-2 sentences)

2. Outline the approach for each technical area (2-3 sentences each)

3. Describe the major outcomes or deliverables expected at the end of the period of performance (1-2 sentences each)

4. Address the path to regulatory approval (1-2 sentences)

A.1. BACKGROUND

Provide draft language with the expectation that it will be finalized by DARPA and proposer during contract negotiations. This section should resemble the introduction section of a research manuscript. It should (a) provide scientific and technical context that supports both the technical merit and the DoD relevance of the proposal, and (b) summarize the information included in the proposal, but not duplicate it. Figures, graphs, tables, and datasets should not be included in this section. Section A.1 may not exceed 1 page (Times New Roman, 12-pt font, single-spaced, standard margins).

B. APPLICABLE DOCUMENTS

(a) HR00119S0070-Pecan

(b) <<Organization>> Proposal Titled “<<Proposal Title>>” dated <<submission date>>.

C. PROJECT WORK DESCRIPTION AND REQUIREMENTS

The Contractor shall provide the facilities and equipment necessary to develop the effort as described herein.

Provide draft language with the expectation that it will be finalized by DARPA and proposer during contract negotiations. This section should address expectations of the proposer to meet DARPA and BAA requirements.

BASE PERIOD (PHASE I)

CATEGORY 1

Task 1: [Title]; [Start: Month X, End Month: Z] Describe the goal of the Task (2-4 sentences). Each task or subtask should begin with “The contractor shall...”

Subtask 1.1: [Title]; [Performing institution(s)]; [Start: Month X, End: Month Y] Describe specific efforts (e.g., experiments) required to achieve Task goal (1-2 sentences).

Milestone 1.1: [End: Month Y] Describe how success will be measured in this Subtask (1 sentence).

Metrics/Completion Criteria 1.1:

Outline specific, quantitative metric(s) to demonstrate successful Milestone completion (1-2 sentences).

Deliverables 1.1:

Describe the final technical achievement(s), product(s), etc. that are generated during this Task (1-2 sentences).

CATEGORY 2 [Insert additional categories as needed.]

OPTION PERIOD (PHASE II)

CATEGORY 1

Task 1: [Title]; [Start: Month X, End Month: Z] Describe the goal of the Task (2-4 sentences). Each task or subtask should begin with “The contractor shall...”

Subtask 1.1: [Title]; [Performing institution(s)]; [Start: Month X, End: Month Y] Describe specific efforts (e.g., experiments) required to achieve Task goal (1-2 sentences).

Milestone 1.1: [End: Month Y] Describe how success will be measured in this Subtask (1 sentence).

Metrics/Completion Criteria 1.1:

Outline specific, quantitative metric(s) to demonstrate successful Milestone completion (1-2 sentences).

Deliverables 1.1:

Describe the final technical achievement(s), product(s), etc. that are generated during this Task (1-2 sentences).

CATEGORY 2 [Insert additional categories as needed.]

OPTION PERIOD (PHASE III)

CATEGORY 1

Task 1: [Title]; [Start: Month X, End Month: Z] Describe the goal of the Task (2-4 sentences). Each task or subtask should begin with “The contractor shall...”

Subtask 1.1: [Title]; [Performing institution(s)]; [Start: Month X, End: Month Y] Describe specific efforts (e.g., experiments) required to achieve Task goal (1-2 sentences).

Milestone 1.1: [End: Month Y] Describe how success will be measured in this Subtask (1 sentence).

Metrics/Completion Criteria 1.1:

Outline specific, quantitative metric(s) to demonstrate successful Milestone completion (1-2 sentences).

Deliverables 1.1:

Describe the final technical achievement(s), product(s), etc. that are generated during this Task (1-2 sentences).

CATEGORY 2 [Insert additional categories as needed.]

D. PROGRAM MANAGEMENT AND REVIEW

Provide draft language with the expectation that it will be finalized by DARPA and proposer during contract negotiations. This section should address expectation of the proposer to meet DARPA and BAA requirements.

D.1. Kick-off Meeting The Contractor shall attend a kick-off meeting at a location selected by DARPA. In this meeting, the Contractor shall introduce the leads on the team, present their scope of work as well as a program management plan and financial tracking plan.

D.2. Monthly Financial Reports The Contractor shall provide monthly financial progress reports to DARPA (Biological Technologies Office and Contract Management Office). The purpose of these reports is to provide a brief project progress and inform the DARPA Program Manager of any potential issues. A template will be provided for monthly reports.

D.3. Quarterly Financial Reports The Contractor shall provide quarterly financial progress reports to the DARPA (BTO and CMO). The purpose of these reports is to provide a brief project progress and inform DARPA (BTO and CMO) of any potential issues.

D.4. Monthly Technical Reporting The Contractor shall provide monthly progress reports to DARPA (BTO and CMO). The purpose of these reports is to present a summary of work completed by SOW tasking and milestones met, discuss any problems encountered, update the program schedule, present the program financial status, and discuss remaining work. A template will be provided for monthly reports.

D.5. Quarterly Technical Reporting The Contractor shall provide detailed technical quarterly progress reports to DARPA (BTO and CMO). The purpose of these reports is to present a summary of work completed and milestones met; discuss any problems encountered; update the program schedule; present the program financial status; and discuss remaining work regarding technical tasks, regulatory engagement, and ELSI activities. Quarterly reports shall also include all technical data items generated under this agreement but not limited to experimental data; processed data, along with methods of processing used; research reports and publications; and software (source code and executables). A template will be provided for quarterly reports.

D.6. PI Meetings DARPA will actively engage with and manage the performer teams throughout the project, to include program level meetings and site visits held every 6 months for the program duration.

All Pecan performer teams will participate in the program review meetings by sharing their accomplishments to date as well as the planned work for the next six-month period. Program review meetings may be attended by other performer teams or U.S. Government stakeholders at the discretion of the DARPA Program Manager.

The Contractor shall host annual site visits of DARPA (BTO and CMO). The purpose of this visit is to present a summary report of all work completed and milestones accomplished and to discuss ongoing or future technical tasks, data sharing, and ELSI activities.

D.7. Final Contract/Cooperative Agreement Review The Recipient shall prepare and deliver a final contract report that completely and clearly describes all work completed, the results obtained and the implications of those results. The contractor shall discuss milestones accomplished and relevant and/or related future efforts which may be pursued. The Recipient shall provide a copy of the final report to DARPA (BTO and CMO).

E. GOVERNMENT FURNISHED EQUIPMENT (GFE) / CONTRACTOR ACQUIRED PROPERTY (CAP)

Leave blank - Will be finalized by DARPA and proposer during negotiations.

F. TRAVEL

Travel is anticipated for meetings between collaborators, meetings with DARPA, annual PI meetings, and annual site visits.

G. PLACE OF PERFORMANCE

<<Insert prime institution name and address>>

<<Insert subcontractor institution name and address>>