Attachment_S1-1_Proposal_Instructions_with_Technical_and_Mangement_Proposal_Template_PWND2.docx

HR001124S0037: Provably Weird Network Deployment and Detection (PWND²) Proposal Instructions with Technical and Management Submission Template

Use of this template is strongly encouraged for all proposal submissions to this BAA. Proposers must submit Stage 1 Attachments, to include the Proposal Instructions with Technical and Management Submission Template (this document), Proposal Summary Slide, Kick-Start OT Price Proposal, Basis of Estimate (BOE), and a statement of acceptence to the terms and conditions (Kick-Start OT Agreement Articles) to constitute a full Stage 1 proposal submission. The completed Proposal Instructions with Technical and Management Template shall include performance for all Stages (Months 1-30). Proposals not meeting the format prescribed herein may not be reviewed.

This document must include all components described herein. The Proposal Summary Slide must be submitted in Microsoft PowerPoint format. Proposal Instructions with Technical and Management Template (this documet) and the BOE must be submitted in PDF or Microsoft Word formats under the file naming convention “Organization_Technical and Management Proposal”.

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-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 Proposal Instructions with Technical and Management Template (this documet) 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.

Official transmittal letter

Table of Contents

Appendix A

References/Bibliography (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 Section 1: Overview Information in the BAA. 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

☐ Large Business ☐ Small Disadvantaged Business ☐ Other Small Business

☐ HBCU

☐ MI

☐ Other Educational ☐ Other Nonprofit

Proposer Reference Number, if any

Address:

Telephone:

Email:

Address:

Telephone:

Email:

Award Instrument Requested

Choose the preferred award instrument your organization would like to negotiate for Months 7-30:

☐ Procurement contract (FFP, Cost Reimbursement or CPFF) ☐ Other Transactions (OT) Agreement (negotiation of additional terms and conditions of the Kick-Start Agreement, extending the scope of the Agreement into Months 7-30).

NOTE: Upon selection of Stage 1 technical proposal, selected proposers may receive a Kick-Start OT Agreement to support Months 1-6 of the PWND2 program.

Place(s) of Performance

Period(s) of Performance

Organization:

Organization Type:

Months 7 - 30: $ 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

Months 7 – 30:

Table of Contents

HR001124S0037 Proposal Instructions with Technical and Management Template Source Selection Sensitive – See FAR 2.101 and FAR 3.104

[Content requirements are stated in blue font and should be deleted prior to proposal submission. This document must address Months-1-30 of the PWND² program unless otherwise stated.] 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?

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

The summary must 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.] Impact [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 the deliverables associated with the proposed project and any plans to commercialize the technology, transition it to a customer, or further the work.] Technical Plan and Rationale [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. Clearly explain why the proposed technical plan will work. 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 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. 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, showing a concise summary of their qualifications, discussion of previous accomplishments, and work in this or closely related research areas.] 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) for Months 7 - 30 The Task Description Document (TDD) for Months 1 – 6 are covered in the Kick-Start OT, Attachment S1-3.

[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, 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.] Schedule and Milestones [Provide a schedule showing the tasks from the SOW and the measurable milestones identified in the technical plan. Identify critical dependencies. The schedule should be defined in time relative to the start of the project.]

APPENDIX A

Key Personnel Please use the table below to identify all key personnel for the project. Indicate the level of effort in terms of percentage of time to be expended by each person 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.

Prime

Non-U.S. Individual: ☐Yes ☐No

LOE

LOE

LOE

Sub awardees/Consultants

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

LOE

LOE

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

LOE

LOE

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

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 12.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 _________________________

· Whether the 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).