I2O_Office_Wide_Abstract_Template.docx

COVER SHEET

Abstract Title

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.

ABSTRACT GUIDELINES: Use of this template is strongly encouragedrequired for all 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 5 pages. This page limit does NOT include the following:

· Abstract Coversheet

· Table of Contents

· Bibliography (Optional)

· Technical Papers (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.

Submission Requirements: Abstract submissions must be submitted in PDF or Microsoft Word formats. The recommended file naming convention is “Organization Name_I2O OW 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 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.

CLASSIFIED abstracts must be submitted in accordance with the requirements, instructions, and procedures contained within the Classified Submissions, Instructions, and Procedures attachment zip file. Classified submissions must NOT be submitted through the (BAAT) or Grants.gov.

TABLE OF CONTENTS

HR001126S0001

I2O OW 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?

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

Cost and Schedule [Provide a cost estimate for resources (e.g. labor, materials) and any subawardees over the entire program (base + options).] Bibliography [Provide a bibliography with links to relevant papers, references, reports, etc.]