DARPA-PA-27-02_Protein_Palace_Attachment_C_Proposal_Instructions_and_Volume_I_Template_Technical_and_Management.docx

Attachment C: DARPA-PA-27-02 Volume I: Technical and Management Proposal Template Competition Sensitive Information – see 41 U.S.C. 2102 DARPA-PA-27-02: Protein Palace Proposal Instructions and Volume I Template Use of this template is mandatory for all proposal submissions to this PA. Proposers must include Attachments B, C, D, E, F, G, H, and the oral presentation slides to constitute a full proposal 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.

Proposers are encouraged to submit concise but descriptive proposals. Specific examples of problems, approaches, or goals are preferred to qualitative generalities. The Government will not consider pages in excess of the page count limitations, as described herein. Proposals with fewer than the maximum number of pages will not be penalized. Additional information not explicitly called for in the Technical and Management Volume must not be submitted with the proposal but may be included as links in the bibliography. Such materials will be considered for the reviewers’ convenience only and not evaluated as part of the proposal.

Oral Presentations Oral presentations will be held in-person and are tentatively scheduled during the dates and times listed in the Overview Information section of the PA. DARPA will notify proposers of their scheduled time via email. Slides cannot be modified between proposal due date and oral presentation.

· The government will not review or evaluate any information that is contained within the notes section of the PDF or PowerPoint slides. All pertinent information must be included in the main body of the presentation slides, and the content presented orally will be the basis for evaluation.

· The government intends to record the oral presentation for internal documentation purposes. The recordings will not be provided to proposers.

· The oral presentation shall not exceed 20 slides and and must be submitted in PDF or Microsoft PowerPoint format. Proposers will be allotted 30 minutes for presentations. Proposers must present their oral presentation slides in real time. The use of a pre-recorded version of their presentation, whether in audio or video form, is not allowed.

· The oral presentation content should follow similar information content as the written component. A presentation template is not provided, but a strong emphasis on the innovative claims, technical approach, and discussion of the technical risks and mitigation strategies is encouraged. A section on how the proposed solution will achieve the program metrics is required. All claims must be justified using quantitative analysis and supporting evidence derived from modeling, simulation, and/or prior experimental work.

· Immediately following the oral presentation, there will be a 30-minute interactive Q&A session to address questions from a government evaluation panel. The government panel may ask questions on any aspect of the proposal during the Q&A session. Answers to questions from the panel cannot be deferred to later time, and proposers cannot modify their proposals in response to the Q&A session.

Written Proposal Technical and Management Volumes shall not exceed a maximum of 15 pages in total.

All text, technical figures, tables, and charts in:

· Proposal Summary

· Goals and Impact

· Technical Plan

· Management Plan

· Personnel, Qualifications, and Commitments

· Capabilities

· Cover Sheet

· Table of Contents

· Official Transmittal Letter

· Requirements for teams that include Government Entities and/or Federally Funded Research and Development Centers (FFRDCs)

· Organizational Conflict of Interest Affirmations and Disclosure

· Novelty of Proposed Work

· References/Bibliography (Optional)

· Intellectual Property (IP)

· Resumes (Optional)

· Technical Papers (Optional)

Proposals 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 section. Proposals received after this time and date may not be reviewed. Please visit Proposer Instructions and General Terms and Conditions and see Enclosure 2 for instructions on how to submit your proposal through the Broad Agency Announcement Tool (BAAT).

COVER SHEET

[PRIME ORGANIZATION LOGO]

Proposal Title

Proposer Organization

Proposer Reference Number, if any

Address:

Telephone:

Email:

Address:

Telephone:

Email:

Place(s) of Performance

Period(s) of Performance

Months

Organization:

Organization Type:

Phase 2: $ Total: $

If YES, you must check the box below to certify compliance:

· [ ] I certify that a Letter of Intent (LOI) to commit to technology transition, signed by the division director of the Federal Laboratory, FFRDC, or UARC, is included.

If YES, you must check the box below to certify compliance:

I certify that our team has contacted the agency POC to verify eligibility and confirm the entity is not on the prohibited IV&V partner list. [ ]

Current CMMC Certification Level 1 or Level 2 (Self-Certification)

SAM.gov Unique Entity ID (UEI)[endnoteRef:2] [2: The SAM-generated UEI becomes the official identifier for doing business with the U.S. Government. This replaces DUNS.]

Taxpayer identification number (TIN)[endnoteRef:3] [3: See https://www.irs.gov/individuals/international-taxpayers/taxpayer-identification-numbers-tin for information on requesting a TIN. Note, requests may take from 1 business day to 1 month depending on the method (online, fax, mail).]

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

Administration Office POC at Defense Contract Management Agency (DCMA)[endnoteRef:5] or Office of Naval Research (ONR)[endnoteRef:6], if known [5: https://pubapp.dcma.mil/CASD/CasdSearch.do.] [6: http://www.onr.navy.mil/Contracts-Grants/Regional-Contacts.aspx.]

Name:

Address:

Telephone:

Audit Office POC at Defense Contract Audit Agency (DCAA)[endnoteRef:7], if known [7: http://www.dcaa.mil/Home/Locator?title=Locator]

Name:

Address:

Telephone:

Date Proposal was Prepared

Proposal Validity Period (minimum 120 days)

Table of Contents

Official Transmittal Letter Attach the official transmittal letter from the prime proposer organization.

Proposal Summary Provide a top-level synopsis of the proposed project, including 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?

· Who will care, and what will be the impact if the work is successful?

· What is new in your approach, and why do you think it will be successful?

The summary should include a description of the key technical challenges, a concise review of the technologies proposed to overcome these challenges and achieve the project’s goal, and a clear statement of the novelty and uniqueness of the proposed work.

A target protein panel with the proposed eight different protein categories and one challenge protein, as outlined below, must be provided.

Challenge protein:

Goals and Impact Describe what you are trying to achieve and the 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 uniqueness and benefits of this project in the context of the state of the art, alternative approaches, and other projects from the past and present. Describe how the proposed project is revolutionary and how it significantly rises above the current state of the art. Describe the deliverables associated with the proposed project and any plans to commercialize the technology, transition it to a customer, or further the work. Discuss the mitigation of any issues related to the sustainment of the technology over its entire lifecycle, assuming the technology transition plan is successful.

Technical Plan Outline and address technical challenges inherent in the approach and possible solutions for overcoming potential problems. Demonstrate a deep understanding of the technical challenges and present a credible (even if risky) plan to achieve the project’s goal. Discuss mitigation of technical risk. Provide appropriate measurable milestones (quantitative if possible) at intermediate stages of the project to demonstrate progress and a plan for achieving the milestones. List Government-furnished materials or data assumed to be available.

Management Plan Provide a summary of the proposed team, including any subawardees/consultants and key personnel who will be executing the work (please use table below). Identify a principal investigator (PI) for the project. Provide a clear description of the team’s organization, including an organization chart that illustrates, as applicable, the relationship of team members, unique capabilities of team members, task responsibilities of team members, teaming strategy among the team members, and key personnel with the amount of effort to be expended by each person during the project. Provide a detailed plan for coordination, including explicit guidelines for interaction among collaborators/subawardees of the proposed project. Include risk management approaches. Describe any formal teaming agreements that are required to execute this project.

Prime

Subawardees/Consultants

Personnel, Qualifications, and Commitments List key personnel (no more than one page per person), showing a concise summary of their qualifications, discussion of previous accomplishments, and work in this or closely related research areas. Indicate the level of effort in terms of hours to be expended by each person during each contract year and other (current and proposed) major sources of support for them and/or commitments of their efforts. DARPA expects all key personnel associated with a proposal to make substantial time commitment to the proposed activity, and the proposal will be evaluated accordingly. It is DARPA’s intention to put key personnel conditions into the awards, so proposers should not propose personnel that are not anticipated to execute the work.

Capabilities Describe the organizational experience in the relevant subject area(s), existing intellectual property, or specialized facilities. Discuss any work in closely related research areas and previous accomplishments. Identify other Government solicitation(s) to which this concept has been proposed. If applicable, state whether funding or a positive funding decision has already been received and from which agency.

Requirements for teams that include Government Entities and/or Federally Funded Research and Development Centers (FFRDCs) Are any of the team member organizations (prime or subawardee) a Government entity or FFRDC? If yes, provide the information outlined below.

No Yes

a. Proof of Eligibility to Propose Provide documentation citing the specific authority that establishes the applicable team member’s eligibility to propose to Government solicitations; include: (1) statutory authority; (2) contractual authority; (3) supporting regulatory guidance; and (4) evidence of agency approval for applicable team member participation. For FFRDCs, this documentation must be in the form of a letter on official letterhead from their sponsoring organization and must also include a statement of compliance with the terms and conditions of the associated FFRDC sponsor agreement, as applicable.

b. Statement of Unique Capability Provide a statement that demonstrates the work to be performed by the Government entity or FFRDC team member is not otherwise available from the private sector.

Organizational Conflict of Interest Affirmations and Disclosure In accordance with the requirements of the BAA, provide the following information.

a. Are any of the proposed individual team members or their respective organizations (whether prime or subawardee or consultant) currently providing SETA, A&AS or similar support to DARPA?

No Yes

b. Did any of the proposed individual team members or their respective organizations (whether prime or subawardee or consultant) provide SETA, A&AS or similar support to DARPA within one calendar year of this proposal submission?

No Yes If yes to 8.a OR 8.b, provide the following information for each applicable team member:

· The name of the DARPA office receiving the support

· The prime contract number

· Identification of proposed team member (subawardee, consultant) providing the support

· An OCI mitigation plan in accordance with FAR 9.5

c. Are there any other potential Organizational Conflicts of Interest involving any of the proposed individual team members or their respective organizations (whether prime or subawardee or consultant)?

No Yes If yes to 8.c, provide the following information for each applicable team member:

· Identification of applicable team member; and

· An OCI mitigation plan in accordance with FAR 9.5.] Novelty of Proposed Work Has the proposed work been submitted to any other Government solicitation?

No Yes If yes, provide the following information:

· Solicitation number ________________________

· Agency _________________________

· Proposed work has already received funding or a positive funding decision.

No Yes Decision pending Bibliography (Optional) A brief (no more than 5 pages) bibliography may be provided with links to relevant papers, references, reports, etc.

Intellectual Property (IP) Performers shall comply with the intellectual property provisions set forth in DARPA Program Announcement DARPA-PA-27-02, Section I, Article F, Intellectual Property. Background Intellectual Property (Background IP) includes intellectual property developed or acquired before the resulting Agreement, as well as intellectual property developed independently of performance under the Agreement without the use of Government resources. Background IP includes such intellectual property when it is used in performing the Agreement or is necessary to use, test, evaluate, reproduce, or transition a deliverable. The delivery of Background IP, or its incorporation into a deliverable, does not by itself convert that Background IP into Foreground Intellectual Property.

a. Technical Data and Computer Software Are you asserting any IP restrictions on any technical data or non-commercial computer software that will be delivered to the Government?

No Yes If yes, list all proprietary claims to results, prototypes, deliverables or systems supporting and/or necessary for the use of the proposed research, results, prototypes and/or deliverables. Provide a short summary for each item asserted with less than unlimited rights that describes the nature of the restriction and the intended use of the intellectual property in the conduct of the proposed research. Use the following format for these lists.

NONCOMMERCIAL

Are you proposing any commercial software that will be delivered to the Government? If yes, please provide licensing terms.

No Yes

COMMERCIAL

b. Patents Does the proposed effort involve using patented inventions that are owned by or assigned to the proposing organization or individual? If yes, provide documentation proving ownership or possession of appropriate licensing rights to all patented inventions to be used for the proposed project. If a patent application has been filed for an invention, but it includes proprietary information and is not publicly available, provide documentation that includes: the patent number, inventor name(s), assignee names (if any), filing date, filing date of any related provisional application, and summary of the patent title, with either: (1) a representation of invention ownership; or (2) proof of possession of appropriate licensing rights in the invention (i.e., an agreement from the owner of the patent granting license to the proposer).

No Yes