Proposal_Instructions_and_Volume_I_Template_for_Technical_and_Management__MOCHA_.docx

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

HR001124S0035: MOCHA

Proposal Instructions and Volume I Template

Use of this template is strongly encouraged for all proposal submissions to this BAA.. Proposals not meeting the format prescribed herein may not be reviewed.

This document must include all components described herein.

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, single-spaced, and font size no 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 25 pages.

Official transmittal letter

Table of Contents

Appendix A

Resumes (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 https://www.darpa.mil/work-with-us/proposer-instructions 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:

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

NOTE: Instructional text in blue font may be deleted.

Official Transmittal Letter [Attach the official transmittal letter from the prime proposer organization.] Executive Summary [Provide a top-level synopsis of the proposed project, addressing the following:

Innovative claims for the proposed research. Succinct description of the uniqueness and benefits of the proposed approach relative to the current state-of-art and alternate approaches.

Technical rationale, key technical challenges, technical approach, and constructive plan for accomplishment of technical goals in support of innovative claims and deliverable creation.] Technical Plan [Present a detailed technical approach, enhancing and completing that presented in the Executive Summary. Discuss the technical risks and challenges inherent in the approach and possible mitigation strategies for addressing potential problems. Discuss other research in the area proposed, indicating comparative advantages and disadvantages of the proposed effort. Discuss how the proposed approach will lead to incorporation of the technology into a sustainable compiler ecosystem after the program ends. 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 sub awardees/consultants and key personnel who will be executing the work. 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, the principal investigator (PI), co-PI, and program manager (if applicable) for each team member to include subcontractor’s PI, co-PI, and program manager, and key personnel with the amount of effort to be expended by each person during the project (for faculty, indicate whether university appointment is hard money or soft money). Provide a detailed plan for coordination, including explicit guidelines for interaction among collaborators/sub awardees of the proposed project. Include risk management approaches. Describe any formal teaming agreements that are required to execute this project.] 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.

NOTE: all key personnel proposed in this section should be consistent with the key personnel stated in Appendix A.] 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.] 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. NOTE: this solicitation does not anticipate Human Subjects Research, Animal Subjects Research or Controlled Unclassified Information (CUI). Proposers should contact the Agency Point of Contact (POC) to describe why the inclusion of such research is necessary to complete the proposed scope of work.

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 be performed on campus at a university.

· Identification (by name) of the primary organization (prime contractor, sub-awardee (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.

· Provide a short explanation for why each task/subtask should be categorized as fundamental or non-fundamental research.] 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.]

APPENDIX A

1. Key Personnel [Please use the table below to identify all key personnel for the project.] Prime

Sub awardees/Consultants

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

[NOTE: Per the BAA, FFRDCs and Government entities should first contact the Agency POC listed in the BAA Overview section prior to submitting an abstract and/or proposal.]

Are any of the team member organizations (prime or sub awardee) 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 sub awardee 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 sub awardee 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 (sub awardee, 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 sub awardee 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] Bibliography (Optional) [A brief (no more than 5 pages) bibliography may be provided with links to relevant papers, references, reports, etc.] Representations and Certifications

· For proposers requesting procurement contracts, please download, complete, and submit within this volume “Procurement Contracts Reps and Certs 2024 Fillable Template” available at the following link: https://www.darpa.mil/work-with-us/procurement-contracts

· For proposers requesting Other Transactions, please download, complete, and submit within this volume “2-SAMPLE OT certifications” available at the following link: https://www.darpa.mil/work-with-us/reps-certs

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