DARPA-SN-26-27_Attachment_A_Abstract_Template.docx

DARPA-SN-26-27: Generative Optogenetics (GO)

Abstract Instructions and Template – DELETE THIS PAGE

Use of this template is mandatory for all abstract submissions to this Special Notice. Proposers must utilize DARPA-SN-26-27 Attachment A. This document must include all components described herein and must be submitted in PDF or Microsoft Word formats. All submissions must be written in English, and all pages shall be formatted for printing on 8-1/2 by 11-inch paper with 1-inch margins and font size no smaller than 12-point. Font sizes of 8 or 10-point may be used for figures, tables, and charts.

Abstracts shall not exceed a maximum of 5 pages. Abstracts should be at the UNCLASSIFIED level. All proprietary data and information should be appropriately marked.

Table of Contents

Bibliography

Technical Papers (Optional, no more than 3)

Proposers are required to submit an abstract before submitting a full proposal. DARPA will respond to abstracts with a statement as to whether DARPA:

a. Invites the proposer submit a full proposal or,

b. does not invite the proposer submit a full proposal with a rationale for this decision.

Proposers must submit an abstract and receive an invitation before submitting a full proposal. Proposals submitted without an abstract and invitation for a full proposal will not be reviewed. Proposers should note that an invitation to submit a full proposal does not guarantee selection for award negotiation. Official notifications will be sent via email to the Technical and Administrative point of contact (POC) identified on the abstract cover sheet.

Abstracts must be submitted per the instructions outlined herein and received by DARPA no later than the due date and time listed in the Overview Information section. Abstracts received after this time and date may not be reviewed. Please visit Proposer Instructions and General Terms and Conditions for instructions on how to submit your abstract through the Broad Agency Announcement Tool.

COVER SHEET

[PRIME ORGANIZATION LOGO]

Abstract Title Comment by Saperstein, Rob: Do you want to add a row for the proposer to state which working group the abstract corresponds to managing? Comment by Zeitouni, Nathalie (contr-bto): Good idea! Done

Proposed Working Group

Special Notice # (if applicable)

Proposer Organization

Mailing Address:

Telephone:

Email:

Mailing Address:

Telephone:

Email:

Organization:

Technical POC Name:

Organization:

Estimated Period of Performance

Identify any other solicitation(s) to which this concept has been proposed.

Table of Contents

Attachment A: DARPA-SN-26-27 Proposal Abstract Source Selection Sensitive – See FAR 2.101 and FAR 3.104

2 | Page

Executive Summary Provide a concise overview of the proposed working group and how it aligns with the GO program’s need to ensure responsible development, regulation, and commercialization of GO technologies. Describe the impact of the proposed approach if successful, emphasizing its innovative aspects compared to existing capabilities and methods. Clearly outline how the relationship of this work to any other projects from the past and present. Articulate how the working group’s activities will address critical challenges in biosecurity, regulatory policy, or commercialization, and how these efforts will anticipate and mitigate risks while enabling the transformative potential of GO technologies in end-use applications. Comment by Saperstein, Rob: Or Comment by Zeitouni, Nathalie (contr-bto): I think the and is fine. This is about aligning with the 3 Program needs (responsible development, regulation, and commercialization) rather than which of the 3 needs the proposers plan to address.

Recommended length of 1 page.

Background and Expertise Provide a brief summary of the expertise of the team, including subawardees and key personnel. While working group members do not need to be identified at the time of abstract submission, proposers are required to describe member recruitment plans, to include solicitation, selection and compensation strategies. Identify a project lead and include a description of the team’s organization, including roles and responsibilities.

Recommended length of approximately 1.5 pages.

Scope of Work Provide a brief summary of proposed plan for defining specific objectives, scheduling, formatting, and facilitating regular working group meetings to ensure productive discussions and progress towards their objectives, tracking progress against key milestones, identifying and addressing roadblocks to program timelines, and providing regular updates to DARPA.

Recommended length of approximately 2 pages.

Basis of Estimate Provide a notional plan/budget for working group compensation. Note: Honorariums are not permissible as a method of compensation. All compensation-related costs must be explicitly incorporated into the basis of estimate.

Recommended length of approximately 0.5 page.

Bibliography [Provide a brief (no more than 2 pages) bibliography with links to relevant papers, references, reports, etc.]