Update on SESAR Deployment - FORUM-AE · SESAR Deployment Manager –SDM 3. Deployment Programme...
Transcript of Update on SESAR Deployment - FORUM-AE · SESAR Deployment Manager –SDM 3. Deployment Programme...
Update on SESAR Deployment Forum AE workshop
I will talk about
1. From ATM Master Plan to deployment of new technology and services
2. SESAR Deployment Manager – SDM
3. Deployment Programme – DP
4. What’s in Pilot Common Projects – PCP
5. Present status and coming activities
In 2014, Europe took a major
step towards ATM modernisation
SESAR R&D is delivering, it‘s time for deployment! First implementation package – the Pilot Common Project - approved
in 2014 as an EU Regulation with binding deadlines (EC 716/2014)
EC providing public funds to support ATM modernisation and PCP implementation via INEA CfPs (CEF incl. Cohesion) – 2.5 bEUR
SESAR Deployment Manager is Established under SES regulatory framework (EC 409/2013)
As an partnership between European Union and European industry
To plan, synchronise and coordinate implementation
100% funded by European Union
SESAR Deployment Managerin the SES framework
Single European
Sky
Institutional
Performance, Functional Airspace
Blocks, Network Manager
Human
Technological
DefinitionResearch and Development
Deployment
SAFETY
5
R&D INDUSTRIALISATION DEPLOYMENT
Large Scale Demonstrations Pre-
implementation
StandardisationSafety
European ATM Master Plan
SESAR JU – SESAR DM2 entities, 1 project
From Master Plan toDeployment Programme
Pilot CommonProject (PCP)
June 2014
DeploymentProgramme (DP)
2015
ATMMaster PlanEdition 2012
Pilot Common ProjectRegulation (EU) 716/2014
SDM to plan/monitor/synchronize…
Extended AMAN and PBN in high density TMAsKey functional improvements addressing critical network performance deficiencies
Airport Integration and Throughput Functionalities
Flexible Airspace Management and Free Route
Network Collaborative Management (Flow & NOP)
iSWIM: ground-ground integration andaeronautical data management and sharing Building the
infrastructure of the future Initial Trajectory Information Sharing:
air-ground integration towards i4D
DP Structure• Defined in PCP regulation
– 6 ATM Functionalities (AF)
– 20 Sub ATM Functionalities (sAF)
• Defined in DP– 44 Families
• CEF Call 2014 (reference to PCP)– 84 implementation projects related to Families
• CEF Call 2015 (reference to DP 2015)– Biding process ongoing until 16 Feb
• Subsequent CEF Calls are expected– Updated versions of DP
What’s so special with the Deployment Programme?
Sole reference for PCP implementation planning and monitoring
Provides the clear picture of the Implementation activities still to be performed towards full PCP deployment for each of the 44 families of implementation projects
Identification of gaps has been carried out in full cooperation with operational stakeholders, EDA, SJU and NM
DP 2015 is the specification for the PCP part of the
CEF call 2015 (515 mEUR + 300 mEUR in CF)
Updated DPs will support subsequent CEF calls
9
10
10
Deployment Programme 2015 SDM’s monitoring: your dashboard for PCP implementation
3.2.1 Upgrade of ATM systems (NM, ANSPs, AUs) to support Direct Routings (DCT) and Free Route Airspace (FRA)
MUAC
N
N
N
N N
N
Chart KeyFamily’s scope fully implemented
Submitted projects (partial coverage)
Implementation in progress (no CEF funding requested/awarded)
Partial coverage (Stakeholders)
No information available
Submitted projects (full coverage)
Implementation planned (no CEF funding requested/awarded)
Partial coverage in terms of scope (functionalities)
Complete lack of any implementation initiative
Not applicable
N Initiatives critical for Network performance improvement
Network Manager has to be considered as a gap
Airspace Users needing updates oftheir Computer Flight Planning Systems
have to be considered as part of the list of gaps
In the Monitoring View, DP 2015 provides overall views concerning the status of Implementation of each family throughout Europe, on a geographical scope basis (airports for AF1, AF2; countries for AF3, AF4, AF5, AF6).
ANSPs, Airports, Airspace Users and Network Manager have been thoroughly involved in the analysis
FCO
MXP
PMIBCN
MADNCE
ORYCDG
DUBGAT
FRA
AMS
MUC
DUS
BER
CPH
ARN
OSL
LHR
STN
MAN
VIE
BRU
ZRH
1.1.2 AMAN Upgrade to include Extended Horizon
N.B. No information available for Istanbul Ataturk Airport
N
N
N
NB – Feeding TMA and en-route sectors for the 25 airports shall be considered
Chart KeyFamily’s scope fully implemented
Submitted projects (partial coverage)
Implementation in progress (no CEF funding requested/awarded)
Partial coverage (Stakeholders)
No information available
Submitted projects (full coverage)
Implementation planned (no CEF funding requested/awarded)
Partial coverage in terms of scope (functionalities)
Complete lack of any implementation initiative
Not applicable
N Initiatives critical for Network performance improvement
AF 1 and AF2: view per airportAF 3, AF4, AF5 and AF6: view per state and airspace users summary
Content of AF 1Extended AMAN and PBN in High Density TMA
Extended AMAN
• Extension of planning horizon to a minimum of 180-200 NM, up to and including ToD– Extension of existing Basic AMAN
• Coordination with all adjacent ATS sectors– Synchronisation to optimise network performance (including AF3)
• Sequencing techniques like “Time to Lose or Gain” and “Speed Advice” may be used• Expected future improvements
– Exchange of information will be based on SWIM services (AF5)– New operational methods for sequencing can be applied (point merge, TTA, TBS (AF2) etc)– Data from airborne FMS available in ground ATM systems through i4D (AF6)
• When combined with PBN that improves aircraft navigation performance– Provides more precise data for ATC planning– Allows pilots to fly their aircraft in the most optimum way and avoid delays
PBN in High Density TMAs
• RNP approaches with vertical guidance (RNP APCH with APV)– Lateral/Vertical navigation (LNAV/VNAV) and Localiser Performance with Vertical Guidance (LPV) minima
• RNP1 operations in high density TMAs• SIDs and STARs using RNP1 including Radius to Fix (RF) path terminator
• Advanced RNP– Connect FRA with RNP procedures in TMA
Content of AF 2Airport Integration and Throughput
Departure Management Synchronised with Pre- departure sequencing• Integrated DMAN and A-CDM
Departure Management integrating Surface Management Constraints• A-SMGCS Level 1&2 routing and DMAN taking into account airport constraints
• Integration with Flight Data Processing systems requires EFS
Time-Based Separation for Final Approach• Separation of aircraft in sequence on approach using time intervals instead of distance
• Controller support tools with safety nets needed
Automated Assistance to Controllers for Surface Movement Planning and Routing• A-SMGCS generates taxi routes automatically avoiding potential conflicts
Airport Safety Nets • Detecting and alerting of conflicting ATC clearances including aircraft and ground vehicles
• Aircraft and vehicle systems contributing to airport safety nets
Content of AF 3Flexible Airspace Management and Free Route
Airspace Management (ASM) and Advanced Flexible Use of Airspace (A-FUA)• Manage airspace reservations more flexible in response to airspace user requirements
• Airspace is managed dynamically with no fixed-route network
• Upgrade of ground ATM systems
Free Route• Includes both FRA and DCT at and above FL 310
• Integration with Flight Data Processing systems requires EFS
• Support tools in ATC systems like (MTCD, CDT, CORA, Conformance Monitoring, APW etc)
• Supported by NM systems (AF4) and SWIM (AF5)
Content of AF 4Network Collaborative Management
Enhanced Short Term ATFCM Measures (STAM)• Ensure close and efficient coordination between ATC and NM to manage flow before flights
enter a sector (including information from AMAN (AF1))
Collaborative NOP• Increased integration of Network Operations Plan (NOP) and Airport Operations Plan (AOP) (AF2)
• Support to FUA and FRA (AF3)
• Availability of shared operational planning and real-time data (AF5)
Calculated Take-off Time to Target times for ATFCM purposes• More sophisticated planning mechanisms focusing on the point of congestion
Automated Support for Traffic Complexity Assessment• Recorded analytical data from past operations and trajectory information for planned traffic to
be used for prediction of traffic complexity and overload situations
• Extended Flight Plan (EFPL) will enhance the quality of the assessment
Content of AF 5Initial System Wide Information Management (iSWIM)
Common infrastructure components• PENS is one example
SWIM Technical Infrastructure and Profiles• Stakeholder infrastructure components
• Service profiles (yellow, blue, purple etc)
Aeronautical Information Exchange
Meteorological information exchange
Cooperative network information exchange
Flight information exchange
Content of AF 6Initial Trajectory Information Sharing (i4D)
Target time and Trajectory Information Sharing (i4D) to improve ATM system performance• Air-ground data exchange
• ADS-C Extended Profile (EFP) included in ATN B2 services
• Upgrade of FDP systems in ground ATM systems
Data link capability is a prerequisite• Includes capability on-board aircraft and in ground ATM systems
Support to• Enhance AMAN functionality (AF 1)
• Automated support for Traffic Complexity Assessment (AF 3)
• Integration into NOP to support TTO/TTA (AF 4)
Support from• FDP to FDP trajectory exchange between ATS units and ATS units and NM using flight object
exchange (AF 5)
Sequence of INEA calls- Public Funds for ATM modernisation -
INEA Calls 2015 *)
INEA Call 2014
INEA Call 2016 *)
Subsequent INEA Call *)
No information yet
Call publicationSept. 2014
Call applications
dueMarch 2015
Call awardsJuly2015
Signatureprocedures
Sep-Dec. 2015
Monitoring/ reporting of awarded projectsfor the period of project/contract duration
*) To note:Current planning - All timelines tentative.Final dates and all decisions up to EC/INEA