FA8650-17-S-2002.pdf

Broad Agency Announcement (BAA)

Open BAA and

BAA with Calls

Overview Information

NAICS Code: The NAICS Code for this acquisition is 541712 (Research and Development in the Physical, Engineering, and Life Sciences (Except Biotechnology) with Aircraft, Aircraft Engine, and Engine Parts exception), and the small business size standard is 1,500 employees.

Federal Agency Name: Air Force Research Laboratory, Aerospace Systems

Directorate, High-Speed Systems Division, AFRL/RQH

Broad Agency Announcement Title: Enabling Technologies for High-speed Operable Systems (ETHOS)

Broad Agency Announcement Type: This is the Initial Announcement

Broad Agency Announcement Number: FA8650-17-S-2002

DUE DATE AND TIME: The BAA is open and effective until 18 January 2024.

White Papers will be considered if received prior to 1500 EST on 18 January 2024.

Only white papers are due at this time. This BAA is set up in two parts: (1)

Open BAA, in which white papers may be submitted at any time during the open period, and (2) BAA with Calls, in which proposal call announcements may be issued by the Government in FedBizOps under FA8650-17-S-2002 at any time during the effectivity of the BAA. The two parts of this BAA are explained in greater detail in separate sections below.

A. OPEN BAA (See Section IV for instructions):

White papers may be submitted at any time during the open period (other than during the “moratorium”) to the Contracting POC IAW the instructions in

Section IV. 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 reviewed. 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 Federal Business

Opportunities website at http://www.fbo.gov in the event this announcement is amended.

NOTE: White Paper/proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). It should be noted that this installation observes strict security procedures to enter the facility. These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the above stated date and time as a result of security delays will be considered “late.” Furthermore, note that if offerors utilize commercial carriers in the delivery of proposals, they may not honor time-of-day delivery guarantees on military installations. Be advised, if the U.S. Postal Service is used, this building only receives U.S. Postal Mail twice a week and delivery by that means may not meet the proposal due date and time established herein. Early white paper/proposal submission is encouraged.

B. BAA with Calls (See Section V for instructions):

Periodically over the period of this BAA, proposal call announcements (Calls) may be issued under FA8650-17-S-2002 to request proposals for specific topic areas. Proposals 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.2). Offerors should monitor the Federal Business Opportunities website at http://www.fbo.gov in the event this announcement is amended or Calls are issued.

Submission: White Papers must be submitted to the Contracting Point of Contact

(POC): Patrick Walsh, AFRL/RQKPA, Bldg 45, 2130 8th St., Wright-Patterson AFB, OH 45433-7541.

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. 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 or Cost). Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract. Firm fixed price contracts may be considered.

Estimated Program Cost: $300M

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:

The High Speed Systems Division within the Air Force Research Laboratory (AFRL) conducts research to develop, demonstrate, integrate and transition high speed vehicle technologies that provide affordable, revolutionary capabilities to the warfighter. Technology developments in high speed systems provide for cost effective weapons and aerospace vehicle platforms capable of accurate and timely delivery of payloads worldwide in support of the Air Force’s desire for rapid, persistent strike/ISR and affordable, responsive space launch. The time frame for development of these capabilities is such that the technologies are demonstrated and matured to a technology readiness level of 6 for mid-term transition in 2025 (persistent engagement) and far-term by 2035 (responsive space launch).

The overall objective is to identify those technologies that support the critical path development of AFRL’s research in the area of high speed systems. Relevant activities include basic, applied, and advanced research to develop, demonstrate, integrate, validate and transition new aerospace technologies. These technologies will enable cost effective, survivable aerospace vehicle platforms operating at Mach 3 and higher. A robust research and development effort may require the use of demonstration vehicles, ground test facilities, flight test facilities, computational studies and modeling, and/or laboratory experiments to develop, analyze, and assess aerospace vehicle system and subsystem performance.

Communication Between Prospective Offerors and Government

Representatives: Dialogue between prospective offerors and Government representatives is encouraged until RFP/Call is issued. Technical and contracting questions can be resolved in writing or through open discussions until RFP/Call is issued. All exchanges with offerors after a RFP/Call is issued 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 questions to the Technical POC:

Keith Bowman, RQH Senior Planner

AFRL/RQH

1950 5th Street, Bldg 18A, Rm A115

Wright-Patterson AFB OH 45433 Tel: 937-255-7328

E-mail address: Keith.bowman.1@us.af.mil

Danelle Williams, Technical Business Specialist

AFRL/RQH

1950 5th Street, Bldg 18A, Rm A106

Wright-Patterson AFB OH 45433 Tel: 937-904-8606 E-mail address: Danelle.williams@us.af.mil

Address contracting questions to the Contracting POC:

Daniel Lyons

AFRL/RQKPA

mailto:Keith.bowman.1@us.af.mil mailto:Danelle.williams@us.af.mil

2130 8th Street, Bldg 45 Wright-Patterson AFB OH 45433

Tel: 937-713-9926 E-mail address: daniel.lyons@us.af.mil

Patrick Walsh

AFRL/RQKPA

2130 8th Street, Bldg 45 Wright-Patterson AFB OH 45433

Tel: 937-713-9949 E-mail address: patrick.walsh.19@us.af.mil mailto:daniel.lyons@us.af.mil mailto:patrick.walsh.19@us.af.mil

Full Text Announcement

I. Program Description (Applicable to both Open BAA and BAA with Calls): Air

Force Research Laboratory, Aerospace Systems Directorate, High-Speed Systems Division, AFRL/RQ, Wright-Patterson Air Force Base is soliciting white papers (and later technical and cost proposals) on the following research effort:

a. Statement of Objectives:

The AFRL High Speed Systems Division leads the integration of subsystems into flight demonstration vehicles to validate advanced technologies and capabilities for reusable high speed aerospace vehicles and global reach hypersonic concepts.

These subsystems include (but are not limited to) propulsion, power & thermal management, structures, communications, guidance/navigation/control (GNC), and sensors. Research is required in the areas of aeroconfiguration design, aerodynamics/aerothermodynamics, propulsion integration (inlets and nozzles), payload integration & deployment, power generation and distribution, hot structure assembly and integrity, fluid-thermal-structural interactions (FTSI), and other technologies that enable the assembly and successful operation of aerospace platforms in Mach 3+ environments, as well as in the environments leading to and from the operating condition(s). The Technical Objectives below further define the desired technology areas.

Technical Objective Area 1 – High Speed Experimental Sciences: Provide research and development of components and diagnostics for high-speed systems/subsystems and their integration into air vehicles, weapons and launch systems. This technical objective seeks to overcome the unique challenges associated with sustained combustion in supersonic flows by conducting experimental and computational research that investigates fundamental phenomena, evaluates prototype and early development concepts associated with high-speed air breathing propulsion components, fuels, systems, and their structural interactions with the vehicle airframe. Develop integration strategies for incorporating systems and subsystems into air vehicles, weapons and launch systems. Research and development efforts should focus on increasing engine scale, control, range of operability, durability and performance, and expansion of skills and tools to advance the state of the art in high-speed propulsion, structural, and external aerodynamics investigations.

Areas of Interest:

High-speed flow physics (internal and external flows) Fuels and fuel injection

Ignition physics Combustion and combustors

Control mechanism to affect engine performance

External flow physics of control surfaces and wing-body junctures

Predicting/controlling boundary-layer (BL) transition and exploiting shock-shock/shock-BL interactions

Thermal loading characterization both for the engine and structural aeroheating

Inflow and exhaust for inlets and nozzles

Diagnostic and modeling tools Flight-worthy sensors

Fluid-thermal-structure interactions

Technical Objective Area 2 – High Speed Propulsion Systems: Research and develop high speed propulsion systems, 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.

High speed propulsion system components

Methods for high speed propulsion system tests High speed propulsion analysis

Aero-propulsion integration Characterization of inlet inflow profile effects Integration of multi-flowpath inlets and nozzles

Additive manufacturing of propulsion system components

Technical Objective Area 3 – Aero-Structures: R&D focused on synergizing aerodynamic and structural interactions throughout a vehicle’s flight, addressing the challenges of minimizing excess weight margins for hot, thick structures, controlling/exploiting thermal growth and deflection, and exploiting hot, thin structures for flow control. Apply new material, structural, and thermal management concepts to improve high speed structures performance.

Efforts may include demonstration flights, vehicle design, experimental research, associated test methods and instrumentation, predictive and diagnostic analysis methods, and modeling and simulation.

Structural response prediction and life forecasting Multidisciplinary modeling and analysis

High temperature mechanical fasteners or novel fastening techniques

Adaptive, multifunctional and/or hybrid hot structures Novel materials or structures concepts Thermal management designs

Power generation and distribution concepts Vehicle conceptual design, integration, and mission/performance analysis Stability and control

Low cost wind tunnel model development Structural design and integration

Payload integration such as on-board sensors and deployable stores

Ground processing and interfaces with other systems Propellant and fluid management Actuation

Technical Objective Area 4 – Modeling and Simulation (M&S): Develop and demonstrate new technologies and capabilities in Simulation Based Research & Development (SBR&D). SBR&D capabilities shall be focused on constructive simulation, virtual simulation, wargaming, hardware-in-the-loop simulation, flight test, multidisciplinary design activities, and application of related tools/techniques needed to develop, evaluate, analyze, and mature aerospace systems technologies and/or system capabilities.

Technical Objective Area 5 – Vehicle Design, Integration and Testing: Design and analysis of high speed flight configurations. Utilization of configuration research, systems engineering and technology assessment principles along with the consideration of reliability, maintainability, safety, training, and logistics aspects to facilitate the design and integration of subsystems into manned and unmanned hypersonic vehicles.

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

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

c. Deliverable Items: Potential deliverables include, but are not limited to:

1) Data Items: [Attachment 2 Contract Data Requirements List (CDRLS)]

A001 – Scientific and Technical Reports (Final Report) – End of Tech Effort

A002 – Performance and Cost Report – Monthly

A003 – Funds and Man-hour Expenditure Report – Monthly

A004 – Contract Funds Status Report (CFSR) – Quarterly

A005 – Status Report – Monthly

A006 – Presentation Material – As Required

A007 – Engineering Drawings – As Generated

A008 – Computer Software Product – As Generated

A009 – Technical Report-Study/Services – As Generated

A010 – Software User Manual (SUM) – As Generated

2) Software: Software deliverables can be anticipated where analytical modeling or code integration takes place. If proposed as a deliverable, it should be clearly identified in the proposal. Unlimited rights are desired for software that is delivered.

3) Hardware: Hardware deliverables in the form of test coupons, samples, subcomponents, and components are anticipated. Hardware deliverables should be clearly identified in the offeror’s proposal.

4) Other: Other deliverables may be required depending on the content of the whitepaper or the requirements of the Call.

d. Schedule:

1) 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. The technical period of performance is not to exceed 60 months.

2) Data Items: The contractor shall provide deliverables in compliance with the Contract Data Requirements List (CDRL), DD Form 1423-1, as established on an individual contract basis.

3) Software: The contractor shall meet specific software deliverable requirements as established on an individual contract basis.

4) Hardware: The contractor shall identify any specific hardware deliverable requirements as established on an individual contract basis.

e. Other Requirements:

1) This announcement incorporates FAR and supplement provisions and clauses by reference. The full text of provisions and clauses can be found at http://farsite.hill.af.mil/.

2) Program Security Classification: Technical work will be conducted at no greater than SECRET. DD Form 254 is attached (Attachment 3). If classified material is involved, a SECRET facility and storage clearance will be required and the proposal should discuss appropriate personnel and facility clearances. Additionally, as a DD254 is applicable, offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil.

3) TEMPEST Requirements: None

4) OPSEC: See I.a. (above) for OPSEC guidance.

5) 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.

6) 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.

http://farsite.hill.af.mil/ http://www.dss.mil/

f. Other Information:

1) Government Furnished Property (GFP) Availability: GFP is not anticipated, but may be requested in the offeror’s white paper, and clearly identified in the proposal. For Calls, any GFP should be clearly identified in the proposal.

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.

2) Base Support/ Network Access: Base support may be proposed.

a) Available Base Facilities: Various structural and propulsion test facilities at Wright-Patterson AFB and Arnold Engineering Development Center.

b) Voluntary Protection Program (VPP): Wright-Patterson AFB is participating in and is pursuing recognition under the Occupational

Safety and Health Administration’s (OSHA) Voluntary Protection Program (VPP), VPP is a systems approach to identify, evaluate, prevent, and control occupational hazards to prevent injuries/illnesses by promoting effective worksite safety and health protection. VPP is required for applicable contractors defined as

“contractors working on an Air Force Installation for more than 1,000 hours per quarter to include construction and services contracts.” Contractors are responsible for managing their own safety and health program (Public Law 91-596). Contractors are advised to become familiar with VPP and how their performance is linked to the installations pursuit of VPP recognition at the OSHA website, http://www.osha.gov/dcsp/vpp/index.html. Applicable contractors are required to submit three years of Total Case Incidence Rate (TCIR)/Day Away, Restricted and/or Transfer Case Rate (DART) data with their proposal for the government’s evaluation. The TCIR and DART are the number of recordable injuries and illness cases per 100 fulltime employees resulting in days away from work, restricted work activity, and/or job transfer that a site has experienced in a given timeframe. Instructions for computing the TCIR and DART data can be found at the OSHA website. Contractors must also provide a copy of their Safety and Health Plan and corresponding site checklist with their proposal which must be accepted by the installation safety officer prior to contract performance. The contractor’s plan shall include appropriate measures to ensure the contractor reacts promptly to investigate, correct and track alleged safety and health violations and/or uncontrolled hazards in contractor work area. Additionally, http://www.osha.gov/dcsp/vpp/index.html installation specific references and policies may be included/attached. The plan shall:

Demonstrate management commitment to employee safety and health;

Identify the application of the safety and health plan to subcontractor;

Identify the roles and responsibilities of the following individuals: Management, Supervisors, Employees, and Safety Coordinator;

Identify applicable safety rules and regulations;

Include a worksite hazard analysis to include base-line hazard identification and required control measures;

Identify a job site analysis to include hazards of tasks required to control measures;

Identify employee safety and health training requirements and the documentation process;

Include a workplace inspection frequency, to include identifying the individual conducting the inspections;

Include employee hazard reporting procedures;

Identify individual(s) responsible for corrective actions hazards;

Identify first aid/injury procedures;

Identify procedures for accident investigation and reporting;

Identify emergency response procedures; and

Identify the process for tracking controlled hazards in contractor work areas.

An applicable contractor is responsible for establishing these requirements for all subcontractors who qualify as applicable contractors under the resulting contract. In addition, applicable contractors will be required to submit their TCIR and DART rates and OSHA Form 300A annually to the contracting office for consolidation and submission as part of the installation’s annual

VPP Safety and Health Management report. TCIR and DART rates are due by the 15th of January of each year.

3) Government Furnished Information (GFI) and/or Software: GFI is anticipated, primarily regarding design requirements, preliminary design concepts and test data. Government supplied software is possible. If needed, GFI may be identified in a request for proposal or call.

4) Data Rights Desired:

a) Technical Data: Unlimited Rights

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

c) NCS Documentation: Unlimited Rights

d) Commercial Computer Software Rights: Customary License

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 technical data and NCS developed or delivered under this contract 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.

In exchange for paying for development of the data, the Government expects technical data, NCS, and NCS documentation developed entirely at Government expense 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 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 technical data, NCS, or NCS documentation subject to Limited Rights, Restricted Rights, or Specifically

Negotiated License Rights will be considered. Proposals 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 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 will be included in Section K and due at time of proposals. Assertions must be completed with specificity. Each assertion must identify both the data and each such item, component, or process listed. Nonconforming assertions lists will be rejected.

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):

DFARS 252.227-7014(d) describes requirements for incorporation of third party computer software. Any third party software (commercial and noncommercial) to be incorporated into a deliverable must be clearly identified in the proposal. Prior to delivery of any third party software, the contractor will obtain an appropriate license for the Government, and the written approval of the contracting officer.

Any third party software to be delivered to the Government that are not reasonably identifiable at proposal submission, must still be approved by the contracting officer prior to incorporation into a system deliverable.

This obligation to obtain pre-approval by the contracting officer, as described above, continues throughout contract administration.

The Government will neither accept nor execute a DD Form 250 for the software deliverables until the Contractor obtains from all third party software suppliers and/or vendors (Licensor) licenses that comply with the following terms and conditions for the Government (Licensee):

1. The license shall not subject the Government to liability that is indefinite or indeterminate, such as an indemnification clause, as it would constitute an obligation in advance or in excess of an appropriation and violate the Anti-Deficiency Act.

2. The license shall not create a contingent liability for the Government.

This includes, but is not limited to: unilateral price increases, automatic assessment of charges, and automatic renewal of the license.

3. The license shall be governed by Federal Statutes, Case Law, and

Federal Regulations, and shall not be subject to the laws or jurisdiction of any municipality, state, or foreign country.

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

5. The license shall not comment on entitlement to attorney fees.

6. The Licensor shall not have the authority to unilaterally terminate the license. All remedies available shall be consistent with the Disputes

Clause in the underlying basic contract.

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

8. The Licensor shall not use any injunctive relief clauses as the Licensor cannot prevent the Licensee from performing mission operations.

9. The Licensor shall not have the authority to control any litigation between a third party and the Licensee.

10. The Licensor shall not use the fact that the Licensee is using the

Licensor's products in any notification to the public (e.g., no publicity rights permitted).

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

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

2. 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 ETHOS. In performance of ETHOS, Government personnel as well as Government contractors may use the software.

3. The license shall not limit the Government’s use of the software at other Government and Government contractor sites.

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

5. The Licensee shall not be restricted 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 to 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 and/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.

The Contractor shall provide documentation to clearly correlate or map software license(s) 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 software corresponding to certain software license agreement(s) are physically located on the system to be delivered under the contract.

II. Award Information (Applicable to both Open BAA and BAA with Calls)

a. Anticipated Award Date: This is an 84 month 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 seven year period.

Periodically over the 84 month period, Call announcements may be issued to FedBizOps to request proposals for specific research efforts. Awards are anticipated as a result of these Calls.

b. Anticipated Funding for the Program

This funding profile is an estimate only and not a contractual obligation for funding. All funding is subject to change due to Government discretion and availability. All potential offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.

FY17 $5M

FY18 $15M

FY19 $30M

FY20 $50M

FY21 $60M

FY22 $60M

FY23 $60M

FY24 $20M

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.

III. Eligibility Information (Applicable to both Open BAA and BAA with 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 Technical POC 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:

1) Foreign Participation: Foreign Nationals (FNs) can be employed by the US Prime Contractor or Sub-Contractor; however, FNs will be limited to Public

Domain information unless the contractor has obtained the proper License or Technical Assistance Agreement that authorizes disclosure of CMI and/or CUI to foreign entities pursuant to the Department of State’s ITAR or Department of Commerce’s EAR.

2) 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 Services Center (DLSC) and have a legitimate business purpose may participate in this solicitation. Contact the Defense Logistics Services Center, 74 Washington Avenue N., Battle

Creek, Michigan 40917-3084 (1-800-352-3572) 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.

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

4) Eligibility: You may be ineligible for award if all requirements of this solicitation are not met on the white paper/proposal due date.

IV. Basic Open BAA Section (This is a two-step process)

a. WHITE PAPER SUBMISSION INFORMATION (Step 1):

1) Overview:

This Announcement 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.

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 http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf?

2) White Paper Instructions:

a) 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 http://www.dlis.dla.mil/jcp/ http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf approach. The Government will review the white papers in accordance with the FIRST STEP considerations set forth in Section IV. c. 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. It is anticipated that Government review of the white papers submitted will take 30 days.

Those offerors submitting white papers assessed as meeting Air Force needs will be asked to submit a technical and cost proposal. Those offerors not requested to submit a technical and cost proposal will be notified. The cost of preparing white papers in response to this Solicitation is not considered an allowable direct charge to any resulting or any other contract; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in FAR 31.205-18.

Offerors should submit a paper version of the White Paper to the

Contracting POC identified in the “Submission” Paragraph of the Overview Information. Please also email an electronic copy to the Contracting POC identified in the “Overview Information” section.

For each CALL that is announced pursuant to this BAA (see Section V below), 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 reviewed.

b) Page Limitation: The White Paper shall be limited to 10 pages, prepared and submitted in Word format. Font shall be standard 10-point business font Arial. Character spacing must be “normal,” not condensed in any manner. Pages shall be double-spaced (must use standard double-space function in Microsoft Word), double-sided (each side counts as one page),

8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom. All text, including text in tables and charts, must 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. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items. Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page 11. The page limitation covers all information including indices, photographs, foldouts (counted as 1 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.

c) Format: The white paper will be formatted as follows:

1) Section A: BAA Number, Title of Program, Technical Objective

Area and Area of Interest, Name of Company, Business Size, Company’s Commercial and Government Entity (CAGE) number, Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, Contracting POC and Technical POCs with appropriate telephone numbers, and email addresses for the POCs. For submissions that will result in classified work, add the following information: Classified level at which company is cleared, contractor address for forwarding classified material (name, address, zip code), cognizant security office (name, address, zip code), and offeror’s security officer’s name and telephone number).

2) Section B: Period of Performance and Task Objectives;

3) Section C: Technical Summary and Proposed Deliverables; and

4) Section D: Cost of Task (Rough Order of Magnitude (ROM))

d) Technical Portion: 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 are not required at this point.

e) Cost Portion: The cost portion of the white paper shall include a ROM cost estimate. No detailed price or cost support information should be included; only a time-phased bottom line figure should be provided.

f) 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). See Para. IV.a.2)a) above regarding the “moratorium.”

g) White Paper/Proposal Content Summary: You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date.

b. PROPOSAL SUBMISSION INFORMATION (Step 2):

1. General Instructions:

a) The SECOND STEP consists of offerors submitting a technical and cost proposal within 30 calendar days of a request for proposal. After receipt, proposals will be evaluated in accordance with the award criteria in

Section IV. c. below. Proposals will be categorized and potentially selected for negotiations.

b) Offerors should apply the restrictive notice prescribed in FAR 52.215-1(e) Instructions to Offerors—Competitive Acquisition. Offerors should consider proposal instructions contained in the Broad Agency Announcement (BAA)

Guide for Industry, which can be accessed on line at http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf. This guide is specifically designed to assist the offeror in understanding the BAA proposal process.

c) Technical/management and cost/business volumes should be submitted in separate volumes and must be valid for 180 days.

d) Proposals must reference the announcement number FA8650-17-S-2002, the relevant Technical Objective Area (1, 2, 3, 4 or 5) and, if applicable, the “Area of Interest.”

e) Offerors must submit one original paper proposal and one hard copy of their proposals to the Contracting POC.

f) Offerors must include one (1) CD in Microsoft Office or Adobe format containing all electronic versions of required submittals. All electronic versions must match the hard copies.

1) The cost file(s) spreadsheets must be in Microsoft Excel and include the formulas for calculating cost element bases (i.e., G&A, O/H, etc.)

2) The CDs should be labeled with the company name and proposal title.

g) Offerors are advised that only Contracting Officers are legally authorized to contractually bind or otherwise commit the Government.

h) The cost of preparing proposals in response to this BAA is not considered an allowable direct charge to any resulting or any other contract;

however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in FAR 31.205-18.

i) No classified technical proposals or cost volumes are expected. Offerors are encouraged to keep all elements of the proposal package unclassified.

In the rare case where an offeror has a need to submit a classified appendix, please contact the technical POCs for delivery instructions.

2. Technical/Management Proposal:

a) Page Limitations: The following describes proposal page limitations:

1) The Technical/Management Proposal shall be limited to twenty-five (25) pages. Technical/Management proposals and Statements of Work must be provided in Microsoft Word. Signed pages may be submitted in Adobe.

2) Font shall be standard 10-point business font Arial.

3) Character spacing must be “normal,” not condensed in any manner.

4) Pages shall be double-spaced (must use standard double-space function in Microsoft Word), double sided (each side counts as one page), 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom.

5) All text, including text in tables and charts, must 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. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items.

6) Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page 26. The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5 by 11 portion) tables, charts, appendices, attachments, resumes, etc.

7) The proposal page limit does not include the offeror’s proposed Statement of Work (SOW); however, the same formatting rules apply to the SOW, which is limited to five (5) pages.

8) Please Note: The Government will check the proposal and SOW for conformance to the stated requirements. Any pages in excess of the stated page limitation after the format check will not be considered for evaluation purposes.

b) The Technical/Management proposal(s) shall include a discussion of the nature and scope of the research and the technical approach. Additional information on prior work in this area, descriptions of available equipment, use of base support (if requested), data and facilities and resumes of personnel who will be participating in this effort should also be included as attachments to the technical proposal. These volumes shall include a SOW detailing the technical tasks proposed to be accomplished under the proposed effort and suitable for contract incorporation. Do not include any proprietary information in the SOW. Refer to the BAA Guide for Industry referenced above to assist in SOW preparation. In addition to the contractor proposed SOW, a Government generated supplemental SOW containing additional contracting requirements may be included in any resulting contracts. The Supplemental SOW (Attch 5) may be included as necessary as an attachment to a request for proposal.

c) Any questions concerning the technical proposal or SOW preparation shall be referred to the Contracting POC.

3. Cost/Business Proposal:

http://www.afrl.af.mil/contract/default.htm

a) Separate the proposal into a business section and cost section. Adequate price competition is not anticipated.

1) The business section should contain all business aspects to the proposed contract, such as type of contract, any exceptions to terms and conditions of the announcement including the Model Contract (Attch 4), any information not technically related, etc. Provide rationale for exceptions.

2) Associate Contractor Agreements: Associate Contractor Agreements

(ACAs) are agreements between contractors working on Government contracts that require them to share information, data, technical knowledge, expertise, or resources. The contracting officer may require ACAs when contractors working on separate Government contracts must cooperate, share resources or otherwise jointly participate in working on contracts or projects. Prime contractor to subcontractor relationships do not constitute ACAs. For each award, the contracting officer will identify associate contractors with whom agreements are required.

3) Identify any technical data that will be delivered with less than unlimited rights.

4) Subcontracting Plans: For efforts to exceed $700,000, Subcontracting Plans shall be submitted in the cost/business proposal. Reference FAR

19.704, DFARS 219.704, and AFFARS 5319.704(a)(1) for subcontracting plan requirements. Small business concerns are exempt from this requirement. Page limitations do not apply to this requirement.

5) Limitations on Pass-Through Charges: As prescribed in FAR 15.408(n)(1) & 15.408(n)(2), provisions 52.215-22, “Limitations on Pass Through

Charges- Identification of Subcontract Effort (Oct 2009),” apply.

6) Completed Certifications and Representations (Section K – Attch. 4) are due with the proposal. Offerors may also be required to submit updated or supplemental Certifications and Representations based on the specifics of their proposal.

7) If an offeror proposes the use of Government Furnished Property (GFP), the offer must specifically identify each piece of GFP in the Cost/Business

Proposal and propose and substantiate a rental cost for evaluation purposes in accordance with FAR 45.202. Include the following information in the proposal:

a) A list describing all Government property that the offeror or its subcontractors propose to use on a rent-free basis. The list shall identify the accountable contract under which the property is held and the authorization for its use (from the contracting officer having cognizance of the property);

b) The dates during which the property will be used and, for any property that will be used concurrently in performing two or more contracts, the amounts of the respective uses in sufficient detail to support prorating the rent;

c) The amount of rent that would otherwise be charged in accordance with FAR 52.245-9, Use and Charges; and

d) The voluntary consensus standard or industry leading practices and standards to be used in the management of Government property, or existing property management plans, methods, practices, or procedures for accounting for property.

b) Cost Element Breakdown: Clear, concise, and accurate cost proposals reflect the offeror's financial plan for accomplishing…