APM Enclosure 2 Proposer Checklist

DARPA-PS-26-141

APM

Enclosure 2
Proposer Checklist

The Proposer Checklist serves as a tool for proposers in the preparation of the full proposal against this solicitation. The Proposer Checklist is for informational purposes only and is intended to aid proposers in compiling submissions. The content of DARPA-PS-26-141 and its Attachments takes precedence over this informational aid. It is the responsibility of the proposer to follow all submission requirements, regardless of whether they are reproduced in this Proposer Checklist or not. Does your proposal contain the following?

I. Core Proposal Volumes & Attachments

Attachment B: Proposal Summary Slide
Attachment C: Volume I: Technical and Management
Oral Presentation slides
Attachment D: Volume II: Price Proposal
Attachment E: Price Detail Spreadsheet
Attachment F: Other Transaction Certification
Attachment G: Task Description Document (TDD)
Attachment H: Schedule of Milestones and Payments
For each subawardee (as applicable):
Subawardee’s Volume II: Price Proposal
Subawardee’s Price Detail Spreadsheet
II. Intellectual Property and Commercialization
Does your proposal package contain the required IP assertions, commercialization strategy, and data rights documentation as outlined in Information to validate compliance is provided as outlined in Paragraph 8 of Attachment C: DARPA-PS-26-141 Volume I: Technical and Management Proposal Template? Ensure your submission addresses each of the following:

Does your proposal articulate a commercialization and transition strategy that leverages your retained ownership of newly developed IP to advance both defense applications and commercial scaling? Does your proposal explicitly confirm acceptance of the Government’s expectation to receive, at a minimum, Government Purpose Rights (GPR) for all technical data, computer software, processes, hardware designs, datasets, and documentation first generated, developed, or delivered under the Agreement? Does your submission confirm that all deliverable data includes sufficient Form, Fit, and Function (FFF) data to permit complete test, evaluation, and verification of deliverables by the Government team and its support contractors? Have you identified and outlined all pre-existing technical data, software, datasets, or other BIP proposed for use during performance or required to test, evaluate, or transition program deliverables? Are all restrictions and the specific basis for each restriction clearly identified? (Note: Listing BIP does not constitute Government acceptance of proposed restrictions.)