timetable current developments
play

Timetable current developments SMA und Partner AG Telefon - PowerPoint PPT Presentation

railML-Meeting in Paris 18.09.2013 Timetable current developments SMA und Partner AG Telefon +41-44-317 50 60 Unternehmens-, Verkehrs- und Betriebsplaner Telefax +41-44-317 50 77 Gubelstrasse 28, CH-8050 Zrich info@sma-partner.ch,


  1. railML-Meeting in Paris 18.09.2013 Timetable – current developments SMA und Partner AG Telefon +41-44-317 50 60 Unternehmens-, Verkehrs- und Betriebsplaner Telefax +41-44-317 50 77 Gubelstrasse 28, CH-8050 Zürich info@sma-partner.ch, www.sma-partner.ch

  2. Timetable 2 dicussions in our forum http://www.railml.org/forum/ro/index.php current discussion : • communication process, «changed» or «deleted» trains • train uniqueness • ridership • … railML | Paris | 1-00 | freigegeben | 18.09.2013 | jr

  3. Timetable 3 issues for future implementation http://trac.assembla.com/railML/report/2 planned issues : • enhancements (after previous agreement in forum) • tasks (refactoring, documentation) • grouped by Version (no breaking changes in minor releases) railML | Paris | 1-00 | freigegeben | 18.09.2013 | jr

  4. Timetable 4 annotations #224: train annotations: • defined as individual element • referenced by trainPart, stopDescription or connection railML | Paris | 1-00 | freigegeben | 18.09.2013 | jr

  5. Timetable 5 working with references timetable infrastructure #288, #195 using references: • everything is defined in its proper environment • references on track elements railML | Paris | 1-00 | freigegeben | 18.09.2013 | jr

  6. Timetable 6 connections #126: connection element: • references on other trains • train «is waiting for» or «is expected by» other train railML | Paris | 1-00 | freigegeben | 18.09.2013 | jr

  7. Timetable 7 master data, organizational units master data, organizational units: • coherent use with infrastructure and rollingstock • external maintained codes • language independent (xml:lang) railML | Paris | 1-00 | freigegeben | 18.09.2013 | jr

  8. Timetable 8 delay causes, cancellations #170 delay causes, cancellations: • how to communicate planned data vs. real data? • how to communicate planned cancellations? • shall we adopt «states» solution from infrastructure? railML | Paris | 1-00 | freigegeben | 18.09.2013 | jr

  9. Timetable 9 Questions and comments? Thank you for your attention! railML | Paris | 1-00 | freigegeben | 18.09.2013 | jr

Recommend


More recommend