12/10/2014 european commission atm master plan implementation package 1 (ip1) cns atm steering...
TRANSCRIPT
11/04/23EUROPEANCOMMISSION
ATM Master PlanImplementation Package 1 (IP1)
CNS ATM Steering Group, UK CAA, 10.Feb.2009
| 2Sven Halle
Eurocontrol meetings, January 2009
ATM Masterplan
. Interoperability and standardisationInteroperability 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.. DeploymentThe 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.
| 3Sven 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 capacity2. Improving information sharing at network level3. Improving environmental and energy performance4. Improving Airport/Terminal operations efficiency and capacity5. Improving En-Route efficiency and capacity
| 4Sven Halle
Eurocontrol meetings, January 2009
TECHNOLOGY
2013 2020Date of Initial
Operating Capability
2017 20252009
2
3
4
1
5
0
AT
M
Ser
vic
e L
evel
Implementation
Available for Operations
Rolling out current Best Practices
(CDA, Flexible sectorisation, Continuous Climb Departure, Initial Data link, Automatic Flight Conformance Monitoring,
Basic Departure Management (DMAN), Ground Based Safety Nets, Use of Runway Occupancy Time (ROT) Reduction Techniques)
Implementation
R&D
Available for Operations
Preparing Trajectory based operations
Interactive rolling NOP, Manual UDPP
AMAN/DMAN integration
ATSAW in flight and on surface, ATSA-ITP
Improved Low Visibility Procedures
Implementation
R&D
Available for Operations
Implementing net-centric trajectory managementSWIM enabled NOP using RBT/SBTFull set of Complexity Management ToolsASPA S&M2D-PTC on Predefined RoutesAutomated Surface Movement Planning and RoutingAdjustment of Separation Based on Ground Wake Vortex detection
Implementation
R&D
Available for Operations
Achieving advanced automation in a shared trajectory environmentDynamic TMAs and Flexible Military structuresDynamic ATFM using RBTManagement Revision of RBT using DatalinkFull set of Advanced Controller tools using RBT/SBTASEP-ITP2D-PTC on User Preferred Trajectories3D-PTC on Predefined Routes
Implementation
R&D
Available for Operations
Extending operations with advanced separation modesDynamic Mobile Area, 3D-PTC User preferred trajectoriesASEP C&P, SVS in low visibility conditionsCompatibility between Airborne and Ground Safety nets
Implementation
R&D
Available for Operations
Accommodating full 4D trajectory managementbased on user preferred trajectoriesDynamic Sector shapesASEP WV spacing, ASAS Self separation4D-PTC
IP1
| 5Sven 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 thecurrent system
Prepare fortrajectory /time
based operationsmap
ping
| 6Sven Halle
Eurocontrol meetings, January 2009
Further IP1 Refinement
IP 1 Deployment
Improve thecurrent system
Prepare fortrajectory /time
based operations
Time classification
Geographical classification
Stakeholder/Airspace Usersegmentation
further parameters……
| 7Sven Halle
Eurocontrol meetings, January 2009
Airports and Aerodrome ATCThe 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
| 8Sven Halle
Eurocontrol meetings, January 2009
Aircraft SystemsThe 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
| 9Sven 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)
| 10Sven Halle
Eurocontrol meetings, January 2009
TMA/En-Route OperationsThe 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
| 11Sven Halle
Eurocontrol meetings, January 2009
SWIMThe 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)
| 12Sven Halle
Eurocontrol meetings, January 2009
CNS Systems & InfrastructureThe 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
| 13Sven Halle
Eurocontrol meetings, January 2009
Airspace and Network Management 1The 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)
....
| 14Sven Halle
Eurocontrol meetings, January 2009
Airspace and Network Management 2The 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
| 15Sven Halle
Eurocontrol meetings, January 2009
Aeronautical InformationThe 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
| 16Sven Halle
Eurocontrol meetings, January 2009
IP1 baseline SESAR WP link
(High-level)Target Concept and
Architecture Maintenance(B)
Master Plan Maintenance
(C)
SJU
ATM Network R&D Programme
Validation infrastructure Needs Management
(WP 3)
R&D Transversal Areas
(WP 16)
Networking Operation
En Route Operation
TMA Operation
Airport Operation
Information Management
SWIM technical
architecture
Aircraft Systems
F/WOCNetwork Information Management System
En-Route & Approach ATC Systems
Airport system
Non Avionic CNS System
WP 7 WP 5
WP 4 WP 6
WP 8 WP 14
WP 9
WP 11 WP 15 WP 13
WP 10 WP 12
Transversal Thread
Operational Thread SWIM Thread System Thread
Long-Term andInnovative
Research Programme(E)
| 17Sven Halle
Eurocontrol meetings, January 2009
Implement initial SWIM network and start localSWIM 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 anddeploy airport MET information systems (SJU WP8)
Improvements to the current system preparing for trajectory/ time based operations
IP1 baselineInformation Management
TrajectoryManagement,Separation and Automation
| 18Sven 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 baselineNetwork Management
Improvements to the current system preparing for trajectory/ time based operations
TrajectoryManagement,Separation and Automation
| 19Sven 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 baselineTrajectory Management & Automation
Improvements to the current system preparing for trajectory/ time based operations
TrajectoryManagement,Separation and Automation
| 20Sven Halle
Eurocontrol meetings, January 2009
Implement Airport CDM to improve operationsin adverse conditions, turn-around, de-icing and pre-departure sequencing and use common data model(SJU WP6, 12)
Implement Airport and runway capacity enhancementsbased on best practices (HIRO, ROT reduction, rapid exit taxiways, ILS sensitive & critical areas) (SJU WP6, 12)
Implement basic Arrival / Departure / SurfaceManagement systems AMAN,DMAN;SMAN (SJU WP 5, 6, 12, 10)
Implement initial airport datalink services (SJU WP 12, 15)
Implement environmentally sustainable airportoperations ( local monitoring of environmental performance) CEM (SJU WP6, 12)
Information Management
Network Management
Airport
Implement A-SMGCS level 1 +2 (to improve airportsurface management) and safety net systems (SJU WP 6, 12)
Basic CDA implementation (SJU WP5, 6, 11, 9)
Wake Vortex classificationsbased on best practices (SJU WP6, 12, 5)
Implementation of GNSS applications (APV/LPV) (SJU WP9, 6, 5)
IP1 baselineAirport
Improvements to the current system preparing for trajectory/ time based operations
TrajectoryManagement,Separation and Automation
| 21Sven 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)