25-04 amend 2 admin update.docx

Amendment No. 2 to BAA FA8750-25-S-7004

The purpose of this amendment is to update the Pre-Proposal Communication language as shown below:

1. Part I Overview Information, is changed as shown below:

Pre-Proposal Communication between Prospective Offerors and Government Representatives: Dialogue between prospective offerors and Government representatives is encouraged. Technical and contracting questions can be resolved in writing through email. Communications with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the Government.

No other changes are made.

NAICS CODE: 541715

FEDERAL AGENCY NAME: Department of the Air Force, Air Force Materiel Command, AFRL - Rome Research Site, AFRL/Information Directorate, 26 Electronic Parkway, Rome, NY, 13441-4514

BAA ANNOUNCEMENT TYPE: Modification

BROAD AGENCY ANNOUNCEMENT (BAA)

TITLE: Multi-Domain Force Applications and Traffic Management for Unmanned Aircraft Systems (M-FAT)

BAA NUMBER: FA8750-25-S-7004

PART I – OVERVIEW INFORMATION

This announcement is for an Open, 2 Step BAA which is open and effective until 4 AUG 2030. Only white papers will be accepted as initial submissions; formal proposals will be accepted by invitation only. While white papers will be considered if received prior to 3pm Eastern Standard Time (EST) on 4 AUG 2030, the following submission dates are suggested to best align with projected funding:

FY26 by 05 SEP 2025 FY27 by 31 AUG 2026 FY28 by 31 AUG 2027 FY29 by 31 AUG 2028 FY30 by 31 AUG 2029

Offerors should monitor the Contract Opportunities on the SAM website at https://SAM.gov in the event this announcement is amended.

CONCISE SUMMARY OF TECHNOLOGY REQUIREMENT: Seeking innovative research to enhance Counter-small Unmanned Aerial System (C-sUAS) kill chain and point defense capabilities through advancements in Electronic Warfare (EW), Cyberspace Operations (CO), Command and Control (C2) Automation and Autonomy, Low-Collateral Defeat (LCD), Low-Collateral Effect Interceptors (LCEI)/Blue Force Interceptors (BFI), and communications.

One goal is to blur the line between EW and CO by developing cyberspace countermeasures that disrupt sUAS operations, particularly command and control links. This includes improving system resiliency in contested environments and prioritizing low-collateral damage solutions. C2 advancements aim to automate and optimize responses to sUAS threats, especially swarm attacks, through AI/ML, sensor fusion, and automated decision-making. Research into LCD/LCEI/BFI could lead to the development of low-cost, autonomous interceptors with integrated EW/CO capabilities and other C-sUAS payloads.

Further research will focus on improving sensor technologies for enhanced detection, identification, and tracking, as well as developing a library for storing and indexing cyberspace effects. In parallel, efforts will be made to advance UAS Traffic Management (UTM) systems, integrating them with existing air traffic control, enabling safe integration of unmanned aircraft into the airspace.

Finally, communication systems will be enhanced through advanced modeling and simulation, development of resilient waveforms and networking protocols for swarm operations, and integration of AI for network optimization and spectrum management.

BAA ESTIMATED FUNDING: Total funding for this BAA is approximately $499M. Individual awards will not normally exceed sixty (60) months with dollar amounts normally ranging from $500K to $20M. There is also the potential to make awards up to $99M.

ANTICIPATED INDIVIDUAL AWARDS: Multiple Awards are anticipated. However, the Air Force reserves the right to award zero, one, or more Procurement Contracts or Other Transactions and assistance instruments, for all, some, or none of the solicited effort based on the offeror’s ability to perform desired work and funding fluctuations. There is no limit on the number of OTs that may be awarded to an individual offeror.

TYPE OF INSTRUMENTS THAT MAY BE AWARDED: FAR based Procurement contracts, CFR based grants and cooperative agreements or other transactions (OT) under 10 USC 4021, 10 USC 4022 (previously 10 USC 4002, 2371, 10 USC 4003, 2371b) depending upon the nature of the work proposed. 10 USC 4023 also allows for FAR based contracts, OTs for research, OTs for Prototype, and assistance instruments.

In the event that an Other Transaction for Prototype agreement is awarded as a result of this competitive BAA, and the prototype project is successfully completed, there is the potential for a prototype project to transition to award of a follow-on production contract or transaction. The Other Transaction for Prototype agreement itself will also contain a similar notice of a potential follow-on production contract or agreement.

AGENCY CONTACT INFORMATION: All white paper submissions and any questions of a technical nature shall be directed to the cognizant Technical Point of Contact (TPOC) as specified below (unless otherwise specified in the technical area):

Questions of a contractual/business nature shall be directed to the cognizant contracting officer, as specified below (email requests are preferred):

Amber Buckley Email: Amber.Buckley@us.af.mil

Emails must reference the solicitation (BAA) number and title of the acquisition.

Pre-Proposal Communication between Prospective Offerors and Government Representatives: Dialogue between prospective offerors and Government representatives is encouraged. Technical and contracting questions can be resolved in writing through email. Communications with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the Government.

Offerors are cautioned that evaluation ratings may be lowered and/or proposal rejected if proposal preparation (Proposal format, content, etc.) and/or submittal instructions are not followed.

PART II – FULL TEXT ANNOUNCEMENT

BROAD AGENCY ANNOUNCEMENT (BAA) TITLE: Multi-Domain Force Applications and Traffic Management for Unmanned Aircraft Systems (M-FAT)

BAA NUMBER: FA8750-25-S-7004

Assistance Listing Number: 12.800 and 12.910

Federal Acquisition Supply Chain Security Act (FASCSA) Orders: Depending on the date of issuance of this solicitation, FASCSA order(s) may be applicable. Therefore, the Offeror shall search for the phrase “FASCSA order” in the System for Award Management (SAM) (https://www.sam.gov) for any covered article, or any products or services produced or provided by a source, if there is an applicable Federal Acquisition Supply Chain Security Act Orders prohibition. This requirement only applies to FAR based awards.

I. TECHNOLOGY REQUIREMENTS:

The Air Force Research Laboratory is soliciting white papers under this Broad Agency Announcement (BAA) for research, development, integration, test and evaluation of technologies/techniques with the following requirements:

1.1 Electronic Warfare (EW) and Cyberspace Operations (CO)

· Seam between EW and CO:

· Develop EW-enabled cyberspace countermeasures (CM).

· Develop CM for new and emerging sUAS C2 links (protocol manipulation, access denial, etc.).

· Develop low collateral damage Electronic Attack/Cyberspace countermeasures.

· Improve performance and resiliency in contested Radio Frequency (RF)/cyberspace environments.

· Defensive Cyberspace Operations (DCO):

· Develop advanced C-sUAS system DCO capabilities.

· Enhance cybersecurity hardening and resiliency.

· Prevent adversary access to friendly C-sUAS assets and technologies.

· Prevent the use of friendly nodes as adversary entry points.

· Apply anti-tamper technologies for Blue Force Interceptors (BFI).

· Develop authentication and tracking for Blue Force Interceptors (BFI).

· Offensive Cyberspace Operations (OCO):

· Develop technologies for immediate and/or near-real time Battle Damage Assessment (BDA) and cyberspace Situational Awareness (SA) of C-sUAS effects.

· Cyberspace C2:

· Develop cyberspace countermeasures.

· Develop user interfaces for cyberspace countermeasure parameter selection.

· Ensure coordination and de-confliction of cyberspace countermeasures from different operators.

· Signature and Effects Library:

· Develop methods for storing and indexing Cyberspace Effects ("Cyber Bullets").

· Develop and implement reverse engineer waveforms.

· Develop methods for storing waveforms securely.

“The government may provide Government Furnished Property (GFP) for this technical area of sUAS platforms for related efforts”

1.2 C-sUAS Command and Control (C2)

· Automation/Autonomy for C2:

· Research, develop, and prototype technologies to integrate with existing C2 systems and solutions to enhance automation/autonomy capabilities.

· Research, develop, and prototype methods to leverage human-machine teaming to reduce C-sUAS operator burden when leveraging multiple sensors and effectors against mass/swarm sUAS attacks.

· Research, develop, and prototype technologies that understand and enforce Rules of Engagement (ROE).

· Research, develop, and prototype technologies to recommend optimized and executable Courses of Action (COA) to mitigate sUAS threats including mass/swarm attacks from a variety of C-sUAS sensors and effectors.

· Research, develop, and prototype technologies for single-operator engagement of mass/swarm attacks.

· Research, develop, and prototype technologies for advanced planning and resource management with a collection of C-sUAS sensors and effectors.

· Research, develop, and prototype technologies to fuse track data from multiple sensors and feedback loops for improved fusion methods across data processing stages.

· Research, develop, and prototype mechanisms and technologies to accurately assess and fuse classification probability/confidence levels of various sensors and effectors from different domains/modalities.

· Research, develop, and prototype technologies to identify sUAS swarm characteristics such as, but not limited to, topology, mesh network, follow-the-leader, semi-autonomous, and autonomous swarms.

· Research, develop, and prototype technologies to identify possible sUAS targets with respective confidence levels.

· Research, develop, and prototype technologies to classify sUAS intent (hobbyist, Information, Surveillance, and Reconnaissance (ISR), nuisance, etc.) from available sensor data such as sUAS geolocation, sUAS kinematics, asset locations, defined areas, and Artificial Intelligence/Machine Learning (AI/ML) classification.

· Research, develop, and prototype software and algorithms to establish threat level of a track individually and relative to a swarm for user and downstream reasoning.

· Research, develop, and prototype technologies and techniques to present multi-domain options/COA to the operator and their probabilities of defeat.

· Swarms:

· Develop scalable swarm architectures that are decentralized, heterogeneous in makeup, and can achieve mission effects without centralized coordination or command and control while also absorbing some amount of member attrition.

· Develop scalable and decentralized swarm coordination algorithms to achieve novel effects for swarm operations.

· Develop communication, coordination, sensing, and navigation techniques to facilitate decentralized swarm operations.

· Develop effective mission planning and command and control user interfaces for swarm operations.

· Airspace Coordination Measures (ACM)/Air Traffic Control (ATC):

· Develop technologies to interface existing systems such as joint ACM or ATC systems and prospective systems (e.g., FAA's UAS Traffic Management (UTM), Remote ID (RID)).

1.3 C-sUAS Sensors

· Research and prototype hardware and software methods to improve threat detection, identification, and tracking with existing COTS sensors such as acoustic, Electro-optical (EO)/Infrared (IR) cameras, Radio Frequency (RF), radar, Light Detection and Ranging (LiDAR), etc.

· Research and prototype leveraging existing sensors for C2-silent (signal silent) sUAS detection, identification, and tracking.

· Research and prototype leveraging LIDAR technologies for low-light conditions.

· Develop technologies and solutions that employ active emissions to detect and ID C-sUAS threats.

1.4 C-sUAS Effectors

· Low-Collateral Defeat (LCD) and Blue Force Interceptors (BFI)/Low-Collateral Effect Interceptors (LCEI):

· Research and develop low-cost BFI/LCEI prototypes to be used in C-sUAS and counter-swarm operations.

· Research, develop, and prototype C-UAS LCD software and hardware.

· Develop low Size, Weight, and Power, plus Cooling/Cost (SWAP-C) BFI payload solutions that enable threat detection, identification, and tracking from BFI platforms.

· Integrate EW/CO capabilities in BFI.

· Develop BFI/LCEI platform movement and decision-making autonomy.

· Develop enclosures for BFI deployment in austere environments.

· Effectors:

· Research and prototype low collateral effect mitigation methods for sUAS threats including mass/swarm sUAS threats.

“The government may provide Government Furnished Property (GFP) for this technical area of sUAS platforms for related efforts”

1.5 UAS Traffic Management (UTM)

· Research and prototype hardware and software methods to enable and improve DoD/Federal UTM operational capability, including tactical applications.

· Integrate Air Traffic Management (ATM) sensing capabilities to expand UTM Air Domain Awareness (ADA) and Situational Awareness (SA) (i.e., military and federal RADAR platforms).

· Integrate capabilities to extend UTM into Advanced Air Mobility (AAM) and Extensible Traffic Management (xTM).

· Develop and integrate AI/ML mechanisms into the DoD/Federal UTM-AAM architecture that provides the means to rapidly and reliably identify cases that will impact airspace safety and security including tactical and strategic airspace conflicts and uncooperative UAS.

· Investigate mechanisms for augmenting raw sensor feeds with meta data that enables more advanced UTM multi-modality sensor data integration.

· Develop and integrate AI/ML algorithms into the DoD/Federal UTM-AAM architecture that enhance the capability for rapidly and reliably distinguishing cooperative from uncooperative UAS.

· Investigate correlation and fusion algorithms to support the complex event processing on multiple sensor detections of an object (e.g., UAS).

· Identify and investigate Detect and Avoid (DAA) technologies that enable UAS operations beyond visual line of sight.

“The government may provide Government Furnished Property (GFP) for this technical area of UAS platforms for related efforts”

1.6 Communications

· Modeling, Simulation, and Analysis (MS&A):

· Develop MS&A software and required infrastructure.

· Develop military real world operational mission scenarios of interest (aligning with AF mission sets using notional communications systems and platforms) and perform the desired analysis using multiple M&S tool sets to include AFSIM, CORE, EMANE, Builder, and Matlab (other tools may be needed).

· Develop performance improvements and perform upgrades of existing MS&A models.

· Develop new models for MS&A tools.

· Integrate tools as applicable.

· Waveforms design and implementation

· Develop new adaptive, intelligent, secure waveforms that are responsive to contested operating environments.

· Implement these new waveforms on hardware.

· Develop a non-proprietary small form factor and ruggedized platform that will speed up waveform transition.

· Swarm communications and networking

· Develop improvements in terms of data rates, resilient connectivity, alternate Position, Navigation, & Timing (PNT), reconfigurable intelligent surfaces (RIS).

· Develop and prototype communication protocols for airborne large-scale networked swarm applications, addressing current research problems in scalability, latency, network organization and sustainable network throughput.

· Advanced communication technologies development

· Develop experimentation, data analysis, modeling, and emulation software to modernize communication technology. Examples include:

· Develop waveforms that are intended for use in cross frequency mesh networks.

· Experimentation of digital, wideband High Frequency (HF) implemented on Permutable, Over-the-air Laboratory for Advanced Radio and Ionospheric Studies (POLARIS) nodes.

· Develop Artificial Intelligence engines to evaluate the spectral conditions present and execute RF communications and spectrum effects to include:

· Network performance monitoring and anomaly detection.

· RF Environmental sensing capabilities.

· Rapid reconfiguration and tuning of digital modulation.

· Rapid reconfiguration and consensus agreement wireless network parameters.

· Research, develop, and prototype data collection techniques and analysis of communication data.

· Research and define methods and best practices for experimentation, including spectral management, to facilitate laboratory and remote site development and operations.

· Research and define methods and techniques for the development, construction, installation, and maintenance of communication technologies at worldwide locations.

· Research and define methods and best practices for help desk monitoring of communications technologies.

· Research and define methods and best practices for emerging communication technologies to facilitate transitions to program office and logistic centers.

IMPORTANT NOTES REGARDING:

1. FUNDAMENTAL RESEARCH. It is DoD 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.

As of the date of publication of this BAA, the Government cannot identify whether work proposed under this BAA may be considered fundamental research and may award both fundamental and non-fundamental research. 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 select award instrument type and to negotiate all instrument terms and conditions with selectees. Appropriate clauses will be included in resultant awards for non-fundamental research to prescribe publication requirements and other restrictions, as appropriate.

For certain research projects, it may be possible that although the research being performed by the awardee is restricted research, a sub-awardee may be conducting fundamental research. In those cases, it is the awardee’s responsibility to explain in their proposal why its sub-awardee’s effort is fundamental research.

2. CLOUD COMPUTING. In accordance with DFARS Clause 252.239-7010, if the development proposed requires storage of Government, or Government-related data on the cloud, offerors need to ensure that the cloud service provider proposed has been granted Provisional Authorization by the Defense Information Systems Agency (DISA) at the level appropriate to the requirement.

II. AWARD INFORMATION:

1. FUNDING: Total funding for this BAA is approximately $499M. The anticipated funding to be obligated under this BAA is broken out by fiscal year as follows:

FY26 - $100M

FY27 - $100M

FY28 - $100M

FY29 - $100M

FY30 - $99M

a. Individual awards will not normally exceed 60 months with dollar values normally ranging from $500K to $20M. There is also the potential to make awards up to $99M.

b. The Government reserves the right to select all, part, or none of the proposals received, subject to the availability of funds. All potential Offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.

2. FORM. Awards of efforts as a result of this announcement will be in the form of contracts, grants, cooperative agreements, or other transactions depending upon the nature of the work proposed.

3. BAA TYPE: This is a two-step open broad agency announcement. This announcement constitutes the only solicitation.

As STEP ONE – The Government is only soliciting white papers at this time. DO NOT SUBMIT A FORMAL PROPOSAL. Those white papers found to be consistent with the intent of this BAA may be invited to submit a technical and cost proposal. See Section VI of this announcement for further details regarding the proposal.

III. ELIGIBILITY INFORMATION:

1. ELIGIBILITY: All qualified offerors who meet the requirements of this BAA may apply.

2. FOREIGN PARTICIPATION/ACCESS:

a. This BAA is closed to foreign participation. This includes both foreign ownership and foreign nationals as employees or subcontractors.

b. Exceptions.

i. Fundamental Research. If the work to be performed is unclassified, fundamental research, this must be clearly identified in the white paper and/or proposal. See Part II, Section I for more details regarding Fundamental Research. Offerors should still identify any performance by foreign nationals at any level (prime contractor or subcontractor) in their proposals. Please specify the nationals’ country of origin, the type of visa or work permit under which they are performing and an explanation of their anticipated level of involvement. You may be asked to provide additional information during negotiations in order to verify the foreign citizen’s eligibility to participate on any contract or assistance agreement or other transaction issued as a result of this announcement

ii. Foreign Ownership, Control or Influence (FOCI) companies who have mitigation plans/paperwork in place. Proof of approved mitigation documentation must be provided to Amber Buckley, Contracting Officer, at Amber.Buckley@us.af.mil prior to submitting a white paper and/or a proposal. Defense Counterintelligence Security Agency (DCSA) approved mitigation documentation includes one of the following: Board Resolution; Security Control Agreement; Special Security Agreement; Proxy Agreement; and Voting Trust Agreement. In addition to providing the approved mitigation documentation, also provide your CAGE Code and your fully executed DCSA cover letter. Expect at least 10 business days for the Government to review and verify FOCI mitigation documentation. Offerors who do not hold one of the above FOCI mitigation documents must work with DCSA to obtain mitigation documentation prior to being eligible under the BAA. For information on FOCI mitigation, contact DCSA. Additional details can be found at: https://www.dcsa.mil/Industrial-Security/Entity-Vetting-Facility-Clearances-FOCI/Foreign-Ownership-Control-or-Influence/

iii. Foreign Nationals as Employees or Subcontractors. Applicable to any effort not considered Fundamental Research. Offerors are responsible for ensuring that all employees and/or subcontractors who will work on a resulting contract are eligible to do so. Any employee who is not a U.S. citizen or a permanent resident will be restricted from working on any resultant contract unless prior approval of the Department of State or the Department of Commerce is obtained via a technical assistance agreement or an export license. Violations of these regulations can result in criminal or civil penalties.

c. Information Regarding Non-US Citizens Assigned to this Project

1. Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S. Government Information Technology (IT) networks in connection with the work on contracts, assistance instruments or other transactions awarded under this BAA must be U.S. citizens. For the purpose of base and network access, possession of a permanent resident card ("Green Card") does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. It also does not apply to dual citizens who possess US citizenship, to include Naturalized citizens. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. Specific format for waiver request will be provided upon request to the Contracting Officer. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC).

2. For the purposes of Paragraph 1, it an IT network/system does not require AFRL to endorse a contractor's application to said network/system in order to gain access, the organization operating the IT network/system is responsible for controlling access to its system. If an IT network/system requires a U.S. Government sponsor to endorse the application in order for access to the IT network/system, AFRL will only endorse the following types of applications, consistent with the requirements above:

a) Contractor employees who are U.S. citizens performing work under contracts, assistance instruments or other transactions awarded under this BAA.

b) Contractor employees who are non-U.S. citizens and who have been granted a waiver.

Any additional access restrictions established by the IT network/system owner apply.

3. FEDERALLY FUNDED RESEARCH AND DEVELOPMENT CENTERS AND GOVERNMENT ENTITIES: Federally Funded Research and Development Centers (FFRDCs) and Government entities (e.g., Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they meet the following conditions:

1. FFRDCs: FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector; and FFRDCs must provide a letter on official letterhead from their sponsoring organization citing the specific authority establishing their eligibility to propose to Government solicitations and compete with industry, and their compliance with the associated FFRDC sponsor agreement’s terms and conditions. This information is required for FFRDCs proposing to be prime contractors or sub-awardees.

1. Government Entities: Government entities must clearly demonstrate that the work is not otherwise available from the private sector and provide written documentation citing the specific statutory authority and contractual authority, if relevant, establishing their ability to propose to Government solicitations. While 10 U.S.C.§ 2539b may be the appropriate statutory starting point for some entities, specific supporting regulatory guidance, together with evidence of agency approval, will still be required to fully establish eligibility.

FFRDC and Government entity eligibility will be determined on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the proposer.

Government entities interested in performing work related to this announcement should contact the Technical Point of Contact (TPOC). If resulting discussions reveal a mutual interest, cooperation may be pursued via other vehicles.

4. ORGANIZATIONAL CONFLICTS OF INTEREST: In accordance with FAR 9.5, offerors are required to identify and disclose all facts relevant to potential OCIs involving the offerors organization and any proposed team member (subawardee, consultant). Under this Section, the offeror is responsible for providing this disclosure with each proposal submitted to the solicitation. The disclosure must include the offerors, and as applicable, proposed team member’s OCI mitigation plan. The OCI mitigation plan must include a description of the actions the offeror has taken, or intends to take, to prevent the existence of conflicting roles that might bias the offerors judgment and to prevent the offeror from having unfair competitive advantage. The OCI mitigation plan will specifically discuss the disclosed OCI in the context of each of the OCI limitations outlined in FAR 9.505-1 through FAR 9.505-4.

a. Agency Supplemental OCI Policy: In addition, AFRL has a supplemental OCI policy that prohibits contractors/performers from concurrently providing Scientific Engineering Technical Assistance (SETA), Advisory and Assistance Services (A&AS) or similar support services and being a technical performer. Therefore, as part of the FAR 9.5 disclosure requirement above, an offeror must affirm whether the offeror or any proposed team member (subawardee, consultant) is providing SETA, A&AS, or similar support to any AFRL office(s) under: (a) a current award or subaward; or (b) a past award or subaward that ended within one calendar year prior to the proposal’s submission date. If SETA, A&AS, or similar support is being or was provided to any AFRL office(s), the proposal must include:

· The name of the AFRL office receiving the support;

· The prime contract number;

· Identification of the proposed team member (subawardee, consultant) providing the support; and

· OCI migitation plan in accordance with FAR 9.5

b. Government Procedures: In accordance with FAR 9.503, 9.504 and 9.506, the Government will evaluate OCI mitigation plans to avoid, neutralize or mitigate potential OCI issues before award and to determine whether it is in the Government’s interest to grant a waiver. The Government will only evaluate OCI mitigation plans for proposals that are determined selectable under the solicitation evaluation criteria and funding availability. The Government may require proposers to provide additional information to assist the Government in evaluating the offerors OCI mitigation plan. If the Government determines that an offeror failed to fully disclose an OCI; or failed to provide the affirmation of AFRL support as described above; or failed to reasonably provide additional information requested by the Government to assist in evaluating the proposer’s OCI mitigation plan, the Government may reject the proposal and withdraw it from consideration for award.

5. S&T PROTECTION.

I. Notice of Intent.

(a) Security Risk Review. Each proposal submission will be subject to a Security Risk Review prior to selection for award. The Security Risk Review is applied to federally funded research designed to help protect Department of the Air Force Science and Technology (S&T) by identifying possible vectors of undue foreign influence. AFRL will follow all policy and procedures outlined in Air Force Research Laboratory (AFRL) Instruction AFRLI 61-113, Science and Technology Protection for the Air Force Research Laboratory and Department of the Air Force Instruction DAFI 63-101/20-101, Integrated Lifecycle Management.

(b) Security risk review for these subject proposals will be developed for all proposed Senior/Key personnel and “Covered Individuals”. These risk reviews will be based on information disclosed in a Research and Related Senior and Key Person Profile and Security Questionnaire. In addition, any accompanying or referenced documents, publicly available information, and information contained in internal U.S. Government databases will be utilized in risk reviews. Nationality or citizenship is not a factor in the security risk reviews.

(c) When considering all external engagements, AFRL incorporates a holistic decision-making process that encompasses technical and security factors. The security review method implemented by AFRL measures risk factors to identify the appropriate Risk Acceptance Level (RAL) within the organization. The objective analysis of the security risk factors is conducted to empower AFRL’s S&T leaders to make risk-informed decisions. The review process generally looks at five factors, or risk areas, but with authority for expanded review as noted in OSD R&E Memorandum dated 6 Jun 2023. The potential security risk factors are set forth below:

Potential security risk factors:

II. Actions Required by Applicants/Recipients at proposal submission.

(a) In accordance with AFRLI 61-113, S&T Protection, Applicants/Recipients are required to submit the following documentation with their proposal:

(1) Grant or Cooperative Agreement (CA) proposals:

(i) Standard Form 424, “Research and Related Senior and Key Person Profile (Expanded) (See Appendix 1) AND;

(ii) Security Program Questionnaire (See Appendix 2) AND;

(iii) “Privacy Act Statement” consent form for each Covered Individual that is also signed by the Applicants/Recipients as that Individual’s Sponsor. (See “Covered Individual” section below, and Appendix 4)

(2) Contract or Other Transaction Agreement (OTA) proposals:

(i) Research and Related Senior and Key Person Profile Worksheet (See Appendix 3) AND;

(ii) Security Program Questionnaire (See Appendix 2) AND;

(iii) “Privacy Act Statement” consent form for each Covered Individual that is also signed by the Applicant/Recipient as that Individual’s Sponsor. (See “Covered Individual” section below, and Appendix 4)

The above appendices are included in the RI-Specific Proposal Preparation Instructions which can be accessed at: https://sam.gov/opp/5d5947ee115b4a49adc07d0bc4bc72e5/view . Always reference the latest versions of these documents. Complete and submit the required forms with your proposal to the technical point of contact (TPOC) listed in Section VII-Agency Contacts AND AFRL.RIOF@us.af.mil.

(3) In the event a security risk is identified, and the Government has determined the security risk exceeds the acceptable threshold, the Applicant/Recipient will be notified and informed of the decline of award. The Government will only provide a general statement of the reasoning due to Government OPSEC measures.

(4) By submission of the Research and Related Senior Key Person Profile and Security Program Questionnaire, the Applicant/Recipient agrees to comply with the following:

(i) To certify that each covered individual who is listed on the application has been made aware: 1) of all relevant disclosure requirements, including the requirements of 42 U.S.C. § 6605; and 2) that false representations may be subject to prosecution and liability pursuant to, but not limited to, 18 U.S.C. §§287, 1001, 1031 and 31 U.S.C. §§ 3729-3733 and 3802. See National Science and Technology Council Guidance for Implementing National Security Presidential Memorandum 33 (NSPM-33) on National Security Strategy for United States Government-Supported Research and Development (January 2022).

(ii) To establish and maintain an internal process or procedure to address foreign talent programs, conflicts of commitment, conflicts of interest, and research integrity.

(iii) To exercise due diligence to identify Foreign Components or participation by Senior/Key Personnel in Foreign Government Talent Recruitment Programs and agree to share such information with the Government upon request.

III. Actions Required by Covered Individuals.

(a) Covered Individual. An individual who contributes to a substantive, meaningful way to the scientific development or execution of a research and development project proposed to be carried out with a research and development award from a federal research agency; and is designated as a covered individual by the federal research agency concerned. See 42 U.S.C. § 6605, Definitions. (Note: For purposes of a Broad Agency Announcement (BAA) or Advanced Research Announcement (ARA) solicitation, “covered individuals” are all Senior/Key Personnel.)

(b) Federal law requires that all current and pending research support, as defined by 42 U.S.C. §6605, must be disclosed at the time of proposal submission, for all covered individuals. The Government may require an updated disclosure during the performance of any research project selected for funding. The Government will require an updated disclosure whenever covered individuals are added or identified as performing under the funded project.

(c) Covered Individuals are also required to sign the “Privacy Act Statement” and provide such signed statement to the Applicant/Recipient for submission with the proposal. (See Appendix 4)

(d) Any decision to accept a proposal for funding under this announcement will include full reliance on the individual’s statements. Failure to report fully and completely all sources of project support and outside positions and affiliations may be considered a material statement within the meaning of the False Claims Act, 31 U.S.C. 3729, and constitute a violation of Federal law.

IV. Actions required by Applicants/Recipients during period of performance:

(a) Applicant/Recipient will be required to re-submit the Research and Related Senior and Key Person Profile as an annual requirement. In addition, whenever a new covered individual(s) is to be added or identified as performing under the funded project, a new Research and Related Senior and Key Person Profile will be required prior to continued performance.

(b) If, at any time, during performance of this award, the Applicant/Recipient learns that its Senior/Key Research Personnel (including any sub awardee personnel who receive this designation) are or are believed to be participants in a Foreign Government Talent Program or have Foreign Components with a strategic competitor or country with a history of targeting U.S. technology for unauthorized transfer, the Applicant/Recipient will notify the Contracting/Grants/Agreements Officer within 5 business days of awareness.

(c) This disclosure must include specific information as to the personnel involved and the nature of the situation and relationship. The Government will review this information and conduct any necessary fact-finding or discussion with the Applicant/Recipient. The Government’s determination on disclosure may include acceptance, mitigation, or termination of the award.

(d) Failure of the Applicant/Recipient to reasonably exercise due diligence to discover or ensure that neither it nor any of its Senior/Key Research Personnel involved in the subject award are participating in a Foreign Government Talent Program or have a Foreign Component with a strategic competitor or country with a history of targeting U.S. technology for unauthorized transfer may result in the Government exercising remedies in accordance with federal law and regulation.

(e) The Applicant/Recipient will be required to flow down this provision to all sub awardees who have personnel designated as Senior/Key Research Personnel as a result of their involvement in the performance of the research.

IV. APPLICATION AND SUBMISSION INFORMATION:

All responses to this announcement must be addressed to the Technical Point of Contact (TPOC) listed in SECTION VII. DO NOT send white papers to the Contracting Officer.

All responsible sources may submit a bid, proposal, or quotation which shall be considered by the agency.

1. SUBMISSION DATES AND TIMES:

It is recommended that white papers be received by 3PM Eastern Standard Time (EST) on the following dates to maximize the possibility of award:

FY26 by 05 SEP 2025 FY27 by 31 AUG 2026 FY28 by 31 AUG 2027 FY29 by 31 AUG 2028 FY30 by 31 AUG 2029

White papers will be accepted until 3PM EST on 4 AUG 2030, but it is less likely that funding will be available in each respective fiscal year after the dates cited. This BAA will close on 4 AUG 2030.

All offerors submitting white papers will receive notification of their evaluation results within 45 days of submission. Offerors should email the TPOC and the Contracting Officer listed in Section VII, for status of their white paper(s) after 45 days, if no such correspondence has been received.

2. CONTENT AND FORMAT: Offerors are required to submit one copy of a 1 to 4 page white paper summarizing their proposed approach/solution. The purpose of the white paper is to preclude unwarranted effort on the part of an offeror whose proposed work is not of interest to the Government.

The white paper will be formatted as follows:

1. Section A: Title, Period of Performance, Estimated Cost, Name/Address of Company, Technical and Contracting Points of Contact (phone and email)(this section is NOT included in the page count);

1. Section B: Task Objective; and

1. Section C: Technical Summary and Proposed Deliverables.

All white papers shall be double spaced with a font no smaller than 12 point. Please note that less than 12 point font is acceptable for graphics and illustrations (as in labels and short descriptions) as long as it is readable when printed out on standard 8x11 paper. In addition, respondents are requested to provide their Commercial and Government Entity (CAGE) Code, their unique entity identifier and electronic funds transfer (EFT) indicator (if applicable), an e-mail address and reference BAA FA8750-25-S-7004 with their submission.

Multiple white papers within the purview of this announcement may be submitted by each offeror. If the offeror wishes to restrict its white papers, they must be marked with the restrictive language stated in FAR 15.609(a) and (b).

3. HANDLING AND MAILING INSTRUCTIONS:

a. CLASSIFICATION GUIDANCE. All Proposers should review the NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL (NISPOM), 32 CFR Part 117, as it provides baseline standards for the protection of classified information and prescribes the requirements concerning Contractor Developed Information under paragraph §117.13. Defense Counterintelligence and Security Agency (DCSA) Site for the NISPOM is: http://www.dcsa.mil/.

In the event of a possible or actual compromise of classified information in the submission of your white paper or proposal, immediately but no later than 24 hours, bring this to the attention of your cognizant security authority and AFRL Rome Research Site Information Protection Office (IPO):

Information Protection Office (contact only if a security compromise has occurred)

b. CLASSIFIED SUBMISSIONS. AFRL/RIGD will accept classified responses to this BAA when the classification is mandated by classification guidance provided by an Original Classification Authority of the U.S. Government, or when the offeror believes the work, if successful, would merit classification.

Security classification guidance in the form of a DD Form 254 (DoD Contract Security Classification Specification) will not be provided at this time since AFRL is soliciting ideas only.

Offerors that intend to include classified information or data in their white paper submission or who are unsure about the appropriate classification of their white papers should contact the technical point of contact listed in Section VII for guidance and direction in advance of preparation.

c. MAILING INSTRUCTIONS.

Email Unclassified electronic submission to the TPOC identified in Section VII. Encrypt or password-protect all proprietary information prior to sending. Offerors are responsible to confirm receipt with the TPOC. AFRL is not responsible for undelivered documents. If electronic submission is used, only one copy of the documentation is required.

Questions can be directed to the TPOC listed in Section VII.

4. OTHER SUBMISSION REQUIREMENTS/CONSIDERATIONS:

a. COST SHARING OR MATCHING RELATED TO FAR BASED AWARDS: Cost sharing is not a requirement. Cost sharing may be proposed and will be considered on a case-by-case basis. Cost share will not be a factor in selection for award. For OT awards, see Section IV.4.h.3.

b. SYSTEM FOR AWARD MANAGEMENT (SAM). Offerors must be registered in the SAM database to receive a contract award, and remain registered during performance and through final payment of any contract or agreement. Processing time for registration in SAM, which normally takes forty-eight hours, should be taken into consideration when registering. Offerors who are not already registered should consider applying for registration before submitting a proposal. The provision at FAR 52.204-7, System for Award Management (Nov 2024) applies.

c. EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT/ SUBRECIPIENT AWARDS: Any contract award resulting from this announcement may contain the clause at FAR 52.204-10 - Reporting Executive Compensation and First-Tier Subcontract Awards (Jun 2020). Any grant or agreement award resulting from this announcement may contain the award term set forth in 2 CFR, Appendix A to Part 25 which can be viewed at: https://www.govinfo.gov/app/details/CFR-2023-title2-vol1/CFR-2023-title2-vol1-part25-appA

d. ALLOWABLE CHARGES: The cost of preparing white papers/proposals in response to this announcement is not considered an allowable direct charge to any resulting contract or any other contract, but may be an allowable expense to the normal bid and proposal indirect cost specified in FAR 31.205-18. Incurring pre-award costs for ASSISTANCE INSTRUMENTS ONLY are regulated by 2 CFR part 200.458, Pre-Award Costs.

e. GOVERNMENT APPROVED ACCOUNTING SYSTEM: An offeror must have a government approved accounting system prior to award of a cost-reimbursement contract per limitations set forth in FAR 16.301-3(a) to ensure the system is adequate for determining costs applicable to the contract. The acceptability of an accounting system is determined based upon an audit performed by the Defense Contract Audit Agency (DCAA). IMPORTANT: If you do not have a DCAA approved accounting system access the following link for instructions: https://sam.gov/opp/e628c811fafe041accdddf55fb8539bf/view?keywords=AFRL-BAA-Guide&sort=-relevance&index=&is_active=true&page=1 For Other Transactions, an offeror must provide documentation that their accounting system is Generally Accepted Accounting Principles (GAAP) compliant in accordance with the DoD Other Transaction Guide.

f. HUMAN USE: All research involving human subjects, to include the use of human biological specimens and human data, selected for funding must comply with Federal regulations for human subject protection. Further, research involving human subjects that is conducted or supported by the DoD must comply with 32 CFR 219, “Protection of Human Subjects” found at: http://www.access.gpo.gov/nara/cfr/waisidx_07/32cfr219_07.html, and DoD Instruction 3216.02, “Protection of Human Subjects and Adherence to Ethical Standards in DoD-Supported Research” found at: http://www.dtic.mil/whs/directives/corres/pdf/321602p.pdf.

1. Institutions awarded funding for research involving human subjects must provide documentation of a current Assurance of Compliance with Federal regulations for human subject protection, for example a Department of Health and Human Services, Office of Human Research Protection Federal Wide Assurance found at: http://www.hhs.gov/ohrp.

2. All institutions engaged in human subject research, to include subcontractors, must have a valid assurance. In addition, personnel involved in human subject research must document the completion of appropriate training for the protection of human subjects.

3. For all research that will involve human subjects in the first year or phase of the project, the institution must submit evidence of a plan for review by an institutional review board (IRB) as part of the proposal. The IRB conducting the review must be the IRB identified on the institution’s Assurance of Compliance. The protocol, separate from the proposal, must include a detailed description of the research plan, study population, risks and benefits of study participation, recruitment and consent process, data collection, and data analysis. The designated IRB should be consulted for guidance on writing the protocol. The informed consent document must comply with 32 CFR 219.116. A valid Assurance of Compliance and evidence of appropriate training by all investigators should accompany the protocol for review by the IRB.

4. In addition to a local IRB approval, an AFRL-level human subject regulatory review and approval is required for all research conducted or supported by the DoD. The Air Force office responsible for managing the award can provide guidance and information about the AFRL-level review process. Confirmation of a current Assurance of Compliance and appropriate human subjects protection training is required before AFRL-level approval can be issued.

5. The time required to complete the IRB review/approval process will vary depending on the complexity of the research and/or the level of risk to study participants; ample time should be allotted to complete the approval process. The IRB approval process can last between 1 to 3 months, followed by a DoD review that could last 3 to 6 months. No funding may be used toward human subject research until all approvals are granted.

g. . SUPPLIER PERFORMANCE RISK SYSTEM (SPRS). Offerors should have a BASIC NIST SP 800 171 DoD Assessment in the SPRS (https://www.sprs.csd.disa.mil/). Basic assessment is to be conducted by the offeror.

V. APPLICATION REVIEW INFORMATION:

1. CRITERIA: The following criteria, which are of equal importance and will be used to determine whether white papers and proposals submitted are consistent with the intent of this BAA and of interest to the Government:

a) Overall Scientific and Technical Merit - The soundness of approach for the development and/or enhancement of the proposed technology,

b) The potential contributions of the effort to the U.S. Air Force Cyber Asymmetric Force Applications for Unmanned Aircraft Systems mission,

c) Related Experience - The extent to which the offeror demonstrates relevant technology and domain knowledge including experience and qualification of the types of…