Professional Documents
Culture Documents
Preliminary
Deployment Programme V0
(PDP V0)
Preliminary Deployment Programme V0
Table of contents
3. Structure............................................................................................................................................ 7
7.1. AF#1 - Extended Arrival Management and Performance Based Navigation in high density Terminal
Manoeuvring Areas .................................................................................................................................. 14
DEPLOYMENT ALLIANCE 2
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 3
Preliminary Deployment Programme V0
7.6.5. Interdependencies with other sub-functionalities and/or implementation projects and high level
timeline .................................................................................................................................................... 79
DEPLOYMENT ALLIANCE 4
Preliminary Deployment Programme V0
1. Executive Summary
The Preliminary Deployment Programme (PDP) shall provide the initial project view of the
ATM functionalities of the Pilot Common Project in order to support the successful
implementation of the Regulation (EU) N716/2014.
The PDP has been conceived to provide the implementing stakeholders with further
indications concerning their project proposals versus the contents of the PCP. It consists
of project clusters whose purpose is to prepare and ensure consistency, interconnection
and interoperability with the implementation of the overall PCP. This will be achieved
through a number of proposed high level initiatives, strictly linked to PCP requirements,
whose intent is to involve and synchronize implementations from the relevant
operational stakeholders.
Since there is already a delay on the delivery of the so-called baseline elements, as
already addressed by the IDSG1 through the monitoring and reporting of the Interim
Deployment Programme and detailed in its Transition Report, the PDP is intended to:
Speed up deployment of all the pre-requisites and facilitators of the PCP
functionalities, in order to be ready for a timely, coordinated and synchronised
deployment of PCP elements;
Cover the deployment of mature elements of the PCP.
The timely and coordinated execution of the PDP will minimize the risk of delaying the full
PCP deployment that could seriously jeopardise the operational benefits expected by its
implementation.
The proposed PDP focuses on clusters of Implementation projects, which are named and
referred to as Fast Tracks. Each Fast Track is identified as belonging to:
Family 1 all baseline activity, mainly covered by IDP indications, necessary for
the timely and synchronised implementation of the prerequisites of the PCP;
Family 2 all PCP elements mature to be deployed.
Each Fast Track is described in a standard format, providing the required information on
the area of interest, the scope, the involved stakeholders and the geographical
applicability, in accordance with Regulation (EU) N716/2014.
1
The Interim Deployment Steering Group (IDSG) was established in February 2012 in order to consolidate
the steering process for early deployment activities, as test bed for the governance mechanisms to be
implemented, and ensure its continuation up to the establishment of the future deployment governance
(January 2012). In its plenary configuration, it consists of designated experts from the civil and military
representatives of the States within the SES area and also from the relevant ATM operational stakeholders
(ANSPs, Airspace users, Airports, the Network Manager (NM)), the EASA, and the SJU. The IDSG also meets
in a technical configuration, called Expert Team, in order to perform detailed analysis and prepare the
reports to the Single Sky Committee for positive opinion. In this configuration, membership is extended to
experts from the manufacturing industry.
DEPLOYMENT ALLIANCE 5
Preliminary Deployment Programme V0
All Fast Tracks are grouped taking into consideration the relevant AFs they contribute to.
Interdependencies between AFs are described at high level, while a direct link between
the Fast Tracks and their respective AFs is shown in the indicative Gantt charts, where
timing information from ESSIP and further IDP (Interim Deployment Programme)
monitoring results can be identified.
The main source to identify the list of prerequisites and facilitators is the IDP (Interim
Deployment Programme) and the IDSG results on the analysis of the PCP priorities and
baseline essentials.
The IDSG experience has been highly valuable in order to identify the areas where major
effort should be invested and where solid processes should be built, in order to ensure
effective delivery from the implementation projects. Furthermore, the IDSG transition
reports highlights monitoring functions to be performed by the Deployment Manager,
e.g. to develop a programmatic approach that would address the potential ECAC needs
for lower airspace/TMAs reorganization and optimization in relation to continuous
descent / continuous climb application.
DEPLOYMENT ALLIANCE 6
Preliminary Deployment Programme V0
3. Structure
The Preliminary Deployment Programme is organized in three levels deriving the project
view of the Pilot Common Project from the ATM functionalities and sub-ATM
Functionalities included in the PCP IR 716/2014. The contents of the three levels are
described in the table below:
Level 1 ATM Functionalities (AF) ATM functionality means a group of ATM operational
improvements and associated enablers related to
trajectory operations, airspace and surface management
or to information sharing within the en-route, terminal,
airport or network operating environments;
Level 2 ATM Sub-Functionalities Essential operational changes (from the European ATM
(S-AF) Master Plan level 1) selected for their performance
contribution and synchronization into what an AF can be
split in a more granular way.
Level 3 Early Implementation Sampler/implementation initiatives under which local
Projects cluster implementation projects are grouped that require
Fast Tracks coordination/ synchronization at local or regional level
and/or pursue the same (part of a) Sub-Functionality
Table 1: PDPs structure
The (local) implementation projects (Level 4) belonging to the Fast Tracks will be derived
from the results of the first call INEA launched in September.
From the list of ATM functionalities described in the PCP Regulation Annex, a selection of
Fast Tracks has been derived, which have reached a high level of maturity and are
therefore suitable for immediate implementation.
These Fast Tracks are fulfilling the following criteria:
Be a prerequisite of the PCP needed to be deployed prior to the PCP: indicating an
enabler (technical or operational) conditioning the subsequent implementation of
(elements of) a PCP ATM Functionality.
Be facilitators of the PCP needed to be deployed prior to the PCP: indicating is an
enabler (technical or operational) not yet implemented from which the
subsequent implementation of (elements of) a PCP ATM Functionality would
benefit;
Be mature: PCP elements that do not require additional activities to start the
deployment (i.e. specific regulatory measures or additional standards);
Be implemented in the geographical scope of the PCP.
DEPLOYMENT ALLIANCE 7
Preliminary Deployment Programme V0
According to this assessment, the Fast Tracks defined in this document are grouped
according to the following criteria:
The following picture provides the graphical presentation of the 3 levels of the PDP, it
allows to immediately capture derivation of the Implementation Projects clusters from
the ATM functionalities and sub-functionalities, highlighting also the expected integration
which will derive from the evolution PDP to full Deployment programme.
ATM Functionality X
Preliminary ATM Sub- Full Deployment
Deployment ATM Sub-Functionality X.1 Programme
Programme Functionality X.2
Fast Track
Fast Track Project X.1.1 Project Fast Track Project X.2.1
X.1.2
Applications
for INEAs
Local Local Local Local Local Call for Proposal
Implementation Implementation Implementation Implementation Implementation
Project Project Project Project Project IDP
Implementation
projects
Key: xxx - Family 1 project xxx - Family 2 project Text in white refers to another S-AF
The following table shows information included in the PDP Level 3 Fast Tracks:
ITEM Description
DEPLOYMENT ALLIANCE 8
Preliminary Deployment Programme V0
GEOGRAPHICAL
APPLICABILITY Regulation (EU) N716/2014
4. Overall timeframe
This Preliminary Deployment Programme consists of Fast Tracks, implementation project
clusters, whose purpose is to ensure the smooth and timely deployment of the elements
of the PCP as defined in the IR and in the annex of the IR (mitigating the risk related to a
PCP non-deployment scenario).
One of the targets of the Deployment Programme will be to ensure the implementation
of the remaining elements of the Interim Deployment programme (IDP) required or
facilitating the deployment of PCP elements so that the PCP objectives do not suffer a risk
of late deployment. For the same purpose, additional PCP prerequisites and facilitators
have been identified in the framework of the IDSG-ET, to be enclosed in the initiatives to
be deployed with priority. These deployment activities are projects to be undertaken in
the framework of the present call which defines the priority projects that, given their
level of maturity, could be undertaken in 2014, 2015 or 2016.
Below is a full Gantt chart with all implementation activities for all Fast-Tracks under each
of the 6 AFs in the PCP.
DEPLOYMENT ALLIANCE 9
Preliminary Deployment Programme V0
Fast Tracks and in particular their delivery dates result mainly from the analysis of ESSIP
and IDSG IDP monitoring activity, to be further refined at DP level on the basis of the
overall picture available from the (Local) Implementation Projects.
DEPLOYMENT ALLIANCE 10
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 11
Preliminary Deployment Programme V0
Environment: Reduced noise and emissions due to limiting engine ground running
time due to better timed operations
AF#3 Flexible Airspace Management and Free Route:
Safety: Improved through better co-ordination of civil and military airspace needs
at the European Network level. Potential gains through more efficient airspace
allocation and better knowledge of traffic environment and some enhancement
through reduction in controller workload.
Capacity: Increased through better utilization of airspace resources within and
across airspace boundaries and reduced controller workload. Potential increase in
productivity through dynamic adjustment of airspace resources and suppression
of some flight regulations thanks to local ATFCM measures with the same ATC
sector manning.
Cost-effectiveness: Savings in route distances as well as better fuel efficiency
through increased use of more optimum routes/trajectories and improved
sectorization.
Environment: Emissions reduced through the use of more optimum
routes/trajectories.
AF#4 Network collaborative management:
Safety: Optimized management of traffic demand, including high-level/peak hours
traffic requests. Enhancement through reduction in controllers workload.
Enhanced by improved sharing of the network situation.
Capacity: Optimum use of the available network capacity, Increased through
suppression of flight ATFM regulations thanks to local ATFCM measures with a
standardized manning of ATC sectors configuration. Small benefits through
improved use of the airport and airspace capacity resulting from a better
knowledge of the airspace availability and of the traffic demand.
Cost-effectiveness: Reduction of costs by reduction of ATFM delays, reduction of
flight delays, enhanced through use of cost effective tools to access network
information instead of expensive local tools or procedures and through the
improved capacity
AF#5 Initial System-Wide Information Management
AF#5 SWIM is primarily an enabler for other PCP elements that deliver benefits in
safety, capacity, cost-effectiveness and environment, in AF#1, AF#3, AF#4 and
AF#6.
AF#6 Initial Trajectory Information Sharing
The only fast track in AF#6 is a family 1 precursor, and as such it does not deliver
performance benefits in its own right, but is an enabler for other projects
delivering benefits.
DEPLOYMENT ALLIANCE 12
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 13
Preliminary Deployment Programme V0
7. ATM Functionalities
7.1. AF#1 - Extended Arrival Management and Performance Based
Navigation in high density Terminal Manoeuvring Areas
7.1.1. ATM Functionality and Sub-functionalities
Target date for Operations of the complete AF as from 1 January 2024 (no distinction
Sub-AF between sub AF)
Geographical Extended AMAN and PBN in high density TMAs [and associated en-route
scope sectors] shall be operated at the airports listed in Regulation (EU
716/2014)
DEPLOYMENT ALLIANCE 14
Preliminary Deployment Programme V0
AF1
Extended AMAN and PBN in high density TMA
S-AF 1.1
S-AF1.2
Arrival Management extended
Enhanced TMA using RNP-Based Operations
to en-route Airspace
Key: xxx - Family 1 project xxx - Family 2 project Text in white refers to another S-AF
Figure 3: Structure ATM functionality AF#1 Extended AMAN and PBN in high density
TMA
DEPLOYMENT ALLIANCE 15
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 16
Preliminary Deployment Programme V0
Designator FT 1.2.1
DEPLOYMENT ALLIANCE 17
Preliminary Deployment Programme V0
Designator FT 1.2.2
Guidance material EUROCAE ER-009 / Guidance material for the generation of aerodrome
mapping database (December 2012)
DEPLOYMENT ALLIANCE 18
Preliminary Deployment Programme V0
Concerned ANSPs (operating each high density TMA and ANSPs operating
stakeholders associated and adjacent en route ACCs), NM, AU
Any of the airports/TMAs listed in Regulation (EU 716/2014) + adjacent
Geographical ACCs (the adjacent ACC may be operated by a different ANSP than the
applicability one operating the TMA)
Note: the Implementing rule does not specify the list of impacted ACCs.
DEPLOYMENT ALLIANCE 19
Preliminary Deployment Programme V0
Designator FT 1.2.3
Name RNP/RNAV (2D navigation), for high density TMAs (including aircraft
capabilities)
Sub-AF Enhanced Terminal Airspace using RNP-Based Operations
DEPLOYMENT ALLIANCE 20
Preliminary Deployment Programme V0
7.1.6. Timeline
The dates identified in this simplified Gantt chart result mainly from the analysis of ESSIP
and IDSG IDP monitoring activity, and will be further assessed upon availability of all
(local) implementation projects. Comprehensive economic appraisal of AF#1 fast-tracks
implementation
DEPLOYMENT ALLIANCE 21
Preliminary Deployment Programme V0
The overall cost of AF # 1, amounting at 0.2 billion (0.3 billion undiscounted) [till the
target implementation date 2024], would be borne by ANSPs.
DEPLOYMENT ALLIANCE 22
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 23
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 24
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 25
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 26
Preliminary Deployment Programme V0
Designator FT2.1.2
Name Electronic Flight Strips (EFS)
S-AF2.1: Departure Management Synchronised with Pre-departure
Sub-AF
sequencing
Implement Digital Flight Data Management System, such as EFS,
improve situational awareness of towers controllers by:
having data updates, received from an FDP system or by
manual inputs, automatically available at all connected
working positions;
performing Data inputs generally by simple mouse clicks
or by selecting data from menus so that no time-
absorbing interactions are needed;
Description
presenting the flight plan data in a clear and easy to read
way;
allowing combination with advanced tools like AMAN,
DMAN; A-SMGCS and to support Airport-CDM
Ref. S-AF2.5
Digital systems, such as EFSs, shall integrate the instructions given by
the air traffic controller with other data such as flight plan,
surveillance, routing, published rules and procedures.
The operational context of electronic dialogue as automated
assistance to controller during coordination and transfer addresses
the facilities and processes for data exchange between ATC
components serving ATC units for the purpose of achieving:
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 OLDI messages in
order to perform an electronic dialogue :
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 OLDI messages in order to perform
Scope an electronic dialogue:
The coordination processes that support the exchange of OLDI
messages related to the Basic procedure
Ref. S-AF2.4
The flight data processing system shall be able to receive planned and
DEPLOYMENT ALLIANCE 27
Preliminary Deployment Programme V0
cleared routes assigned to aircraft and vehicles and manage the status
of the route for all concerned aircraft and vehicles.
Ref. S-AF2.5
The controller working position shall allow the air traffic controller to
manage surface route trajectories.
DEPLOYMENT ALLIANCE 28
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 29
Preliminary Deployment Programme V0
Designator FT2.1.3
Name Basic A-CDM
S-AF2.1: Departure Management Synchronised with Pre-departure
Sub-AF sequencing
DEPLOYMENT ALLIANCE 30
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 31
Preliminary Deployment Programme V0
Designator FT2.1.4
Name Initial Airport Operational Plan (AOP)
S-AF2.1: Departure Management Synchronised with Pre-departure
Sub-AF
sequencing
The Airport element that reflects the operational status of the Airport
and therefore facilitates Demand and Capacity Balancing is the Airport
Operations Plan (AOP). The AOP connects the relevant stakeholders,
notably the Airspace Users Flight Operations Centre (FOC). It contains
data and information relating to the different status of planning
phases and is in the format of a rolling plan, which naturally evolves
over time.
Description
The AOP is a single, common and collaboratively agreed rolling plan
available to all airport stakeholders whose purpose is to provide
common situational awareness and to form the basis upon which
stakeholder decisions relating to process optimization can be made.
There are strong interdependencies with S-AF4.2 Collaborative NOP as
well as with S-AF5.5 Cooperative Network Information Exchange.
The ATM stakeholders planning processes and working methods are
included in the AOP. The initial AOP is partly integrated in the NOP
which provides a rolling picture of the network situation used by
stakeholders to prepare their plans and their inputs to the network
Scope CDM processes (e.g. negotiation of airspace configurations).
NM Information will be freely exchanged by Operational stakeholders
by means of defined cooperative network information services, using
the yellow SWIM TI Profile.
References ESSIP FCM05
Concerned stakeholders CIV/MIL ANSPs, AOP, NM, AU
Geographical
ECAC airports
applicability
The deployment of Network Collaborative Management functionality
shall be coordinated and synchronized with the AOP due to the
potential network performance impact of delayed implementation.
The synchronization of investments shall involve multiple air
navigation service providers, airports and the Network Manager.
Synchronization
The concept of A-CDM constitutes the basis for airports to establish
predictability in processes related to aircraft turn-around and as such
feeds the AOP with essential and critical information concerning
capacity issues as well as availability. This information is integrated in
the NOP (ref. S-AF4.2 Collaborative NOP).
DEPLOYMENT ALLIANCE 32
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 33
Preliminary Deployment Programme V0
Designator FT2.2.1
Name A-SMGCS Level 1/2
S-AF2.2 Departure Management integrating Surface Management
Sub-AF
Constraints
Advanced Surface Movement Guidance and Control System (A-SMGCS) is a
system providing routing, guidance and surveillance for the control of aircraft
and vehicles in order to maintain the declared surface movement rate under
all weather conditions within the aerodrome visibility operational level
(AVOL) while maintaining the required level of safety.
A-SMGCS Level 1 provides ATC with the position and automatic identity of:
- All relevant aircraft on the movement area;
- All relevant vehicles on the manoeuvring area.
DEPLOYMENT ALLIANCE 34
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 35
Preliminary Deployment Programme V0
Designator FT2.5.1
Name Airport Safety Nets associated with A-SMGCS Level 2
Sub-AF A-AF 2.5 Airport Safety Nets
Airport safety nets consist of the detection and alerting of
conflicting ATC clearances to aircraft and deviation of vehicles and
Description
aircraft from their instructions, procedures or routing which may
potentially put the vehicles and aircraft at risk of a collision.
The scope of this sub-functionality includes the Runway and
Airfield Surface Movement area. ATC support tools at the
aerodrome shall provide the detection of Conflicting ATC
Clearances as well as deviations from ATC instructions,
procedures or routes and shall be performed by the ATC system
based on the knowledge of data including the clearances given to
aircraft and vehicles by the air traffic controller, the assigned
runway and holding point. The air traffic controller shall input all
clearances given to aircraft or vehicles into the ATC system using a
digital system, such as the EFS. Different types of conflicting
Scope
clearances shall be identified (for example Line-Up vs. Take-Off).
Some may only be based on the air traffic controller input; others
may in addition use other data such as A-SMGCS surveillance
data. Airport Safety Nets tools shall alert air traffic controllers
when aircraft and vehicles deviate from ATC instructions,
procedures or routes. The detection of Conflicting ATC Clearances
shall aim to provide an early prediction of situations that if not
corrected would end up in hazardous situations that would be
detected in turn by the runway incursion monitoring system
(RIMS) if in operation
DEPLOYMENT ALLIANCE 36
Preliminary Deployment Programme V0
Designator FT 2.5.2
Name Implement aircraft systems contributing to airport safety nets
Sub-AF Airport safety nets
DEPLOYMENT ALLIANCE 37
Preliminary Deployment Programme V0
Interdependencies
DEPLOYMENT ALLIANCE 38
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 39
Preliminary Deployment Programme V0
7.2.5.Interdependencies
Interdependencies I with FT 2.5.1 Airport Safety Nets
n
terdependencies with other sub-functionalities and/or
implementation projects
The following prerequisites are required:
Digital systems, such as EFS, A-CDM and initial DMAN for Departure
Management Synchronised with Pre- departure sequencing
Digital systems, such as EFS, initial DMAN and A-SMGCS level 1 & 2 for
Departure Management integrating Surface Management Constraints
Digital systems, such as EFS for TBS
Digital systems, such as EFS and A-SMGCS level 1 & 2 for Automated
Assistance to Controller for Surface Movement Planning and Routing
Digital systems, such as EFS and A-SMGCS surveillance for Airport Safety Nets.
The sub-functionalities Departure Management Synchronised with Pre-
departure sequencing and Time Based Separation for Final Approach may
be implemented independently from the other sub-functionalities.
Interdependencies with other sub-functionalities not yet implemented will be
addressed when updating the deployment programme.
DEPLOYMENT ALLIANCE 40
Preliminary Deployment Programme V0
7.2.6. Timeline
The dates identified in this simplified Gantt chart result mainly from the analysis of ESSIP
and IDSG IDP monitoring activity, and will be further assessed upon availability of all
(local) implementation projects.
DEPLOYMENT ALLIANCE 41
Preliminary Deployment Programme V0
Geographical Flexible Airspace Management and Free Route shall be provided and
scope operated in the airspace for which the Member States are responsible at
and above flight level 310 in the ICAO EUR region
DEPLOYMENT ALLIANCE 42
Preliminary Deployment Programme V0
AF3
Flexible ASM and Free Route
S-AF 3.1
S-AF3.2
ASM and
Free Route
Advanced FUA
Key: xxx - Family 1 projec xxx - Family 2 project Text in white refers to another S-AF
Figure 7: Structure ATM functionality AF#3 Flexible ASM and Free Route
DEPLOYMENT ALLIANCE 43
Preliminary Deployment Programme V0
Geographical
Flexible Airspace Management shall be provided and operated in the
applicability
airspace for which the Member States are responsible in the ICAO
(extract from IR PCP) EUR region.
DEPLOYMENT ALLIANCE 44
Preliminary Deployment Programme V0
Designator FT 3.2.1
Geographical Free Route shall be provided and operated in the airspace for which
applicability the Member States are responsible at and above flight level 310 in
the ICAO EUR region.
DEPLOYMENT ALLIANCE 45
Preliminary Deployment Programme V0
Designator FT 3.2.2
Description Upgrade of NM systems (e.g. ADR, DDR, NOP, IFPS) to support direct
routing operations.
Implement system improvements (ADR and Airspace Management
Scope
tools), Procedures and processes to support direct routings.
DEPLOYMENT ALLIANCE 46
Preliminary Deployment Programme V0
Free Route shall be provided and operated in the airspace for which
the Member States are responsible at and above flight level 310 in
Geographical the ICAO EUR region. In a first step, DCT shall be introduced above
applicability FL 365 because this has been recognized by all ANSPs as the
optimum starting point for incremental implementation.
However, each state, based on operational environment (such as
airspace structure, ATM system limitations) can choose a different
lower level of initial Free Route Airspace implementation.
2
Implementation of Direct routes (DCT) has already been covered by the IDP WP2.3. Due to the fact, that
DCT is a first but important step towards Free Route, this fast track is listed under family 2 rather than under
family 1 where it should be listed according to the definition.
DEPLOYMENT ALLIANCE 47
Preliminary Deployment Programme V0
S-AF3.2:
When available, FRA and DCT shall be supported by Network Manager and SWIM
systems specified in AF 4 (Network Collaborative Management) and AF 5 (Initial
System Wide Information Management).
7.3.6. Timeline
The dates identified in this simplified Gantt chart result mainly from the analysis of
ESSIP and IDSG IDP monitoring activity, and will be further assessed upon
availability of all (local) implementation projects.
DEPLOYMENT ALLIANCE 48
Preliminary Deployment Programme V0
The overall cost of AF # 3, amounting at 0.7 billion [till the target implementation
date 2021], would be shared by the different stakeholders categories as follows:
ANSPs: 75% of total investment;
Military: 22% of total investment;
Network Manager: 2% of total investment;
Airspace Users (ground investment): 1% of total investment.
DEPLOYMENT ALLIANCE 49
Preliminary Deployment Programme V0
Name
AF4: Network Collaborative Management
Description
Network Collaborative Management improves the European ATM
network performance, notably capacity and flight efficiency through
exchange, modification and management of trajectory information. Flow
Management shall move to a Cooperative Traffic Management (CTM)
environment, optimizing the delivery of traffic into sectors and airports
and the need for Air Traffic Flow and Capacity Management (ATFCM)
measures.
Sub-ATM
S-AF4.1: Enhanced Short Term ATFCM Measures
Functionalities
S-AF4.2: Collaborative NOP
S-AF4.3: Calculated Take-off Time to Target Times for ATFCM purposes
S-AF4.4: Automated Support for Traffic Complexity Assessment
Target date
Operational stakeholders and Network Manager shall operate Network
for Sub-AF
Collaborative Management as from 1 January 2022
Geographical
Network Collaborative Management shall be deployed in the EATMN. In
scope
ATC centres in Member States where civil-military operations are not
integrated(Austria, Belgium, Czech Republic, France, Ireland, Italy,
Portugal, Romania, Slovakia and Spain), Network Collaborative
Management shall be deployed to the extent required by Regulation
(EC) N552/2004, point 4 of Part A of Annex II
DEPLOYMENT ALLIANCE 50
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 51
Preliminary Deployment Programme V0
Scope The target of the Short Term ATFCM Measures (STAM) is to replace En
Route CASA regulations for situations where the capacity is nominal.
DEPLOYMENT ALLIANCE 52
Preliminary Deployment Programme V0
Concerned
stakeholders CIV/MIL ANSPs, AOP, NM
DEPLOYMENT ALLIANCE 53
Preliminary Deployment Programme V0
Designator FT 4.2.2
DEPLOYMENT ALLIANCE 54
Preliminary Deployment Programme V0
Designator FT 4.2.3
Name Interface to NMS AFP
Sub-AF Collaborative NOP
DEPLOYMENT ALLIANCE 55
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 56
Preliminary Deployment Programme V0
Designator FT 4.4.1
Name
FDP System adaptation and EFD (EFTMS flight data message)
DEPLOYMENT ALLIANCE 57
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 58
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 59
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 60
Preliminary Deployment Programme V0
Designator FT 4.4.2
DEPLOYMENT ALLIANCE 61
Preliminary Deployment Programme V0
7.4.6. Timeline
The dates identified in this simplified Gantt chart result mainly from the analysis of ESSIP
and IDSG IDP monitoring activity, and will be further assessed upon availability of all
(local) implementation projects.
DEPLOYMENT ALLIANCE 62
Preliminary Deployment Programme V0
Target date Operations of the complete AF as from 1 January 2025 (no distinction
for Sub-AF between sub AF)
DEPLOYMENT ALLIANCE 63
Preliminary Deployment Programme V0
The diagram above and the tables below describe the fast tracks that are definitely ready
for deployment. However, this is fast-moving field where agreements and clarifications of
specifications could enable deployment earlier than expected.
DEPLOYMENT ALLIANCE 64
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 65
Preliminary Deployment Programme V0
Designator FT 5.2.1
DEPLOYMENT ALLIANCE 66
Preliminary Deployment Programme V0
Designator FT 5.3.1
DEPLOYMENT ALLIANCE 67
Preliminary Deployment Programme V0
Designator FT 5.3.2
Name ATM System Upgrade to support AIXM 5.1
Sub-AF Aeronautical Information Exchange
Upgrade of ATM Systems to provide data and services into SWIM and
Description
make use of SWIM services for data
ANSPs ATM systems shall:
Adopt a service-oriented approach to provision of data
Provide information to SWIM network by standard XML
Scope schema as per AIXM 5.1
Utilise SWIM for data in preference to point-to-point
interfaces where possible
Be compliant with the applicable version of the AIRM and
ISRM.
References ESSIP FCM05
Concerned ANSPs
stakeholders
iSWIM functionality shall be deployed in the EATMN as indicated in
the table in section 5.2 of Regulation (EU 716/2014). In centres in the
Geographical
Member States that have non-integrated civil/military service
applicability
provision (1), iSWIM functionality shall be deployed to the extent
required by Regulation (EC) N552/2004, point 4 of Part A of Annex II.
No ex-ante synchronization requirements, to be further assessed at
Synchronization
the level of Local Implementation Projects
As in ESSIP FCM05
Guidance material
AIXM 5.1
DEPLOYMENT ALLIANCE 68
Preliminary Deployment Programme V0
Designator FT 5.3.3
DEPLOYMENT ALLIANCE 69
Preliminary Deployment Programme V0
Designator FT 5.4.1
Description Upgrade Meteo service to provide reliable actual and forecast Meteo
data, wherever required across the ATM network, in WXXM format.
DEPLOYMENT ALLIANCE 70
Preliminary Deployment Programme V0
Designator FT 5.5.1
References
Concerned ANSPs Airports NM
stakeholders
iSWIM functionality shall be deployed in the EATMN as indicated in
the table in section 5.2 of Regulation (EU 716/2014). In centres in the
Geographical
Member States that have non-integrated civil/military service
applicability
provision (1), iSWIM functionality shall be deployed to the extent
required by Regulation (EC) N552/2004, point 4 of Part A of Annex II.
The deployment of Initial System Wide Information Management
functionality shall be coordinated due to the potential network
performance impact of delayed implementation in a wide
geographical scope involving a number of stakeholders. From a
technical perspective the deployment of targeted system and service
delivery changes shall be synchronized to ensure that the
Synchronization performance objectives are met. This synchronization shall enable
changes targeted within ATM functionalities referred to in Sub-AF 1
to 4 as well as future common projects. Synchronization shall involve
all ATM ground stakeholders (civil/military air navigation service
providers, airspace users for AOC systems, airport operators, MET
Service Providers and the Network Manager. Furthermore,
synchronization during the related industrialization phase shall take
DEPLOYMENT ALLIANCE 71
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 72
Preliminary Deployment Programme V0
Designator FT 5.6.1
Name FDPS Upgrade preparing for IOP Flight Object Exchanges
Sub-AF Flight Information Exchange
Flight information shall be exchanged during the pre-tactical and
Description tactical phases by ATC systems and Network Manager, using SWIM
standard services of the blue and yellow SWIM TI Profiles.
Operational stakeholders shall implement services which support the
exchange of the following flight information as indicated in the table
below using the blue SWIM TI Profile:
Various operations on a flight object: Acknowledge reception,
Acknowledge agreement to FO, End subscription of a FO
distribution, Subscribe to FO distribution, Modify FO constraints,
Modify route, Set arrival runway, Update coordination related
information, Modify SSR code, Set STAR, Skip ATSU in
Scope coordination dialogue
Share Flight Object information. Flight Object includes the flight
script composed of the ATC constraints and the 4D trajectory
Operational stakeholders shall implement the following services
for exchange of flight information using the yellow SWIM TI
Profile:
Validate flight plan and routes
Flight plans, 4D trajectory, flight performance data, flight status
Flights lists and detailed flight data
Flight update message related (departure information)
References Not applicable
Concerned ANSPs
stakeholders
iSWIM functionality shall be deployed in the EATMN as indicated in
the table in section 5.2 of Regulation (EU 716/2014). In centres in the
Geographical
Member States that have non-integrated civ/mil service provision (1),
applicability
iSWIM functionality shall be deployed to the extent required by
Regulation (EC) N552/2004, point 4 of Part A of Annex II.
Synchronization Peer-to-peer synchronization is needed.
Guidance material References TBD
DEPLOYMENT ALLIANCE 73
Preliminary Deployment Programme V0
7.5.6. Timeline
The dates identified in this simplified Gantt chart result mainly from the analysis of ESSIP
and IDSG IDP monitoring activity, and will be further assessed upon availability of all
(local) implementation projects.
DEPLOYMENT ALLIANCE 74
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 75
Preliminary Deployment Programme V0
DEPLOYMENT ALLIANCE 76
Preliminary Deployment Programme V0
AF6
Initial trajectory information sharing
FT6.1.1
FDP upgrade in prep. of integration of aircraft flight data prediction
Key: xxx - Family 1 project xxx - Family 2 project Text in white refers to another S-AF
Figure 13: Structure ATM functionality AF#6 Initial trajectory information sharing
DEPLOYMENT ALLIANCE 77
Preliminary Deployment Programme V0
Adapt FDP to process the air derived flight data provided through
ADS-C EPP service. This includes potential interface with the data-link
Description system (to access to the aircraft flight data) and the adaptation of the
Trajectory Prediction sub system to integrate such additional
information. It could also include the integration of the ADS-C EPP
contract and the associated CPDLC messages.
Ground System: The following are main system improvements for
ground FDP systems
Inclusion of aircraft FMS 4D trajectory within FDP Trajectory
Scope Prediction.
ADS-C contracts management (demand/event/periodic.)
Manage CPDLC messages.
HMI in CWP must also be adjusted accordingly.
DEPLOYMENT ALLIANCE 78
Preliminary Deployment Programme V0
7.6.6. Timeline
The dates identified in this simplified Gantt chart result mainly from the analysis of
ESSIP and IDSG IDP monitoring activity, and will be further assessed upon
availability of all (local) implementation projects.
DEPLOYMENT ALLIANCE 79
Preliminary Deployment Programme V0
8. List of Acronyms
Acronyms Meaning
ACC Area Control Centre
A-CDM Airport Collaborative Decision Making
ACH ATC flight plan change message
ADR Airspace Data Repository
ADS-C Automatic Dependent Surveillance-Contract
AF ATM functionality
AFP ATC Flight plan Proposal
A-FUA Advanced Flexible Use of Airspace
A-SMGCS Advanced Surface Movement Guidance and Control System
AIRM Aeronautical Information Reference Model
AIS Aeronautical Information Service
AIXM Aeronautical Information eXchange Model
AMAN Arrival Manager
ANSP Air navigation service provider
AO Airline Operator
AOC Airline Operations centre
AOP Airport operator
APCH Approach
APL ATC flight plan message
APV Approach Procedure with Vertical guidance
ASM Airspace Management
ATC Air Traffic Control
ATCO Air Traffic Controller
ATFCM Air Traffic Flow and Capacity Management
ATFM Air Traffic Flow Management
ATM Air traffic management
ATN Air Traffic Network
DEPLOYMENT ALLIANCE 80
Preliminary Deployment Programme V0
Acronyms Meaning
ATS Air Traffic Service
ATSU Air Traffic Service Unit
AU Airspace user
B2B Business-to-Business
CBA Cost benefit analysis
CDM Collaborative Decision Making
CEF Connecting Europe Facility
CFMU Central Flow Management Unit
CHMI CFMU Human Machine Interface
CIAM Collaboration Interface for Airspace Managers
CIV Civil
COP Coordination Point
CPDLC Controller-Pilot Data Link Communications
CTM Cooperative Traffic Management
CTO/CTA Controlled Time Over/Controlled Time of Arrival
DCT Direct Routing
DDR Demand Data Repository
DLS IR Data-Link Service Implementing Rule
DM Deployment Manager
DMAN Departure Management
DME Distance Measuring Equipment
DP Deployment Programme
D-TAXI Data link Taxi Support
EAD European Aeronautical Database
EASA European Aviation Safety Agency
EC European Commission
ECAC European Civil Aviation Conference
EAD European AIS Database
EFD ETFMS Flight Data
DEPLOYMENT ALLIANCE 81
Preliminary Deployment Programme V0
Acronyms Meaning
EPP Extended Projected Profile
ERNIP European Route Network Improvement Plan
ESARR Eurocontrol Safety Regulatory Requirement
ESSIP European Single Sky Implementation
ETFMS Enhanced Tactical Flow Management System
ETSI European Telecommunications Standards Institute
EUR (ICAO) European (region)
EUROCAE European Organisation for Civil Aviation Equipment
FAA Federal Aviation Authority
FAB Functional Airspace Block
FDP Flight Data Processing
FDPS Flight Data Processing System
FIN Finance (e.g. Sub-Group)
FCM Flow and capacity Management
FMP Flow Management Position
FMS Flight Model Simulator
FMS Flight Management System
FMTP Flight Message Transfer Protocol
FO Flight Object
FOC Flight Operations Centre
FPA Framework partnership Agreement
FRA Free Rout Airspace
FT Fast Track Implementation project
FUA Flexible Use of Airspace
GNSS Global Navigation Satellite System
i4D Initial Trajectory Information Sharing
4DTRAJ 4D Trajectory
IATA International Air Transport Association
ICAO International Civil Aviation Organization
DEPLOYMENT ALLIANCE 82
Preliminary Deployment Programme V0
Acronyms Meaning
IDP Interim Deployment Programme
IDSG Interim Deployment Steering group
IDSG-ET Interim Deployment Steering group expert team
IFPS Initial Flight Plan Processing System
INEA Innovation and Networks Executive Agency
IOP Interoperability
IP Internet Protocol
IR Implementing Rule
ISRM Information Service Reference Model
iSWIM Initial system wide information management
MIL military
MONA Monitoring Aid
MP Master Plan
MTCD Medium-term Conflict Detection
NSA National Supervisory Agency
NM Network Manager
NMF Network Management Function
NMS Network Management System
NOP Network Operations Plan
OLDI On-line Data Interchange
PBN Performance based navigation
PCP Pilot Common Project
PDP Preliminary Deployment programme
PANS Procedures for Air Navigation Services
PENS Pan European Network System
PKI Public Key infrastructure
RF Radius to Fix
RNP Required navigation performance
S-AF ATM Sub-functionality
DEPLOYMENT ALLIANCE 83
Preliminary Deployment Programme V0
Acronyms Meaning
SBAS SatelliteBased Augmentation System
SESAR Single European Sky ATM Research
SID Standard Instrument Departure
SJU SESAR Joint Undertaking
SG Sub-Group
SLoA Stakeholder Lines of Action
SSR Secondary Surveillance Radar
STCA Short-term Conflict Alert
STAR Standard Arrival Route
SWIM System-Wide Information Management
TBO Time Based Operation
TI Technical Infrastructure
TMA Terminal manoeuvring area
TTG Time To Gain
TTL Time To Lose
TTOT Target Take Off Time
TSAT Target Start-up Approval Time
VOR VHF Omnidirectional Radio Beacon
WXXM Weather Information Exchange Model
XML Extensible Mark-up Language
DEPLOYMENT ALLIANCE 84