Attachment_A_Abstract_Instructions_and_Template.docx
DOCX document 41 KB Posted
- Attached to
- Microsystems Technology Office (MTO) Office-wide Federal contract opportunity
- Solicitation number
- HR001124S0028
About this file
This document provides instructions and a template for submitting abstracts in response to the Microsystems Technology Office (MTO) Office-wide Broad Agency Announcement (BAA) solicitation number HR001124S0028.
The instructions outline the required format and content for the 6-page abstract, including a cover sheet, table of contents, and sections on innovative claims, technical approach, deliverables, other research, cost and schedule, capabilities/management plan, and bibliography. Abstracts must be submitted electronically through the Broad Agency Announcement Tool by the specified deadline. DARPA will review the abstracts and provide a response on whether to submit a full proposal, though proposers may still submit a full proposal regardless of DARPA's recommendation. The solicitation seeks revolutionary research ideas not addressed by existing MTO programs or other published solicitations. No other details about the specific products, services, or requirements are provided in this document.
View the file
Other files for this federal contract opportunity
Show all 34
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
HR001124S0028: Microsystems Technology Office (MTO) Office-wide Broad Agency Announcement (BAA)
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 6 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
Proposers are strongly encouraged but not required to submit an abstract before submitting a full proposal. Proposers are strongly encouraged to submit an abstract in advance of a full proposal in order to provide potential proposers with a rapid response and to minimize unnecessary effort in proposal preparation and review. 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 through the Broad Agency Announcement Tool, must follow the instructions outlined herein, and must be 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 the Unclassified Submission Instructions section of 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
MTO Topic(s) of Interest (see Section I.A.)
Type of Organization
Choose all that apply: Large Organization, Small Disadvantaged Organization, Other Small Organization, HBCU, MI, Other Educational, Other Nonprofit
Prime 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:
Type of Organization:
Technical POC Name:
Organization:
Type of Organization:
| Total Funds requested from DARPA, and the amount of cost share (if any) |
| $ |
Identify any other solicitation(s) to which this concept has been proposed.
Table of Contents
| 1. | Innovative Claims | 4 |
| 2. | Technical Approach | 4 |
| 3. | Deliverables | 4 |
| 4. | Other Research | 4 |
| 5. | Cost and Schedule | 4 |
| 6. | Capablitilies/Management Plan | 4 |
| 7. | Bibliography | 4 |
Attachment A: HR001124S0028: Abstract Instructions and Template Source Selection Sensitive – See FAR 2.101 and FAR 3.104
Innovative Claims [Summary of innovative claims for the proposed research. This section is the centerpiece of the abstract and should succinctly describe the uniqueness and benefits of the proposed approach relative to the current state-of-art alternate approaches.] Technical Approach [Technical rationale, technical approach, and constructive plan for accomplishment of technical goals in support of innovative claims and deliverable production.] Deliverables [Deliverables associated with the proposed research and the plans and capability to accomplish technology transition and commercialization.] Other Research [General discussion of other research in this area.] Cost and Schedule [Provide a cost estimate for resources (e.g. labor, materials) and any subcontractors over the proposed timeline of the project, broken down by Government fiscal year.] Capabilities/Management Plan [A clearly defined organization chart for the program team which includes, as applicable: (1) the programmatic relationship of team member; (2) the unique capabilities of team members; (3) the task of responsibilities of team members; (4) the teaming strategy among the team members; and (5) the key personnel along with the amount of effort to be expended by each person during each year.] Bibliography [Provide a brief (no more than 2 pages) bibliography with links to relevant papers, references, reports, etc. The bibliography does not count towards the total page count of the abstract.]
File details come from the government source that posted it. Updated .