90 likes | 159 Views
Objective ATC 17. ESSIP Plan 2013. Luca DELL’ORTO DSS/EIPR 13.09.2013. Comprehensive Explanation. Target Date: 12/2018 SCOPE: ECAC – All States except SK
E N D
Objective ATC 17 ESSIP Plan 2013 Luca DELL’ORTO DSS/EIPR 13.09.2013
Comprehensive Explanation • Target Date: 12/2018 • SCOPE: ECAC – All States except SK • Electronic dialogue as automated assistance to controller during coordination and transfer addresses the facilities and processes between ATC components serving ATC units. • ATC17 complements ITY-COTR. • Purpose: • Co-ordination prior to the transfer of flights from one ATC unit to the next; • Transfer of communication from one ATC unit to the next ATC unit of such flights; • Support the exchange of OLDI messages related to the Basic procedure and, if applicable, SSR Code Assignment Message. ESSIP Plan 2013 / Objective ATC17
What is new or has changed for ESSIP Plan ed. 2013 • Change in the applicability area: removal of SK ESSIP Plan 2013 / Objective ATC17
Link to European ATM Master Plan and/or Interim Deployment Programme (IDP) Eur. ATM Master Plan: • [CM-0201] – Automated Assistance to Controller for Seamless Coordination, Transfer and Dialogue - ESSENTIAL IDP: • WP 5.2 ESSIP Plan 2013 / Objective ATC17
Most important SLoA(s) • All • Note: whereas this objective is defined with an ECAC scope, it will be the decision of the individual ATS Provider to: • define its local applicability in terms of relevant ATSUs, and • identify the processes to be implemented (refer to ATC17 SLoAs and in particular, their finalisation criteria, for the complete list of processes). ESSIP Plan 2013 / Objective ATC17
Finalisation Criteria and Closed Questions For REG01: • Formal acceptance by NSA of the proposed changes For ASP01: • Deliver safety arguments for all changes related to implementation of electronic dialogue for Coordination and Transfer. For ASP02/3/4 (important to clearly identify ATSUs involved and which processes are implemented): • Ground systems updated • Technical File with evidences of compliance to EC Declaration of Verification; • Functions (form the list in it he individual SLoAs) documented and in operational use. For ASP05: • Training plans updated and training package developed by the ANSP for the use of electronic dialogue procedure. ESSIP Plan 2013 / Objective ATC17
Supporting Material • EUROCONTROL-Specification for On-Line Data Interchange (OLDI) Edition 4.2 (OJEU Reference 2011/C 146/05) • EUROCONTROL-System Supported Coordination (SYSCO) Implementation Guidelines ESSIP Plan 2013 / Objective ATC17
ESSIP Report 2012 • Objective introduced in the ESSIP Plan in 2012. • No ANSPs have reported it as completed; 6 reported it partially completed (functionalities available and ATCOs trained but not implemented operationally). This requires agreement with neighbouring ACCs where the same functionalities must be available. • From the reported ANSP plans, the current estimate for achievement is 12/2016 for 80% of the applicable area. ESSIP Plan 2013 / Objective ATC15
Links and contacts • Objective Coordinator: Dell’Orto Luca, +32 2 729 3325 luca.dellorto@eurocontrol.int • EUROCONTROL Objective Expert: Stephen Morton, +32 2 729 3492 stephen.morton@eurocontrol.int ESSIP Plan 2013 / Objective ATC17