HR001120S0039.pdf

Broad Agency Announcement

Air Space Total Awareness for Rapid Tactical Execution

(ASTARTE)

STRATEGIC TECHNOLOGY OFFICE

HR001120S0039

April 7, 2020

TABLE OF CONTENTS

PART I: OVERVIEW INFORMATION

PART II: FULL TEXT OF ANNOUNCEMENT

I. Funding Opportunity Description

A. Program Overview

B. PROGRAM METRICS

II. Award Information A. General Award Information B. Fundamental Research

III. Eligibility Information A. Eligible Applicants B. Organizational Conflicts of Interest C. Cost Sharing/Matching D. Collaborative Efforts E. Other Eligibility Criteria

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 of Proposals

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

VII. Agency Contacts VIII. Other Information IX. APPENDIX 1: Proposal Slide Summary X. APPENDIX 2: Technical Interface Specifications XI. APPENDIX 3: VOLUME 1 Cover Sheet Template XII. APPENDIX 4: VOLUME 2 Cover Sheet, Checklist, and Sample Templates XIII. APPENDIX 5: ASTARTE Security Classification Guide

PART I: OVERVIEW INFORMATION

Federal Agency Name – Defense Advanced Research Projects Agency (DARPA), Strategic Technology Office (STO) Funding Opportunity Title – Air Space Total Awareness for Rapid Tactical Execution

(ASTARTE)

Announcement Type – Initial Announcement Funding Opportunity Number – HR001120S0039 Catalog of Federal Domestic Assistance Numbers (CFDA) – Not applicable Dates o Posting Date: April 7, 2020 o Proposers’ Day: April 21, 2020 o Abstract Due Date and Time: April 28, 2020, 4:00PM (Eastern) o Questions Due Date: May 14, 2020, 4:00PM (Eastern) o Deadline to Notify Security of Intent to Submit Classified Proposal: May 28, 2020, 4:00PM (Eastern) o Proposal Due Date and Time: June 23, 2020, 4:00PM (Eastern)

Anticipated individual awards – Multiple awards are anticipated.

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

Agency contact o Point of Contact The BAA Coordinator for this effort can be reached at:

electronic mail: HR001120S0039@darpa.mil mailto:HR001119SXXXX@darpa.mil

PART II: FULL TEXT OF ANNOUNCEMENT

I. Funding Opportunity Description

This publication constitutes a Broad Agency Announcement (BAA) as contemplated in Federal Acquisition Regulation (FAR) 6.102(d)(2) and 35.016 and 2 CFR § 200.203. Any resultant award negotiations will follow all pertinent law and regulation, and any negotiations and/or awards for procurement contracts will use procedures under FAR 15.4, Contract Pricing, as specified in the BAA.

The Defense Advanced Research Projects Agency (DARPA) Air Space Total Awareness for Rapid Tactical Execution (ASTARTE) program seeks to provide real-time, low-risk joint de-confliction between airspace users and joint fires at an Army Division-level to enable responsive support to tactical units and build a resilient air picture in an Anti-Access/Area Denial (A2/AD) environment while conducting Joint All-Domain Command and Control (JADC2) operations.

ASTARTE will develop a virtual and live testbed for airspace management systems, a series of algorithms for airspace planning and operations, and a sensor network for delivering real-time spatial and temporal tracking of airborne platforms. Together, these elements will perform all aspects of sensor tasking, data processing, multi-modal data fusion and near-real time dissemination to enable dynamic spatial and temporal airspace management and operations.

The ASTARTE program is soliciting innovative proposals that will focus on the following three technical areas: TA-1) Understanding and Decision Algorithms that are capable of identifying and predicting airspace usage conflicts, determining immediate restricted operating zones, proposing alternative airspace de-confliction solutions (courses of action) with assessed risk levels, and dynamically planning and tasking sensors in the ASTARTE network to achieve a complete airspace picture. TA-2) Sensors that can detect and track, in real-time, aircraft (manned and unmanned), airborne weapons, and other potential flight hazards such as unmanned balloons or other hazards to safety of flight in an A2/AD environment. TA-3) Virtual Lab Testbed development that allows for the modeling, simulation, and virtualization of current joint military airspace management systems, operations and ASTARTE technology, with interfaces to connect real-world hardware and software, leveraging a common software framework that supports both the virtual and real world environments.

Proposers must propose to all three technical areas in a single proposal. The proposals must satisfactorily address each technical area. Proposers are highly encouraged to submit an abstract in advance of a full proposal. Proposers submitting a full proposal may request the technical interface specifications, message set definitions, and supporting documentation for relevant military operational Command and Control (C2) systems using the request form in Appendix 2.

These controlled unclassified documents will not be available during the abstract period and will only be made available for full proposal submissions.

Proposed research should investigate innovative approaches that enable revolutionary advances in science, devices, or systems. Specifically excluded is research that primarily results in evolutionary improvements to the existing state of practice. Proposals must explicitly address how their approach will contribute to the DARPA mission, “To make pivotal investments in breakthrough technologies for national security”.

A. Program Overview

The goal of the ASTARTE Program is to provide real-time, low-risk de-confliction between airspace users and joint fires to enable support to tactical units and build a resilient air picture under an Anti-Access/Area Denial (A2/AD) bubble while conducting JADC2 operations.

ASTARTE consists of an artificial intelligence (AI) engine, running understanding and decision algorithms, combined with a networked layer of innovative, traditional and non-traditional sensors. ASTARTE will provide a more accurate, timely picture of the airspace, allowing simultaneous and dynamic long-range fire missions, manned and unmanned aircraft systems (UAS) to operate within the same airspace in a safe and efficient manner. It will interoperate and coordinate with existing C2 systems to ensure airspace users and operators have the most current and relevant information available. ASTARTE will not only provide a continuously updating, real-time four-dimensional (space and time) moving picture of the battlespace for blue forces, but will also use its sensor network to detect and map adversary airspace use, increasing situational awareness within A2/AD environments.

The current approach to airspace planning and control involves predominately manual and static procedures that allocate “lanes” and “zones” which prohibit adaptive re-tasking and reapportionment resulting in increased risk in order to accomplish the mission and missed mission opportunities. In addition, this approach is generally over-previsioned as the only way to provide any flexibility but at the cost of very inefficient use of available airspace. The case of airspace de-confliction between long-range fires and airspace users is emblematic of this larger airspace operations problem. Coordination between fires and airspace users is slow and inexact, often requiring de-confliction to be conducted manually via voice communications prior to the execution of a fires mission, greatly increasing the ability of an adversary to fire and maneuver unchallenged.

Airspace is divided into large three-dimensional blocks which do not support multiple uses and remain restricted for extended periods of time. Additionally, track correlation and airspace clearance is done manually, new weapons and systems cannot be integrated efficiently, not all aerial platforms are visible or tracked, and current airspace management systems have difficulty connecting with each other due to data connectivity and formatting limitations. With the expected increase in swarms of autonomous air vehicles and long-range munitions in the battlespace comes additional complexity, which current airspace management systems and processes will struggle to support. Moreover, conventional approaches to conducting JADC2 airspace operations in an A2/AD environment, can expose targets by the nature of readily detectable Radio Frequency (RF) emissions. Finally, current airspace management systems have an incomplete picture of adversary air and ground activity, an essential element required to fully understand the airspace.

Prior attempts to create a more dynamic, joint picture of the airspace (e.g. the Single Integrated Air Picture or SIAP joint program) relied upon an overly complex and burdensome centralized approach that attempted to force all operations, data, and C2 systems into a common framework and attempted to maintain an unattainable high-resolution, real-time update of all air tracks. In contrast, ASTARTE seeks to gather data, form a refined airspace picture, and re-plan by exception as needed to support dynamic JADC2 operations.

The ASTARTE Program will leverage advanced understanding and decision algorithms in combination with traditional airspace management techniques such as pre-filed flight plans, detailed routes from mission planning software, and self-reporting air platforms along with non-traditional means such as novel innovative RF and optical approaches to create a more complete airspace picture. The proliferation of radio transmitters, low-cost processing power, ubiquity of sensors on the battlefield, and advancements in machine learning will all contribute to ASTARTE’s success. A key aspect to ASTARTE’s approach will be the understanding that in order to determine where an entity is, we only need to determine where it is not. Most platforms and weapons only occupy airspace briefly, so the current practice of designating and restricting large blocks of airspace for extended periods in order to support one platform will be dramatically improved to a dynamic temporal system, allowing coexistence of multiple platforms and weapons in the same airspace. Courses of Action (COA) will be determined by assessing the risk (consequences and likelihood) associated with different options, allowing maximum temporal and spatial use of the airspace. Figure 1 is a graphical representation of the comparison of current airspace operations utilizing large air corridors and restricted operating zones to an envisioned future where ASTARTE will reduce the restricted airspace to small estimated probability bubbles around each aerial platform and weapon, providing accurate locations of all entities in the airspace. These probability bubbles will evolve in a digital world model allowing ASTARTE to experiment with different plans, anticipate conflicts, task sensors to refine locations, propose alternatives that include risk assessments, and provide a four-dimensional common operating picture (4D COP).

Figure 1. ASTARTE Future Airspace Operations

ASTARTE will focus on the most challenging airspace problem – the airspace above an Army Division under the A2/AD bubble. This block of airspace is approximately 100 km by 100 km and extends from the ground up to 18,000 feet, as shown in Figure 2. This volume of interest contains Army, Air Force, Navy, Marine Corps, Special Operations Forces, Coalition, and adversary manned and unmanned aircraft and munitions entering and transiting the airspace to conduct operations. It also contains forces conducting fire missions, and close air support. The airspace may also include commercial aircraft and other hazards. However, the system must be cognizant of adjacent air spaces and the airspace above the division airspace to include assets in space. Army Division-level airspace management is the first echelon that leverages joint and coalition planning tools. Interfaces to these tools will help ensure ASTARTE is designed from the ground up to support all joint and coalition airspace operations.

Figure 2. ASTARTE Volume of Interest

Figure 3 shows current existing military C2 Systems: Theatre Battle Management Core Systems (TBMCS), and other systems in the Army Battle Command Server (ABCS) such as Tactical Airspace Integration System (TAIS), Advanced Field Artillery Tactical Data System (AFATDS), Air and Missile Defense Workstation (AMDWS), Unmanned Aerial Systems (UAS) Ground Control Stations, Distributed Common Ground System – Army (DCGS-A). These systems use standard military message formats such as the Data Dissemination Service (DDS), Variable Message Format (VMF), United States Message Text Format (USMTF), and other data exchanges in order to share information between each other. ASTARTE algorithm solutions should be “headless” and designed with an application programming interface (API) that enables easy integration and interoperability with this full range of systems, so that operators can utilize ASTARTE capabilities within their native environments that they already own and are trained to.

Figure 3. Current Military Airspace Management and Operations Systems

Figure 4 shows a conceptual visualization of ASTARTE’s role in the planning and execution of airspace operations. The clouds in the figure represent both the C2 System Interfaces and Sensor Systems. The C2 System Interfaces will provide the Plans, Guidance, and Decisions via a number of current existing military systems such as TAIS, AFATDS, TBMCS, AMDWS, UAS Ground Control Stations, DCGS-A, and others. The ASTARTE Engine will reside in the Command Post Computing Environment (CPCE), which already hosts several of the C2 systems depicted in the figure. However, ASTARTE should be extensible to other computing platforms or cloud hosting. The Sensor Systems could include Electro-Optics, Infrared, Counter-Mortar Radar, Monostatic Radar, RF sensors, laser designators, weather radar and others. Like the C2 system interface layer, ASTARTE algorithm solutions should have sensor-facing APIs that enable easy integration and interoperability with this wide range of sensors and data sources.

Figure 4. Operational Execution of ASTARTE in Airspace Operations

ASTARTE Technical Areas

The ASTARTE Program will consist of three technical areas: Understanding and Decision Algorithms, Sensors, and Virtual Lab Testbed.

Technical Area 1 (TA-1) Understanding and Decision Algorithms: The goal of TA-1 is to develop understanding and decision algorithms leveraging advances in AI, data analytics, and reinforcement learning and cognitive human-machine interfaces. These algorithms will simulate multiple airspace user courses of action, identify conflicts, determine immediate restricted operating zones, and provide recommendations with assessed risk levels. TA-1 algorithms will assist airspace users in both the planning and execution phases of airspace operations by predictively and dynamically estimating airspace requirements using the state of airborne entities, confidence ellipses of these entities based on locational accuracy, and updated mission tasking.

In addition, TA-1 algorithms will develop and execute the sensor collection strategies to monitor airspace operations, taking resource availability, network load, and information requirements into consideration. These algorithms will refine and update entity positions and platform uncertainty confidence ellipses in the airspace and forecast future positions based on information provided by the sensor network or other data sources. Operators will be alerted to potential conflicts in airspace and fire plans and will be offered resolution with alternate courses of action incorporating risks and rationale. Potential approaches to the TA-1 algorithms could include approaches such as graph theory, reinforcement learning, global optimization with particle swarm optimization, and game theory to generate courses of action. Proposers are encouraged to partner with several technology teammates such as universities and accomplished AI experts who can contribute to the overall innovative algorithm solutions.

Proposals should provide a detailed approach that will:

a. Develop physics-guided algorithms to generate multiple COAs, identify and resolve conflicts, and assess risk levels;

b. Develop and execute sensor collection plans and strategies to monitor airspace operations, provide updates to plan;

c. Describe the ability to task sensors in real-time utilizing standard military message formats;

d. Refine airspace entity positions and forecast future positions;

e. Alert operators to conflicts during operations, offer resolution, and provide risks and rationale;

f. Create a 4D COP based on detections, locations, and tracks from the sensor network, other data sources, and predictions;

g. Support seamless transition from the virtual simulation to real-world operations by leveraging a common software framework based on the Army’s Command Post Computing Environment (CPCE); and,

h. Leverage best DevSecOps practices and software.

Technical Area 2 (TA-2) Sensors: The goal of TA-2 is to develop an innovative layered sensor network system that can detect and track aircraft, weapons, and ground entities in an A2/AD environment. The sensor network coverage approach is depicted in Figure 5. It consists of multiple areas of coverage in the airspace. A variety of traditional and non-traditional sensors can be leveraged to refine entity locations. Modeling and simulation of sensors will be conducted to determine performance, rules for sensor placement, latency, and accuracy. Sensor systems considered include but are not limited to: novel electro-optics/infrared, radar, laser designators, lightweight counter-fire radars, transponders, and communications systems.

Figure 5. ASTARTE Sensor Coverage

TA-2 will include the design and prototype development of each sensor component in the sensor network, which may consist of high-quality, low-cost commercial-off-the-shelf technology or existing sensors repurposed for the ASTARTE program. These sensors are expected to be a mixture of both relatively mature technologies in addition to innovative but less mature technologies. The sensor network proposed should include sufficient performance details of each contributing component in addition to sufficient performance details of the overall system.

Sensors to be considered may be stationary, mobile, or sensors of opportunity. Proposers are encouraged to partner with several technology teammates who can contribute innovative sensors of different and varying capabilities that will enable an effective system-of-systems sensor network solution. Proposals should include separately priced individual sensor technologies within the sensor network.

Proposals should provide a detailed approach that will:

a. Develop a system-of-systems sensor network framework and interoperability approach for complete airspace coverage under the A2/AD bubble;

b. Incorporate both novel uses of existing sensors and field additional sensors to complete the air picture;

c. Allow for scalability, flexibility, and reconfigurability of the system to integrate additional sensors of varying modalities to increase accuracy and robustness;

d. Provide detailed description of each sensor and sensor coverage that will provide information to refine entity locations;

e. Describe the ability to find and identify available sensors and their health status;

f. Describe the ability for sensors to receive tasking in real-time utilizing standard military message formats;

g. Describe the ability for the sensor network to respond to tasking with a location and accuracy estimate;

h. Create a resilient sensor network that can survive degradation in an A2/AD environment;

i. Support seamless transition from the virtual simulation to real-world operations by leveraging a common software framework based on the Army’s Command Post Computing Environment (CPCE);

j. Provide a plan for using existing tactical communications networks and sensor standards;

and,

k. Provide a unit cost for each sensor and rough order of magnitude (ROM) cost estimate of overall sensor network system required for complete Division level coverage.

Technical Area 3 (TA-3) Virtual Lab Testbed: The goal of TA-3 is to develop a virtual testbed environment incorporating a faster than real-time simulation of the airspace, models of sensors and virtual machine or actual implementations of existing C2 systems. Figure 6 represents the relationship between the virtual machine implementation, world model estimate, AI enabled conflict identification, and conflict probability space. ASTARTE will also interface with intelligence feeds, which will enable ASTARTE to understand and affect the Joint mission.

The testbed will take full advantage of open architecture and best DevSecOps practices and software. It will allow the exploration of fully virtual implementations of airspace operations algorithms and sensor models of interest. The environment will support seamless transition from the virtual simulation to real-world operations by leveraging a common software framework based on the Army’s Command Post Computing Environment (CPCE). The overall system performance will be assessed through modeling and simulation (M&S) as well as live experimentation and demonstration.

Proposals should provide a detailed approach that will:

a. Create the software for a virtual lab testbed that provides APIS to support interoperability to legacy airspace operations systems and the TA-2 sensor network through standard military message formats;

b. Leverage existing airspace operations systems for input and output using standard military message formats;

c. Identify and implement a world model of the airspace that can feed and acquire data from the legacy airspace operations systems;

d. Use an open software architecture framework to allow rapid insertion and experimentation with algorithms and sensors;

e. Document the interface specifications to TA-1 and TA-2 and perform the integration of TA-1 algorithms and TA-2 sensor network into the virtual lab testbed;

f. Identify and explain how to incorporate legacy intel and other data feeds into the virtual lab testbed; and,

g. Work with Army and Air Force representatives to deploy the virtual lab test bed software at one Air Force and one Army site.

Figure 6. Representation of ASTARTE System Components and Functions

Cross-Technical Area Interactions

Each ASTARTE TA is separate with independent goals and will be assessed independently.

However, ASTARTE performers must take a holistic system view and appreciate how decisions in one technical area affect the other.

Figure 7 shows a notional representation of the connections and interdependencies between ASTARTE system technologies.

Figure 8 illustrates an example of cross-TA data and notional information exchanges for

ASTARTE.

It is envisioned that the ASTARTE engine and sensor network will operate at the SECRET level when algorithms based on real operational scenarios, real intelligence or C2 data, real threat systems, or real blue force platforms and weapons are used to develop, train, experiment with, or test the system. ASTARTE performers must have an appropriate capability to handle and generate classified information at the SECRET level. However, this requirement does not apply to organizations such as universities that may participate as a subcontractor.

Figure 7. Notional Representation of ASTARTE System Components and Relationships

Figure 8. Example of Cross-Technical Area Information Exchanges

1. Program Structure

The ASTARTE program has three (3) phases for a total of 46 months, as shown in Figure 9. The three phases are as follows:

Phase 1 Base Period: Component Development, 14 months Phase 2 (Option 1): Virtual Environment Integration, 14 months Phase 3 (Option 2): Live Environment Integration, 18 months

Proposers must propose a solution that addresses all technical areas, TA-1, TA-2, and TA-3 in a single proposal. It is strongly encouraged that proposers team with organizations that have specialized expertise in each technical area. Each proposal submission should include Phase 1 (Base) and separately priced options for Phase 2 and Phase 3. Submissions that do not include all TAs and separately priced options for Phase 2 and Phase 3 will not be considered. It is anticipated that there will be multiple performers for ASTARTE Phase 1. Decisions for Phase 2 and Phase 3 Option exercise will be based on previous Phase performance and funding availability. The number of awards planned are subject to change at the Government’s discretion.

Figure 9. ASTARTE Program Schedule

Phase 1, Base Period, 14 Months

Phase 1, the TA-1 task is to develop the algorithms and conduct unit tests of algorithms to verify performance. The algorithms will simulate multiple airspace user courses of action, identify conflicts, determine current and projected airspace usage requirements and associated confidence levels, and propose alternative solutions with assessed risk levels. The algorithms will also develop a sensor collection strategy to monitor airspace operations against the plan and assign tasking for multiple sensor sources in the network. It is envisioned that algorithms developed will seamlessly transition from the virtual environment to the live environment and run faster than real time in virtual environment. Performers will also develop methods and interfaces which enable the algorithms to run in the TA-3 virtual lab testbed. Performers will ensure that TA-1 technologies can retrieve data from and deliver data to airspace management and operations systems. At the end of Phase 1, performers will deliver their algorithms to the government.

In Phase 1, the TA-2 task is to design a sensor network architecture to meet ASTARTE specifications, develop sensor models for the virtual environment, procure sensor prototypes, ensure sensors interface with standard military message formats, and conduct unit tests of the sensors to verify performance. At the end of Phase 1, performers will deliver the sensor network architecture specifications, models, and software for the models to the government.

In Phase 1, the TA-3 task is to develop the virtual lab testbed architecture, specifications for how TA-1 and TA-2 will integrate into that architecture, and will work with the government to define interfaces for virtual machine implementations of existing airspace systems. TA-3 will develop the virtual lab testbed in accordance with the Army’s CPCE, leveraging government-furnished hardware and virtual machine implementation of existing airspace management systems. TA-3 will work with the government to ensure that TA-1 and TA-2 technologies can be integrated into the virtual lab testbed. At the end of Phase 1, performers will demonstrate a virtual world model integrated with existing airspace management and operations systems.

Phase 2, Option 1 Period, 14 Months

In Phase 2, the TA-1 task is to support the integration of the understanding and decision algorithms into the virtual lab testbed, and support performance assessment against the metrics.

The algorithms will be refined based on integration and performance assessment and continually improved as necessary.

In Phase 2, the TA-2 task is to support the integration of the sensor models into the virtual lab testbed and performance assessments will be made against the metrics. Sensor models and assessments will be refined and continually improved as necessary.

In Phase 2, the TA-3 task is to integrate the understanding and decision algorithms and sensor models into the virtual lab testbed and performance will be assessed against the metrics developed in Phase 1. The real-world model will operate faster than real-time in the operational environment. Iterative refinements will be made and performance assessments repeated as necessary.

Phase 3, Option 2 Period, 18 Months

In Phase 3, the TA-1 and TA-2 tasks will support mission planning and operations with live TAIS, AFATDS, TBMCS, sensors, and other systems involved in airspace management and operations in live environments.

In Phase 3, the TA-3 task is to transform the virtual capability to a live capability by integrating TA-2 sensors and connecting live versions of TAIS, AFATDS, TBMCS and other data feeds and systems involved in airspace management and operations. The real-world model will operate faster than real-time in the operational environment. Experimentation at the National Training Center (NTC) or other Government facilities will include live joint brigade operations and division command post exercises to demonstrate scenarios.

The joint brigade operations will be approximately 3 weeks in duration and represent a realistic combat environment with simulated and live fires and close air support missions. Division level command post exercises will be one week in duration at an Army division level headquarters installation with simulated fires and close air support missions. It is anticipated that performers will deploy sensor networks and algorithms in support of these events to fully engage with airspace operations and demonstrate ASTARTE capabilities.

Deliverables

ASTARTE Phase 1 Base deliverables are shown in Table 1.

Item Due Date (Months after Contract Award) Monthly Technical and Financial Status Reports Monthly Presentation materials for Phase 1 Kickoff and all Program Reviews

1 week in advance (Draft) 48 hours in advance (Final)

Phase 1 Integrated Master Schedule and Technical Tasking Plan Month 1

Program Protection Plan Month 2 Preliminary Design Documentation and Software Month 7 Final Design Documentation and Software

Show how approach from Preliminary Design Documentation has matured, status of current development, and technical plan for Phase 2

Month 11

Virtual Lab Testbed Software Delivery Month 13 Phase 1 Final Report

Final report summary of program, accomplishments, metrics compliance, and technical documentation of Phase 1

Month 14

Table 1. Phase 1 Base Deliverables

Phase 1 Programmatic deliverables (monthly technical and financial status reports, presentation materials, integrated master schedule and technical tasking plan, and program protection plan) will follow guidelines provided by the Government at kickoff. Technical deliverables should address the following:

Phase 1 Preliminary Design Documentation and Software

a. TA-1

a. Explanation of software development process utilizing DevSecOps

b. Documentation and software implementation of

i. Algorithms for generation of multiple COAs and deconfliction

ii. Algorithms for generation of airspace entity positions

iii. Sensor collection plan, including tasking of sensors in real-time using standard military message formats

iv. Method of detections, locations and tracking onto 4D COP

v. Common software framework to support interfaces with operational C2 systems and common military message formats

b. TA-2

a. Documentation and software implementation of

i. Sensor network architecture of airspace coverage and interface standards to include communications plan leveraging existing tactical networks

ii. Utilization of existing sensors and additional sensors, addressing scalability and flexibility

iii. Analyses of each sensor in sensor network, sensor performance, health, status, and location

iv. Resiliency and survivability of sensor network in an A2/AD environment

v. Common software framework and sensor standards that support interfaces with operational C2 systems and common military message formats

vi. Use of existing tactical communications networks and sensor standards

b. Updated documentation to support unit cost estimate for each sensor and overall sensor network based on initial findings and estimates from proposal

c. TA-3

a. Documentation and software implementation of

i. Virtual Lab Testbed architecture design using an open software architecture framework

ii. Interfaces to legacy airspace operations systems, TA-2 sensor network, and other data feeds, through standard military message formats

b. Documentation of initial interface specifications to the virtual lab testbed enabling efficient integration of TA-1 algorithms and TA-2 sensor network

Phase 1 Final Design Documentation and Software

a. Deliver final documentation and software implementation of understanding and decision algorithms, sensor network models, and virtual lab testbed to Government

b. Final designs for interfaces to algorithms and sensor network with virtual lab testbed

Phase 1 Virtual Lab Testbed Software Delivery

a. Deliver and install Virtual Lab Testbed software at Army and Air Force locations

b. Deliver Virtual Lab Testbed software, source code, and instructions to

Government

ASTARTE Phase 2 Option 1 deliverables are shown in Table 2.

Item Due Date (Months after Option Exercise) Monthly Technical and Financial Status Reports Monthly Presentation materials for Phase 2 Kickoff and all Program Reviews

1 week in advance (Draft) 48 hours in advance (Final)

Updates to Integration Plan Month 5 Updates to Phase 1 Final Design Documentation and Software Month 7

Virtual Demonstration Plan Month 9 Virtual Demonstration Security Plan Month 9 Virtual Demonstration Performance Assessment Report, Software, Prototype Hardware Month 14

Phase 2 Final Report Final report summary of program, accomplishments, metrics compliance, and technical documentation of Phase 2

Month 14

Table 2. Phase 2 Option 1 Deliverables

Phase 2 Programmatic deliverables (monthly technical and financial status reports and presentation materials) will follow guidelines provided by the government at kick-off. Technical deliverables should address the following:

Phase 2 Updates to Integration Plan

a. Detailed documentation of updates to final interface specifications for TA-1 and

TA-2 technologies developed in Phase 1 and plan for continuous improvement to integration with the virtual lab testbed

b. Tactical communications plan leveraging existing tactical radios

Phase 2 Updates to Phase 1 Final Design Documentation and Software

a. Detailed updates to documentation and software implementation of understanding and decision algorithms, sensor network, and virtual lab testbed to the Government showing how approach has matured and status of current development

Phase 2 Virtual Demonstration Plan

a. Detailed documentation describing scope, approach, and execution strategy for virtual integration demonstration of algorithms, sensor network, and virtual lab testbed

Phase 2 Virtual Demonstration Security Plan

a. Detailed documentation describing security plan for algorithms, sensor network, and virtual lab testbed

Phase 2 Virtual Demonstration Performance Assessment Report, Software, Prototype Hardware

a. Detailed documentation and experimentation results of Army-Air Force Demo for algorithms, sensor network, and virtual lab testbed

b. Deliver final documentation and software of algorithms, sensors, and virtual lab testbed to the Government

c. Deliver final prototype of sensors to Government

ASTARTE Phase 3 Option 2 deliverables are shown in Table 3.

Item Due Date (Months after Option Exercise) Monthly Technical and Financial Status Reports Monthly Presentation materials for Phase 3 Kickoff and all Program Reviews

1 week in advance (Draft) 48 hours in advance (Final)

Updated Integration Plan Month 5 Updates to Final Design Documentation and Software Month 7 Live Demonstration Plan Month 7 Live Demonstration Security Test Plan Month 7 Live Demonstration Performance Assessment Report Month 9 Final Live Demonstration Plan Month 15 Live Demonstration Performance Assessment Report, Final Software, and Final Prototype Hardware Month 17

Phase 3 Final Report Final report summary of program, accomplishments, metrics compliance, and technical documentation of Phase 3

Month 18

Table 3. Phase 3 Option 2 Deliverables

Phase 3 Programmatic deliverables (monthly technical and financial status reports and presentation materials) will follow guidelines provided by the Government at kickoff. Technical deliverables should address the following:

Phase 3 Updates to Integration Plan

a. Detailed documentation of updates to final interface specifications for TA-1 and

TA-2 technologies developed in Phase 2 and plan for continuous improvement to integration with the virtual lab testbed

Phase 3 Updates to Phase 2 Final Design Documentation and Software

a. Detailed updates to documentation and software implementation of understanding and decision algorithms, sensor network, and virtual lab testbed to the Government showing how approach has matured and status of current development

Phase 3 Live Demonstration Plan

a. Detailed documentation describing scope, approach, and execution strategy for live integration demonstration of algorithms, sensor network using live sensor feeds, and virtual lab testbed using live operational systems and live sensor feeds

Phase 3 Live Demonstration Security Test Plan

a. Detailed documentation for security plan of algorithms, sensor network using live sensor feeds, and virtual lab testbed using live operational systems and live sensor feeds

Phase 3 Live Demonstration Performance Assessment Report

a. Detailed documentation and experimentation results of live Army-Air Force

Demo for algorithms, sensor network, and virtual lab testbed

Phase 3 Final Live Demonstration Plan

a. Detailed documentation describing scope, approach, and execution strategy for final live integration demonstration of algorithms, sensor network using live sensor feeds, and virtual lab testbed using live operational systems and live sensor feeds

Phase 3 Final Live Demonstration Performance Assessment Report, Final Software, and Final Prototype Hardware

a. Detailed documentation and experimentation results of final live Army-Air Force Demo for algorithms, sensor network, and virtual lab testbed

b. Deliver final documentation and final software delivery of algorithms and sensors, final prototype delivery of sensors, and final documentation and software delivery of virtual lab testbed to Government in appropriate form factor

B. PROGRAM METRICS

In order for the Government to evaluate the effectiveness of a proposed solution in achieving the stated program objectives, proposers should note that the Government hereby promulgates the following program metrics that may serve as the basis for determining whether satisfactory progress is being made to warrant continued funding of the program. Although the following program metrics are specified, proposers should note that the government has identified these goals with the intention of bounding the scope of effort, while affording the maximum flexibility, creativity, and innovation in proposing solutions to the stated problem.

ASTARTE system-level metrics have been designed to objectively measure the performance of each of the TAs with increasing fidelity and levels of difficulty in each Phase and facet of the program. These metrics span all aspects of airspace planning and operations. While ASTARTE is heavily focused on operations, the system plays a role in the planning in order to ensure that the plans are optimized for execution. Tables 4, 5, and 6 provide metrics germane to specific TAs and ASTARTE system components. The ASTARTE Program will be evaluated continuously throughout its development.

Phase 1 will utilize analysis and M&S at the component level to extrapolate to system level performance in order to ensure that algorithms and sensors will ultimately meet system level requirements. The performance evaluations in Phase 2 will evaluate integrated system performance against the system metrics leveraging a combination of faster than real-time simulations and human-in-the-loop experimentation with a small staff in a simulated environment. Human-in-the-loop evaluators will assess quality of courses of action proposed by ASTARTE, as well as provide opportunities to measure improvements in decision times. In Phase 3 the metrics will be evaluated in larger and more complex live warfighter exercises where the number and frequency of the conflicts will increase significantly.

Operational performance parameters for de-confliction times, accuracy, risk projections and establishing a 4D COP will be evaluated. The first live evaluation will be with individual aircraft, followed by multiple manned and unmanned aircraft with simulated and live artillery, both on controlled ranges. The final evaluation will be done at a Combat Training Center (CTC), with live units, where the duration of the battle is days and the number and complexity of the missions has increased significantly.

TA-1 Performance Metrics

Phase 1 Base Component Development

Phase 2 Option 1 Virtual Environment

Phase 3 Option 2 Live Environment

Metric (Threshold/Objective) (Threshold/Objective) (Threshold/Objective)

Improvement in Operational Efficiency;

Planning time and re-plan time

Decrease by a factor of 2 /

Decrease by a factor of 4 /

Decrease by a factor of 6 /

Probability of Loss of Separation* in Either Vertical or Horizontal Plane, per Mission**

(live or simulated) without Operator

Notification

0.1 / 0.01 0.01 / 0.001 0.001 / 0.0001

COA Generation Performance (Average Time to Generate One

Plan)

120s / 90s 90s / 60s 30s / 10s

COA Performance (Percentage of COAs that are deemed operationally acceptable by government team Subject Matter Experts)

75% Acceptable 20% Require Operator

Decision 5% System Cannot

Resolve

85% Acceptable 10% Require Operator

Decision 5% System Cannot

Resolve

95% Acceptable 5% Require Operator

Decision 0% System Cannot

Resolve

Conflicts Presented to Operators during

Planning (Percentage of planned missions that result in a conflict;

conflicts occur when

10% / 5% 5% / 2.5% 0% separation loss* is likely to occur)

Volume of Entities Tracked (air and ground) 100 / 500 1,000 / 5,000 10,000 / 15,000

Entities Tracked (percentage of total entities in Division

Airspace)

All: 60 / 70 Blue: 65 / 75

All: 75 / 85 Blue: 80 / 90

All: 95 / 100 Blue: 95 / 100

Volume of Missions Processed per Hour 250 / 500 1,000 / 1,500 2,600 / 3,600

Number of Simultaneous Missions 15 / 30 30 / 45 60 / 75

Reliability (based on degradation-free federated capability;

probability of completing an 120-hour mission free from mission-degrading failure)

37% (component) 75% (system)

42% (component) 85% (system)

48% (component) 95% (system)

Accuracy of Projection to 4D COP

Manned Rotary Wing: <100m Manned Fixed Wing: <500m

Unmanned: <250m

(Projected 1σ aircraft distance from true aircraft location, metrics remain constant but are demonstrated via unit test in Phase 1, simulation in Phase 2, and live demonstration in Phase 3) Table 4. TA-1 Performance Metrics

*A loss of separation occurs between two aircraft whenever specified separation minima in controlled airspace are breached. Separation minima will be an operator-defined value.

**A mission consists of one blue entity in the airspace performing one task, such as one sortie conducting an airstrike.

TA-2 Performance Metrics Phase 1 Base Component

Development

Phase 2 Option 1 Virtual

Environment

Phase 3 Option 2 Live

Environment

Metric (Threshold/Objective) (Threshold/Objective) (Threshold/Objective)

Sensor Network Coverage:

Probability of detecting an

Entity* in Division Airspace, using more than one sensor

(live or simulated)

0.50 / 0.60 0.75 / 0.85 0.95 / 1.00

Number of Entities Tracked by Sensor Network 100 / 500 1,000 / 5,000 10,000 / 15,000

Entities Tracked (percentage of total entities in Division

Airspace)

All: 60 / 70 Blue: 65 / 75

All: 75 / 85 Blue: 80 / 90

All: 95 / 100 Blue: 95 / 100

Ability of Sensor Network to Maintain Track of a Group 1 UAS in Division Airspace, Represented as Percentage of Target Flight Time

0.50 / 0.60 0.65 / 0.75 0.85 / 0.95

Sensor Network Bearing Accuracy against a Group 1

UAS Target Track or Similarly Sized Aircraft

±0.30°/ ±0.25° ±0.20°/ ±0.15° ±0.10°/ ±0.05°

Sensor Network Range Accuracy against a Group 1

UAS Target Track or Similarly Sized Aircraft

60m / 45m 40m / 20m 15m / 5m

Sensor Network Altitude Detection 4000ft / 2000ft 2000ft / 1000ft 1000ft/ 500ft

Responsiveness to New Tasking (in Seconds) 30 / 20 20 / 10 5 / 2

Reliability (based on not degraded federated capability;

probability of completing an 120-hour mission free from mission-degrading failure)

37% (component) 75% (system)

42% (component) 85% (system)

48% (component) 95% (system)

Table 5. TA-2 Performance Metrics

*Entities will have signatures ranging from that of a Group 1 UAS up to a commercial aircraft.

A Group 1 UAS is defined as a vehicle weighing up to 20 pounds and with a maximum speed of <100 knots.

TA-3 Performance Metrics

Phase 1 Base Component

Development

Phase 2 Option 1 Virtual

Environment

Phase 3 Option 2 Live

Environment

Metric (Threshold/Objective) (Threshold/Objective) (Threshold/Objective)

Number of Entities that can be Simulated in the

Virtual Testbed 100 / 500 1,000 / 5,000 10,000 / 15,000

Ability of Virtual Lab Testbed to Run Faster-than-Real-Time Simulations

50x / 100x 200x / 500x 750x / 1,000x

Ability to Interface to Airspace Operations

Systems (percentage of errors in transmitting messages to and from airspace operations systems per hour)

10% / 5% 4% / 2% 2% / 0%

Volume of Missions Processed per Hour in

Virtual Testbed 250 / 500 1,000 / 1,500 2,600 / 3,600

Number of Simultaneous Missions in Virtual

Testbeds 15 / 30 30 / 45 60 / 75

Open Architecture/Ease of Integration; Days to

Integrate Sensor or Algorithm

Sensor / Algorithm:

<30 days Data feed:

<3 days

Sensor / Algorithm:

<15 days Data feed:

<2 days

Sensor / Algorithm:

<5 days

Data feed:

<1 days

Reliability (based on not degraded federated capability; probability of completing an 120-hour mission free from mission-degrading failure)

37% (component) 75% (system)

42% (component) 85% (system)

48% (component) 95% (system)

Table 6. TA-3 Performance Metrics

Government Furnished Equipment/Information (GFE/GFI)

The Government furnished equipment/information (GFE/GFI) is summarized below in Table 7.

Item Due Date for Government Delivery Detailed interface specifications for relevant Command and Control systems and data feeds

Phase 1 Kickoff

Scenarios, blue force structure, test asset information, and other relevant information for live testing

Phase 3 Kickoff

Table 7. GFE/GFI Items

II. Award Information

A. General Award Information

Multiple awards are 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 resulting awards 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, as applicable.

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 (see Section VI.B.4., “Representations and Certifications”). The Government reserves the right to remove proposers from award consideration should the parties fail to reach agreement on award terms, conditions, and/or cost/price within a reasonable time, and the proposer fails to timely provide requested additional information. 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.

Proposers looking for innovative, commercial-like contractual arrangements are encouraged to consider requesting Other Transactions. To understand the flexibility and options associated with Other Transactions, consult http://www.darpa.mil/work-with-us/contract-management#OtherTransactions.

In accordance with 10 U.S.C. § 2371b(f), the Government may award a follow-on production contract or Other Transaction (OT) for any OT awarded under this BAA if: (1) that participant in the OT, or a recognized successor in interest to the OT, successfully completed the entire prototype project provided for in the OT, as modified; and (2) the OT provides for the award of a follow-on production contract or OT to the participant, or a recognized successor in interest to the OT.

In all cases, the Government contracting officer shall have sole discretion to select award instrument type, regardless of instrument type proposed, and to negotiate all instrument terms and conditions with selectees. 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.

B. Fundamental Research

It is DoD policy that the publication of products of fundamental research will remain unrestricted to the maximum extent possible. National Security Decision Directive (NSDD) 189 defines fundamental research as follows:

‘Fundamental research’ means basic and applied research in science and engineering, the results of which ordinarily are published and shared broadly within…