Objective ATC 07.1 ESSIP Plan 2013 Luca DELL’ORTO DSS/EIPR

2 Comprehensive Explanation  Implementation of Arrival MANager (AMAN) (metering, sequencing and advisory tool) (AMAN)  Scope: Multi-National (changed in ESSIP Plan ed to match the reports provided by individual ANSPs in the LSSIP 2012 exercise)  Applicability Area: AT / BA / BE / CH / CZ / DE / DK / ES / FI / FR / HR / IE / IT / LU / LV / MAS / NL / NO / PL / PT / RO / SE / UA / UK  Additional States have implemented basic AMAN functions (sequencing and metering without advisory tool) Detailed functionalities:  AMAN calculates the a/c sequencing for the concerned airport based on the  flight predicted trajectory,  environmental data (i.e. holding patterns),  declared airport capacity transferred into separation criteria (time) and  ATM separation criteria within TMA/CTR. AMAN provides strategic advise as to how to establish the calculated airport arrival sequence (delay on airway, flight in holding) Requirement: Initial Basic AMAN requires appropriate presentation of airport arrival sequence (arrival list) to the ACC and APP planning controllers. ESSIP Plan 2013 / Objective ATC 07.1

3 What is new or has changed in ESSIP Plan ed  SCOPE changed from ECAC to Multi-N ESSIP Plan 2013 / Objective ATC 07.1

4 Link to European ATM Master Plan  [TS-0102] - Basic Arrival Management Supporting TMA Improvements (incl. CDA, PRNAV) – ESSENTIAL ESSIP Plan 2013 / Objective ATC 07.1

5 Most important SLoA  ASP04 - Implement AMAN with advisory tool (ASP01 only refers to AMAN function concerning the sequencing and metering).  ASP02 & ASP03 - Definition, validation and implementation of ATC procedures for an operational use of AMAN tool, including the changes in the TMA organisation (SID/STAR and adapted holding patterns). Note: The implementation scope has to be defined locally, depending on the complexity of concerned TMAs ESSIP Plan 2013 / Objective ATC 07.1

6 Finalisation Criteria and Closed Questions  Ensure AMAN is part of new systems, or:  implemented during upgrade of current system.  AMAN can be implemented as a stand alone system; providing advice to arrival management using a separate system trajectory and presentation facility (  stand-alone Controller Working Position (CWP) for AMAN function)  AMAN initial basic in operational use?  Basic AMAN implemented? ESSIP Plan 2013 / Objective ATC 07.1

7 Supporting Material  The relevant Operational Requirements Document (ORD) and functional specification were produced by EATCHIP in 1997/1998. Note: These documents have not been revised since.  EROCONTROL Arrival Manager Implementation Guidelines and Lessons Learned Edition ESSIP Plan 2013 / Objective ATC 07.1

8 ESSIP Report 2012  This objective exists since 1995 and very slow progress has been recorded in the last 18 years.  At December 2012, 10 (out of 21) States declared the objective as Completed  No delay reported for the implementation of this objective. This is mainly due to the postponement of its Full Operational Capability date, which in 2011 (ESSIP Plan ed. 2012) was changed from 12/2010 to 12/2015. ESSIP Plan 2013 / Objective ATC 07.1

9 Links and contacts  Objective Coordinator: Dell’Orto Luca,  EUROCONTROL Objective Expert(s): Paul Conroy Predrag Terzioski, ESSIP Plan 2013 / Objective ATC 07.1