A1_-_DICE_Abstract_Template.docx

COVER SHEET

[PRIME ORGANIZATION LOGO optional]

Abstract Title

☐ TA 3

Proposer Organization

Mailing Address:

Telephone:

Email:

Mailing Address:

Telephone:

Email:

Organization:

Technical POC Name:

Organization:

☐ Procurement contract ☐ OT for Prototype ☐ OT for Research ☐ Cooperative agreement

Estimated Period of Performance

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

SAM.gov Unique Entity ID (UEI)

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

Page Limit Requirement:

· TA1 & TA2 abstracts shall not exceed a maximum of 7 pages.

· TA3 only abstracts shall not exceed a maximum of 7 pages.

The above stated page limit does NOT include the following:

· Abstract Coversheet

· Table of Contents

· Technical Papers

· Bibliography (Optional)

Formatting Requirements: All submissions must be typed in English on 8.5" by 11" pages using 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 prior to abstract submission.

Security Requirements: TA1 and TA2 abstracts must be written at the UNCLASSIFIED level. TA3 abstracts may be written at the UNCLASSIFIED or Controlled Unclassified (CUI) level.

Submission Requirements: Abstract submissions must be submitted in PDF or Microsoft Word formats. The recommended file naming convention is “Organization Name_DICE 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 or CUI abstracts must be submitted via DARPA’s Broad Agency Announcement Tool (BAAT). Please visit Proposer Instructions and General Terms and Conditions for specific information regarding submission methods through BAAT. Please note, BAAT is a method of secure transmission for CUI documentation. Submissions sent through other mediums, channels, or after the prescribed deadline will not be accepted. Comment by Mack, Jennifer (contr-i2o): We just need to make sure this is consistent with Section 3.1 of the BAA.

Table of Contents

HR001126S0010: DICE Abstract Source Selection Sensitive – See FAR 2.101 and FAR 3.104

[Content requirements are stated in blue font and should be deleted prior to abstract submission.] 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 [Refer to the BAA for all elements that should be addressed with the Technical Plan. The description should also include:

· Links to any online demonstrations or repositories from relevant prior work by the team that represents an existing technical capability that will be leveraged by the proposed approach. For software artifacts, please identify any associated licenses.

· Include a description of computational capability with the team to run experiments with a large number of agentic AI systems for their technical approach. This description should include any relevant architecture details (e.g., number and kind of graphic processing units, memory, and intranode/internode interconnects) that are relevant to the proposed technical approach. Proposals can also include description of any access to external compute such as (but not limited to) national compute initiatives.] 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.] Cost and Schedule [Provide a cost estimate for resources (e.g. labor, materials) and any subawardees over the entire program (base + options). Please provide a breakdown of the cost estimate by each phase with the estimated cost of computing for each phase identified separately. The proposers are encouraged to review the state of art and recent technical breakthroughs (such as efficient inference frameworks and emergence of small reasoning models) when estimating compute cost.] Publications [Include a list of up to 10 of the most relevant publications (including technical reports) published in 2016 or later, with the author list highlighting the names of key personnel who are included on the proposed team.] Bibliography [Provide a brief bibliography with links to relevant papers, references, reports, etc.]