Attachment_1_Written_Abstract_Instructions_and_Template_20260602.docx

COVER SHEET

Abstract Title

Proposed Thrust Areas and Technical Office:

See RSO Section 4, Subsection II. Research Thrust Areas. No more than one Technical Office may be listed.

Mailing Address:

Telephone:

SAM/UEI:

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.

· The title page and attestation pages do not count against Page Limits. A response is required for all table elements and attestations.

ABSTRACT GUIDELINES: Use of this template is required for all written abstract submissions. Proposers must include all information in this template to constitute a fully conforming abstract submission.

Page Limit Requirement: Abstracts shall not exceed a maximum of 4 pages. This page limit does NOT include the following:

· Abstract Coversheet

· Attestations

· Table of Contents

· Bibliography (Optional)

· Technical Papers (Optional)

Formatting Requirements: All submissions must be typed in English on 8.5" by 11" pages using a 12-point font with 1" margins all around. 8 or 10-point fonts may be used for figures, tables, and charts. Use of diagram(s) or figure(s) to depict the essence of the proposed solution is encouraged. Do NOT include elaborate brochures or marketing materials.

Content Requirements: Content requirements are noted in blue font under each section of the abstract template. Proposers should delete all content requirements before submitting the abstract.

Submission Requirements: Abstracts must be submitted in PDF or Microsoft Word format. The recommended file naming convention is “Organization Name_DARPA RSO Abstract.” All proprietary information should be appropriately marked. NOTE: "Confidential" is a classification marking used to control the dissemination of U.S. Government National Security Information as dictated in Executive Order 13526 and should not be used to identify proprietary business information.

UNCLASSIFIED abstracts must be submitted via DARPA’s Broad Agency Announcement Tool (BAAT). Please visit the Proposer Instructions and General Terms and Conditions site for specific information regarding submission methods through BAAT. Please note that BAAT is a secure method of transmission for CUI documentation. Submissions sent through other mediums, channels, or after the prescribed deadline will not be accepted.

ATTESTATION STATEMENTS

Submitters must also include the following statements attesting to the below on a separate page (these statements will NOT count toward the four (4) page limit):

· No individuals on the submitter's team are currently performing services for DARPA as Systems Engineering Technical Assistance (SETA) contractors, Advisory and Assistance Services (A&AS) contractors, or similar support services, as DARPA has a policy prohibiting SETA and A&AS contractors from simultaneously serving as technical performers. See Section 4, subsection IV, for additional eligibility requirements.

· All Principal Investigators nominated as IPAs are U.S. citizens, and all institutions associated with the abstract and full proposal (if requested by the Government) are U.S. institutions.

· The proposed concept is applicable to at least one research thrust area described in Section 4 of the RSO. Further, the abstract identifies the Technical Office and Thrust Area under which the proposed research falls.

· The proposed concept is relevant to DARPA’s current investment portfolio and the RSO thrust areas. DARPA's current research areas are found at https://www.darpa.mil/research/programs.

· The proposed concept investigates an innovative approach capable of enabling revolutionary advances, rather than primarily resulting in evolutionary improvements to the existing state of practice.

· The proposed research has not already been completed (i.e., the research element is complete, but manufacturing/fabrication funds are required).

· DARPA or another Government agency: (1) has not previously funded, (2) is not currently funding, and (3) has not provided a positive funding decision for substantially the same proposed concept as the submitter’s proposed research.

TABLE OF CONTENTS

DARPA-PA-26-08

DARPA RSO ABSTRACT

Source Selection Sensitive – See FAR 2.101 and 3.104

DARPA-PA-26-08

DARPA RSO ABSTRACT

Source Selection Sensitive – See FAR 2.101 and 3.104

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.] 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?

· If applicable, what are the plans to deliver resilient software?

· In addition, provide the proposed technology transition strategy and the extent to which any proposed intellectual property (IP) rights will potentially impact the Government's ability to transition the technology.

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. Identify the principal investigators for the project and include a description of the team’s organization, including roles and responsibilities. Identify any]

Rough Order of Magnitude [Provide a cost estimate for resources (e.g., labor, materials) over the entire program (base + options).] Ensure the estimate is realistic and supported by the technical details provided in the abstract. At a minimum, the proposed price/ROM should include a high-level description and estimate of the resources required to accomplish the proposed effort, including labor categories, number of labor hours, types and quantities of materials, and other significant price drivers.

DARPA recognizes that undue emphasis on the ROM/Price Realism may incentivize submitters to offer low-risk concepts with minimal uncertainty or to staff the effort with junior personnel to be in a more competitive posture. DARPA discourages such strategies.

Bibliography [Provide a bibliography with links to relevant papers, references, reports, etc.]