HR001126S0011-Amendment-02.pdf

Broad Agency Announcement Information Processing Techniques

Office (IPTO)

IPTO Office-Wide

HR001126S0011

June 22, 2026

Amendment 01

This publication constitutes a Broad Agency Announcement (BAA) as contemplated in Federal Acquisition Regulation (FAR) 6.102(d)(2) and 35.016 and 2 Code of Federal Regulations (CFR) § 200.203. Any resultant award negotiations will follow all pertinent laws and regulations, and any negotiations and/or awards for procurement contracts will use procedures under FAR 15.4, Contract Pricing, as specified in the BAA.

HR001126S0011

Amendment 01

Amendment 01 updates:

• Agency Point of Contact information

• Conforming submission definition

• Abstract comprehensive evaluation criteria

• Links to Model Contracts, OT Agreements, and Cooperative Agreements

• IPTO OW Abstract Template [Required] –Requires a SAM.gov Unique Entity ID (UEI) to be provided at the time of abstract submission

• Update to the Potential Contribution and Relevance to the DARPA Mission proposal evaluation criteria.

Removes:

• Removal of the IPTO OW Proposal Summary Slide from the required proposal submission documents

All changes are highlighted in yellow.

CONTENTS

1. Overview Information

2. Funding Opportunity Description

3. Security

3.1 Classified Work

3.3. Controlled Unclassified Information (CUI)

3.4 Cybersecurity Maturity Model Certification (CMMC) Requirements

3.4.1 Applicable to Procurement Contracts (FAR/DFARS-based) under this BAA

3.4.2 Applicable to OT Agreements under this BAA

3.5 DARPA Fundamental Research Risk-Based Security (FRRBS)

3.5.1 DARPA FRRBS Review

3.5.2. DARPA FRRBS Required Documents

4. Submission Information

4.1 Conforming Submissions

4.2 Non-conforming Submissions

5. Abstracts [REQUIRED]

5.1 Abstract Submission Requirements

5.2 Abstract Content and formatting Requirements

5.3 Abstract Basis of Evaluation

5.4 Abstract Feedback

6. Proposals

6.1 Proposal Submission Requirements

6.2 Proposal Content and Formatting Requirements

6.3 Model Contracts and Model OT Agreements (PROPOSAL SUBMISSION ONLY)

6.4 Common Disclosure Forms for FRRBS Review (PROPOSAL SUBMISSION ONLY) ..13

7. Proposal Basis of Evaluation

8. Special Considerations

1. OVERVIEW INFORMATION

• Federal Agency Name – Defense Advanced Research Projects Agency (DARPA), Information Processing Techniques Office (IPTO)

• Funding Opportunity Title – IPTO Office-Wide

• Announcement Type – Amendment

• Funding Opportunity Number – HR001126S0011

• Assistance Listing Number: 12.910

• Dates/Time - All Times are Eastern Time Zone (ET) o Posting Date: June 22, 2026 o Abstract Due Date: June 22, 2027, by 2:00 PM o Question Submittal Closes: June 22, 2027, by 2:00 PM o Proposal Due Date: By Invitation Only, a due date will be provided in the Invitation to Proceed.

• Anticipated Individual Awards - Multiple awards are anticipated.

• Types of Instruments that may be Awarded: Procurement Contract, Research Other

Transaction (OT) (10 U.S.C. § 4021), OT for Prototype Agreement (10 U.S.C. § 4022), Cooperative Agreement, Grant

• Resource Sharing Requirements: In accordance with 10 U.S.C. § 4021 and 4022, resource sharing may be required for Research OT or OT for Prototype Agreements

• NAICS Code: 541715

• Questions and Answers (Q&As): All administrative, technical, and award questions should be emailed to the Agency Point of Contact (POC) stated below. All questions must be written in English and must include the name of a designated point of contact.

• Agency POC The BAA Coordinator for this effort may be reached at: IPTO_OfficeWide@darpa.mil

DARPA/ IPTO

ATTN: HR001126S0011

675 North Randolph Street Arlington, VA 22203-2114

• Attachments to this Broad Agency Announcement (BAA):

• IPTO Office Wide Abstract Template

• IPTO Office Wide Proposal Templates Zip file

• Common Disclosures Forms Zip file

• Classified Submission Requirements, Instructions, and Procedures

2. FUNDING OPPORTUNITY DESCRIPTION

The Information Processing Techniques Office (IPTO) creates technological surprise through groundbreaking information science, technology development, and the delivery of fundamentally new information capabilities for national security. The office's current portfolio is centered on three primary thrust areas:

AI Innovation and Execution

We envision vastly more energy-efficient and assured artificial intelligence (AI) systems to advance asymmetric capabilities at the edge of the network and to provide trustworthy, understandable AI to warfighters where and when they need it. We also seek to mitigate risks of misalignment of machine actions and human interests.

Inherent Security and Privacy

We seek to create a new generation of systems that are inherently secure and inherently private, together with security and privacy tools that are more effective and more adaptable

– both in the moving-target and reactive senses – than current solutions. We aim to develop more trustworthy and resilient systems based on the fundamental principles of the cyber networking, computing, and storage environment, and to create an asymmetric advantage in cyberspace.

Resilient Megasystems

We aim to develop machine-derived abstractions and models that expose the governing principles of highly complex and interconnected systems – like supply chains and power grids – to identify hidden systemic risks and emergent properties, and to enable the precise targeting of interventions and the proactive assurance of mission-critical functions.

IPTO may also consider submissions outside these thrust areas if the proposal involves the development of novel capabilities having a promise to provide decisive information or computational advantage for the United States and its allies. IPTO seeks unconventional approaches that are outside the mainstream, challenge-accepted assumptions, and have the potential to change established practices radically. Proposed research should enable revolutionary advances in science, technology, or systems. Specifically excluded is research that primarily results in evolutionary improvements to the existing state of the art.

IPTO collaborates with other DARPA technical offices, in some cases acting as the recipient of significant emerging technologies and, in other cases, serving as a catalyst by identifying relevant new external technology trends and capabilities. Novel methods are sought to build technical communities and tap into sources of innovation both inside and outside traditional Department of War (DoW) performer communities. However, proposers may not propose work (1) they have already completed, nor (2) for which they have already received funding or a positive funding decision from DARPA or another Government agency. IPTO encourages efforts that are creative and agile both in terms of the technologies proposed and in the structure of the approach (e.g., shorter periods of performance).

The DoW is focused on delivering resilient software capability at the speed of relevance. Resilience implies software that is high-quality, secure, and able to withstand and recover in the face of challenging conditions. See “Department of Defense Software Modernization Strategy” November 2021, p. 2. DARPA’s preferred method to achieve this goal is the use of formal methods. “Formal methods” is an umbrella term for a range of mathematically rigorous techniques for producing software along with machine-checkable evidence that the software does what it is supposed to do and, perhaps more importantly, does not do what it is not supposed to do. Used judiciously, formal methods can eliminate virtually all exploitable vulnerabilities in software.

3. SECURITY

3.1 CLASSIFIED WORK

Proposed work could potentially involve access to or the generation of classified information.

Proposals that anticipate classified work will include a security plan. The security plan will detail how the team's security capabilities will enable the technical plan (facilities, key personnel clearances, networks, security personnel assigned to support), as well as identify possible security challenges and proposed solution(s) unique to the proposer team and technical plan. Common program security requirements and challenges include but are not limited to: classified information technology (IT) systems, classified facility construction and accreditation, operational security (OPSEC), Intelligence Oversight (IO), contracting/sub-contracting, foreign participation or materials utilization, range utilization and support plans (air, sea, land, space, and cyber), data dissemination, asset transportation, classified test activity, and classified material/asset disposition.

DARPA anticipates that proposals submitted in response to this BAA may generate or involve access to classified information. Classified submissions must NOT be submitted through BAAT or Grants.gov. Prior to generating any information that is or is suspected to be classified, contact IPTOsecurity@darpa.mil for specific instructions.

Proposers considering generating a proposal or abstract that may contain classified information must first be issued a solicitation Contract Security Classification Specification, DD Form 254 (DD-254) specifically for HR001126S0011 by DARPA. The generation of classified material for this solicitation is not authorized until a solicitation DD-254 for HR001126S0011 is issued by

DARPA.

For classified proposals or abstracts, proposers will ensure all industrial, personnel, and information systems processing security requirements are in place and at the appropriate level (e.g., Facility Clearance Level (FCL), Automated Information Security (AIS), Certification and Accreditation (C&A), and any Foreign Ownership Control and Influence (FOCI) issues are mitigated prior to submission. Additional information on these subjects can be found at https://www.dcsa.mil/.

3.3. CONTROLLED UNCLASSIFIED INFORMATION (CUI)

Proposal or abstract materials containing CUI shall only be processed, stored and transmitted on information systems that meet Cybersecurity Maturity Model Certification (CMMC) Level 2 mailto:IPTOsecurity@darpa.mil https://www.dcsa.mil/ requirements as described in Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7021.

If an unclassified submission contains CUI or the suspicion of such, as defined by Executive Order 13556 and 32 CFR Part 2002, the information must be appropriately and conspicuously marked CUI in accordance with DoDI 5200.48. Additionally, proposers shall adhere to all CUI safeguarding requirements enumerated here: https://www.darpa.mil/about/offices/contracts-management/proposer-general-terms#cui

3.4 CYBERSECURITY MATURITY MODEL CERTIFICATION (CMMC) REQUIREMENTS

3.4.1 Applicable to Procurement Contracts (FAR/DFARS-based) under this BAA

a. Awards resulting from this BAA that take the form of procurement contracts are subject to the CMMC requirements prescribed in 32 CFR Part 170 and DFARS 252.204-7021, Cybersecurity Maturity Model Certification Requirements.

b. CMMC Level 1 certification is required at proposal submission. The Government will designate the required CMMC level (1, 2, or 3) in each resulting contract based on the sensitivity of the information involved—Federal Contract Information (FCI) or CUI.

Additional details will be provided to proposers who receive an invitation to proceed to full proposal submission.

c. Proposers must demonstrate compliance with the applicable CMMC level at the time of contract award and maintain that level for the duration of contract performance.

d. CMMC requirements must be flowed down to all subcontractors whose performance involves processing, storing, or transmitting FCI or CUI on unclassified contractor or university systems.

3.4.2 Applicable to OT Agreements under this BAA

As codified in 32 CFR Part 170, the Cybersecurity Maturity Model Certification (CMMC) Program is designed to ensure Department of War (DoW) performers are properly safeguarding Federal Contract Information (FCI) and Controlled Unclassified Information (CUI) that is processed, stored, or transmitted on performer information systems. FCI and CUI must be protected to meet evolving threats and safeguard nonpublic, unclassified information that supports and enables the warfighter. The CMMC Program provides a consistent methodology to assess a defense contractor's implementation of required cybersecurity requirements. Proposers are encouraged to visit the DoW Chief Information Officer CMMC Resources & Documentation site for more information on CMMC: https://dodcio.defense.gov/cmmc/Resources- Documentation/.

This provision outlines the CMMC requirements pertaining to this solicitation, to include the required CMMC level and the corresponding proposal requirements. All DARPA efforts, including those involving Fundamental Research, at a minimum require prime performers and subcontractors to demonstrate compliance with CMMC Level 1, which focuses on the protection of FCI and consists of the security requirements that correspond to the 15 basic safeguarding requirements specified in 48 CFR 52.204-21.

https://www.google.com/url?q=https%3A%2F%2Fdodcio.defense.gov%2Fcmmc%2FResources-Documentation%2F https://www.google.com/url?q=https%3A%2F%2Fdodcio.defense.gov%2Fcmmc%2FResources-Documentation%2F

1. Required CMMC Level

The required CMMC level for this solicitation is:

• CMMC Level 2 (Self-Assessment). Level 2 focuses on the protection of CUI and incorporates the 110 security requirements specified in NIST SP 800-171 Rev 2.

2. Eligibility for Award

Proposers have two potential pathways to demonstrate compliance with the CMMC level required for this solicitation:

Compliance at Proposal Submission

To be eligible for award under this solicitation, the CMMC Unique Identifier (UID) associated with the prime proposer must reflect a current CMMC status (representing either Final or Conditional status) posted in the Supplier Performance Risk System (SPRS) indicating compliance at the required level above. Additionally, the proposer must have a current annual CMMC affirmation, submitted by an authorized Affirming Official, posted in SPRS. Further, as some entities may have multiple business segments, multiple CAGE codes, etc., DARPA must reasonably be able to relate the CMMC UID in SPRS to the proposing entity.

(Note: SPRS is housed within the Procurement Integrated Enterprise Environment https://piee.eb.mil; an additional resource on SPRS is located here:

https://dodcio.defense.gov/Portals/0/Documents/CMMC/CMMC-SPRS.pdf )

OR

Alternative Compliance Pathway:

For any prime proposer that does not, at the time of proposal submission, have a valid, unexpired CMMC status and current annual affirmation posted in SPRS for the required level above, the prime proposer must include within its proposal a CMMC Compliance Plan. This plan must:

• Detail a realistic path to achieve final or conditional status at the required CMMC level no later than the applicable Milestone as established in the Task Description Document

(TDD)

• Identify the specific information system(s) to be used, document current gaps against NIST SP 800-171 Rev 2, and provide a Plan of Action & Milestones (POA&M) for the closure of those gaps with targeted dates for assessment/affirmation.

• Acknowledge that no CUI shall be processed, stored, or transmitted on the performer's systems until the required CMMC status and annual affirmation are officially active in

SPRS.

Evaluation & Award Impact:

• The feasibility and schedule risk of the proposed CMMC Compliance Plan will be evaluated as part of the Overall Scientific and Technical Merit evaluation criterion.

• If selected for award, the agreed-upon compliance timeline will be incorporated as a binding milestone in the resultant Other Transaction agreement. Failure to meet https://piee.eb.mil/ https://www.google.com/url?q=https%3A%2F%2Fdodcio.defense.gov%2FPortals%2F0%2FDocuments%2FCMMC%2FCMMC-SPRS.pdf this milestone may result in remedies up to and including the immediate termination of the agreement.

(Note: this alternative pathway is only applicable to attaining compliance with CMMC Level 2 (Self-Assessment); as a prerequisite for award, all proposers must demonstrate compliance with CMMC Level 1 at the time of award)

3. Subcontractor Flow-Down

Prime Proposers are responsible for verifying subcontractor compliance. In the proposal, the prime proposer must attest that all subcontractors who will process, store, or transmit FCI or CUI under a resultant award will meet the applicable CMMC level required by 32 CFR § 170.23, and indicate how proposers will verify subcontractors’ status prior to subcontract award. The proposal must also describe the verification method the prime proposer will use to ensure subcontractors have the required CMMC status in SPRS prior to subcontract award.

Specifically:

If the Subcontractor will process, store, or transmit...

...the Subcontractor's Minimum Required CMMC Level is:

Federal Contract Information (FCI) only CMMC Level 1 (Self-Assessment)

Controlled Unclassified Information (CUI) The CMMC Level required by this solicitation

3.5 DARPA FUNDAMENTAL RESEARCH RISK-BASED SECURITY (FRRBS)

3.5.1 DARPA FRRBS Review

DARPA’s Fundamental Research Risk-Based Security Review Process (formerly Countering Foreign Influence Program (CFIP)) is an adaptive risk management security program designed to help protect the critical technology and performer intellectual property associated with DARPA’s research projects by identifying the possible vectors of undue foreign influence. DARPA will create risk assessments of all proposed senior/key personnel selected for negotiation of a fundamental research grant, cooperative agreement or OT Agreement award. The DARPA risk assessment process will be conducted separately from the DARPA scientific review process and adjudicated prior to final award. For additional information on this process, please visit Proposer Instructions: Grants/Cooperative Agreements.

Further, it is DoW policy that the publication of products of fundamental research will remain unrestricted to the maximum extent possible. National Security Decision Directive (NSDD) 189 defines fundamental research as follows:

'Fundamental research' means basic and applied research in science and engineering, the results of which ordinarily are published and shared broadly within the scientific community, as distinguished from proprietary research and from industrial development, design, production, and product utilization, the results of which ordinarily are restricted for proprietary or national security reasons.

https://www.darpa.mil/work-with-us/grant-cooperative-agreements https://www.darpa.mil/work-with-us/grant-cooperative-agreements

Proposers should indicate in their proposal whether they believe the scope of the research included in their proposal is fundamental or not. While proposers should clearly explain the intended results of their research, the Government shall have sole discretion to determine whether the proposed research shall be considered fundamental research, to select the award instrument type, regardless of the instrument type proposed, and to negotiate all instrument terms and conditions with selectees. Appropriate language will be included in resultant awards for non-fundamental research to prescribe publication requirements and other restrictions, as applicable. For additional information, please see - https://www.darpa.mil/about/offices/contracts-management/proposer-transactions.

All proposal submissions proposing fundamental research that are requesting a Grant, Cooperative Agreement, or OT Agreement must complete the FRRBS forms found in the proposal package as part of their proposal submission.

3.5.2. DARPA FRRBS Required Documents

As part of the proposal response to this solicitation proposers requesting a Grant, Cooperative Agreement, or OT Agreement must provide to the Government the forms listed below for all key personnel identified in the proposal:

• Common Form (CF) for Biographical Sketch

• CF for Current and Pending (Other) Support

Instructions for how to fill out the Common Disclosures Forms can be found through NSF.gov.

4. SUBMISSION INFORMATION

This solicitation allows for multiple award instrument types to be awarded, including Procurement Contracts, Grants, Cooperative Agreements, and OT Agreements. Some award instrument types have specific cost-sharing requirements. The following websites are incorporated by reference and contain additional information and model agreements and contracts regarding overall proposer instructions, general terms and conditions, and each specific award instrument type.

Proposers are strongly encouraged to review the following links as they are part of this solicitation:

• Proposer Instructions: General Terms and Conditions:

https://www.darpa.mil/about/offices/contracts-management/proposer-general-terms

• Procurement Contracts: https://www.darpa.mil/about/offices/contracts-management/proposer-procurement

• Assistance (Grants and Cooperative Agreements):

https://www.darpa.mil/about/offices/contracts-management/grants-agreements

• OT Agreements: https://www.darpa.mil/about/offices/contracts-management/proposer-transactions https://www.darpa.mil/about/offices/contracts-management/proposer-transactions https://www.darpa.mil/about/offices/contracts-management/proposer-transactions https://www.darpa.mil/about/offices/contracts-management/proposer-transactions https://www.nsf.gov/funding/senior-personnel-documents https://www.darpa.mil/about/offices/contracts-management/proposer-general-terms https://www.darpa.mil/about/offices/contracts-management/proposer-procurement https://www.darpa.mil/about/offices/contracts-management/proposer-procurement https://www.darpa.mil/about/offices/contracts-management/proposer-procurement https://www.darpa.mil/work-with-us/grant-cooperative-agreements https://www.darpa.mil/about/offices/contracts-management/grants-agreements https://www.darpa.mil/about/offices/contracts-management/proposer-transactions https://www.darpa.mil/about/offices/contracts-management/proposer-transactions

4.1 CONFORMING SUBMISSIONS

For the purposes of this solicitation, only submissions deemed conforming and relevant will be evaluated against the stated criteria. Conformance and relevance require that submissions encompass:

• One or more of the IPTO thrust areas and/or propose revolutionary advances in information or computational science, technology, or systems.

• A technical approach demonstrating scientific/technological originality, depth of mission understanding, and operational realism.

• The overall goal of the proposed effort, if achieved, would create technology significantly beyond the state-of-the-art, and whether the timetable for achieving results is appropriate for a mission agency such as DARPA.

• The proposed Principal Investigator (PI) and other key personnel have provided strong evidence of their successful execution of similar research projects on which they have performed.

• The cost, scale, and scope of work are commensurate with IPTO resources and priorities.

4.2 NON-CONFORMING SUBMISSIONS

Submissions that are not applicable to HR001126S0011, as defined above, will be deemed non-conforming and removed from consideration. All submissions must provide sufficient information to assess the validity/feasibility of their claims as well as comply with the requirements outlined herein for submission formatting, content, and transmission to DARPA. Submissions that fail to do so may be deemed non-conforming and removed from consideration.

5. ABSTRACTS [REQUIRED]

Potential proposers are strongly encouraged to reach out to DARPA Program Managers (PM) to gauge their interest in a technical approach prior to submitting a formal abstract. Early coordination ensures alignment with IPTO mission priorities and minimizes the expenditure of resources on concepts that may not meet current technical or strategic office requirements.

Proposers are required to submit an abstract, in advance of a full proposal submission, to minimize effort and reduce the potential expense of preparing an out-of-scope proposal. Proposals are by invitation only.

5.1 ABSTRACT SUBMISSION REQUIREMENTS

• Abstracts are due by the date and time stated in Section 1 (Overview Information)

• Unclassified abstracts must be submitted to the DARPA Broad Agency Announcement

Tool (BAAT). Please visit Proposer Instructions and General Terms and Conditions for specific information regarding submission methods through BAAT. Submissions sent through other mediums, channels, or after the prescribed deadline will not be accepted.

• Classified abstracts must be submitted in accordance with the procedures outlined within the Classified Submission Requirements, Instructions, and Procedures attachment.

• Proposers are responsible for identifying proprietary information. Submissions containing proprietary information must have the cover page and each page containing such information clearly marked with a label such as "Proprietary" or "Company Proprietary."

https://www.darpa.mil/work-with-us/proposer-instructions

NOTE: "Confidential" is a classification marking used to control the dissemination of U.S. Government National Security Information as dictated in Executive Order 13526 and should not be used to identify proprietary business information.

5.2 ABSTRACT CONTENT AND FORMATTING REQUIREMENTS

Instructions for abstract submissions including content and formatting requirements, are contained within the required IPTO Office Wide Abstract Template. Failure to comply with all stated content and formatting requirements may result in the abstract submission being deemed non-conforming.

Information not explicitly requested will not be reviewed.

5.3 ABSTRACT BASIS OF EVALUATION

The Government will review abstract submissions using a two-step process. Step 1 will consist of a strict Mandatory Technical Conformance review. Only submissions found to be conforming in Step 1 will advance to Step 2 for a comprehensive evaluation.

Step 1: Mandatory Technical Conformance: The Government will evaluate the Technical Approach for scientific/technological originality, depth of mission understanding, and operational realism. Abstracts that present generic, boilerplate, or broadly aggregated content lacking mission-specific synthesis, will be found non-conforming.

Step 2: Comprehensive Evaluation of Abstract: The proposed technical approach is innovative, feasible, and aligned with the DARPA mission. Key technical challenges and risks are identified.

The proposer demonstrates an ability to achieve the goals of the proposed effort.

5.4 ABSTRACT FEEDBACK

DARPA anticipates sending notification letters via email to all designated Technical and Administrative POC(s) for abstract submissions. Each letter will communicate one of three outcomes:

Non-Conforming: Proposers will be informed that their abstract was found non-conforming and was not reviewed in Step 2.

Invited to Proceed: Proposers will be informed that DARPA is interested in the proposed concept and is inviting the submission of a full proposal. The Government will include feedback on the abstract’s evaluation.

Non-Selection: Proposers will be informed that their abstract was not selected for advancement, and they will not be permitted to submit a full proposal. The Government will include feedback on the abstract’s evaluation.

6. PROPOSALS

6.1 PROPOSAL SUBMISSION REQUIREMENTS

• Full proposals are accepted by invitation only and as stated in Section 1. A full proposal submission must include the following:

o IPTO OW Volume I (Technical and Management) o IPTO OW Volume II (Cost)

• The DARPA Standard Cost Spreadsheet is strongly encouraged but not required as part of a full proposal submission However, if a proposer elects to use an alternative cost format, the burden is entirely on the proposer to ensure the format provides the necessary fidelity, detail, and formula transparency required for a comprehensive Government evaluation.

• Unclassified proposals are strongly encouraged to be submitted to the DARPA Broad Agency Announcement Tool (BAAT). Please visit Proposer Instructions and General Terms and Conditions for specific information regarding submission methods through

BAAT.

• Alternatively, proposals requesting a Grant or Cooperative Agreement may also be submitted via Grants.gov. Submissions sent through other mediums, channels, or after the prescribed deadline will not be accepted.

• Classified proposals must be submitted in accordance with the procedures outlined within the Classified Submission Requirements, Instructions, and Procedures attachment.

• Proposers are responsible for identifying proprietary information. Submissions containing proprietary information must have the cover page and each page containing such information clearly marked with a label such as "Proprietary" or "Company Proprietary."

NOTE: "Confidential" is a classification marking used to control the dissemination of U.S. Government National Security Information as dictated in Executive Order 13526 and should not be used to identify proprietary business information.

6.2 PROPOSAL CONTENT AND FORMATTING REQUIREMENTS

Instructions for proposal submissions, including content and formatting requirements, are contained within the IPTO Office Wide Proposal Templates zip file. Failure to comply with all stated content and formatting requirements may result in the abstract submission being deemed non-conforming. Information not explicitly requested will not be reviewed.

6.3 MODEL CONTRACTS AND MODEL OT AGREEMENTS (PROPOSAL SUBMISSION ONLY)

The Government strongly encourages proposers to make redlined edits (track changes are sufficient) to the appropriate Model Cooperative Agreement, Model Contract, or Model OT Agreement that the proposer's organization would like to negotiate if selected for award negotiations. Redline edits in MS Word Track Changes should be accompanied by comment boxes explaining the context for requested changes. Proposers should submit the edited Model Cooperative Agreement, Model Contract, or Model OT Agreement with their proposal submission.

• Procurement Contracts: https://www.darpa.mil/about/offices/contracts-management/far-based

• Assistance (Grants and Cooperative Agreements):

https://www.darpa.mil/about/offices/contracts-management/grants-agreements

• Other Transaction Agreements: https://acquisitioninnovation.darpa.mil/samples-and-resources/samples https://www.darpa.mil/work-with-us/proposer-instructions https://www.darpa.mil/work-with-us/proposer-instructions https://www.darpa.mil/about/offices/contracts-management/far-based https://www.darpa.mil/about/offices/contracts-management/far-based https://www.darpa.mil/work-with-us/grant-cooperative-agreements https://www.darpa.mil/about/offices/contracts-management/grants-agreements https://acquisitioninnovation.darpa.mil/samples-and-resources/samples https://acquisitioninnovation.darpa.mil/samples-and-resources/samples

6.4 COMMON DISCLOSURE FORMS FOR FRRBS REVIEW (PROPOSAL SUBMISSION

ONLY)

As stated in Section 3.4, all submissions proposing fundamental research that are requesting a Grant, Cooperative Agreement, or OT Agreement should complete and return the common forms found in the proposal package as part of their proposal submission. Proposal submissions that require the common form submission but failed to provide the common forms may not be reviewed.

7. PROPOSAL BASIS OF EVALUATION

Proposal submissions will be evaluated using the following criteria listed in descending order of importance. Overall Scientific and Technical Merit; Potential Contribution and Relevance to the DARPA Mission; Plans to Implement Resilient Software; and Cost Realism.

• Overall Scientific and Technical Merit: The proposed technical approach is innovative, feasible, achievable, and complete. The proposed technical team has the expertise and experience to accomplish the proposed tasks. Key personnel proposed are proposed at a level of effort that will be meaningful and impactful to the proposed research. The proposal identifies major technical risks and planned mitigation efforts are clearly defined and feasible.

• Potential Contribution and Relevance to the DARPA Mission: The potential contributions of the proposed effort bolster the national security technology base and support DARPA’s mission to make pivotal early technology investments that create or prevent technological surprise. The proposed intellectual property restrictions (if any) will not significantly impact the Government’s ability to transition the technology.

• Plans to Implement Resilient Software: The proposal clearly demonstrates the capability to design, implement, and deliver resilient software capabilities within its technical approach. The proposed software implementation approach is feasible and achievable. The approach ensures interoperability, security, and the ability to meet mission objectives at the DoW, DARPA, and program levels. When appropriate, the approach uses formal methods to work towards the goal of eliminating virtually all software vulnerabilities.

• Cost Realism: The proposed costs are realistic for the technical and management approach and accurately reflect the technical goals and objectives of the solicitation. The proposed costs are consistent with the proposer's Statement of Work and reflect a sufficient understanding of the costs and level of effort needed to successfully accomplish the proposed technical approach. The costs for the prime proposer and proposed sub-awardees are substantiated by the details provided in the proposal (e.g., the type and number of labor hours proposed per task, the types and quantities of materials, equipment and fabrication costs, travel and any other applicable costs and the basis for the estimates). It is expected that the effort will leverage all available relevant prior research in order to obtain the maximum benefit from the available funding.

Unless otherwise specified in this announcement, for additional information on how DARPA reviews and evaluates proposals through the Scientific Review Process, please visit: Proposer Instructions: General Terms and Conditions.

8. SPECIAL CONSIDERATIONS

• This announcement, stated attachments, and websites incorporated by reference constitute the entire solicitation. In the event of a discrepancy between the announcement, attachments, or websites, the announcement takes precedence.

• All responsible sources capable of satisfying the Government's needs, including both U.S. and non-U.S. sources, may submit a proposal that shall be considered by DARPA. Historically Black Colleges and Universities, Small Businesses, Small Disadvantaged Businesses and Minority Institutions are encouraged to submit proposals and join others in submitting proposals; however, no portion of this announcement will be set aside for these organizations’ participation due to the impracticality of reserving discrete or severable areas of this research for exclusive competition among these entities. Non-U.S. organizations and/or individuals may participate to the extent that such participants comply with any necessary nondisclosure agreements, security regulations, export control laws, and other governing statutes applicable under the circumstances.

• DARPA encourages technical solutions from all responsible sources capable of satisfying the government's needs. To ensure fair competition across the ecosystem, DARPA prohibits contractors/performers from concurrently providing Systems Engineering Technical Assistance (SETA), Advisory and Assistance Services (A&AS), or similar support services and being a technical performer, unless the DARPA Deputy Director grants a written waiver.

• DARPA encourages technical solutions from all responsible sources capable of satisfying the government’s needs. To ensure fair competition across the ecosystem, DARPA prohibits performers from concurrently providing Systems Engineering Technical Assistance (SETA), Advisory and Assistance Services (A&AS), or similar support services and being a technical performer, unless a waiver is granted. DARPA extends this eligibility criteria to Federally Funded Research and Development Centers (FFRDCs), University-Affiliated Research Centers (UARCs), and Government Entities including national laboratories, who, as a result of their specialized expertise and areas of competencies, are able to accomplish integral tasks that cannot be met by government or contractor resources.

Due to their specialized roles and longstanding regulatory relationships with the government, FFRDCs, UARCs, and Government Entities including national laboratories present potential conflicts and advantages that could compromise fair and open competition. If an FFRDC, UARC, or Government Entity believes they offer unique and innovative approaches to this solicitation and are interested in this solicitation, either as a prime or a subcontractor, they must adhere to the unique instructions outlined in the following sections. If scientifically merited, DARPA may fund work proposed by these entities with the following caveats:

Due to their specialized roles and longstanding regulatory relationships with the Government, Federally Funded Research and Development Centers (FFRDCs), University Affiliated Research Centers (UARCs), and Government Entities to include National Laboratories present potential conflicts and advantages that would compromise fair and open competition. These entities typically may only receive funding through existing awards they hold with their sponsoring agencies. If these entities are proposed as subawardees, their costs must be clearly segregable in cost proposals. If scientifically merited, DARPA may fund work proposed by these entities with the following caveats:

• FFRDCs: (1) FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector. (2) FFRDCs must provide a letter, on official letterhead from their sponsoring organization, that (a) cites the specific authority establishing their eligibility to propose to Government solicitations and compete with industry, and (b) certifies the FFRDC’s compliance with the associated FFRDC sponsor agreement’s terms and conditions. DARPA, under this solicitation, will not award separate contracts to FFRDCs as prime or subawardees but will instead leverage their existing sponsors' agreements.

• UARCs: While UARCs typically have statutory authority to compete with industry, internal DARPA policy views them as trusted advisors who are only eligible to act as performers in fields where they do not serve in an advisory role. Even in those situations, DARPA still considers UARCs as having organizational conflicts of interest (OCI) when applying for a performer role. Proposals with UARCs as prime or subawardees must include an OCI mitigation plan.

For this solicitation, DARPA will not establish new contractual agreements for their participation. Accordingly, any proposal submitted directly by these entities in a prime contractor capacity may be deemed non-conforming and not evaluated. Proposals that include a UARC, FFRDC, Government entities, or National Laboratory as a subcontractor may also be deemed non-conforming unless: (1) their role is clearly defined in the technical proposal with a point of contact, and (2) a rough order of magnitude cost is provided in the technical proposal only—cost proposals must exclude their funding, as DARPA will not fund them through the prime. It is important to note that if funded, these organizations will be required to share their work and findings with other performers also supporting the same program. Additionally, DARPA may contact these entities directly to discuss proposed activities.

• As of the date of publication of this solicitation, the Government cannot identify whether the work under this solicitation may be considered fundamental research and may award both fundamental and non-fundamental research. For additional information on fundamental research, please visit Proposer Instructions: General Terms and Conditions.

• All proposers must have an active SAM.gov Unique Entity Identifier (UEI) with the appropriate “Registration Type”.

• Per Section 8123 of the Department of Defense Appropriations Act, 2015 (Pub. L. 113-235), all grant awards must be posted on a public website in a searchable format. To comply with this requirement, proposers requesting grant awards must submit a maximum one (1) page abstract that may be publicly posted and explains the program or project to the public. The proposer should sign the bottom of the abstract confirming the information in the abstract is approved for public release. Proposers are advised to provide both a signed PDF copy, as well as an editable (e.g., Microsoft word) copy. Abstracts contained in grant proposals that are not selected for award will not be publicly posted.

https://www.darpa.mil/work-with-us/proposer-instructions https://ddmdraft.darpa.mil/work-with-us/proposer-instructions https://sam.gov/entity-registration

• Proposals could potentially include Human Subjects Research (HSR) and/or Animal Use.

Proposers that anticipate involving human subjects or animals in the proposed research must comply with the approval procedures detailed at https://www.darpa.mil/work-with-us/humanresearch to include providing the information specified therein as required for proposal submission.

• Periodically, DARPA may endeavor to hold “Pitch Day(s).” A “Pitch Day” entails DARPA soliciting proposals for a specific, targeted aspect under one or more of the BAA's thrust areas. Proposers ultimately would pitch their proposals to DARPA via oral presentations.

Any "Pitch Day" established under this BAA would be advertised via a separate Special Notice announcement linked to this BAA and posted on SAM.gov and will include specific instructions and evaluation criteria.

• The APEX Accelerators program, formerly known as the Procurement Technical Assistance Program (PTAP), focuses on building strong, sustainable, and resilient U.S. supply chains by assisting a wide range of businesses that pursue and perform under contracts with the DoW, other federal agencies, state and local governments, and government prime contractors. See www.apexaccelerators.us/ for more information.

APEX Accelerators helps businesses:

• Complete registration with a wide range of databases necessary for them to participate in the government marketplace (e.g., SAM).

• Identify which agencies and offices may need their products or services and how to connect with buying agencies and offices.

• Determine whether they are ready for government opportunities and how to position themselves to succeed.

• Navigate solicitations and potential funding opportunities.

• Receive notifications of government contract opportunities on a regular basis.

• Network with buying officers, prime contractors, and other businesses.

• Resolve performance issues and prepare for audit, only if the service is needed, after receiving an award.

• Project Spectrum is a nonprofit effort funded by the DoW Office of Small Business Programs to help educate the Defense Industrial Base (DIB) on compliance. Project Spectrum is vendor-neutral and available to assist businesses with their cybersecurity and compliance needs. Their mission is to improve cybersecurity readiness, resilience, and compliance for small/medium-sized businesses and the federal manufacturing supply chain. Project Spectrum events and programs will enhance awareness of cybersecurity threats within the manufacturing, research and development, and knowledge-based services sectors of the industrial base. Project Spectrum will leverage strategic partnerships within and outside of the DoW to accelerate the overall cybersecurity compliance of the DIB. www.projectspectrum.io is a web portal that will provide resources such as individualized dashboards, a marketplace, and Pilot Program to help accelerate cybersecurity compliance.

https://sam.gov/entity-registration https://www.apexaccelerators.us/ http://www.projectspectrum.io/

• DARPAConnect offers free resources to potential performers to help them navigate DARPA, including “Understanding DARPA Award Vehicles and Solicitations”, “Making the Most of Proposers Days”, and “Tips for DARPA Proposal Success”. Join DARPAConnect at www.DARPAConnect.us to leverage on-demand learning and networking resources.

• DARPA has streamlined our Broad Agency Announcements and is interested in your feedback on this new format. Please send any comments to DARPAsolicitations@darpa.mil.

http://www.darpaconnect.us/ mailto:DARPAsolicitations@darpa.mil