ATT3 - 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: Technical Areas (TAs), Tasks, and Subtasks that fit the parameters defined by the Task Specifications.

Each of the TAs will be comprised of high-level Tasks. 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 that operate within the Task Specifications. Subtasks should include interactions with regulatory agencies, when needed. Deliverables that IV&V teams will test should be described for the end of each Phase.

All Tasks and Subtasks should indicate the Performer that will complete the work and whether the Task/Subtask is expected to be fundamental research or research that requires use of CUI (see CUI guide).

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 D Section D should be written in a concise manner and must not exceed 10 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.” Colors should be removed from final submission, as well as these instructions.

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)

B. 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 B may not exceed 1 page (Times New Roman, 12-pt font, single-spaced, standard margins).

C. APPLICABLE DOCUMENTS

(a) HR001121SXXXX-EMBER

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

D. 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)

Technical Area 1 : Bioengineering for REE Utilization 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...”

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

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).

Task Specifications 1.1:

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

Technical Area 2: REE Biomining 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...”

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

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).

Task Specifications 1.1:

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

End of Phase 1 Deliverables:

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

OPTION PERIOD (PHASE II)

Technical Area 1: Bioengineering for REE Utilization Task 4: [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...”

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

Subtask 4.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).

Task Specifications 4.1:

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

Technical Area 2: REE Biomining Task 3: [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...”

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

Subtask 3.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).

Task Specifications 3.1:

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

End of Phase 2 Deliverables:

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

OPTION PERIOD (PHASE III)

Technical Area 1: Bioengineering for REE Utilization Task 7: [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...”

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

Subtask 7.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).

Task Specifications 7.1:

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

Technical Area 2: REE Biomining Task 5: [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...”

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

Subtask 5.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).

Task Specifications 5.1:

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

End of Phase 3 Deliverables:

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

E. 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.

The Government will actively monitor, review, and approve the Contractor's performance to ensure the performers are at pace with the Government's requirements. At the Government-PI meeting, all performers shall demonstrate their technical capabilities and engage or challenge each other in a cooperative environment. Along these lines, the Government will ensure that the performers each share technical information with each other, as appropriate, to enable the testing/challenging of each other's capabilities. The Government will further oversee the program and will review, approve, and participate in the demonstrations, as well as determine which performers will advance to the Option Periods (Phase II, Phase III).

To prevent the release of sensitive technical information certain aspects of proposals may be considered Controlled Unclassified Information (CUI) and may require safeguarding or dissemination controls, pursuant to and consistent with applicable law, regulations, and government-wide policies. Performers must partition potentially sensitive tasks from non-sensitive research efforts. Research conducted for TA1 Bioengineering for REE Utilization is expected to constitute fundamental research, and research conducted on REE Biomining (Technical Area 2) is expected to produce Controlled Unclassified Information (CUI). However, the overall program will require protection as CUI, thus the Government expects that all awards, to include subawardees, will include restrictions on the resultant research that will require the awardee to seek DARPA permission before publishing any information or results relative to the program. All performers (prime contractor and subcontractor) desiring public release of project information that may contain CUI as defined in the CUI Guide must submit a request for public release from DARPA/PRC in accordance with contractual requirements. Academic contractors considered to be conducting fundamental research on this program may publish papers (after review by DARPA) that describe scientific or engineering advances that are general in nature and adhere to the above guidance.

E.1. Regulatory Strategy Performers will obtain any necessary permits, licenses or certifications required for acquisition, transportation, storage, and/or disposal of REE source materials, radioactive elements, biomass, waste by-products, and other system components as determined by the chosen REE source. Performers will describe anticipated regulatory guidance (if any) and safety practices applicable to their planned research activities using their selected REE source material. This may include EPA, Department of the Interior, Nuclear Regulatory Commission, State or local regulators for certification, licensing, packaging, handling, transportation, research uses, and disposal of rare earth elements, heavy metals, radioactive elements, other hazardous materials, and genetically modified living organisms (if used in the biomining workflow).

Proposers must present a detailed plan for early and continued engagement with regulators (e.g., EPA, NRC, DOI, throughout the program to discuss developing technologies and challenges in order to inform and improve the design of Biomining strategies for REE extraction, purification and recovery.

E.2. Ethical, Legal, Environmental, and Social Issues (ELESI) Activities to address Ethical, Legal, Environmental, and Social Issues (ELESI) are anticipated in this effort. The Recipient shall support ELESI activities with DARPA including semi-annual teleconference calls with the ELESI Panel and regular feedback from the Panel regarding the performer’s activities. ELESI activities will be reported regularly to DARPA.

E.2. 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.

E.3. Monthly Financial Reports The Contractor shall provide monthly financial progress reports to DARPA. 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.

E.4. Quarterly Financial Reports The Contractor shall provide quarterly financial progress reports to the DARPA. The purpose of these reports is to provide a brief project progress and inform Government of any potential issues.

E.5. Monthly Technical Reporting The Contractor shall provide monthly progress reports to DARPA. 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.

E.6. Quarterly Technical Reporting The Contractor shall provide detailed technical quarterly progress reports to DARPA. 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 (if any), and ELESI 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.

E.7. 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 EMBER performer teams will participate in 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, and with appropriate protections of any proprietary information.

The Contractor shall host annual site visits of DARPA. 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 ELESI activities.

E.8. Final Contract/Cooperative Agreement Report Comment by Chrisey, Linda: I am not sure CA’s will be permitted given the CUI stance 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 and others as identified in their award instrument).

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

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

G. TRAVEL

Travel is anticipated for meetings between collaborators, meetings with DARPA, and to professional conferences to include annual PI meetings, ELESI activities, and annual site visits.

H. PLACE OF PERFORMANCE

<<Insert prime institution name and address>>

<<Insert subcontractor institution name(s) and address(es)>>

I. SECURITY

This work is unclassified but expected to contain Controlled Unclassified (CUI). The SOW should state whether the Task/Subtask is expected to require use of CUI (see CUI guide). Performer teams will have to submit a CUI Management Plan with the SOW.