Attachment_A_Abstract_Instructions_and_Template_COFFEETA2.docx

HR001124S0027: COmpact Front-end Filters at the ElEment-level (COFFEE) Technical Area 2 (TA2)

Abstract Instructions and Template

Use of this template is mandatory for all abstract submissions to this BAA. 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 may be at the unclassified, Controlled Unclassified Information (CUI), or classified level. For an abstract that includes both classified and unclassified information, it is recommended that the abstract be separated into an unclassified portion and a classified portion. All proprietary data and information should be appropriately marked.

Table of Contents

Bibliography

Technical Papers (Optional, no more than 3)

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

a. recommends the proposer submit a full proposal or,

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

Regardless of DARPA’s response to an abstract, proposers may submit a full proposal. DARPA will review all conforming full proposals using the published evaluation criteria and without regard to any comments resulting from the review of an abstract. Proposers should note that a favorable response to an abstract is not a guarantee that a proposal based on the abstract will ultimately be selected for award negotiation. It is DARPA policy to attempt to reply to abstracts within thirty calendar days. These official notifications will be sent via email to the Technical POC and/or Administrative 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. 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

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: HR001124S0027 Abstract Instructions and Template Source Selection Sensitive – See FAR 2.101 and FAR 3.104

2 | Page

Goals and Impact [Describe what is being proposed and what difference it will make (qualitatively and quantitatively) if successful. Describe the innovative aspects of the project in the context of existing capabilities and approaches, clearly delineating the relationship of this work to any other projects from the past and present.

Technology Transition Plan [Describe the primary deliverables associated with the proposed project and any plans to commercialize the technology, transition it to a customer, or further the work. Describe how the deliverables enable this plan and create or accelerate disruption. Discuss how the technology will be sustained over its lifecycle, assuming the technology transition plan is successful.] Technical Approach [Provide answers to the following questions:

· What is the proposed work attempting to accomplish or do?

· How is the work performed today (what is the state of the art or practice), and what are the limitations?

· What is new in your approach, and why do you think it will be successful?

· How would the DoD community and commercial sector implement the proposed approach/work?

· How much will it cost (rough order of magnitude), and how long will it take?

Outline and address technical challenges inherent in the approach and possible solutions for overcoming potential problems. Provide appropriate measurable milestones (quantitative if possible) at intermediate stages of the project to demonstrate progress and a plan for achieving the milestones.] Capabilities/Management Plan [Provide a brief summary of the expertise of the team, including subawardees and key personnel. While teaming arrangements do not need to be finalized at the time of abstract submission, mention of potential teaming/collaboration arrangements is highly encouraged. Identify a principal investigator for the project and include a description of the team’s organization, including roles and responsibilities.] Bibliography [Provide a brief (no more than 2 pages) bibliography with links to relevant papers, references, reports, etc.]