Industry standards in support
of ATM/UTM/C-UAS integration
TIM on UAS and UAM – 13 Nov 2020
13rd November 2020 1
Jorge Munir El Malek Vázquez
Chairman EUROCAE WG-115
Alain Vallée
EUROCAE Technical Secretary Expert
Agenda
1. Introduction to EUROCAE WG-115 (Counter UAS)
2. Status update of the working group activity
3. ATM/UTM/C-UAS Interoperability
13rd November 2020 2
Industry standards in support of
ATM/UTM/C-UAS integration
Introduction to
EUROCAE WG-115
(Counter UAS)
13rd November 2020 3
1
Introduction to EUROCAE
WG-115 (Counter UAS)
Need identified for Standards on Minimum Requirements
Request from both Airports, Airlines & Pilots Assoc.
Need for Harmonisation/CoordinationEffective contribution to the holistic EU action plan on UAS and
C-UAS
Interaction and coordination with Security and Defence
stakeholders (Law enforcement, Police, NATO, EDA, MS….)
13rd November 2020 4
“The need for standards and guidance to
mitigate the risks of, and to improve
response to unauthorized UAS operations”
(40th Assembly ICAO, fall 2019)
"… there is a need to facilitate the
development of effective tools to counter
non-cooperative drones now and in the
years to come“ (EUROPEAN COMMISSION
- DG HOME, DG MOVE – November 2019)
Introduction to EUROCAE
WG-115 (Counter UAS)
Initiative recommended by the
EUROCAE Technical Advisory
Committee (20 Sept. 2019)
Initiative approved by the
EUROCAE Council (25 Oct. 2019).
Finally Kick-off took place in
December 2019 (12 Dec. 2019).
Now Joint with RTCA Special
Committee 238
13rd November 2020 5
WG-115 Participation
A.D.Ventures Software Ltd
Aeroport de Paris
Airbus Defence & Space (Spain)
Airbus Group
Airbus SAS
Blighter Surveillance Systems Ltd
CAA/SRG
CAA of Singapore
Collins Aerospace
CS Group
DSNA
EASA
ENAC
ENAIRE
EUROCONTROL
European Cockpit Association
European Commission
Everis Aeroespacial y Defensa
Fraport
Frequentis AG
GE Aviation Systems UK
Hensoldt Sensors GmbH
Havelsan AS
HOVERTAXI
Hungaro Control
IATA
International Air Traffic Automation
Systems
Indra Sistemas
INECO
International Aero Navigation Systems
Concern, JSC
Japan Radio Air Navigation Systems
Association
Korea Institute of Aviation Safety
Technology
Lilium GmbH
Nav Portugal
Naviair
NEC Corp
NLR
Nordic Radar Solutions
ONE-ATM
ONUR A.S.
RETIA A.S.
Rinicom Intelligent Solutions Ltd
Rohde & Schwarz GmbH & Co.
RPE CRTS LLC
RTCA, Inc.
SESAR JU
Terma A/S
Thales Group
Thales LAS France
Unifly NV
Università Telematica Giustino
Fortunato
More than 100 participants in WG-115
& more than 70 in RTCA SC-238
Industry standards in support of
ATM/UTM/C-UAS integration
Status update of the
working group activity
13rd November 2020 7
2
WG-115 Terms of Reference
WG-115 is established to develop standards to support the safe and harmonised implementation of Counter-UAS
Systems into airport and ANSP systems
Document Title Target date
OSED OSED for Counter-UAS in controlled airspace Q3/2020
SPRSystem Performance Requirements for non-cooperative UAS detection systems
Q2/2021
INTEROPInteroperability Requirements for Counter-UAS systems.
Q2/2021
13rd November 2020 8
Operational Services and Environment
Definition – Operational Expectations
13rd November 2020 9
The OSED document provides a detailed description of the operational services(chapter 3) of a C-UAS system, and the environment (chapter 4) in which such asystem will operate. It proposes operational requirements and associatedassumptions that will be further detailed in the complementary standarddocuments: SPR and INTEROP
13rd November 2020 10
Table of Contents
CHAPTER 1 PURPOSE AND SCOPE
CHAPTER 2 COUNTER-UAS CONCEPT
2.1 The UAS Threat
2.2 Counter UAS
2.3 High level legal framework
CHAPTER 3 OPERATIONAL SERVICES
3.1 Introduction
3.2 Detection
3.3 Decision Support
3.4 Neutralization
CHAPTER 4 OPERATIONAL ENVIRONMENT
4.1 Environment Identification
4.2 Airport and air traffic
4.3 Traffic Management
4.4 Actors
4.5 Other surroundings and environments
CHAPTER 5 SCENARIO DESCRIPTIONs
APPENDIX A GENERAL OPEN FRAMEWORK FOR C-UAS
APPENDIX B SUMMARY OF REQUIREMENTS
OSED: ToC and Open Consultation
Open Consultation
Deadline: 11/16/2020 -
12:00 AM
https://www.eurocae.net/news/posts/2020/october/
eurocae-open-consultation-ed-286/
Note: OSED content is draft, under open consultation
13rd November 2020 11
OSED: Operational Requirements
REQ Requirement REQ Requirement
[REQ:1] The C-UAS system shall provide support for protection according to both approaches, security and safety.
[REQ:2] The C-UAS system shall continually adapt to new threats and more efficient elements, as they appear on the market.
[REQ:3] The operation of a C-UAS system shall be compliant with the legal framework of the nation where it is deployed, considering spectrum regulation, privacy laws as well as restrictions governing safety and efficiency of airport operations
[REQ:4] C-UAS operation response shall be integrated into Standard Operating Procedures (SOP).
[REQ:5] The C-UAS system shall report about status and performance degradation or failure
[REQ:6] The C-UAS system shall detect simultaneously one or multiple UAS
[REQ:7] The C-UAS system shall provide information about the detected UAS (number, location, direction and speed)
[REQ:8] The C-UAS system shall support decision by providing information and tools for threat analysis, alerting, incident response and initial engagement
[REQ:9] The C-UAS system shall report the level of confidence of the provided information
[REQ:10] The C-UAS system shall provide flexibility to support current airport infrastructure and airport operations, and to support change or expansion of airport operations (e.g. a new runway is built)
[REQ:11] The C-UAS system shall be able to evaluate risk areas as required by the airport specific operational procedures
[REQ:12] The C-UAS system shall not compromise the existing aviation safety and security levels of the airport considering the specificities of the airspace associated to the airport.
Note: OSED content is draft, under open consultation
13rd November 2020 12
OSED: Operational Requirements
REQ Requirement REQ Requirement
[REQ:13] The C-UAS system shall not affect current operations of Communication, Navigation and Surveillance (CNS) systems
[REQ:14] The C-UAS system shall be able to interface with existing ATM system for exchange of information on collaborative/cooperative aircraft or UAS
[REQ:15] The C-UAS system shall interface with appropriate UTM/U-Space systems and services for exchange of information on collaborative/cooperative UAS or other relevant information
[REQ:16] The C-UAS system shall support C-UAS operations developed by each stakeholder involved in the C-UAS cycle.
[REQ:17] The C-UAS system shall provide suitable information to every stakeholder involved in the C-UAS cycle
[REQ:18] The C-UAS system shall be robust against electromagnetic interferences generated by airport operations
[REQ:19] The C-UAS system shall be robust against adverse weather conditions, according to the type of airport operations.
[OPT:1] The C-UAS system shall be able to assist with other surveillance and security tasks, for example, perimeter monitoring, detection and tracking of humans and vehicles.
Note: OSED content is draft, under open consultation
13rd November 2020 13
OSED: Operational Recommendations
REC Recommendation REC Recommendation
[REC:1] The C-UAS system should support open standards to allow for scalability with existing systems and future systems and innovation, e.g. new sensors, new countermeasures, new UAS service providers or other third-party systems
[REC:2] The C-UAS system should be able to continuously (24/7) provide the necessary information to support alerts on unauthorized UAS.
[REC:3] The C-UAS system should be able to provide the necessary information to support the distinction between unauthorized and authorized drones.
[REC:4] The C-UAS system should provide additional information about the detected UAS (size, type/model, operator/RP location, payload, …).
[REC:5] The C-UAS system should be ready to support a combination of multiple types of detection technologies in order to improve C-UAS performance.
[REC:6] Relevant information from the CUAS system should be shared across incident management or workflow management tools to coordinate stakeholder response activities.
[REC:7] The C-UAS system should evaluate unpredictable and undesired effects into the environment, other UAS and manned aircraft, when active components e.g. sensors and neutralization measures are intended to be used.
Note: OSED content is draft, under open consultation
13rd November 2020 14
SPR and INTEROP
• Once OSED is under Open Consultation, new stage focused on SPR and
INTEROP has been recently opened.
• According to the TOR:
• 2nd Deliverable
• Title: System Performance Requirements (SPR) for non-
cooperative UAS detection systems.
• Purpose and justification of the proposal: Create a
performance specification for non-cooperative surveillance
systems for detection of UAS in controlled airspace, especially in
the vicinity of airports. Provide performance parameters and an
unambiguous set of system minimum requirements.
• Note: TOR states “The topic of cooperative targets detection is not
to be addressed, but interaction with information from cooperative
sensors should be included in the overall system assessment”
Detection System
Performance
Provide the information required to react
against non-authorised UAS operating in
a defined perimeter around an airport
Focus is on non-cooperative detection, as U-Space
(UTM) will address cooperative/collaborative UAS
Functions
Detection, Tracking, Identification
Coverage
Range, Altitude
Generic or parametric
Detection
Probability of detection
False Alarm Rate
…
Information
Initial detection
4D Location
Speed Vector
Information about UA - Type, Make, Model…
Information about RPS location
Information about C2 Link
Data Quality
Accuracy, resolution, data rate, noise
rejection, linearity, resolution, etc.
13rd November 2020 16
SPR and INTEROP
• 3rd Deliverable
• Deliverable title: Interoperability (INTEROP) Requirements for
Counter-UAS systems.
• Purpose and justification of the proposal:
• Take into account the need for real time and high-quality data
transmission of non-cooperative sensor systems for the detection
of UAS. Derive a set of minimum interface requirements and an
interface description to the existing A-SMGCS at airports and to
other partner systems for the display and alerting of UAS.
• Consider effects and performance of typical defeating
capacities of C-UAS system and their impact on existing airport
and ANSP systems, and derive interoperability requirements.
• Note: TOR states “… but interaction with information from
cooperative sensor should be included in the overall system
assessment”
Interoperability Requirements
Interface requirements
Between Components of C-UAS
Between C-UAS and external Systems
e.g. ATM/ATC systems, UTM services
Between C-UAS and Stakeholders
e.g. ATC, Airport Authorities, Law Enforcement, Pilots?
Main constraints for C-UAS - Including Neutralisation Systems
Compliance with (national) legal Framework
Not interfering with, or impacting, airport Activities & Systems
C-UAS Overall Architecture
DetectionDecisionSupport* Neutralisation
Sensor 1
Sensor 2
Sensor n
DetectionLocation
& Tracking
Classif. & Ident.
Data Collec.
Provide information about unauthorised UAS (potential
threats)
ThreatAnalysis
Alerts
Incident Response
Initial Engagement
Effector 1
Effector 2
Effector n
Provide information for decision making*
Provide desired effect to mitigate the threat
* If man in the loop/could be fully or partially automated
Situation Awareness
(or DTI)
Industry standards in support of
ATM/UTM/C-UAS integration
ATM/UTM/C-UAS
Interoperability
13rd November 2020 19
3
✈ OSED - Chapter 3 (Operational Services)✈ Operational Service “Detection”: “The data collection process could
interface with ATM, UTM/U-space, and other available services for exchanging of information” (Detection by C-UAS)”.
✈ OSED - Chapter 4 (Operational Environment)✈ Regarding ATM/ATC:
✈C-UAS procedures should be coordinated in advance with ATM representatives to ensure de-confliction and effective integration of detection and response efforts
✈ [REQ:14] The C-UAS system shall be able to interface with existing ATM system for exchange of information on collaborative/cooperative aircraft or UAS.
✈ Regarding UTM/U-Space:✈UTM/U-Space systems may assist authorities with performing rapid identification
of the authorization status and the identification of UAS near the airport environment. This information can aid in differentiating UAS flights performing legitimate operations from those operations that are illegitimate
✈ [REQ:15] The C-UAS system shall interface with appropriate UTM/U-Space systems and services for exchange of information on collaborative/cooperative UAS or other relevant information.
ATM/UTM/C-UAS Interoperability
DecisionSupport* Neutralisation
ThreatAnalysis
Alerts
Incident Response
Initial Engagement
Effector 1
Effector 2
Effector n
ATM UTMU-Space
Airport Authorities
Law Enforc.
Authorities……
ATM/UTMU-Space
* If man in the loop/could be fully or partially automated
Detection
Sensor 1
Sensor 2
Sensor n
DetectionLocation
& Tracking
Classif. & Ident.
Data Collec.
Situation Awareness
(or DTI)
ATM/UTM/C-UAS Interoperability
Jorge Munir El Malek Vázquez
Chairman of WG-115 (C-UAS)
Phone: +34 607 202 247
13rd November 2020 22
Alain Vallée
Technical Secretary Expert
Phone: +33 6 07 52 77 69
