Presentation is loading. Please wait.

Presentation is loading. Please wait.

12/10/2014 EUROPEAN COMMISSION ATM Master Plan Implementation Package 1 (IP1) CNS ATM Steering Group, UK CAA, 10.Feb.2009.

Similar presentations


Presentation on theme: "12/10/2014 EUROPEAN COMMISSION ATM Master Plan Implementation Package 1 (IP1) CNS ATM Steering Group, UK CAA, 10.Feb.2009."— Presentation transcript:

1 12/10/2014 EUROPEAN COMMISSION ATM Master Plan Implementation Package 1 (IP1) CNS ATM Steering Group, UK CAA, 10.Feb.2009

2 | 2 Sven Halle Eurocontrol meetings, January 2009 ATM Masterplan. Interoperability and standardisation Interoperability requires internationally agreed standards and norms. The SESAR development phase will deliver the technical ground for defining them. A standardisation roadmap shall be developed and kept up to date as a specific chapter of the ATM Master Plan. It will allow ATM stakeholders to anticipate and coordinate their efforts to ease the adoption of SESAR technical proposals as standards and norms by the relevant standardisation bodies.. Deployment The deployment phase of SESAR consists of a succession of three Implementation Packages coming with Operational Improvements. Implementation Packages deployment shall be supported by existing Community legal framework (Implementing Rules and Community Specifications). This will form a regulatory roadmap to be developed by the Commission and kept consistent with the ATM Master Plan.

3 | 3 Sven Halle Eurocontrol meetings, January 2009 IP1 main characteristics…  Essential as the baseline for SESAR deployment  It must be all about improving the current system and making it coherent through implementation of best practices, better coordination and the preparation for trajectory / time based operations: 1.Generating additional network capacity 2.Improving information sharing at network level 3.Improving environmental and energy performance 4.Improving Airport/Terminal operations efficiency and capacity 5.Improving En-Route efficiency and capacity

4 | 4 Sven Halle Eurocontrol meetings, January 2009 TECHNOLOGY IP1

5 | 5 Sven Halle Eurocontrol meetings, January 2009 Process of IP1 Refinement ”IP 3 - 2” Developments CND work programme, existing developments, R&D results Filtering of OIs from D5 = Existing IR, or linked to SES (IR & CS) regulation Or Mature/Complete or confidence in initial deployment within the timeframe Justifiable with clear criteria (i.e. endorsed business case, anticipated network benefits) No critical R&D needed (~end of V3) IP 1 Deployment Improve the current system Prepare for trajectory /time based operations mapping

6 | 6 Sven Halle Eurocontrol meetings, January 2009 Further IP1 Refinement IP 1 Deployment Improve the current system Prepare for trajectory /time based operations Time classification Geographical classification Stakeholder/Airspace User segmentation further parameters……

7 | 7 Sven Halle Eurocontrol meetings, January 2009 Airports and Aerodrome ATC The IP1 baseline builds on existing/mature elements and consists of the following items: 1.Implement Airport CDM 2.Implement ground movement control systems (A-SMGCS level 1+2) and safety nets (runway incursions) 3.Implement basic Departure Management Systems (DMAN) 4.Implement initial Airport data link (DCL, ATIS) 5.Implement environmentally sustainable (aircraft fuel use, noise and emissions) airport operations (CEM) 6.Runway usage optimisation (Mixed mode operations, parallel operations, low visibility procedures, crosswind separations, ILS areas, MLS operations, runway occupancy time reduction techniques, brake to vacate procedures) 7.On-Line NOP access

8 | 8 Sven Halle Eurocontrol meetings, January 2009 Aircraft Systems The IP1 baseline builds on existing/mature elements and consists of the following items: 1.Implement Precision Navigation (2-D RNP, precision approaches, optimised cruise-descend modes, GNSS approaches) 2.Upgrade the existing avionics and cockpit HMI to initial ATSAW applications based on ADS-B (in / out) 3.Upgrade ACAS display modes 4.Deployment of secure CPDLC to complement VHF voice communication

9 | 9 Sven Halle Eurocontrol meetings, January 2009 Aircraft Operations FOC The IP1 baseline builds on existing/mature elements and consists of the following items: 1.Implement Airport CDM 2.Reduce aircraft impact on the environment (Airport, En-route aircraft fuel and emissions) 3.System adaptation to common data model (starting with weather information systems)

10 | 10 Sven Halle Eurocontrol meetings, January 2009 TMA/En-Route Operations The IP1 baseline builds on existing/mature elements and consists of the following items: 1.Implement AMAN in high density TMAs and link AMAN to en-route systems 2.Improve airspace planning referred as AAMS (flexible sectorisation management) 3.Implement automated support for controllers (safety nets, conflict detection tools, flight conformance monitoring aids) 4.Deployment of secure CPDLC to complement voice communication 5.Implement in-trail procedures in oceanic airspace (ATSA-IP) 6.Implement TMA improvements (CCD/CDA, crosswind separations) 7.Network Operations Plan (NOP) access

11 | 11 Sven Halle Eurocontrol meetings, January 2009 SWIM The IP1 baseline builds on existing/mature elements and consists of the following items: 1.Set up the institutional framework for SWIM 2.Implement the initial SWIM network and connectivity based on the SWIM capability level 1 3.Start local SWIM interoperable services 4.Implement initial SWIM-enabled user applications (CDM, flight plan / flight data, aeronautical or weather information / briefing)

12 | 12 Sven Halle Eurocontrol meetings, January 2009 CNS Systems & Infrastructure The IP1 baseline builds on existing/mature elements and consists of the following items: 1.Deployment of AMHS for ground-ground data communications 2.Deployment of VHF (8.33kHz) above FL195 for voice communication and VDL2/ATN for initial data link 3.Implement MLAT systems and deploy ADS-B ground stations to support surveillance applications 4.Implementation of GNSS applications (APV/LPV) 5.Creation of a European IP backbone network and start implementation of VoIP (Voice over IP) for ground-ground voice communication

13 | 13 Sven Halle Eurocontrol meetings, January 2009 Airspace and Network Management 1 The IP1 baseline builds on existing/mature elements and consists of the following items: 1.Implement uniform airspace classification (7 ICAO classes below FL195) 2.Improve airspace planning (multiple route options, cross-border sectorisation, further routing options, optimum trajectories in defined airspace/time, etc.) referred as AAMS 3.Integrate military activity and traffic into network to optimise utilisation of available airspace 4.Implement data repositories (Airspace-ADR, Demand-DDR) to improve data consolidation and sharing 5.Improve and integrate capacity planning and ATFCM processes/tools (seamless planning, scenarios and simulation tools, CDM procedures, short-term ATFCM measures, critical events)....

14 | 14 Sven Halle Eurocontrol meetings, January 2009 Airspace and Network Management 2 The IP1 baseline builds on existing/mature elements and consists of the following items: 6. Improve flight plan filing (including through briefing facilities) and ensure FPL consistency for all users in a flexible airspace environment 7. Network performance assessment (including civil/military elements) 8. Implementation of the Network Operations Plan (NOP) 9. Integration of airports into the network management process

15 | 15 Sven Halle Eurocontrol meetings, January 2009 Aeronautical Information The IP1 baseline builds on existing/mature elements and consists of the following items: 1.Implement Aeronautical Information Management quality measures (CHAIN) 2.Move towards digital NOTAMs (common data model) and digital AIM 3.Integrate environmental requirements (CEM Collaborative Environmental Management) 4.Harmonise MET information management policy 5.Increase quality of weather forecasts 6.Integrate weather information in the ATM and AOC Systems 7.Deployment of weather information systems at Airports

16 | 16 Sven Halle Eurocontrol meetings, January 2009 IP1 baseline SESAR WP link

17 | 17 Sven Halle Eurocontrol meetings, January 2009 Implement initial SWIM network and start local SWIM interoperable services (SJU WP14) Information Management Network Management Airport Implement initial SWIM enabled user applications (CDM/ flight data, aeronautical or weather information (SJU WP14) Set up the institutional framework for SWIM (SJU WP14) Implement Aeronautical Information Management quality measures (CHAIN) (SJU WP8) Move towards digital NOTAM´s (SJU WP8) Harmonise MET information management policy (SJU WP8) Integrate weather information in the ATM systems (interoperability with AOC systems) (SJU WP10,11) Increase quality of weather forecasts and deploy airport MET information systems (SJU WP8) Improvements to the current system preparing for trajectory/ time based operations IP1 baseline Information Management Trajectory Management, Separation and Automation

18 | 18 Sven Halle Eurocontrol meetings, January 2009 Information Management Network Management Airport Implement advanced ASM system (AAMS) including scenario management and integrate into the European Airspace, Flow & Capacity planning (SJU WP 7, 13) Creation of Airspace data repository (SJU WP7, 13) Implement capacity planning tools and use CDM (including A-CDM) processes (SJU WP7,13) Update flight planning and facilitate flight plan filing (SJU WP 7, 13) Implement demand data & flight plan repositories and use them with demand & capacity what-if tools (SJU WP7, 13) Implementation of the NOP and creation of external interface (SJU WP7, 13) Creation of a European IP backbone network (SJU WP15) Deployment of AMHS for ground data Communications (SJU WP15) IP1 baseline Network Management Improvements to the current system preparing for trajectory/ time based operations Trajectory Management, Separation and Automation

19 | 19 Sven Halle Eurocontrol meetings, January 2009 Implement basic AMAN and link to En-Route systems and DMAN/SMAN (SJU WP5, 4, 6, 10) Implement AAMS dynamic sector management (SJU WP 7, 13, 4, 5) Information Management Network Management Airport Implement ground based Safety nets, Conflict detection tools and flight conformance monitoring aids (SJU WP4, 5, 10) Basic CDA implementation (SJU WP5, 4, 6) Implement precision navigation (2-D RNP, precision approaches optimised climb-cruise-descend modes, GNSS approaches) (SJU WP5, 4, 10, 9, 11) Upgrade existing Airborne avionics to initial ATSAW applications based on ADS-B (SJU WP9) Upgrade ACAS display modes (SJU WP9) Deployment of secure CPDLC to complement voice communication (SJU WP15, 4, 5) Deployment of 8,33 above FL 195 for voice communication and VDL2/ATN for initial data link (SJU WP 15, 10, 4) Implement MLAT systems and deploy ADS-B (1090) ground stations to support surveillance applications (SJU WP15, 10) IP1 baseline Trajectory Management & Automation Improvements to the current system preparing for trajectory/ time based operations Trajectory Management, Separation and Automation

20 | 20 Sven Halle Eurocontrol meetings, January 2009 Implement Airport CDM to improve operations in adverse conditions, turn-around, de-icing and pre-departure sequencing and use common data model (SJU WP6, 12) Implement Airport and runway capacity enhancements based on best practices (HIRO, ROT reduction, rapid exit taxiways, ILS sensitive & critical areas) (SJU WP6, 12) Implement basic Arrival / Departure / Surface Management systems AMAN,DMAN;SMAN (SJU WP 5, 6, 12, 10) Implement initial airport datalink services (SJU WP 12, 15) Implement environmentally sustainable airport operations ( local monitoring of environmental performance) CEM (SJU WP6, 12) Information Management Network Management Airport Implement A-SMGCS level 1 +2 (to improve airport surface management) and safety net systems (SJU WP 6, 12) Basic CDA implementation (SJU WP5, 6, 11, 9) Wake Vortex classifications based on best practices (SJU WP6, 12, 5) Implementation of GNSS applications (APV/LPV) (SJU WP9, 6, 5) IP1 baseline Airport Improvements to the current system preparing for trajectory/ time based operations Trajectory Management, Separation and Automation

21 | 21 Sven Halle Eurocontrol meetings, January 2009 Conclusions. Definition of IP1 & a consequent implementation plan is essential in order to secure timely implementation and to avoid stakeholder confusion on the required baseline for SESAR. As time is a crucial element, a simplified methodology for the classification of deployable IP1 elements is absolutely necessary:. Link to SJU work programme must be established in order to capture synergies, avoid gaps or duplications of work. After the endorsement of the ATM Masterplan by the Council, the refined definition of the Implementation Package 1 will require an update of the ATM Masterplan Existing IR, or linked to SES (IR & CS) regulation Or Mature/Complete or confidence in initial deployment within the timeframe Justifiable with clear criteria (i.e. endorsed business case, anticipated network benefits) No critical R&D needed (~end of V3)


Download ppt "12/10/2014 EUROPEAN COMMISSION ATM Master Plan Implementation Package 1 (IP1) CNS ATM Steering Group, UK CAA, 10.Feb.2009."

Similar presentations


Ads by Google