HR001125S0007_MICA_Attachment_B_Abstract_Instructions_and_Template.docx
DOCX document 44 KB Posted
- Attached to
- Microsystem Induced CAtalysis (MICA) Federal contract opportunity
- Solicitation number
- HR001125S0007
About this file
This is an abstract template and submission instructions for DARPA's Microsystems Induced CAtalysis (MICA) Broad Agency Announcement (BAA). The template requires abstracts to be submitted in PDF or Microsoft Word format, limited to 5 pages with 12-point font and 1-inch margins, and must include both Attachment A (Abstract Summary Slide) and B to be considered complete.
The abstract submission must include a cover sheet with organizational and POC details, followed by three main sections: Goals and Impact (describing the proposed innovation and its significance), Technical Approach (detailing methodology and addressing technical challenges), and Capabilities/Management Plan (outlining team expertise and organization). DARPA will respond to abstracts within 30 days with either a recommendation to submit a full proposal or not. While a favorable response to an abstract does not guarantee award selection, proposers may submit full proposals regardless of DARPA's abstract review feedback. The document requires abstracts to be UNCLASSIFIED or CUI level, with all proprietary information appropriately marked.
View the file
Other files for this federal contract opportunity
Show all 16
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
HR001125S0007: Microsystems Induced CAtalysis (MICA)
Abstract Instructions and Template
Use of this template is mandatory for all abstract submissions to this BAA. Proposers must include Attachments A (Abstract Summary Slide Template) and B to constitute a full abstract submission. 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 or Controlled Unclassified Information (CUI) level. All proprietary data and information should be appropriately marked.
| Page limit includes: |
| Page limit does NOT include: |
| All figures, tables, charts |
| Cover Sheet |
Table of Contents
Bibliography
Technical Papers (Optional, no more than 3)
Proposers are strongly encouraged 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
| Technical Point of Contact (POC) |
| Name: |
Mailing Address:
Telephone:
Email:
| Administrative POC |
| Name: |
Mailing Address:
Telephone:
Email:
| Other Team Members (subcontractors and consultants), if known/applicable |
| Technical POC Name: |
Organization:
Technical POC Name:
Organization:
| Estimated Total Cost (Base + Options) |
| $ |
Estimated Period of Performance
Identify any other solicitation(s) to which this concept has been proposed.
Table of Contents
| 1. | Goals and Impact | 4 |
| 2. | Technical Approach | 4 |
| 3. | Capabilities/Management Plan | 4 |
| 4. | Bibliography | 4 |
HR001125S0007 Abstract 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. Describe the significance and impact of of the proposed reaction(s).] 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 testing community 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.]
File details come from the government source that posted it. Updated .