From PCP to Common Project 1

Erki Must, European Commission, DG Move, E3

Web Seminar on SESAR deployment

28.04.2020

#PCPtoCP1

• SESAR deployment framework;

• Introducing Common Project 1;

• Main updates in Common Project 1;

• Next steps towards adoption of the CP1.

Topics covered

Common Project is not:

• A Financing program – Financing for deployment projects is provided by Connecting Europe Facility, managed by INEA in cooperation with SESAR Deployment Manager;

• A greatest hits of SESAR solutions – Common Project should only include solutions that require universal deployment. However, there are many more good and useful SESAR solutions.

What a Common Project is not?

43

AF1

Arrival Management extended to en-route airspace

AF2

Departure Management Synchronised with Pre-departure sequencing

Departure Management integrating Surface Management Constraints

Time-Based Separation for Final Approach

Automated Assistance to Controller for Surface Movement Planning and Routing

Airport Safety Nets

AF6

Initial Trajectory Information Sharing

AF5

Common infrastructure components

SWIM Technical Infrastructure, Specifications and Profiles

Aeronautical information exchange

Meteorological information exchange

Cooperative network information exchange

Flight information exchange

AF4

Enhanced Short Term ATFCM Measures

Collaborative NOP

Calculated Take-off Time to Target Times for ATFCM purposes

Automated Support for Traffic Complexity Assessment

AF3

Airspace Management and Advanced Flexible Use of Airspace

Free RouteEnhanced Terminal Airspace using RNP-based operations

The first agreement – Pilot Common Project

• Review clause – PCP 1 regulation foresaw a review to take into account the firstexperiences;

• ECA audit – Special Report 11/2019 invites the Commission to improve the focus and to reinforce the effectiveness of the common projects;

Reasons for the PCP Review 1/2

• Council – invited the Commission to review the PCP in the light of the European Court of Auditors' recommendations and to explore the means for improving the effectiveness of common projects within the SESAR innovation cycle, while maintaining the momentum already initiated by the Pilot Common Project;

• On the spot visits – EC and INEA have carried out more than 20 on the spot visits to see the deployment in practice. This has lead to increased situational awareness and proposals for PCP review.

Reasons for the PCP Review 2/2

• PCP includes certain solutions that are not mature for deployment;

• Not all the solutions included into the PCP have passed the V4 maturity level;

• Certain deployment deadlines are no longer realistic;

• Some solutions included into PCP do not provide network benefit;

• There is a weak link between the PCP and the Performance Plans;

• Several solutions provide only local benefits.

PCP review conclusions

The proposed content of the Common Project 1

• AMAN/DMAN integration for 9 airports added as new Sub-AF coming as aproposal elaborated by SJU;

• Enhanced Terminal Airspace using RNP-based operations excluded due toentry into force of a dedicated EU implementing regulation;

AF 1 - Extended Arrival Management, Performance Based Navigation and Integrated AMAN/DMAN in the High-Density Terminal Maneuvering Areas

• Departure Management Synchronised with Pre-departure sequencingdeployment deadline prolonged from 1 January 2021 to 1 January 2022;

• Airport Safety Nets deployment deadline prolonged from 1 January 2021 to1 January 2024;

• Departure Management integrating Surface Management Constraints andTime-Based Separation for Final Approach removed from AF2 due tomaturity and synchronization issues;

• Airport Operations Plan added as new Sub-AF proposed by the SJU andsupported by the operational partners.

AF 2 - Airport Integration and Throughput

• FRA implementation split into 2 phases:

• Initial FRA to be implemented with time limitations and airspace constraints by 1January 2022

• Final FRA including Cross-Border dimension and TMAs connectivity by 1 January 2025.

AF 3 - Flexible Airspace Management and Free Route Airspace

• Calculated Take-off Time to Target Times for ATFCM purposes removedfrom AF4 due to maturity issues;

• More specified list of affected airports;

• The target time in planning is in use but is no longer obligatory due to thenon-validation of the use of target time in execution;

• Enhanced integration of Airports with Network added as new Sub-AF with adeployment deadline by the end of 2027.

AF 4 - Network Collaborative Management

• SWIM Yellow and Blue Profiles split into different Sub-AFs to betterdistinguish the system requirements and the implementation target dates:2025 for the Yellow Profile and 2027 for the Blue Profile;

• Industrialisation target date set for the SWIM Blue Profile: 2023

• New implementation target date given to SWIM Blue Profile: 2027

AF 5 - System Wide Information Management (SWIM)

• „Downlink of the trajectory data to the ground systems“ and „The distributionon the ground together with the use of the data by Network Manager“, splitinto two different Sub-AFs;

• Industrialisation target date given for the use and distribution of the dataon the ground: 2023;

• Deployment target date is prolonged to the end of 2027.

AF 6 - Initial Trajectory Information Sharing

Industrialisation target date – the end of the standardisation and certification processes;

Implementation target date - readiness for procurement, installation and putting into service.

• Industrialisation target date enables to verify if the specific solution has reached a sufficient maturity level (at least V4) so as its deployment is feasible by the end of 2027;

• The Industrialisation Maturity Gate mechanism is being developed. It will involve the inputs of EASA, EUROCAE, ANSPs, airspace users and other relevant stakeholders.

The concept of „Industralisation maturity gate“

OperationsPerforming and monitoring

InnovationCycle

Single European SkyRegulatory Framework

Industrialization Phase

Development Phase

Research, development, validation, industrialization

Definition Phase

Exploring, defining and Planning

Deployment PhaseSynchronisation and investments

Air Navigation Service Providers

Airport Operators

MET Providers

Airspace Users

Military Authorities

Network Manager

v4

v3 v5

R&D, Industrialisation and Implementation phases

55

AF

1A

F2

AF

4A

F3

56

GANTT Chart for the PCP (AF1, AF2, AF3, AF4)

2020 2021 2022 2023 2024 2025 2026 2027

Sub-AF 1.1 – Arrival Management Extended to en-route Airspace

Sub-AF 1.2 - Enhanced Terminal Airspace using RNP-based Operations

Sub-AF 2.1

Sub-AF 2.2

Sub-AF 2.3 – Time-Based Separation for Final Approach

Sub-AF 4.1 - Enhanced STAM

Sub-AF 4.2 - Collaborative NOP

Sub-AF 4.3

Sub-AF 4.4

Sub-AF 3.1 - ASM and Advanced FUA

Sub-AF 3.2 - Free Route

Departure Management Synchronised with Pre-departure sequencing

Departure Management integrating Surface Management Constraints

Sub-AF 2.4 - Automated Assistance to Controller for Surface Movement Planning and Routing

Sub-AF 2.5 Airport Safety Nets

*No specific target date

Calculated Take-off Time to Target Times for ATFCM purposes

Automated Support for Traffic Complexity Assessment

AF

1A

F2

AF

4A

F3

57

GANTT Chart for the new CP1 (AF1, AF2, AF3, AF4)

2020 2021 2022 2023 2024 2025 2026 2027

Sub-AF 1.1 – Arrival Management Extended to en-route Airspace

Sub-AF 1.2 - Enhanced Terminal Airspace using RNP-based Operations

Sub-AF 1.3 - AMAN/DMAN Integration

Sub-AF 2.1 - Departure Management Synchronised with Pre-departure sequencing

Sub-AF 2.2 - Airport Operations Plan

Sub-AF 2.3 - Airport Safety Nets

Sub-AF 4.1 - Enhanced Short Term ATFCM Measures

Sub-AF 4.2 - Collaborative NOP

Sub-AF 4.3 - Automated Support for Traffic Complexity Assessment

Sub-AF 4.4 Enhanced Integrations of Airports with Network

Sub-AF 3.1 - Airspace Management and Advanced FUA

Sub-AF 3.2 - Free Route

Initial Free Route Final Free Route

AF

5A

F6

2020 2021 2022 2023 2024 2025 2026 2027

58

GANTT Chart for the PCP (AF5 and AF6)

Sub-AF 5.1 Common Infrastructure Components

Sub-AF 5.2 SWIM Infrastructure and Profiles

Sub-AF 5.3 SWIM Aeronautical Information Exchange

Sub-AF 5.4 SWIM Meteorological Information Exchange

Sub-AF 5.5 SWIM Cooperative Network Information Exchange

Sub-AF 5.6 SWIM Flights Information Exchange

Sub-AF 6.1 Initial Trajectory Information Sh ground

Target Implementation dates

airborne

59

GANTT Chart for the new CP1 (AF5 and AF6)

Industrialisation target dates

Target deployment dates

AF

5A

F6

2020 2021 2022 2023 2024 2025 2026 2027

Sub-AF 5.1 Common Infrastructure Components

Sub-AF 5.2 SWIM Technical Infrastructure, Specifications and Profiles (Yellow Profile)

Sub-AF 5.3 Aeronautical Information Exchange

Sub-AF 5.4 Meteorological Information Exchange

Sub-AF 5.5 Cooperative Network Information Exchange

Sub-AF 5.6 Flight Object Information Exchange (Yellow Profile)

Sub-AF 5.7 SWIM Technical Infrastrcture, Specifications and Profiles (Blue Profile)

Sub-AF 5.8 Flight Object Information Exchange (Blue Profile)

Sub-AF 6.1 Initial Trajectory Information Sharing

Sub-AF 6.2 Network Manager Trajectory Information Enhancement and Ground Distribution

CP 1 – CBA results

• Internal Service Consultation

• May – Stakeholder conslutation in line with the Article 5(2), (3), (4) of Reg. 409/2013;

• From June – Better regulation portal;

• June SSC – discussion on the CP 1 legal proposal;

• November SSC – decision on the CP1 legal proposal;

• December – approval by the European Commission.

Further timeline

Thank you!erki.must@ec.euroopa.eu

© European Union 2020

Unless otherwise noted the reuse of this presentation is authorised under the CC BY 4.0 license. For any use or reproduction of elements that are not owned by the EU, permission may need to be sought directly from the respective right holders.

Slide xx: element concerned, source: e.g. Fotolia.com; Slide xx: element concerned, source: e.g. iStock.com