DARPA-BAA-16-45.pdf

DARPA-BAA-16-45

Broad Agency Announcement

ADVANCED FULL RANGE ENGINE (AFRE)

PROGRAM

Tactical Technology Office

DARPA-BAA-16-45

12 August 2016

Contents

PART I: OVERVIEW INFORMATION

PART II: FULL TEXT OF ANNOUNCEMENT

I. Funding Opportunity Description II. Award Information III. Eligibility Information

A. Eligible Applicants B. Procurement Integrity, Standards of Conduct, Ethical Considerations, and Organizational Conflicts of Interest C. Cost Sharing/Matching

IV. Application and Submission Information A. Address to Request Application Package B. Content and Form of Application Submission

V. Application Review Information A. Evaluation Criteria B. Review and Selection Process

VI. Award Administration Information A. Selection Notices B. Administrative and National Policy Requirements C. Reporting D. Electronic Systems

VII. Agency Contacts VIII. Other Information

A. Intellectual Property Procurement Contract Proposers B. Non-Procurement Contract Proposers – Noncommercial and Commercial Items (Technical Data and Computer Software) C. All Proposers – Patents D. All Proposers – Intellectual Property Representations

APPENDIX A – DARPA Tailored Critical Design Review Criteria APPENDIX B – Technical and Performance Data Sheets APPENDIX C – Cost Summary Spreadsheet

PART I: OVERVIEW INFORMATION

Federal Agency Name – Defense Advanced Research Projects Agency (DARPA), Tactical Technology Office (TTO)

Funding Opportunity Title – Advanced Full Range Engine (AFRE) Program Announcement Type – Initial announcement Funding Opportunity Number – DARPA-BAA-16-45 Catalog of Federal Domestic Assistance Numbers (CFDA) – Not

Applicable Dates o Proposers Day: 13 July 2016 o Posting Date: 12 August 2016 o Questions Due: 31 August 2016 o Proposals Due: 28 September 2016

Concise description of the funding opportunity – The AFRE program will be a two-phased effort to conduct component-level and full scale ground-based testing of a reusable propulsion system that will enable future long range hypersonic air vehicle applications.

Total amount of money to be awarded – Approximately $65M (Phase I and II) Anticipated individual awards – A singe award is anticipated.

Types of instruments that may be awarded -- Procurement contract or other transaction agreement.

Agency contact – The BAA Coordinator for this effort can be reached at:

DARPA-BAA-16-45@darpa.mil mailto:DARPA-BAA-16-45@darpa.mil

PART II: FULL TEXT OF ANNOUNCEMENT

I. Funding Opportunity Description

The Defense Advanced Research Projects Agency often selects its research efforts through the Broad Agency Announcement (BAA) process. This BAA is being issued, and any resultant selection will be made, using procedures under Federal Acquisition Regulation (FAR) 35.016. Any negotiations and/or awards will use procedures under FAR 15.4, Contract Pricing, as specified in the BAA. Proposals received as a result of this BAA shall be evaluated in accordance with evaluation criteria specified herein through a scientific review process. DARPA BAAs are posted on the Federal Business Opportunities (FedBizOpps) website, http://www.fbo.gov/. The following information is for those wishing to respond to the BAA.

DARPA is seeking innovative propulsion system solutions that will expand the knowledge base and design capabilities for future hypersonic air vehicles. The use of a BAA allows a wide range of innovative ideas and concepts, and proposer(s) will have the flexibility to develop a tailored program plan that best meets Advanced Full Range Engine (AFRE) program objectives.

The primary goal of the AFRE program is to develop and ground demonstrate a reusable hydrocarbon propulsion system that can seamlessly operate over the full range of speeds between Mach 0 and Mach 5+ to enable responsive hypersonic aircraft for missions such as penetrating and providing unwarned Intelligence, Surveillance, and Reconnaissance (ISR) in denied environments. Based on ongoing research and development activities across the Government and industry hypersonic research and development community, DARPA believes that a dual flowpath engine such as a Turbine Based Combined Cycle (TBCC) system offers the best solution for a future hypersonic air vehicle. A TBCC system combines a turbine engine for low-speed operations with a dual mode ramjet (DMRJ) for high-speed operations via a common inlet and nozzle serving both the low-speed and high-speed flowpaths. This design concept is enabled by advances made in the previous AFRL/DARPA funded X-51 scramjet engine flight demonstration program and the DARPA Falcon Combined-cycle Engine Technology (FaCET) program.

A recent DARPA study and industry IRAD efforts have shown promise in lowering the Mach number operating range of the high-speed portion of the engine (the DMRJ). This last development facilitates integration of the high- and low-speed flow paths and enables a near term, affordable demonstration with existing turbine engine technology.

While the Government believes the TBCC offers the best approach for achieving program objectives, proposers may propose alternative propulsion system concepts, provided those concepts have the technical maturity to support the proposed demonstration schedule and adequate performance margin to support future hypersonic air vehicle applications. Successful proposers will propose robust AFRE conceptual designs that could be modified and integrated into multiple aircraft designs versus a single point aircraft solution. DARPA is only interested in proposals addressing full system solutions for http://www.fbo.gov/

AFRE. DARPA is not interested in lower Mach solutions such as a turbo-ramjet or solutions that use accelerants.

Given the highly integrated nature of hypersonic airframes and propulsion systems, DARPA is currently sponsoring air vehicle conceptual design studies to provide early guidance and insights to the AFRE effort to ensure the demonstration system is relevant to future hypersonic air vehicle designs. DARPA expects the AFRE program to be performed by a collaborative team of propulsion system and airframe contractors. DARPA believes this approach will maximize success on the program, offering the quickest path towards enabling a future hypersonic vehicle flight demonstration.

A. Program Vision

Future U.S. military operations against peer/near-peer adversaries will be severely hampered by erosion in the availability of timely information from airborne ISR. Fielding of fifth generation aircraft equipped with capable air-to-air missiles, proliferation of highly capable Integrated Air Defense Systems (IADS), and other long-range defensive capabilities directly challenge the information superiority the U.S. has enjoyed with ISR capabilities provided by airborne platforms. These platforms, developed for more permissive threat environments, are unable to access more contested battlespaces. With space also becoming contested, our unique ability to observe, orient, decide, and act (OODA) within an adversaries’ OODA loop is diminishing, sacrificing U.S. decision-making superiority. Without a survivable airborne ISR capability to complement space ISR capabilities, the effectiveness of future U.S. offensive strike operations may be limited.

To meet future requirements, DARPA envisions a survivable and affordable hypersonic regional ISR aircraft with the following attributes:

• Range greater than 1200 nm

• Speed greater than Mach 5

• 60,000+ ft operation

AFRE is one of the key enabling technologies for this envisioned future aircraft application. This program will address the critical technologies enabling the required operating regimes and demonstrate the viability of the AFRE system to propel future hypersonic aircraft into our most challenging environments. The program will focus on consistently and seamlessly transitioning the propulsion system from low-speed to supersonic to hypersonic speeds, and the reverse, in a safe and affordable manner. At a minimum, the AFRE demonstration system must be full scale to be considered relevant to this future hypersonic aircraft application. AFRE demonstration systems that show higher degrees of traceability/maturity to a future flight capable engine will be viewed more favorably, as they have higher relevance to the DARPA mission and program transition.

For the purposes of this BAA, “full scale” is defined to mean that for the AFRE demonstration system, the high-speed flow path is matched to the selected off-the-shelf turbine so as to have maximum relevance to a future hypersonic ISR flight vehicle and potential to be further developed into a flight demonstration engine.

B. System-Level Performance Capabilities and Propulsion System Requirements

Based on the body of prior hypersonic air vehicle and propulsion system work, DARPA believes that an AFRE must be consistent with the following system-level capabilities to have adequate performance:

• Successful Mode Transition (between Mach 1.5 and Mach 3)

• Extended turbine operation

• Extended DMRJ operation

• Positive Thrust Margin

• Acceleration: 0.25g minimum in level flight at transonic pitch point and during mode transition

• DMRJ Combustion Efficiency during mode transition (75% - 80%)

• DMRJ Combustion Efficiency at maximum Mach (85% - 90%)

• Thermal Management/Cocooning

• Turbine engine within specs

• Turbine engine restart simulated at supersonic vehicle speed conditions

The proposer must develop specific metrics appropriate for their system approach, provide rationale for how those metrics were derived, substantiate how their proposed system meets those requirements, and provide requisite air vehicle design and performance analysis that shows that their proposed design will yield a viable air vehicle system. Note that certain specific performance metrics achievable by a particular design may be classified. Proposers must read and adhere to the program classification guide in their proposal response.

Outside the scope of this BAA, DARPA is sponsoring air vehicle conceptual design trade studies that have a 6-month period of performance and are expected to be completed during the first quarter of calendar year 2017. These studies will result in additional inputs for consideration as the performer develops AFRE demonstrator system requirements (performance, sizing, materials, etc.) for the inlet, nozzle, turbine, controls, and combustor.

It is expected that the AFRE performer will incorporate these requirements into their AFRE design process and continue to iterate propulsion and air vehicle designs to ensure that the propulsion system developed for the AFRE program ground demonstrations continues to be relevant for the future hypersonic ISR aircraft application.

A non-proprietary Government baseline vehicle will also be developed and provide another source of independent propulsion/aeropropulsion integration results and systems/threat analyses. The results of the Government baseline system and threat analysis will be made available to the performer. Differences in propulsion system performance between the Government baseline and contractor concepts should be explored in the performer’s design, analyses, and test plans.

C. Program Plan

The AFRE program will be conducted in two phases (Phase I base period and Phase II option) with a single performer team expected. DARPA plans to invest approximately $65M over the two phases. Program continuation beyond Phase I (base) will depend on promising Phase I results. DARPA has developed a notional baseline schedule, shown in Figure 1, which includes the envisioned top-level program activities.

Phase I will be comprised of subscale and full scale component ground-based testing. Phase I will progressively mature the design and component technologies required to enable a full AFRE system-level demonstration and validate the ability to achieve AFRE system performance. DARPA envisions a build-up demonstration approach that provides incremental progress towards full scale component performance validation traceable to meeting system-level objectives. For affordability, DARPA also envisions that some or all of the full scale component hardware (inlet, DMRJ, Nozzle, duct/turbine) developed and tested in Phase I can be reused and integrated into the Phase II demonstration system. At the end of Phase I, DARPA will conduct a system-level critical design review for the full scale AFRE demonstration system that incorporates the results of the component testing. This review will enable the Government to assess whether the Phase I component-level performance metrics have been achieved and indicate that the AFRE performance goals are achievable and to determine whether it is technically and fiscally prudent to continue with the Phase II full system demonstration.

Phase II will consist of incremental full scale system integration and testing, culminating in integrated full AFRE system ground-based freejet testing.

Figure 1. Notional AFRE Program Schedule

Proposers should propose their own more detailed schedule tailored to their unique AFRE design and technology maturation approach. This schedule should contain additional key program events such as System Requirements Review (SRR) and Preliminary Design Review (PDR). It should be noted that DARPA is open to innovative or high-value development approaches that achieve program goals more rapidly than the notional schedule in Figure 1. The following sections describe the specific technical objectives of Phase I and Phase II.

D. Government Furnished Equipment and Information (GFE/GFI)

Technical Information: As described above, DARPA will provide the performer with the results of the Air Vehicle Conceptual Design Framing Studies as they become available. DARPA will also provide the performer with analysis and test results from the TBCC Maturation activities (Water Injection with an F405-RR-402 Turbine Engine and the Low Mach DMRJ Free-Jet) as they become available.

Turbine Engine: The Government intends to provide an off–the-shelf F-405-RR- 402 turbine engine for integration into the AFRE demonstration system. Proposers may elect to use an alternative turbine engine; however, the performer is responsible for identifying the source and availability of the alternative engine, and any cost associated with that engine will be counted against the total amount of funding available to the performer. Information on the F-405-RR-402 turbine engine availability timeline and associated technical data can be made available upon the proposers’ request to DARPA- BAA-16-45@darpa.mil.

Integrated Controls: The Government will provide NASA-developed autonomous mode transition control laws/algorithms that will be experimentally validated for low Mach mode transition of a representative integrated TBCC propulsion system using an off-the-shelf turbine engine and an advanced dual mode ramjet (or simulator).

Test Facilities: If the performer agrees to share all test data with NASA with Government Purpose Rights, NASA will waive facility costs for occupancy (test set up) and operations for the following facilities: NASA Langley's 8-FT High Temperature Tunnel, NASA Glenn's Propulsion System Laboratory (PSL) and NASA Glenn's 10X10 supersonic wind tunnel. The only costs that are not waived will be special test equipment/fixtures, fuel, consumables, and power. These costs should be included as part of the proposer’s cost estimate.

Any additional GFE, including test facilities and facility upgrades, must be identified and priced in the proposal. These GFE items will count against the total funding available.

E. Phase I (Base Period) Objectives

The primary objectives of Phase I are to:

• Conduct iterative airframe and propulsion system trade studies and analysis to develop system-level AFRE demonstration system requirements and derive system component performance requirements that meet program objectives

• Conduct risk reduction and component-level performance validation activities

• Develop a detailed system-level design to enable a system-level critical design at the completion of Phase I, integrating the results of all of the component test activities to validate the ability to achieve the AFRE demonstration system-level objectives

• Support ongoing Government program planning, documentation and transition activities

The performer should implement a disciplined systems engineering process to ensure a successful full AFRE system integration and demonstration in Phase II.

The Phase I results must convince DARPA that: (1) AFRE is a feasible and effective option for enabling future hypersonic air vehicles; (2) there is adequate technology maturity and performance capability to perform the AFRE system-level demonstration within the Phase II program schedule and budget; and (3) continuation into Phase II is warranted. More detail on each of the Phase I objectives is provided in the following paragraphs.

Design and Analysis The performer shall conduct integrated airframe and propulsion design trades leveraging the initial Government-funded air vehicle conceptual design framing studies.

The objective of these design activities will be to develop a full set of system-level requirements for the AFRE demonstration system to enable Phase II freejet testing and performance validation of a propulsion system that is relevant to a future hypersonic ISR air vehicle application. The goal is for the AFRE demonstration system to be full scale and as representative as possible of a future flightworthy engine, within program cost and schedule constraints. To assist Government future planning efforts, the performer shall clearly identify any areas where the system would require additional development to enable flight demonstration, as well as a rough order of magnitude of the cost and schedule for additional development work. As part of the design and requirements analysis activities, the performer will decompose the system-level requirements into component-level design and performance requirements and refine their proposed AFRE Maturation Plan (AMP) as needed.

Component-Level Risk Reduction The performer will conduct component-level risk reduction and performance validation for their proposed AFRE demonstration system design in accordance with their AMP. The Government envisions that a combination of subscale and full scale component testing will be needed to mature the inlet and nozzle designs to support low- and high-speed operations. For the high-speed flow path, the critical risk reduction activities will be focused on validating full scale combustor performance across the required Mach number range and feasibility for integration and mode transition with the F-405-RR-402 GFE engine. For the low-speed flow path, risk reduction activities will be conducted for any high risk integration or F-405-RR-402 modification activities or its equivalent.

In order to substantiate the feasibility and technology maturity to be able to meet the AFRE demonstration system performance objectives, DARPA has established the following minimum full scale component-level demonstration success metrics for Phase I:

Matched mass flow during mode transition matches total inlet mass capture within 2%

High-speed flow path combustion efficiency greater than 75% during mode transition

High-speed flow path combustion efficiency greater than 80% at maximum Mach number

Extended turbine operation while maintaining manufacturer’s specifications Extended high-speed flowpath combustor operation down to Mach 2.5 minimum with goal to demonstrate minimum Mach at light-off, minimum Mach for reduced drag, and minimum Mach with thrust

Component manufacturing estimates consistent with vehicle design engine allocation

The performer should supplement this list with additional demonstration objectives to fully validate component-level performance for their unique AFRE demonstration system design.

Detailed Design The performer shall fully document their proposed system-level design and interfaces. The Government anticipates rolling component-level critical design reviews (CDRs) during Phase I to support full scale component fabrication and risk reduction testing. The proposer must provide a disciplined and detailed rolling CDR approach that tracks component design and interface requirements and feeds into the final full system CDR and final Interface Control Document (ICD).

Support of Government Planning, Documentation and Transition Activities The performer will participate in ongoing Government-related activities to assist in maintaining program advocacy. The Government will internally maintain and update ongoing air vehicle baseline designs to analyze and integrate AFRE program results. The performer will support these design activities by providing periodic updated AFRE design and performance information. The performer will also assist in the development of ROM cost and schedule information to support future program planning.

F. Phase I (Base Period) Deliverables

DARPA desires that the program include quarterly program reviews at the contractor’s facility. The objective of these reviews will be to assess progress, provide feedback and stay abreast of any emerging technical, cost, or schedule issues. DARPA will staff a team of subject matter experts from Government and support contractors to attend program reviews to provide feedback to the Program Manager. In addition to formal program reviews, regular telecoms are encouraged to enhance communications with the Government team. To successfully achieve the Phase I objectives, DARPA has developed a minimum list of deliverables that must be included in the proposer’s Phase I program.

The desired content at each review is described below. Proposers should populate their program schedule with these minimum deliverables and supplement this list with additional deliverables/material to be presented at each quarterly review in accordance with their unique program schedule and development approach. It is envisioned that routine system design updates, technical status reviews, and results of any risk reduction activities/component demonstrations will be provided at each quarterly review.

Kick-off Meeting The objective of the kick-off meeting will be to discuss the performer’s approach to the program and provide feedback to guide the performer in executing their Phase I program. The Government and the performer will also establish the program review schedule as well as a schedule of interim informal interactions, including routine management and technical telecoms.

System Requirements Review (SRR) An SRR will be conducted early in Phase I to review the results of the requirements analysis and derivation process. The objective of SRR will be to determine the adequacy of the AFRE demonstration system functional and performance requirements, and to ensure the requirements and the demonstration system design will satisfy the program objectives.

Preliminary Design Review (PDR) A PDR will be conducted early in Phase I to assess the maturity of the AFRE demonstration system design. The objective of PDR will be to ensure the AFRE demonstration system preliminary design and architecture can be integrated into a system, is ready for detailed design, and can be produced at an acceptable level of risk that satisfies the technical objectives/capabilities within cost and schedule.

At this review, the Government will evaluate the progress, technical adequacy, and risk of the AFRE demonstration system design; assess its compatibility with AFRE performance requirements and demonstration objectives; and establish the existence and compatibility of the physical and functional interfaces. For software items, the Government will evaluate the consistency and technical adequacy of the design and test approach, and compatibility between software requirements, test requirements and the preliminary design. Specific PDR objectives are as follows:

Requirements (system, lower level, and interface) are derived/quantified and verification methods defined

Preliminary design (hardware and software) is traceable to, consistent with, and satisfies the demonstration system requirements

Performance capabilities are substantiated by analysis and/or test results that use representative/achievable inputs

Modeling, simulation, and analysis at the system and subsystem/component-level are sufficient and contain an appropriate environment supporting readiness for detailed design

Assembly, integration, and test approach, including both hardware and software (at the system and subsystem/component-level) define the type of testing required at each level of the system, present general and specific requirements that will be demonstrated and the associated evaluation activities, describe the required test-unique support software, hardware, facilities/range (including any GFE), and other resources, testing limitations, and the interrelationship of these items including schedule aligned with the program IMS

Traceability documentation of the demonstration system to future air vehicle designs is maintained, including deviations/differences and updated risk assessments

Phase I Component-Level Risk Reduction and Demonstration Results The performer will report on the results of component-level risk reduction and demonstration activities. Demonstration results should be presented at quarterly reviews and include an assessment of performance with relation to the AFRE system-level objectives. The performer shall provide a comparison of pre-test predictions with measured data along with analysis of the implications of any differences. If the component-level testing does not achieve desired performance, the performer shall describe potential remediation activities.

Critical Design Review At the completion of Phase I, the performer shall complete a system-level CDR capturing the detailed design and performance predictions for the AFRE demonstration system. The objective of the CDR will be to ensure the demonstration system critical design and architecture can be integrated into a system, is ready for assembly, integration, and test, and can be produced at an acceptable level of risk that satisfies the technical objectives/capabilities within cost and schedule. This design review shall incorporate the results of the component-level risk reduction to ensure that the detailed design solution satisfies the baselined requirements derived from AFRE program objectives. This review shall establish a “build-to” design, validate compatibility among the components, assess component risk areas, demonstrate the capability to fabricate, code and integrate hardware and software and review the hardware drawing and work packages. The Government’s expectations and success criteria for CDR are detailed in Appendix A.

Government Technical, Program Planning and Transition Data The performer shall propose a nominal level of effort to generate data in support of

Government baseline vehicle analysis, future program planning, and transition discussions.

In Phase I, it is envisioned that the focus of these activities will be in establishing robust system-level design and performance requirements for the AFRE demonstration system that are traceable to the future hypersonic ISR vehicle application. The proposer should propose the scope and timing of the information provided consistent with their program schedule and budget.

G. Phases II (Option Period) Objectives

The decision to continue the program into Phase II will be based in part upon the Government’s determination that the performer has successfully completed Phase I with a feasible design that has adequate performance and an executable Phase II plan. The decision to continue the program into Phase II is the prerogative of the Government and will be based upon the availability of funds and the determination that performers have met the Phase I success metrics defined above.

The performer will perform full system integration of the inlet, nozzle, high-speed flow path and low-speed flow path, culminating in full AFRE demonstration system freejet testing. In addition, the performer will continue to support Government technical analysis, program planning, and transition activities.

System Integration and Test It is envisioned that the full scale components developed in Phase 1, along with the

GFE F-405-RR-402 engine, will be combined into an integrated test series including interim subsystem integration and test activities to reduce risk for the full system test.

Following full system assembly and integration, the performer shall conduct a freejet test of their full scale AFRE demonstration system.

In order to substantiate AFRE feasibility and technology maturity to support the future hypersonic ISR air vehicle application, DARPA has established the following minimum AFRE system demonstration success metrics for Phase II:

Successful mode transition traceable to minimum air vehicle acceleration of 0.25g maintained at transonic pitch point and during mode transition

Turbine engine thermal management/cocooning o Turbine engine within specifications during operation o Turbine engine non-operating temperatures within manufacturer’s specifications o Turbine engine safe shutdown and restart simulated at supersonic vehicle speed conditions

Support of Government Planning, Documentation and Transition Activities The performer shall propose a nominal level of effort to generate data in support of

Government baseline vehicle analysis, future program planning, and transition discussions.

The performer will continue to support baseline vehicle system design activities by providing periodic updated AFRE design and performance information. The performer will also assist in the development of ROM cost and schedule information to support future program planning and other transition activities.

H. Phase II (Option Period) Deliverables

In Phase II, DARPA desires the continuation of the quarterly program review and routine teleconference schedule established in Phase I.

To successfully achieve the Phase II objectives, DARPA has developed a minimum list of deliverables that must be included in the proposer’s Phase II program. The desired content for these deliverables is described below. Proposers should populate their program schedule with these minimum deliverables and supplement this list with additional deliverables/material to be presented at each quarterly review in accordance with their unique program schedule and development approach. It is envisioned that routine system design updates, technical status reviews and results of any risk reduction activities/component demonstrations will be provided at each quarterly review.

System Integration Incremental Testing and Full System Demonstration Results The performer will report on the results of their system integration work as they build up to their full AFRE demonstration system. This may include subsystem testing and performance validation, system checkout testing or other interim activities. These results should be presented at quarterly reviews and, as appropriate, the performer will also report on all full AFRE demonstration system testing, including at a minimum the results of the freejet test. For all test activities, the performer shall provide an assessment of performance with relation to the AFRE system-level objectives. The performer shall provide a comparison of pre-test predictions with measured data along with analysis of the implications of any differences. If the test results do not achieve desired performance, the performer shall describe potential remediation activities. Following completion of the freejet testing, the performer shall provide a comprehensive technical report fully documenting the integrating results of the AFRE test program. This report shall include an analysis of the test data, including implications for full system performance and operating envelope, additional development required, and impact on air vehicle performance.

Government Technical, Program Planning and Transition Data The performer shall propose a nominal level of effort to generate data in support of

Government baseline vehicle analysis, future program planning, and transition discussions.

In Phase II it is envisioned that these activities will focus on updated air vehicle performance analysis and air vehicle integration and flight test planning. The proposer should propose the scope and timing of the information provided consistent with their program schedule and budget. At the completion of Phase II, the performer shall provide an AFRE development roadmap outlining additional activities (if any) required to mature the demonstration system to enable future flight demonstration.

I. Options

At this time, DARPA only intends to fund the basic Phase I and Phase II option program. However, should additional funding become available, DARPA may elect to fund additional optional activities, and ROM options will assist in program planning. The proposal instructions under IV.B.3.a provide guidance regarding the option information that is desired in the proposal.

II. Award Information

Number of Awards

A single award is anticipated. The amount of resources made available under this BAA will depend on the quality of the proposals received and the availability of funds.

The Government reserves the right to select for negotiation all, some, one, or none of the proposals received in response to this solicitation, and to make awards without discussions with proposers. The Government also reserves the right to conduct discussions if it is later determined to be necessary. If warranted, portions of the resulting award may be segregated into pre-priced options. Additionally, DARPA reserves the right to accept proposals in their entirety or to select only portions of proposals for award. In the event that DARPA desires to award only portions of a proposal, negotiations may be opened with that proposer. The Government reserves the right to fund proposals in phases with options for continued work at the end of one or more of the phases.

Awards under this BAA will be made to proposers on the basis of the evaluation criteria listed below (see section labeled “Application Review Information,” Sec. V.), and program balance to provide overall value to the Government. The Government reserves the right to request any additional, necessary documentation once it makes the award instrument determination. Such additional information may include, but is not limited to, Representations and Certifications and additional cost substantiation data. The Government reserves the right to remove proposers from award consideration, should the parties fail to reach agreement on award terms, conditions or cost/price within a reasonable time or the proposer fails to provide requested additional information in a timely manner.

Proposals identified for negotiation may result in a procurement contract or other transaction, depending upon the nature of the work proposed, the required degree of interaction between parties, whether or not the research is classified as Fundamental Research, and other factors.

In all cases, the Government contracting officer shall have sole discretion to select award instrument type and to negotiate all instrument terms and conditions with selectees.

Proposers are advised that regardless of the instrument type proposed, DARPA personnel, in consultation with the Government contracting officer, may select other award instruments, as they deem appropriate. DARPA will apply publication or other restrictions, as necessary, if it determines that the research resulting from the proposed effort will present a high likelihood of disclosing performance characteristics of military systems or manufacturing technologies that are unique and critical to defense. Any award resulting from such a determination will include a requirement for DARPA permission before publishing any information or results on the program. For more information on publication restrictions, see the section below on Fundamental Research.

Fundamental Research

It is DoD policy that the publication of products of fundamental research will remain unrestricted to the maximum extent possible. National Security Decision Directive (NSDD) 189 established the national policy for controlling the flow of scientific, technical, and engineering information produced in federally funded fundamental research at colleges, universities, and laboratories. The Directive defines fundamental research as follows:

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

As of the date of publication of this BAA, the Government expects that program goals as described herein either cannot be met by proposers intending to perform fundamental research or the proposed research is anticipated to present a high likelihood of disclosing performance characteristics of military systems or manufacturing technologies that are unique and critical to defense. Therefore, the Government anticipates restrictions on the resultant research that will require the contractor to seek DARPA permission before publishing any information or results relative to the program.

Proposers should indicate in their proposal whether they believe the scope of the research included in their proposal is fundamental or not. While proposers should clearly explain the intended results of their research, the Government shall have sole discretion to select award instrument type and to negotiate all instrument terms and conditions with selectees. Appropriate clauses will be included in resultant awards for non-fundamental research to prescribe publication requirements and other restrictions, as appropriate.

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

The following statement or similar provision will be incorporated into any resultant non-fundamental research procurement contract or other transaction:

There shall be no dissemination or publication, except within and between the contractor and any subawardees, of information developed under this contract or contained in the reports to be furnished pursuant to this contract without prior written approval of DARPA’s Public Release Center (DARPA/PRC). All technical reports will be given proper review by appropriate authority to determine which Distribution Statement is to be applied prior to the initial distribution of these reports by the contractor. With regard to subawardee proposals for Fundamental

Research, papers resulting from unclassified fundamental research are exempt from prepublication controls and this review requirement, pursuant to DoD Instruction

5230.27 dated October 6, 1987.

When submitting material for written approval for open publication, the contractor/awardee must submit a request for public release to the DARPA/PRC and include the following information: (1) Document Information: document title, document author, short plain-language description of technology discussed in the material (approx. 30 words), number of pages (or minutes of video) and document type (e.g., briefing, report, abstract, article, or paper); (2) Event Information: event type (conference, principal investigator meeting, article or paper), event date, desired date for DARPA's approval; (3) DARPA Sponsor: DARPA Program Manager, DARPA office, and contract number; and (4) Contractor/Awardee's Information: POC name, email and phone. Allow four weeks for processing; due dates under four weeks require a justification. Unusual electronic file formats may require additional processing time. Requests may be sent either via email to public_release_center@darpa.mil or by mail at 675 North Randolph Street, Arlington VA 22203-2114, telephone (571) 218-4235. Refer to the following for link for information about DARPA’s public release process:

http://www.darpa.mil/work-with-us/contract-management/public-release.”

III. Eligibility Information

All responsible sources capable of satisfying the Government's needs may submit a proposal that shall be considered by DARPA.

A. Eligible Applicants

Federally Funded Research and Development Centers (FFRDCs) and Government entities (e.g., Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they meet the following conditions: (1) FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector; and (2) FFRDCs must provide a letter on official letterhead from their sponsoring organization citing the specific authority establishing their eligibility to propose to Government solicitations and compete with industry, and their compliance with the associated FFRDC sponsor agreement’s terms and conditions. This information is required for FFRDCs proposing to be prime contractors or subawardees. Government entities must clearly demonstrate that the work is not otherwise available from the private sector and provide written documentation citing the specific statutory authority and contractual authority, if relevant, establishing their ability to propose to Government solicitations. At the present time, DARPA does not consider 15 U.S.C. § 3710a to be sufficient legal authority to show eligibility. While 10 U.S.C.§ 2539b may be the appropriate statutory starting point for some entities, specific supporting regulatory guidance, together with evidence of agency approval, will still be required to fully establish eligibility. DARPA will consider FFRDC mailto:public_release_center@darpa.mil and Government entity eligibility submissions on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the proposer.

All proposers are expected to address transition (see proposal format under IV.B.3);

transition is part of the evaluation criteria in Section V.A. However, given their special status, FFRDCs should describe how and when a proposed technology/system will transition to which Non-FFRDC organization(s).

Non-U.S. organizations and/or individuals may participate to the extent that such participants comply with any necessary nondisclosure agreements, security regulations, export control laws, and other governing statutes applicable under the circumstances.

B. Procurement Integrity, Standards of Conduct, Ethical Considerations, and Organizational Conflicts of Interest

Current federal employees are prohibited from participating in particular matters involving conflicting financial, employment, and representational interests (18 U.S.C. §§ 203, 205, and 208). Once the proposals have been received, and prior to the start of proposal evaluations, the Government will assess potential conflicts of interest and will promptly notify the proposer if any appear to exist. The Government assessment does NOT affect, offset, or mitigate the proposer’s responsibility to give full notice and planned mitigation for all potential organizational conflicts, as discussed below.

Without prior approval or a waiver from the DARPA Director, in accordance with FAR 9.503, a contractor cannot simultaneously provide scientific, engineering, technical assistance (SETA) or similar support and also be a technical performer. As part of the proposal submission, all members of the proposed team (prime proposers, proposed subawardees, and consultants) must affirm whether they (their organizations and individual team members) are providing SETA or similar support to any DARPA technical office(s) through an active contract or subcontract. All affirmations must state which office(s) the proposer, subawardees, consultant, or individual supports and identify the prime contract number(s). All facts relevant to the existence or potential existence of organizational conflicts of interest (FAR 9.5) must be disclosed. The disclosure must include a description of the action the proposer has taken or proposes to take to avoid, neutralize, or mitigate such conflict. If in the sole opinion of the Government after full consideration of the circumstances, a proposal fails to fully disclose potential conflicts of interest and/or any identified conflict situation cannot be effectively mitigated, the proposal will be rejected without technical evaluation and withdrawn from further consideration for award.

If a prospective proposer believes a conflict of interest exists or may exist (whether organizational or otherwise) or has questions on what constitutes a conflict of interest, the proposer should send his/her contact information and a summary of the potential conflict via email to the BAA email address before time and effort are expended in preparing a proposal and mitigation plan.

C. Cost Sharing/Matching

Cost sharing is not required; however, it will be carefully considered where there is an applicable statutory condition relating to the selected funding instrument (e.g., for any Other Transactions under the authority of 10 U.S.C. §2371). Cost sharing is encouraged where there is a reasonable probability of a potential commercial application related to the proposed research and development effort.

IV. Application and Submission Information

A. Address to Request Application Package

This solicitation contains all information required to submit a proposal. No additional forms, kits, or other materials are needed. This notice constitutes the total solicitation. No additional information is available, except as provided at FBO.gov or Grants.gov, nor will a formal Request for Proposal (RFP) or additional solicitation regarding this announcement be issued. Requests for the same will be disregarded.

B. Content and Form of Application Submission

1. Proprietary and Security Information

DARPA policy is to treat all submissions as source selection information (see FAR 2.101 and 3.104), and to disclose their contents only for the purpose of evaluation.

Restrictive notices notwithstanding, during the evaluation process, submissions may be handled by support contractors for administrative purposes and/or to assist with technical evaluation. All DARPA support contractors performing this role are expressly prohibited from performing DARPA-sponsored technical research and are bound by appropriate nondisclosure agreements.

Submissions will not be returned. An electronic copy of each submission received will be retained at DARPA and all other non-required copies destroyed. A certification of destruction may be requested, provided the formal request is received at this office within 5 days after notification that a proposal was not selected.

a. Proprietary Information Proposers are responsible for clearly identifying proprietary information.

Submissions containing proprietary information must have the cover page and each page containing such information clearly marked with a label such as “Proprietary” or “Company Proprietary.” Note, “Confidential” is a classification marking used to control the dissemination of U.S. Government National Security Information as dictated in Executive Order 13526 and should not be used to identify proprietary business information.

b. Security Information

Classified submissions shall be transmitted in accordance with the following guidance. Additional information on the subjects discussed in this section may be found at http://www.dss.mil/.

If a submission contains Classified National Security Information as defined by Executive Order 13526, the information must be appropriately and conspicuously marked with the proposed classification level and declassification date. Similarly, when the classification of a submission is in question, the submission must be appropriately and conspicuously marked with the proposed classification level and declassification date.

Submissions requiring DARPA to make a final classification determination shall be marked as follows:

“CLASSIFICATION DETERMINATION PENDING. Protect as though classified____________________________ (insert the recommended classification level, e.g., Top Secret, Secret or Confidential)”

NOTE: Classified submissions must indicate the classification level of not only the submitted materials, but also the classification level of the anticipated award.

Proposers submitting classified information must have, or be able to obtain prior to contract award, cognizant security agency approved facilities, information systems, and appropriately cleared/eligible personnel to perform at the classification level proposed. All proposer personnel performing Information Assurance (IA)/Cybersecurity related duties on classified Information Systems shall meet the requirements set forth in DoD Manual 8570.01-M (Information Assurance Workforce Improvement Program).

Proposers choosing to submit classified information from other collateral classified sources (i.e., sources other than DARPA) must ensure (1) they have permission from an authorized individual at the cognizant Government agency (e.g., Contracting Officer, Program Manager); (2) the proposal is marked in accordance with the source Security Classification Guide (SCG) from which the material is derived; and (3) the source SCG is submitted along with the proposal.

The effort being solicited by this BAA is classified or otherwise involves access to, or generation of, classified information. Security classification guidance via a Security Classification Guide (SCG) and/or DD Form 254, “DoD Contract Security Classification Specification will be provided to eligible…