FA2391-23-S-2403_June 2024.pdf

Broad Agency Announcement (BAA) Open Two-Step BAA and

BAA with Calls (Revision 1) 5 June 2024

Overview Information

NAICS Code: The NAICS Code for this acquisition is: 541715 (Research and Technology in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology), and the small business size standard is 1,000 employees. The following Small Business Administration (SBA) size standard exceptions may apply: Aircraft, Aircraft Engine and Engine Parts is 1,500 employees;

Other Aircraft Parts and Auxiliary Equipment is 1,250 employees; and Guided Missiles and Space Vehicles, Their Propulsion Units and Propulsion Parts is 1,300 employees.

Federal Agency Name: Air Force Research Laboratory, Aerospace Systems Directorate, AFRL/RQ

Broad Agency Announcement Title: Pioneering Aerospace Capabilities, Engineering and Research (PACER)

Broad Agency Announcement Type: This is the Initial Announcement

Broad Agency Announcement Number: FA2391-23-S-2403

Catalog of Federal Domestic Assistance (CFDA) Number(s): 12.800 AIR FORCE

DEFENSE RESEARCH SCIENCES PROGRAM

THIS IS A HYBRID SOLICITATION AGAINST WHICH WHITE PAPERS MAY BE

SUBMITTED AND/OR CALLS WILL BE RELEASED. The BAA will remain open for White Papers and Calls until 10 May 2043.

1. OPEN BAA (Two-Step, See Section IV for instructions):

White papers may be electronically submitted at any time during the open period (other than during the “moratorium”) to the PACER central inbox identified in the “Submission” Paragraph of the Overview Information. For each Call that is announced pursuant to this BAA, there will be a “moratorium” beginning when the Call is published and continuing until six months after the due date for proposals, during which no white papers submitted covering the topic specified in the Call will be accepted. White papers will be reviewed and those selected for further consideration will result in a Request for Proposal (RFP). Due dates and times will be specified in each RFP. There will be no other announcement issued requesting white papers. Offerors should monitor the System for Award Management (SAM) website at https://www.sam.gov in the event this announcement is amended.

First Step: WHITE PAPER DUE DATE AND TIME: White Papers will be considered if received prior to 1500 EST on 10 May 2043. Only white papers are due at this time.

Second Step: PROPOSAL DUE DATE AND TIME: To be provided in the RFPs sent to offerors that submit White Papers considered to meet the needs of the Air Force (see Section IV.4.1).

2. CALLS (One-Step or Two-Step, See Section V for instructions):

Over the period of this BAA, Calls may be issued to request white papers or proposals for specific topic areas. It will be determined on a Call by Call basis whether or not the announcement is for white papers (two-step) or proposals (one-step). Each Call will contain specific requirements and pertinent information. White Papers/Proposals submitted in response to the Calls will be accepted as specified in the individual Calls and evaluated in accordance with the Proposal Review Information (Section V.4). Offerors should monitor the System for Award Management (SAM) website at https://www.sam.gov in the event this announcement is amended or Calls are issued.

For ONE-STEP Calls

First Step: PROPOSAL DUE DATE AND TIME: To be provided in Calls.

For TWO-STEP Calls

First Step: WHITE PAPER DUE DATE AND TIME: To be provided in Calls.

Second Step: PROPOSAL DUE DATE AND TIME: To be provided in the RFPs sent to offerors that submit White Papers considered to meet the needs of the Air Force (see Section V.4.1).

NOTE: White Paper/proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3).

Submission: Electronic submission is required. White Papers must be electronically submitted to the PACER central inbox, AFRL.RQ.PACERBAA@us.af.mil.

Please contact the PACER central inbox if there are any issues submitting an electronic copy. White Papers submitted directly to AFRL/RQ Technical and/or Contracting POCs will not be reviewed. For Calls, the Technical and Contracting POCs and instructions for electronic submission will be identified in each individual Call.

Type of Contract/Instrument: The Air Force reserves the right to award the instrument best suited to the nature of research proposed. Accordingly, the Government may award any appropriate contract type under the FAR or Other Transaction (OT) for Prototype, grant, cooperative agreement, or OT for Research. The Air Force may also consider award of an appropriate technology transfer mechanism if applicable. It is anticipated that awards under this BAA will generally be cost reimbursement contracts (Cost Plus Fixed Fee, Cost or Cost Share). Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.

Estimated Program Cost: $500M ceiling on any individual award resulting from a white paper. $500M cumulative ceiling on all award(s) resulting from an individual Call.

Anticipated Number of Awards: The Air Force anticipates multiple awards for this announcement. However, the Air Force reserves the right to award zero, one, or more contracts for all, some or none of the solicited efforts based on the offeror’s ability to perform desired work and funding fluctuations.

Brief Program Summary:

PACER BAA is a Two-Step Open BAA and BAA with Calls which will enable study efforts on novel concepts, as well as research and development efforts to mature specific technologies to appropriate technology readiness levels (TRL) depending on end use.

Efforts under this BAA are intended to further AFRL/RQ’s mission in pioneering transformative aerospace technologies for the warfighter’s decisive advantage. Specific award details are described below, but the Government anticipates multiple awards of varying duration and value. This BAA allows consideration of White Papers as well as Calls issued by the Government when specific requirements are identified.

Communication Between Prospective Offerors and Government Representatives: Prospective offerors are encouraged to reach out to Government representatives with questions or clarifications prior to submitting a White Paper.

However, please note that technical or contract discussions will not be arranged prior to submission. Instead, offerors should submit a White Paper if they have a topic that they believe matches a research topic. After White Paper submission, all exchanges with offerors after proposal submission shall go through the Contracting POC.

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

Address Technical and Contracting questions to: PACER central inbox, AFRL.RQ.PACERBAA@us.af.mil

Full Text Announcement

I. Program Description (Applicable to both Open Two-Step BAA and Calls;

future Calls may be either One-Step or Two-Step Calls): Air Force Research Laboratory, Aerospace Systems Directorate, AFRL/RQ, Wright-Patterson Air Force Base is only soliciting white papers (and later technical and cost proposals) under the Open BAA on the following research efforts at this time:

1. Statement of Objectives:

The PACER BAA will enable study efforts on novel concepts, as well as research and development efforts to mature specific technologies to appropriate technology readiness levels (TRL) depending on end use. Efforts under this BAA are intended to further AFRL/RQ’s mission in pioneering transformative aerospace technologies for the warfighter’s decisive advantage.

AFRL/RQH High Speed Systems Technology Development: This technology area seeks to research, develop, demonstrate and validate advanced technologies and capabilities for high-speed aerospace vehicles. These technologies enable the analysis, test, assembly and successful operation of aerospace platforms in Mach 3+ flight regimes, as well as in environments leading to and from the operating condition(s). The breadth of technology includes: fundamental science, research and development of high-speed systems and components utilizing advanced analysis techniques, ground and flight test. This technical area also focuses on developing subsystems, advanced test methods, system studies, and integration of technologies into flight demonstration vehicles using appropriate model-based engineering approaches. The high-speed systems research and development technology areas include the following topics:

Topic 1 – Aero-Structures: Research and develop aerodynamic, material, structural, and thermal management concepts, methods and designs to improve high speed structures performance. Efforts are focused on aerodynamic and structural interactions throughout a high-speed vehicle's mission including single flight and reusable systems.

Improvements of high-speed structures performance can be achieved through applications of new material, structural, and thermal management concepts. Structural technologies can be validated through demonstration flights, vehicle design, experimental research, associated test methods and instrumentation, predictive and diagnostic analysis methods, and modeling and simulation.

Topic 2– Propulsion Technologies: Research and develop propulsion systems to enable high-speed flight, such as: Scramjet, ramjet, combined cycle, advance propulsion concepts, innovative propulsion concepts, air launch and ground launch, expendable and reusable, and integrated design studies. This research would be conducted on concepts of varying sizes and scales. Areas of interest include but are not limited to: advanced testing methods, analysis, aero-propulsion integration, characterization of inlet and nozzle flow fields, additive manufacturing techniques, advanced fuel development, and efficient combustion techniques. Experimental and computational research challenges associated with sustained combustion in supersonic flows used to evaluate prototype and early development concepts associated with high-speed air breathing propulsion components, fuels, and systems.

Topic 3 – Vehicle Integration and Analysis: Research and development to facilitate the design, analysis, and integration of high-speed systems into reliable configurations of expendable/reusable, manned/ unmanned, high-speed vehicles. Robust model-based systems engineering and digital engineering approaches should be utilized to support the requirements, design, analysis, verification, and validation associated with the development of high-speed systems. Areas of interest include vehicle conceptual design, optimization, multidisciplinary modeling and analysis, mission/performance analysis, military utility analysis (including warfighter/stakeholder engagement), concept of operations development, structural design, payload integration, and the collection of coherent sets of validation data in hypersonic flight environment through flight experimentation.

Topic 4 – Experimental Sciences: Research and develop components and diagnostics for high-speed systems/subsystems and their integration into air vehicles, weapons and launch systems. Efforts should focus on high-speed flow physics, flow over control surfaces and wing-body junctures, boundary-layer (BL) transitions, exploiting shock-shock/shock-BL interactions, and fluid-thermal-structure interactions. Development of flight worthy sensors and expansion of state of the art in experimental methods to advance high-speed propulsion, structural, and external aerodynamics investigations

AFRL/RQQ Power and Controls Technology Development and Demonstration:

This technology area focuses development and demonstration of technologies and integrated systems for aerospace applications, which enhance the mission capabilities, vehicle performance or efficiency, autonomy and teaming of current or future military air vehicles.

Topic 5 – Autonomous Control Branch: Discovery, development, and demonstration of integrated aerodynamic technologies that enable revolutionary capabilities for future military air vehicles. Technologies include, but are not limited to, cooperative control of unmanned aerial vehicles, autonomous air combat tactics and operations, optimization under uncertainty, verification and validation of complex systems, high speed/hypersonic platforms, and aircraft flight control, thermal management, and fault tolerance.

Topic 6 – Control Systems: Autonomous control technologies to make autonomous aerospace systems the preferred option for any joint mission. These technologies include, but are not limited to, autonomous collaboration and manned-unmanned teaming; autonomous safety systems; mission autonomy and intelligence; and autonomy test and evaluation.

Topic 7 – Electrical Systems: Technologies for aerospace power generation, energy storage, power distribution and intelligent power management, protection, and control. This includes, but not limited to, affordable power generation, high impedance arc fault detection, wide temperature solid state batteries, EMI suppression techniques, and advanced power control to name a few.

Topic 8 – Flight Systems Integration: Focus on analysis, development, and demonstration of advanced technologies and integrated systems that provide new capabilities, capability enhancements, or increase air vehicle performance and efficiency as new capabilities to address current or projected warfighting shortfalls. Technologies may be applicable to: a) air vehicles of all classes and speed regimes accomplishing any military mission germane to current, emerging or envisioned Air Force missions; b) enhance air vehicle energy state awareness and coordination of internal vehicle systems, subsystems, and components for improved vehicle capability; c) tools, techniques and analysis for the system-level modeling, digital engineering, and hardware emulation of aircraft power and thermal management, including interactions with the platform and engine.

Topic 9 – Mechanical & Thermal Systems: Analysis, development, maturation and demonstration of advanced aerospace technology concepts, at the subsystem or system level. Focus on technologies to improve reliability and/or cost of electrical to mechanical energy transfer components as well as subsystem/system improvements in thermal acquisition, transport and rejection. Emphasis includes, but is not limited to fundamental thermal sciences, two-phase material applications, adaptive and hybrid thermal cycle systems, and hi-power, low duty cycle thermal management. Also of specific interest are technology improvements for electric actuation, power generation and thermal management for hypersonic platforms, solid-state power generation, advanced magnetic materials, and multi-scale modeling and simulation for these electromechanical/thermal systems.

Topic 10 – Medium Scale Integrated Propulsion, Power, and Thermal (MSIPPT): Focus on analysis, development, maturation (targeting Technology Readiness Levels [TRL] of 5 or 6), integration, control, and demonstration of technologies to enable high-power mission systems on future Autonomous Collaborative Platforms (ACP). Technologies at the component-, subsystem-, and system-level will be considered, as will integration with propulsion systems and ACP vehicles. Specific technology thrusts include (but may not be limited to):

electromechanical actuation for ACP-relevant flight controls and utility actuation, thermal management systems incorporating thermal lift to reduce operational limitations, engine-agnostic power generation, integration of electrical power generation with low-spool propulsion system power extraction, electric machine/power generation systems development, intelligent electrical power storage and distribution, and integrated ground demonstrations of ACP-relevant technologies.

AFRL/RQS Strategic Planning and Analysis Technology Development: This technology area develops advanced modeling and simulation methods and tools to facilitate high-fidelity DAF mission effectiveness analysis. It also develops the Aerospace Systems Directorate’s digital materiel management strategy and implementation plans. It utilizes high-performance mission analysis to assess the potential benefits of new or emerging technology in complex and dynamic battlespace environments. It adapts and advances digital engineering techniques for research and development (R&D) while implementing digital transformation methodologies and tools across the directorate to benefit business processes and functional support. The strategic planning and analysis technology development area includes the following topics:

Topic 11 – Science of Modeling, Simulation, and Analysis (MS&A):

Advances MS&A tools and techniques for technology R&D applications with an emphasis on constructive operational simulations, virtual and immersive visual environments, and advanced computing techniques.

Development includes, but is not limited to, agile software development and delivery processes, simulation framework development, support toolset development, model creation, and scenario development.

Topic 12 – Aerospace Systems MS&A: Utilizes MS&A to assess technology impacts and define operational capability targets. Evaluates the military utility of technological concepts and capabilities in future, multi-domain warfare environments by utilizing a mission-engineering approach. The scope of work includes engineering-level (i.e., system, subsystem, and component), engagement-level (i.e., one-on- one and many-on-many), mission-level (i.e., groups of systems and force packages), and campaign-level MS&A activities and wargames utilizing constructive, virtual, or live simulation of varying fidelity. Also of interest are analysis methods and studies related to the cost, logistics/sustainment, and producibility of future technology concepts and their military utility.

Topic 13 – Digital Materiel Management: Adapts and advances business operations and engineering techniques to build digital capabilities, processes and tools to support informed strategic investment planning and decision making by the Aerospace Systems Directorate. This includes, but is not limited to, establishing digital interfaces; optimized processes and policies; workforce upskill requirements; a “digital first” culture; data management to include increased accessibility to data and models, information architectures, and data science; optimized infrastructure; and enterprise/domain architectures among the directorates technical and functional divisions to help define requirements for repositories, processes, toolchains, and integrated digital environments that enable online collaboration amongst all stakeholders

AFRL/RQT Air-Breathing Engine Technology Development: AFRL/RQT seeks to design, develop, demonstrate, and transition advanced propulsion, power, and thermal technologies that provide disruptive improvement in affordable mission capability. This approach extends to a range of legacy, emerging, and future military propulsion, power, and thermal technology needs in multiple applications.

Technology objectives aim to reduce development, production, and maintenance costs and timelines; increase fuel efficiency; increase propulsive capability; and integrate system propulsion, power, and thermal management. White Papers or Proposals shall address how the proposed technology will impact the systems into which it will be incorporated and explain what current system challenge(s) the technology is overcoming.

The Turbine Engine Division research and development technology areas of interest include the following topics:

RQT Topic 14 – Affordability: Research, development, demonstration, and validation of technologies or approaches that increase cost effectiveness and reduce development timelines for turbine engine-related applications. This could include, but is not limited to, new design approaches, novel manufacturing techniques, innovative component design and material application, and reduced logistics support.

RQT Topic 15 – Future Enabling Air Breathing Propulsion: Research, development, demonstration, and validation of technologies or approaches that will enhance the capability, performance, endurance, and reliability of advanced air breathing propulsion for military applications. This could include, but is not limited to, high payoff engine concepts and components with novel architectures, integrated thermal management, advanced design tools with mission-specific Multi-Disciplinary Analysis and Optimization (MDAO) and Model-Based Systems Engineering (MBSE) tools for Digital Engineering, and concepts tailored to enable effectiveness for crewed and uncrewed weapons systems.

AFRL/RQV Air Vehicle Technologies Development and Demonstration: This technology area focuses on technologies, at all levels of maturity, which enhance the performance or efficiency of current or future military air vehicles of any class or mission. Performance and efficiency may be of any measure, to include metrics of cost. Across the area of interest, the use and advancement of models-based systems engineering and other digital engineering principles and practices to rapidly advance the state of the art, accelerate maturation and enhance the transitionability of the subject technology products is of paramount interest.

Topic 16 – Aerodynamic Technologies: Discovery, development, validation, and demonstration of integrated aerodynamic technologies that enable revolutionary capability for military air vehicles. This area seeks to discover and understand aerodynamic and fluid dynamic processes using foundations of theory, experiment, simulation, and analysis. This knowledge is then used to support the design, analysis and demonstration of new aerodynamic technologies and components, and their integration on military air vehicles.

Topic 17 – Airframe Structures: Drive step function improvements in cost, life, performance, and time to market of tomorrow’s military aircraft structures. Develop technologies to enable affordable yet capable limited life structures for attritable aircraft concepts, including new approaches to airworthiness certification. Develop innovative structural concepts, materials and manufacturing methods that can dramatically reduce airframe weight and/or manufacturing cost for all classes of air vehicles. Explore concepts for multifunctional structures (electrical, thermal, power, etc.) for all sizes of aircraft. Understand structural aspects of morphing and adaptive structures that can eliminate the use of conventional articulated surfaces and enable multi-state flight performance optimization. For all applications, develop the accompanying structural test and analysis methods, particularly with regard to their application to digitally-based aircraft structural design, certification and health monitoring / failure prediction.

Topic 18 – Multidisciplinary Design, Analysis and Optimization (MDAO):

Discover, develop and demonstrate MDAO methods and technologies to enable next-generation aerospace vehicles and provide Air Force decision makers risk-quantified effectiveness assessments of concepts and technologies. Areas of interest include but are not limited to multidisciplinary, multi-fidelity system level effectiveness based design optimization, risk-quantified multi-fidelity coupled analyses and sensitivities, goal oriented adaptive analyses, risk-quantified gradient and non-gradient based design space exploration including machine learning, physics- and statistics-based Reduced Order Models (ROMs), optimization methods, uncertainty quantification methods, model based systems engineering, robust model construction methods, data assimilation methods, digital engineering design methods, multidisciplinary technologies (such as active aeroelastic wing, active flutter suppression, multifunctional structures, etc..), additive manufacturing for design and testing, and experimental validation via ground or flight testing.

Topic 19 – Development and Demonstration of Advanced Military Air Vehicle Capabilities: Analysis, development, maturation and demonstration of advanced technology concepts, at the subsystem or system level. Of interest are both technologies integrated onto existing Air Force weapon systems as capability enhancements and into new systems as new capabilities to address current or projected warfighting shortfalls. Technologies may be applicable to air vehicles of all classes and speed regimes accomplishing any military mission germane to current, emerging or envisioned Air Force missions.

Security: It is expected that during the development and demonstration of technologies supporting the AFRL high speed portfolio that information will be used or generated up to the level of Top Secret, Sensitive Compartmented Information

(TS/SCI).

The contractor shall train personnel in, and follow appropriate Operations Security (OPSEC) measures during the performance of these research activities.

OPSEC: Operations Security (OPSEC) must be an integral part of our daily activities. As we maintain security on our future technologies that are vital to national interest, we must recognize and prepare for the threat poised against our technology. Department of Defense policies mandate a high degree of security throughout the acquisition process. However, heightened security awareness and threat-based countermeasures are particularly essential during the research and development phase when our technology is most vulnerable to espionage, sabotage, or exploitation. It is the obligation of each employee or persons involved on this contract to be constantly aware of and strictly adhere to security requirements designed to protect sensitive unclassified and other information and resources produced by acquisition, research and development, and technological security efforts outlined in this BAA. The contractor shall ensure employees receive training and follow appropriate Operations Security (OPSEC) measures during the performance of the contract.

Safety: The contractor shall consider system safety requirements when developing these identified technologies/technical objectives. (Ref: Military Standard (Mil-Std 882E Department of Defense Standard Practice System Safety)). The system safety process is to identify and document any system safety hazards introduced during all phases (e.g., planning, design, fabrication and testing) and recommend adequate risk mitigations to either eliminate the identified safety risk or minimize them to acceptable risk level. The design goal shall be to eliminate all hazards.

Any residual hazards and subsequent design risk shall be summarized and provide enough detail to support an informed program management decision with regard to the design’s overall safety risk. The contractor shall conduct an evaluation or assessment of these technologies and recommends appropriate system safety task(s) to be conducted in the appropriate technical objectives.

2. Within Scope Modifications: Potential offerors are advised that due to the inherent uncertainty of research and development efforts, awards resulting from this announcement may be modified during performance to make within scope changes, to include but not limited to, modifications which increase overall contract ceiling amount and modifications under authority of

DFARS 235.006-71.

3. Deliverable Items: Applicable Contract Data Requirements Lists (CDRL) data items will be identified in each Request for Proposal submitted during the Open Period and in each Call. Potential deliverables may include, but are not limited to:

a. Data Items: [See Attachment 6 CDRLs]

A001 – Scientific and Technical Reports (Final Report) – End of Tech Effort A002 – Funds and Man-hour Expenditure Report – Monthly A003 – Contractor Spend and Expenditure Plan - Monthly A004 – Contract Funds Status Report (CFSR) – Quarterly A005 – Status Report – Monthly A006 – Presentation Material – As Required A007 – Technical Information Report – SF 424 Annual Update – Annually A008 – Computer Software Product – As Generated A009 – Test Plan – As Required A010 – Material and Processing Digital Data Package –As Generated A011 – System/Subsystem Design Description – As Generated A012 – Technical Data Package – As Generated

b. Software: Software deliverables are anticipated under this program.

Specific software deliverable requirements may be included in each RFP submitted during the Open Period and in each Call.

c. Hardware: Hardware deliverables are anticipated under this program. Specific hardware deliverable requirements may be included in each RFP submitted during the Open Period and in each Call.

d. Other: Other deliverables may be required depending on the requirements and will be identified in each RFP submitted during the Open Period and in each Call.

4. Schedule:

a. Overall effort: It is anticipated that the period of performance for individual awards will vary between 12 and 36 months with an additional 3 months for final report submittal. However, period of performance will be addressed in each RFP submitted during the Open Period and in each Call.

b. Data Items: The contractor shall provide deliverables in compliance with the CDRLs, DD Form 1423-1, as specified in each RFP or Call.

c. Software: The contractor shall meet specific software deliverable requirements as specified in each RFP or Call.

d. Hardware: The contractor shall meet specific hardware deliverable requirements as specified in each RFP or Call.

5. Other Requirements:

a. This announcement incorporates FAR and supplement provisions and clauses by reference. The full text of provisions and clauses can be found at Acquisition.gov.

b. Program Security Classification: Technical work will be conducted at no greater than TOP SECRET/ Sensitive Compartmented Information (TS/SCI). A sample DD Form 254 is attached (Attachment 7). If classified material is involved, a TOP SECRET facility and storage clearance will be required, and the proposal should discuss appropriate personnel and facility clearances. Additionally, if a DD254 is applicable, offerors must verify their Cognizant Security Office information is current with Defense Counterintelligence and Security Agency (DCSA) at www.dcsa.mil.

c. OPSEC: See I.1. (above) for OPSEC guidance.

d. Export Control: Information involved in this research effort may be subject to Export Control (International Traffic in Arms Regulation (ITAR) 22 CFR 120-131, or Export Administration Regulations (EAR) 15 CFR 710-774). If effort may be subject to export control, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal.

e. Export-Controlled Items: As prescribed by DFARS 225.7901-4, DFARS 252.225-7048, “Export-Controlled Item (JUN 2013)” shall be contained in ALL resulting contracts. The contractor must have an active DD Form 2345, Militarily Critical Technical Data Agreement, and a NIST 800-171 assessment in SPRS.

f. Contractor Performance Assessment Reporting System (CPARS): To be determined (TBD) per individual Call/Award. In accordance with FAR 42.1502 and DFARS 242.1502 (and CPARS Guide, Section B, 2.0), past performance evaluations are required for R&D efforts funded with Budget Activity 6.4+ funds and having a value greater than $1M, where 6.4+ type effort is the preponderance. If CPARS is determined to be applicable, interim and final evaluations of contractor performance for contract awards will be prepared in accordance with AFFARS 5342.1503. The final performance evaluation will be prepared at the time of completion of work. In addition to the final evaluation, interim evaluation(s) will be prepared annually (at a minimum). Awardees will be requested to provide a POC to receive notifications of the opportunity to provide feedback.

The contractor will be permitted 14 days to review the document and to submit additional information or a rebutting statement. If agreement cannot be reached between the parties, the matter will be referred to an individual one level above the Contracting Officer, whose decision will be final. Copies of the assessments, contractor responses, and review comments, if any, will be retained as part of the contract file, and may be used to support future award decisions for other procurements.

g. Science and Technology (S&T) Protection: This section is deleted.

(effective with Revision 1, June 2024)

6. Other Information:

a. Government Furnished Property (GFP) Availability: GFP is not anticipated to be made available under any resulting contract. It may be requested in the offeror’s White Paper, and must clearly be identified in the Proposal. For Calls, any GFP should be clearly identified in the White Paper and/or Proposal.

b. Base Support/ Network Access: Base support may be proposed.

(1) Available Base Facilities: Various test facilities at Wright-Patterson AFB and Arnold Engineering Development Center. A list of base facilities is available upon request to the PACER central inbox.

c. Data Rights Desired:

(1) Noncommercial Technical Data: To Be Determined

(2) Noncommercial Computer Software (NCS): To Be Determined

(3) NCS Documentation: To Be Determined

(4) Commercial Computer Software Rights: To Be Determined

The Air Force Research Laboratory is engaged in the discovery, development, and integration of warfighting technologies for our air, space, and cyberspace forces. As such, rights in noncommercial technical data and NCS developed or delivered under this contract are of significant concern to the Government. The Government will therefore evaluate any restrictions on the use of noncommercial technical data, NCS, and NCS documentation which could result in transition difficulty or less-than full and open competition for subsequent development of this technology.

In accordance with DFARS 252.227-7013(b)(1) and 252.227- 7014(b)(1), the Government shall receive unlimited rights in all noncommercial technical data and computer software developed exclusively with Government funds.

In accordance with DFARS 252.227-7013(b)(2) and DFARS 252.227- 7014(b)(2), the Government shall receive Government Purpose Rights (GPR) in all noncommercial technical data and computer software developed with mixed funding. “Developed with mixed funding” means, “development was accomplished partially with costs charged to indirect cost pools and/or costs not allocated to a government contract, and partially with costs charged directly to a government contract.”

Offerors that propose delivery of noncommercial technical data, NCS, or NCS documentation subject to GPR should fully explain how a portion of the data was developed at private expense. Specifically, offerors must explain what noncommercial technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated, how the incorporation will benefit the program, and address whether those portions or processes are segregable.

Offerors that propose delivery of noncommercial technical data with Limited Rights, NCS with Restricted Rights, or NCS documentation with Limited Rights will be considered. Proposals should fully explain what noncommercial technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated and how the incorporation will benefit the program and whether those portions or processes are segregable.

Offerors shall include the data rights assertions as required by DFARS 252.227-7017, Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software. The assertions list is included in Section K and due at time of proposals. Assertions must be completed with specificity. Each assertion must identify the technical data or computer software to be delivered and the associated item, component, or process developed exclusively or partially at private expense to which it pertains. Nonconforming data rights assertion lists will not be accepted until submitted in accordance with DFARS 252.227-7017.

Terms used in this section are defined in the clauses at 252.227-7013, Rights in Technical Data-Noncommercial Items, and 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation.

THIRD PARTY SOFTWARE (COMMERCIAL AND

NONCOMMERCIAL):

If any such software, noncommercial or commercial, is not reasonably identifiable at proposal submission, it must still be approved by the contracting officer prior to incorporation. This obligation to obtain pre-approval by the contracting officer, as described above, continues throughout contract administration.

Noncommercial Computer Software:

DFARS 252.227-7014(d) describes requirements for incorporation of third party noncommercial copyrighted computer software and computer software documentation and is incorporated as follows: The Contractor shall not, without the written approval of the Contracting Officer, incorporate any copyrighted computer software or computer software documentation in the software or documentation to be delivered under this contract unless the Contractor is the copyright owner or has obtained for the Government the license rights necessary to perfect a license or licenses in the deliverable software or documentation of the appropriate scope set forth in DFARS 252.227- 7014(b), and prior to delivery of such—

a. Computer software, has provided a statement of the license rights obtained in a form acceptable to the Contracting Officer;

or

b. Computer software documentation, has affixed to the transmittal document a statement of the license rights obtained.

In addition, all noncommercial computer software will receive the appropriate level rights set forth in DFARS 252-7014(b), which could include: Unlimited rights, GPR, Restricted Rights, or specifically negotiated license.

Commercial Computer Software:

For commercial computer software, the Government will neither accept nor execute a DD Form 250 for such software deliverables until the Contractor obtains from all third party software suppliers and/or vendors (Licensor) licenses for any commercial computer software to be delivered that are consistent with Federal Statutes, Federal Case Law, and Federal Regulations.

The following is a non-exhaustive list of terms and conditions which are inconsistent with Federal law and shall not be included in the commercial computer software license agreement between the Licensor and the Government:

1. The license shall not subject the Government to a contingent liability or a liability that is indefinite or indeterminate, including but not limited to: indemnification clauses, unilateral price increases, the right to attorney fees, automatic assessment of charges, or automatic renewal provisions. These provisions constitute obligations in advance or in excess of an appropriation and violate the Anti-Deficiency Act.

2. The license shall be governed by Federal Statutes, Federal Case Law, and Federal Regulations, and shall not be subject to the laws or jurisdiction of any municipality, state, or foreign country. The license shall not bind the Government to litigation in a particular forum or venue or require the Government to participate in arbitration.

3. The license shall not include non-substitution language that would preclude or limit the Government from using another vendor/reseller and/or product to fulfill Government requirements.

4. The Licensor shall not have the authority to unilaterally terminate the license. All remedies available shall be consistent with the Disputes and Termination Clauses in the underlying basic contract.

5. The Licensor shall not have the right to enter the premise or monitor Government networks for the purpose of auditing the use of the license.

6. The Licensor shall not have the authority to control or otherwise influence any litigation between a third party and the Government. The United States Department of Justice has the sole authority to represent the Government in all litigation matters.

7. The Licensor shall not use the fact that the Government is using the Licensor's products in any notification or advertisement to the public (e.g., no publicity rights permitted).

8. The license shall not require automatic updates or give Licensor the authority to unilaterally replace the software.

[IF APPLICABLE] Additionally, the Contractor may be required to obtain licenses that comply with the following terms and conditions, based on the Government’s needs:

1. [IF APPLICABLE] The license shall not disclaim all warranties through use of an “as is” provision.

2. [IF APPLICABLE] The license shall neither restrict the Government from using the product at various sites nor limit use of the product by various Government agencies or third parties performing work on behalf of the Air Force under the [PROGRAM NAME]. In performance of the [PROGRAM NAME], Government personnel as well as Government contractors may use the software, subject to any negotiated limits on number of users, as applicable.

3. [IF APPLICABLE] [The license shall not limit the Government’s use of the software at other Government and Government contractor sites.] [The license shall authorize the Government to use the software at the following sites: [list].

4. [IF APPLICABLE] The license shall not restrict the Government from copying or embedding elements of accessible code into other applications (e.g., nesting code, derivative works).

The Contractor may obtain agreement from the Licensor to insert the clause below in its respective software licenses intended to be transferred to the Government:

“In the event that any of the provisions of the [Software License] are determined to be inconsistent with Federal law or do not otherwise satisfy the Government's needs, the parties to the [Software License] hereby agree that such provisions shall be null and void as they pertain to the Government. Specifically, the following sections are hereby deleted from the [Software License] [and/or amended as indicated below]:

[Section X: deleted; Section Y: amended as follows […]”

If the Licensor will not agree to the terms and conditions cited herein and/or as contained in DFARS 227.72, the Contractor shall retain the current license on behalf of and for the benefit of the US Government if permissible under its license and such use will not subject the Government to the terms of the license. If the software in question is required to be delivered to the Government, the Licensor must grant the Government a sublicense that allows the Government to use the software to meet its requirements.

The Contractor shall provide documentation to clearly correlate or map any commercial computer software to be delivered to:

a) Contract Line Item Numbers (CLINS);

b) Contract Deliverables (CDRLS);

c) Paragraphs in the statement of work (SOW); and

d) Portions of any functional block diagrams and/or system architecture diagrams, so that it can be readily determined where certain commercial computer software corresponding to certain software license agreement(s) are physically located on the system to be delivered under the contract.

c. Award Information (Applicable to both Open Two-Step BAA and Calls)

a. Anticipated Award Date: This is a 20 (twenty) year BAA. White papers may be submitted at any time during this period (except during Moratorium, if applicable); the white papers may result in the Air Force requesting proposals which would result in awards at any time during this 20 (twenty) year period.

Over the 20 (twenty) year period, Call announcements may be issued to the System for Award Management (SAM) to request proposals for specific research efforts. Awards are anticipated as a result of these Calls.

b. Anticipated Funding for the Program: Individual awards resulting from a white paper are not anticipated to exceed $500M per effort, and total awards under an individual Call are not anticipated to exceed $500M per Call; however there is no pre-defined minimum or maximum. Anticipated funding includes future year funding that has not been appropriated as of the release of this BAA.

No award will be made under this solicitation until funds are available by appropriate budgeting agencies. The Government reserves the right to cancel this solicitation at any time. The Government has no obligation to reimburse an offeror for any costs related to responses to this solicitation (i.e. white papers or proposals). Each Call will have funding profiles specific to that effort. However, similarly, all offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.

d. Eligibility Information (Applicable to both Open Two-Step BAA and Calls)

a. Eligible Offeror: This is an unrestricted solicitation. Small businesses are encouraged to propose.

b. Cost Sharing or Matching: Cost Sharing is not required.

c. Federally Funded Research and Development Centers: The following guidance is provided for Federally Funded Research and Development Centers (FFRDCs) contemplating submitting a proposal, as either a prime or subcontractor. FAR 35.017-1(c)(4) prohibits an FFRDC from competing with any non-FFRDC concern in response to a Federal agency request for proposal for other than the operation of an FFRDC (with exceptions stated in DFARS 235.017-1(c)(4)). There is no regulation prohibiting an FFRDC from responding to a solicitation. However, the FFRDC’s sponsoring agency must first make a determination that the effort being proposed falls within the purpose, mission, general scope of effort, or special competency of the FFRDC, and that determination must be included in the FFRDC’s proposal. In addition, AFRL must make a determination that the work proposed would not place the FFRDC in direct competition with domestic private industry. Only after these determinations are made, would a determination be made concerning the FFRDC’s eligibility to receive an award.

d. Government Agencies: If a Government agency is interested in performing work, contact the PACER central inbox identified in the BAA. If those discussions result in a mutual interest to pursue your agency's participation, the effort will be pursued independent of this announcement.

e. Other:

i. Foreign Participation: Foreign Nationals (FNs) can be employed by a US

Prime Contractor (or Recipient) or Sub-contractor (or Sub-awardee);

however, FNs will be limited to Public Domain information unless the recipient has obtained the proper License of Technical Assistance Agreement that authorizes disclosure of CMI and/CUI to foreign entities pursuant to the Department of State’s International Traffic in Arms Regulations (ITAR) or Department of Commerce’s EAR.

ii. Export Control: This acquisition involves data that are subject to export control laws and regulations. Only contractors who are registered and certified with the Defense Logistics Agency and have a legitimate business purpose may participate in this solicitation. Contact the U.S./Canada Joint Certification Program Office, Defense Logistics Agency, Logistics Information Services J34, HDI Federal Center, 74 Washington Avenue N., Battle Creek, Michigan 49037-3084, (1-800-352-3572) or the Joint Certification Program Office (JCO) at JCP-Helpdesk@dla.mil for further information on the certification process. You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with your proposal.

iii. Number of Proposals: There are no limits on the number of white papers/proposals an offeror may submit.

iv. Eligibility: You may be ineligible for award if all requirements of this solicitation are not met on the white paper (and later proposal) due date as identified above.

e. OPEN TWO-STEP BAA SECTION (This is a Two-Step process)

a. Overview: The Open Period consists of a Two-Step Process described in detail below. White Papers/Proposals submitted shall be in accordance with this announcement. There will be no other solicitation issued in regard to this requirement. The Government intends to review white papers/proposals and award some, all, or none of the proposals received without negotiation/discussion;

however, the Government reserves the right to negotiate with the offeror(s) whose proposal is selected for funding.

ONLY WHITE PAPERS ARE BEING SOLICITED AT THIS TIME.

Offerors should be alert for any BAA amendments that may permit extensions to the white paper submission date.

For additional information, a copy of the Broad Agency Announcement (BAA) Guide for Industry is located at https://www.afrl.af.mil/Portals/90/Documents/HQ/BAA%20Ind%20Guide%2 02020.pdf?ver=7AivkWvoUoptKgypgCuIvw%3d%3d

b. White Paper Instructions (STEP ONE):

i. General: The FIRST STEP requests a white paper and a rough order of magnitude (ROM) cost. The white paper shall include a discussion of the nature and scope of the research and the offeror’s proposed technical approach. The Government will review the white papers in accordance with the FIRST STEP White Paper Review Criteria, set forth in Section IV.4.1. below. Based on this review, the Government will determine whether the white paper has the potential to best meet the Air Force’s needs. Offerors will be notified of the disposition of their white paper. An email response will be sent notifying offerors that their white paper has been received. If an offeror does not receive written communication from the Contracting Officer requesting a proposal within approximately 180 days, the government is not interested in pursuing the white paper. Please note: 180 days is a notional timeframe and could be longer based on the government white paper review cycle. Those offerors submitting white papers assessed as meeting Air Force needs will be asked to submit a technical proposal.