DARPA-PS-26-126_RAAPTR_Attachment_B_Abstract_Instructions_and_Template.docx

Attachment B: DARPA-PS-26-126 Abstract Competition Sensitive Information – Distribution with Agreements Officer’s authorization only Program Solicitation DARPA-PS-26-126: RAAPTR Abstract Instructions and Template Use of this template is mandatory for all abstract submissions to this Program Solicitation (PS). Proposers must include Attachment B to constitute a full abstract submission. 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 points. Font sizes of 8 or 10 points may be used for figures, tables, and charts.

Abstracts shall not exceed a maximum of 7 pages.

All text, figures, and tables in:

· Use Case

· Architecture Approach

· Photonics Approach

· Program Deliverables

· Team Structure and Proposer Capabilities

· Cover Sheet

· Table of Contents

· Bibliography

· Technical Papers (Optional, no more than 3)

Proposers must submit an abstract before submitting a full proposal. 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 per the instructions outlined herein and received by DARPA no later than the due date and time listed in the Overview Information of DARPA-PS-26-126. Abstracts received after this time and date may not be reviewed.

Please visit Proposer Instructions and General Terms and Conditions and review Attachment L for instructions on how to submit your abstract through the Broad Agency Announcement Tool (BAAT).

ABSTRACT COVER SHEET

[PRIME ORGANIZATION LOGO]

Abstract Title

Proposer Organization

Proposer Organization Commercial and Government Entity (CAGE) code[footnoteRef:2] [2: A CAGE Code identifies companies doing or wishing to do business with the Federal Government.]

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

Use Case (~1 page suggested) Clearly describe how the proposed project will advance the goals of the RAAPTR program. Identify and describe the proposed use case and host platform that drive the development of the RAAPTR architecture. Include notional derived requirements from the proposed application onto the oscillator and other RAAPTR hardware. Identify the envisioned platform and mission domain for the proposed application.

Architecture Approach (~1 page suggested) Describe the analog devices planned for development or procurement. Describe the planned scope of digital algorithm development, if proposed.

Photonics Approach (~2 – 3 pages suggested) Describe the method for microwave generation and general approach for photonic oscillator development. Summarize the current status of photonic oscillator development that will comprise the starting point for RAAPTR development and include preliminary data if available. Describe the expected additional optical components and functions that are intended for incorporation into the RAAPTR architecture, if proposed.

Program Deliverables Describe the expected format of program hardware deliverables, including the photonic oscillator, breadboard prototype, and brassboard prototype.

Team Structure and Proposer Capabilities (~0.5 – 1 page suggested) Detail why the proposer believes their team can succeed at achieving the program goals if selected to participate in the RAAPTR program. The proposer may include past experience, organizational capabilities, team members’ qualifications, or anything else that demonstrates competence in developing the proposed technology, managing the project, and pursuing transition.

Bibliography Provide a list of citations, references, or end notes. References do not count against the page limit.