FA9300-20-S-0001 May 2022.pdf

BROAD AGENCY ANNOUNCEMENT

FOR THE AIR FORCE RESEARCH LABORATORY

ROCKET PROPULSION DIVISION

AEROSPACE SYSTEMS DIRECTORATE

RESEARCH AND DEVELOPMENT

BROAD AGENCY ANNOUNCEMENT (BAA)

FA9300-20-S-0001

4 May 2022

Issuing Office: Air Force Test Center, Directorate of Contracting Edwards AFB, CA

Distribution Statement A: Approved for public release: distribution unlimited.

Public Affairs Clearance Number 20052.

Other requests for this document shall be referred to AFRL/RQR, 5 Pollux Drive, Edwards AFB, CA 93524-7048.

Distribution A: Approved for public release; distribution unlimited.

Public Affairs Clearance Number 20052

TABLE OF CONTENTS:

I. PROGRAM DESCRIPTION

I-1. Statement of Needs I-2. Deliverable Items I-3. Schedule I-4. Other Information

II. AWARD INFORMATION

II-1. Anticipated Funding II-2. Anticipated Number of Awards II-3. Anticipated Award Date

III. ELIGIBILITY INFORMATION

III-1. Eligible Offeror/Applicants III-2. Military Critical Technical Data Agreement III-3. Federally Funded Research and Development Centers III-4. Government Agencies

IV. WHITE PAPER AND PROPOSAL PREPARATION/SUBMISSION INFORMATION ... 16

IV-1. Application Package IV-2. Call Instructions IV-3. Other Instructions IV-4. Amendments IV-5. BAA Guide

V. PROPOSAL REVIEW INFORMATION

V-1. White Paper Review Information V-2. Review and Selection Process

VI. AWARD ADMINISTRATION INFORMATION

VI-1. White Paper Process VI-2. Closed Process VI-3. Awarding of Contracts VI-4. Award Notices VI-5. Proposal Categories VI-6. Negotiations

VII. AGENCY CONTACTS

VII-1. Technical Point of Contact (TPOC)

VII-2. Contracting Points of Contact (CPOC) VII-3 Ombudsmen

VIII. OTHER INFORMATION

VIII-1. Communication VIII-2. Debriefings VIII-3. Wide Area Work Flow Notice VIII-4. Item Identification and Valuation VIII-5. Forward Pricing Rate Agreements VIII-6. Pre-Award Clearance VIII-7. Excessive Pass-Through Charges VIII-8. Post-Award Small Business Program Re-representation VIII-9. System for Award Management Registration VIII-10. Non-Government Advisors VIII-11. Safeguarding Covered Defense Information and Cyber Incident

VIII-12. Compliance with Safeguarding Covered Defense Information Controls ..…..…….23

BROAD AGENCY ANNOUNCEMENT

FA9300-20-S-0001

NAICS CODE: 541715 – Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology) (Guided Missiles and Space Vehicles, Their Propulsion Units and Propulsion Parts) with a small business size standard of 1,250 employees.

FEDERAL AGENCY NAME: Air Force Research Laboratory, Aerospace Systems Directorate (AFRL/RQ-West).

BROAD AGENCY ANNOUNCEMENT TITLE: AFRL Rocket Lab Hermes BAA

BROAD AGENCY ANNOUNCEMENT TYPE: This is an Open Broad Agency Announcement

(BAA).

BROAD AGENCY ANNOUNCEMENT NUMBER: FA9300-20-S-0001

Solicitation Request: Air Force Research Laboratory, Aerospace Systems Directorate (AFRL/RQ-West) is establishing this open two-step BAA to solicit innovative research white papers of interest to the Air Force Research Laboratory research as described below. Potential offerors issuing white papers may be requested to provide a full proposal after white paper reviews.

In addition to the white paper process, AFRL may issue calls under this BAA for specific research objectives. Calls issued under this BAA will include instructions to potential offerors, evaluation criteria, and include a common due date for proposals received in response to the call. The BAA will allow for submission of white papers during the open period of the BAA and will provide for specific proposal preparation times and due dates on individual calls identified during the open period of the BAA. White papers should be addressed to the White Paper Focal Point identified below. This is an unrestricted solicitation. Small businesses are encouraged to respond on all or any part of this solicitation. The NAICS Code for this acquisition is 541715, and the small business size standard is 1,250 employees. White papers/proposals submitted shall be in accordance with this announcement or with any specific calls issued as a part of this announcement. Offerors should remain vigilant for any specific calls or updates related to this BAA.

Communication related to this BAA, including submission of white papers and feedback on this solicitation shall be submitted to the following email address:

White Paper Focal Point*: AFTC.PZRA.BAAs@us.af.mil

Please CC the CPOC listed in VII-2 in all submissions. The Government CPOC will provide a confirmation of receipt for each white paper submitted. Offerors are advised only contracting officers are legally authorized to contractually bind or otherwise commit the Government.

*DO NOT SUBMIT CLASSIFIED INFORMATION TO THE WHITE PAPER FOCAL POINT

UNDER ANY CIRCUMSTANCE. IV-1.1.8. lists steps to be taken prior to the submission or handling of classified information.

Open Period: The AFRL Rocket Lab Hermes BAA has an open period of 20 years. For ease of reference, this BAA may be republished at a minimum of yearly intervals within the open period, but may be updated more frequently dependent on mission requirements.

Type of Contract/Instrument: The Air Force reserves the right to award the instrument best suited to the nature of research proposed. Awards of efforts as a result of this announcement will be in the form of contracts, purchase orders, grants, cooperative agreements or other transactions depending upon the nature of the work proposed. Accordingly, the Government may award any appropriate contract type.

Brief Program Summary: AFRL Rocket Lab Hermes BAA is a two-step open BAA with the ability of issuing future calls that enable study efforts on novel concepts, as well as research and development contracts to mature specific technologies to appropriate technology readiness levels (TRL) depending on end use. Specific award details are described below, but the Government anticipates awarding multiple contracts of varying duration and value. However, the maximum single award value issued against this BAA is less than $100M. This BAA allows consideration of white papers as well as calls issued by the Government when specific requirements are identified.

Proposals Due Date and Time: White papers must be submitted as described below. Multiple awards are anticipated. The amount of resources made available under this BAA will depend on the quality of the white papers and any subsequent proposals received and the availability of funds.

White papers may be submitted anytime during the open period. Calls issued by the Government against this BAA will specify a due date when proposals specific to each call are due.

I. PROGRAM DESCRIPTION

I-1. Statement of Needs

AFRL/RQRM Solid Rocket Motor Technology Development: AFRL/RQRM seeks to design, develop, and demonstrate propulsion technologies for advanced missiles and similar vehicles. The breadth of technology area includes strategic and tactical missiles, from component development to lifecycle management with a focus on facilitating technology transition to applications and users with strong emphasis on verification and validation on a system level. Topics of interest in this technology area include the following:

• RQRM Topic 1 – Development and demonstration of advanced components and manufacturing processes for solid rocket motors (SRMs) including inert components (the motor case, internal insulation, nozzle, thrust vector control and thrust vector actuators, etc.), energetic components (safe/arm, igniters, flight termination systems, destruct charges, etc.) and automated assembly operations.

• RQRM Topic 2 – Design and development of modeling and simulation (M&S) tools that more fully describe the physical processes that occur during manufacture and/or operation, and that reduce predictive uncertainty in design and analysis of SRMs over current State-of-the-Art (SOTA) methods. This area includes development of physicochemical models, coding and software, and unit level/subscale/full scale validation experiments.

• RQRM Topic 3 – Development and testing of SRMs relevant to Air Force missions, including but not limited to air-launched missiles, large air-launched boosters for high-speed weapon applications, and other novel solid rocket motor applications.

• RQRM Topic 4 – Please see the Eternal Quiver Industry Day Primer slide deck for further information on the RQRM objectives. Please note that there is a Distribution D version that is available upon request to the CPOC. Interested vendors may submit any questions related to this BAA to the CPOC and the questions will be answered and posted along with this BAA. Vendors also have the opportunity to request a one-on-one meeting with the TCOP to discuss RQRM topics.

AFRL/RQRE Liquid Rocket Engine Technology Development: This technology area seeks to improve the utility of space launch system propulsion technology for resiliency and rapid launch applications. This includes, but is not limited to, a broad range of technologies, different degrees of development efforts, ground-based experiments, studies, and modeling and simulation activities. Topic areas of specific interest include the following.

• RQRE Topic 1 – Liquid Rocket Engines: Disruptive engine concepts/cycles for liquid propellant engines, engine system components, and control. Complete propulsion systems and engine components for National Security Space launch systems including combustion chambers, injectors, nozzles, turbomachinery, valves, and fluid delivery systems. This area includes plume phenomenology, embedded sensors, data recording and distribution, and modelling & simulation (M&S) tool development as well as the facilities to test, manufacture, or advocate for such systems.

• RQRE Topic 2 – Modularity: Modular propulsion system components, and/or complete propulsion systems as well as the facilities to test, manufacture, or advocate for such systems to benefit the space launch enterprise. Modularity includes multiple thrust chambers manifolded to a common propellant feed system with two or more pumps. Modular engine aspects address scalability, applicability, testability, and life cycle cost for National Security Space applications.

• RQRE Topic 3 – Advanced Material and Manufacturing: Advanced materials development and manufacturing processes as applied to liquid engine, liquid engine system components, and/or complete propulsion systems to address complexity, unpredictability, and mass of space launch systems.

• RQRE Topic 4 – Rapid Launch and Austere Location: Experimentation, development, optimization, and demonstration of enabling mission concepts, operational constructs, concepts of operations, and/or enabling architectures for rapid or responsive launch for disruptive space access. This includes full-scale concept development, demonstration, and system modeling of launch, employment of austere locations, reusability, modularity, launch vehicle-to-space vehicle integration, facilities to test, manufacture, or advocate for such systems, and related concepts to increase speed and reach of lethality.

• RQRE Topic 5 – Vehicle: Resilient and rapidly innovative technologies for space access, tactically responsive space access, and maneuvering, covering topics such as vehicle stages, main propulsion system, feed systems and control, flight controls and telemetry, health monitoring, concept of operations, payload adapters, processing facilities for loading and unloading cargo, and ground service equipment. This area leverages Digital Engineering for architecture modeling, mission analysis and engineering, simulation & analysis (MS&A) of to-through-from space architectures, global rocket cargo transport, and global persistent awareness.

• RQRE Topic 6 – Rotating Detonation Rocket Engine/Combustors: Innovative rotating detonation concepts for improved high mass flux thrust chamber assemblies, injector components, combustor/nozzle materials, unsteady nozzles, gas generators, and preburners. This area solicits design innovations, as well as modeling and compact, high-speed sensor diagnostic technologies supporting leading to a full-scale rocket ground/flight demonstration program for rotating detonation technology transition.

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:

• RQH Topic 1 – Structures: Research, development, demonstration and validation of structures to enable high speed flight.

• RQH Topic 2 – Aerodynamics: Research, development, demonstration and validation of aerodynamic solutions (e.g. controls, predictions, designs) to enable high speed flight.

• RQH Topic 3 – Propulsion: Research, development, demonstration and validation of propulsion-related approaches to enable high speed flight and may include Aeropropulsion Integration (API).

• RQH Topic 4 – Integration and Assessment: Research, development, demonstration and validation of systems and vehicles to enable high speed flight.

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.

• RQV Topic 1 – Aerodynamic Technologies: Discovery, development, validation, and demonstration of integrated aerodynamic technologies that enable revolutionary capability for future 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.

• RQV Topic 2 – 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.

• RQV Topic 3 – 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.

• RQV Topic 4 – 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.

AFRL/RQT Air-Breathing Turbine Engine Technology Development: AFRL/RQT seeks to design, develop, demonstrate and transition advanced turbine propulsion, power and thermal technologies that provide a 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; increase fuel efficiency; increase propulsive capability; and integrate propulsion, power, and thermal management. The air-breathing turbine engine research and development technology areas include the following topics:

• RQT Topic 1 – Turbine Engine Turbomachinery: Research, development, demonstration and validation of technologies that provide compact, efficient, durable and affordable fan, compression, and turbine systems for military propulsion systems. Technologies include, but are not limited to: innovative component aerodynamic and thermodynamic design and assessment, system integration techniques, advanced analysis and experimental measurement techniques, evaluation of internal and external cooling configurations, advanced testing capability for compression systems and aircraft/engine integration technologies and digital engineering.

• RQT Topic 2 – Turbine Engine Integrity: Research, development, demonstration and validation of technologies that ensure mechanical integrity, durability and sustainability of advanced turbine propulsion for military applications.

Technologies include, but are not limited to: innovative component design capabilities, design with advanced materials, structural dynamic assessment, advanced Modeling and Simulation (M&S) and experimentation, instrumentation, fatigue and fracture of advanced materials, metrology advancements, rotordynamics, and digital engineering.

• RQT Topic 3 – Fuels: Research and development of fuels and fuel technologies for military specific environments and applications. Technologies include, but are not limited to: capability to predict impacts of fuel composition & variance on performance, enhanced fuel-combustion performance, fuels for expanded speed envelope flight, biotechnologies mitigating biocontamination & corrosion, advanced fuel thermal management, advanced fuels M&S, experimentation, and digital engineering.

• RQT Topic 4 – Turbine Engine Mechanical Systems: Research, development, demonstration, and validation of mechanical systems technologies for turbine engine military propulsion systems. Technologies include, but are not limited to:

turbine engine mechanical systems architecture design, bearing and gear fatigue/tribology/lifing, lubricants and lubrication systems, and modeling & simulation tool development.

• RQT Topic 5 – Air Breathing Propulsion Systems: Research, development, demonstration and validation of technologies that will enhance the capability, performance, endurance, reliability, and reduce the through-life cost of advanced turbine propulsion for military applications. Technologies include, but are not limited to: high payoff engine concepts and components with novel architectures, shared engine and aircraft thermal management systems, advanced aircraft-integrated inlet and exhaust systems, open-architecture electronic control systems with modular hardware/software, engine health management technologies, and advanced M&S and digital engineering for the analysis, investigation, development, and demonstration of engine improvements.

• RQT Topic 6 – Turbine Engine Combustion: Research, development, demonstration and validation of combustion technologies for advanced turbine propulsion for military applications. Technologies include, but are not limited to:

combustion science, unique combustion approaches, advanced combustor designs, augmentors, advanced design tools, experimentation and digital engineering.

• RQT Topic 7 – Turbine Engine Materials and Manufacturing: Research, development, demonstration and validation of materials and manufacturing technologies, including but not limited to: metals, non-metals, coatings, advanced manufacturing, alternative manufacturing and inspection. Technologies that will enable turbine engines to increase performance, reduce weight and/or reduce cost.

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.

• RQQ Topic 1 – 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, optimization under uncertainty, verification and validation of complex systems, high speed/hypersonic platforms, and aircraft flight control, thermal management, and fault tolerance.

• RQQ Topic 2 – 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.

• RQQ Topic 3 – Electrical Systems: Technologies for aerospace next generation direct current (dc) 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, electromagnetic interference suppression techniques, and advanced power control to name a few.

• RQQ Topic 4 – 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.

• RQQ Topic 5 – 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.

Additional technology areas may be added in updates to this BAA. Contractors are responsible for monitoring this BAA for changes.

I-2. Deliverable Items

I-2.1. Contract Data Requirements List (CDRLs): CDRLs may include but are not limited to Status Reports, Scientific and Technical Reports, Performance and Cost Reports and Presentation Material. At minimum, a final report shall be delivered. Specific CDRL requirements will be identified within a letter request for proposal (RFP), specific calls, or contracts issued under this BAA. If less than unlimited data rights is included in any deliveries, it shall be provided in a separate section.

I-2.2. Scientific and Technical Reports, Final Report: Approval to be based on technical content, including a complete accounting of all activities performed under the technical effort with sufficient detail to allow a follow-on activity to pick up where the technical effort ended and for replication of the results, and format, including compliance with ANSI/NISO Z39.18. The Government will have 30 days to review, edit, and approve/disapprove for technical content and format. The updated final report shall be delivered 30 days after receiving the Government's review. Further guidance on the Test/Inspection Report CDRL will be outlined in the associated DD Form 1423.

I-2.3. Software: Specific software deliverable requirements will be identified within letter RFPs, specific calls, or awards issued under this BAA.

I-2.4. Hardware: Specific hardware deliverable requirements will be identified within letter RFPs, specific calls, or awards issued under this BAA.

1-2.5. Contractor-Acquired Property (CAP): Property acquired or fabricated under this contract and with contract funds shall be considered Government property IAW FAR 52.245-1 Government Property. Delivery of residual contractor-acquired property is required. Delivery is due thirty days after end of technical effort of each contract if residual hardware is developed. The proposal shall include related costs associated with packaging and shipping CAP to AFRL in accordance with specific details in individual contracts.

I-2.6. Other: All other deliverables will be identified within letter RFPs, specific calls, or awards issued under this BAA. Cost reimbursement type contracts awarded under the BAA will include a Not Separately Priced (NSP) CAP Contract Line Item Number (CLIN) in order to provide for disposition of CAP not anticipated at time of contract award or otherwise not specified for delivery on an existing CLIN.

I-2.7. Additional Data: Alternate or additional data items that would streamline or enhance the effectiveness of the effort are solicited. Proposals shall show a list of CDRL items included in the price of the proposal. Electronic submission of data items shall be required on all efforts.

I-3. Schedule

Each award is anticipated to be between 6 to 60 months; however, period of performance will be tailored to each award.

I-4. Other Information

I-4.1. Program Security Classification/DD form 254, Operations Security (OPSEC), International Traffic in Arms Regulations (ITAR) 22 CFR 120-131, Export Administration Regulations (EAR) 15 CFR 710-774), and specific Base Support (including network access) will be considered for each award on a case-by-case basis.

I-4.2. Conferences: Offerors should plan for participation in appropriate conferences and workshops in order to present current results. This participation will serve as a mechanism to report current progress to the community.

I-4.3. Government Furnished Property or Information (GFP or GFI): GFP and/or GFI may be available for any individual contract. All offerors are encouraged to engage with an appropriate Government POC to identify possible ways to leverage GFP or GFI.

Specific calls may have specific requirements and/or GFP or GFI available. In accordance with FAR 45.201(b), the contractor is responsible for all costs related to making the property available for use, such as payment of all transportation, installation or rehabilitation costs.

I-4.4. Data Rights Desired:

(1) Technical Data: Unlimited Rights

(2) Non-Commercial Software (NCS): Unlimited Rights

(3) NCS Documentation: Unlimited Rights

(4) Commercial Computer Software Rights: Customary License

The Air Force Research Laboratory is engaged in the discovery, development, and integration of warfighting technologies for air, space, and cyberspace forces. As such, rights in technical data and NCS developed or delivered under this BAA are of significant concern to the Government. The Government will therefore carefully consider any restrictions on the use of 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.

Offerors that propose delivery of technical data, software, NCS, and NCS documentation developed entirely at Government expense are to be delivered with Unlimited Rights.

Technical data, NCS, and NCS documentation developed with mixed funding are expected to be delivered with at least Government Purpose Rights. Offers that propose delivery of technical data, NCS, or NCS documentation subject to Government Purpose Rights should fully explain how the data was developed at private expense. Specifically, offers must explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government award will be incorporated, how the incorporation will benefit the program, and address whether those portions or processes are segregable.

Offerors that propose delivery of technical data, NCS, or NCS documentation subject to Limited Rights, Restricted Rights, or Specifically Negotiated License Rights will be considered. White papers or proposals submitted in response to individual calls should fully explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government award will be incorporated and how the incorporation will benefit the program and whether those portions or processes are segregable.

Offerors responding to the letter RFP within the white paper process or to a specific call 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. Assertions must be completed with specificity.

Each assertion must identify the data and each such item, component, or process listed.

Data rights assertions do not count towards page limits provided within this BAA.

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.

Additional information/instruction regarding data rights may be identified in letter RFPs.

I-4.5. Model Contract: A model contract may be provided to prospective offerors with letter RFPs or provided as attachments to specific calls. Model agreements may be provided when a non-FAR based agreement is pursued.

II. AWARD INFORMATION

II-1. Anticipated Funding

Individual awards are not anticipated to exceed $100M per contract; 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 budging 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).

II-2. Anticipated Number of Awards

The Air Force anticipates awarding multiple awards over the course of this BAA. Calls issued under this BAA may identify the number of anticipated awards specific to each call, subject to the availability of funds.

II-3. Anticipated Award Date

Awards made as a result of a white paper submission are subject to full proposal evaluation, successful negotiations, and funds availability.

III. ELIGIBILITY INFORMATION

III-1. Eligible Offeror/Applicants

This is an unrestricted solicitation. Small businesses are encouraged to propose on all or any part of this solicitation. Foreign persons or foreign-owned firms are precluded from proposing and participating on subsequent awards.

III-2. Military Critical Technical Data Agreement

All offerors shall register and certify with the Defense Logistics Services Center (DLSC), Federal Center, Battle Creek, MI, 49017-3084 (1-800-352-3572). Contractors that are registered with the DLSC must submit a copy of the approved DD Form 2345, Military Critical Technical Data Agreement, with white paper proposals to the CPOC for verification. The DD Form 2345 submission does not count towards page limits provided in this BAA.

III-3. 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, against this BAA. FAR 35.017-1(c)(4) prohibits an FFRDC from competing with any non- FFRDC concern in response to a Federal agency RFP 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 FFRDC, and that determination must be included in the FFRDC’s proposal. In addition, the non-sponsoring agency (in this case 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.

III-4. Government Agencies

If a Government agency is interested in performing work, contact the Program Office identified in the BAA. If those discussions result in a mutual interest to pursue agency's participation, the effort may be pursued independent of this announcement.

IV. WHITE PAPER AND PROPOSAL PREPARATION/SUBMISSION INFORMATION

IV-1. Application Package

This announcement is an open BAA, which includes possible awards to white papers.

White papers shall be submitted in accordance with this announcement or associated call.

The Government will review white papers received. The Government may select white papers for further consideration and award some, all, or none of the work described within the white paper received. Negotiations may/may not occur after a full proposal is received in response to a white paper submission.

IV-1.1. White Paper Instructions:

IV-1.1.1. General: A white paper shall include discussion of the nature and scope of the research, the offeror’s proposed technical approach, and a rough order of magnitude (ROM) cost. The Government will review the white papers in accordance with the review criteria, set forth in Section V.

Based on this review, the Government will determine which have the potential to best meet the Air Force’s needs. Offerors may be notified of the disposition of their white paper. White papers will be kept for up to one year (para. V-2.1) Those offerors submitting white papers assessed as meeting Air Force needs will be asked to submit a technical and cost proposal. The cost of preparing white papers in response to this announcement is not considered an allowable direct charge to any resulting or any other award; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in FAR 31.205-

18. White papers may be ineligible for further award consideration if all requirements of this solicitation are not met.

IV-1.1.2. Page Limitations:

IV-1.1.2.1. The white paper shall be limited to five (5) pages, prepared and submitted in .pdf format. The white paper shall be legible, use a standard business font no smaller than 10 point, character spacing must be “normal” not condensed in any manner, and pages should be double-spaced (each side counts as one page), 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom.

Contractors who submit white papers that are not legible will be asked to resubmit a legible white paper in order to be considered for award.

IV-1.1.2.2. Lines between text lines should be the same font size as the text lines. All text, including text in tables and charts, should adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams, although any text on these items must be legible.

IV-1.1.2.3. Pages should be numbered starting with the title page being Page 1.

The page limitation covers all information including indices, photographs, foldouts (counted as one page for each 8.5 by 11 portion) tables, charts, appendices, attachments, resumes, etc. The Government will not consider pages in excess of these limitations.

Offerors should submit one (1) electronic copy of the white paper to the CPOC, identified in Section VII-2.

IV-1.1.3. Format: The white paper shall be formatted as follows:

• Section A (Title Page): Title of Program, identification of the technology area the white paper is being submitted under (see para. I-1 above for a list of technology areas within this BAA), Name of Company, Company’s Commercial and Government Entity (CAGE) number, Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, Contractor’s Contracting POC and Technical POC with appropriate telephone numbers, fax numbers, and email addresses for the POCs, confirmation of whether the company would like to participate in the interested contractor capability repository (see para. IV-6);

• Section B: Period of Performance and Task Objectives;

• Section C: Technical Summary and Proposed Deliverables; and

• Section D: Estimated cost of program.

IV-1.1.4. Title Page: Single page, self-explanatory. See attached Title Page form as a tool to be used in white paper submissions. The title page does not count towards the page count described in para. IV-1.1.2.1.

above.

IV-1.1.5. Period of Performance and Task Objectives: Dates on proposed program shall be stated simply and obviously. Tasks shall be written as a summary, preferably with task titles and supporting bullets defining the task. Task names/numbering shall be consistent throughout the proposal for clarity.

IV-1.1.6. Technical Summary and Proposed Deliverables: The technical portion of the white paper shall include a discussion of the nature and scope of the research and the offeror’s proposed technical approach/solution. It may also include any proposed deliverables.

Resumes, descriptions of facilities and equipment, and a proposed Statement of Work (SOW) are not required within the white paper.

IV-1.1.7. Cost Portion: The cost portion of the white paper shall include a rough-order-of-magnitude cost estimate. No detailed price or cost support information should be forwarded; only a time-phased bottom line figure of the major tasks should be provided.

IV-1.1.8. Other Information: 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 52.215-1(e).

Offerors are asked to contact the CPOC, prior to submitting any white papers that are classified in nature, for handling instructions.

IV-1.2. Proposal Instructions:

IV-1.2.1. General: Notification from the government of interest in the submitted white paper will take the form of a letter Request-for- Proposal (RFP)/solicitation/application. This letter will identify the required proposal content (e.g., technical section, cost section, etc.).

At a minimum the Government will evaluate responses to the letter for technical and cost/price criteria. Additional criteria may be required in order to adequately evaluate an offerors proposed approach (e.g., management criteria, past performance, etc.) and will be described in the letter. In addition to content, the letter will identify other instructions such as the proposal due date, format, and submission method. Offerors are advised only contracting officers/agreements officers are legally authorized to contractually bind or otherwise commit the Government. The cost of preparing a response to the letter is not considered an allowable direct charge to any resulting or any other award; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in

FAR 31.205-18.

IV-1.2.2. Statement of Work (SOW): Each response to a letter

RFP/solicitation/application will include a non-proprietary version of the SOW. The SOW shall contain a summary description of the technical methodology as well as detailed task descriptions.

Offerors are cautioned to include only the essential information for a clear, logical, and reasonable SOW. This document will be made part of any resulting award. Do not include any proprietary information in the SOW. The SOW section structure below is based on the SOW description in the BAA Guide for Industry referenced in para. Part I-V of the BAA; offerors should refer to that document for more information. All subsections of the SOW are to be numbered in outline form according to the number of the main section (i.e. 1.1, 1.2, 1.2.1.1, 1.2.1.2, etc.).

1.0 BACKGROUND

The background information should identify the requirement in very general terms; describe why the project is being pursued, and how it relates to other projects. Summarize any statutory authority or regulations affecting the overall requirement.

2.0 SCOPE

This section should provide a brief statement of what the offeror expects to accomplish under the award — the breadth and limitations of the effort. It should not include specific work tasks or a description of deliverable products since this will be included in the “Tasks” section.

3.0 OBJECTIVES

This section should provide a concise overview of the effort goals and objectives; and how the results or end products will be used.

4.0 TASKS/TECHNICAL REQUIREMENTS

This section defines the tasks that the contractor or recipient shall complete during performance of the effort and would have a task description for each step of the Work Breakdown Schedule (WBS). The description of task requirements will depend on the approach that is selected to describe the required effort. Tasks shall be detailed to a WBS-third-level equivalent to give reviewers sufficient detail to evaluation work and costs.

5.0 DELIVERABLES

This section should clearly state all deliverables including CDRLs and material.

6.0 PERIOD OF PERFORMANCE

The period of performance shall be clearly stated using in units of months after contract award. Milestones shall be stated as a number of months after award. These milestones shall include the end of technical effort and end of the period of performance of the effort.

IV-1.2.3. Guidelines for Submission of Other than Cost or Pricing Data: The contracting officer has anticipated that adequate price competition (APC) does not exist when considering award of a research effort based on receipt of a white paper. Offerors are/will be requested to submit in its proposal information described in FAR 15.403-5, Instructions for Submission of Certified Cost or Pricing Data and Data Other Than Certified Cost or Pricing Data. This information will be used to support price reasonableness and cost realism. The agreements officer may ask for enough detail to determine the non- FAR based award to be fair and reasonable.

IV-1.2.4. Proposal Validity Period: Offerors must state, on the cover page of each volume of their proposal, that their proposal is valid for at least 180 days from submission. Any proposal received that does not include this information in the specified location will be assumed valid for 360 days from the submission date. Proposals submitted shall be in accordance with this announcement and any subsequent call.

IV-2. Call Instructions

Calls issued under this BAA will identify specific proposal instructions. Information may include but is not limited to anticipated funding, number of awards, award date, and data rights instruction. Contractors that are registered with the DLSC must submit a copy of the approved DD Form 2345, Military Critical Technical Data Agreement in response to a call to the (CPOC) for verification.

IV-2.1. Call Review Information

The Government will define the evaluation criteria within each call. Each call shall, at a minimum, contain technical and price/cost evaluation criteria.

IV-2.2. Call Review and Selection

Proposals will be evaluated in accordance with evaluation criteria identified in each call. After evaluation, proposals will be categorized as identified in BAA section VI-5 and funding selection will occur. This marks the end of the proposal evaluation period. The Government reserves the right to enter into negotiations with those companies selected for award in order to arrive at a final fair and reasonable price.

IV-3. Other Instructions All offerors must comply with all provisions of FAR 52.215-1 “Instructions to Offerors – Competitive Acquisitions.” Proposals should be marked in accordance with FAR 52.215- 1(e). A copy of this provision is available from acquisition.gov. Properly marked proprietary information will be treated in accordance with DFARS 252.227-7016, Rights in Bid or Proposal Information. Proposals must reference the BAA announcement number.

Offerors are advised that only contracting officers are legally authorized to contractually bind or otherwise commit the Government.

IV-4. Amendments

Offerors should be alert for any BAA amendments to this announcement or any subsequent calls. Any additional information will be posted on the Government Wide Point of Entry (i.e. the Federal Business Opportunities website, beta.sam.gov) and awareness of any change is the offeror’s responsibility.

IV-5. BAA Guide

A copy of the Broad Agency Announcement (BAA) Guide for Industry is available at https://www.afrl.af.mil/Portals/90/Documents/HQ/BAA%20Ind%20Guide%202020.pdf?

ver=7AivkWvoUoptKgypgCuIvw%3D%3D.

IV-6. Capability Repository A capability statement repository will be kept as an attachment to the BAA. This is meant to encourage teaming and provide a tool for subcontracting opportunities. Offerors may upload a maximum 1 page, 12 font, Times New Roman, capabilities statement document that includes their company name, Cage Code/DUNS number, size considering the NAICS 541715 (1,250 employees), socioeconomic status (e.g., Historically Underutilized Business Zone, Service Disabled Veteran-Owned, Economically Disadvantaged Women Owned, etc.), and a POC along with a brief description of their company capabilities. No classified or proprietary information shall be included in the information provided to the government as this statement will be posted with the BAA and will be accessible to the public. Offerors are solely responsible for information provided for this subcontractor capability repository and providing any documents implies voluntary acceptance of any liability associated therein. This can be submitted along with white papers or separately from white papers. This submission does not count against page limitations established in para. IV-1.1.2. The list will be updated on beta.sam.gov at least quarterly. Participation is completely voluntary. This list will not be used as consideration for award decisions made under this BAA.

IV-7. Highest Security Classification

Some areas, or specific calls, associated with the BAA may require access to classified information up to and including Top Secret, Sensitive Compartmented Information (TS/SCI). A DD254 will be considered before awarding any contract under this BAA.

https://www.afrl.af.mil/Portals/90/Documents/HQ/BAA%20Ind%20Guide%202020.pdf?ver=7AivkWvoUoptKgypgCuIvw%3D%3D https://www.afrl.af.mil/Portals/90/Documents/HQ/BAA%20Ind%20Guide%202020.pdf?ver=7AivkWvoUoptKgypgCuIvw%3D%3D

V. PROPOSAL REVIEW INFORMATION

V-1. White Paper Review Information

The Government will review white papers to determine which of them have the potential to best meet the Air Force’s needs based on the following relative criteria:

V-1.1. Is the technical approach consistent with the technologies listed in para. I-

1. of this BAA, specifically with the technology topic cited on the title page of the white…