Adversary Aircraft – Uncrewed

Quality

Attribute

             Rationale

AV.1 Physical Characteristics

a. Altitude – Typical fighter operating altitudes

Adversary platforms have the capability to operate at altitudes up to the commonly accepted upper physiological limit of fighter operations.

b. Airspeed – At least “high subsonic”

The ADAIR-UX platform must be able to train CAF aircrew on threat-relevant timelines for intercept pacing and decisions. 

c. Size

Similar to, but can be slightly smaller than, typical crewed air threats.  ADAIR-UX must be able to present a reasonably-sized platform for visual identification at a merge.

d. Size Weight Power and Cooling (SWaP-C)

SWaP-C must be sufficient to support threat-representative payloads and capabilities in terms of sensors, self-protection, and computing power.

e. Aircraft Signature

Threat-representative and augmentable.

f. Takeoff and Landing

Vehicles will perform conventional takeoffs and landings with weather limits commensurate with those of crewed Air Force fighter aircraft.

Quality

Attribute

             Rationale

SP.1 Threat Representative

a. Active sensors

Threat-representative active sensors OR the ability to credibly replicate the effects of those sensors based on position data. 

b. Passive sensors

Threat-representative passive sensors OR the ability to credibly replicate the effects of those sensors based on position data. 

c. Self-Protection

Threat-representative self-protection systems, with an emphasis on those systems used for electronic self-protection.

    Quality

Attribute

             Rationale

DC.1 Datalinks and Information Sharing

a. Command and Control

Ability to maintain secure/encrypted linkage between operators and vehicles throughout range of in-flight operations.  Operators will be providing general direction for vehicle activity, NOT “flying the aircraft.” 

b. Situational Awareness

Radios with the ability to provide share data through encrypted waveforms already propagated across the Combat Air Forces.

c. Inter-flight

Ability for UX vehicles to communicate via encrypted channels between each other to share data for both safety of flight and credible tactical execution.

DC.2 Adaptable Threat Replication

a. Fused Common Tactical Picture

Ability to fuse various data sources to form a common tactical picture (CTP) sufficient for 1) deconfliction and 2) tactical in-flight execution.

b. Assisted Capability

Ability to credibly employ simulated ordnance, with the ability to cause blue systems to react in a manner commensurate to the targeting method.

c. Programmable Capability

Ability to adjust vehicle, sensor, and emitter characteristics to approach those of a variety of threat aircraft.

 DC.3 Open Architecture and Interfaces

a. High Performance Computing

Ability to host onboard automation software, threat and shot replication, and other traditional flight functions with the speed and processing capacity necessary for mission success.

b. Aircraft Bus Architecture

Integration between components of the ADAIR-UX capability will allow for “plug and play” functionality via accepted physical and logical standards for both hardware (such as radios and sensors) and software (such as automation & operational flight programs).

c.  Data Recording

All recorded data (mission and systems performance) will be captured in an open-source, non-proprietary format and available to the government.  Specific parts of the mission data will be readily available for aircrew debrief and formatted to optimize lessons learned.

    Quality

Attribute

Rationale

HM.1 Human Oversight

a. Operator to Vehicle Ratio

Vehicle operations will be automated to the extent where one trained operator can safety and credibly oversee the administrative and tactical operation of multiple ADAIR-UX vehicles throughout all phases of ground operations & flight.

b. Graphical User Interface

Operators will be able to visualize and control administrative and tactical vehicle operations using a laptop-style interface with intuitive features such as click and drag pairing and phase-of-flight-informed drop-down menus.

c. Maintenance Interface

Maintainers will be able to initiate and oversee an automated preflight and start sequence.  Maintainers and operators will be able to hand off control of the vehicles with a positive, intuitive, and secure methodology.

HM.2 Onboard Automation

a. Mission Planning

Operators will use intuitive mission planning interfaces, which will enable predictable yet flexible administrative and tactical operations and will use fielded USAF mission planning tools.

b. Terminal Operations

Vehicles will be able to taxi, takeoff, land, rejoin, and administratively transit within DoD owned airspace via single commands from the operator.

c. Emergency Procedures

Vehicles will have pre-planned actions to undertake in case of critical emergency procedures, to include an awareness of takeoff and landing data (TOLD).  In the case of non-critical emergencies, operators will require intuitive interfaces with the affected vehicle while still administratively monitoring the unaffected vehicles. 

d. Tactical Execution

Vehicles will assist the operator with both in-flight navigation and sensor/emission management to credibly and safely replicate the capabilities and tactics of threat aircraft.