1 / 22

WP1 PRESENTATION

WP1 PRESENTATION. Agenda. CDM WP1 & WP2 Presentation 09:00 (all) WP1 : Analysis of Malpensa main Operations Result List of possible Improvements

judah-william
Télécharger la présentation

WP1 PRESENTATION

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP1 PRESENTATION

  2. Agenda CDM WP1 & WP2 Presentation • 09:00 (all) WP1 : Analysis of Malpensa main Operations Result List of possible Improvements Discussion Coffee Break • 10:45 (all) WP2 : Airport CDM Projects Status List of possible Improvements Discussion • 14:00 (small group) : Malpensa Specific Objectives

  3. WP3 - IMPLEMENTATION PHASE to be specified WP4 - TRIALS AND EVALUATION to be specified Current Project Status Malpensa PROJECT STATUS WP1 - ANALYSIS OF MALPENSA OPERATIONS 03.02.2003 26.05.2003 WP2 - IDENTIFICATION AND SELECTION OF COMMON IMPROVEMENTS 27.05.2003 30.09.2003 Steering Comittee ASSESSMENT / DECISION

  4. ENAV • Aircraft Operators (AOC, Alitalia, Volare, Lauda Air) • Ground Handling Services (SEA Handling, ATA Handling) • Airport (SEA) • Cargo (ALHA, MLE) • Eurocontrol Experimental Centre • CFMU ENAV ACC / APP ENAV TWR ENAV FMP CFMU CEE CDM PROJECT AT MALPENSA AIRPORT Alitalia SEA H ALHA AOC S E A MLE Volare Lauda ATA H Project Partners

  5. Project Phases Phase 1 : Phase 2Phase 3Phase 4 Design and implement processes and information systems Identify and Identify the gaps Measure, Analyse the state of operation at Malpensa select common between the actual follow up, situation and the correct Improvement Targets common targets . Measure the results obtained evaluating the changes made according to the defined parameters . Definitive establishment of the airport model . Design, implement the information systems , the technical and the organisational supports . Establish a set of parameters, including a method to check and verify that the pursued improvements are met . Identify and analyse the possible objectives and improvements to realise in the map of processes . Detect individual and global operative improvements and the decisions to take in order to implement them . Analyse the current state of operations in Malpensa’s airport from the strategic to the tactical phase . Analyse operational processes, agents and decision drivers involved in the operations . Detect the missing information necessary to meet the desired objectives (information gaps) . Define the information systems, the technical and the organisational supports required. WP1 leads to build a common understanding of the actual situation and the assessment of potential improvements in the process and information flows map

  6. Analysis of Operations at Malpensa airport Identification and Selection of common improvements Airport Collaboration Map Improvements Areas Interviews / Observations Available Documents Analysis of the Gaps Refining Proposals Airport Authorities AOs ATC Measurements Statistics CDM Gaps Airport Slots ATFM Handling Operations Assessing their potential Available data Overall Process

  7. Business model of operations at Malpensa airport • Analysis of coordination processes between actors • Analysis of information flows between processes (automatic and non-automatic) • Time Estimates Terminology • Analysis of the process for updating time estimates • Analysis of information systems used • Analysis of automatic links Phase 1 Approach Analyse the state of operations at MALPENSA Airport • Project launch • Project scope • Analysis of operations • Consolidation • Final presentation • Final report 03/02/2003 1 week 11 weeks 2 weeks 3 weeks 26/05/03

  8. Interviews Airport Authorities Airport Coordination SEA ENAV (TWR) • Planning of traffic (strategic, pre-tactical) and planning of the daily traffic, • Stand and Gate planning and allocation processes and systems, • Emergency and crisis processes and systems, • Information flows with other partners (CFMU, Airlines, and Handlers), • Time estimates and data issued for each process. • Etc ... • Departure and arrival sequence planning and management processes and systems, • Information flows during the departure and arrival process with other partners (CFMU, Airlines, Airport and Handlers), • Ground traffic control and apron control process and systems, • Time estimates and data issued for each processes. • Etc ... Collaborative Processes • De-icing • SEA / ENAV Apron Management • Alitalia / SEA Handling Hub Control Center • Crisis Committee CDM project initial objectives : to analyse the current state of operations in MALPENSA airport from the strategic to the tactical phase • Planning and scheduling processes (aircraft, crew …), • Departure / arrival processes (check-in, baggage processing, catering, boarding …), • Operations control and dispatch processes (daily operations control, decision making process, needed data and time estimates); , • Major information flow between the airlines and the other partners (Airport, Handlers, ATC and the CFMU), • Time estimates and data issued and received for each process. • Etc ... • Aircraft servicing processes (fueling, catering management), • Baggage, cargo and mail handling processes, • Information flows between SEA Handling / ATA Handling and the other partners (Airlines, Airport, ATC, the CFMU), • Time estimates and data issued and updated for each process • Etc … Aircraft Operators Ground Handling Services

  9. CFMU ENAV FMP ENAV ACC ENAV TWR (1) Pre-tactical planning (6) En route operations (tactical phase) (4) Pre-tactical planning (8) Start up clearance delivery (2) FP management (5) Operations management (tactical phase) (7) Approach operations (tactical phase) (9) Push back & taxi clearance deliveries Ground control (3) Operations management (slots and regulations management) Alitalia SEA (13) Airport resources planning (strategic phase) (17) Flight planning & operations dispatching (pre-tactical & tactical phases) (10) Airport control (ARR & DEP) Airport Coordinator ATA Handling (11) Airport slots planning (strategic phase) (14) Airport resources planning (pre-tactical phase) (27) Resources planning (strategic & pre-tactical phases) (18) Hub operations management (tactical phase) (12) Airport slots management (tactical phase) (15) Airport resources management (tactical phase) (28) Resources management (tactical phase) (19) Fleet & crew operations management (tactical phase) (16) Messages & data management (tactical phase) (29) Handling activities (tactical phase) SEA Handling (24) Resources planning (strategic & pre-tactical phases) Lauda Air Volare (22) Flight planning & operations dispatching (pre-tactical & tactical phases) (20) Flight planning & operations dispatching (pre-tactical & tactical phases) (25) Resources management (tactical phase) (21) Operations management (tactical phase) (23) Operations management (tactical phase) (26) Handling activities (tactical phase) Business Processes Identification • A model of each of those processes has been established, • The coordination processes between actors have been identified and analysed, • Information flows between the processes have been identified and analysed.

  10. Airport General Information Flows CFMU delays A/C daily rotations FLICS GIRO FPs & CFMU messages IFPS CASA / TACT Flight data FPs & CFMU messages ARCO Alitalia flight data for handling FPs Flight data for handling LIDO PEGASO Other AO DCS FPs, CFMU data, NOTAM & SIGMET AOIS Flight data for Stands& Gates allocation Flight data, MVT & LDM Flight data GAPS FPs MVT & LDM Allocation results BDV FDP NET 2000 / TVCC Stands Flight data ENAV flight data Boarding / Pre-boarding status DIGIN Flight data for buses management ENAV flight data Baggage data RFD SGB Buses data ADAM & EVE Baggage data Flight data for baggage management Baggage data Baggage data RIBAG SIBAG BHD Baggage data

  11. Information Analysis CFMU information arrival flights 24-02 MXP 24-02-03 8h00 9h14

  12. TWR Increase safety Maximisethroughput Aircraft Operators Achieve Fleet Punctuality (network) Achieve Departure Punctuality Airport ARR & DEP Punctuality Optimum use of resources Handling Agents Achieve Departure punctuality Respect Turnaround Time ATFM CTOT Compliance avoid sector overloading Strategic Objectives

  13. Improving the Quality of Data [reliability, accuracy, predictability, timeliness] and information distribution Monitoring & Control Post Operations Evaluation “Share Good and Bad Experiences” Synchronise Operations Establish Collaborative Procedures Identifying Objectives Punctuality (On Time Performance) is the most important factor of satisfaction for airport customers

  14. Identifying Objectives Improving the Quality of Service / Data [reliability, accuracy, predictability, timeliness] and information distribution Be more TRANSPARENT Monitoring & Control Post Operations Evaluation “Share Good and Bad Experiences” Change your HABITS AIBT = ALDT + 10’ Link ARR & DEP Discuss by E-mail The earlier the better ! Punctuality (On Time Performance) is the most important factor of satisfaction for airport customers MOVE TO A COMMON OBJECTIVE “At Malpensa the Airport is the SUN ” Higher level of AUTOMATION Share your DATA in time Automation of FMO & TMO Automation of AOBT input Make Correct & Stable Decisions Synchronise Operations Establish Collaborative Procedures

  15. Preliminary Assessment • No shortage of data available but some data are not shared or automatically available through the BDV ELDT update, RWY configuration, RWY closure information, ETOT, CFMU slots update….

  16. Preliminary Assessment • Some data/events that do not exist for the moment could be helpful for enhanced collaboration between partners: Actual Aircraft Ready Time, Expected Taxi-Out Period, Estimated First Clearance Delivery Time ...

  17. Preliminary Assessment • Data Quality regarding Arrival Times could be enhanced, • Special emphasis could be put on improving information about Departure times • Information streams between arrival and departure information could be distributed to all the airport partners

  18. Preliminary Assessment • Collaboration is effective and efficient at Malpensa between partners but improvements can be performed to take into account partners constraints : Collaborative departure sequence, AOs preferences & priorities, Earlier recovery from disruption ...

  19. Preliminary Assessment • To achieve the CDM objectives, an airport information system should be easily accessible by each partner in Malpensa.

  20. Initial Proposals for Change 1. CFMU data (slots and revisions), FMO & TMO events and MVT data (ALDT, AOBT, ATOT) could be automatically input into the BDV 2. CFMU slots for arriving flights could be distributed to airport via the BDV. FSA departure messages from outbound stations could supplement MVT messages 3. CFMU could be provided with reliable ETOTs 4. Better ELDTs could be distributed earlier to airport users (handling agents, airlines, etc.) especially when stacks are implemented with a limited time horizon that would take into account peak hours effects 5. Better ETOTs could be provided by implementing a flexible and reliable taxi-out period with a limited time horizon that would take into account peak hours effects (queues), RWY / stand distance, etc. 6. Better EOBTs could be distributed to users: 3 minutes accuracy Vs 25 minutes time horizon through extensive cooperation (TOBT?) 7. Ready to move status (Airline / Handling) could be published

  21. Initial Proposals for Change 08. Real-time Information about stacks (implementation, expected duration), airport conditions (RWY configuration, RWY closure & expected durations), icing conditions, information about disruption... could be distributed to all the airport partners 09. Post-Operations Evaluation Reports could be made aware to all according to KPIs to specify 10. Push Back Sequence as known in the TWR could be delivered to the airport partners 11. Arriving and Departing information could be linked (for better Traffic Monitoring) 12. Need for accurate Information about flights (centralise the correction of erroneous flight information messages and the correspondence between IATA and ICAO flight codes; deliver those data to all the airport partners, etc.) 13. Coordination (new procedures) between the airport partners could be achieved (airline preferences, passengers in transit, delay codes management, etc.)

  22. Initial Proposals for Change Proposed Approach WP 1 Comments, Questions

More Related