 |
Operational requirements for an Arrival Manager (AMAN) were developed in the late 1990s and the ATM systems industry has been developing Arrival Managers in line with these guidelines resulting in the delivery of (commercial) systems/products to a number of ANSPs.
Some ANSPs have also been developing and prototyping AMAN tools tailored to their own specific needs. As a result a number of different AMAN systems are in day-to-day use across Europe.
However, little documentation exists to assist new implementers or to provide experience or information from earlier implementations.
|
|
 |
 |
The general objective of AMAN software is to assist, through dedicated automation, in the management of the flow of arriving traffic in a particular airspace and to particular points (i.e. runway thresholds or metering points). Its main aims are to:
- Optimise the arrival traffic (sequence)
- Regulate/manage the flow of aircraft to improve predictability, reduce workload and at the same time minimise the impact on the environment (meter)
|
 |
 |
The planning and/or sequencing function of the AMAN also aims to assist controller management of the arrival flow, particularly in the case of perturbations (i.e. runway closure).
|
 |
 |
EUROCONTROL carried out a survey of the status of the various AMAN implementations across Europe in 2009 resulting in the AMAN Status Review 2009 (see below). A further review was performed in 2010 which resulted in an new status review (see below).
|
 |
 |
As a result of the 2009 review it became clear that there are various interpretations of what constitutes ‘arrival management functionality’ and that defining or classifying all the different types and levels of automation used in arrival management is a complex task.
Resulting from the 2009 review a consolidated set of guidelines for AMAN implementations documenting the experience gained by ANSPs during their AMAN development has been produced (see below). These are aimed at providing assistance both for new and ongoing implementations.
|
 |
 |
Stakeholders have approved the inclusion of 2 AMAN-related activities within the scope of the FASTI Working Arrangements. These cover:
- Arrival Management System Support
- Extended Arrival Management
|
 |
 |
In both of these areas the scope of activity includes the co-ordination of the implementation and the provision of support for deployment, where required, up to 2013.
Both these activities are supporting SESAR IP1 Operational Improvements: “Arrival Management Supporting TMA Improvements” and “Extended Arrival (AMAN in En-route)”, respectively.
|
 |
 |
 |
| Arrival Manager - Implementation Guidelines and Lessons Learned
|
|
This document presents AMAN Implementation Guidelines.
It provides an overview of available AMANs in Europe with recommended implementation guidance material, including material on required studies. It summarizes some of the identified issues and builds on the exchange of the lessons learned by AMAN pioneers.
This document should be viewed in parallel with “AMAN Status Review 2010”
|
|
|
Released: 17/12/2010
|
Edition: 0.1
Author: Nathalie Hasevoets & Paul Conroy
|
|
| AMAN Status Review 2010
|
|
This document presents a Status Review report on AMAN in Europe in 2010. It is an updated version of the document “AMAN Status Review 2009”.
This document provides an overview of available AMANs in Europe and their respective users, together with some users’ comments. Material on AMAN Concept, System Components and AMAN Issues, previously contained in the 2009 version of this document is now available in the “AMAN Guidelines".
This document should be viewed in parallel with those “AMAN Guidelines”.
|
|
|
Released: 17/12/2010
|
Edition: 0.1
Author: Nathalie Hasevoets & Paul Conroy
|
|
| AMAN Status Review 2009
|
|
This document presents a Status Review report on the implementation of AMAN in Europe in 2009.
|
|
|
Proposed Issue: 17/02/2010
|
Edition: 0.2
Author: Nathalie Hasevoets
|
|
| AMAN Information Extension to En-route Sectors - Concept of Operations
|
|
This document proposes a harmonised way for the extension of the AMAN information to adjacent En-route sectors.
|
|
|
Released: 05/06/2009
|
Edition: 1.0
|
|
 |
|
 |