Skip to main content

The infrastructure model

TrenoLive uses a two-levelled infrastructure model. While the timetable is planned and constructed on a macroscopic level, the running times can be calculated on a microscopic level for additional precision.

The macroscopic model is stored directly in TrenoLive, instead the microscopic model will be contained in the specialised infrastructure database of trenissimo.

Additional information on how trenissimo works can be found here: https://trenolab.atlassian.net/wiki/spaces/TRENISSIMO/pages/1049182/Create+and+edit+the+microscopic+infrastructure+model+trenissimo

Macroscopic model​

The macroscopic model in TrenoLive contains the railway infrastructure in an edge-vertex-graph, where vertices are OCPs and edges are the tracks linking these OCPs. Edges can have an unlimited number of tracks (edge tracks), which can be configured to be bi-directional or (primarily) mono-directional. Single track lines are always bidirectional. Double track lines can have a primary direction assigned, so trains run either on the left or on the right side (unless contrary information has been specified). Alternatively, both tracks can be used in both directions.

General structure​

In trenoLive different infrastructures can be maintained. The history of changes is managed by infrastructure releases. After changes have been made to an infrastructure, a new release needs to be created. A new timetable scenario is always based on a specific release. The validity period of the scenario needs to be within the validity period of a infrastructure release, but it can also be a subset of it. To create a variant of the infrastructure, the infrastructure release should be cloned. This will create a new branch of the infrastructure without influencing the existing model.

Each infrastructure consists of OCPs, Lines and Infrastructure Managers. Lines and OCP have a substructure which in the following is explained in more detail.

Line and line tracks​

Bidirectional tracks can be distinguished in four categories of opposite direction working:

Main​

Main direction of travel. Identified by a double arrow.

Alternative​

Not main direction of travel, but used for planned and dispatched movements without limitations. Identified by a single arrow.

Allowed​

Not main direction of travel, but it is possible to plan movements - restrictions may apply.

Forbidden​

No trains are allowed in this direction. Identified by an 'X' marker

Operation Control Points​

On the level of OCP it is possible to define tracks (OCP tracks) and platforms, which both can, but do not have to, be partitioned in sectors. Track sectors should be defined if the physical track is operationally divided to allow simultaneous track occupation. The definition of platforms and track sectors with the correct length allows the use of the Conflict checker to reveal errors in the planning process. The definition of OCP tracks is obligatory.

To complete the OCP layout the OCP tracks should to be connected with the edgeTracks. If orange edgeTracks are present at the bottom of the layout it means they are not assigned. To assign the edgeTracks to one or the other side of the station drag and drop them to the left or right of the station layout. This is necessary for a correct representation of incoming and outgoing movements in the track occupation diagram and the conflict checker. If a clear distinction of through tracks is possible, the edgeTracks and the corresponding tracks in the OCP can be connected by dragging a line from the OCP track to the arrow of an edgeTrack.

(If you are using Firefox as main browser this connection is not always possible. The name of the edgeTrack can block the connection. It is possible to use a different browser, select a short code for line names and edges or drag the line around the text)

Unfeasible Paths​

Unfeasible paths are used to prevent the planning of unfeasible itineraries through stations and junctions. It is possible to define three different combinations of unfeasible paths:

  • Inbound edge track and outbound edge track
  • Inbound edge track and OCP track
  • OCP track and outbound edge track

Default tracks​

Default tracks are used in timetable planning and in simulation. A default track can be assigned to each itinerary within a station. Default tracks are a required input if track assignments are not provided directly in the timetable.

The Default tracks are not officially part of the macroscopic model. To edit the default track, use the Default Tracks tab of the Station Layout editor in the timetable module (Timetable -> TT scenario selection -> OCPs -> Layout editor). Default tracks can also be transferred between scenarions.