The operational context of electronic dialogue as automated assistance to controller during coordination and transfer addresses the facilities and processes between ATC components serving ATC units for the purpose of achieving:
1.The electronic dialogue in co-ordination prior to the transfer of flights from one ATC unit to the next.
In the scope of this objective the implementers should use the following OLDI messages in order to perform an electronic dialogue :
- Referred Activate Proposal Message (RAP);
- Referred Revision Proposal Message (RRV)
- Co-ordination Message (CDN)
- Acceptance Message (ACP)
- Reject Co-ordination Message (RJC)
- Stand-by Message (SBY)
2. The transfer of communication from one ATC unit to the next ATC unit of such flights.
In the scope of this objective the implementers should use the following OLDI messages in order to perform an electronic dialogue:
- Change of Frequency Message (COF)
- Manual Assumption of Communications Message (MAS)
- Transfer Initiation Message (TIM)
- Supplementary Data Message (SDM)
- Hand-Over Proposal Message (HOP)
- Request on Frequency Message (ROF)
3. The coordination processes that support the exchange of OLDI messages related to the Basic procedure, specifically Preliminary Activation Message (PAC) and, if applicable, SSR Code Assignment Message (COD).
The system permits controllers to conduct screen to screen coordination between adjacent ATSUs / sectors reducing workload associated with coordination, integration and identification tasks. The system supports coordination dialogue between controllers and transfer of flights between ATSUs, and facilitates early resolution of conflicts through inter ATSU/sector coordination.
NOTE: This objective complements the (mandatory) requirements of basic notification, coordination and transfer functionalities which were covered in Implementation objective ITY-COTR (achieved in 2015) and regulated by Regulation (EC) No 1032/2006.
NOTE FOR MILITARY AUTHORITIES: It is the responsibility of each military authority to review this Objective IN ITS ENTIRETY and address each of the SLoAs that the military authority considers RELEVANT for itself. This has to be done on top and above of the review of "MIL" SLoAs which identify actions EXCLUSIVE to military authorities.
Code | Title | IOC | FOC | Related Elements |
---|---|---|---|---|
CM-0201 | Automated Assistance to Controller for Seamless Coordination, Transfer and Dialogue | — | — |
Code | Title | IOC | Related Elements |
---|---|---|---|
PRO-048 | ATC Procedures to implement screen to screen coordination for transfer of control conditions | — |
Code | Title | Program | Related Elements | Analysis |
---|---|---|---|---|
#104 | Sector Team Operations - En-route Air Traffic Organiser | SESAR1 | Analysis |
Code | Dates | |
---|---|---|
1999
99
2000
00
2001
01
2002
02
2003
03
2004
04
2005
05
2006
06
2007
07
2008
08
2009
09
2010
10
2011
11
2012
12
2013
13
2014
14
2015
15
2016
16
2017
17
2018
18
2019
19
2020
20
2021
21
2022
22
2023
23
2024
24
2025
25
|
||
|
||
ATC17 | 20130101_20220101 | |
REG01 (DELETED) | 20130101_20220101 | |
ASP01 | 20130101_20220101 | |
ASP02 | 20130101_20220101 | |
ASP03 | 20130101_20220101 | |
ASP04 | 20130101_20220101 | |
ASP05 | 20130101_20220101 |
Title | Related SLoAs |
---|---|
EUROCONTROL - EAM 4 - ESARR 4 - Risk Assessment and Mitigation in ATM - Edition 1.0 / 04/2001 https://www.eurocontrol.int/publication/esarr-4-risk-assessment-and-mitigation-atm |
ASP01 |
EUROCONTROL - EAM 4/GUI 1 - Explanatory Material on ESARR 4 Requirements - Edition 2.0 / 03/2005 https://www.eurocontrol.int/publication/esarr-4-risk-assessment-and-mitigation-atm |
ASP01 |
EUROCONTROL - SPEC-106 - EUROCONTROL Specification for On-Line Data Interchange (OLDI) - Edition 5.0 / 07/2020 https://www.eurocontrol.int/publication/eurocontrol-specification-line-data-interchange-oldi |
ASP01, ASP02, ASP03, ASP04, ASP05 |
EUROCONTROL - System Supported Coordination (SYSCO) Implementation Guidelines - Edition 2.0 / 03/2011 |
ASP02, ASP03, ASP04, ASP05 |