Attachment_D_Proposal_Instructions_and_Volume_I_Template__Technical_and_Management_.docx

HR001124S0018: SURGE

Proposal Instructions and Volume I Template Use of this template is mandatory for all proposal submissions to this BAA. Proposers requesting a Procurement Contract or Other Transaction (OT) for Prototype must also include Attachments C, E, and F. Proposers requesting a Cooperative Agreement are not required to submit Attachment E; they must instead complete the SF 424 (R&R) through Grants.gov. (instructions here: Proposer Instructions: Grants/Cooperative Agreements). Proposals not meeting the format prescribed herein may not be reviewed. This document must include all components described herein and must be submitted in .pdf, .odx, .doc, or .docx formats.

All proposers must also use Attachment F (MS ExcelTM DARPA Standard Cost Proposal Spreadsheet) regardless of requested award type.

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 not smaller than 12 point. Font sizes of 8 or 10 point 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.

Technical and Management Volumes shall not exceed a maximum of 20 pages.

Table of Contents

Sections 8-15

Resumes (Optional)

References/Bibliography (Optional)

Technical Papers (Optional, no more than 3)

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 section. Proposals 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 proposal through the Broad Agency Announcement Tool (BAAT). For proposers requesting a cooperative agreement or Other Transaction for Research, full proposals must be submitted through grants.gov.

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:

Year 2: $ Year 3: $ Year 4: $ Total: $

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. See BAA Section VI.B.2 for further information.]

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

Attachment D: HR001124S0018 Volume I: Technical and Management Proposal Template Source Selection Sensitive – See FAR 2.101 and FAR 3.104

2 | Page

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?

· How much will it cost, and how long will it take?

· 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.] 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 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.] Capabilities [Describe organizational experience in 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.] Statement of Work (SOW) [Provide a detailed task breakdown by Contractor Fiscal Year citing specific tasks and their connection to the interim milestones and metrics, as applicable. Do not include proprietary information.

For each defined task and subtask, provide:

· A general description of the objective.

· A detailed description of the approach to be taken to accomplish each defined task/subtask.

· Identification of any tasks/subtasks that will involve human subjects or animals.

· Identification of any tasks/subtasks that will be performed on campus at a university.

· Identification (by name) of the primary organization (prime contractor, subawardee(s), consultant(s)) responsible for task/subtask execution.

· A measurable milestone (e.g., a deliverable, demonstration, or other event/activity that marks task completion).

· A definition of all deliverables (e.g., data, reports, software) to be provided to the Government in support of the proposed tasks/subtasks.

· Identification of the proposed classification for each task/subtask.

· For all tasks and subtasks proposed to be unclassified, identify if the task/subtask is proposed as fundamental research or controlled unclassified information (CUI).

· Provide a short explanation for why each task/subtask should be categorized as fundamental research or CUI.] Schedule and Milestones [Provide a detailed schedule showing tasks (task name, duration, work breakdown structure element as applicable, performing organization), milestones, and the interrelationships among tasks. The task structure must be consistent with that in the SOW. Measurable milestones should be clearly articulated and defined in time relative to the start of the project.] Management Plan [Provide a summary of the proposed team, including any subawardees/consultants and key personnel who will be executing the work. 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

Non-U.S. Individual:¨ Yes¨ No FFRDC: ¨ Yes ¨ No Government Entity:¨ Yes¨ No

Subawardees/Consultants

Non-U.S. Individual:¨ Yes¨ No FFRDC: ¨ Yes ¨ No Government Entity:¨ Yes¨ No

Non-U.S. Individual:¨ Yes¨ No FFRDC: ¨ Yes ¨ No Government Entity:¨ Yes¨ No

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.] 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? ¨ No ¨ Yes [If yes, provide the information outlined below.]

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 you answered “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; and

· 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, 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] Representations and Certifications

· For proposers requesting procurement contracts, please download, complete, and submit within this volume “Procurement Contracts Reps and Certs 2024-01-25 Fillable Template” available at the following link: Procurement Contracts

· For proposers requesting Other Transactions, please download, complete, and submit within this volume “2-SAMPLE OT certifications” available at the following link: DARPA Representations and Certifications

· For proposers requesting Cooperative Agreements, please download, complete, and submit within this volume “Cooperative Agreement Grants - Certifications” available at the following link: Proposer Instructions: Grants/Cooperative Agreements Intellectual Property (IP) Please provide the following information, as applicable. Note: The Government will assume unlimited rights to all IP not explicitly identified as restricted in the proposal.

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

Asserted Rights Category

Name of Person Asserting Restrictions

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

COMMERCIAL

Asserted Rights Category

Name of Person Asserting Restrictions

b. Patents Does the proposed effort involve using patented inventions that are owned by or assigned to the proposing organization or individual? ¨ No ¨ Yes [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).] Bibliography (Optional) [A brief (no more than 5 pages) bibliography may be provided with links to relevant papers, references, reports, etc.]