1 / 36

Deutsche Lufthansa AG Axel Goos, FRA OZ1/E 15. Oktober 1998

Deutsche Lufthansa AG System Operations Control Center Processes and IT Systems AGIFORS 2000 - Budapest/Hungary. Deutsche Lufthansa AG Axel Goos, FRA OZ1/E 15. Oktober 1998. Topics of this presentation. How are we organized? How we do OPS control? Which systems do we use?

zuriel
Télécharger la présentation

Deutsche Lufthansa AG Axel Goos, FRA OZ1/E 15. Oktober 1998

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. Deutsche Lufthansa AG System Operations Control Center Processes and IT Systems AGIFORS 2000 - Budapest/Hungary Deutsche Lufthansa AGAxel Goos, FRA OZ1/E15. Oktober 1998

  2. Topics of this presentation • How are we organized? • How we do OPS control? • Which systems do we use? • Visions for the near future?

  3. Activities Y2K Let me move some months back in time... Finally we can go on with our normal job! And what about Y2K + 1?

  4. Quantity Figures Aircraft Flights GroundEvents 4 Different SOC‘s! Lufthansa 225 1000 450 Cityline 52 500 - Condor 44 150 50 LufthansaCargo 20 100 -

  5. Quantity Figures Aircraft Flights GroundEvents Lufthansa 225 1000 450 Cityline 52 500 - Condor 44 150 50 LufthansaCargo 20 100 -

  6. Processes

  7. Timeframe of Workflow 2 days DoO 1 day 3 days 4 weeks Flight Scheduling CommercialCoordinator Maintenance Control Flight Planning Operations Control Crew Control

  8. New OPS Control Center • In former times they have been located in different • floors/buildings: • Flight planning / Dispatch

  9. New OPS Control Center • In former times they have been located in different • floors/buildings: • Flight planning / Dispatch • OPS control / Short-range flight scheduling

  10. New OPS Control Center • In former times they have been located in different • floors/buildings: • Flight planning / Dispatch • OPS control / Short-range flight scheduling • Maintenance control

  11. New OPS Control Center • In former times they have been located in different • floors/buildings: • Flight planning / Dispatch • OPS control / Short-range flight scheduling • Maintenance control • Crew Control

  12. New OPS Control Center • In former times they have been located in different • floors/buildings: • Flight planning / Dispatch • OPS control / Short-range flight scheduling • Maintenance control • Crew Control  Communication problems! Different data sources!

  13. New OPS Control Center IT Support Statistics Flight Scheduling Operations Control

  14. New OPS Control Center IT Support Statistics Maintenance Control Flight Scheduling Operations Control

  15. New OPS Control Center IT Support Statistics Flight Planning Now: People are workingtogether. Future: Link the systems closer together! Goal: Develop global solution (not only n local solutions) Maintenance Control Flight Scheduling Operations Control Crew Control

  16. Computer Systems  Flight Scheduling STORM (based on AIROPS)  Commercial Coordinator STORM (based on AIROPS)  Maintenance Control STORM (based on AIROPS)  Flight Planning LIDO  Operations Control STORM (based on AIROPS)  Crew Control CAS, DAYSY  Data Warehouse OBELISK

  17. STORM: Gantt Chart

  18. STORM: OPS-/Maintenance Control • Based on AIROPS from SDT • Client-server-architecture • 2 HP K210 Server with MC/ServiceGuard • 30 Client Workstations (HP B1000, 512MB, 9.3 GB Disk, 4 screens) • Interfaces to host systems and other UNIX systems • Decision support subsystem • Intranet components • Used at: LH, Condor, Condor Berlin, LH Technik, Condor Cargo Technik • Maintenance: MPP Consulting

  19. STORM: Decision Support • Based on AIROPS from SDT • Client-server-architecture • 2 HP K210 Server with MC/ServiceGuard • 30 Client Workstations (HP B1000, 512MB, 9.3 GB Disk, 4 screens) • Interfaces to host systems and other UNIX systems • Decision support subsystem  • Intranet components • Used at: LH, Condor, Condor Berlin, LH Technik, Condor Cargo Technik • Maintenance: LH Systems GmbH

  20. STORM: Decision Support

  21. STORM: Plans for Enhancements • Achieve better punctuality (groundtime buffers, ATC-critical airports, aircraft as reserves)

  22. STORM: Plans for Enhancements • Achieve better punctuality (groundtime buffers, ATC-critical airports, aircraft as reserves) • Slot monitoring

  23. STORM: Plans for Enhancements • Achieve better punctuality (groundtime buffers, ATC-critical airports, aircraft as reserves) • Slot monitoring • Interface to LIDO (weather data, notams, slots, aircraft and airport data)

  24. STORM: Plans for Enhancements • Achieve better punctuality (groundtime buffers, ATC-critical airports, aircraft as reserves) • Slot monitoring • Interface to LIDO (weather data, notams, slots, aircraft and airport data) • Interface to DAYSY (evaluation of what/if scenarios)

  25. STORM: Plans for Enhancements • Achieve better punctuality (groundtime buffers, ATC-critical airports, aircraft as reserves) • Slot monitoring • Interface to LIDO (weather data, notams, slots, aircraft and airport data) • Interface to DAYSY (evaluation of what/if scenarios) • Automatic telex generation (check planning, aircraft restrictions)

  26. STORM: Plans for Enhancements • Achieve better punctuality (groundtime buffers, ATC-critical airports, aircraft as reserves) • Slot monitoring • Interface to LIDO (weather data, notams, slots, aircraft and airport data) • Interface to DAYSY (evaluation of what/if scenarios) • Automatic telex generation (check planning, aircraft restrictions) • Evaluation of scenarios to provide cost and yield information

  27. STORM: Intranet Site

  28. OBELISK: Architecture Extraction of Data:Interfaces to operative systems Consolidation OBELISK Data Warehouse Intranet Site Applications Reporting (internal, press, IATA, AEA, etc.) Analysis (Seagate HOLOS)

  29. OBELISK: Data Catagogue • STORM/OPS (in future: STORM/TANGO) • WAB (Weight and Balance) • FDL (Flight Data Load) • CKI (Check-In System) • ATHOS (Flight Scheduling System) • WTS (World Tracer System) • RES (Reservation System) • DAS (Tow Movements) • DLK (Datalink - ACARS) • TEFLOS (Pax, Load, Baggage Data • ...

  30. OBELISK Intranet: Flight Information

  31. OBELISK Intranet: Aicraft Rotation

  32. OBELISK Intranet: MVT/Change Messages

  33. OBELISK Warehouse: Delay Airports DimensionAirports AllLegs DelayedLegs AllPax DelayedPax DimensionTime: 1. half 98 DimensionDelays: All

  34. OBELISK Warehouse: Delay Groups DimensionDelays DimensionAirport: FRA

  35. OBELISK Warehouse: Delay Codes Details viaDrill Down

  36. OBELISK Warehouse: Multidimensional Analysis • Delays and punctuality • Groundtimes • Robustness/stability of schedule • Handling/usage of reserves

More Related