A-2_Abstract_Instructions_and_Submission_Template__Final_.docx

A-2 Abstract Instructions and Submission Template Securing Artificial Intelligence for Battlefield Effective Robustness (SABER)

Use of this template is required for all abstract submissions to this BAA. Proposers must include all information in the Abstract Instructions and Submission Template (this documents) and the Abstract Summary Slide Template to constitute a full abstract submission.

The Abstract Instructions and Submission Template (this document) must include all components described herein and must be submitted in PDF or Microsoft Word formats under the file naming convention “Organization_A-2_Abstract Submission”.

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.

Table of Contents

Bibliography

Proposers are strongly encouraged to submit an abstract before submitting a full proposal. See Section III, Abstract Guidelines in the BAA for abstract feedback information.

REMINDER: 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, 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 Section 1, Overview Information section of the BAA. 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. Regardless of instrument type desired, abstracts should not be submitted through Grants.gov.

COVER SHEET

[PRIME ORGANIZATION LOGO optional]

Abstract Title

☐ TT1.2

Proposer Organization

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

HR001125S0009

HR001125S0009: 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. The Abstract Instructions should also be deleted prior to abstract submission.]

Goals and Impact [Describe the proposed approach, specifically 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:

· How does the proposed effort address the goals of the program?

· Why do you think it will be successful?

· What are the key technical challenges and how will they be addressed?

· How much will it cost (rough order of magnitude)?]

In answering the above questions, potential proposers are reminded to address and demonstrate the following:

· TT1.1: Exquisite, targeted technologies in a domain that will enable successful implementation of AI attack effects. These are diverse and dependent on your proposed methods; however, useful components include technologies for high quality printing/manufacturing, light projection, offensive cyber, EW, as well as others.

· TT1.1: A concept of operation, documenting how your technology will enable an adversarial AI attack effect against an AI-enabled battlefield system pipeline and justifying its operational requirement.

· TT1.2: The ability to contribute novel methods of AI attack effects that account for the dynamics of an operational environment as well as a particular AI attack vector for the adversarial attack. Experience in solving more traditional Sim-to-Real problems in AI may also be a strength in this area.

Capabilities and Team [Provide a summary of the expertise of the team, including subawardees and key personnel. Identify a principal investigator for the project and include a brief description of the team’s organization, including high-level roles and responsibilities.]

Potential proposers are reminded to address and demonstrate the following in responding to this section:

· TT1.1/TT1.2: Experience in the development/implementation of practical counter-AI, particularly over reduced access threat models such as gray, black, and hidden box methods.

· TT1.1: A strong team of developers who can interface with TT1.2/Government for employment.

· TT1.2: Experience in the development of AI-enabled systems for deployment in real world settings. Experience in developing toolkits via the integration of other techniques/tools.

· TT1.2: Excellent software engineering practices pulling together various systems originally un-intended to work together.

Bibliography [Provide a brief (no more than 2 pages) bibliography with links to relevant papers, references, reports, etc.]