Dev:TT guide

The setting

In timetable users focus only on functional IS, reference functional IS. Topology can be there and describe the structure between the elements of functional IS but topology is not referenced from TT. This allows the systems which do not have/need microscopic infrastructure still to communicate.

• Functional Infrastructure
  • Operational Points: stations, block posts, …
    • Reference operational equipment
  • Tracks
    • support hierarchy
  • Stopping Places
    • Relate to platform edges
  • Platform Edges
    • Support hierarchy, relate to platforms
  • Platforms
• Rollingstock
  • Vehicles and Formations

There are operational points like stations, junctions etc. and tracks within these operational points. It is possible to say which track belongs to which operational point.

In the current example connections between operational points are not available.

Stopping places are locations, usually within the station, where the train may stop depending on train length, type etc. You can link them to microscopic infrastructure and have explicit positions for them but within TT domain they are only used as objects to reference them.

Platform edges are seen as interface between a area where passengers move to a train. Each platform edge is at one track and belongs to one platform. Platform is what is in between two platform edges. This can be useful to say which platform edge is direct opposite an other platform edge.

Vehicles can be assembled into formations. This formations are then used in operational trains to say which type of formation, which type of vehicle is operating on the certain type of service. For commercial train you can specify that you need that many passenger seats and same per vehicle. Later on you can fulfill the requirement by assigning vehicles to operational journeys that fulfill commercial journeys (trains).

Base itineraries

See code example at https://wiki3.railml.org/wiki/TT:baseItinerary.

Timetable starts with base itineraries. They are building blocks to be used within the modeling process resulting in operational and commercial trains. Base itinerary is a drivable sequence of operational points. It may depend on local rules if you need to include all the operational points that the train will go through or you can omit certain ones to have only e.g. stations. In the base itinerary they should be in the order they should be traversed.

Base itinerary models sequence of operational points as base itinerary points. Each point refers to one location, which is operational point. It says which track, which platform.