Timetable

The railML® timetable subschema is used to describe the railway timetable including all its various facets that are needed by the rail data exchange partners. The main objective is to improve the data exchange and interoperability so that infrastructure managers, train operators, software developers can understand and process timetable data in a consistent manner in their railway applications with better integration and less errors.

Key components of the railML® timetable schema:

• Train Schedules: Provide a description of the trains path including arrival and departure times, used tracks and platforms, conducted operations at the stop, and much more.
• Operating Periods: They represent specific time frames during which train services are scheduled to operate for train services or rostering. Operating periods are capable of encoding repeating operating day patterns as well as irregular patterns. Additionally, it is possible to describe the rules that lead to the resulting operating day pattern, which may help providing detailed passenger information.
• Rostering: Train parts can be linked to form the circulations necessary for rostering (rolling stock schedules).
• Connection Information: This allows passengers to transfer between trains and allows routing systems to find connecting trains.
• Passenger Information: It includes essential details, displayed on screens or announced via speaker, for informing passengers about train schedules, routes and service updates.

Example use cases for the railML® timetable schema:

• Integrated Traffic Management System provides system support for dispatching operations and managing timetables to optimise rail traffic flow.
• Passenger Information at Stations involves displaying and announcing relevant information to passengers at stations.
• Run Time Calculation Input Data is intended to exchange data with systems that are focused on train runtime calculation.
• Long-Term Circulation Planning is aimed at exchanging data for optimising the train circulation.
• Possession Management (POMA) is intended to manage restrictions in the railway network.

To explore more detailed features and elements of the timetable schema, please visit the railML wiki3 pages.

For further inquiries, you may contact Milan Wölke, the current coordinator for the railML.org timetable subschema.