Attachment_B_BLIND_ABSTRACT_TEMPLATE.docx

HR001122S0007 Coded Visibility BAA Abstract 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, .odx, .doc, or .docx 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 not smaller than 12 point. Font sizes of 8 or 10 point may be used for figures, tables, and charts.

Please note that DARPA is using a blind Abstract review process. The cover sheet will be removed from the Abstract prior to commencement of the review process. Please DO NOT include any company identifying information or personnel names, including the proposed Principle Investigator, or the names of any subcontractor institutions or companies on any pages except for the cover sheet. Abstracts that include identifying company information or personnel names on a page other than the cover sheet may be deemed non-conforming, and may not be evaluated. Regardless of the conformity of the submitted abstract, or any feedback received in response to an abstract, you may still submit a full proposal.

Abstracts shall not exceed a maximum of 5 pages.

Table of Contents

Bibliography (Optional)

Technical Papers (No more than 3)

[PRIME ORGANIZATION LOGO]

HR001122S0007 Coded Visibility

Abstract

Abstract Title

Proposer Organization

Technical Area

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

Source Selection Information – See FAR 2.101 and 3.104

HR001122S0007 Abstract 4 Goals and Impact [Without naming the institution, company, or any proposed personnel, 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.] Technical Plan [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?

· Who will care and what will the impact be if the work is successful?

· How much will it cost, and how long will it take?

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

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 [Without naming the institution, company, or any proposed personnel, provide a brief summary of expertise of the team, including subawardees and key personnel. In lieu of naming, use entity identifiers. Examples for companies or institutions, include: “large business”, “small business”, “university”, etc. Examples for personnel include: “PI”, “Senior Physicist”, “Junior Electrical Engineer”, “Graduate Student”, “Post Doc”, etc. While teaming arrangements do not need to be finalized at the time of abstract submission, mention of potential teaming/collaboration arrangements is highly encouraged. Include a description of the team’s organization including roles and responsibilities, to include which entities may generate, and which will be responsible for management of, Controlled Unclassified Information (CUI), if needed.] Cost and Schedule [Without naming the institution, company, or any proposed personnel, provide a cost estimate for resources (e.g., labor, materials) and any subawardees over the entire program (base + options), broken down by Contractor Fiscal Year]