1 / 27

Presentation Information Technology and Operations Control

Presentation Information Technology and Operations Control. Axel Goos, Dt. Lufthansa AG IT Management Operations FRA IO Ocho Rios, 14.-17. Mai 2001. Financial figures / Global information. Please refer to http://www.lufthansa-financials.de http://www.lufthansa.com. IT Organisation - Old.

gari
Download Presentation

Presentation Information Technology and Operations Control

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. PresentationInformation Technology and Operations Control Axel Goos, Dt. Lufthansa AG IT Management Operations FRA IO Ocho Rios, 14.-17. Mai 2001

  2. Financial figures / Global information Please refer to http://www.lufthansa-financials.de http://www.lufthansa.com

  3. IT Organisation - Old Lufthansa Passage Airline Sales Product and Service Personnel Netmanage- ment/ Marketing Operations IT IT IT IT IT IT IT

  4. IT Organisation - New Lufthansa Passage Airline Sales Product and Service Personnel Netmanage- ment/ Marketing Operations IT

  5. Quantity Figures Aircraft Flights GroundEvents Lufthansa 244 1100 500 Cityline 84 400 - Condor 47 150 130 LufthansaCargo 22 - -

  6. Processes

  7. 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

  8. STORM - Hardware-/Software Environment • Based on AIROPS from SDT • Client-server-architecture • Oracle 8.x database • 2 HP L2000 server with MC/ServiceGuard • 35 client workstations (HP B1000, 512MB, 9.3 GB) • 3-5 screens per workstation • Interfaces to host systems and other UNIX systems • Decision support subsystem • Intranet components • Used at: LH, Condor, LH Technik, Condor Cargo Technik • Maintenance: M2P Frankfurt, IDG Frankfurt

  9. STORM - Gantt-Chart

  10. STORM - Interfaces

  11. STORM Intranet Component - 1

  12. STORM Intranet Component - 2

  13. STORM - Enhancements 2001 • Implementation of rules for „Critical aircraft rotations“ • Interface to Crew Control System • Interface to MinGT System • Interface to DataLink • Interface to LIDO • Slot-Monitoring • Cost- and Yield-Model

  14. OBELISK - System Architecture Extraction of data:Interfaces to operative systems OBELISK Data Warehouse Intranet access (worldwide) Applications, Interfaces Reporting (Lufthansa, CityLine, Condor) OLAP Analysis

  15. OBELISK - Interfaces • ESPRIT (flight schedules) • FDL (basic data) • STORM (flight data, ground event data, basic data) • OPS/TANGO (movement messages, ASM - flight changes) • WAB (weight & balance data) • CKI (check-in data) • TEFLOS (passenger data) • ACARS (flight data via datalink) • EUROCONTROL (slot data from CFMU) • DLR/HIR (delay data, irregularity reports) • WTS (beggage loss data from World Tracer System) • ZFE (aircraft counters)

  16. OBELISK Intranet - 1

  17. OBELISK Intranet - 2

  18. OBELISK Intranet - 3

  19. OBELISK - Enhancements 2001 • OLAP Analysis • Daily report of operation / Ticker • Enhancements of intranet applications • Basic data handling / Workflow • Ground information display • Weekly/monthly reporting of technical issues

  20. Project ALLEGRO - Information • Information about ground processes should be available online (FRA, MUC) • ~80 timestamps between two flights • Irregularities can be realized earlier, reaction can begin sooner • Reasons in case of problems can be determined earlier • Timestamps for ground processes should be available in OBELISK for analysis and reporting • Values can be user for new Service Level Agreements

  21. Project ALLEGRO - Timestamps

  22. Project MinGT - Information • Problem: different MinGT‘s in different systems and departments • Problem: not only different values, but also different definitions • Result: problems in operation and punctuality • Definitions will be consolidated • MinGT server will be implemented for input, retrieval and quality assurance • MinGT workflow will be installed • Interfaces to different applications will be build

  23. Project MinGT - Interfaces Input of MinGT by station Quality assurance by area manager Input: MinGT Server OBELISK Intranet Output: ATHOS Flight Scheduling STORM OPS Control Interfaces:

  24. Project MinGT - Example Output

  25. Project Quality Monitoring - Information • Monitoring of critical parameters in flight scheduling and ops control process • Analysis of influence of scheduling process on production • Transparency about development of parameters • Analysis of dependencies between parameters • Change management for parameters • Goal: optimizing of processes • Goal: improvement of punctuality and regularity

  26. Project Quality Monitoring - Processes Online Monitoring in Tools (ATHOS, STOM) • Direct feedback in case of problem • Generation of alert in system • Suggestions for optimization Monitoring of Processes • Providing of deeper insight for wider range of people • Analysis of different points in time in current ops • Different characteristic in many aggregations Reporting • Weekly reporting • Monthly reporting

  27. Project Quality Monitoring - Parameters • Reserves (operational or maintenance, usage per fleet and hubs) • MinGT (degree of consumption) • Blocktime (degree of consumption) • ATC Buffer • Nightstops • Stability of rotations (number of changes per leg or equipment) • Technical demands • Consumption of aircraft

More Related