Attachment_A_Abstract_Instructions_Template.docx

HR001125S0014 CoasterChase BAA Abstract Instructions and Template

Proposers are strongly encouraged to submit an abstract to reduce the potential expense of preparing an out-of-scope proposal. DARPA will attempt to reply within five (5) calendar days of receipt 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.

These official notifications will be sent via email to the Technical POC and/or Administrative POC identified on the abstract coversheet. Full proposals may be submitted irrespective of comments or feedback received in response to the abstract. Proposals are reviewed without regard to feedback given as a result of abstract review. The time and date for submission of proposal abstracts are specified in Section III of the BAA.

The abstract is a concise version of the proposal comprising a maximum of five (5) pages, including all figures, tables, and charts. All submissions must be written in English with type no smaller than 12-point font. Font sizes of 8- or 10-point may be used for figures, tables, and charts. All pages shall be formatted for printing on 8-½ by 11-inch paper. Margins must be 1-inch on all sides. Copies of all documents submitted must be clearly with the DARPA BAA number, proposer organization, and proposal abstract title.

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. Abstracts should be at the UNCLASSIFIED or Controlled Unclassified Information (CUI) level. All proprietary data and information should be appropriately marked. Comment by Roa, Laura (contr-bto): Since we're fundamental research, we shouldn't have any CUI, right? Comment by Waud, Kelly (contr-bto): Right - I just don’t know what folks might introduce that could be sensitive. Was leaving it in, but we can also ask Elvis.

Cover Sheet

Table of Contents

Bibliography (Optional)

Please visit Proposer Instructions and General Terms and Conditions for instructions on how to submit your abstract through DARPA’s Broad Agency Announcement Tool (BAAT). Regardless of instrument type desired, abstracts should not be submitted through Grants.gov.

COVER SHEET

[PRIME ORGANIZATION LOGO (optional)]

Abstract Title

Proposer Organization

Mailing Address:

Telephone:

Email:

Mailing Address:

Telephone:

Email:

Organization:

Technical POC Name:

Organization:

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

Table of Contents

HR001125S0014 CoasterChase Abstract Source Selection Sensitive – See FAR 2.101 and FAR 3.104

2 | Page

Goals and Impact Describe the proposed approach, specifically 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. Address the following questions:

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

· How is it done today? What are the limitations?

· What is innovative in your approach/ how does it compare to the correct state-of-the-art?

· Who will care, and what will the impact be if you are successful?

Technical Approach Provide answers to the following questions:

· How does the proposed effort address the goals of the program?

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

· What are the key technical challenges and how will they be addressed?

Ensure that all technical areas and challenges inherent in the approach are outlined and addressed, along with possible solutions for overcoming potential problems. This section should provide specific objectives at intermediate stages of the project to demonstrate a plan for accomplishment of the program goals, milestones, and metrics.

Capabilities/Management Plan Describe the team’s organization including roles and responsibilities. Team member descriptions should address the Technical Plan, describe the time and percent effort divisions for members participating across both functional areas (FAs), and delineate individuals to avoid duplication of efforts. While teaming arrangements do not need to be finalized at the time of abstract submission, mention of potential teaming/collaboration arrangements is highly encouraged.

All teams are strongly encouraged to identify a Project Manager/Integrator to serve as the primary point of contact to communicate with the DARPA Program Manager and Contracting Officer’s Representative, coordinate the effort across co-performers, vendors, and subcontractor teams, organize regular performer meetings or discussions, facilitate data sharing, and ensure timely completion of milestones and deliverables.

Include a description of the organizational experience in this area, existing intellectual property required to complete the project, and any specialized facilities to be used as part of the project. List Government-furnished materials or data assumed to be available.

Cost and Schedule Provide a cost estimate for resources over the proposed timeline of the project, broken down by phase and major cost items (e.g. labor, materials, etc...)

Include cost estimates for each potential subcontractor (rough order of magnitude acceptable). Provide a reasonable schedule/timeline for the completion of major tasks that adhere to the program months for milestones, metrics, and deliverables.

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