 The design and optimisation of train services on complex infrastructure is Viriato’s central purpose. With the help of the new Network Visualisation auxiliary module, the user can first of all create a graphical illustration of infrastructure defined in Viriato. The module’s graphical interface also pro-vides a fast and simple way to place, prolong, shorten or re-reroute a train without detailed knowledge of the infrastructure. |
|
Read more...
|
 It is possible to use a single standard day type to develop and evaluate timetables at the conceptual level, however, as the date of timetable introduction draws near, planners must define the timetable in greater detail.
Furthermore, at the operational planning level a day-specific timetable is needed to optimally respond to short term changes such as added or cancelled trains. |
|
Read more...
|
 A railway timetable must fulfill numerous constraints including infrastructure (tracks, interlocking systems etc.), vehicle (performance, train type) and service pattern (intermediate stops, connections, etc.). The higher the railway system’s degree of networking and the closer it is to operating at capacity, the more constraints must be considered in timetable development. |
|
Read more...
|
 Timetable production is an interactive process involving many constraints and conflicting goals. Operational constraints often cause impacts that are not initially obvious. Furthermore, the system-wide impacts of local timetable changes are not directly evident in large railway networks. |
|
Read more...
|
 While the graphic timetable represents operations on the network level, the service timetable describes operation of a particular train. It provides the engine driver with all the temporal and spatial information needed to operate the train including: station arrival/departure times, and safety-relevant information such as crossings and over-takings. |
|
Read more...
|
|
|
