A Appendix
1.1 A.1 Glossary
Terminology Used in this Article
AAM = Advanced Air Mobility. Refers to innovative and disruptive airborne technology to transport people and goods to areas beyond the reach of traditional air transport, including complex and rural urban environments [1].
Air Taxi = aircraft with or without pilot on board that carries passengers [2].
CIS = The Common Information Service distributes data to support the provision of U-space services [2].
CORUS-XUAM = European U-space concept of operations developed as part of a European Horizon 2020 funded project [2].
Drone = aircraft without an on-board pilot, also known as UAS [2].
Emergency Responders = organisations that handle emergency operations, including fire brigades, medical services, and Search and Rescue teams [2].
Geo-fence zone = a defined airspace volume with operational requirements or constraints that can restrict access to aircraft. If no operations are allowed, it is referred to as a no-fly zone.
UAM = Urban Air Mobility. Refers to aircraft-based means of transportation near or within cities [2].
UAM Operations = air operations above urban areas, in U-space airspace, carried out by a mix of aircraft with limited range and unable to fly visual or instrument flight rules, which require tactical separation [2].
UAS = Uncrewed/Unmanned Aerial System. Aircraft that can carry passengers but is usually piloted remotely or autonomously [2].
UTM = UAS Traffic Management. An ecosystem for traffic management of UAS operations [2].
U-space airspace = the airspace that contains the UAS and UAM operations [2].
U-space services = European system to manage UAS and UAM operations [2].
U-plan = flight plan in U-space airspace [2].
UAM Control Centre (UCC) = the office of the UAM Coordinator and the DUC.
Vertiport = similar to conventional airports, these are dedicated ground-based facilities that support the take-off and landing of aircraft, including UAS and piloted aircraft such as VTOL and helicopters.
VTOL = Aircraft capable of Vertical Take-OFF and Landing [2].
Roles Referred to in this Article
DUC = Digital Assistant for the UAM Coordinator. A conceptual AI-based intelligent assistant that collaborates with the UAM Coordinator to manage the U-space and provide U-space services.
UAM Coordinator = human actor responsible for the tactical management of the U-space and the provision of U-space services.
UAM Operator = legal entity that operates and is responsible for one or more UAM flights that carry passengers or goods [2].
UAS Operator = legal entity that operates and is responsible for one or more UAS flights [2].
U-space Service Provider (USSP) = stakeholder providing U-space services [2].
Vertiport Operator = entity that manages and provides vertiport services, including accommodating incoming aircraft [2].
1.2 A.2 DUC HAT Requirements
Situation Awareness
-
DUC should be able to continuously monitor the U-space and traffic operations, providing real-time updates and alerts to the UAM Coordinator.
-
DUC should be able to monitor the U-space by collecting real-time data from multiple sources, including data from aircraft and weather.
-
DUC should be able to process the incoming data to identify trends and detect anomalies.
-
DUC should be able to generate status reports on U-space operations, incidents, and performance metrics.
-
DUC should be able to detect potential conflicts between UAS/UAM vehicles, such as near-collisions or airspace violations.
-
DUC should be able to perform simulations and scenario planning to anticipate future traffic patterns and potential U-space capacity issues.
-
DUC should be able to retrieve and present information on the request of the UAM Coordinator.
-
DUC should be able to infer what information the UAM Coordinator needs and present it.
-
DUC should be able to call for/direct the UAM Coordinator’s attention to important information (e.g., attention guidance).
Transparency
-
DUC should be able to provide explanations on request.
-
DUC should be able to correctly determine and understand what the UAM Coordinator is trying to understand, for which an explanation is needed.
-
DUC should be able to demonstrate the relevance of an explanation for a decision/action.
-
DUC should be able to determine an appropriate level of abstraction of an explanation according to the task, situation, trust, and expertise of the UAM Coordinator.
-
DUC should be able to explain how it derived an output.
-
DUC should be able to explain how it works.
Bidirectional Communication
-
DUC should be able to provide indication of having acknowledged the UAM Coordinators’ instructions/intentions.
-
DUC should be able to understand and generate human natural language.
-
DUC should be able to communicate using different modalities, including voice, text, and graphics (e.g., highlight areas on the map).
-
DUC should be able to not interfere when the UAM Coordinator is involved in other communications or actions.
-
DUC should be able to automatically adapt the modality of interactions to end-user states, preferences, and situations
Decision Making
-
DUC should be able to recommend actions/solutions.
-
DUC should be able to decide and implement actions within its performance envelope.
-
The DUC should allow the UAM Coordinator to adjust some of the authority limits and constraints in decision making and action implementation.
-
DUC should be able to identify poor and suboptimal strategies/actions/solutions proposed by the UAM Coordinator.
-
DUC should be able to propose and justify optimised solutions, where applicable.
-
DUC should be able to propose alternative strategies/actions/solutions.
-
DUC should be able to solve problems with the UAM Coordinator following a checklist.