1 / 23

5 years experiences in being responsible for an optimisation system

5 years experiences in being responsible for an optimisation system. Dr. Erwin Achermann Friday, 18 th January 2013 ETH Zürich. Agenda. What have we done? How have we done it? How have we been? What have we learnt?. Agenda. What have we done? How have we done it? How have we been?

inga
Download Presentation

5 years experiences in being responsible for an optimisation system

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. 5 years experiences in being responsible for an optimisation system Dr. Erwin Achermann Friday, 18th January 2013 ETH Zürich

  2. Agenda • What have we done? • How have we done it? • How have we been? • What have we learnt? IT13.rail

  3. Agenda • What have we done? • How have we done it? • How have we been? • What have we learnt? IT13.rail

  4. What have we done? • Train Traffic Control System for the Lötschberg Base Tunnel, • that can optimise Train Traffic in LBT: Minimize Time on Single Line Track inside Tunnel • Stabilization of Timetable • Reduction of Energy consumption • … • and that does other novel and particular things for LBT. IT13.rail

  5. What have we done? IT13.rail

  6. What have we done? Video: The Explanation to the Swiss people by Swiss Public Television. IT13.rail

  7. What have we done? Achievement 1: Timetable stability IT13.rail

  8. What have we done? Achievement 2: Energy saving IT13.rail

  9. What have we done? Achievement 3: Capacity Increased Conventional operation planned with 100 trains per day Average trains per day using Speed Advisory System AF: 120 trains per day Peak performance using Speed Advisory System AF 144 trains per day  Increased 20 trains per day compared to conventional single line operation IT13.rail

  10. Agenda • What have we done? • How have we done it? • How have we been? • What have we learnt? IT13.rail

  11. How have we done it? Rescheduling Decisions ReschedulingProposals Adaptations AF HMI Scheduling Plan State Commands Routes,Order Train numbers Plannedentry times AF Server TrainDescribers 85 72 NeighbourTCC RouteStates Position-Reports Train routeRequests Optimalspeed OBU 85 Commissioning Vopt TrainRoutes Interlocking RBC OBU 72 MA, Occupations Position Rep. It13.RAIL

  12. How have we done it? Rescheduling Decisions ReschedulingProposals Adaptations AF HMI Scheduling Plan State Commands Routes,Order Train numbers Plannedentry times AF Server TrainDescribers 85 72 NeighbourTCC RouteStates Position-Reports Train routeRequests Optimalspeed OBU 85 Commissioning Vopt TrainRoutes Interlocking RBC OBU 72 MA, Occupations Position Rep. It13.RAIL

  13. How have we done it? Rescheduling Decisions ReschedulingProposals Adaptations AF HMI Scheduling Plan State Commands Routes,Order Train numbers Plannedentry times AF Server TrainDescribers 85 72 NeighbourTCC RouteStates Position-Reports Train routeRequests Optimalspeed OBU 85 Commissioning Vopt TrainRoutes Interlocking RBC OBU 72 MA, Occupations Position Rep. It13.RAIL

  14. Agenda • What have we done? • How have we done it? • How have we been? • What have we learnt? IT13.rail

  15. How have we been? First Drive at 230 km/h on Oct 3 2006, 16h15 IT13.rail

  16. How have we been? First Drive at 230 km/h on Oct 3 2006, 16h15 IT13.rail

  17. How have we been? Going into Operation Issues tracker statistics: Note the trend! IT13.rail

  18. How have we been? Going into Operation IT13.rail

  19. Agenda • What have we done? • How have we done it? • How have we been? • What have we learnt? IT13.rail

  20. What have we learnt? IT13.rail

  21. What have we learnt? • 2/3 of all Issues irrelevant. • Wishes for improvements • Misunderstanding • Not reproducible • Duplicates • Better organise an efficient Treatment of Issue Reports • Again 2/3 of those is a pile of good ideas for improvements. • Wishes for improvements • Misunderstanding  Better organise an efficient Collection of Issue Reports IT13.rail

  22. What have we learnt? • Trust in the applied principles and tools.  Better built up an infrastructure • Software Architecture • Testing environment • Communication processes which is exactly tailored to the needs of the project. • Clarify expectations. • Better sit down and discuss it once more with all partners. • Be ready. • Reality is more creative in finding unforeseen combinations. IT13.rail

  23. Thanks for your attention IT13.rail

More Related