2020 Local Single Sky Implementation (LSSIP) event - 20 October 2020 Supporting European Aviation
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
2020 Local Single Sky Supporting
Implementation (LSSIP) event European
Aviation
20 October 2020
1
Supporting
European
Aviation
2020 LSSIP Event
ATM Master Plan Level 3 - Implementation Plan 2020
Igor Marcetic – NMD/INF/PAS
Presentation Outline
• Context of the Implementation Plan 2020
• Overview of the Changes in the Structure & Content
• Changes to Implementation Objectives
• Reminder-useful tips
• Special case for LSSIP - objective NAV10
• Questions
3
Context of the Plan 2020 – drafting and approval
PJ20. WP4
4
Context of the Plan 2020 – use of it & drivers for the changes
5
Context of the L3 Plan 2020 – ATM Concept Lifecycle Phases
6
Context of the Plan 2020 – Geographical scope
7
Context of the Plan 2020 – two files
Printed book Only electronic PDF
Distributed to FP by post Only available online
Available online too
High level info Detailed info for LSSIP work
Not very useful for LSSIP DB work Recommended for use during
work in LSSIP DB.
8
If you would like a paper copy, ask national FP.
Changes in the Structure & Content - Printed book
Essential Operational Changes (EOC)
EOCs are established by European ATM Master Plan Executive View
9
Changes in Operational View - Printed book
10Changes in Deployment View - Printed book
11Implementation Objectives – Changes Overview
FCM09 - not in LSSIP DB, only NM actions
FCM08 (eFPL) – removed from the Plan Remaining for ICAO ASBU:
1. AOM21.1
ATC21 (ADS-B/WAM) – New ‘’Initial’’ objective 2. ATC02.2
(not in LSSIP yet) 3. ATC16
4. FCM01
5. ITY-COTR
FP
One less objective to be monitored in LSSIP 2020 compared to LSSIP 2019.
12Implementation Objectives – Detailed Changes
FCM08 - Objective on Extended Flight Plan. Addressing SESAR Sol #37.
• e-FPL functionality/Specs described in objective FCM08 are incompatible with the new CP1
Regulation AF5 Sub-AF 5.1.6 FF-ICE Release 1 Services.
Removed
• As CP1 Reg. was developed in parallel with Plan 2020, it became obvious that asking
stakeholders to continue with FCM08 implementation will not support compliance with CP1
Reg. (about to be published).
• Thus, new objective will be created in 2021, addressing the implementation of e-FPL in line
with the ICAO FF-ICE (Flight and Flow information for a Collaborative Environment) and in
compliance with CP1 Reg. Sub-AF 5.1.6
FP
One less objective to be monitored in LSSIP 2020 compared to LSSIP 2019.
13Implementation Objectives – Detailed Changes
SLoA FCM03-ASP06 Automatically provide AFP message for change of route. Description
of this SLoA changed to align with the definition in the IFPS User Manual (ed. June 2020) –
modification of the ‘’triggering events’’ – change to be implemented “at the best convenience”);
Old text
An AFP message shall be sent to IFPS automatically in ADEXP format by an ATC centre when a
change of route where the exit point from the flight data processing area (FDPA) has changed.”
New text
“AFP for a change of route where the exit coordination point from the Air Traffic Control Unit (ATCU)
has changed AND the next downstream ATCU is new when compared to the last flight plan data.”
1. If already ‘’Completed’’/Implemented, no need to “reopen” the objective BUT change to the SLoA should
FP
be considered in the future releases of the system.
2. If implementation is ongoing (new ATM system), change to the SLoA should not impact progress (BUT
implementation shall be based on the latest specs).
14Implementation Objectives – Detailed Changes
Alignment of FOC dates in the existing Implementation Objectives
To ensure alignment with the all relevant regulations and plans in the context of implementation
planning in European ATM.
To support harmonised and single implementation monitoring across ECAC+, as far as practical.
The criteria for changing to NEW FOC date in Plan 2020 are as follows, starting with the highest priority
first:
1. Objective is regulated by IR (Regulation), NEW FOC = IR date
2. Objective has SESAR Deployment Program Family, NEW FOC = DP Family Date.
3. Objective is:
I. not Regulated,
II. no reference to DP Family,
III. is not LOCAL objective, and
IV. has SESAR SOL reference,
• NEW FOC = Deployment Scenario Date as specified in MPL1.
4. Objective is:
I. not Regulated,
II. no reference to DP Family,
III. no reference to SESAR SOL,
IV. with SESAR SOL but SOL is not identified in any DS.
• NEW FOC = Open end i.e. no date, unless there is a previous EUROCONTROL PC commitment.
15Implementation Objectives – Detailed Changes
FOC date delayed significantly (except AOP11 which is brought forward):
Obj. ID Objective Title Old FOC New FOC Date
Date Plan 2020
AOM19. ASM Support Tools to Support Advanced FUA 31/12/2018 01/01/2022
1
AOP04.1 Advanced Surface Movement Guidance and Control System A-SMGCS Surveillance 31/12/2011 01/01/2021
AOP04.2 Advanced Surface Movement Guidance and Control System (A-SMGCS) Runway Monitoring and Conflict 31/12/2017 01/01/2021
Alerting (RMCA)
AOP05 Airport Collaborative Decision Making 31/12/2016 01/01/2021
AOP11 Initial Airport Operations Plan 31/12/2021 01/01/2021
ATC02.8 Ground-Based Safety Nets 31/12/2016 01/01/2022
ATC17 Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer 31/12/2018 01/01/2022
COM12 New Pan-European Network Service (NewPENS) 33 ANSPs: 01/01/2025
31-12-2020
Other STKs:
31-12-2024
FCM03 Collaborative Flight Planning 31/12/2017 01/01/2022
INF07 Electronic Terrain and Obstacle Data (eTOD) 31/05/2018 01/01/2019
FP
If you had a status ‘’Late’’ for these objectives, you shall change it in LSSIP 2020.
Adopted date format convention from SESAR Deployment Program.
16Implementation Objectives – Detailed Changes
FOC date minor editorial change by 1 day
Obj. ID Objective Title Old FOC New FOC Date
Date Plan 2020
AOM19.2 ASM Management of Real-Time Airspace Data 31/12/2021 01/01/2022
AOM19.3 Full Rolling ASM/ATFCM Process and ASM Information Sharing 31/12/2021 01/01/2022
AOM19.4 Management of Pre-defined Airspace Configurations 31/12/2021 01/01/2022
AOM21.2 Free Route Airspace 31/12/2021 01/01/2022
AOP10 Time-Based Separation 31/12/2023 01/01/2024
AOP12 Improve Runway and Airfield Safety with Conflicting ATC Clearances (CATC) Detection and 31/12/2020 01/01/2021
Conformance Monitoring Alerts for Controllers (CMAC)
AOP13 Automated Assistance to Controller for Surface Movement Planning and Routing 31/12/2023 01/01/2024
ATC07.1 AMAN Tools and Procedures 31/12/2019 01/01/2020
ATC12.1 Automated Support for Conflict Detection, Resolution Support Information and Conformance 31/12/2021 01/01/2022
Monitoring
ATC15.2 Arrival Management Extended to En-route Airspace 31/12/2023 01/01/2024
COM11.1 Voice over Internet Protocol (VoIP) in En-Route 31/12/2021 01/01/2022
FCM04.2 Short Term ATFCM Measures (STAM) - Phase 2 31/12/2021 01/01/2022
FCM05 Interactive Rolling NOP 31/12/2021 01/01/2022
FCM06 Traffic Complexity Assessment 31/12/2021 01/01/2022
FCM07 CTOT to TTA for ATFCM purposes 31/12/2021 01/01/2022
INF08.1 Information Exchanges using the SWIM Yellow TI Profile 31/12/2024 01/01/2025
INF08.2 Information Exchanges using the SWIM Blue TI Profile Nil (initial) 01/01/2027
Adopted date format convention from SESAR Deployment Program.
17Implementation Objectives – Detailed Changes
Adjustment of Applicability Area based on LSSIP 2019 reporting results
Those who were part of Applicability Area in Plan 2019 and reported ‘’Not Applicable’’ for an
objective, were taken out of the Applicability Area in Plan 2020
Those who were not part of Applicability Area in Plan 2019 and reported any implementation
status except N/A, were added to the Applicability Area in Plan 2020
FP
Much cleaner and consistent presentation of data in the L3 Report, LSSIP Map Tool and in LSSIP DB.
18Implementation Objectives – Summary of all Changes
• Supporting PDF document to facilitate work of all FPs/CPs in LSSIP 2020 cycle.
• This list contains all Implementation Objectives found in MPL3 Plan 2020 with the
indicated changes compared to Plan 2019
• Available at
• EUROCONTROL website https://www.eurocontrol.int/sites/default/files/2020-
07/eurocontrol-mpl3-details-changes-objectives-plan2020-vs-plan2019.pdf
• LSSIP Share Point Hyperlink: LSSIP Share Point MPL3 2020 Annexes
19Reminder: Engineering View – Technical Annex of the Objectives
Your view! - Expert level.
Important for LSSIP FP/CP reporting is ENGINEERING VIEW – Technical Annex
Only in Engineering View, you can find:
• full description of SLoA,
• its finalisation criteria, and
• explanatory notes.
It can be accessed:
• in LSSIP DB
• on LSSIP Share Point (PDF file) - Hyperlink: LSSIP Share Point MPL3 2020 Annexes
• On EUROCONTROL Website - https://www.eurocontrol.int/publication/european-
atm-master-plan-implementation-plan-level-3
Engineering view is not available as printed hard copy document.
FP
When reporting, do not rely only on SLoA Title in LSSIP DB. It may not be clear/comprehensive enough.
20Reminder: Engineering View - Technical Annex of the Objectives
21Reminder: Engineering View - Technical Annex in LSSIP DB
22Reminder: Engineering View - Technical Annex in LSSIP SharePoint
23Reminder – All documents on EUROCONTROL Website
24Supporting
European
Aviation
NAV10 in LSSIP vs PBN Map Tool
Avoid unnecessary double reporting for NAV10
Igor Marcetic – NMD/INF/PASPBN Map Tool Basics
1. There is a newly launched Eurocontrol PBN Portal https://pbnportal.eu/epbn/home/home.html
and Eurocontrol PBN Map Tool https://ext.eurocontrol.int/airport_map_tool
2. PBN Map Tool
a) Shows the deployment of PBN instrument approach procedures
b) Includes PCP and PBN IR requirements
c) Is available via EUROCONTROL ‘’OneSky Online tools’’
d) Covers about 1500 RWY ends of 760 Airports/Heliports in ECAC area
e) Covers 17 approach types/minima. Which is 14 more than objective NAV10
f) Does not include Israel and Morocco (yet)
g) Does not include SID/STAR (yet). Thus, it does not cover NAV03.1 and NAV03.2 (yet)
3. Information source and update
a) The implementation status info is obtained from AIPs every AIRAC cycle.
b) The plans are collected from: SBAS channel allocation for LPV, stakeholder groups
RAISG/NSG/ICAO EUR PBN TF, the PBN Transition Plans submitted by ANSPs to the
NM.
c) “Plans” are introduced as they come. No cyclical update, but reviewed at least once a
year.
We reuse the data available at EUROCONTROL to reduce reporting workload on LSSIP FP, as far as practical.
26PBN Map Tool in Details
27PBN Map Tool in Details
28PBN Map Tool in Details
29Coverage of NAV10 SLoAs in PBN Map Tool
= Yes, included in PBN Map Tool = Not included in PBN Map Tool
NAV10-REG01 Apply EASA material to local national regulatory activities FP to continue reporting. 66% completed.
NAV10-REG02 Verify the transition plan for PBN in ANS provision No need for FP to report. Available in NAV03.1, NAV03.2, NAV12.
NAV10-ASP01 Design and Publish RNP approach procedures to LNAV, LNAV/VNAV and LPV
No need for FP to report.
minima to RWYs served by precision approach
NAV10-ASP03 Develop National safety case for RNP approach down to LNAV/VNAV and LPV
minima No need for FP to report. Generic change management activity.
NAV10-ASP04 Publish in AIPs all coordinates data in WGS-84 in accordance with ICAO Annex 15
requirements and Article 14 of Regulation (EU) No 73/2010 Continue reporting. 85% completed.
NAV10-ASP05 Design and Publish RNP approach procedures to LNAV, LNAV/VNAV and LPV
No need for FP to report.
minima to RWYs without precision approach
NAV10-ASP06 Design and Publish RNP non-precision (NPA) approach procedures to LNAV minima No need for FP to report.
NAV10-ASP07 Establish the transition plan for PBN in ANS provision No need for FP to report. Available in NAV03.1, NAV03.2, NAV12.
NAV10-ASP08 At PCP airport, Design and Publish RNP approach procedures to LNAV,
LNAV/VNAV and LPV minima to RWYs without precision approach No need for FP to report.
NAV10-ASP09 At PCP airport, Design and Publish RNP non-precision (NPA) approach procedures
to LNAV minima No need for FP to report.
NAV10-USE01 Equip aircraft with systems approved for RNP approach down to LNAV/VNAV and/or Not in LSSIP. Equipage level available at CNS Dashboard
LPV minima operations
NAV10-USE02 Get airworthiness certification and operational approval Not in LSSIP. Equipage level available at CNS Dashboard
30What to do in LSSIP 2020?
Keep objective NAV10 in MPL3 Plan/Report and LSSIP DB due to: completeness of ATM MP L3 &
National LSSIP, use in ICAO ASBU Report & reference to DP.
LSSIP FPs, except Israel and Morocco, to stop reporting on 8 SLoAs, but continue reporting on the
following 2 SLoAs
SLoA NAV10-REG01
SLoA NAV10-ASP04
FP
LSSIP FPs may consult PBN Map Tool to get detailed PBN APCH information
EUROCONTROL will transfer LNAV, LNAV/VNAV, and LPV information from PBN Map Tool to the
NAV10 SLoAs concerned in LSSIP DB. For the LSSIP airports of the states.
Deadline for EUROCONTROL to transfer information into LSSIP DB is mid January 2021.
3132
33
You can also read
