OpenTrack - Manual EN.1.9 PDF

Daniel Huerlimann, Andrew B.
Nash
Simulation of Railway Networks

Version 1.9
OpenTrack Railway Technology Ltd.
and
ETH Zurich
Institute for Transport Planning and Systems
Table of Contents
Table of Contents
1. Introduction .................................................................................................... 1
2. Structure of OpenTrack ........................................................................... 3

2.1 Input Data .................................................................................................. 3
2.2 Simulation .................................................................................................. 5
2.3 Evaluations................................................................................................. 5
2.4 Data Management in Open Track .............................................................. 7
3. OpenTrack Application ............................................................................ 9

3.1 Starting OpenTrack and File Management .............................................. 10
3.2 OpenTrack Worksheet ............................................................................. 10
3.3 Vertex....................................................................................................... 11
3.4 Edges (Sections of Railroad Track) ......................................................... 17
3.5 Connector Vertices .................................................................................. 22
3.6 Signals...................................................................................................... 23
3.7 Stations..................................................................................................... 31
3.8 Power Supply Area .................................................................................. 36
3.9 Additional Worksheet Objects................................................................. 39
3.10 Behaviour of Objects on the Worksheet .................................................. 48
3.11 Alternative Methods to start OpenTrack ................................................. 50
4. Train Operations: Routes, Paths and Itineraries ..................... 53

4.1 Routes ...................................................................................................... 54
4.2 Shuntings ................................................................................................. 58
4.3 Paths......................................................................................................... 60
4.4 Itineraries ................................................................................................. 62
5. Train Management (Trains) .................................................................. 67

5.1 Trains Window ........................................................................................ 67
5.2 Locomotive Management (Engines)........................................................ 71
5.3 Train Resistance Calculation ................................................................... 75
5.4 Examples.................................................................................................. 83
5.5 Train Categories....................................................................................... 87
5.6 Distribution Functions in OpenTrack ...................................................... 93
6. Courses and Timetables........................................................................ 95
OpenTrack Simulation of Railway Networks

Table of Contents
6.1 Course Management (Courses)................................................................ 95

6.2 Timetable Database................................................................................ 100
6.3 Connections ........................................................................................... 106
7. Simulation in Open Track ................................................................... 113

7.1 Calculation Basis of the Simulation...................................................... 113
7.2 Behaviour of Protection Systems.......................................................... 117
7.3 Dispatching in OpenTrack ..................................................................... 123
8. Running an OpenTrack Simulation ............................................... 127

8.1 Preferences............................................................................................. 127
8.2 Running and Monitoring an OpenTrack Simulation ............................. 130
8.3 Incidents................................................................................................. 134
8.4 Train Graph (Train Diagram) ................................................................ 142
8.5 Working with Timetable Data on the Train Graph................................ 146
8.6 Monitoring the Simulation..................................................................... 148
8.7 Evaluations............................................................................................. 150
8.8 Headway Calculator............................................................................... 154
8.9 Dispatching Rules .................................................................................. 158
9. Further Tools and Settings ................................................................ 165

9.1 File Commands: Menu Document ......................................................... 165
9.2 Print........................................................................................................ 168
9.3 Menu Info .............................................................................................. 168
9.4 Menu Edit .............................................................................................. 170
9.5 Menu Format.......................................................................................... 172
9.6 Menu Tools ............................................................................................ 173
9.7 Menu Functions ..................................................................................... 174
9.8 Data Exchange ....................................................................................... 181
9.9 Menus Hide and Quit ............................................................................. 186
9.10 Checklist for OpenTrack Projects.......................................................... 187
10. Final Remark .............................................................................................. 189
11. Literature ...................................................................................................... 191
12. Summary of Menu Operations ......................................................... 193

Introduction 1
1. Introduction
This document outlines the background and use of OpenTrack, a railroad network simulation
program developed as part of the Swiss Federal Institute of Technology Institute for Transport
Planning and Systems (ETH IVT) research project entitled OpenTrack - Simulation of Railway
Networks. The project objective was to develop a user-friendly railroad simulation program
that can run on different computer platforms and can answer many different questions about
railway operations.
This manual describes the OpenTrack program and summarizes the OpenTrack research. A
more detailed presentation of the program’s theoretical basis and simulation model are presen-
ted in the full research report [Hue 01].
The main modules of OpenTrack are illustrated in Figure 1.
Input Simulation Output
km/h
150
km/h 100
220.0 100 200
50 250
50
0 300
0
0 10 20 30 40 km
Rolling Stock Interactivity Diagrams

km
40
30
20
10
Station A 0
08:00 09:00 10:00
S4
S7
S3
S5 Train Graphs
S6
S2 S8
2201 2203 2205
Track 1
S1
(111) 221 (113)

Track 2
Infrastructure (112) 222

Track 3
08:00 08:30 09:00
Occupations
s
Course ID Station Arrival Departure Wait
200
IC 5000 IGG HH:MM:SS 08:20:00 0
IC 5000 YPS 08:24:00 08:25:00 60
8002
IC 5000 OBE HH:MM:SS 08:31:00 30

100
RE 8002
8002
8000
8000
2001
2003
103
111
IC 5000 AAT HH:MM:SS 08:38:00 60

IC 5000 GRS HH:MM:SS HH:MM:SS 0 IC 101 0
IC 5000 PEW HH:MM:SS HH:MM:SS 0
WED
WED
PEW
PEW
OBE
ZET
ZET
IGG
IC 5000 WED 08:55:00 HH:MM:SS 60
Timetable Animation Statistics
Figure 1: OpenTrack Process: Input-Simulation-Output
As shown in Figure 1, OpenTrack administers input data in three modules: rolling stock, infra-
structure, and timetable. Users enter input information into these modules and then run the
simulation.
The simulation is carried out with the user defined input data. Predefined trains move on a
defined track layout on the conditions of the timetable data. OpenTrack uses a mixed discrete/
continuous simulation process that calculates both the continuous numerical solution of the

2 Introduction
differential motion equations for the vehicles (trains), and the discrete processes of signal box
states and delay distributions.
A wide variety of output data is developed in the simulation process. OpenTrack allows users
to present this data in many different formats including, time-space diagrams, tables and gra-
phical elements (pictures).

Structure of OpenTrack 3
2. Structure of OpenTrack
2.1 Input Data
2.1.1 Rolling Stock: Locomotives and Wagons

Rolling stock consists of locomotives and wagons which are combined to form trains.
Locomotive data is stored in a database called Depot. This database describes all possible
locomotive types in terms of technical specifications such as: tractive effort/speed diagram,
weight, length, and adhesive values. The user can enter new data for specific locomotives into
the locomotive database from the OpenTrack program or can make use of pre-defined locomo-
tives already in the database.
Wagons are not specifically defined in OpenTrack, since the only data necessary for the simu-
lation is the length and load of the complete train. Therefore, the program models trains crea-
ted by selecting one or more locomotives from the locomotive database and combining them
with length and weight data that serves to model the train’s wagons in the simulation. These
trains are managed by OpenTrack in a train database.
2.1.2 Track Layout Data

Track layout data consists of a description of the physical infrastructure being simulated. This
includes actual infrastructure such as track segments (called “edges” in OpenTrack), signals,
and stations; as well as, virtual elements such as vertices (points) and routes. Figure 2 shows
part of a track layout in the area of a station.
Project Olten
FR10000
RE10003
.
355
354
IC200
08
353
352
Olten
351
569
Olten.opentrack
Figure 2: Example OpenTrack Station Layout

4 Structure of OpenTrack
The track layout can be graphically recorded and managed by means of a track picture editor.
Attributes can be assigned to the various graphical elements using an “Inspector” tool. For
example, the Edge Inspector can be used to assign information such as length, gradient, and
maximum speed, to a particular edge. Similarly, the Vertex Inspector can be used to assign
attributes such as a name, Kilometer reference point, and switch information to a vertex.
An important aspect of OpenTrack is that it describes the track layout in terms of double ver-
tex graphs (see Chapter 3.3.1 for more information on double vertex graphs). Using double
vertex graphs allows directional data to be more easily managed in OpenTrack.
2.1.3 Timetable Data

Timetable data consists of information on the movement of trains. This information includes
desired arrival and departure times, connection information, minimum stop times, and stop
information. OpenTrack manages timetable data in a timetable database.
2.1.4 Train Operations

OpenTrack simulates train operations on a track network. There are many names used to des-
cribe the physical track network (infrastructure) and train operations that are similar and often
these are used in different ways in different applications (e.g. different rail simulation pro-
grams). This manual fully describes OpenTrack’s terminology in the sections below, however
as an initial orientation, OpenTrack’s terminology is outlined below.
Infrastructure Related Terms
Infrastructure related train operations terms are user defined combinations of physical ele-
ments that are logical to group together. These terms are associated with the infrastructure and
do not have movement information (i.e. schedules) associated with them. There are three
levels of infrastructure related terms, higher levels consist of sets of the lower level. Specifi-
cally:
• Route - Routes are the first level of train movement description. They consist of a set of
vertexes and edges which are linked together. In physical terms they can be thought of as
sections of track.
• Path - Paths are the second level, they consist of sets of Routes. In physical terms they can
be thought of as a group of track sections in a certain area, for example, a group of track
sections that a train would use to pass through a station.
• Itinerary - Itineraries are the third level, they consist of sets of Paths.

Timetable Oriented Movement Terms
Timetable oriented train operations terms are user defined combinations of schedule data with
the physical infrastructure used by a train. The physical infrastructure is defined in terms of
Itineraries (see above). Timetable oriented terms are associations of itineraries with schedule
data, and consist of the following:
• Course - Courses are sets of itineraries with schedule data (timetable data, information on
whether a train stops at a certain station, etc.) associated with the itinerary data. A course
can be thought of as a particular train operating over a given time period.
• Turnaround - Turnarounds are groups of courses. They can be used to show that the same
physical train composition is used for several different courses. There are other ways of
indicating this and so turnarounds are not used often in OpenTrack.
2.2 Simulation
The objective of the OpenTrack simulation process is for the user-defined trains to fulfil the
user-defined timetable on the user-defined track layout. As mentioned above OpenTrack uses
a mixed continuous - discrete method to model train movement. The motion of trains is
modelled by the solution of the differential motion equation (continuous) combined with
signal information (discrete).
The differential motion equation calculates the train’s forward motion based on the maximum
possible acceleration per time step (the acceleration rate is determined using train performance
and track layout data such as maximum tractive effort, train resistance, and track gradient,
track radius, and segment maximum speeds). The train speed is obtained using integration and
the distance covered using reintegration.
Train movements are also governed by the signals controlling the track layout. Occupied track
sections, switching times of the signals or restrictive states of signals influence the perfor-
mance of the trains. In other words, if the signal shows stop, the train does not move.
During the simulation each train feeds a virtual tachograph (output database), which stores
data such as acceleration, speed and distance covered. In this way various evaluations can be
performed after the simulation has been completed.
The simulation can be performed normally or in an animation mode. In animation mode the
user sees the running trains, the occupied and the allocated track sections, as well as the states
of the signals on the track layout.
2.3 Evaluations
OpenTrack can perform a variety of evaluations using the simulation data. These evaluations
can be made on several different perspectives, for example, per train, per route or per station.
Several examples of typical OpenTrack evaluations are presented in the following figures;
more examples are presented throughout this manual.

Figure 3 illustrates acceleration characteristics and speed of a train operating on a given route
(speed-distance diagram); Figure 4 illustrates a train diagram (space-time diagram) which
shows actual and desired travel times; and, Figure 5 illustrates station track occupation data.
[km/h]
140
130
120
110
100
90
80
70
60
50
40
30
20
10
0
0 10 20 30 40 50 [km]
Zetthausen
Ypslikon
Pewald
Iggswil
Figure 3: Speed/Distance-Diagram
08.00 .10 .20 .30 .40 .50 09.00

STATZ
0 00 1
FR 4
R E1
IC4
IC4
FR3
FR 4
000
002
000
5 00 0
0 00 2
0
STATY
FR
STATT
40
00
0
STATU
1
5 00 1
3
000
0 00
RE1
FR3
F R4
01 03
40 40
IC IC
STATV
08.00 .10 .20 .30 .40 .50 09.00
Figure 4: Train Graph (Space-Time Diagram)

SE40000 SE40002
STATY 01
IC4001 RE10001 IC4003 FR35001 IC4005 RE10003 IC4007 FR35003

STATY 02
RE10000 IC4000 FR35000 IC4002 RE10002 IC4004 FR35002 IC4006

STATY 03
08:00 08:30 09:00 09:30 10:00 Time
Figure 5: Track Occupations
2.4 Data Management in Open Track

OpenTrack administers input and output data in three different kinds of files: documents, data-
bases, and evaluations. The relationship between these files and OpenTrack is illustrated in
Figure 6. The files can be summarized as follows:
• Documents - OpenTrack stores track infrastructure information and train graphs as docu-
ments. These files can be edited by users with a graphical editor (or Inspector). The num-
ber of documents used in a simulation is unlimited; it depends upon the type of modelling
being performed, the modularity of the track layout, and the number of graphical timeta-
bles to be produced.
• Databases - OpenTrack uses six different databases to store rolling stock, station, and
timetable information. These consist of: locomotive data, train data, course data, timetable
data, station data, and itinerary data. There can be several different versions of any data
file, however only one version can be active for a given simulation run.
• Evaluations - OpenTrack saves evaluation data from the simulation in different output
files. This data consists of tab separated ASCII text files. It can be edited in a text editor or
in a spreadsheet program.
Documents Output (ASCII-Text)
etc.
*.opentrack *.otsimcor *.vs *.as *.tt
Databases
*.depot *.trains *.courses *.timetable *.stations *.dest
Figure 6: OpenTrack Input-Output Data Management


OpenTrack Application 9
3. OpenTrack Application
The OpenTrack application runs on the Windows (XP, Vista, 7, 8, 10) and Mac (MacOS X,
macOS) operating systems. The figures presented in this document come from the Windows
8.1 version. On other platforms the windows, the menu representations, or the build-up of the
screen can deviate slightly from the examples presented in this document. However, all versi-
ons of OpenTrack have the same functionality.
Figure 7: OpenTrack User Interface
Figure 7 illustrates the main elements of the OpenTrack program. The large windows consist
of worksheet documents that contain the track layout data. On the right side of the figure an
OpenTrack “Inspector” is illustrated, in this case the Signal Inspector, and on the far right side
the long window is called the “OpenTrack Tool Palette” or more simply the “Palette.”
The basic process for creating or editing OpenTrack track networks uses graphical tools to
create and place objects on the worksheet, and a tool called the inspector for giving these
objects attributes (e.g. a length of track has a gradient or speed limit). OpenTrack’s graphical
tools are displayed on the Palette. The palette tools include the Pointer (used to select objects
on the worksheet), icons for worksheet objects (vertex, station vertex, connector vertex, edge,
signal, exclusion link, and station), graphical icons, and evaluation tool icons.
After objects are placed on the worksheet their attributes are entered or set using the inspector
tool. There is a different inspector for each type of object, however OpenTrack will automati-
cally open the appropriate inspector for the selected object by entering the command: Tools 
Inspector.
The following sections outline how various objects are placed on the worksheet, how attribu-
tes are input or edited, and describes the object attributes in detail.

10 OpenTrack Application
3.1 Starting OpenTrack and File Management
Starting OpenTrack
• Find the OpenTrack.exe file in the file directory or the application icon on the desktop
• Double click on the file name or the icon
• OpenTrack is started
Alternative methods to start OpenTrack (e.g. script mode) are described in Chapter 3.11.
3.2 OpenTrack Worksheet
Track Layout Elements
Worksheet
In OpenTrack the track layout is created and edited using a file called a worksheet. A work-
sheet consists of a track layout section with all its elements such as route, signals, stations etc.
A worksheet can also include additional information such as text, pictures, graphical elements
(rectangles, circles, lines) to help users better visualize the layout. Figure 8 illustrates a typical
worksheet.
The railway network to be modelled can be spread over several worksheets by means of a
“connector.” A connector connects points on two different worksheets. In this way the com-
plete network can be subdivided into clear modules, which can be loaded separately or
together depending on the need.
Figure 8: OpenTrack Worksheet

3.3 Vertex
Vertices mark the points in the railway network where at least one route attribute (gradient,
radius, speed etc.) changes or where there is a signal. In OpenTrack vertices always appear in
pairs (since OpenTrack represents the network using the double vertex graphing technique),
but as single objects on the worksheet. Attributes such as names and reference points asso-
ciated with a vertex can be entered and edited using the Inspector tool.
3.3.1 Double Vertex Graphs (DVG)

OpenTrack structures the track network using the double vertex graph technique [Mon 92b,
Mon 92b, Mon 94]. In a double vertex graph the graph’s vertices do not appear alone, but
always together with a second vertex. Thus, contrary to classical (single vertex) graphs,
double vertex graphs can provide information at each vertex about the edge via which the ver-
tex has been reached.
The differences between classical graphs and double vertex graphs can be illustrated using the
example of a switch represented in Figure 9 as a classical graph and in Figure 10 as a double
vertex graph.
E F
A B C D
Figure 9: Switch Represented as Classical Graph
EE' F F'
AA' BB' CC' DD'
Figure 10: Switch Represented as Double Vertex Graph
In searching through the network layout for possible routes, a possible route of D-C-B-E-F or
the reverse is found using the classical graph representation shown in Figure 9. Since real
switches cannot be traversed in this vertex order, a rule would need to be introduced in the
representing graph preventing this operation.
A simple solution is available using the double vertex graphing technique, which represents
the track layout with the sequence rule of: vertex-vertex-edge-vertex-vertex-edge-vertex-ver-
tex... Using this rule only the possible train routes through the switch would be found (i.e. the
routes AA‘-BB‘-CC‘-DD‘ or the reverse, and AA‘-BB‘-EE‘-FF‘ or the reverse) in Figure 10.

Similarly, double vertex graphs provide a simple and easily understood method for placing
signals in OpenTrack so that they control only one direction of travel.
Vertex Commands
Inserting a Vertex
• Select Vertex Tool from palette (illustrated above).
• Mouse click on the worksheet.
• Vertex (double vertex) is created.
• Set vertex attributes using the Vertex Inspector.
Inserting a Vertex in an Existing Edge

• Select Vertex Tool from palette.
• Mouse click on the edge with the SHIFT key pressed down.
• Vertex (double vertex) is created, edge is divided into two.
• Set vertex attributes using the Vertex Inspector.
Deleting a Vertex from an Edge

• Select Pointer Tool from palette.
• Select vertex to be deleted.
• Press SHIFT key and Backspace -or- Press SHIFT key and DELETE key simultaneously.
Splitting a Double Vertex

A single double vertex can be split into two double vertices; this has the effect of breaking the
‘track’ connection between the two vertices. This command can be used in cases where the
user is editing the track network and does not want to lose information about the edges that
connect to the vertex. (Since simply removing a vertex will merge the edges on either side of
the vertex into a single edge and OpenTrack then automatically deletes edge attributes.) The
following procedure can be used to split a vertex:

• Highlight vertex to be split.
• Click Functions Cut Vertex.
Merging Two Double Vertices

Two double vertices (including connector vertices) can be merged into a single double vertex
using a drag and drop process. Vertices which already have edges or signals cannot be merged,
however the use of double vertex graphs means that one side of the vertex can have an edge or
signal while the other side does not. It is these ‘empty’ sides that can be merged. The process
for joining two vertices is:

• Select Edge Tool from palette.

• Press SHIFT Key and select Vertex (empty side) to be merged by pressing mouse button.
• While holding SHIFT Key and mouse button down, drag edge to target vertex.
• Release mouse button.
It is important to note that you can only merge two ‘empty’ sides of vertices. If you start by
selecting a vertex side with an edge or signal the program will simply place a new vertex on
the document. Similarly, the program will not allow you to ‘drop’ an empty side of one vertex
on the non-empty side of another vertex.
Vertex Inspector
OpenTrack uses a tool called “Inspector” to view and assign attributes to various elements. In
the case of a vertex this tool is called the Vertex Inspector.
Figure 11 illustrates the Vertex Inspector. When using the Vertex Inspector it is important to
remember that OpenTrack uses double vertices. This means that vertex attributes are assigned
to each of the “sides” that make-up the double vertex separately. Thus, for example, if you
want to assign the same name to both sides of the vertex you need to enter the data twice, once
for each side. The Vertex Inspector allows you to choose which side of the vertex you are wor-
king with by selecting the side you want in the “Vertex Selector” located at the bottom of the
Vertex Inspector (in the Misc. box).
The Vertex Inspector can be used to give vertices names. These vertex names are used in
OpenTrack’s description of routes and paths. Therefore, it is very important to use meaningful
names for the vertices particularly for vertices where routes begin or end. This will assist the
user in understanding and editing train operation descriptions. Typical names include: 01 for
track 1, HOME for vertices with home signals etc.
When using the inspector to enter any text data attributes (e.g. name) the user must press the
ENTER key following inputting the data. This signals OpenTrack that the user is finished
entering data and the attribute is ready to be assigned. Alternatively the “Set Data” button at
the bottom of the inspector can be selected to save text data, but pressing ENTER following
each data input is probably safer.
The Vertex Inspector allows the user to view or edit the following information about the
selected vertex (or vertices):
General - All vertices can have data in this section.
Vertex Name: Name of vertex (see note above regarding naming vertices).
Kilometre Point: KM Reference Point (used as information, not to calculate lengths).
Station Sign: The station abbreviation is shown if the vertex has been grouped into a
station area. See “Defining a Station Area” on page 33.
Station Vertex: Box is checked if the vertex is a station vertex.
“No. of”- Cells: Show number of elements starting at vertex location (routes, paths, iti-
neraries, etc.)
Insulated Joint: Insulated joint at vertex location

Axle Counter: Axle counter at vertex location
Switch - Only vertices that are switches have data in this section. Note that only one side of the
vertex belongs to a switch and has data in this section.
Default Position: When box is checked the switch is currently in the default position. The
default position is taken to be the switch position when opening the
document or at the beginning of a simulation.
[Switch] Click to change switch position from the default position to the oppo-
site position or vice versa.
Switch Time: Switch operation time (default is 0 seconds).
Figure 11: Vertex Inspector
Connector - Only vertices that are connectors have data in this section.
Layout: Name of linked document file (i.e. document with connector vertex that
is connected with the selected vertex).
Connector ID: OpenTrack Identification number for connector vertex on linked docu-
ment.
Misc.
[Rotate Right] Allows user to rotate vertex 90° to the right.

[Rotate Left] Allows user to rotate vertex 90° to the left.

[Vertex Selector] Allows user to select which “side” of vertex is being edited.
Horizontal/Vertical Allows user to preset the direction which the next double vertex to be
inserted will take.
ID, Element: OpenTrack object and safety element ID numbers (cannot be changed
by user).
Set Data - Click this button to save all data in the inspector.
Displaying the Vertex Inspector

• Highlight one or more vertices using the Pointer Tool.
• Click Tools  Inspector.
Editing or Adding Attribute Data to One Vertex

• Highlight the vertex using the Pointer Tool.
• Click Tools  Inspector.
• Use mouse to select location (cell/button) for editing or adding data.
• When finished entering text data in cell press ENTER key.
• When finished entering all data for vertex press Set Data button.
Remember to press the ENTER key after entering text data in any cell, and press the Set Data
key when finished editing the vertex; otherwise the changes will not be saved.
Editing or Adding Attribute Data to Multiple Vertices

It is possible to edit or add attribute data to multiple vertices by selecting the group of vertices
(by drawing a box around them using the Pointer Tool) and entering data using the inspector
tool. The inspector will display empty fields in cells/data elements for which the selected ver-
tices have different attributes. Note that this process will set both “sides” of all selected ver-
tices with the same data.
As with editing single vertices it is important to press the ENTER key after entering text data
in a cell and the Set Data button to save the changes to the OpenTrack files.
OpenTrack will automatically check whether both sides of a double vertex have the same
Kilometre-post data and name when the vertex is inspected. If both sides are not the same this
will be indicated by a "!" displayed before the corresponding text cell.
You can use the Vertex Inspector (Inspector - End) to indicate whether a vertex contains an
insulated joint (Insulated Joint) or an axle counter (Axle Counter).
Vertices with insulated joints or axle counters can be identified by a black dash in the middle
of the double vertex on the infrastructure drawing as shown in the figure below.

Insulated Joints / Axle Counters
Figure 12: Insulated Joints / Axle Counters
These attributes will be used in the construction of Release Groups for routes (Tools  Rou-
tes). When there are insulated joints or axle counters in a route, then the release group ends at
the vertex by default. Users can change these default release groups later using the command
Edit in the route panel (Tools  Routes).
Vertex Representation on Worksheet

Vertices can be shown in two different sizes on the worksheet. Use the following commands to
change the size:
• Format  Show Small Vertices ... changes the vertices from large to small.
• Format  Show Big Vertices ... changes the vertices from small to large.
3.3.2 Station Reference Point (Station Vertex)

In OpenTrack all stations must have a clearly defined reference point. OpenTrack uses a spe-
cial type of double vertex called a Station Vertex for these vertices. The Station Vertex should
be placed at the location of the station building and must be placed on all tracks in the station.
Figure 13 illustrates a station with station vertices on all tracks.
Station A
Figure 13: Station with Station Vertices (Dark-Blue)
Changing an Existing Vertex to a Station Vertex
You can use the Vertex Inspector to change a vertex from a normal vertex to a station vertex
using the following procedure:

• Using Pointer Tool select vertex you want changed to a station vertex.
• Click Tools  Inspector
• Place a Check in the Station Vertex box.

• Set any other vertex attributes using the inspector.

• Press Set Data button to save changes.
3.4 Edges (Sections of Railroad Track)

In OpenTrack railroad track segments are symbolized by lines called “Edges”. In a manner
similar to vertices, edges can be drawn on the worksheet using the palette’s Edge Tool and can
be given attributes using an inspector.
Edge attributes include edge length (edges can be of any length), radius, and gradient. Additio-
nal information such as a description of the tunnel cross section (and/or a tunnel factor: fT
between 0.5 and 50), provision of pilot line (loop), train speed per direction of travel, and
membership of the edge in a safety margin after a signal (overlap) can also be attributed to an
edge.
Edges have a direction which is set based on how the edge was drawn on the worksheet; the
direction will be from the starting (first) vertex to the target (second) vertex. Edge direction is
important because it is used to indicate gradient, radius, and line speed attributes; for example,
a positive gradient on an edge indicates that the second vertex is at a higher position than the
first.
The OpenTrack procedures for showing edge direction on the worksheet and changing edge
direction are outlined below.
Edges can be linked together so that the edges are only occupied or allocated together. An
edge linked to another is a special type of edge called an Exclusion Link (described in more
detail below). An example where an exclusion link can be used is to prevent a station track
(e.g. ST-1) from being used when passengers are unloading from an adjacent track and must
cross the first track (ST-1) at grade to reach the station.
During the simulation reservations and occupations of edges (which train at what time) can be
monitored and evaluated. Details are given in Chapter 8.6: Monitoring the Simulation on page
148.
Procedure to Insert an Edge
• Select Edge Tool on palette (illustrated above).

• Mouse click in starting vertex.
• Keeping mouse pressed move cursor to target vertex.
• Edge is created.
• Set edge attributes in the inspector.
• Press ENTER key after entering text data in any cell.
• Press Set Data button to save changes.

Displaying Edge Direction on Worksheet

• Format Show Direction of Edges.
• Arrow indications appear on all edges.
Changing Edge Direction

• Select Pointer Tool on palette.
• Select edge you want to change direction of.
• Click Tools  Inspector
• Press “Swap” button on Edge Inspector.
• Edge direction is reversed.
Edge Inspector
As with vertices OpenTrack uses a tool called “Inspector” to view and assign attributes to
edges. In the case of an edge this tool is called the Edge Inspector. To display the Edge Inspec-
tor use the command: Tools  Inspector.
Figure 14 illustrates the Edge Inspector. The edge inspector can be used to input or edit the
following edge attributes:
Track - All edges can have data in this section.
Length: Length in metres (Length must be >= 0 metres).

[Cal.]: Button that computes the edge length using vertex data.
Length Sum: Sum of the lengths of all selected edges in metres
Radius: Curve radius in metres (none for straight track section)
Gradient: Gradient in the edge direction (from vertex 1 to vertex 2) in per mill
Tunnel PopUp: PopUp menu for tunnel type:

no Tunnel No tunnel.
Tunnel single, smooth Single track tunnel, smooth tunnel wall.
Tunnel double, smooth Double track tunnel, smooth tunnel wall.
Tunnel single, rough Single track tunnel, rough tunnel wall.
Tunnel double, rough Double track tunnel, rough tunnel wall.
Tunnel (fT = 0.5….50) Tunnel factor for use instead of tunnel type.
Loop: Check box if route section is equipped with a pilot line.

Rack Rail: Check box if route section is equipped with rack rail.
Overlap/Slip: Check box if route section is part of a safety margin after a signal.
Power Supply: Name of the power supply group to which edge belongs (optional).
Link to: If the edge has an exclusion link its ID is shown on this line. An exclu-
sion link can be deleted by pressing the [delete] button. An exclusion
link is another edge that may not be occupied or allocated as long as the
edge from which the relationship comes is allocated or occupied.

Speed (km/h) - All edges can have data in this section.
Speed Table: Table of the permissible speeds per train type and direction of travel
12 and 21 expressed in km/h. The number of train types and their
designations presented in the Speed Table are designated by the user in
the Preferences menu (Info  Preferences).
The user can edit speeds in the table by clicking on the speed to be
changed and then entering the new speed. After entering a new value
press ENTER or the Set Data button to store the data.
Same Speed When the Check Box “Same Speed both Dir” is checked then the speed
from 12 is set equal to the speed from 21.The Copy button can be
used to copy the speeds from one train type to another.
General
Line Name: Optional attribute for a line name (facilitates data exchange via railML
format)
Track Name: Optional attribute for a track name (facilitates data exchange via railML
format)
Edge Name: Edge name (optional)
Misc.
Res.: (Reserved) = Shows for which course the edge is allocated. Special
case: If the user changes the occupation state manually, the string User
appears in this field.
[State] Changes the occupation state of the selected edge from free to alloca-
ted, from allocated to occupied, or from occupied to free
[Swap] Changes the edge direction; vertex 1 and vertex 2 are swapped
by user).
Set Data - Saves new data to OpenTrack files.

Figure 14: Edge Inspector
3.4.1 Safety Elements

Safety elements are sections of track that can generally be occupied by only one train at a time.
Thus in OpenTrack, a safety element comprises one or several edges (with their start and end
vertices) of the network that can only be free or allocated together.
OpenTrack automatically generates safety elements as the track network is input on the work-
sheet. The safety elements are not visible on the worksheet but are generated behind the track
layout. OpenTrack automatically creates safety elements using the following rule:
Edges that touch one another in a vertex belong to the same safety element.
There is one case where OpenTrack’s automatic method of generating safety elements does
not accurately represent the track network, this is the case of at grade railroad crossing. If the
user draws a track edge that simply crosses another track edge creating a rail crossing Open-
Track will assume that this is grade separated. There are two methods that can be used to
accurately create safety elements in at grade rail crossings.
These are:
• Draw crossing by starting with a normal switch between two lines and then remove the

through edge (keeping the switch edge). In this case the joint safety element formed auto-
matically (since both edges were in the same vertex) remains in existence.
• Draw the crossing and use the command: Functions  Merge Elements (see below).
Figure 15: Safety Elements
Figure 15 illustrates safety elements in a track network. As shown in the figure, individual
safety elements can consist of single edges, edges of switches, crossings, slips or double slips.
Safety elements are not displayed on the worksheet, however edges joined in a safety element
can be found either by viewing the ID of the elements (using Inspector tool) or by making a
status change. If the status of one edge in a safety element is changed from free to allocated
(using the Change State command in the Edge Inspector), all the edges belonging to the same
safety element are allocated and OpenTrack highlights all these edges in the same color on the
screen.
Merging Safety Elements

In some cases the user may wish to create larger safety areas (i.e. areas within which generally
only one train can occupy) than OpenTrack generates automatically. The following procedure
can be used to merge safety elements into larger areas:
• Select Pointing Tool on the palette.

• Select Elements to be Merged by drawing box around the desired elements.
• Select Functions Merge Elements.
Resetting Safety Elements (to OpenTrack Default Safety Elements)

In some cases the user may wish to reset selected safety elements to the OpenTrack automati-
cally generated (default) definitions. The following procedure can be used to reset selected
safety elements into the OpenTrack default definitions:
• Select Pointing Tool on the palette.

• Select Elements to be resetted by drawing box around the desired elements.
• Select Functions Reset Elements.
Inserting an Exclusion Link

The procedure used to create an exclusion edge is as follows:
• Select Arrow Tool on palette.

• Select edge from which the link comes.

• Open edge inspector.
• Press New button next to title Link.
• Click on starting edge and keep holding down mouse button move cursor to the target edge
(edge to be linked).
• Link is created (target edge will change color).
An exclusion edge describes a relationship between one edge and another. If an edge K1 has
such a relationship to an edge K2, then edge K1 can only be allocated for a train if the edge K2
is also free and can be allocated simultaneously.
3.5 Connector Vertices

Connector vertices enable the user to break-up the display of a track network to different
places on a worksheet or to continue a track network on another worksheet document.
Connector vertices are used to represent the “same” point on two track networks. Using
connectors enables the user to provide a better visualization of track networks and to simplify
data management.
OpenTrack illustrates connectors using a special vertex icon which consists of a square next to
a diamond shape (rather than two squares side-by-side as in a regular vertex).
The process for connecting two track layouts consists of three steps. First, the user defines two
track layouts on the same or different worksheets using the techniques described earlier in this
manual. Second, the user designates one of the vertices on each track layout as a connector
vertex. Third, the user links the connector vertex on the first layout to the target connector ver-
tex on the second track layout. Steps two and three are described below.
In order to interlink two connectors, both worksheets must have valid file names (Untitled is
not a valid file name). Vertices that are converted into a connector may not have an adjacent
edge or a signal. A signal may not be allocated to adjacent vertices of connectors.
As described in Chapter above, the Vertex Inspector contains fields that display the Layout
(filename of the worksheet where the layout is continued) and Connector ID (OpenTrack iden-
tification number for the target vertex on the worksheet where the layout is continued). The
user can view this information using the Vertex Inspector.
Inserting a Connector
• Select Connector Tool from palette (illustrated above).

• Mouse click in existing vertex on first worksheet.
• Vertex is converted into a connector vertex.
• Repeat process to create a connector vertex at an existing vertex on the second worksheet.

Linking Connectors
• Make certain that both layout worksheets (files) are open and have valid filenames.
• Select Connector Tool or Edge Tool from Palette.
• Mouse click in connector 1.
• Holding mouse button down drag connector 1 into connector 2 on second worksheet.
• Connection is made - You can use Vertex Inspector to check.
3.6 Signals
OpenTrack uses two different types of signals: signals with changing information (light
signals, beacons) and halt position indicators. The light signals are subdivided into main
signals (signals that can show stop), distant signals (signals without stop aspect), combined
signals (combination of main and distant signal) and shunting signals. Main signals (including
combined signals) can be further subdivided into home, exit and block signals.
Virtual signals do not have a corresponding installation on the route, but are merely used to
show the safety technology (for example discrete block division in case of the cab signaling).
The halt position indicators characterize a position in a station or at a stop, at which a train
having a given length is to stop. OpenTrack allows the user to distinguish between many
length graduations (10 m ... 1000 m) and a general halt for all trains. During the simulation an
entering train stops at the appropriate position given its length.
OpenTrack represents main and distant signals on the worksheet either by means of general,
land independent icons or by means of the usual signal icons for so called Aspect Signaling
(e.g. UK). All types of signals used in OpenTrack are illustrated and described in Figure 16.
OpenTrack treats signals similar to other track layout elements (e.g. vertices, edges) and
allows the user to place signals on the worksheet using a graphical editor and to set signal
attributes using the Inspector tool.
Inserting a Signal
• Select the Signal Tool from the palette (illustrated above).

• Mouse click in the vertex to receive the signal (remember vertices have two “sides” and so
click on the appropriate side for the direction you want the signal to control).
• The signal is generated.
• Set signal attributes in the inspector.

Showing Signal Type on Worksheet
OpenTrack can display different signal icons to distinguish between types of signals. This can
be done using the Inspector. An easy way to show the type of signal on all worksheet signals is
to use the following process:
• Edit Select All.

• Edit Subselect Signals.
• Signal Inspector appears on screen.
• Click box: Show Symbol.
• Signal type icons appear at all signals.
Signal Types
Main Signal
(can show Stop)
Main Signal 2-Aspect
(can show Stop)
Distant Signal
(shows the State of the next Main Signal)
Distant Signal 2-Aspect
(shows the State of the next Main Signal)
Combined Signal
(Combination of Distant and Main Signal)
Combined Signal 3-Aspect
Combined Signal 4-Aspect
Line with Cab-Signalling
(Begin, End)
Line with Speed Optimization
(Begin, End)
Balise, Beacon (transmits State of the next
Main Signal to the Train)
Speed Restriction, Speed Information
(Begin, End)
Shunting Signal
P
Performance Signal
C
Power Off, Power On, Coasting Signal
General Halt for all Train Lengths

H C T
(Ref. Point. H:Train Head, C: Train Center T: Tail of Train)
1 ... 8 Halt for certain Train Lengths (10 .. 1000 m)
Wind Signal, Resistance Signal
Crossing Barrier, Grade Crossing
Figure 16: Types of Signals used in OpenTrack

Signal Inspector
The Signal Inspector can be used to edit or set attributes of signals. One or a group of signals
can be selected using the palette’s Pointer Tool. Then the Signal Inspector window can be dis-
played using the command Tools  Inspector. Figure 17 illustrates the Signal Inspector.
Type - This box describes the signal type.
Type PopUp: PopUp-Menu for signal type, following types available:

Main Signal Main signal
Main Signal 2-Aspect Main signal 2-Aspect
Main / Distant Signal Main and distant signal
(combined signal)
Main / Distant Sig. 3-Asp. Main and distant signal 3-Aspect
Main / Distant Sig. 4-Asp. Main and distant signal 4-Aspect
Distant Signal Distant signal
Distant Sig. 2-Asp. Distant signal 2-Aspect
Balise / Beacon ETCS balise, beacon
CAB-Signal Indication for segment with cab signaling
OPT-Signal Indication for segment with speed opti-
mization
Speed Restriction Indication for segment with speed restric-
tion
Requested Speed Requested speed is indicated when
passing the signal
Performance Signal Local Performance Value in %
Performance Cat. Signal Local Performance Value in % per train
category
Power Off Signal Beginning of track segment without
power (Electric locomotives can no
longer accelerate)
Power On Signal End of track segment without power
Coasting Signal Coasting (within a speed range with an
upper and lower speed limit)
Shunting Signal Shunting signal
Stop ... (general) General halt position
Stop 10m... 1000m Halt position dependent on train length
Wind Signal Actual wind strength in km/h (this will be
used in computing the actual train
resistance)
Resistance Signal Additional resistance value in kN (this
will be used in computing the actual
train resistance)
Level Crossing At grade roadway/railway crossing
Gate / Barrier Grade crossing with barrier
Unspecified Signal Unknown signal type (this can be used
especially when exchanging data with
other programs, e.g. via railML)

Type Selection: Additional description of the main signals

Home Signal Home signal
Block Signal Block signal
Exit Signal Exit signal
Show Symbol Check this box to display signal type on the worksheet
Signal is virtual Check this box to indicate that the signal is a virtual signal
Show Icon Check this box to display signal icons on the worksheet
Show Icon Menu PopUp menu to for the type signal icon
Display - This box describes characteristics of the signal.
Aspects Menu: PopUp menu for the kind of display of the main signals:
Speed Speed is shown.
Indication SBB Speeds follow from lamp combination (System
SBB).
Indication NS Speeds based on NS (Netherlands) signaling
system.
Universal (Metric) Speed based on metric levels (km/h).
Universal (US) Speed based on US system (mph).
Aspects List: Selection list of possible speeds that can be displayed on the signal. All
the aspects (signal states) that can be shown by the signal (independent
of the route to which it is allocated) are listed here. Double click on the
aspect to select or unselect it for the signal being edited.
Sight: Distance at which the locomotive driver can act on the information
from the next signal (in meters).
Allow Entry : Check box to indicate that trains can pass a main signal despite occu-
pied track elements ahead.
Spec - This box displays special characteristics of the signal.
Warning Speed: Speed which a train must maintain after passing the second closed
distant signal in consequence, until the next open main signal is passed
(Optional).
Release Speed : Release speed in km/h for beacons. A train monitored once by a beacon
has to free itself from monitoring either by braking to below the release
speed or by passing a pilot line reporting to the train that the monitored
position of conflict can be passed.
Rel at Balise Loc: In the case of Release at Balise Loc. only the observed train is not allo-
wed to accelerate after reaching the allowed speed and is only allowed
to accelerate again at the next balise or on the next loop.
Dist. Sig Balise: Describes whether the balise also transmits information about the
distant signal.
Acc. forbidden: Signals that indicate that acceleration is forbidden
Use Performance: Attribute for Speed Restriction Dist. Signals, Speed Restriction Startsi-

gnals and Requested Speed Startsignals; use the actual performance of

the course or not.
Dispatching: Dispatching type for this signal (see also Chapter : Dispatching at
Signal Groups on page 125)
Keep closed: For exit signals: Determines whether an exit signal should remain clo-
sed for a train approaching the station that is making a station stop, or if
the exit route should already be set, when that allows at the entry signal
a higher priority train movement.
Signal Name: Signal name (optional)
Figure 17: Signal Inspector
Misc.
[<->] Press button to change track side at which signal is placed. This is for
purposes of worksheet display only, the signal still is associated with
the original direction of travel.
[ < ] and [ > ] Press button to move the signal to the adjoining vertex (can be depres-
sed multiple times to move signal over several vertices). You cannot
move a signal over another signal or over a switch.
[Change State] Click this button to manually reserve sections of track controlled by the
signal. When a track section is reserved in this manner a red box outli-
nes the signal icon.

by user).
Example: Universal Signal System (Metric)

The signal system Universal (Metric) is a general multi-aspect system, which represents speed
relevant signal information in km/h. Speeds apply from the signal's Proceed-Indication or
from the start of an optionally defined Slow Speed Zone, the Approach-Indication allows a
brake application to the displayed speed, in case a train passes the signal with a higher speed.
Signal Aspect Meaning Def. in OpenTrack

Clear Free to drive at segment maximum speed Track Speed
Proceed v Drive at speed v from signal position (or P v (e.g. P 50)
from the beginning of a user defined
optional Slow Speed Zone)
Approach v The speed v should be expected at the A v (e.g. A 50)
next signal. Trains with a speed greater
than v should reduce speed from the sig-
nal position to the speed v
Advance Approach v The speed v should be expected 2 signals AA v (e.g. AA 50)
ahead. Trains with a speed greater than v
should reduce their speed from the signal
position to the speed v
Stop Stop No further definition
needed, all main sig-
nals can show stop.
Example: Performance Signal

The signal's Performance factor also affects train simulation. The accelerating power and the
future maximum speed of a train both depend on the signal's Performance [%]. The delay
dependent performance factor (Tools - > Courses/Services) impacts accelerating power and
future maximum speed in the same manner.
If the performance signal is given the attribute Acceleration Forbidden this prevents a train
from further acceleration until the next performance signal is passed (provided it does not also
have the Acceleration Forbidden setting) or until the train comes to a stop.
Example:
Last Signal Passed - Performance Factor: 80%

Performance (on Time): 93 %
Track Segment Speed Limit: 100 km/h
Train Calculated Speed Limit: 100 km/h * 0.8 * 0.93 = 74.4 km/h

Example: Coasting Signal

The Coasting Signal allows train to coast on a given section of track, the signal defines the
allowable coasting behaviour, i.e. the train can accelerate to an upper coasting speed (Upper
Speed [km/h]), then the power can be turned off allowing the train to roll freely until it reaches
the lower coasting speed (Lower Speed [km/h]), aat which point the power is switched on
again.
Figure 18 illustrates an example with an upper speed set at 60 km/h and a lower speed set at 55
km/h.
[km/h]
80
70
60
50
40
30
20
10
0
0 1 2 3 4 5 6 [km]
Station A
Station B
Figure 18: Coasting
Coasting signals have a delay attribute (Delay <= [s]). This attribute means that coasting
signals are only valid for trains whose actual delay is smaller than, or equal to, the defined
delay value. It is also possible to make the coasting process dependent on the amount of delay
by defining a sequence of coasting signals with different delay values (e.g., 0s / 10s / 20s).
Example: Use of Track Beacons (Balises)

Beacons enable a direct transmission of signal indications to the locomotive. If the next signal
after the beacon shows a restrictive indication, the braking towards this signal is monitored.
The locomotive driver can only free himself from the monitoring if he reduces the speed so
much that it is below a minimum speed (for example 40 km/h) or if a message saying that the
monitoring is cancelled because the restrictive state of the main signal has changed to a less
restrictive state. Such a message is given to the engine via the passing of an additional beacon
during the braking or via pilot lines within the range of vision of the signal.

[km/h]
130
120
110
100
90
80
70 Train 3
60 Train 2
Train 1
50
40
30
20
10
0
28 29 30 31 32 33 [km]
Train 1
Train 2
Train 3
D1 S1,D2 S2
Figure 19: Train Behaviour at Beacons
Figure 19 shows the behaviour of three trains running on track systems differently equipped
with beacons and pilot lines for the monitoring of train brakings to comply with signal indica-
tions. In all three scenarios the train passes the open home signal S1, which is provided with a
beacon and which contains the additional information of the distant signal D2 that the exit
signal S2 is closed. Train 1 is brought to a standstill at signal S2 because continuation of the
journey was excluded due to the occupation of the next part of the route within the braking
process.
In case of trains 2 and 3 the state of signal S2 changes from halt to proceed shortly after the
trains pass the home signal S1. In case of train 2 the braking must be continued until the speed
has dropped below the limit of 40 km/h in order to free the train from the monitoring (since the
exit signal was not supplemented with a zone equipped with a pilot line). In the case of Train
3, braking can be ended as soon as the train passes the pilot line 200 m before the signal (sight
distance of the signal equals the length of the pilot line). The pilot line transfers the new, less
restrictive state to the train.
The attribute Release at Balise Loc. only can be used to better control how an approaching
train behaves when a signal clears. This is relevant in the context of automatic braking super-
vision by means of transponders (such as balises).
Consider a train approaching a signal showing stop or that there is a reduced speed ahead; if
the signal then changes to proceed freely two options are possible: when the attribute Release
at Balise Loc. only is selected the train continues at the release speed until it reaches the balise
location where it can then begin to accelerate, in contrast, if the Release at Balise Loc. only
attribute is not selected then the train slows down to the Release Speed and accelerates to the
track speed as soon as the signal changes .
The attribute Distant Signal Balise can be used to instruct balises to differentiate whether or
not they transfer pilot signal information in addition to current signal information. If a balise

does transfer pilot signal information, then OpenTrack tries to open the distant (main) signal
(for which the pilot signal information of the balise applies) before or during passage of the
train over the balise so that no restrictive drive information must be conveyed to the train.
One reason not to equip a balise with the distant signal information would be if the distance to
the next main signal is very large (much larger than the train braking distance) to prevent that
signal from being opened unnecessarily early.
3.7 Stations
OpenTrack uses two methods to manage station data: a station database and as worksheet
objects. The station database contains properties of as many stations as possible and is availa-
ble to all users. Such information includes station name, abbreviation, rail administration data,
height above sea level, territorial coordinates etc.
When creating a track network the user places stations on the worksheet using the palette’s
Station Tool. Then, using the inspector, the user sets station attributes including a linkage to
the stations database. Station attributes assigned using the Inspector include such as kind of
station (manned or unmanned, stop, service location) and type of signal box. A station cannot
be placed on a worksheet until it has been first entered into the station database. Stations
include passenger stations, train stops and service locations.
Inserting a Station
• Select station tool from palette (illustrated above).

• Mouse click on the worksheet.
• Station object is generated.
• Set station attributes in the inspector
3.7.1 Station Inspector

The Station Inspector is used to edit or set attributes of stations. The Station Inspector window
can be displayed by selecting a station and then using the command Tools  Inspector. Figure
20 illustrates the Station Inspector.
Station - This box presents information from the station database for the particular station and
allows the user to set certain information about the station.
Station list: Selection list of all stations in the station database. Double click on a
station in the list to assign the station name to the selected station on the
worksheet. Station names can be found either via navigation in the list
or by inputing a search string in the Search field.
Type selection: Station manned Station manned

Station unmanned Station not manned

Halt Halt position
Service Service location
Depot Depot location
Junction Junction location
Block Post Block Post location
Signal Signal location
Signal box sel.: None No signal box

Mech. Signal Box Mechanical signal box
Electromech. Signal Box Electromechanical signal box
Electric Signal Box Electric signal box
Electronic Signal Box Electronic signal box
Show Icon: When this box is checked the station icon is shown on worksheet.
Figure 20: Station Inspector
Station Sign: Station abbreviation (comes from the station database)

Coordinates: Territorial coordinates and/or world-coordinates (latitude, longitude)
(comes from the station database)
Height a. S.: Height above sea level (comes from the station database)

Misc.
[Rotate Right] Allows user to rotate station icon 90° to the right.
[Rotate Left] Allows user to rotate station icon 90° to the left.
[Show] Clicking this button causes the vertices grouped with the station to be
highlighted on the document.
[Label] Click this button to display the station name on the worksheet.
by user).
3.7.2 Defining a Station Area

Defining station areas in OpenTrack eases visualization of the network and improves data
management. Station areas consist of any number of double vertices, edges and signals as well
as exactly one station icon. The following procedure can be used to define station areas:

• Draw a box around all elements to be included in station area.
• Select Functions Group Station Area.
Following this procedure all objects in the station area will have the station abbreviation inclu-
ded in their attributes.
Elements in a station area can be ungrouped using the command:
• Select Functions Ungroup Station Area.
3.7.3 Representing Stations with OpenTrack

The station area generally encompasses the area from the entry signal on one side to the entry
signal on the other side of the station. Figure 21 illustrates this type of station area.
In the simplest case (e.g. with a single stop) the station area contains only the station icon, the
station vertex, and the vertices with the train halt points (halt boards). (Note that the edges bet-
ween vertices in the station area are also included in the station area.) It should be noted that
during a station stop a train is located completely within the station area.
The station vertices must be set in such a way that each path through the station passes through
exactly one station vertex. The station vertex represents the Kilometre reference point from
the station database on the OpenTrack worksheet. (The station database information is gene-
rally from the railroad’s infrastructure department and represents the location of the station
building.) In addition to its use as a geographic reference point, the station vertex is displayed
on evaluations made with OpenTrack such as the graphical timetable.

Area of Station Y
Station Y
S1 S3 S7
7
S2
H
S5 S9
S4
7
S6 H
Home Exit Stop Station Stop Exit Stop Exit Home

Signal Signals general Location 400 m Signals 700 m Signals Signal
Figure 21: Station Area
When considering stations with main signals the user should pay particular attention to setting
the type of main signal (e.g. home signal, exit signal) since different signal types have diffe-
rent functions. For example, at home signals it is possible to define a sequence of train arri-
vals (see Chapter 6.3: Connections on page 106). Similarly exit signals can be station halt
points for trains and also used for connection points and to define train sequences.
OpenTrack computes the optimal entry path and halt point for stopping a train in a station
based on the train length. Trains can stop at main signals and halt points. Among main signals
first priority is given to exit signals; home signals or block signals are only considered as stop
points if they are in the train’s travel direction and located following the station vertex. This
means that every station in OpenTrack must have at least one halt signal or main signal per
track and per direction.
For example, for trains arriving from the left (Home Signal S1) on the upper track illustrated
in Figure 21, OpenTrack would make the following stop location assignments:
• Exit Signal S7 for trains with a length over 700 meters.

• Halt Point [7] for trains with a length between 400 and 700 meters.
• Halt Point [4] for trains with a length of 400 meters or less.
The search for a stop location begins at the most distant main signal that is on the opposite side
of the station area. All halt points and main signals are candidates for stop locations. In this
example the Exit Signal S7 is found first and assigned as the default stop point for all train
lengths. Next the halt point [7] is then identified then for trains with a length of less than 700
meters, and the halt point [4] is identified as the optimal stopping point for trains with a length
of 400 meters or less.
3.7.4 Station Database (Stations)

A station database comprises a collection of station data sets in which the station name, the
abbreviation, the distinctive number of the rail administration, the distinctive number of the
unit next below, the territorial coordinates and the height above sea level are managed. Figure
22 illustrates the station database.

The station database is not set up anew for each OpenTrack project, but is a growing data file,
the entries of which can always be accessed. It is also possible to read in a complete station
collection (for example all stations in Switzerland) from an external file.
Figure 22: Station Database
There can exist several station databases side by side (for example one per country: Switzer-
land.stations, Austria.stations, Germany.stations, ...). The user can select which station data-
bases are available using the preferences command (Info  Preferences), see Chapter 8.1:
Preferences on page 127.
ID: Station ID, Station code, Abbreviation (must be unique)

Name: Station name
Type: User defined description (for example, for station type)
Timing: Indication whether station is a time comparison station (trains wait for
departure time only at time comparison stations)
Comp. ID*: Station ID number from rail administration
Dept. ID*: Station ID number from the local administration
Coord X*: X coordinate (in metres)
Coord Y*: Y coordinate (in metres)
Longitude*: Geographic longitude (in degrees)
Latitude*: Geographic latitude (in degrees)
Height a. S.*: Height above sea level
Search field: Search field (the station name is selected in which the entered combination
of letters is found)
Update changes: Changes in station ID will also be shown in schedule
Show Timing St.: Check box to display the time comparison stations
[Next] Search for the next station name or abbreviation in which the string in the
search field is found

[Sort] Sorts the entries (after ascending station abbreviation or station name)
[New] Records a new station (is added right at the bottom and can be edited
directly in the table)
[Find] Opens the finder panel based on the selected station
[Show Itin.] Select all the active itineraries (Itineraries) in the itinerary panel (Tools 
Itineraries) traveling through a selected station.
[Save DB] Stations are written in the database (happens automatically after termina-
tion of the application)
[Delete] Selected station is deleted
* Optional entries (do not influence the basic functionality of OpenTrack, but
can be used in future evaluations).
The stations database includes the attribute Timing Station (time comparison station). At time
comparison stations a train always waits for a defined departure time, at other stations trains
can depart as soon as they have stopped for the minimum dwell time. By default all stations
are time comparison stations. For each timetable entry (Tools  Timetable) users can specify
whether a time comparison takes place or not.
The checkbox Show Timing Stations can be used to display or fade-out information about time
comparison stations.
3.8 Power Supply Area

OpenTrack allows the user to define power supply areas on the worksheet and provide them
with attributes. The areas are defined in a manner similar to station areas and the Inspector tool
is used to provide attributes.
The most important attribute of a power supply area is the type of power provided in the area.
OpenTrack includes over 35 different power supply systems (e.g. AC 15 kV 16 2/3 Hz, DC
3000 V, etc.) as well as user defined custom types. OpenTrack also includes power types for
magnetic levitation trains.
The power supply designation “none” defines explicitly locations with no traction energy (e.g.
insulated sections). In these sections only trains that move under their own power (e.g. diesel
locomotives) can operate.
Figure 23 illustrates the modelling of a current system change. The area around Station A is
equipped with 15kV alternating current and the area around Station B is equipped with 1500 V
direct current. An insulated (dead) section with no contact wire current must be placed bet-
ween the two sections.
Track sections (edges) which are not assigned to power areas are considered as electrified
(universal electric). All traction types (diesel or electric) can operate on these sections of
track.

Figure 23: Power Supply Change - Insulated Section
Inserting a Power Supply Type
• Select Power Supply Tool from palette (illustrated above).

• Mouse click on worksheet at location for power supply icon.
• Power supply icon appears on worksheet.
• Set attributes of power supply using inspector.
Defining a Power Supply Area
A power supply area consists of double vertices, edges and signals as well as exactly one
power supply icon. All the track in this area has the same power supply. The following proce-
dure can be used to define a power supply area:

• Draw a box around all elements to be included in power supply area.
• Select Functions Group Power Supply Area.
Power Supply Inspector

The Power Supply Inspector is used to set attributes of power supply areas. The Power Supply
Inspector window is displayed by selecting a power supply icon using the palette’s Pointer
Tool and then using the command Tools  Inspector. Figure 24 illustrates the Power Supply
Inspector.

Figure 24: Power Supply Inspector
General - This box includes the text field “Name” which allows the user to assign a name to
the power supply area.
System - This box allows the user to select the type of power system provided in the area using
the selection of types provided by OpenTrack.
Visualization - This describes how the power supply area is displayed on the worksheet.
Color: Click button to choose a color for edges and power supply icon.
Show Icon: When box is checked power supply icon is displayed on worksheet.
Color Edges: Menu allows user to choose when track sections (edges) in power sup-
ply area will be outlined in selected color. Choices: Never, Always, and
Simulation.
Prop. Segment: Definition of Maglev propulsion segments.

Prop. Seg. Group: Definition of Maglev propulsion segment groups.
Misc.
[Rotate Right] Allows user to rotate power supply icon icon 90° to the right.

[Rotate Left] Allows user to rotate power supply icon icon 90° to the left.
[Show] Clicking this button causes the vertices grouped in the power supply
area to be highlighted on the document.
[Label] Click this button to display the power supply name on the worksheet.
by user).
[Set Data] Saves new data to OpenTrack files.
3.9 Additional Worksheet Objects
3.9.1 Instrument Windows

Measuring instrument windows show data on trains passing a vertex during the simulation
process. Figure 25 illustrates a measuring instrument window. Users can place measuring
instruments on the worksheet at any vertex. The measuring instrument window shows course
number, actual speed and the headway of trains passing through the vertex.
The measuring instrument window’s headway display can be changed between headway and
pass through time (i.e. how long it took the train to go by the point) by double-clicking on the
time field in the window.
#: 20001
v: 115 km/h
dt: 00:02:15
Figure 25: Measuring Instrument Window
Inserting a Measuring Instrument
• Select Instrument Tool from palette (illustrated above).

• Mouse click in the vertex.
• Diagnosis window is created.
Measuring Instrument Inspector

Name: Name of measuring instrument
Show Name: Show name of measuring instrument
Show Course ID: Show course ID
Show Speed: Show speed
Show Time: Show passing time of the last train
Show Headway: Show train headway
Show No. of Trains: Show number of trains passing the instrument
Show No. of Switch Op.: Show the number of switch movements/operations (for measuring
tools associated with switches)

Show No of Sig. Stops: Show the number of unplanned stops at the signal (for measuring
tools placed on main signals)
Data Collection: Direction of data collection (None: no data collected; Forward:

data collected in the forward direction; Backward: data collected in
backward direction; Both: data collected in both directions, Head:
monitor and record the front of a passing train, Tail: monitor and
record the rear of a passing train)
Size-Menu: Measuring tool size

Show Instrument: Show measuring tool
Color Instr. Background: Tool background color
Color Text Background: Text background color
Highlight Instrument: Highlight measuring tool
Vertex: ID of the vertex where the measurement instrument is located

Edges: IDs of the edges that are evaluated with the measurement instru-
ment (not available in OpenTrack standard version)
ID: Identification number of the measurement instrument
Figure 26: Measuring Instrument Inspector

Measuring tools associated with switches can show the number of switch movements/operati-
ons during the simulation period. To activate this function check the box Show Number of
Switch Op. in the Inspector.
Measuring tools placed on main signals can display how many trains have come to an (unplan-
ned) stop at the signal. To activate this function check the box Show Number of Sig. Stops in
the Inspector. The measurement tool’s output file will report the number of trains and the
amount of time spent stopped at the signal. The time spent stopped at the signal is also dis-
played on the measuring tool upon completion of the simulation.
3.9.2 Plot Objects (Plot)

Plot objects enable graphical evaluation of simulation results. During a simulation OpenTrack
stores data in a (virtual) tachograph. Following the simulation this data can be plotted. A plot
object comprises plots (functions) and legends for the X and Y axes.
[km/h]
140
130
120
110
100
90
80
70
60
50
40
30
20
10
0
0 10 20 30 40 50 [km]
Zetthausen
Ypslikon
Pewald
Iggswil
Figure 27: Example Plot (speed/distance diagram)
Inserting a Plot
• Select Plot Tool from the palette (illustrated above).

• Set up a rectangle on the worksheet to generate a plot.
• Empty plot is generated.
• Functions and legends can be inserted by means of drag & drop or using “Add” button on
the Plot Inspector (OpenTrack Output-Files).
• Set plot attributes using the inspector.
Plot Inspector
The Plot Inspector is used to set attributes of plots. Display the plot inspector by selecting the
plot and using the command Tools  Inspector. Figure 28 illustrates the Plot Inspector. The

Plot inspector displays the following plot attributes:
Plot - List of all the functions and legends included in the plot. By checking OD (Overwrite
Data) the evaluation will be updated after every simulation run. By checking PO (Plot Online)
the plot will be drawn while the simulation is running. Attributes of the selected function are
shown (line width, line color) and can be modified. The user can add plots to this list using the
Add button.
Width: Line width of the selected plot.

Color: Line color of the selected plot.
Dash: Dashed line.
[Add] Click this button to display a window that presents courses that will be
monitored and the type of plot that will be made. This allows the user to
insert predefined functions per course (for example route/time diagram,
speed/distance diagram).
[Delete] Deletes the selected plot or the selected legend.
[Del. All] Deletes all selected plots and legends.
[Rotate] Rotates selected legend.
[Flip] Assigns selected legend to the other axis.
Visible Rectangle - The fields in this box allow users to control attributes of the plot. Remem-
ber to press ENTER or Set Data to save changes when entering data in text fields.
Min. X, Min. Y: Smallest functional value shown in the plot.

Max. X, Max Y: Highest functional value shown in the plot.
Leg. X, Leg. Y: Axis legend (units).
Grid switch: M: main axis grid, D: detail axis grid, S: station grid.
Font Size: Font size.
Border: Line width of the plot border (width = 0  no frame).
Border color: Line color of the plot border.
Fill switch: Selection whether the plot object is to be filled with color.
Fill color: Fill color of the plot object.
Misc.
Autoscale: Performs automatic scaling of the axes.

ID: OpenTrack object identification number.
[Set Data] Saves new data to OpenTrack files.

Figure 28: Plot Inspector
OpenTrack can display additional information in the (platform) occupation charts, such as the
time values and actual/planned times. Times can be displayed in different formats.
Display times (Show Times):
• Actual arrival and departure or transit times;

• Planned arrival and departure or transit times;
• Occupation (upper bar);
• Reservation (lower bar);
• The duration of the reservation or the free time;
The time formats that can be displayed are:
• M (minutes)
• S (seconds)
• MM:SS
• MM.SS

Arrows (Arrows) can be displayed for:
• Actual times (black)

• Actual (black) and planned times (gray, only for arrival and departure times or transit time)
The up-arrow is used to show arrival, the down-arrow for departure or transit.
SE75000
STATY 01
10:38 15:00
IC4001 RE10001 IC4003 FR35001
STATY 02
(13:22) 30:42 31:12 (43:38) (50:51)
RE10000 IC4000 FR35000 IC4002
STATY 03
5:02 5:32 (17:49) (32:42) (47:49)
08:00 08:10 08:20 08:30 08:40 08:50 09:00 Time
Figure 29: Platform Occupation Chart (time format MM:SS)
The context menus (right mouse click) on the occupation chart provides quick access to the
course (Tools  Courses) and the timetable (Tools  Timetable) based on the point of the mouse
click (or the selected object underneath the click on the diagram).
3.9.3 Graphical Elements

OpenTrack allows the user to input graphical elements on the worksheet in order to help visua-
lize the track network or present other information. These elements are merely for illustrative
purposes and do not impact the simulation. The three basic forms of graphical element are the
line, the rectangle and the circle, which can be provided with various attributes (size, line
width, color). Each of these elements has its own icon on the palette.
Inserting a Graphical Element
• Select the desired tool (line, rectangle, circle) from the palette (tools illustrated above).
• Draw the element on worksheet.
• Graphical element is generated.
• Set element attributes using the Graphic Inspector.
Graphic Inspector
The Graphic Inspector works in the same way as other OpenTrack inspectors. Use the pointer
tool from the palette to select a graphic element and the Graphic Inspector appears automati-
cally (or select Inspector from the Tools menu). The Graphic Inspector is shown in Figure 30
and has the following functions:
Linewidth: Line width (1.0 ... 5.0)

Line Color Line color

Fill switch: Selection whether the object is to be filled with color

Fill color: Fill color
Size: Size of the element (W = width, H = Height)
Position: Position on the worksheet (X, Y coordinates)
ID: OpenTrack element identification number (cannot be changed by user)
As with all Inspector tools, after entering text data (e.g. size, position data) press ENTER or
Set Data to display and save your changes.
Figure 30: Inspector for Graphical Elements (Lines, Rectangular and Circles)
Text
Text can be freely placed and formatted in OpenTrack documents. Character font, type size
and font style can be changed with Format  Font.

Inserting Text
• Select text tool from pallet (illustrated above).

• Mouse click on the worksheet (text cursor appears).
• Enter text.
• Set element attributes in the inspector.
Text Inspector
Justification: Justification (left, centred, right)
Text Color: Color of the text
Fill Color: Color of the text background
Fill switch: Information whether the background is to be activated
Temp. switch: Information whether the text is only temporary (temporary texts can be
removed by selecting Functions Remove temp. Labels)
Rotate buttons: Rotates the text by 90° to the right or left
ID: OpenTrack identification number of the object
Figure 31: Text Inspector

3.9.4 Images (Photos-Drawings)

OpenTrack allows users to import vector and bit-mapped graphics (.tiff, .eps) directly into
OpenTrack documents. These graphics can then be moved and expanded using the Image
Inspector.
Inserting Images on OpenTrack Documents

• Insert graphics file in the worksheet by means of drag & drop or copy it into the document
via the pasteboard.
• Picture is generated in its original size.
• Bring the picture to the desired size.
Exporting a Picture from an Open Track Document

• Select a picture.
• Copy the picture into the pasteboard.
• Insert the picture in another application from the pasteboard.
or
• Save the document as a graph via Document  SaveTo
Image Inspector
The Image Inspector works in the same way as other OpenTrack inspectors. Use the pointer
tool from the palette to select an image and the Image Inspector appears automatically (or
select Inspector from the Tools menu). The Image Inspector is shown in Figure 32 and has the
following functions:
Size: Size of the element (W = width, H = height)

Position: Position on the worksheet (X, Y coordinates)
[Original] Brings the image to the original size
[Natural] Brings the image to the original proportions
PDF-Image: Permits leafing through multilateral pdf picture (only MacOS)
Rotate buttons: Rotates the text by 90° to the right or left
ID: OpenTrack identification number of the object
As with all Inspector tools, after entering data in a text field (e.g. size, position data) press
ENTER or Set Data to display and save your changes.

Figure 32: Image Inspector
3.10 Behaviour of Objects on the Worksheet

• Placing
During insertion, objects are justified to a grid lying under the worksheet. This grid can be
made visible (Format  Grid  Show Grid). The mesh width of the grid can also be chan-
ged in the grid panel.
• Selection of Objects on Worksheet
Use the Pointer Tool in the palette to select worksheet objects. When the Pointer Tool is
active, an object is selected as soon as a mouse click is made within its limits.
Selected objects are shown with a selection box on the worksheet.
The Pointer Tool can also be used to draw a rectangle on the worksheet which serves to
select all the objects lying in the rectangle. Objects can be removed or added to the
selected group by holding down the shift key and clicking the mouse on the object you
want to add to, or delete from, the group.

Selected objects can be moved on the worksheet or the appropriate Inspector can be ope-
ned to view, add, or edit attributes of the object or group of objects.
• Moving Objects
Most objects can be relocated on the worksheet (following the grid). Edges are relocated
automatically as soon as one of the end points are relocated.
• Changing the Size of Objects
Some objects (pictures, graphic elements, plots) can vary their size. The new size is defi-
ned by the relocation of an edge point.
• Copy and Paste
OpenTrack uses the pasteboard for the cut out, copying or reinsertion of objects. All the
selected objects are copied into the pasteboard via Edit  Copy. All the objects in the
pasteboard are inserted into the worksheet via Edit  Paste.
The exchange of pasteboard data with other applications is possible. If a picture or a text
lies in the pasteboard, OpenTrack creates the corresponding object after an insertion
process.
If another (graphic) application inserts a pasteboard object generated by OpenTrack, a

postcript or bit-mapped image is inserted that represents the OpenTrack object.
• Delete
Objects can be removed from the worksheet either using the command: Edit  Cut
(objects cut out go into the pasteboard) or using the commands: backspace or delete
(objects are deleted immediately).
Vertices can be deleted with shift delete or shift backspace so that the edge connections of
the adjacent vertices are not lost.
Context Menus
Click the right mouse button on an object to display a context menu. The context menu corre-
sponds to the type of object selected. The menu items are the same as in the main menu.
The following objects now have corresponding context menus:
• Worksheet
• Vertices
• Edges
• Signal

Further context menus exist for train diagrams and for various tables (e.g. timetable, courses,
etc.).
3.11 Alternative Methods to start OpenTrack
3.11.1 Starting OpenTrack with a Parameter File

Call:
OpenTrack.exe -runfile="<aRunFileName>"
The parameter -runfile can be used independently of Scriptmode (see Chapter 3.11.3 and
Chapter 3.11.4). This allows users to define all the OpenTrack parameters (preferences, simu-
lation parameters, infrastructure documents, graphic timetables, incidents) in a text file (a
socalled Run-File).
A Run-File can be created directly from OpenTrack using the function: Info Preferences 
Export.
This function offers an easy and efficient way to manage and use different OpenTrack pro-
jects in parallel on one computer. For example, each project can be placed on the desktop with
a different shortcut. Clicking on the shortcut loads the project, opens the specified data (infra-
structure, graphical timetables), activates the incidents and sets the parameters (as specified in
the designated Run-File) to be used in the simulation.
Example of a function call (console, target attribute of a shortcut):
C:\Users\opentrack\Apps\OpenTrack.app\OpenTrack.exe -runfile="C:\Users\opentrack
\OTProjects\Demo\aRunFile.txt"
In all cases the absolute file names (including path) must be used for both the application
(.exe) as well as for the run-file.
3.11.2 Starting OpenTrack with a ASCII-Text Timetable File

Call:
OpenTrack.exe -asciitexttimetable="<anASCIITextTimetableFileName>"
This allows users to define the used timetable in OpenTrack-Format (Tab-separated ASCII
Text). After the start, OpenTrack imports the timetable and uses it for the next simulation run.
Example of a function call (console, target attribute of a shortcut):
C:\Users\opentrack\Apps\OpenTrack.app\OpenTrack.exe -asciitexttimetble="C:\Users
\opentrack\OTProjects\Demo\aTimetable.txt"
The parameter - asciitexttimetable can be used independently of Scriptmode or in combination

with the Scriptmode.

The timetable database can be exported to a file in OpenTrack-Format using Functions Ex-
change Timetable Data Export Timetable Data (OpenTrack-Format).
3.11.3 Script Mode for OpenTrack (without Run-Files)

Call:
OpenTrack.exe –scriptinit -delayscenario = "aDelaySenario"
or
OpenTrack.exe -script
OpenTrack allows users to run the application using a script from outside the program itself.
This can be done using two parameters: scriptinit or script.
When the script is run OpenTrack opens automatically, runs a simulation with the most
recently used data, and then closes automatically.
The parameter scriptinit must be used the first time you run the simulation with a script. The
parameter script can be used for additional runs.
On the first call (with scriptinit) the delay scenario is set to the value of the specified delay
scenario (delay scenario). If the delay scenario parameter is not provided, the delay scenario is
set to 1.
On subsequent calls (with script) the delay scenario is increased by 1.
Examples:
OpenTrack.exe -scriptinit -delayscenario="5"

OpenTrack.exe -script
When the simulation is run using a script, the evaluation results are recorded in the same man-
ner as a regular multiple simulation in the output files OT_Timetable.txt and OT_Timeta-
ble.xml.
Graphical timetables developed during the simulation are saved under the filename:
<Filename>.<DelayScenario>.otsimcor in the output path.
3.11.4 Script Mode for OpenTrack (with Run-Files)

Call:
OpenTrack.exe -scriptinit -delayscenario="<aDelayScenario>" -runfile="<aRunFileName>"
or
OpenTrack.exe -script -runfile="<aRunFileName>"
A more powerful way to use OpenTrack in script mode is to use “run-files”. Run-files allow
you to set input parameters for OpenTrack by specifying a text file in the script call.

A run-file can be produced directly by OpenTrack using the function Info  Preferences 
Export.
When using script mode with run files the first simulation is also started using the parameter
scriptinit and additional simulations are made using the parameter script.
For simulation runs started with the scriptinit parameter, the parameter delayscenario speci-
fied in the call will only be used if no delay scenario is defined in the specified run-file.
For simulation runs started with the script parameter, and for which no delay scenario is speci-
fied in the run-file, the delay scenario is increased by one.
The timetable evaluation results are recorded in the same manner as a regular multiple simula-
tion, namely in the output files OT_Timetable.txt and OT_Timetable.xml of the output path
(folder). The output path can also be defined in the run-file.
All graphical timetables developed during the simulation are saved under the filename:
<Filename>.<DelayScenario>.otsimcor in the output path.

Train Operations: Routes, Paths and Itineraries 53
4. Train Operations: Routes, Paths and Itineraries

OpenTrack uses several types of data structure to describe the track used by a train in its ope-
ration. These data structures are differentiated by level and by the type of information included
in the particular data structure.
The first level of train path is called a route. Routes consist of an order of vertices of one direc-
tion of travel. Routes and shuntings do not, however, only serve to describe the track, but also
form part of the safety apparatus of the track system.
The second level is called a path. Paths consist of 1-to-n routes of one direction of travel.
Typically, a set of routes that are often used together (for example all the routes that make up
the track infrastructure from the exit signal of one station to the exit signal of the next station)
are concatenated to form paths.
The top level is called an itinerary. An itinerary consists of one or several successive paths.
Setting backs can also be modelled here. For the simulation the train is given a list of itinera-
ries with a priority for each itinerary. This list comprises all itineraries on which the train may
move. The actual route is determined during the simulation in that the train always selects the
available itinerary (track that is unoccupied or not reserved for another train) having the hig-
hest priority.
Typical Length of an Itinerary: 10 .. 1000 km

Itinerary Describes a line (e.g. Metro Line 1, Paris-Brussels, ...)
*
an Itinerary is a Sequence of Paths /
1..* an Itinerary contains 1 or more Paths
Typical Length of a Path: 1 .. 100 km
Path A Set of Routes typically used together
*
a Path is a Sequence of Routes /
1..* a Path contains 1 or more Routes
Typical Length of a Route: 0.1 .. 5 km
Route From a Main Signal to the next Main Signal
*
a Route is a Sequence of Vertices /
2..* a Route contains 2 ore more Vertices
A Vertex describes a given Location (e.g. Signal
Vertex Location, Grade Change, Speed Change, ...)
Figure 33: Routes, paths and itineraries and their relations
Routes, paths and itineraries are described below.

54 Train Operations: Routes, Paths and Itineraries
4.1 Routes
A route consists of 2...n vertices. Figure 34 illustrates a simple route. Routes always begin and
end at main signals (home signal, exit signal or block signal). In OpenTrack routes belong to
the vertex at which the main signal of the route begin is located. Route attributes such as
release time, signal indications, release groups and slow speed zone can be allocated to a route
using the Route Inspector.
Signal S1 Signal S2
Route R1(S1-S2)
Figure 34: Route (Example with Combined Signals)
During the simulation process if a route is required by a train, the route will be reserved for the
train only if it is not reserved for another train and if an edge belonging to the route is not
reserved or occupied. Once the last part of a train has passed the release point of the route (or
a route group), the reserved section is made available for another train after passage of the
release time.
4.1.1 Automated Search for All Possible Routes from a Main Signal
OpenTrack will automatically finds routes in the track layout, however the user must review
these routes to ensure that they are valid for the particular railroad situation being modeled.
The process for completing the automated search and selection of valid routes is as follows:
• Use palette Pointer Tool to select the start vertex for routes.
• Open Route Window (Tools  Routes), alternatively click on the start signal with the right
mouse button to display the context menu - Route Window is illustrated in Figure 35.
• Select “Search” button to begin search.
• All possible routes from the start vertex are shown in the Route Window’s upper table.
• Highlight a route in the upper table.
• Select “Fetch” button or double click the route, to enter the route on the definitive route list
(Route Window’s lower table).
• Data for the route selected on the route list are shown and can be edited by selecting “Edit”
button. This causes the Route Inspector, shown in Figure 35, to be displayed.
• Vertices with at least one defined route are displayed in red on the worksheet.
Route attributes are described in more detail below.

Figure 35: Route Window Figure 36: Route Inspector
4.1.2 Route Inspector

The following process is used to display the Route Inspector which then can be used to set the
attributes described below for each route.
• Tools Routes (alternatively click on the start signal with the right mouse button to dis-
play the context menu) ... can be used to open the Route Window (Figure 35).
• Press “Edit” button on Route Window to open Route Inspector (Figure 36).
Route Attributes
Routes Selection: Selection between Route Window and Shunting Window.
Search Button: Selecting this button causes all possible routes from the selected vertex to
be displayed in the upper table of the Route Window.
Fetch Button: Enters the selected route from upper table into the route list (lower table).
Route Name: Name of route.
Description: Description of the route (optional).

Length: Length of the route in metres (calculated using edge length data).
Avg. Grad.: Average gradient of route in per thousands (calculated using edge data).
Max. Switch Time: Maximum switch operation time on section (seconds).
Reserve Time: Time needed to reserve the route (seconds).
Release Time: Time needed to release the route (seconds).
Dist. to Res. Point: Distance to the reservation point of the route (automatic or user defined).
Dist. to Rel. Point: Distance to the release point of the route (as soon as the rear of the train
has passed the vertex at the release point, the release process is started).
Overlap: The route allocated overlap (optional).
Res. with prev. R.: When this box is checked the route is reserved if the previous route of the
train movement is reserved (this is used to prevent deadlock - see below).
Discr. Mov. Block: This route will be reserved using discrete block rules.
Signal Indications: Signal indications (see below).
Entry in occ. Block: When checked a train is allowed to enter an already occupied block.
Speed Restriction: Restricted speed for use in occupied blocks (km/h).
Stop Time: Waiting time before entering an occupied block (seconds).
Release Groups: Release groups (edges that are released together); default value: all edges
of the route are released together.
Slow Speed Zone: Edges on which the shown speed restriction applies at the signal; default
value: all edges of the route (see below).
Zone valid for ...: If selected, a speed restriction only applies to the train head, otherwise to
the complete train.
Appr. Zone Speed: Speed (in km/h), which must be achieved at the beginning of the zone
(Zone Speed).
Appr. Zone Length: Distance (in m) before the signal, where the reduced speed must be achie-
ved (length of zone, Zone Length).
[Cancel] Cancel the settings.

[Delete] Deletes the selected route from the list of routes.
[Duplicate] Duplicates the selected route.
[Edit] Opens Route Inspector which allows editing of routes.
[OK] Saves changes.
4.1.3 Preventing Deadlock on Routes

In OpenTrack there is no real block construct preventing a meeting of two trains having diffe-
rent directions of travel (deadlock) in the same block. However, deadlock can be prevented by
adding the ‘Reserve with Previous’ attribute to a route. If this attribute is selected for a route,
the first route segment can only be reserved for a train if the next route segment can also be
released for this train, or if there is a train in the next route segment traveling in the same
direction as the requesting train.
4.1.4 Signal Indication at the Main Signal

Every route can have n (n > 0; n <= number of showable signal aspects) different signal indi-
cations allocated to it. The number of pre-reservable routes then determines which signal indi-
cation will be shown for a train that wishes to use this route.

For example, if a route has three different signal indications (TS [free running], 90 km/h, 60
km/h), then the signal will only show ‘free running’ if the two route segments following the
first route segment can be reserved in addition to the first route segment. Similarly, the signal
will show ‘90 km/h’ if only one additional route segment can be reserved; and will show ‘60
km/h’ if only the first route segment is free.
4.1.5 Slow Speed Zone

If a signal at the beginning of a route shows a speed limit indication, the edges on which the
restricted speed applies can be defined via the slow speed zone. By default the signalized
speed applies from the signal location. This rule is normal for SBB home signals, but there are
locations in the network at which the speed limit only applies at the first switch of the station.
Figure 37 illustrates a situation where the restricted speed could apply only at the station
switch not at the home signal (left side of figure).
Station A
First Switch
Home Signal Exit Signals

Direction of Movement 
Figure 37: Slow Speed Zone at Entry into a Station
4.1.6 Approach Zone

It is possible to define an approach zone and approach speed before a signal. This means that
trains must decelerate to the approach speed within the approach zone when the signal shows
stop as shown in Figure 38. This is done by setting the zone speed and zone length attributes:
Zone Speed [km/h]: Maximum speed (km/h) in approach zone. It must be attained at the
beginning of the approach zone (Zone Speed).
Zone Length [m]: Distance (in meters) before the signal, where the reduced speed must be
maintained (Zone Length).
OpenTrack uses default values of 0 km/h for Zone Speed and 0 m for Zone Length. The Zone
Speed of 0 km/h means that the route does not have a reduced speed zone.

[km/h]
100
90
80
70
60
50
40
30
20
Zone Speed 10
0
5.5 5.6 5.7 5.8 5.9 6.0 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 [km]
Zone Length
Figure 38: Approach Speed, Approach Zone
4.2 Shuntings
Shunting movements are movements within stations that involve a change of direction. Open-
Track defines shuntings as a special type of Route. Shunting movements within a station area
are modelled by means of shuntings, which consist of an order of vertices of one direction of
travel.
Definition of Shunting Movements

OpenTrack allows the user to define shunting movements using a browser tool to select ver-
tices on the shunting route. The browser automatically generates a list of vertices from the
“current vertex” and the user selects the appropriate vertex. The process is repeated until the
entire shunting movement has been defined. Shunting movements can be defined by selecting
the “Shunting” menu in the Route Window. The complete procedure is:
• Use palette Pointer Tool to select start vertex for shunting operation.
• Open Route Window (Tools Routes) - Route Window is illustrated in Figure 35.
• Select “Shuntings” in Routes Selection box.
• Shunting Window is displayed - Figure 39.
• Navigate through the track layout with the browser until you reach the shunting destination.
• Record the name and speed of the shunting in appropriate cells of the Shunting Window.
• Press “New” to add the shunting into the shunting list.
The shunting attributes shown in the Shunting Window (Figure 39) are described in more
detail below.

Figure 39: Shunting Window
Shunting selection: Selection between Route Window and Shuntings Window

Shunting browser: Browser for the navigation through the railway network
From: Name of the starting point
To: Name of the target point in question
Name: Name of the shunting
[Default] Push button to automatically generate a shunting name (based on the
names of the start and the end points).
Speed: Shunting speed in km/h.
Shunting list: List of all shuntings belonging to the selected starting point
[Delete] Deletes the selected shunting from the list.
[New] Takes over the shunting selected in the browser into the list.
4.2.1 Overlaps (extended functionality)

Creating an overlap means that routes are not released immediately following passage of a
train. When an overlap has been created it means that, if a train comes to a halt, say for a sta-
tion stop, the overlap route is not released immediately, but only after a user defined overlap
release time (Release Time).
A simple way of creating overlaps is by setting appropriate slip attributes of the edges down-
stream of a home signal. If this method for defining an overlap is not sufficient for the track
layout being modelled OpenTrack also provides a special tool that enables users to freely
define both an overlap and a corresponding release time for each route, which provides greater
functionality.
To assign an overlap to a route, start by defining the end vertex of the route. Using Tools 
Routes, at the top of the Routes window, you can choose between Routes and Shuntings/Over-
laps. Select Shuntings/Overlaps to create or update an overlap.

Next, in the Routes Inspector, assign the overlap to a route. Select the appropriate route in the
table and press Edit. This displays the Route Inspector. Within the Overlap box, press Change
to have OpenTrack display all possible overlaps. Select one of them.
4.2.2 Definition of Shunting Movements and Overlaps

OpenTrack allows the user to define shunting movements and overlaps using a browser tool to
select vertices on the shunting/overlap route. The browser automatically generates a list of
vertices from the “current vertex” and the user selects the appropriate vertex. The process is
repeated until the entire shunting movement/overlap has been defined. Shunting movements
and overlaps can be defined by selecting the “Shuntings/Overlaps” menu on the Route
Window. The complete procedure is:
• Use palette Pointer Tool to select start vertex for shunting/overlap operation.
• Open Route Window (Tools  Routes).
• Select “Shuntings/Overlaps” in Routes Selection box.
• Shunting/Overlaps Window is displayed.
• Navigate through the track layout with the browser until you reach the shunting or overlap
destination.
• Record the name, speed and release time (for overlaps) of the shunting/overlap operation in
the appropriate cells of the Shunting/Overlaps Window.
• Press “New” to add the shunting/overlap into the shunting/overlap list.
4.3 Paths
The second level of train operation definition in OpenTrack is called a path. Paths consist of a
series of successive routes in one direction of travel. An unlimited number of routes can be
included in a path. Paths are merely an organizational structure and do not correspond to any
particular element of railway reality. As, however, train operations generally travel over seve-
ral routes, route orders can be grouped into paths.
4.3.1 Path Inspector

OpenTrack allows the user to define paths using a browser tool similar to that used to define
shuntings. The browser tool is located on the Path Inspector which is illustrated in Figure 40.
Path Browser: Browser for navigating through the railway network (shows all possible
routes from the starting vertex).
Show Route N.: Shows the route names in the path browser.
Path List: List of all currently defined paths belonging to the selected start vertex.
From: Name of the path start vertex.
To: Name of the path end vertex.
Last Route: Last route selected in the browser.
Length: Length of the last selected route (metres).
Avg. Grad.: Gradient of the last selected route (per thousand).
Last Signal: Start signal of the last selected route including signal indications.

Figure 40: Path Inspector
Path Name: Name of the path (user defined).

Description: Description of the path (optional).
[Default] Press this button to use default path name (start vertex name to end vertex
name).
Length: Length of selected path (meters).
Avg. Grad.: Average gradient of selected path (per thousand).
Show Path: When this box is checked the path is highlighted on the screen.
Active Routes: Number of routes that are active (in open documents) on the path.
[New] Adds the path to the path list.

[Duplicate] Makes a copy of the selected path.
[Delete] Deletes selected path from the path list.
[Build Itin.] Click this button to create an Itinerary with the selected path.
[Show Itin.] Select all the active itineraries (Itineraries) in the itinerary panel (Tools 
Itineraries) using the selected path.
4.3.2 Defining Paths in OpenTrack

The process for defining paths in OpenTrack uses the Path Inspector illustrated in Figure 40
and is similar to that described above to define shuntings. The procedure is as follows:
• Select start vertex.

• Open path inspector (Tools  Paths) or by right mouse clicking the starting signal to dis-
play the context menu and choosing Paths.

• Using the browser, navigate through the track layout selecting routes that you want included
in the path until you reach the path destination.
• Provide a name for the path (optional).
• Press the “New” button to add the path to the defined path list.
• Vertices with at least one path are displayed in green on the worksheet.
4.4 Itineraries
The top level of train operation infrastructure definition in OpenTrack is called an itinerary.
An itinerary consists of one or several successive paths. Itineraries do not need to include
paths that are all in the same direction; therefore itineraries are used to model setting backs.
There are two types of itineraries: full and local. Full itineraries describe complete trip bet-
ween two main points in the network (e.g. from Station A to Station D through a series of
other stations). Local itineraries describe only a portion of the route (e.g. from intermediate B
to intermediate Station C on the A-D full itinerary). These local itineraries can be used as
alternatives to the ‘main’ route and can be assigned with priorities (e.g. priority 2 or priority
3). The priorities are used by OpenTrack in the simulation process to select the itinerary (i.e.
track segments) that train will use (OpenTrack always uses the available itinerary with the hig-
hest priority).
In the simulation process a train is given a list of itineraries with a priority for each itinerary.
This list comprises all itineraries on which the train may move. The actual itinerary used by
the train is determined during the simulation in that the train always selects the available itine-
rary (track that is unoccupied or not reserved for another train) with the highest priority.
4.4.1 Itinerary Window

The Itinerary Window is illustrated in Figure 41. The Itinerary Window can be opened using
the command: Tools  Itinerary.
OpenTrack’s Itinerary Window lists the names of all itineraries defined application wide.
When the user selects an itinerary in the window, the itinerary’s characteristics (e.g. length)
are displayed in the appropriate fields. By clicking on the appropriate buttons (see below) itin-
eraries can be edited or new itineraries can be defined. The Itinerary Window presents the fol-
lowing data:
Itinerary list: List of all itineraries (application-wide).

Show switch: Check box to highlight the selected itinerary on the worksheet.
[Show Courses] Show all the courses that use a selected set of itineraries.
[Create Train Diagr.] Generate a train diagram for a selected itinerary. Using this function
requires that the infrastructure files for the corresponding itinerary be
open.

Figure 41: Itinerary Window
Search: Enter name of itinerary here to search through the itinerary list.
Description: Description of selected itinerary (optional).
Length: Length of selected itinerary (metres).
Avg. Grad.: Average gradient of selected itinerary (per thousand).
Active Routes: Number of routes that are active in the itinerary (i.e. that begin in open
documents).
Active Path: Number of paths that are active in the itinerary (i.e. that begin in open
documents).
Path List: List of all the paths included in the itinerary.
Route List: List of all the routes included in the itinerary.
First Doc.: Name of the document in which the itinerary start point is located.
Last open Doc.: Name of the document in which the active part of the selected itinerary
ends.
Last Doc.: Name of the document in which the itinerary end point is located.
[New] Creates new itinerary - Click to display New Itinerary Window.

[Edit] Selected itinerary can be edited - Click to display Itinerary Edit
Window.
[Add] Allows user to add an itinerary to the selected itinerary.
[Duplicate] Selected itinerary is duplicated.

[Delete] Selected itinerary is deleted.

[Reset] Deletes all non-active entries from the list (but not the itineraries).
[Save DB] Itinerary data are written in the database.
[Sel. unused] Selects all the itineraries in the table that are not used by any courses
(Tools  Courses). This can be useful for easily deleting all itineraries
that are not used by any trains/courses/routes (using the function
Delete).
4.4.2 Creating a New Itinerary

In order to create a new itinerary press the “New” button at the bottom of the Itinerary
Window, this causes the Itinerary New Window shown in Figure 42 to be displayed. The
window allows users to string together a series of paths into an itinerary.
The Itinerary New Window consists of an upper browser panel and a lower browser panel.
The upper browser window displays the paths that constitute the itinerary. When starting defi-
nition of a new itinerary this browser shows all available paths from the starting vertex (inclu-
ding automatically generated paths from shuntings).
The upper browser panel shows the paths already included on the itinerary. The number at the
end of each line in the list displays Selected Paths panel list presents the path order. A path can
be deleted from the itinerary by double clicking it in the list.
The lower browser panel (Suggested Continuation) displays a list of all potential paths that
can be added to the itinerary from the current itinerary end point. Paths can be added to the iti-
nerary by double clicking on the appropriate entry in the Suggested Continuation panel list.
OpenTrack only lists paths in the Suggested Continuation panel which are permissible.
Selectable paths can be found via the search field.
Usually, the last vertex of the path n is identical with the first vertex of the path n+1, but in
case of setting backs this is not the case. Setting backs are allowed where the first vertex of the
path n+1 lies on the last route/shunting of the path n. The first path after the change of direc-
tion additionally gets the setting back symbol () in the path list.
The user can provide a name to the itinerary using the text field at the bottom of the window.
The default name is: “itinerary start point - itinerary end point.”
Open Track allows users to create new itineraries easily and efficiently using a browser. This
simplified mode works from vertices from which one or more paths start (this can be determi-
ned by, for example, right-clicking on the associated signal and then selecting New Itinerary
from the context menu, or using the Itineraries tool directly Tools  Itineraries).
Pressing the New button in the Itineraries Panel causes the appropriate itinerary definition
panel to be displayed. At the top of the panel are two choices: Extended mode and the Simpli-
fied mode. The extended mode works as described above.
In the Simplified mode it is possible to use a browser to select paths from the starting point
(similar to the path definition process). This makes it easy to create new itineraries. However,

it is not possible to define switchbacks (turnarounds) in simplified mode.
4.4.3 Editing an Itinerary

The order of paths of a itinerary can be varied. For example, groups of paths can be exchanged
(for example change of the station track in station X).
Several successive paths to be replaced can be selected in the path list of the Edit window. The
path list shown thereafter in the Replace window is built up after the same system as the list
for the generation of new itineraries. Before the paths are replaced, OpenTrack tests whether
the rules described above for the creation of a path were observed.
Paths can be added to the beginning or end of an itinerary using the Add function (Tools  Iti-
neraries, Edit). The Add function supplements the existing Replace function. Paths can be
removed at the beginning or end of an itinerary using the Remove function.
Figure 42: New Itinerary Window Figure 43: Edit Itinerary Window


Train Management (Trains) 67
5. Train Management (Trains)

Trains consist of locomotive and wagons (trailer loads). OpenTrack classifies trains in the
following three categories:
• Fast Trains (Intercity (IC))

• Regional Trains
• Freight Trains
The train type influences the formula used in OpenTrack to calculate air resistance.
OpenTrack has a database of trains which is available for use in the simulation process. The
program also allows users to create their own train types. This section outlines how the user
can define trains in OpenTrack.
Locomotives are selected from the locomotive management tool (Tools  Engines).
Every train has a value table of the average braking decelerations per speed zone (default
value: -0.6 m/s2).
5.1 Trains Window

Open the Trains Window by selecting Tools  Trains.
Figure 44 illustrates the Trains Window. The Trains Window contains the following informa-
tion:
Figure 44: Trains Window

68 Train Management (Trains)
Train list: List of all defined train types in the Train Database (application-wide).
Engines: List of locomotives for selected train.
Train Load: Sum of locomotive weights and trailer loads (tonnes).
Train Length: Sum of the lengths of the locomotive(s) and trailers.
Train Desc.: Train description (optional)
Train Type: Train type (fast train, regional train or freight train).
Train Category: User definable train category (see Preferences, page 127).
Equation: Identifies which formula is used to estimate air resistance.
Speed max.: Maximum speed in km/h.
Deceleration: Defined deceleration rate in m/s2 and type of deceleration calculation.
[New] Records a new train type in the train database.

[Edit] Edits database entries for selected train type.
[Duplicate] Creates a duplicate copy of the selected train type in the database.
[Calculate] Carries out calculations on the sel. train type (calculate braking distance).
[Delete] Deletes selected train type from train database.
5.1.1 Creating a New Train

• Open the Trains Window by selecting Tools  Trains.
• Generate a new train by pushing the ‘New’ button.
• Edit panel appears (described below).
• Record train data in Edit panel.
• Be sure to press ENTER to save data.
• Press OK to enter the new train into the Train Database.
5.1.2 Train Edit Panel

The Train Edit Panel appears when the user clicks ‘New’ or ‘Edit’ on the Trains Window.
Figure 45 illustrates the Train Edit Panel. Information on the Train Edit Panel consists of the
following:
Name: Train name.

[Default]: Press this button and OpenTrack automatically assigns a train name.
Description: Train description (optional).
Type: Train type (IC/Fast Train; Regio Train = Regional Train; Freight
Train).
Category: Train category; trains can be placed in a category using the Train Cate-
gory Tool (Tools  Train Category); trains in a given category have
many similar qualities (e.g. dispatching priority, colour display on
train graphs, etc.)
Engines: List of the locomotives.

Pos: Position within train.
Name: Engine name (comes from engine database).
Load: Weight of the locomotive (tonnes).
Len.: Length of the locomotive (metres).
 Load: Sum of locomotive weights (tonnes).

 Length: Sum of locomotive lengths (metres).

[Add] Adds new locomotive.
[Delete] Deletes selected locomotive.
Trailers: List of the trailing loads.

Pos: Position within train.
Name: Name of the trailing load.
Load: Weight of the trailing load (tonnes).
Len.: Length of the trailing load (meters).
P Loss: Power loss for particular train in KW (e.g. for heating, air conditio-
ning, etc.).
No of Items: Count of wagons in train (influences resistance in Maglev trains) .
vmax: Maximum speed of the trailing load (km/h).
Rot.Mass.: Mass factor (addition for rotating masses).
 Load: Sum of trailing loads (tonnes).
 Length: Sum of lengths of trailing loads (meters).
[Add] Adds new trailing load.
[Delete] Deletes selected trailing load.
Resistance Equations: Resistance Formulas
Equation Rolling: Allows user to select formula for use in calculating rolling resistance.
A, B, C: Parameters for use in Davis formula (air resistance calculation).
v on: Switching-on-speed for linear motor (parameter for Maglev formula).
P L: Linear generator power per car (parameter for Maglev formula).
C: Aerodynamic factor (parameter for Maglev formula).
Result Unit: Units in which results of air resistance formula are displayed (N or
kN).
Starting Res.: Starting rolling resistance factor in N/t (optional).
below Speed: Speed below which the starting rolling resistance will be used in km/h.
Equation Gradient: Formula for calculating gradient resistance.
Equation Curve: Formula for calculating resistance in curve.

Percentage: Correction factor for curve resistance in %.
Max. Acceleration : Maximum rate of acceleration (m/s2).

Acc. Delay: Minimum time between the conclusion of brake applications and the
reacceleration (seconds).
Acc. Delay at Stop: Minimum time that a train must remain stopped at a stop before it can
start moving again (seconds).
Max. Drawbar Force: Maximum drawbar force on the first coupling in kN.
M. Time to hold Speed:Train may only increase speed if it can maintain this speed for a min.
specified time (optional).
Deceleration Menu: Type of braking calculation (Table, ETCS table, Braking percentage).
Deceleration Funct.: Average braking deceleration in m/s2 (always negative).

Braked Weight Perc.: Braking percent (%).

C1, C2 Coefficients for braking calculations completed using the breaking
percentage method.
Resulting Dec.: Calculated deceleration for braking calculations completed using the
braking percentage method.
Corr. Deceleration: Correction for the delay value for rising gradients (m/s2/‰).
Min. Deceleration: Minimum deceleration rate (m/s2).
Max. Deceleration: Maximum deceleration rate (m/s2).
Menu ETCS: Selectable ETCS Braking calculation methods.
Dec. Delay Breaking deceleration delay for ETCS (in seconds).
Above: Speed above which the braking delay for ETCS is applied (in km/h).
[OK] Adds edited/new train to train database.
Figure 45: Trains Edit Window

In the train definition it can be selected whether air resistance (part of the total resistance) is to
be computed using the Strahl/Sauthoff formula, a general formula by Davis or a function for
magnetically levitated trains. These formulas are described in more detail below (Chapter 5.3).
OpenTrack enables users to select from several possible braking curves including the detailed
description of ETCS-braking procedures (Level 1 and 2).
The attribute Dec. Delay (deceleration delay after brake application; default value = 0.0
seconds) indicates how many seconds following receipt of the signal information before the
operator applies the brake and the brake curve can be applied in the OpenTrack calculations.
The attribute Above is the speed, above which, the deceleration delay value is applied (in km/
h; Default value 0 km/h).
The additional menu selection governs the type of computation method used in applying the
brake curve. The following types are available:
Default: without ETCS breaking method (default setting)

ETCS: in accordance with ETCS specification
ETCS-: in accordance with ETCS specification, station stops conventionally
Locomotive and Wagon Position in a Train

The first locomotive position (attribute: Pos in the locomotive list) within a train is used for
power-on and power-off signals (in previous versions of Open Track the head of the train was
used for these signals).
Engine 1 (Pos. = 1) Trailer 1 (Pos. = 2)
Trailer 1 (Pos. = 1) Engine 1 (Pos. = 2) Trailer 2 (Pos. = 3)
Engine 1 (Pos. = 1) Trailer 1 (Pos. = 2) Engine 2 (Pos. = 3) Trailer 2 (Pos. = 4)
Figure 46: Positions of locomotives (engines) and wagons (trailers) within a train
5.2 Locomotive Management (Engines)

OpenTrack manages locomotives in a database called Depot. Any number of locomotive types
can be managed in each depot. Depot databases have filenames (name.depot), their extension
name is always depot. Locomotive data can be copied between different depot database files
using the Copy/Paste command.

Locomotive data included in the database includes tractive effort/speed diagram, braking
force/speed diagram, locomotive weight, length, resistance factors, etc. OpenTrack allows the
user to edit the diagrams and data graphically and by using an editor tool (described below).
5.2.1 Engines Window

The Engines Window is used to edit and enter locomotive data into the database. Figure 39
illustrates the Engines Window. The data in the Engines Window is described below.
Figure 47: Engines Window
[Up] and [Down] Use these keys to move thorough the database locomotive list.
Enginename: Locomotive name.

Load: Locomotive weight (Tonnes).
Adh.load: Weight locomotive can apply for adhesion (Tonnes) (Adh. load <= Load)
Length: Locomotive length (Metres).
Resist. factor: Resistance factor train running calculations (Strahl formula).
Rot.mass factor: Mass factor (addition for rotating masses).
Speed max: Maximum speed (km/h).
Tractive Effort max:Maximum tractive effort (kN).
Rack Traction: Locomotive with rack rail capacity.
Balise Telegram: Locomotive with ability to obtain signal data via balises.

Loop Telegram: Locomotive with ability to obtain signal data via loops.
Radio Telegram: Locomotive with ability to obtain signal data via radio.
[Set Data] Saves data in text cells.

[New Engine] Inserts new locomotive in database.
[Del. Engine] Deletes selected locomotive from database.
[Save Depot] Saves database.

[New Depot] Allows user to create a new depot database.
[Open Depot] Allows user to select which depot database to open.
5.2.2 Tractive Effort/Speed Diagram (Z/V-Diagram)

When the Engines Tool is activated the Engines Window and the Z/V Diagram window
(Figure 48) are displayed on the screen.
Z/V Diagrams: List of previously defined Z/V diagrams. The selected diagram is dis-
played in the Z/V diagram window.
[ Dupl. ] Duplicate the selected Z/V diagram.

[ Del. ] Delete the selected Z/V diagram.
[ Add ] Add new Z/V diagram.
[Import] Import Z/V diagram from text data file.
[Export] Export Z/V diagram to text data file.
Color Box: Displays color for Z/V diagram.
5.2.3 Power System

Systems: This box allows the user to select which Z/V diagram will be used for the
particular locomotive type when it operates on track sections with the
selected power system. A power system can have at most one Z/V dia-
gram (in other words, a locomotive will operate with a single Z/V relati-
onship under any given power system); but the same Z/V diagrams can be
used for several different power systems.
5.2.4 Adhesion Behaviour

Empirical formulas exist to estimate the friction traction power. The most well-known begin-
ning comes from Curtius and Kniffler and describes the frictional behavior between wheel and
rail in a speed-dependent manner as follows:
2,1 m/s
μ= + 0,161
v + 12,2 m/s
µ: Friction Coefficient [µ] = 1

v: Speed [v] = m/s

A locomotive’s adhesion behaviour can be described under three scenarios: good, normal and
bad to account for various different conditions (for example weather related). The percentage
value is then used in the Curtius and Kniffler to estimate the adhesion coefficient. For modern
locomotives the following pre-set values are used as defaults by OpenTrack (good: 150%,
normal: 125%, and bad: 80%).
5.2.5 Locomotive Power Loss Function

A locomotive wastes part of its mechanical effort in its very operation. In OpenTrack, for each
locomotive and each diagram of tractive force vs. speed, users can define a power loss func-
tion. The power loss function is entered in the Engines Inspector under Loss Function. For
each speed interval, the function should be entered as a constant in kilowatts (kW) and as a
percentage of tractive effort. OpenTrack then adds these losses to the total power requirement
for a train.
For electric locomotives, total power requirement means power consumption at the catenary
or third rail. For diesel and other non-electric locomotives, total power requirement means
total energy consumption. In all cases this includes losses both in the locomotive and its train.
For example, consider a train moving at 120 km/h that accelerates. The locomotive produces a
power P of 6000 kW.
Locomotive: constant power loss (P loss) = 45 kW; loss factor = 0.16

Rest of train: constant power loss (P loss) = 400 kW
Total power requirement (kW):

Pi = 45 kW + 6000 kW + (0.16 * 6000 kW) + 400 kW = 7405 kW
The Engine inspector shows the power loss function for a given locomotive in the cell Loss
Function. The button Edit enables users to edit the function in a table of values in which, for
each speed interval, users can enter or update both the constant loss (P Loss [kW]) and/or the
Loss Factor.
The train-related power loss can be defined on a per wagon (trailer) basis as described in
Chapter 5.1.2.
5.2.6 Tractive Effort/Speed (Z/V Diagram) Window

The Z/V diagram shows the power/speed relationship for the active (selected) locomotive. A
Z/V diagram is drawn starting from points; these points are then linked with straight or curved
(hyperbolic) line sections. Figure 48 illustrates a tractive effort/speed (Z/V) diagram.
Selection Buttons:
[Arrow] Use the arrow to select or add points to the diagram.

[Linear] Curve section on the left of the new point is drawn as a straight line.
[Hyperbolic] Curve section on the left of the new point is drawn hyperbolically.

Figure 48: Z/V - Diagram Window Figure 49: Document with Locomotive
Image
Inserting New Point on Z/V Diagram

• Select desired curve type (straight/hyperbolic) for next point by clicking appropriate selec-
tion button in top section of diagram.
• Mouse-click in the diagram at the desired insertion position. The inserted point becomes the
selected point.
• Set the point exactly using the ‘Selected Point’ section of the Engines window. Be sure to
press ENTER or Set Data to save data in text boxes.
• Insert additional points until the curve is correct.
The Z/V diagram scale is determined by the appropriate values in the Engines window (maxi-
mum speed, maximum tractive effort, minimum tractive effort). The function Autoscale com-
putes these values automatically and sets the values on the diagram accordingly. The user
cannot insert points on the Z/V diagram that are outside the minimum and maximum values.
5.3 Train Resistance Calculation

Trains experience resistance while traveling. This resistance must be overcome by the loco-
motive’s tractive strength as applied to the rails. The total resistance experienced by the train
(R) is a sum of the traction resistance and acceleration resistance. This can be expressed in the
following formula:
R = RF + R a
R: Total Resistance [R] = N

RF: Traction Resistance [RF] = N
Ra: Acceleration Resistance [Ra] = N

The traction resistance and the acceleration resistance can each be divided and sub-divided
into components as outlined below.
5.3.1 A - Traction Resistance

The traction resistance can be divided into the rolling resistance and the distance resistance as
shown in the following formula:
R F = RL + R Str
RF: Traction Resistance [RF] = N

RL: Rolling Resistance [RL] = N
RStr: Distance Resistance [RStr] = N
A-1: Rolling Resistance
The rolling resistance consists of air resistance, the bearing friction, rolling resistance, and
inertial resistance. In practice three formulas: Sauthoff’s formula (for passenger wagons),
Strahl’s formula (for locomotives), and an improved Strahl’s formula (for freight wagons) are
used together or a general formula in form of a quadratic equation (Davis formula) can be used
to calculate rolling resistance. A special formula is used for Maglev trains. All these formulas
are presented below.
Locomotive Rolling Resistance - Strahl’s formula for calculating rolling resistance of locomo-
tives is as follows:
RLT = g • {[fL • m ]+ [k St1 • ((v + Δv) • 3.6) ]}

2
1000
RLT: Locomotive Resistance [RLT] = N

g: Acceleration due to gravity (9.81 m/s2) [g] = m/s2
m: Weight of locomotives [m] = kg
v: Train Speed [v] = m/s
v: Wind Resistance (15 km/h = 4,17 m/s) [v] = m/s
f L: Resistance Factor (Default value: 3.3) [fL] = 1
kSt1: Resistance Coefficient (0.03 kg • s2/m2) [kSt1] = kg • s2/m2
Passenger Wagon Rolling Resistance - Sauthoff’s formula for calculating rolling resistance for
passenger wagons is:
RLP = g • {[1.9 • m ]+ [kSa1 • v • 3.6 • m ] + [kSa2 • (n+2.7) • ((v + Δv) • 3.6) ]}

2
1000 1000
RLP: Resistance for Passenger Wagons [RLP] = N

m: Weight of passenger wagons [m] = kg

n: Number of passenger wagons [n] = 1

v: Wind Resistance (15 km/h = 4,17 m/s) [v] = m/s
kSa1: Resistance Coefficient (0.0025 s/m) [kSa1] = s/m
kSa2: Resistance Coefficient (0.00696 kg • s2/m2) [kSa2] = kg • s2/m2
Freight Wagon Rolling Resistance - The improved Strahl’s formula for calculating rolling resi-
stance for freight wagons is:
kSt2
RLG = g • m • [2.2 -
2
+ kSt4 • (v • 3.6) ]
1000 v • 3.6 + kSt3
RLG: Resistance of Freight Wagons [RLG] = N

m: Weight of freight wagons [m] = kg
kSt2: Resistance Coefficient (80 m/s) [kSt2] = m/s
kSt3: Resistance Coefficient (38 m/s) [kSt3] = m/s
kSt4: Resistance Coefficient (0.00032 s2/m2) [kSt4] = s2/m2
Davis Formula - The Davis formula is available in a mass-dependent and in a mass-indepen-

dent form. The three parameters A, B and C are typically presented in tabular form.
The mass-dependent Davis formula (result in N) is:
2
r' = A + B • v + C • v
RLZ = m • g • r' / 1000
RLZ: Train air resistance [RLZ] = N

r’: Special air resistance [r’] = N/kN
m: Weight of wagons [m] = kg
v: Train Speed [v] = km/h
The mass-independent Davis formula (result in kN) is as follows:
2
RLZ = A + B • v + C • v
RLZ: Train air resistance [RLZ] = kN

v: Train Speed [v] = km/h

Maglev Train Resistance Formulas - The formulas for determining resistance for Maglev
trains are as follows:
RLZ= FLig + FWs + FAe
FLig = 0 for v < vEin

FLig = nW • ( PLig• 3.6 / v - 0.2) for v >= vEin
0.7
FWs= nW • [ 0.1• v / 3.6 + 0.02 • (v / 3.6) ]
2
FAe = C • v
RLZ: Train air resistance [RLZ] = N

FLig : Linear generator resistance [FLig] = N
FWs : Eddy current resistance [FWs] = N
FAe : Aerodynamic resistance [FAe] = N
m: Weight of wagons [m] = kg
vEin : Switching speed of linear motors [vEin] = km/h
nW : Number of wagons in train [nW] = 1
PLig : Linear motor power per wagon [PLig] = kW
C: Aerodynamic default (same as Davis formula) [C] = 1
Tunnel Air Resistance

Trains traveling in tunnels experience substantially higher air resistance. The amount of resi-
stance depends upon the exterior surface of the train, the tunnel form, the tunnel cross section
and the smoothness of the tunnel walls. The train’s rolling resistance increases by the tunnel
resistance RT. For normal track sections (i.e. not in tunnels) RT = 0.
RT = fT • v2
RT: Tunnel resistance [RT] = N

f T: Tunnel factor [fT] = kg/m
v: Speed [v] = m/s

Total Rolling Resistance
A train’s total rolling resistance will be the sum of its locomotive resistance, wagon (passenger
or freight) resistance, and tunnel resistance. This can be expressed by the following formula:
RL = RLT + R LP + RT Strahl/Sauthoff (Personenzüge / Passenger Trains)

RL = RLT + R LG + R T Strahl/Sauthoff (Güterzüge / Freight Trains)
RL = RLZ + R T Davis, Maglev
A-2: Distance Resistance

The distance resistance consists of gradient resistance, curve resistance and switch resistance
as expressed in the following formula:
RStr = RS+ RB + RW
RStr: Distance Resistance [RStr] = N

RS: Gradient resistance [RS] = N
RB: Curve resistance [RB] = N
RW: Switch resistance [RW] = N
The switch resistance is neglected in the simulation due to its small influence on train operati-
ons in large networks.
Gradient Resistance - Gradient resistance is the portion of the train mass working against the
train’s direction of motion. Figure 50 illustrates the resistance forces acting due to gradient.
m • g • sin(α)
m • g • cos(α) m•g
Figure 50: Gradient Resistance

RS = m • g • sin(α)
I für kleine α
RS = m • g • tan(α) = m • g •
1000 for small α
RS: Gradient resistance [RS] = N

m: Train weight (mass) [m] = kg
g: Acceleration due to gravity [g] = m/s2
: Angle of inclination [] = ° or rad
I: Upward gradient (slope) [I] = ‰
For small angles of inclination (sin () can be replaced by tan(). In railway applications
tan() is called inclination (I) and is expressed in per thousand.
By default, OpenTrack distributes the train mass evenly over the length of the train (Distribu-
ted Mass per Train). If a more detailed calculation is needed users can select (Distributed
Mass per Engine and per Trailer), in which case the gradient resistance for each locomotive
and trailer will be calculated separately, based on their current position in the train and the
track slope under the respective locomotive or trailer.
Curve Resistance - Trains experience resistance when traveling through a curve. This resi-
stance is caused by rigid wheel sets traveling over interior and exterior radii of different
lengths, and because of the transverse shift friction of the drive assemblies. The curve resi-
stance depends on the curve radius and the track gauge. An example of an empirical curve
resistance formula is Roeckl’s formula (Deutsch Bahn) for standard gauge tracks:
6,3
RB = •m for r ≥ 300 m
r-55
4,91
RB = •m for r < 300 m
r-30

r: Curve radius [r] = m
In addition to the Roeckl formula for calculating curve resistance, OpenTrack provides a
second formula for calculating curve resistance for trams:
1+c
RB = • 0,17 • m • g
r


c: Distance of axles per bogie[c] = m (c = 2m)
r: Curve radius [r] = m
g: Acceleration due to gravity [g] = m/s2
OpenTrack can calculate curve resistance very precisely by allowing users to enter the para-
meters D and E in the Roeckl formula. Furthermore, these two parameters can be defined indi-
vidually for both locomotives and trailers (wagons).
During the simulation OpenTrack calculates the curve resistance for each part of the train
(locomotives and trailers) separately. The sum of the partial resistances gives the total curve
resistance for the entire train in the current position.
D
RB = • m
r-E

r: Radius [r] = m
m: Train mass [m] = kg
D: User-defined D-Parameter [D] = m2/s2
E: User-defined E-Parameter [E] = m
In the tables for the locomotives (Engines) and wagon groups (Trailers), the columns for the D
and E parameters become visible when the curve resistance formula (Curve Resistance) is set
to the position user defined (Roekl Formula User defined [R = D*m/(r-E)]).
Default values for parameters D and E are the values used in the basic Roeckl formula (for
standard gauge) (D = 6.3 m2/s2, E = 55 m).

Figure 51: Train Panel (Edit) with new curve resistance formula
Starting Rolling Resistance - The starting rolling resistance is the extra resistance experienced
by a train when it starts from a stopped position. The following starting rolling resistance para-
meters can be defined in OpenTrack:
• Use Starting Resistance: determines if the starting rolling resistance will be used or not;
• Starting Res. [N/t]: starting rolling resistance factor in Newtons per Tonne train mass;
• Below Speed [km/h]: the speed below which the starting rolling resistance will be used;
m: Mass of the Train [m] = t

rSt : Starting Rolling Resistance Factor [rSt ] = N/t
RSt Starting Rolling Resistance [RSt] = N
The starting rolling resistance force RSt is a linear function between the speed v = 0 and the
Below Speed. At the speed v = 0 the value of RSt = rSt * m and when v = v (Below Speed), then
the rolling resistance is calculated using the selected rolling resistance formula (Strahl/
Sauthoff, Davis, ...).
The relationship between rolling resistance and speed is shown in the figure below. The
example shows the rolling resistance calculated using the Strahl/Sauthoff formula with a star-

ting rolling resistance (rSt) of 50 N/t from 0 to 8 km/h, a train mass of 550 t, and a maximum
speed of 140 km/h.
[kN]
50
40
Resistance
30
20
10
0
0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 [km/h]
Speed
Figure 52: Rolling resistance as a function of speed
5.3.2 B - Acceleration Resistance

When a train accelerates or decelerates (brakes) it experiences acceleration resistance. A
train’s acceleration resistance is proportional to the train’s mass and to its rate of acceleration
and consists of a portion for the translation and a portion of the rotary masses. For the portion
of the rotary masses an empirical mass factor  is introduced. The formula for acceleration
resistance is:
Ra = m • a • (1 + 0,01 • ρ)
Ra: Acceleration resistance [Ra] = N

a: Acceleration rate [a] = m/s2
 Empirical mass factor [] = 1
For passenger and freight trains the mass factor  lies between 6 and 10. Reference [Wei 91]
presents a more detailed description of mass factors.
5.4 Examples
This section presents examples on how to use various features of OpenTrack's train manage-
ment features.
5.4.1 Braking Curve Definition Based on Braking Percent

By default OpenTrack uses a value table (which lists speed dependent braking deceleration

values) to define the braking curve. However users can also define locomotive braking using a
percentage factor.
In normal travel time calculations, i.e. those in which the trains brake under normal operati-
ons, it is recommended to use OpenTrack's default table-based braking function. The percen-
tage definition is most suitable for analysis of a train's braking potential, based on use of a
percentage of braking ability. This enables users to visualize brake applications, allowing
them (for example) to examine and plot points where trains apply brakes.
The deceleration formula follows the form:
a = - (C1 + C2 • BWP )
C1: Coefficient 1 (independent coefficient) [C1] = 1

C2: Coefficient 2 (coefficient dependent on breaking percentage) [C2] = 1
BWP: Braked Weight Percentage: Train's Total Braking Potential [BWP] = 1
Users can either develop their own values for the coefficients C1 and C2 or use a pre-defined
value. The following formulae are available:
Formula C1 C2
UIC 0.069 0.006
SBB ZUB 0.06 0.006
SBB FSS 0.063 0.0067
In order to use this new function, define the attributes in OpenTrack's Train Panel (Tools 
Trains).
As a check for the user, the resulting delay is displayed in the field Resulting Deceleration for
the selected function.
5.4.2 Braking Calculations for Trains Operating Under ETCS Level 2

In order to realistically model trains that can be operated on both ETCS Level 2 and on con-
ventional routes, OpenTrack enables users to define the braking characteristics (i.e. the Dece-
leration Function) of a train with a menu item, under which the properties are managed for
both types of system (Function Table: non-ETCS / ETCS).
This information is presented in the Train Inspector's Deceleration Box (shown in Figure 53 -
compare to Figure 45 for a non-ETCS train).

Figure 53: Train Inspector for trains running under ETCS-Level 2
In the case of a train that operates under ETCS control, the deceleration function table consists
of four columns rather than three for trains operating only in non-ETCS controlled track. The
third column of the table in both cases lists deceleration values for the area outside of the
ETCS control. In the case of the trains operating under ETCS, a fourth column is displayed
which lists deceleration values for the area managed under ETCS.
The ETCS values in the fourth column are the starting point for calculating the individual
ETCS braking curves. These values are used along with the values for the braking application
delay curve (Dec. Delay [s]) and the speed above which the delay is applied when operating
under ETCS release speed (above [km/h]).
The Dec. Delay [s] and above [km/h] values are shown at the bottom of the Deceleration Box
when ETCS is indicated on the pulldown menu in the bottom left corner of the Train Inspec-
tor's Deceleration Box.

Station A Station B Station C Station D
non-ETCS Section ETCS Level 2 Section non-ETCS Section
Figure 54: Line with non-ETCS / ETCS Level 2
Figure 54 shows a track section that contains one segment of ETCS Level 2 control. The
beginning and end of the ETCS Level 2 control is shown by the cab signalling start/end
signals (CAB Startsignal ETCS L2 or CAB Endsignal ETCS L2 in the signal inspector). The
edges within the ETCS L2 controlled area have the property that signal information can be
sent and received via radio (Loop / Radio ETCS in the Edge Inspector). These signals are mar-
ked as virtual signals (signal box is virtual in the Signal Inspector).
A train that starts at station A, which has the brake property: Function Table: non-ETCS /
ETCS, will start operating as conventionally signalled train (calculating its braking curves
according to the deceleration values in the third column of the table). Once the train reaches
the ETCS L2 zone, (the ETCS L2 zone is between the first block signal leaving station B and
the last block signal before the station D entry signal), the train will calculate its braking cur-
ves based on the deceleration values presented in the fourth column of the table. When the
train leaves the ETCS L2 zone, it goes back to using the third column values to calculate its
braking curves.
[km/h]
130
120
110
100
90
Speed
80
70
60
50
40
30
20
10
0
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 [km]
Station C
Station D
Station A
Station B
[m/s^2]
0.3
Acceleration
0.2
0.1
0.0
-0.1
-0.2
-0.3
-0.4
-0.5
-0.6
-0.7
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 [km]
non-ETCS Section ETCS Level 2 Section non-ETCS Section
Figure 55: Speed vs. distance and acceleration vs. distance non-ETCS / ETCS Level 2

Figure 55 shows the difference in train braking between the ETCS-section and the non-ETCS
sections.
5.4.3 Train Acceleration Rule ("30-second rule")

Some railways have rules specifying that a train may only increase its speed if it can maintain
this speed for a specified time (e.g., 30 seconds) before it must brake. In OpenTrack users can
define this time (between 0 and 60 seconds) using the attribute Min. Time to hold Speed on the
Trains Panel. OpenTrack only applies this rule for punctual trains traveling over 40 km/h, the
rule is not applied for delayed trains.
5.5 Train Categories

A function located in the Train Categories window allows users to designate a set of particular
trains and give them certain attributes (e.g. a distribution of initial delays) that differ from the
other trains in the simulation. This section describes the Train Categories window and the
main attributes that can be set using the window.
5.5.1 Train Categories Window Description

The train categories window is illustrated in Figure 56
Category Name: User-defined name of the train category.
Dispatching
Priority: Dispatching priority for the train category (Priority 1 > Prio-
rity 2 etc.)
Look ahead Dist. [m]: Length of 'look ahead distance' in meters.
Look ahead Time [s]: Period of time for 'look ahead time' in seconds.
Selection of Routes: Method of selecting alternative routes (offensive or defen-
sive).
Initial Delay
Use Initial Delay: Check this box if the user-defined initial delay should be
used.
Distribution: Type of distribution function (negative exponential or piece-
wise linear).
Distr. Function (Table): Definition of distribution function by means of attributes,
average, maximum and percentage (for negative-exponen-
tial) or definition of each interval (for piecewise linear).
[Add] Add interval data to table.
[Delete] Delete interval data from table.
[Export] Export distribution function data to text file.

Figure 56: Train Categories Window
Station Dwell and Delays
Add Delays to: Handling of delays (add to departure time (Dept. Time) or to
dwell time (Dwell)).
Use max. Station Delay: Check box to use the station-based maximum station delay
in the simulation.
Max. Station Delay [s]: Maximum value of initial delay at a station in seconds.
Used Station Delays [%]: Possibility of a station delay.
Dwell Time Variation: Dwell time variation (optional), see also Chapter Dwell Time
Variation.
Dept. Process Time: Departure process time (optional) in seconds, see also Chap-
ter Departure Process Time.

Performance Distribution
Use Performance Distr.: Check box to use performance distribution function.
Distr. Function (Table): Table defining the distribution function to be used (one table
for on-time trains, one table for delayed trains).
[Add] Add interval data to table.
[Delete] Delete interval data from table.
Timetable Defaults
Stop at every Station: Default dwell time (Dwell) for all stations in seconds.
Timing Stations: All stations or based on definition in station database (Tools
 Stations).
Min Connection Time: Default Min. Wait time for connections.
Use Track Names: Use the Track Names in the timetable based on the selected
type.
Category Delay Settings

Small Delay [s]: Minimum value for a train to be considered late (> 0; default
= 1s).
Medium Delay [s]: Trains delayed by more than this value are considered to
have a medium delay (> 0; default = 60s).
Large Delay [s]: Trains delayed by more than this value are considered to
have a large delay (> 0; default = 300s).
Colors
Category Color: Train category color.
Background Color: Background color (for animation).
Misc.
Driving on Sight Speed [km/h ]: Max. Speed while Driving on Sight.
Dwell Time Variation

The function Dwell Time Variation can be used to define the dwell time for early and delayed
trains (punctual trains use the scheduled dwell time). The Dwell Time Variation can be speci-
fied as a percentage of the planned dwell time or in seconds. It allows both positive and nega-
tive time and percentage values.
The Dwell Time Variation describes how the dwell time should be changed for trains that
arrive early (delay <= -1.0 s) and late (delay >= 1.0 s).
Examples:
Dwell Time Variation Early Trains: -20% for delays <= -10 s: trains that arrive 10 or more
seconds early shorten their dwell time (compared to the planned stopping time / Dwell Time)
by 20 percent.
Dwell Time Variation Delayed Trains: 10 s for delays >= 15 s: trains that arrive 15 or more
seconds delayed extend their dwell time (compared to the planned stopping time / Dwell Time)

by 10 seconds.
Departure Process Time

The Departure Process Time is the time needed to complete all the processes necessary bet-
ween the time a train receives its departure signal (e.g., signal shows green) and the actual
departure of the train. Departure process time is measured in seconds and the default value =
0.0 s.
There are two options for using Departure Process Time: selecting the “+” means that the
departure process time begins at the scheduled departure time, selecting the “-“ means that the
departure process time can begin before the scheduled departure time with the objective, that
the train can depart at the scheduled departure time.
The departure process time is used for all stations that have a minimum stop time (Dwell) > 0
s defined in the timetable.
Usage of Track Names in the Timetable

The menu item Use Track Name can be used to determine whether the track name should be
used when creating a timetable (Tools Courses, New Timetable) or when updating a timeta-
ble (Tools  Timetable, Update) or whether it is to be defined in the process, and if so, what
attribute is to be used (the vertex name of the station vertex [Vertex Name], or the track name
of the edge adjacent to the station vertex [Edge Track Name]).
The exit signal can also be included in the definition of the timetable attribute Track Names
(Tools Timetable) with its name (Exit Signal Name) and the name of the vertex (Exit Signal
Vertex Name) or the name of the adjacent edge (Exit Signal Track Name, Exit Signal Edge
Name).
The following figure shows the selection options and the objects from whose attributes the
name is generated.
Station Vertex Track Name Exit Signal Vertex Name

Station Vertex Edge Name Exit Signal Track Name
Exit Signal Edge Name
S1
Station Vertex Name Exit Signal Name
Station Exit
Vertex Signal
Figure 57: Station elements used to generate timetable attributes Track Name

For example:
If a schedule is created for a new course of a train category with the type Exit Signal Name, the
value "S1" (Name of the Exit Signal) is used for the attribute Track Name in the timetable for
the particular station.
5.5.2 Dispatching Priority by Train Category

In OpenTrack it is possible to assign dispatching priority for categories of trains using the train
category window.
The priority of each train in a category can be defined depending on its delay. This is done
using the table in the Train Categories Window Dispatching box. Users can enter data in this
table to define the priority for trains with different levels of delay; for example, the priority of
trains with a high delay can be increased or decreased.
Each train category has a user-defined “look ahead” zone. During the simulation trains moni-
tor this zone in front of it to determine if there is a lower priority train in the segment. The look
ahead zone is defined in terms of distance and time. The look ahead zone is the maximum of
either the spatial definition (Look ahead Distance [m]) or the product of the current speed (m/
s) and the temporal definition (Look ahead Time [s]).
If a train with a lower priority is identified in the look ahead zone, then the simulation attempts
to move the lower priority train away from the path of the higher priority train at the next pos-
sible location in which the route has not yet been reserved and/or to stop the lower priority
train. Once the higher priority train has overtaken the lower priority train the lower priority
train is allowed to continue its journey.
OpenTrack also enables users to define what type of alternative route should be reserved in
case it is not possible to dispatch trains to a higher priority infrastructure or the assigned prio-
rity infrastructure. This can be done using the pull down menu titled: Selection of alt. Routes.
OpenTrack has two possibilities for switching trains to alternative routes: offensive and defen-
sive. In the case of offensive route selection, trains are switched to alternative routes whenever
the next route is not free, independent of the nature of the occupancy or reservation.
In the case of defensive route selection, trains are only switched to another route if the track
occupation is due to a stopped train, a train travelling in the opposite direction or due to a
disturbance, trains are not switched to alternative routes if the occupied track is being used by
a train travelling in the same direction.
5.5.3 Initial Delay by Train Category

OpenTrack also enables users to define an initial delay for each category of trains. This initial
delay value will be used in the simulation when the Use Initial Delay check box is selected.
The initial delay of trains can be modelled using either a negative exponential function or a
piecewise linear function. Users can select which function to use by selecting from the pull-

down menu in the Train Categories Window Initial Delay box (illustrated in Figure 56). The
initial delay for specific trains is modelled using a random number generator combined with
the chosen distribution function.
Next users enter the parameters for the selected distribution type into the Initial Delay box's
table. If a negative exponential distribution has been selected, users enter three values: an
average delay (Mean [s]), maximum delay (Max [s]) and the percentage of delayed trains
(Perc. [%]) in the first row of the table.
If a piecewise linear distribution has been selected, users enter the intervals (From [s] through
To [s]) and the probability of delay for each interval (Perc. [%]) in each row of the table (one
row per interval). It is assumed that the distribution is linear within each interval. Users can
enter as many intervals as they wish, but the sum of the probabilities for all intervals must add
up to 100%, if this is not the case, then the column with the probabilities will be shown in red.
5.5.4 Station Delays by Train Category

OpenTrack users can set maximum values for station delay by train category using the Station
Delays box in the Train Categories Window. These values will be used in the simulation when
the Use max. Station Delay check box is selected.
When the maximum station delay box is checked, then OpenTrack will automatically reduce
the station delay to the user defined upper limit, if during the simulation, OpenTrack estimates
that a train in the given category at an intermediate station will have a delay higher than the
maximum (based on the simulation's actual delay scenario and the station's defined mean
delay [mean Delay]).
The function (Used Station Delays [%]) allows users to define the probability of station delays
(Station Delays) for particular train categories in the simulation. For each individual station
delay (Mean Delay from the timetable) is defined based on the train category probability, if the
delay will be used (the train suffers an auxiliary delay) or not (the train does not receive any
additional delay) at the particular station.
5.5.5 Performance Distribution

The Train Categories Window Performance Distribution box enables users to define and edit
their own piecewise linear distribution functions for travel time performance of punctual (on
time) and delayed individual trains. This allows OpenTrack to provide a more realistic distri-
bution of travel times.
For example, the data shown in the Trains Category Window presented in Figure 56, shows
the following:
For trains operating punctually:
20% of trains operate with performance values between 90% and 92%

For delayed trains:
All trains operate with performance values between 98% and 100%
5.5.6 Delay Definitions

OpenTrack enables users to define delay categories (small, medium and large) based on the
amount of time a train is delayed for different train categories. This is done using the Category
Delays Settings box in the bottom right hand corner of the Train Categories Window.
In general, a train is considered delayed, if the delay is greater than or equal to the user-defi-
ned “small” delay value; this means that above this value the delay is considered a conflict and
will be displayed in the reporting window and on the graphic schedule. Similarly, the colour
changes on the appropriate train numbers shown in the animated display. Small delays are
shown with a yellow border around the train number, medium delays with an orange border
and large delays with a red border.
Trains have different performance goals for punctual departures and delays (Performance on
time [%], Performance delayed [%]), this will change the behaviour of the train from reaching
the lower limit, in other words the train is considered on time for all actual schedule deviations
that are smaller than the limit set for a small delay.
5.6 Distribution Functions in OpenTrack

OpenTrack uses distribution functions in several different modules including delay distribu-
tion (outlined in the sections above) and duration of incidents and disturbances in the simula-
tion process. OpenTrack stores all the distributions in a central distributions database.
The OpenTrack distributions database stores user-defined distributions under a unique name
(this name is shown in OpenTrack functions that use the distribution function).
The distribution functions currently allowed by OpenTrack are in the form of piecewise linear
distributions. These are formed by assigning a probability (Perc. [%]) that an event takes
place within a user-defined time interval set using the (From [s]) and (To [s]) commands. The
sum of the probabilities in the distribution should equal 100%, if this is not the case the proba-
bilities column will be shown in red. OpenTrack provides commands for editing data, and
deleting or adding intervals.
Figure 58 illustrates the Distributions Window showing an example distribution. The example
distribution function indicates that there is a 10% possibility that the event will occur in the
time between 0 and 10 seconds, a 80% possibility that it will occur in the time between 10 and
20 seconds, and a 10% possibility it will occur in the time between 20 and 60 seconds.

Figure 58: Distribution Function Window
Distributions: List with the name of user-defined distribution functions.

Distr.-Menu: Shows type of distribution function.
[New] Create new distribution function.

[Edit] Edit distribution function.
[Duplicate] Duplicate selected distribution function.
[Delete] Delete selected distribution function.
In Edit mode:
[Add] Creates a new interval so user can enter data.
[Delete] Deletes selected interval.

Courses and Timetables 95
6. Courses and Timetables
6.1 Course Management (Courses)

OpenTrack uses the term course to define a service operated by a train over a period of time
(e.g. a day). In OpenTrack a course consists of a set of itineraries with an associated set of
timetable entries (OpenTrack timetables are described in Chapter 6.2), a train definition, a
course number (each course must be unique), a train type (speed type), and an entry speed.
Each course also specifies which train spacing philosophy should be used (i.e. discrete block,
moving block). Another way to think of a course is as a particular “train.”
The locomotive driver’s behaviour can also be defined and in the case that the train is on sche-
dule or late. During the simulation at each train stop or station passage, the actual time is com-
pared to the planned time (when defined in the timetable) and is used to determine which
acceleration and speed behaviour the train will use on the next section. For example, an acce-
leration value of 95% means that 95% of the technically possible acceleration rate will be
used, but also, that only 95% of the travel speed on the section will be used.
6.1.1 Courses/Services Window

Figure 59 illustrates the Courses/Services Window. The information presented in this window
is described below.
Figure 59: Courses/Services Window

96 Courses and Timetables
Use: Check mark indicates that the course is included in the simulation.
Course ID: List of all course ID numbers application-wide (course numbers can consist
of digits and letters, but must include at least one digit).
Itineraries: The itineraries operated by the selected course.
[Show] Show itinerary (priority 1) in the itinerary panel.

[Show All] Highlight all of the selected course’s itineraries (the main
itinerary with priority 1 in red, other priorities in orange
color).
[Define] Automatially assign sutiable itineraries.
[Create T.D.]Generate a train diagram for the selected course. Using this
function requires that the infrastructure files for the highest
priority corresponding itinerary (priority 1) of the course be
open.
Description: User defined designation for course.

Comment: Comment (optional).
Kind: Description of Course type (optional).
Train: Name of the train.
Train Category: The train specific train category.
Traintype: Type of train (corresponds to the train speed type in the preferences (Info
 Preferences) and to those of the edge attributes).
First Departure: Departure time at the first station (from the timetable database).
[New Timetable] Click here to input timetable entries for selected course (note: all itinerary
worksheets must be open).
[Show Timetable] The timetable for the selected course is shown in the timetable window.
Perf. (on time) Course-specific performance factor (in %) for courses operating on sche-
dule (In the simulation the performance factor is effectively the course-spe-
cific acceleration factor multiplied by the global performance factor (Tools
 Simulation)).
Perf. (delayed): Course-specific performance factor for late courses (%).
Entry Speed: Entry speed of the train during the simulation (km/h).
Output Offset: Offset distance (start collecting data at value other than zero (metres)).
Sort by: Sort order of the courses list.
[Inv] Inverts the use flag on all selected courses.

[Use] Sets the use flag on all selected courses.
[Unuse] Deletes the Use-Flag in all selected courses.
Select: Select courses based on different criteria.
Search: Search for courses after the Course ID in field.

[New] Records the new course.
[Edit] Edits the selected course.
[Duplicate] Duplicates the selected course.
[Analyze] Displays Analyzer-Panel to display train data during simulation.

[Sets] Course sets (groups of courses).

[Update] Update the schedule for all the selected courses.
[Delete] Deletes the selected course.
The courses panel also supports several context menu functions (right mouse button). For
example, the context menu in the Course Table allows users to quickly change the selected
entries (Invert, Unuse, Use, Edit, Duplicate, Delete).
If exactly one course is selected, the context menu contains the command Start Course for
triggering a single train simulation. This can be triggered for both courses with or without
checkmarks.
6.1.2 Defining a New Course

The Courses-Services Edit Window illustrated in Figure 60 can be used to define a new course
using the following procedure:
• Open the Courses/Services Window (Figure 59) ( Tools  Courses).

• Press “New” button to generate a new course (Courses-Services Edit Window appears).
• Enter user defined course ID and description in appropriate fields.
• Add itineraries to the course by double clicking on the desired itinerary in the Itinerary List.
• Enter additional information in appropriate fields.
• Press the “OK” button to enter the course definitively in the course list.
Figure 60: Courses / Services - Edit Window

Speedtype: Speed type (from Info  Preferences).

Route Res./Rel.: Type of route reservation and release:
Discrete: Discrete for reservation and release.
Discr./Mov. Discrete for reservation, continuous for release.
Moving: Continuous reservation and release.
Moving (CBTC): Continuous reservation and release,
type CBTC.
Route Add Res. Time: Additional course specific route reservation time in s.
Route Add. Rel. Time: Additional course specific route release time in s.
The itineraries allocated to the train are provided with priorities (1: highest priority). If there
are several different itineraries available between two points OpenTrack tries to reserve the
highest priority available track for the course.
The “Reset Itineraries” function on the Courses/Services Window removes all non-active iti-
neraries from the list, i.e. that begin in non-opened documents or no longer exist.
The reservation and release times of routes can be controlled with course specific attributes.
The attributes are named Route Additional Reserve Time and Route Additional Release Time.
The time needed to reserve a route is the sum of the course specific reservation time plus the
reservation time of the route itself. Similarly, the time needed to release a route is the sum of
the course specific release time plus the release time of the route itself.
Speed Restrictions
The performance (Performance on time / Delayed performance) is not processed with the spe-
cification of speed restrictions (Speed Restriction Signal, e.g. 30 km/h). This corresponds clo-
sely to the realistic train behavior.
OpenTrack includes a distant signal for speed restrictions (Speed Restriction Dist. Sig.). When
a train passes through the (optional) distant signal, it begins braking to the speed given by the
speed restriction.
6.1.3 Course Sets

The Course Sets function provides users with a flexible tool for selecting, editing or activating
groups of courses.
A “course set” is a group of courses defined by the user and given a name. A course can be a
member of any number of course sets.
The course sets are managed from the Course Sets panel (displayed by clicking the button Sets
in the Courses Panel).

Figure 61: Course Sets Panel
[New (used)] New course set is created with the active courses (used) of the course list.
[New (selected)] New course set is created with the selected courses of the course list.
[Duplicate] Duplicate the course set.
[Delete] Delete the course set.
Course List Functions (In Course List):
The following course list functions (In Course List) are available on the Course Sets Panel:
[Select] Select all courses in the course list belonging to the set (and deselect all
others).
[Use] Activate only the courses belonging to the set in the course list (and deacti-
vate all others).
[Add use] Activates all the courses of the course set in the course list (without deacti-
vating other courses).
[Remove use] Deactivates all the courses of the course set in the course list.
Context menus (right mouse click):
Show Course: Lists all courses of the set. The selected one will be selected in the courses
list.
Add Course: Lists all courses not belonging to the set. The selected one will be added to
the set.
Remove Course: Lists all courses of the set. The selected one will be removed from the set.
6.1.4 Course Attributes for Trains using CBTC Systems

Communications based train control (CBTC) is based on moving block signaling. In CBTC
systems, the minimum distance between two trains is equal to the actual braking distance of
the rear train plus a safety margin. Some railways add additional parameters to increase the
spacing between trains such as increased spacing in specific locations or speed dependent
parameters.

OpenTrack allows these additional parameters to be added using the attribute Route Reserva-
tion/Release in the Moving (CBTC) setting.
The minimum spacing for the setting Moving of OpenTrack is:
l (v) = lb + ls
The minimum spacing for the setting Moving (CBTC) is:
l(v) = lb + ls + lres + lrel + (tr * v)
l: Minimum separation distance [l] = m

lb: Current braking distance of the following train [lb] = m
(dependent on the actual speed v)
ls: Safety margin (from Info  Preferences) [ls] = m
lres: Reservation distance (attribute Distance to Reservation Point [lres] = m
for the current route)
lrel: Release Distance (attribute Distance to Release Point for the [lrel] = m
current route)
tr: Reaction time (attribute Release Time for the current route [tr] = s
v: Current speed of the following train [v] = m/s
The current route is determined by the location of the front (head) of the train.
6.1.5 Manual Scheduling of Individual Courses

OpenTrack allows users to manually select courses. In the Analyzer (Tools  Courses Ana-
lyzer or double click on the CourseID) the user selects whether the dispatching should be done
automatically (Automatic) or manually (Manual).
If a train is manually dispatched, OpenTrack allows users to set the route (Set Route) or
reserve a route (Reserve Route) at each signal beyond those where routes have already been
reserved (already reserved routes are shown in light green). This can be done using the right
mouse button. Users can choose from a list of all routes that are available for the course based
on the assigned itineraries (sorted by priority).
Set Route means that the route will be used, but that the route reservation will be made by
OpenTrack at the optimal time.
Reserve Route means that the route is reserved as soon as possible.
6.2 Timetable Database

The timetable database manages the desired departure times, the minimum stop times at stati-
ons, connections, and other key data for the train movements being simulated in OpenTrack.

The timetable database works closely with the course management because the timetable data-
base defines the single courses and their typification.
An entry of a course into the timetable consists of many entries into the timetable database
(course number, station, arrival, departure and minimum stop time) as well as entries per sta-
tion in the table of connections (optional). As outlined below, connections are possible for
both stopping trains and trains that pass through stations.
6.2.1 Time Format in OpenTrack

The general time format used in OpenTrack is HH:MM:SS but the application also includes an
optional day offset. The day offset enables users to run a simulation over multiple simulation
days (earlier versions of OpenTrack were limited to one service day with a maximum of 24-
hours).
The same time format is used for all OpenTrack time inputs (e.g. timetable arrival and depar-
ture times, time values for incidents, plot values, simulation starting and end-time, etc.). The
day offset default value is = 0, i.e. the first simulation day. The exact time is now defined in
OpenTrack as follows:
Time = Day Offset * 1 day + HH Hours + MM Minutes + SS Seconds
The day offset is typically shown to the left of the time information (which is displayed in the
format of HH:MM:SS). An empty space indicates a day offset of zero, in other words the day
of the first simulation day.
Users can choose whether or not to display the day offset using the attribute (Show Day) in the
timetable menu (Tools  Timetable).
Inputing times (for example in the timetable, during the definition of incidents, in the simula-
tion panel, etc.) has to be efficient. In OpenTrack users can enter as few characters as possible
to define a time.
Examples:
7  07:00:00
703  07:03:00
0703  07:03:00
73  07:03:00
7.03  07:03:00
7.3  07:03:00
7,03  07:03:00
7:03  07:03:00
07.03  07:03:00
70310  07:03:10
7.03.10  07:03:10
7,03,10  07:03:10
7:03:10  07:03:10

6.2.2 Timetable Management Window

The timetable management window (Figure 62) also enables simple recording of interval
trains. The user can define new trains modeled after the first train by simply inputing an inter-
val and the modification value of the course ID number. The timetable management window
and its attributes are outlined below.
With the exception of the departure time (Departure) at the first station, all entries for arrival,
departure and passing times are optional (if no time is defined, the cell shows HH:MM:SS).
Course Information - The top section of the Timetable Management Window presents data on
the selected course.
Figure 62: Timetable Management Window
Course ID: Course identification number.

Station: Station abbreviation.
Track (Name): Track/platform information (optional).
Arrival: Desired arrival time (HH:MM:SS = hour:minute:second).
Departure: Desired departure time (HH:MM:SS = hour:minute:second).
Use: Use departure time.
Dwell: Minimum stop time in seconds.
Stop: Check mark indicates that train stops in station.
Delta Load: Delta load in tonnes (optional) to add or remove loads (passengers and

cargo). The changed train load will influence the train behavior.
Distr.: Name of distribution function (optional); display name by checking box
Mean Delay: Average delay in seconds (exponential distribution) for delay scenarios
1 to 200 (See Chapter 8.2: Running and Monitoring an OpenTrack
Simulation on page 130).
Course-Connections Commands
[Add Rows] Adds a new row to the timetable database for a course.
[Ins. Rows] Inserts a new row into the timetable database for a course.
[Del. Rows] Deletes the selected row from the timetable database for a course.
The Functions pull down menu (directly under the schedule entry table in the Timetable
Management Window) contains several functions that can be applied to a set of selected sche-
dule entries. The parameters of each function can be edited right from the menu in the text
cell. Clicking on the Go button on the far right side causes the entries to be saved.
Functions:
Add Stops: Enter a planned station stop.

Remove Stops: Remove a planned station stop.
Set Mean Delay: Enter average (mean) delay.
Set Distr. Name: Enter the name of the distribution function.
Ins. Connection: Enter a connection.
Ins. Turnround to: Enter a turnaround definition at the last station to a different train.
Ins. Turnr. From: Enter a turnaround definition at the first station to a different train.
Connections Table - The connections table of the Timetable Management Window presents
connections data for the selected course.
Course ID: Course number to which a connection is made.

Station: Station abbreviation (station where the train makes a connection accor-
ding to the connection definitions).
Type: Alternates between the Arr./Pass. type for a relationship with the arri-
val/transit time, or Dept. for a relationship to the departure time.
Min. Wait: Minimum transfer time (HH:MM:SS = hour:minute:second).
Max. Wait: Maximum transfer time (HH:MM:SS = hour:minute:second) - after
expiry of this time or in case the delay of the connecting train exceeds
the maximum transfer time, the connection is broken. If no maximum
transfer time is defined, the connection is awaited in any case.
Join: Information whether trains are joined.
Split: Information whether trains are split.
Ref. signal: Location of the connection (entry, exit); see Figure 63 and Figure 64.
[Show Conn. Co.] Displays the timetable data of the connecting train. The timetable entry
for the station where the connection is defined is selected automatically
by OpenTrack.

[Ins. Conn.] Generates an entry on Connections Table for the selected course.
[Del. Conn.] Deletes selected connection from Connections Table.
[Show all Conn.] Display all the connections of a train (Course ID) using the connection
window.
Interval Box - The interval box can be used to define interval trains based on the selected
course.
Course ID: Change pattern of the course number.

Delta Time: Interval.
Keep Int. Ref.: At each change of a course in an interval structure all other trains in the
group are also changed.
Keep Int. Ref. Del: With any change of the delay distribution or the delay of a middle
course in a regular interval train, all other trains in the group will also
be changed.
Keep Int. Ref. Conn.: With any change of a connection of a middle course in a regular interval
train, all other trains in the group will also be changed.
Update Courses: When interval trains are added, the course is also inserted in the course
management.
[Create] Push button to create the indicated number of interval courses based on
the selected train.
Course Summary Box - Presents information on the course.
Act. Course ID: Course ID number of the actual course (selected course).
Ref. Course ID: Reference train (course) for interval trains.
Train: Further information on the selected train.
Train Speedtype: Speed type from train definition.
Train Category: Train category from train definition.
[Course]: Displays course in the courses panel (Tools  Courses).

[Remove]: A single train (course) will be removed from a group of regular interval
trains
[Show]: Displays timetable data of reference train (course).
Display Options - Allows user to set certain display options.
Show Operations: Check this box to show connections and their type in first column.
Show Stationnames: Check this box to show full station names or abbreviations.
Show Stops only: Check this box to show only stations where train stops (first and last
stations are always shown).
Show Track Name: Displays the column for track names.
Show Day: Displays the day offset for each day.
Show actual Data: Check this box to show computed times (actual times) from the last
simulation together with the planned timetable data (scheduled times).
To show this data Timetable Statistics must be chosen in Tools  Simu-
lation.

Show Delay Colors: Check this box to show deviation between actual and scheduled times
for timetable entries.
Show Use Dep. Time: Displays column with the information showing whether stations are
time comparison station.
Show Delta Load: Displays the delta load column.
Show Distr. Name: Displays column with names of the distribution functions for the station
delays.
Show Mean Delay: Displays column with mean delays for the station delays.
[Adjust] (plan. Data): The actual time (simulation-calculated) is entered in timetable database
as new scheduled time.
Timetable Window Buttons - Allows user to manage database.
[Show] Shows selected train’s timetable data in the course number field.
[Show All] Shows all timetable data.
[Sort] Sorts timetable data after the course number.
[Move] Click to move the selected train by a given amount of time (all timeta-
ble entries are changed by given amount of time).
[Add] Inserts two schedules together or appends new timetable entries on
selected trains.
[Start] Triggers a single-train simulation of the current course.
[Save DB] Timetable data are written in the database (happens automatically upon
termination of the application).
[Update] The timetable entries are updated.
[Sync.] Deletes all schedule entries which have no course record in the course
database.
[Delete] Selected train or selected connection is deleted.
6.2.3 Recording a New Timetable Entry

At this point the user has defined a course following the procedure presented in Chapter 6.1.2:
Defining a New Course on page 97 and wishes to enter timetable data for the course.
• Select desired course in the Courses/Services Window (Figure 59).

• Insure that all itinerary files belonging to the course are open.
• Press “New” button (next to text cell “Timetable: First Departure”) to generate time table
entries in Timetable Management Window (Tools  Timetable).
• Record new course data in the Timetable Management Window.

6.3 Connections
A connection is the waiting of a train at a defined location for the arrival of another train.
Connections can be made to trains (courses) stopping at stations (course arrival or departure
time is the reference time) or to passing trains (course passing time at the station cross section
is the reference time). Connection definitions are at the station cross sections in cases without
scheduled stops or at home signals in cases where connections are being used to model train
order in the simulation.
Course ID Station Type Min. Wait Max. Wait Join Split Course ID Station Type Min. Wait Max. Wait Join Split
201 ZET Arr./Pass. 00:07:00 HH:MM:SS 8002 ZET Arr./Pass. 00:00:00 HH:MM:SS
Figure 63: Connection at the Home Signal Figure 64: Connection at the Exit Signal
In the Timetable window, when you select Show Operations, the first column of the schedule
table now indicates the presence of connections both to and from a train at a station:
• An arrow pointing away from the timetable entry means that the current train offers pas-
sengers a connection to at least one other train.
• An arrow pointing toward the timetable entry means that the current train offers passen-
gers a connection from at least one other train.
Figure 65 shows a typical example of a connection relationship with the OpenTrack default
settings. Figure 65 illustrates a row from the Timetable Management Window’s Course Infor-
mation for Train (course) 20000 at station ZET (top), and the corresponding row from the
Connections Table (bottom). The figure shows train 20000 in station ZET, which departs a
minimum of 7 minutes after the arrival of the train 20001.
Course ID Station Arrival Departure Dwell Stop M. Del.

20000 ZET HH:MM:SS HH:MM:SS 30 0
Course ID Station Type Min. Wait Max. Wait Join Split

20001 ZET Arr./Pass. 00:07:00 HH:MM:SS
Figure 65: Connection
As shown in Figure 65, connection relationships can be provided with a maximum waiting
time. If this time is exceeded by a waiting train or if the connecting train has a larger actual
delay than the maximum waiting time, the connection is broken. If no maximum waiting time
is defined (entry for Maximum Wait = HH:MM:SS), the connection is awaited in all cases.
Connection relationships with train joinings, train splits or train meetings cannot have a maxi-
mum waiting time.
If a connection relationship defined in the timetable is not possible during the simulation (for
example if the connecting train is not active, or the connecting train does not pass the specified
station cross section), OpenTrack generates a warning message.
6.3.1 Recording a New Connection

• Select the line in the Timetable Management Window (course number, station) at which a

new connection is to be inserted.

• Press “Ins. Connection” (Insert Connection) to generate a blank connection in the window’s
Connections Table.
• Enter course ID number of the train to which the connection is made in the Connection field.
• Enter station abbreviation, in which the connection must take place according to the connec-
tion definition (default value: same station as for the schedule selected course)
• Enter connection type .
• Enter the minimum wait time (default: 7 minutes respectively setting in train categories).
• Enter the maximum wait time (default: unlimited - train will always wait).
• Select train joinings and splits.
• Select reference signal for conditioned connections (home or exit signal).
6.3.2 Connection Examples

Connection relationships with unlimited wait times for connections can be used to model
several typical railroad operations. (Note that in OpenTrack, if no maximum transfer time is
defined, the default value is unlimited.) The procedures for using connections to model these
operations is outlined below.
Maximum Waiting Time Connection - Figure 66 shows an example of a connection with maxi-
mum and minimum waiting times. The figure shows that train 30000 will wait a maximum of
6 minutes and a minimum of 2 minutes for its connecting train 7000 in the station ZET. The
connection is broken if course 7000 has a delay greater than 6 minutes at the last possibility of
time comparison.
Conditioned Overtaking - Connections with maximum waiting time can be used to model
conditioned overtakings. In this case a lower-priority train can be overtaken by a higher-prio-
rity train if the higher priority train does not have a delay exceeding a certain limit.

30000 ZET HH:MM:SS HH:MM:SS 30 0

7000 ZET Arr./Pass. 00:02:00 00:06:00
Figure 66: Connection with Maximum Waiting Time
Station Entry Order - Figure 67 shows how a connection can be used to control the entry order
for trains into a station. This is done by defining a connection with minimum wait time for a
train at the home signal. In Figure 67 train 301 is only allowed to arrive at station YPS after
train 201 has passed the station.

301 YPS HH:MM:SS HH:MM:SS 0 0

201 YPS Arr./Pass. 00:07:00 HH:MM:SS
Figure 67: Connection to Define Entry Order
Conditioned Halt - Figure 68 shows how a connection can be used to model a conditioned halt
at an exit signal. This is done by defining a connection at the exit signal for a planned station

passage. The train only stops at the exit signal if a connection condition has not been fulfilled,
in all other cases the train can pass the station without stopping. In Figure 68, train 8000 only
stops at the station WED if train 8002 has not passed the station.

8000 WED HH:MM:SS HH:MM:SS 0 0

8002 WED Arr./Pass. 00:00:00 HH:MM:SS
Figure 68: Connection to Model Conditioned Halt at Exit Signal
6.3.3 Split of Trains

Train split means that a part of the entering composition is uncoupled during a station stop and
then continues under its own course number. The composition of the original train is reduced
with the engines and trailing loads defined in the course management for the split train. If a
correct split is not possible (for example if the separated composition is not part of the original
train, or the separated composition corresponds exactly to the original composition), Open-
Track generates a warning message.
Figure 69 shows the course 30000, which originates at station YPS as a split from the course
20000. In the list of connections of course 20000 (figure, left side-bottom), course 30000 has
the split flag; while in the list of connections for course 30000 (figure, right side-bottom),
course 20000 is defined as a connecting course with an unlimited maximum wait time.
Course ID Station Arrival Departure Dwell Stop M. Del. Course ID Station Arrival Departure Dwell Stop M. Del.
20000 YPS HH:MM:SS 08:20:00 180 0 30000 YPS HH:MM:SS 08:19:00 0 0
30000 YPS Arr./Pass. 00:07:00 HH:MM:SS 20000 YPS Arr./Pass. 00:01:00 HH:MM:SS
Figure 69: Split of Trains
6.3.4 Joining of Trains

Joining of trains means that a train is coupled to another train at its end station and that the two
compositions continue the journey together under the course number of the second train. Simi-
lar to train splits, joining of two trains is defined by an entry in the connections table.
If at least one of the two trains can use more than one track at the meeting station (in other
words there is more than one itinerary entry in the train’s course definition), OpenTrack auto-
matically coordinates the entering of the two trains on the same track using disposition messa-
ges. The first train that knows its exact way through the station reports its station halt point to
the second train via a disposition message. From this time on the second train must select track
that can lead to the first train’s halt point.
Figure 70 presents timetable data for the meeting of courses 26000 and 26002 in station YPS.
In order to join two trains both courses must have a halt defined at the station, and show a
connection to the joining train in the table of connections (each train needs to identify the
other train in the Course ID field and include a check mark in the join field). In the simulation
the locomotives and trailing loads of one composition are added to the composition continuing

the journey after the joining.
26000 YPS HH:MM:SS HH:MM:SS 60 0 26002 YPS HH:MM:SS HH:MM:SS 0 0
26002 YPS Arr./Pass. 00:07:00 HH:MM:SS 26000 YPS Arr./Pass. 00:07:00 HH:MM:SS
Figure 70: Joining two Trains
6.3.5 Occupied Entry

Connections can also be used to model occupied entry into a station track. In an occupied
entry a train uses a station track already occupied by another train. In order to allow occupied
entry the track’s home signal must explicitly allow an occupied entry by means of a correspon-
ding signal indication (a signal aspect). The entry speed for occupied entries is reduced; the
reduced speed is also a signal attribute that can be set by the user (default value: 40 km/h). For
more information on setting attributes of signals please see Chapter 3.6: Signals on page 23.
Conditions for signals and routes to allow an occupied entry or a joining of two trains:
• Main signal (home signal) (Tools Inspector) has an activated Allow Entry in occ. Block
flag .
• Route starting at main signal (home signal) (Tools Routes) has an activated Allow Entry
in occupied Block flag.
Figure 71 presents timetable data for an occupied entry. In the figure, train 6000 awaits entry
of train 6002 in station ZET. Train 6002 stops directly behind train 6000. The table of connec-
tions for the meeting of two trains shows a simultaneous joining and splitting of the two com-
positions.
6000 ZET HH:MM:SS HH:MM:SS 0 0 6002 ZET HH:MM:SS HH:MM:SS 0 0
6002 ZET Arr./Pass. 00:07:00 HH:MM:SS 6000 ZET Arr./Pass. 00:07:00 HH:MM:SS
Figure 71: Occupied Entry
6.3.6 Turnround
Turnround means the running of a physical train composition during its operation with all its
course numbers and over all its tracks.
Continuation of a train unit at its end station under a new course number can be modeled by
creating a train split at the end station to the new course number and a connection for the new
course to the original course at its starting station.
Figure 72 shows the course 20003, which comes into being at its starting station PEW from
the course 20000, which has its end station in PEW.

20000 PEW HH:MM:SS HH:MM:SS 60 0 20003 PEW HH:MM:SS 09:15:00 0 0
20003 PEW Arr./Pass. 00:07:00 HH:MM:SS 20000 PEW Arr./Pass. 00:07:00 HH:MM:SS
Figure 72: Turnround
6.3.7 Example: Train Split and Continue Maneuver

This section presents an example of how one train can leave some of its wagons at one station
and then these wagons can continue as another train. In the example, Intercity Train IC 5000
traveling in one direction leaves cars at Station Y; these cars are then joined to a new locomo-
tive and operated as a course in the opposite direction as Intercity Train IC 6001. The locomo-
tive for IC 6001 (name: SE 70000) comes from Depot Y. The initial position of the trains is
illustrated in Figure 73 and the timetable data for Course IC 5000 for Station Y is presented in
Figure 74.
Station Y
IC 5000 S2
S3
S1
SE 70000
S4
S5
Depot Y
Figure 73: Example: Initial Train Positions

IC 5000 STAY HH:MM:SS 08:20:00 180 0

IC 6001 STAY Arr./Pass. 00:02:00 HH:MM:SS
Figure 74: Timetable Data for Course IC 5000 at Station Y
After the arrival of the course IC 5000 in STAY (abbreviation for Station Y) the rear half of
the train is uncoupled. The remainder of the train continues its course leaving Station Y via
Signal S1 no earlier than 08:20:00. The train’s uncoupled part is initialized and is assigned the
Course ID of IC 6001. The situation is illustrated in Figure 75 and the timetable data for IC
6001 in STAY is shown in Figure 76.

Station Y
IC 6001 S2
S3
S1
SE 70000
S4
S5
Depot Y
Figure 75: Example: Situation Following Separation of Cars from Course IC 5000

IC 6001 STAY HH:MM:SS 08:30:00 0 0

SE 70000 STAY Arr./Pass. 00:05:00 HH:MM:SS
Figure 76: Timetable Data for Course IC 6001 at Station Y
Next, Locomotive SE 70000 leaves the Depot Y and travels to Station Y where it joins the cars
waiting there (Course IC 6001). Figure 77 shows the timetable data for SE 70000 in Depot Y;
Figure 78 shows timetable data for SE 70000 in Station Y. Figure 79 illustrates the situation
following SE 70000’s move from Depot Y to Station Y.

SE 70000 DEPY 08:00:00 08:21:00 0 0
Figure 77: Timetable Data for Course SE 70000 in DEPY

SE 70000 STAY HH:MM:SS HH:MM:SS 0 0

Figure 78: Timetable Data for Course SE 70000 in STAY
Station Y
IC 6001 S2
S3
S1
S4
S5
Depot Y
Figure 79: Situation Before the Departure of Course IC 6001 from Station Y

As shown in Figure 76 (timetable data), Course IC 6001 can depart via Signal S2 from Station
Y no earlier than 08:30:00.
Assumptions:
• Signal S4 is a homesignal for Station Y which allows occupied entry.

• Route from Signal S4 to Signal S1 allows occupied entry.
• Signal S5 is an exit signal for Depot Y (belongs to the station area of DEPY).
• The itinerary for Course IC 5000 goes through the Station STAY.
• The itinerary for Course IC 6001 begins in the Station STAY.
• The itinerary for Course SE 70000 begins in the Depot DEPY and ends in Station STAY.
• The train identified for Course IC 6001 (initial train composition is described in the Train
Database) consists of cars (no locomotive) uncoupled from Course IC 5000.
• The train identified for Course SE 70000 consists of only the tractor.

Simulation in Open Track 113
7. Simulation in Open Track

This chapter describes OpenTrack’s simulation process. In the simulation OpenTrack models
the behaviour of all trains operating on the track network under user defined constraints inclu-
ding the infrastructure, the physical limitations of the rolling stock, and given timetable. The
first three sections of this chapter outline, respectively, the theoretical basis used by Open-
Track to simulate train motion, model protection systems (e.g. how OpenTrack reserves track
for trains); and dispatch trains.
Following these three theoretical sections, three sections describe the procedures used in run-
ning a simulation, OpenTrack’s animation features, and messages generated by the program
during the simulation process. As these sections outline, OpenTrack permits users to define
many parameters for the simulation including time interval, computation accuracy, climatic
conditions and delay characteristics. The user can also specify the amount of animation (e.g.
train positions, signal settings, occupied and reserved track sections) to be displayed on-screen
as the simulation is running. It is also possible to view the current simulation clock, the inter-
active messages, and the measuring instrument representations during the simulation.
7.1 Calculation Basis of the Simulation

The OpenTrack simulation is a mixed simulation. This means that it is a mixture of continuous
and discrete simulation processes. The continuous process consists of train motion. Open-
Track simulates train motions using motion equations (differential equations) of the vehicles.
The discrete processes include such things as changes in the state of safety installations (e.g.
signal aspects) or delays.
A numerical method (Euler’s Method) is used in order to solve the equations for train motion
since it is not possible to find the solution of the differential motion equation in a self-contai-
ned, analytical form. Euler’s method provides sufficiently exact approximate values for the
simulation.
The basic equation of dynamics (Newton) serves as a basis for the calculation of the train
motion:
F
F = m⋅a - or - a =
m
F: Tractive effort of the engine [F] = N

m: Mass of the train [m] = kg
a: Acceleration of the train [a] = m/s2
In order for a train to accelerate, the traction vehicle must transfer a force to the rail which is
larger than the traction resistance. The difference between tractive effort and traction resi-
stance is called traction power surplus and is expressed in the following formula:

114 Simulation in Open Track
FZ = Z(v) - RF(v, s)
FZ: Tractive effort surplus [FZ] = N

Z: Tractive effort [Z] = N
RF: Friction resistance [RF] = N
v: Speed [v] = m/s
s: Distance covered [s] = m
The tractive effort is calculated using the tractive effort/speed diagram and depends upon the
speed and environmental conditions (adhesion conditions). The traction resistance depends
upon train speed and the track network’s physical conditions.
The maximum technically possible acceleration rate is attained if the entire traction effort sur-
plus is invested into accelerating the train; in this case the acceleration resistance is equal to
the traction power surplus. From this follows:
FZ
a=
m • (1 + 0.01 • ρ)
FZ: Traction power surplus [FZ] = N

a: Acceleration [a] = m/s2
 Mass factor for rotating masses [] = 1
The train’s maximum possible acceleration rate at any point is also dependent on track speed
limit, the locomotive’s maximum speed, and the weight of trailing wagons.
Euler’s Method works by calculating the change in a variable from a given starting point. It
estimates each functional value using the preceding functional value (start value), the prece-
ding derivative of the function, and a fixed time step. An example of Euler’s Method for deter-
mining the speed at a time t is presented below and illustrated in Figure 80:
dv
v ( t ) = v ( t − Δt ) + Δt ⋅ ( t − Δt ) ; v ( t0 ) = v0
dt

v(t)
v(t - Δt)
t - Δt t t
Figure 80: Euler’s Method
Using the motion equation the actual speed of a train is calculated by integrating the formula
below between the valid integration limits, as shown in the following equation:
t2 dv
v = v0 + a dt - or - a =
t1 dt
Similarly the distance covered can be calculated by repeated integration of the following equa-
tion:
t2 ds
s = s0 + v dt - or - v =
t1 dt
A more comprehensive analysis of running dynamics and determination of journey times is

described in [Fil 91] and [Wie 91].
7.1.1 Modeling Braking Behaviour

It would be very complicated to simulate a train’s braking behaviour completely. The model
would need to simulate the braking behaviour of each locomotive and wagon in the train, as
well as the behaviour of the locomotive driver. Therefore, OpenTrack uses a simplified com-
putation model to simulate braking behaviour in the travel time computation algorithms which
provides sufficiently accurate results. This method is based on the braking characteristics of
each type of locomotive, it provides a braking rate for various speed intervals. Table 1 presents
an example of a braking characteristic table for a particular locomotive.

vvon [km/h] vbis [km/h] a [m/s2]

vmax 100 - 0,4
100 40 - 0,5
40 0 - 0,6
Table 1: Example Locomotive Braking Rate Table
The actual computation of the brake applications is calculated backwards from the target point
(e.g. stopping point) and its target speed (i.e. its speed at the target point). Figure 81 illustrates
a pre-calculated braking function for train T1 approaching a closed signal MS1. The marked
points in the speed/distance diagram symbolize the values of the individual calculation steps.
As soon as Train T1 crosses the brake employment point P1, it brakes to a stop following the
brake curve. Once the train reaches its target speed or if the brake action becomes void by a
status change in the protection system (e.g. if a signal changes from a stop to a proceed
aspect), then the current brake application is regarded as settled and the train is informed about
the next brake employment which must be considered. Figure 82 illustrates a braking curve for
a speed reduction example.
v v
s s
T1 MS1 T1
P1 P1
Figure 81: Brake Application - Halt Figure 82: Brake Application - Reduce Speed
7.1.2 Stopping at Stations and Stops

Figure 83 illustrates a flowchart that describes the steps that OpenTrack takes before a train
can proceed after stopping at a station or stop. As shown, before a train can proceed after a
planned stop the following criteria must be fulfilled:
• It must be later than the earliest departure time listed in the user defined timetable.
• The train must have stopped for at least the minimum halt time at the stop.
• The incidence-generated delay was taken (included).
• All the connection operations defined for the course must have been fulfilled.
If a further track segment for the course is free after fulfilling these criteria, the track segment

is reserved, before the train can accelerate and leave the stop.
Arrival at register
Station Arrival Time
[NO] Is Departure wait for wait for Are Connections [NO]

Time defined? minimal random Delay defined at Station?
Halt Time
[YES] [YES]
wait for wait for

Departure Time connecting Trains
Departure Connection
Time Criteria Criteria
fullfilled fullfilled
Application for
further Track
Segments
Reserve
Track Segments
Departure register
from Station Departure Time
Figure 83: OpenTrack Flowchart (UML Activity Diagram): Station Stop
7.2 Behaviour of Protection Systems

OpenTrack uses a protection system to ensure collision-free train operations during the simu-
lation process. The following two conditions guarantee safe operations:
• Each track section is reserved either for no trains or at most one train.
• Each train must be able to stop within the track section reserved for it.
The protection system and safety philosophy are used to define the effective distance ahead of
and behind a train that lies in the train’s protected zone. The method currently used by rail-
roads is to release track sections in discrete units, or routes. Each route is protected by a main
signal, which prevents movement of trains on the route when it is set on stop. The flowchart
illustrated in Figure 84 outlines the conditions for a successful route reservation. A route can
be reserved and its main signal display the appropriate signal for proceeding only if:
• All safety elements belonging to the route are free or reserved for the applying train.
• The applying train must have a free continuing way at the end of the route.
• The free blocking is ensured, i.e. prevent the situation where two trains have the same
track section available for occupation (deadlock).

Inquiry: Can
Track Segment
be reserved?
Are all Safety

Overlap Deadlock
Elements free or
available? impossible
reserved for Train
[NO] [YES] [NO] [YES] [NO] [YES]
reserve
Track Segment
unsuccessful successful
Figure 84: OpenTrack Flowchart: Track Segment Reservation
The two following figures illustrate the behavior of the protection systems following a request
for track segment reservation by a given train for two examples.
Figure 85 illustrates the case of a successful route reservation. In this example Train T1 is
approaching the point (AP1) of requesting the route from MS1 to MS2. As the figure shows,
the train’s brake curve has been precalculated for the possibility that Train T1 will need to stop
at Point MS1. In the example Train T1 receives permission to proceed on the route MS1 to
MS2 and so the figure shows the train continuing at speed vT1 until it the point where it is
necessary to brake to stop at point MS2.
v
T1
s
T1 DS1 MS1 DS2 MS2
AP1
Figure 85: Successful Track Segment Reservation

In contrast, Figure 86 illustrates the case of an unsuccessful route reservation. In this example
Train T1’s request to enter the section behind Signal MS1 fails despite free safety elements
because a part (segment overlap in the figure) of the through route is being used to accommo-
date Train T2. Thus Train T1 must assume that it will need to stop at the beginning of the
requested route (at MS1) and can proceed past main signal MS1 only when Train T2 moves
into the siding and can release the section of the through route requested by Train T1.
v
T1
s
T1 DS1 DS2/MS1 MS2 T2
AP1
DS4/MS3 DS3
MS4 Overlap
Figure 86: Unsuccessful Track Segment Reservation (Through Route not free)
Route Reservation (Discrete Block)

Open Track calculates the optimal location for the route reservation so that the route is reser-
ved once the train has reached the point within sight of the first distant signal for the start
signal of the route. This means that the train driver should (almost) never see a “warning” indi-
cation on a distant signal or combined signal. If the line is equipped with loop or radio signa-
ling (Edge Attribute Loop / Radio (ETCS)), then the point is chosen based on the predicted
braking point of the closed main signal, rather than the distant signal location.
The automatic route reservation can be adjusted using the route attribute Distance To Reserva-
tion Point [m]. This is especially helpful for railway systems in which automatic route
reservation tends to be done too early. The attribute allows users to define the earliest possible
point where OpenTrack can attempt to reserve a route. This distance describes the train’s
effective distance from the main signal before OpenTrack first attempts to make a route reser-
vation.
The other conditions for successfully reserving a route are the same, the train must be located
within sight distance of a distant signal or main signal, cross over a balise, be located on a loop
antenna, or on a line equipped with cab signaling.
The reservation distance function is activated by clicking on the corresponding checkbox on

the Route Inspector panel. Automatic route reservation continues to be the default behaviour
for OpenTrack.

Figure 87: Route Edit Panel (left shows automatic route reservation, right shows route reser-
vation with a specified reservation distance).
Example:
Signal S1 is a combined signal with a distant signal for Signal S2. In the automatic route reser-
vation method OpenTrack tries to complete the reservation of route R2 once train T1 reaches
the point where it can see the distant signal (distance to signal S1 = sSight (S1)), i.e., the point
marked RP1(R2) on Figure 88. If the route R2 has a specified Distance to Reservation Point (s
Res. (R2)) then OpenTrack tries to complete the reservation process when the train reaches point
RP2(R2), in other words, the moment when the train is within the defined distance (s Res.(R2))
from the starting signal for route R2.
If the sight distance (s Sight (S2)) is less than the Distance to Reservation Point (s Res. (R2)), the
route segment is reserved when the train reaches the sight distance point.

v
Speed
Distance s
Train T1 Signal S1 Signal S2
Route R1 Route R2
S Sight (S1) S Sight (S2)
S Res. (R2)
RP1(R2) RP2(R2)
(for an automatic Reservation of Route R2) (using a “Distance to Reservation Point” for Route R2)
Figure 88: Route Reservation
Users can also specify the release point for a route. This is done using a checkbox on the Route
Edit panel (Tools  Routes). If it is not checked, the route segment is released when the rear
of the train passes the end signal (Dist. To Release Point = 0 m), if the box is checked, the user
specified value is used.
Here it is also important to note that the route release process begins when the end of the train
has passed the vertex that is beyond the route release distance from the route’s endsignal.
Example:
The specified distance to release point for the example main signal = 30 m. After the main
signal there are two edges both of which are 20 m in length. In this case the release process
starts when the end of the train is at least 40 meters beyond the main signal.
7.2.1 Moving Block Signal System

The second major type of signaling system is a moving block signal system. A moving block
signal system is characterized by flexible block lengths; the block length is calculated based
on train braking characteristics, train speeds and track layout. In contrast to fixed block
systems, in a moving block system the flexible block (Moving block) is continuously exami-
ned to determine whether it is the appropriate length for the optimal progressive movement of
the train while maintaining the necessary braking distance from other trains (i.e. track seg-
ments occupied or reserved for other trains). During acceleration or travel at constant speed
the moving block system constantly checks that the train remains within its safe current bra-
king distance. If the system recognizes a point of conflict, it moves into the next more restric-
tive speed condition. Figure 89 shows the process used by OpenTrack to reserve track sections
in moving block signal systems.

Inquiry: Is 'n'
Meter further
Route available?
Are all Safety

Deadlock
Elements free or
impossible
reserved for Train
[NO] [YES] [NO] [YES]
reserve new
Elements
Figure 89: OpenTrack Flowchart: Route Reservation with Moving Block
Figure 90 illustrates the braking behaviour of Train T2 as it approaches a stopped train (Train
T1) in a moving block signal system. In the figure Train T2 has been accelerating up its maxi-
mum speed, but at time (t-Δt) it receives a warning that further acceleration is impossible
given the available braking distance. At the time t Train T2 begins its effective brake applica-
tions, with the goal of stopping behind Train T1. During each brake step the system examines
whether Train T2’s speed can be increased, which would only be true if Train T1 moved far
enough to the right to shift Train T2’s danger point, thus permitting a termination of braking
for Train T2.
v
vm
s(t-∆t) s(t) s(t+∆t) s
T2 T1
Figure 90: Moving Block: Braking Behaviour
Trains following closely after other trains in moving block sections observe the parameter:
acceleration delay (Acc. Delay [s]). Acceleration delay is set using the train definition func-
tion (Tools  Trains).

Acceleration delay is used when a following train needs to slow down due to a preceding train.
In this case, the second train waits for the time set in the Acc. Delay parameter before accele-
rating again. This prevents creating a cycle of braking and accelerating and reflects actual train
behaviour more realistically.
Moving block trains, which travel on “Discrete for Mov. Block Operations” routes, use the
release groups of the corresponding routes. This means that these release groups of a route will
only be released after the train has left the release group completely.
7.3 Dispatching in OpenTrack

OpenTrack’s dispatching module performs the central task of time sensitive track segment
reservation and providing appropriate the travel commands to individual trains during the
simulation process. The dispatching module also controls the optimal progress of trains
through pre-reservation of track segments and selecting alternative routes based on priority
settings.
The flow chart in Figure 91 illustrates the interaction between the dispatching and safety
systems when routes are requested. The dispatching system communicates to the safety
system the starting point of the train and the number of track segments it wishes to reserve.
Reasons for pre-reserving several routes include:
• Train can travel at a higher speed on the route, if the subsequent route is also reserved.
• Reserving only one route segment could lead to deadlock.
The route request function of the safety system sorts route start positions according to ascen-
ding position for each requested route segment following the process illustrated in Figure 83
until either it encounters a route segment that cannot be reserved, or until all the route seg-
ments have been successfully reserved. The process is considered successful if at least one
route segment can be reserved (m > 0). The dispatching module is informed about the success
and/or failure of each individual inquiry.
OpenTrack’s dispatching module continuously examines possible route changes in the courses
operating on the track network. The dispatching module assesses, with each route request
inquiry, possible route changes, which could make the course’s highest priority route availa-
ble.

Dispatching Interlocking
Dispatching
possible to reserve
'n' Routes
Inquiry: Can 'n'

Routes be
reserved?
*[for all 'n' Routes]
*[for all 'n-m' not

[m = 0] Dispatch reserved Routes] Attempt
Report to reserve
Routes
*[for all 'm' successfully

reserved Routes]
Dispatch *[for all 'm' Routes] set

Report Signals
Figure 91: Open Track Flowchart: Dispatching Multi-Route Segment Routes
Figure 92 illustrates an example of OpenTrack’s route selection process. In this example, Train
T1 tries to receive authorization for using its highest priority route R1 (from Signal S1 to
Signal S2) for entry into the station. Since Route R1 is partially allocated to Train T2 the
safety system rejects Train T1’s request for the route. Train T1 then tries to receive authoriza-
tion for its second ranking route (Route R2) which the safety system confirms is available and
therefore the route is certified. The dispatching module attempts to move trains operating on
low priority routes to high priority routes as quickly as possible.
S4
T1 S1 S3
S2
T2
AP
R3 (S1-S4)
R2 (S1-S3)
R1 (S1-S2)
Figure 92: Example: Choosing a Route

Dispatching at Signal Groups

There are severak dispatching possibilities at a main signal within a station area. The main
signals have an attribute Dispatching, which describes, which criteria should be used to con-
trol trains at this signal. The following criteria are possible:
• Default - trains follow the rule: first come first serve

• Priority - the train with the highest priority goes first
• Delay - the train with the largest delay goes first
• Wait Time - the train that has waited the longest at the signal goes first
• Arrival Time - the train that has arrived first at the signal goes first
OpenTrack allows users to distinguish whether the stopping train (or soon to be stopping train)
should be taken into account when making dispatching decisions (the suffix "+" indicates that
the stopping train is involved, "-" indicates that this is not the case).
Under the Arrival Time disposition strategy the first train to be dispatched is the train that
arrived first or stopped first. It is a “First In First Out” strategy (FIFO), i.e. the train that
arrives first leaves first and is not overtaken by other trains.
The difference from the criterion Wait Time is that in the Wait Time option, the wait time only
begins to run when the train is stopped at the signal (= conflict of the type: Stop at Signal),
which is not the case during a normal station stopping process. Under the option Arrival - the
time, after which the train will be dispatched, starts to run when the train arrives at the station
or when it stops at the main signal.
Whenever a route reservation attempt is made for a route R1 over a signal in a station area
which has its dispatching priority set as Priority, Delay, Wait Time or Arrival , OpenTrack
checks to see if another train will reserve a route R2, which would conflict with R1. If Open-
Track detects this type of conflict and if the starting signal for route R2 has the same
dispatching criteria, then the train order is determined in accordance with the defined criteria.
The following examples show how trains would be dispatched under the priority criteria.

Example 1 (Figure 93)

The train T100000 (with priority 2) is waiting at Station Y and is ready to leave. The train
R10002 (with priority 1) needs to use the same track segment after Station Y as train T100000.
Since train R10002 has higher priority it is the first train to leave.
Station Y
R10002
T100000
Signals: Dispatching Priority
Station Y
R10002
T100000
Signals: Dispatching Priority
Figure 93: Example of “Priority-based” Dispatching
Example 2 (Figure 94)

This example shows dispatching based on the criteria of actual train delay. Both trains want to
use the same track segment. Since train P15000 is more delayed it receives priority for using
the segment.
Station Y
P15000
X2000
Signals: Dispatching Delay
Station Y
P15000
X2000
Signals: Dispatching Delay
Figure 94: Example of “Delay-based” Dispatching
A special case applies where a conflict occurs between two trains, but the second train stops in
a station and/or has a station stop planned. In this case priority is given to whichever train is
ready for departure.

Running an OpenTrack Simulation 127
8. Running an OpenTrack Simulation
8.1 Preferences
The Preferences Window (illustrated in Figure 95) is used to select files and parameters for
use in the simulation process. Preferences are managed in so called sets. A set, which is iden-
tified by the set name, comprises a single combination of the parameters. Existing sets can be
edited and new sets created using the Preferences Window.
Info  Preferences activates the Preferences Window.
Figure 95: Preferences Window
The following parameters and filenames are managed using the Preferences Window:
Selected Set: Active set (active OpenTrack project).

Open Docs.: Open documents when set changes (see below).

128 Running an OpenTrack Simulation
File Management Parameters
OpenTrack Home Dir.: OpenTrack home directory, this can be used to set the directory in
which all the OpenTrack projects and data is stored.
Preferences Path: The file path for saving user preferences, is built from Home Dir
+”\Library\OpenTrack”.
Dest-Info: Itinerary database filename.
Engine-Depot: Locomotive database filename.
Trains: Train database filename.
Courses: Course database filename.
Stations: Station database filename.
Timetable: Timetable database filename.
Output-Path: Output path and filename into which the output files are written.
Train Speed Types - Table lists Train-Speed-Types used in the simulation. (A separate speed
can be defined per traintype, edge and direction). Traintypes can be added or deleted, respecti-
vely, via [Add] and [Delete].
Saving - When the “Create Backup Files” box is checked, a copy of the existing (original) file
(documents or database files) is made before the document (new) is saved at each backup
procedure. A tilde (~) is added to the file name of the copy. The autosave function saves the
active document regularly based on a user defined time interval.
Display Options - These settings relate to the display of elements, courses and legends.
Highlight selected Edges: The selected edges of the worksheet are highlighted.
Show Switch Positions: Shows the position of switches.
Toggle Windows: Memory reducing mode for viewing animations (disadvantage:
pixels will blink periodically).
Use Vertex Tooltips: Open Track creates a tool tip that displays the kilometer and
name for all vertices when it loads documents and when vertex
information is changed. Attention: this feature uses a significant
amount of computer resources and therefore it is advisable to
disable it for large documents.
Use Sound: OpenTrack will make indicate a pause in or the end of a simula-
tion with an acoustical signal.
Legend: This character string appears as the title of all legends.
Train Categories: The number of train categories and the colors in which they can
be visualized can be selected here (color for train number in the
animation, distance/time line in the train graph). If a category is
provided with a checkmark in the first column, it is also shown
in the legends. The position can be varied within the list via the
up and down arrows.
Conflicts: The colors and designations of the various types of conflicts for
the train graphs can be edited here.
Use Category Color: Check this box to display the planned timetable data in the same
color as the actual timetable data.

Dashed Line: Check this box to display the planned timetable data with a das-
hed line.
Pattern (Occupation): Fills the blocking time stairway with a gray shading or cross-
hatch.
Calculation
Use Curve Resistance: If box is checked the curve resistance will be computed, other-
wise an average value is used.
Use Switch Time: If box is checked the defined switch operation times and route
reservation times are used during the simulation, otherwise
default value (switch time = 0) will be used.
Safety System - ETCS Level 2 - These variables are only used in situations with European
Train Control System Level 2 signal systems.
Communication Period: Period duration for ETCS level 2 communication between RBC
and train.
Optimization Period: Period duration for optimization of ETCS level 2 distances
(optional).
Optimize Train Sequence: If box is checked course sequence may be changed in optimiza-
tion process.
ETCS L3 Safety Margin: Minimal safety distance between trains operating under moving
block control.
Preference Set File Commands
[Export] Export all setting information into a text file.

[Import] Import all setting information from a text file.
[Load DB from Dir.] Loads a set of preference settings (databases) from a user-defi-
ned directory.
[Delete Set] Deletes the displayed set of preference settings.
[Save Set As] Saves the displayed set of preference settings under a new name
[Cancel] Cancel the preference settings.
[OK] Save the preference settings.
The setting checkbox Open Doc. in Preferences facilitates the handling of documents and
document sets with the same project name. When Open Doc. is selected, OpenTrack attempts
to open all the documents in a document set with the same name as the active project, as soon
as OpenTrack is started or when the active project is changed (using the command Selected Set
in the Preferences). For example, both the Selected Set from the Preferences (Info  Preferen-
ces) and the Document Set (Document  Documents Sets...) have the name Pro-
ject.South.2020.
Recommended project organization / file structure:
It is highly recommended to organize OpenTrack projects on the computer with the focus that

they are easy and efficient to use, exchange with other users (or the support organization) and
to backup.
- OpenTrack (OpenTrack directory OpenTrack folder)
- Projectname 1 (directory for project 1, project folder 1)

- OTDocuments (directory for infrastructure documents)
- OTDiagrams (directory for train diagrams)
- OTData (directory with 6 databases)
- OTOutput (output directory)
- Projectname 2 (directory for project 2, project folder 2)

- OTDocuments
- OTDiagrams
- OTData
- OTOutput
8.2 Running and Monitoring an OpenTrack Simulation

This section describes how the user can run a simulation using OpenTrack and how simulation
progress can be monitored on screen. The following two sections describe OpenTrack’s ani-
mation and monitoring message features respectively.
OpenTrack users set parameters regarding control and monitoring of the simulation using the
Simulation Window. The Simulation Window is used to input information used to define the
simulation and output information, including simulation input values (e.g. time window,
scenarios, delays, ...) and the desired output quantities and diagrams.
The general process for running an OpenTrack simulation consists of the following seven
steps:
1. Open Simulation Window (Tools  Simulation).

2. Enter simulation time interval (Start Time / Stop Time) and all other simulation para-
meters in the Simulation Window (Figure 96).
3. Select “Output” in the Simulation Window’s selection box (top of window).
4. Specify evaluations to be performed on the Output Window (Figure 97).
5. Press “Start” button to begin simulation.
6. The simulation clock begins to run.
7. After expiry of the simulation time (Stop Time) the simulation is ended.
During the simulation process, the simulation is worked off step by step (dependent on the
time step set by the user [Step]). At each time “t” the trains calculate their actual position,
speed and acceleration. The necessary routes are requested automatically by the trains and
reserved, if possible, and the appertaining signals are set on proceed. If a route cannot be reser-
ved (e.g. if it is occupied by another train, or the route is blocked, etc.), the train brakes so that
it comes to a standstill at the main signal before the route in question.

The Simulation Window is used to enter parameters for the simulation and to start the simula-
tion. The information presented in the Simulation Window is described below.
8.2.1 Simulation Window

Simulation Menu: Box allows user to select Simulation Window or Output Window.
Start Time: Start time of the simulation (courses with first departure time < start
time are not included in the simulation).
Stop Time: End of the simulation interval (courses with first departure time > stop
time are not simulated).
Break Time: Time at which the simulation is to be interrupted.
Step: Time step of the simulation in seconds (large step: fast but less exact;
small step: slow but more exact).
Current Time: Current simulation time (if selected).
Scenario
Adhesion: Adhesive scenario (good = good adhesion; normal = normal adhesion;

bad = bad adhesion).
Adhesion Tunnel: Adhesion scenario for track segments in tunnels.
Delay Scenario: Delay scenario (for break-down delay and extended station halts).
none: No delay scenario used in simulation.
defined: User defined delay scenario (no random values).
No 1 .. No 200: Incident delays with defined avg delay (Mean Delay)
Simulation Run: For multiple simulation: current simulation run / total number of simu-
lation runs (the default value for number of simulation runs is 1).
Mean Delay: Average beginning delay for courses without initial delay (first depar-
ture time in the timetable with delay entry).
Performance: Scaling value for acceleration and maximum speed (initial state 100%).
Misc.
Keep Occupations: Check box to indicate that the railway network is not freed from all
occupations before the simulation (is needed to e.g. build in hindrances
in the network).
Opt. Dispatching: Check box to indicate that train dispatching should be optimized (only
available for ETCS-Level 2 track segments and for dynamic overta-
king).
Pause if Sig. Stop...: Pause the simulation when a train stops for a given amount of time in
front of a closed signal (Stop at Signal).

Figure 96: Simulation Window Figure 97: Output Window
Animation
Show Train: Reserved elements, occupied edges and signal positions are displayed
during the simulation
Show ID: Current position of the train is displayed with train number. The size of
the text label can be set by the user (XXS, XS, S, M, L, XL, XXL).
Show Description: Train description is displayed on worksheet.
Show Delay: Train delay, can be shown in seconds (Sec.), minutes (Min.) or minutes
and seconds (M:SS).
Show Current Time: Check box to show running clock in the Current Time field (makes the
simulation slower). The current time can be shown in seconds (S),
hours and minutes (HH:MM) or hours, minutes and seconds
(HH:MM:SS).
Show Messages: Messages on the state of the simulation, on the driving trains, on
disabled states and hindrances are shown in the message window.
Show Instruments: The measuring instruments show the data of the passing trains.
Simulation Control Buttons
[Start] Starts the simulation.

[Step] Runs the simulation for a single time step.

[Pause] Interrupts the simulation.
[Stop] Terminates the simulation.
8.2.2 Output Window

The OpenTrack user can specify which evaluations are produced by the program using the
Output Window shown in Figure 97. The virtual tachometers for individual trains (courses)
store the selected data during the simulation and following the simulation save the data to a
group of output files (for additional information on evaluations please see Chapter 8.7:
Evaluations on page 150).
Data and options in the Output Window are outlined below.
Simulation Menu: Box allows user to select Simulation Window or Output Window.
Data: Selection continuous (value for each time step) or discrete (value only
if different) output values.
Units: Format for distances (metric, UK Imperial, US).
Output Type Checkboxes
Use these checkboxes to select types of output diagrams and information collected during the
simulation.
Occupations
Occupation objects can contain several edges and a text label. An edge can belong to at most
one occupation object. After a simulation, the text label can show statistics on the occupation
object (number of trains, average number of trains per hour, maximum number of trains in any
hour, average occupancy in percent, maximum percent occupancy in any hour).
To create an occupation object, first select the appropriate edges. Now going into the Simula-
tion window, and press Add. (OpenTrack will refuse to create the occupation object if an edge
is already in another occupation object.) In the table Occupations, OpenTrack adds the newly
created occupation object to the bottom of the list. You can click on the object to change its
name.
Immediately below the Occupations table, a pull down menu initially marked No Show lets
you choose how to visualize the infrastructure occupancy. The following options are available:
Menu option: Coloration of edges shows:
• No Show No coloration
• Show avg. Number of Trains Average number of trains
• Show max. Number of trains Maximum number of trains
• Show No. of Trains in Time Slot Number of trains during the user-defined time interval
(Time Slot)

• Show avg. Occupation Percent Average occupation.

• Show max. Occupation Percent Maximum occupation.
• Show Occ. Perc. in Time Slot Percentage of occupancy during the user-defined time
interval (Time Slot).
OpenTrack displays the occupancy in one of four colours based on user-defined thresholds as
follows:
• H High threshold (values above this level are shown in red).

• M Medium threshold (values above this level are shown in orange).
• L Low threshold (values above this level are shown in yellow).
• OpenTrack shows values below the low threshold level in green.
In calculating the average values, OpenTrack uses the time between the first and last process
in the simulation (and not the simulation interval Stop Time minus Start Time).
You can now also have OpenTrack output occupation statistics as bar graphs. To do so, select
the corresponding output type (Occ. Stat.) in the Plot Inspector. The colours of the bars are
those you define in the simulation panel for the categories High, Medium und Low.
[Add] Inserts selected edges of the active document in allocation evaluation.

[Delete] Deletes selected entries of the allocation evaluation.
[Show] Highlights edges that belong to selected allocation evaluation on worksheet.
[Invert] Inverts the Use-flag of the selected allocations.
8.3 Incidents
OpenTrack allows users to examine the impact of disturbances (called “Incidents”) in the
infrastructure, rolling stock and schedule systems. Incidents can either be operational failures
or operational problems (which allow operations to continue but at a reduced speed or capa-
city). Examples of the first type of incident include signal failure and broken track; examples
of the second include slow orders or unplanned train delays. OpenTrack also allows users to
combine individual incidents into sets of incidents that can be applied during the simulation.
All incidents have a starting time and ending time. Route, path and course incidents also have
an associated speed (v >= 0) which applies during the incident.
This section describes the Incidents Window, using the Incidents Definition Window to define
infrastructure and rolling stock incidents, defining incident sets and information on how to
define schedule incidents.
8.3.1 Incidents Window

The Incidents Window is where users can define incidents and select which incidents are used
in a simulation. The Incidents Window is illustrated in Figure 98.
The top portion of the Incidents Window displays a table listing the user-defined Incident Sets.

OpenTrack enables users to define these sets by selecting individual incidents and saving them
under a unique name. The bottom portion of the Incidents Window displays a table listing all
the user-defined individual incidents. The process of defining an incident and incident set is
outlined below.
Figure 98: Incidents Window
Incident Sets Table:
Incident Set Name: User-defined name of the incident set.

No. of Incidents: Number of individual incidents in the set.
[Select] All the individual incidents in this set are highlighted.

[Use] Places a check mark in the Use column for all individual incidents inclu-
ded in the set.
[Unuse] Removes the check mark in the Use column for all individual incidents
included in the set.
[Update] Redefines the incident set to include all individual incidents with check
mark in the Use column.
[Delete] Deletes the selected incident set.
List of Incidents Table:
Use: Checkmark indicates that this incident will be used in the simulation.
Incident Name: User-defined name for the incident.
Comment: User-defined comment for the incident.
Type: Type of incident (Train, Signal, Edge, Route, Path).
Object: Impacted infrastructure object or affected course.
Begin: Start time for the incident (HH:MM:SS = Hour:Minute:Second).
End: End time for the incident (HH:MM:SS = Hour:Minute:Second).
Speed: Maximum speed (in km/h) to be operated during incident.

[New] Define a new incident.

[Edit] Edit selected incident.
[Duplicate] Duplicate selected incident.
[Show] Display infrastructure incident elements on worksheet.
[Save Set] Save all checked incidents as an incident set.
[Delete] Delete selected incident.
[Sort] Sort incidents list based on defined criteria.
[Inv.] Invert the Use check mark for all selected incidents.
[Unuse] Delete the Use check mark for all selected incidents.
[Use] Add Use check mark for all selected incidents.
Defining a New Incident:

In order to define a new infrastructure incident (signal disturbances, route disturbances, closed
track sections), the appropriate objects must be selected in an active worksheet. Then, the
disturbance information can be input using the Incidents Window. Disturbances can be defined
for entire track sections as well as for groups of routes (paths).
Signals with defined disturbances are displayed on the worksheet with a red rectangle border.
No route behind the signal can be run, as long as the signal is disturbed. A signal disturbance
can be introduced using the Incidents Definition Window or using the Signal Inspector
(Change State command).
Define an individual incident using the following steps:
• Open Incidents Window (Tools Incidents).

• Mouse click on NEW button to display Incidents Definition Window (Figure 99).
• Select incident type (train, signal, edge, route, or path).Select impacted infrastructure object
on worksheet (train number or infrastructure element).
• Define incident attributes in the Incidents Window.
Figure 99: Incidents Definition Window

Type: Select type of incident.

Object: List of all selected objects in the document with the selected incident
type.
Incident Name: User defined name for the incident.
Comment: User defined comment for the incident.
Probablity: Probability of the incident occurring (in percent).
Begin: Incident start time (HH:MM:SS).
End: Incident end time (HH:MM:SS).
Begin Distr.: Distribution function for disturbance start time (optional).
Duration Distr.: Distribution function for length of disturbance (optional, however if this
is defined then the user-defined end time will not be used).
Speed: Maximum speed for operations during incident (in km/h).
Wait Time a. Stop: Delay in starting after an incident of the type Stop and Wait (in seconds).
Valid for Head: Incident valid only for head of train (default: incident applies over the
entire train), e.g. if a signal breaks after the locomotive has passed the
signal then the incident does not impact the train.
Periodic Incident: Periodically occurring incident (on: incident active, off: incident inac-
tive).
Incidents Definition Window Parameter Descriptions

This section describes several of the Incidents Definition Window parameters in more detail.
The Discrete for Mov. Block Operations parameter allows users to classify train or route inci-
dents explicitly for trains travelling under Moving Block controls. This is done by checking
the Discrete for Mov. Block Operations box. Under this classification a disturbed route must
be free from all other requests, before the train can move. With this type of disturbance all
controls are requested in discrete form rather than continuous.
The Periodic Incident parameter allows users to define track incidents as occurring on a peri-
odic basis. A period sequence indicates (in seconds), how long a disturbance is active (i.e. how
long the disturbance lasts), then is inactive (i.e. the period when there is no disturbance), then
active again. The period sequence can contain a maximum of four times (incident active 1,
incident in-active 1, incident active 2, incident in-active 2). This feature enables users to
model traffic signal operations and tram crossings more easily.
OpenTrack allows users to define several types of incidents relative to the Kilometerisation of
the track sections, which means that the track network must be completely defined (all nodes
must have accurate Kilometer coordinates and the edge directions must be defined in ascen-
ding order).
Additionally, the edge attributes Line Name and Track Name can be used. If these attributes
remain empty (Line Name = “ “ and/or Track Name = “ “) then the incidents will apply to all
track sections in the defined segment. An incident can only apply for a Line Name and/or a
Track Name.

The following types of incidents can be defined:
Position Incidents:
• Train moves within the incident zone at reduced speed or stops (Speed = 0 km/h).
• A position incident can be defined at an exact location (independent of the edges).
• A position incident can be defined by direction.
• A position incident can apply to the head of the train or the entire train.
Blockage Incidents:
• Blockage incidents affect all edges between the beginning and the end of the disturbance.
• Trains travel to the signal just before the incident zone (in the travel direction) and stop
there.
• Blockage incidents can be defined at an exact location but the impacts depend on the edge
direction.
• Blockage incidents impact travel in both directions.
Stop and Wait Incidents:
• The impacted train will stop and wait for the user defined wait-time (Wait Time after Stop)
then the train will begin moving again.
• Stop and Wait incidents can be defined at an exact location (independent of the edges).
• Stop and Wait incidents can be defined by direction of travel.
• Stop and Wait incidents can apply to the head of the train or the entire train.
Train Tractive Effort Incidents:
This type of incident (Train Tractive Effort) can be used to reduce the tractive effort for an
individual train for a set amount of time. The attribute Used Tractive Effort defines the percen-
tage of the normally available tractive force that is available during the disturbance (based on
the train’s tractive effort/speed diagram).
Signal/Group of Signals Headway Incidents:
The incident type called Signal/Group of Signals Headway allows users to adjust the through-
put (or headway) through a given point in the network.
The attribute Signal Headway (in seconds) determines the amount of time after the first train
has passed through the signal (or group of signals) before another train can pass through the
signal (or group of signals).
Signal Stop Incidents:
The Signal Stop incident type can be used to influence the behaviour of a train that wishes to
reserve a route at the specified main signal.

The attribute Stop Probability gives the probability that a train will need to come to a stop (as
a percentage). The attribute Stop Time / Distribution specifies how long the train will remain
stopped. The Stop Time / Distribution can be entered in seconds or it can refer to a distribution
function defined using the distribution tool (Tools  Distributions).
Incidents that use a predefined distribution function (Tools  Distributions) can be assigned
directly in the Incident Edit Panel. A combo box is visible beneath the respective text cells
(down arrow), which makes the selection possible.
However, each text cell is still independent, so that the inputs can be made directly in the text
cell, this is especially important where a text cell can contain a time value in seconds or the
name of a distribution function.
8.3.2 Creating Incident Sets

Users can combine incidents to create user-defined Incident Sets. Incident sets are groups of
incidents (disturbances) that are saved under a common name. Incident sets are created using
the commands at the bottom of the Incidents Window's top table (see Figure 98).
An Incident set is created by marking the desired incidents in the table of incidents located at
the bottom of the Incidents Window and then using the command Save Set to create the new
set. This will cause users to be prompted to enter an Incident Set name.
The user defined incident sets can be managed using the command buttons at the bottom of the
Incident Set table. Incident sets can be updated with new incidents or deleted using these com-
mands.
The command (Use) allows users to select the set of incidents that will be used in an Open-
Track analysis.
8.3.3 Schedule Incidents

Schedule related incidents are managed in the individual train schedules (see Chapter 6.2) or
by using the train categories function (see Chapter 5.5). Therefore this section only presents a
brief overview of the types of timetable incidents and how they can be managed.
A more common expression for schedule incident is delay.
Initial Delay
The definition of an initial delay is: the train delay measured when the train crosses the border
into the system being investigated (section, node, network). [Source J. Pachl]
Initial delays in OpenTrack can be defined for individual trains, train categories or globally
(i.e. for all trains).
Initial Delay set Globally

A global initial delay is introduced into the OpenTrack using the Mean Delay parameter in the

Simulation Window (see Chapter 8.2.1). Users can enter a mean delay in this field and it will
be applied to all trains in the simulation except for those trains that have individually defined
initial delays or that are members of a train category that has an initial delay parameter.
When and how this average delay value is used is outlined below.
Initial Delay by Train Category

OpenTrack allows users to assign initial delays to train categories using either a negative expo-
nential or piecewise linear distribution function, combined with a random number generator.
The application also provides two functions to better control the delay. First, OpenTrack
enables users to set a maximum delay, this means that the randomly generated delay values
that lie over this ceiling will be reduced to the maximum delay. Second, users can set a maxi-
mum percentage of trains that will be assigned a delay (for negative exponential distribution
only).
Setting the initial delay by train category is described in Chapter 5.5 above.
Initial Delay and Station Delays by Individual Train

OpenTrack also allows users to assign initial delays to individual trains that do not have delays
assigned through their train categories. This is done using the Timetable Window (shown in
Figure 62).
The Timetable Window lists the stations visited by the specific train (course) in the upper
table. The right column is labelled M. Del. (for mean delay) and the user can enter the mean
delay expected at that station for the individual train here.
A train's initial delay is entered in the cell for the first station in the train's schedule. Additional
delays can be entered into other cells to represent station delays at intermediate stations.
The mean delay can be used directly as the delay for a specific train at a specific station, or it
can be used together with a user-defined delay distribution function to generate a probabilistic
delay value. In order to use the delay distribution method, users need to check the box in the
bottom right corner of the Timetable Window and select a distribution name from the pull
down menu.
The process of creating user-defined distributions is described in Chapter 5.6: Distribution

Functions in OpenTrack on page 93.
The delay applied at the first station a train experiences in the network being modelled is defi-
ned as the initial delay. This initial delay is applied to both trains that begin their trip at the sta-
tion (with v = 0 km/h), as well as to trains that do not stop at the station (with v > 0 km/h), but
for which the station is the first station they experience entering the network being modelled.
For all the other stations a train passes through, the (optional) user-defined delay functions as
a station delay (i.e. longer than planned stop at a station). A train's departure from a station is
calculated by adding this delay to the scheduled departure time and/or minimum station dwell

time.
Regarding station delays, it is possible to define a limit on station delay on a train category
basis. This means that delays greater than the maximum value will be set at the maximum
value. The maximum delay values and a box (Use max. Station Delay) that must be checked to
use these values are located in the Train Categories Window (see Figure 56).
The type of delays that are used in a simulation are selected in the Simulation Window (see
Figure 96). There are three general delay scenario options:
• Delay Scenario None The delays are not used

• Delay Scenario Defined Delays will be defined precisely using the mean
delays
• Delay Scenario No.1…No.200 Delay values will be generated using a random
number generator combined with the average
values of the delay distribution.
For the two hundred numbered delay scenarios (No.1 .. No.200) selectable in OpenTrack, the
application computes a random number from the selected distribution function to serve as the
individual delay for each individual train at each station.
The user does not know the random numbers used to generate each scenario, but does know
that the scenarios are reproduce able; in other words knows any calculation with the same
input configuration (Infrastructure, rolling stock, timetable) and same scenario (No.1 ..
No.200) will yield the same delay values and simulation results (i.e. the process is pseudo ran-
dom).

8.4 Train Graph (Train Diagram)

OpenTrack offers evaluations of train journeys in the form of train graph (train diagram). The
route over which a train graph is drawn (corridor) must be defined before the simulation or the
simulation must save all timetable data so that the routes to be evaluated can also be selected
following the simulation run. Figure 100 illustrates an example of a graphical timetable from
OpenTrack.
Figure 100: OpenTrack Train Graph
8.4.1 Corridor Level Simulation

Corridor means an orderly succession of station vertices running distance-proportionally
along an axis of the train graph. Using the Corridor Browser illustrated in Figure 101, corri-
dors for evaluation with a train graph can either be extracted from the active layout data or
from the complete data of a simulation run.

Figure 101: Corridor Browser
Source: Origin of the corridor layout (open layout files).

Dist. min. Minimum distance between station vertices of the corridor starting sta-
tion and the currently selected station (in metres).
Dist. max. Maximum distance between station vertices of corridor starting station
and the currently selected station (in metres).
Browser Section: Stations included in the corridor.
Search field: Search for a station name for the starting station of the corridor.
[New] Creation of the actual corridor selected in the browser.
[Update] Actualization of the layout being the basis of the corridor browser.
[Cancel] Drops the actual corridor selection and closes the window.
Defining a Corridor
• Press the “New” button in the inspector.
• Corridor Browser is displayed on screen.
• Select data source for the corridor (layout, complete simulation file).
• Select the stations to be included in the new corridor using the Browser.
• Examine minimum and maximum distances between stations. A large deviation between
minimum and maximum values suggests an error in the dimensioning of the track sections
(edge length).
• Mouse click on the NEW button to save the new corridor definition.
• Assign a file name to the corridor (.otsimcor file is generated).
• Empty distance/time diagram along the selected corridor appears on the screen.

Train Diagram Inspector

OpenTrack allows the user to create and manage train graphs for corridors and data for com-
plete simulations using the Train Diagram Inspector. The Train Diagram Inspector is illustra-
ted in Figure 102 and is outlined below. The Train Diagram Inspector can be displayed using
the command (Tools  Train Diagram).
Figure 102: Train Diagram Inspector
Document: PopUp menu for the opened corridor files.
Corridor: Corridor stations displayed on diagram.

Title: Title for train diagram (will be printed on diagram).
Comment: Comment that is faded in behind the title.
Areas: Colored markings (see more below).
Train Categories: Displayed train categories.
Time Slot: Selected time domain.
Options - Check the appropriate box to display indicated data.
Actual Timetable: Show actual schedule times (if available).

Planned Timetable: Show planned schedule times (if available).

Course ID: Show the course numbers.

Course Description: Show course description.
Full Stationname: Show full station names.
Schematic Function: Draw distance-time data schematically.
Kilometration: Display of distance in corridor (choice of units).
Single Track Sections: Highlight single track sections in color.
Route Occupation: Display of blocking time stairways (choice of directions).
Legend: Display legend.
Conflicts: Show conflicts.
Flip Axes: Rotate coordinate system.
Overwrite Data: Overwrite data after each simulation run (corridors extracted
from simulation data files cannot be overwritten).
Plot Online: Draw the distance/time plots while the simulation is running
(reduces the simulation speed).
Course ID: Shows train number of the selected train in the diagram.
[New] Opens the corridor browser to create a new corridor.

[Update] Rebuilds the corridor based on the current corridor (important:
selecting Update will cause the last simulation results to be
deleted).
The planned and actual (simulated) arrival, departure and transit times can be displayed
(optionally in the format MM or MM:SS). The transit times are displayed in brackets, i.e., (31)
for a train that passes through at minute 31.
It is possible to use the keyboard arrow keys (right arrow, left arrow, up arrow and down
arrow) in an active train diagram document to shift the time segment (Time Slot) by half the
visible range. Similarly the mouse scroll wheel can be used to shift the displayed time seg-
ment.
Areas
Another feature in the train diagram are the “areas”. An area is a colored marking in the train
diagram. Areas can be freely defined by the user in both the time and distance dimensions.
These areas can then be provided with an (optional) fill colour and/or (optional) hatch colour.
A train diagram can contain any number of areas. Areas can be shown or hidden by checking
or un-checking the activation hook in the first column.
If no time is defined for an area (HH:MM:SS), then the area graphics are shown for the entire
period covered by the train diagram.
Mouse Actions
The following actions can be made with the mouse in the train diagram:
Mouse click within the time-distance display: if the time-distance line of a course is clicked,
the following windows, if they are open, are updated:

• Courses: The selected course is displayed

• Timetable: The timetable entry of the station closest to the mouse click is selected
• Itineraries: The main itinerary of the selected course is selected. If the checkbox Show Itin-
erary is activated in the itinerary panel, the itinerary on the infrastructure is highlighted
(priority 1 in red, other priorities in orange).
Mouse-click outside of the time-distance display: the corridor station whose position is closest
to the position of the mouse click is selected in the Train Diagram Inspector.
The train diagram’s context menu (right mouse button) contains a Show Station function (e.g.,
Show Station STA_X) which can be used to display the station closest to the mouse click in the
corresponding infrastructure document.
Several additional context menu functions are displayed depending on the location of the
mouse click:
• If itineraries exist at the nearest station to the mouse click, this allows users to create a new
course using the function New Course from <aStation> at <aTime> and also allows users
to access the submenu to select an itinerary. This makes it easy to create a new course with
the starting point <aStation> and the starting time <aTime>.
• If the mouse position is on a course contained in the train diagram, the context menu
enables the functions Use or Unuse Course (Use / Unuse in the course database), Start
Course (start a single train simulation) and Delete Course (delete the course in the course
and schedule database).
8.5 Working with Timetable Data on the Train Graph

Timetable data can be edited directly in the train graph by displaying the scheduled timetable
(check “Show Planned Timetable” in Train Diagram Inspector - Options Box).
The first step in the process is to select a course for editing; to select a course click on it in the
train diagram. Once a course run is selected, then the course’s defined departure times, arrival
times, stop times, and travel times are displayed on the train graph in the form of small squares
as shown in Figure 103.

Figure 103: Display of Timetable Data
In each case a square representing a timepoint can be shifted on the time axis in order to
change the appropriate timetable entry in the timetable data base. (You can display the Timeta-
ble Database with the command: Tools  Timetable). Shifting the rhombuses faded in bet-
ween the station-referred times causes a shift of all defined timetable times of the selected
course at the appropriate time (parallel shift). The following table shows the meaning of the
represented symbols.
Symbol Meaning Represented Timepoint

Red Square Stop Arrival and Departure Times
White Square Stop Departure Time minus Stop Time
Green Square Pass Through Time train passes through station
Blue Rhombus Train Running -

The following operations can be made in the train graph:
Convert a Stop to a Pass [SHIFT] + Mouse-click

Through
Convert a Pass Through to a [SHIFT] + Mouse-click
Stop
Insert a Station Stop [INSERT] + Mouse-click -or-
[i] + Mouse-click
Remove a Station Stop [DELETE] + Mouse-click -or-
[BACKSPACE] + Mouse-click -or-
[d] + Mouse-click
Move Together (edit) all Earlier [-] + Mouse-movement -or-
Entries for Selected Train [HOME] + Mouse-movement -or-
[PAGE UP] + Mouse-movement
Move Together (edit) all Later [+] + Mouse-movement -or-
Entries for the Selected Train. [END] + Mouse-movement -or-
[PAGE DOWN] + Mouse-movement
The functions affect the course selected in the picture timetable and, when the selection “Keep
Internal References” is checked in the Timetable Management Window (Figure 62), on the
courses of the appropriate interval train group.
8.6 Monitoring the Simulation
8.6.1 Animation
OpenTrack allows the user to visualize the train positions and signal positions during the
simulation. Trains are displayed by illuminating edges occupied by the train in red, and edges
reserved for the train in green (ahead and behind). During the reservation process a route is
represented in dark-green. Figure 104 compares how OpenTrack displays train position with
reality.
Reality / Realität
Train / Zug IC 8002
Computer Visualization / Darstellung auf dem Computer
IC 8002
Figure 104: Display of Train Position in OpenTrack

For main signals OpenTrack displays red for closed signals, and green if they show a proceed
aspect. Distant signals are shown as yellow if the appertaining main signal is closed and green
if the appertaining signal shows a proceed aspect. Figure 105 illustrates possible OpenTrack
signal states.
Figure 105: Possible Signal States
In addition to the displaying the animation of infrastructure operations, OpenTrack can plot
train diagrams and other function plots while the simulation is proceeding. For more informa-
tion on train diagrams please see Chapter 8.4: Train Graph (Train Diagram) on page 142 and
Chapter 3.9.2: Plot Objects (Plot) on page 41.
8.6.2 Messages During the Simulation

The OpenTrack program generates the following three types of messages during the simula-
tion process:
Normal: Normal messages of the simulation on working steps performed (train started,
train arrived at station XY, ...), which do not impact running the simulation.
Color: green.
Warning: Messages on non-optimal simulation behaviour (train must brake due to a clo-
sed signal, train must stop at a signal, etc.), which do not impact running the
simulation. Color: yellow.
Error: The simulation has discovered an error (train does not exist, file is not open,
etc.), for which reason the simulation cannot be continued. Color: red.
OpenTrack allows the user to view simulation messages while the simulation is running. Mes-
sages are displayed in the Messages Window illustrated in Figure 106.
Options Show Messages ... can be used to display the message window during the simulation
process.

Figure 106: Message Window
The Message Window includes the following information:
Listing of all messages.
Messages selection: Selection menu: User can choose to display: all messages, only warning
and error messages, or only error messages.
Filter: Filter attribute for station or course related messages.
[Show Object] Shows location causing message on worksheet for selected message.
[Clear] Deletes all messages.
8.7 Evaluations
OpenTrack saves various data during the simulation (for example train tachographs, actual
timetables, ...). These data can be evaluated after the simulation is completed. Data are saved
in files (e.g. tachograph) as well as directly imported by the appropriate evaluation modules
during the simulation (e.g. to create train graphs). OpenTrack distinguishes between several
different types of evaluations:
Text or table: The simulation generates certain evaluations in the form of text files,
which can also be used later in text processings or table calculations.
Example:
Actual timetable in tabular form (file OT_<courseID>.tt)
Function: Evaluations in the form of functions can be shown graphically (for

example in OpenTrack plot objects, in general plot tools or via diagram
functions of table calculations). The file lines are built up in the form of
x-value, y1-value, tabulator, y2-value, ...

Examples:
Distance/time diagram (file OT_<courseID>.st1)
Speed/distance diagram (file OT_<courseID>.vs)
Special evaluation: The special OpenTrack evaluations are not readable as text for the user.
The recorded data can only be evaluated via OpenTrack itself.
Example:
Corridor of the train graph (file <corridor name>.otsimcor)
Particular evaluations can only be made if the corresponding selection has been made in Out-
put Definition of the simulation tool before the simulation is run. Please see Chapter 8.4 for
more information on how evaluations are produced in the form of train graphs.
8.7.1 Insert Functions in Plot Objects

A plot object is an xy-coordinate system, in which any number of functions can be shown.
Figure 107 illustrates a typical plot object. In addition to the plot values, legends (for example
station names, signals, etc.) can also be imported into a plot object via drag & drop (see also
Chapter 3.9.2). Using these techniques various different plots and graphical elements can be
placed on a worksheet for display and presentation as shown in Figure 109.
[km/h]
150
140
130
120
110
100
90
80
70
60
50
40
30
20
10
0
0 10 20 30 40 50 [km]
Ypslikon
Pewald
Wedorf
Iggswil
Oberg
Figure 107: Example Plot Object: Speed/Distance Plot with Signal and Station Legends
[km/h]
140
130
120
110
100
90
80
70
60
50
40
30
20
10
0
3 4 5 6 7 [km]
Figure 108: Example of a braking value curve (Braking Actions)

Figure 109: Evaluation Data and Plots in OpenTrack Document
8.7.2 OpenTrack Evaluation Files

Most OpenTrack evaluations are saved in the form of ASCII text files and can be edited or
processed by means of text editors or spread-sheet programs such as MS-Excel (see Figure
110).
Figure 110: Evaluation Data in Excel Spreadsheet
OpenTrack automatically prepares the following data files (in the Output-Path, see: Info 
Preferences):
Course-Specific Evaluation Data Files
OT_<courseID>.as Acceleration in the distance travelled function

OT_<courseID>.at Acceleration in the time function
OT_<courseID>.vs Speed in the distance travelled function
OT_<courseID>.vs2 Speed in the covered distance function

OT_<courseID>.vsb All braking curves used on the route

OT_<courseID>.ms Route speed in the distance function
OT_<courseID>.vt Speed in the time function
OT_<courseID>.st1 Route covered in the time function
OT_<courseID>.st2 Route still to be covered in the time function
OT_<courseID>.ts1 Route covered in the time function (interchanged axes)
OT_<courseID>.ts2 Route still to be covered in the time function (interchanged
axes)
OT_<courseID>.step1 Blocking period step: Distance of the reserved section in the
time function
OT_<courseID>.step2 Blocking period step: Distance of the released section in the
time function
OT_<courseID>.Fs Tractive effort in the distance covered function
OT_<courseID>.Ps Performance (Power) in the distance covered function
OT_<courseID>.Pis Performance (Power) used in distance covered
OT_<courseID>Wis Energy used in distance covered
OT_<courseID>.Rs Resistance in the distance covered function
OT_<courseID>.tsvP Table with the values for the time, distance, speed, traction
power, the resistance and the mechanical power
OT_<courseID>.tt Actual timetable (incl. set/actual comparison) in text format
OT_<courseID>.tunnel Tunnels along the route
OT_<courseID>.radius Track segment curve radius
OT_<courseID>.level Height above sea level of the route
OT_<courseID>.gradient Track segment gradient
OT_<courseID>.sigpos Signal positions and type (can be imported into the plot object
as legend)
OT_<courseID>.statpos Station positions (can be imported into the plot object as
legend)
OT_<courseID>.kmpos Kilometer positioning (imported as a legend in Plot-Object)
Evaluation Data for All Courses
OT_Physic.tsvP Table with the values for the time, distance, speed, traction
power, the resistance and the mechanical power
OT_<PowerSupplyName>.Pt Power consumption over time for each power supply ele-
ment. Power is measured as the sum of power consumed by
all trains traveling through the power district during the time
step (period).
OT_Occ_<OccName>.occ Occupation of edges
OT_Ins_<DocName>_<ID>.ins Measuring device output values
OT_Delay.delall All delays
OT_Delay.delallarr All arrival delays
OT_Delay.delalldep All departure delays
OT_Delay.delavg Average delay per course
OT_Delay.delend Delay at the end station per course
OT_Delay.delmax Maximum delay per course
OT_Delay.delbegin Initial delay

OT_Delay.dellaststop Delay at last station stop

OT_Delay.delact Actual delay (animated during the simulation run)
OT_Messages.txt Simulation messages
OT_CourseStatistics.txt Course statistics
OT_CategoryStatistics.txt Train category statistics
OT_StationStatistics.txt Station statistics
OT_TimetableStatistics.txt Timetable statistics
OT_Protocol.<Date/Time>.txt Simulation notes
Evaluation Data for Train Diagrams
<corridor name>.otsimcor Corridor description for a train graph / graphical timetable

(train diagram). (Typically not stored in the Output-Path
but in a project folder).
Evaluation Data for Multiple Simulation Runs
OT_Timetable.txt Schedule statistics for multiple simulation runs displayed in

table format.
OT_Timetable.xml Schedule statistics for multiple simulation runs displayed in
railML format.
Train Category Statistics:
An evaluation function calculates the delay statistics per train category (Train Categories).
The delays (number and percent) with respect to the defined values for each category (Cate-
gory Delay Settings) for small (Del. S), medium (Del. M) and large delays (Del. L) are listed
for each train category and presented in the file “OT_CategoryStatistics.txt”. The evaluation
table contains information for all intervals of interest (e.g., all delays smaller than Del. M, all
delays greater than or equal to Del. S and less than Del. L, etc.).
The last measured arrival and/or departure delay (Delay last stop) at a station is used to calcu-
late these statistics.
8.8 Headway Calculator

The Headway Calculator (Tools Headway Calculator) uses a set of input parameters to cal-
culate the minimal headways between trains. The two trains can use a fixed block or moving
block signalling, furthermore the two trains can also have different itineraries and/or stopping
patterns. The headway will be calculated for the common portion of the two itineraries.
The minimum headway is calculated so that the second train has exactly no conflicts (based on
a userdefined set of conflict types). When using the headway calculator in Test mode a train
headway of one second below the minimum headway would be considered a conflict.

Figure 111: Headway Calculator
First Train: Description/Definition of the preceeding train.

Second Train: Description/Definition of the following train.
Course ID: ID of the course (from Course Panel Tools Courses)

[Create Train Diagram] Creates a train diagram for the course in the corresponding time
slot (Time Slot) 12:00 - 14:00 (time slot for the train headway
calculation).
Performance: The train performance to be used in the train headway calcula-
tion.
Res./Res.: Method used for reservation and resolution of routes (Discrete,
Moving, ...).
Train: Train type which is being used on this course (Tools Trains).
Start Time Offset [s]: Offset for the starting time of the second train. In the case where
the two trains use different itineraries it is possible to define a
time offset (positive or negative) for the second train when
using the Test Headway calculator mode. In this case the second
train enters the common itinerary by this amount of time after
the first train.
Mode: Calculation type (Test First Train, Test Second Train, Test Head-
way, Search Headway), see mode definitions below.
Headway [s]: The headway to be tested in the calculation mode Test Headway.
Headway from [s] to [s]: Interval within which to search for the train headway in the cal-

culation mode Search Headway.
Conflicts to avoid: List of conflicts that should be used as termination criterion for
the headway calculation process (i.e., the second train must not
have any of the selected conflicts). The conflicts that can be set
are a subset of those in the messages panel (Tools Messages)
and in the train diagram (Tools Train Diagram).
Status: Status of the calculation.

Result: Results of the calculation (e.g., the calculated headway).
Comment: Comments about the calculation results (e.g., number of con-
flicts, total [overall] and selected [from the list of selected con-
flicts]).
[Swap Trains] Switch the order of the first and second trains.
[Stop] Stop a running headway calculation process.
[Start] Start a headway calculation process.
Figure 112 illustrates a train diagram for two trains traveling on the same track section. The
minimum headway is 207 seconds (the parameters used are from the panel illustrated in
Figure 111 above). The critical block section can then be shown by running a simulation in the
Test Headway (206 s, 1 second below the minimum headway) mode using the command
(Show Conflicts in train diagram).
UST-ZMUS: Headway Calculation Uster - Zurich
12.00 .10 .20 .30

UST 0.0
_H
_H
DW
DW
_1
_2
NAEN 3.2
SCWE 5.8
DUE 8.8
STET 11.3
ZSTH 16.7
ZMUS 18.4
12.00 .10 .20 .30
Figure 112: Result of a minimum headway calculation

The four headway calculator function modes:
• Test First Train: The first train is simulated and the conflicts are reported (total, selected
conflict types).
• Test Second Train: The second train is simulated and the conflicts are reported (total,
selected conflict types).
• Test Headway: A user-defined headway is tested and the conflicts for the second train are
reported (total, selected conflict types).
• Search Headway: The minimum headway between the first and second trains is calculated
and reported (numerical calculation is performed using simulation and binary search).
Recommended process for calculating minimum headway:
• Select the two courses for which you want to calculate the headway (First Train: preceed-
ing train, Second Train: following train). The courses must already be defined in the
course panel (Tools Courses) although they do not need to be active. The two courses
must have appropriate timetable entries (Tools  Timetable). The minimum station stop
times (Dwell) for use in the headway calculation will be taken from this data, but other
data (arrival time, departure time, connections, etc.) is not taken. The calculation could be
done for two trains with the same course (in which case the first and second train would
have the same course ID).
• Open all the infrastructure documents that are used by the two courses (Document 
Open).
• It is recommended that you create a train diagram for the common track segment upon
which the two trains travel ( Create Train Diagram).
• Select the train performance to be used for the two courses. The performance values from
the course database will not be used.
• Select the conflicts that are to be considered as termination criterion for finding the min
mum headway (Conflicts to avoid). Both courses should have no such conflicts when they
are traveling alone (this can be checked using the test modes Test First Train and Test Sec-
ond Train). For trains using moving block signaling any braking due to insufficient brak-
ing distance before the preceeding train is considered a conflict (i.e., when the preceeding
train is located within required braking distance). This type of conflict is neither displayed
on the train diagram nor must they be specifically selected in the list of observed conflicts
(Conflicts to avoid). However, this type of conflict is included in the count of conflicts
(total, selected) and they are considered conflicts of the type selected.
• Define a range within which the program should search for the train headway (Headway
from [s] ... to [s]). In the absence of any particular indications, it is recommended to search
in the range from 1 – 3600 seconds (1-second to 60-minutes).
• Select the calculation mode: Search Headway and start the search (press button: Start).
The calculated train headway will be displayed in the results as well as any comments on
the simulation in the fields Status and Comment.
• In cases where both courses have different itineraries (for example the common segment
begins only after a given distance) the results will also include a time offset (Start time off-
set 2nd train, which can be positive or negative). This offset is the difference between the
starting time of the second train and the first train so that both trains reach the common
track section in the same time window.

• The indications "_HDW_1" und "_HDW_2" are used as course ID's. All the evaluations
will be produced for these courses (Tools  Simulation, Output) and they can be analyzed
later (in the Plot-Add-Panel the courses appear under the appropriate entries at the end of
the course list under Headway 1 and Headway 2).
8.9 Dispatching Rules

Call Windows:
OpenTrack.exe -dispatchingrules
OpenTrack.exe -dispatchingrules -dispatchingrulesfile="<aRulesFileName>"
OpenTrack.exe -dispatchingrules -routeidtype="<aRouteIDType>"
-dispatchingrulesfile="<aRulesFileName>"
Call Mac: In the Terminal-Application (Terminal.app):

exec /Applications/OpenTrack.app/Contents/MacOS/OpenTrack -dispatchingrules
-routeidtype="<aRouteIDType>"
Functions:
Functions  Dispatching Rules  Import Dispatching Rules (OTD-Format)
Functions  Dispatching Rules  Import Recent Dispatching Rules (OTD-Format)
Functions  Dispatching Rules  Produce Dispatching Rules File (OTD-Format)
Functions  Dispatching Rules  Delete all Dispatching Rules
OpenTrack now supports the definition of exclusion rules in the dispatching process using so
called sets or rules (Route Rule Set). These are rules that will be checked before routes can be
reserved.
If any of the rules (Route Exclusion Rules) in the Route Rule Set are true, the corresponding
route segment cannot be reserved. These rules within the set can be linked with the “OR” ope-
rator (in which case the rule is true if either of the conditions are met).
A rule can consist of one or more conditions (Route Exclusion Condition). The conditions wit-
hin a rule are linked with the “AND” operator (in which case the rule is true if all conditions
are true).
The rules are defined in an XML file. A suitable structure can be exported from Open Track
using the command (Functions  Dispatching Rules  Produce Dispatching Rules File
(OTDFormat)). This file can then be supplemented with rules that are valid for the current
project.
It is recommended that users open all the project’s infrastructure files (*.opentrack-files)
before using the function: Produce Dispatching Rules File (OTD format), since opening the
files will cause all defined route segments to be displayed on the route segment list (<routes>)

with their RouteID. This information can then be used to facilitate the process of defining
rules (e.g., using copy/paste).
The rules are activated when OpenTrack is started with the parameter: “-dispachtingrules”.
The dispatching rules themselves are provided either by specifying the dispatching rules
filename at the start of the process using the command: (dispachtingrulesfile="<aRulesFile>")
or by importing a dispatching rules file later (Functions  Dispatching Rules  Import
Dispatching Rules (OTD-Format)).
The menu item Functions  Dispatching Rules  Import Recent Dispatching Rules (OTD-
Format) displays the dispatching rule file that was last used for import. The file name is shown
in brackets.
The rules can also be deactivated. The menu item (Functions  Dispatching Rules  Delete
all Dispatching Rules) deletes all the dispatching rules.
An example control file is presented below (example of a file with RouteID from the docu-
ment name, ID of the starting vertex and routes):
<otd>
<routeRuleSets>
<routeRuleSet id="Set0">
<routeExclusionRule>
<routeExclusionCondition
routeID="topoEast-89-R:STA_B_HSE-STA_B_01"/>
</routeExclusionRule>
</routeRuleSet>
routeID="topoEast-101-R:STA_C_HSE-STA_C_01"
minimalLength="400"/>
routeID="topoEast-101-R:STA_C_HSE-STA_C_02"
minimalLength="400"/>
</routeRuleSet>

routeID="topoEast-78-R:STA_F_HSW-STA_F_01"
routeReservationState="free"/>
routeID="topoEast-87-R:STA_F_HSE-STA_F_03"
routeReservationState="reserved"/>
</routeRuleSet>
</routeRuleSets>
<routes>
<route id="topoEast-14-R:STA_A_02-STA_B_HSW"
routeRuleSetID="Set0"/>
<route id="topoEast-56-R:STA_B_02-STA_C_HSW"
<route id="topoEast-62-R:STA_B_01-STA_C_HSW"
<route id="topoEast-55-R:STA_D_01-STA_F_HSW"
</routes>
</otd>
The file begins and ends with the tags <otd> and </otd>.
The first part of the file (starting with the tag <routeRuleSets> and ending with the tag </rou-
teRuleSets>) is where rule sets (Route Rule Set) are defined. Each rule set can contain any
number of exclusion rules (Route Exclusion Rule). Each exclusion rule can contain many
exclusion conditions (Route Exclusion Condition).
The second part of the file (starting with the tag <routes> and ending with the tag </routes> is
where the RouteRuleSets are assigned to specific routes. Route segments where there are no
defined RouteRuleSets are not listed in this section.
The definitions use the following parameters:
<routeRuleSet>
id: Freely definable, unique name for the rule set.
maximalNumberOfTrains:(optional) The maximum number of trains that are allowed to

use a route segment (see example 1 below).

<routeExclusionCondition>
routeID: Unique name for the route segment (RouteID) for the compari-
son. It is formed either from the document name, the ID of the
starting vertex and Route Name (default) or from the Route
Name alone (in which case the user must ensure that the Route
Name is unique and occurs only once in the project).
If OpenTrack is called without routeidtype or with the parame-

ter routeidtype = “topoidroutename”, then the RouteID will be
developed from the document name, the starting vertex ID and
the Route Name. If the program is called with the routeidtype =
“routename” then the Route Name will be used.
minimalLength: (optional) Minimum length of the two trains (being compared)

in meters for which the rule is observed.
routeReservationState: (optional) Status of the route that is being checked. If the rou-
teReservationState = “reserved” then the program checks to see
if the route is reserved. If the routeReservationState = “free”
then the program checks to see if the route is free. This allows
users to construct conditions that are true in either case (i.e.,
when route is free or reserved). The default condition is rou-
teReservationState = “reserved”.
stopCode: (optional) Values “unplannedStop” (unplanned stop) and

“extendedDwell” (extended dwell time) for exclusion conditi-
ons (see examples 2 to 4 below).
extendedDwellTime: (optional) Time in seconds for exclusion conditions of the type

“extended dwell time”. This attribute shows how many seconds
the dwell time can be extended so that exclusion can apply (see
examples 3 and 4 below).
reactionTime: (optional) Response time in seconds for the exclusion conditi-

ons of the type "extended stop time" and "unscheduled stop".
This attribute indicates how many seconds after discontinuation
of the exclusion condition before a waiting train can begin dri-
ving (see Example 6 below).
reactionTimeDistribution:(optional) Delay distribution of the reaction time for the exclu-

sion conditions of the type "extended stop time" and "unschedu-
led stop". The attribute determines which distribution function
is used to determine the reaction time (see Example 5 below).
If both a reaction time and a reaction time distribution are defi-

ned, then the reaction time is used.
<route>
id: RouteID.
routeRuleSetID: ID of the rule set to be used.
Rule Application Examples:
Example 1: This exclusion rule describes how many trains are allowed to be in the specified
route segments. In these examples, two trains are allowed to stay within the three listed routes.
<routeExclusionRule maximalNumberOfTrains = "2">

Examples 2 to 4: These exclusion rules can check whether a train has an unplanned stop or an
extended station dwell time on a defined route segment. The attribute “stopCode” for the tag
<routeExclusionCondition> has the possible values “unplannedStop” and “extendedDwell”.
The “extendedDwellTime” attribute specifies by how many seconds the planned dwell time
must be exceeded so that the exclusion applies. The default value (0 seconds) is used if no
value is entered for the attribute "extendedDwellTime".
Example 2: Detect an unplanned stop on the defined route (resulting an exclusion)
routeID="topoEast-89-R:STA_B_HSE-STA_B_01"
stopCode="unplannedStop"/>
Example 3: Detect an extended station dwell time (for a train on the defined route)
stopCode="extendedDwell"/>

Example 4: Detect extended station dwell times of twenty or more seconds (for train on the
defined route).
stopCode="extendedDwell" extendedDwellTime="20.0"/>
Example 5: Rule states that if an unplanned stop is detected on the defined route segment, the
distribution function D1 should be used to determine the reaction time. The distribution func-
tion names can be set and found in Tools  Distributions.
stopCode="unplannedStop"
reactionTimeDistribution="D1"/>
Example 6: Rule states that if a train on the defined route segment remains stopped 20 seconds
(or more) than the planned dwell time then the reaction time will be 9 seconds.
stopCode="extendedDwell" extendedDwellTime="20.0"
reactionTime="9.0"/>


Further Tools and Settings 165
9. Further Tools and Settings
9.1 File Commands: Menu Document
Create a New Worksheet Document

Document New ... can be used to create a new (empty) worksheet document.
The file name of this document is Untitled until the file is saved. It is advantageous to give the
document a file name immediately because certain data exchange operations are only possible
between documents that have valid file names.
Open Existing Document

Document Open ... can be used to open an existing document (select filename from list).
OpenTrack documents have the extension .opentrack. It is important never to open two or
more files with the same file name simultaneously (not even if they are saved in different
directories) because OpenTrack insists upon an unmistakable layout name.
Open Recently Used Documents

When the user quits OpenTrack, the program makes a note of all open documents and allows
the user to re-open these documents the next time the program is started.
Document Open recent Documents... can be used to open documents in use at last quit.
Further Functions to open Documents

These functions are summarized under Document Open Special...:
... Open (without Images) : to open a document without the included images
... Open Property List (plist): to open a Property List (plist)
... Open all Documents in Directory: to open all documents in a folder
Save Document
Document Save... is used to save a document.
Save your work at frequent intervals to minimize losses in case of problems such as power fai-
lures etc.
Save Document Under Another Name

Document  Save As... is used to save the document under a different name (Figure 113).
Save Document in Another Format

OpenTrack’s standard document format has the file extension ( .opentrack). However, the pro-

166 Further Tools and Settings
gram allows users to save documents in postscript format (.eps) or in the bit-mapped format
(.tiff). If a document is saved under a picture format, the track layout is not saved, but “only” a
picture of it, which can be used in other programs (for example for project documentation).
Document  Save To... is used to save a document in a different file format.
The format selection is made by clicking the appropriate button on the Save To Window.
Figure 114 illustrates the Save To Window.
Figure 113: Save Window Figure 114: Save To Window
Chapter : PDF-Printer (save document as PDF file) on page 168 describes the process to save
a document as PDF file.
Save All Documents

Document  Save All Documents … can be used to save all open infrastructure (*.opentrack),
the schedule (*.otsimcor) and the locomotive depot (*.depot) files.
Further Functions to save Documents

The functions are summarized under Document Save Special...:
...Save as Property List (plist): to save the document as a Property List (plist)
...Save all Documents: to save all open documents
Rename Document
Document  Rename … can be used to rename files. In order to make certain that the connec-
tors to associated documents are properly recognized all connecting infrastructure files need to
be open when the document is renamed.
Refresh Document
Document  Refresh can be used to redraw a document.

Creating and Using Document Sets

Document  Document Sets
A Document Set is a collection of documents that can be identified using a single name. A
number of open documents can be given a common name using the command (Save Set As),
so that the same group of documents can be opened at a later time (similar to the function
Open Recent Documents which opens the last several documents used). The name of an exi-
sting set can be deleted using the command (Delete Set).
Revert to the Saved Version of the Document

In some cases while editing a document the user may want to return to the last saved version
of the document, for example if the user makes a mistake.
Document  Revert To Saved ... is used to revert to the last saved version.
Note that when this command is used, the edited version is lost and the last saved version
becomes the current document.
Close Document
OpenTrack documents can be closed in the following two ways:
• Document  Close ... from the menu, or

• Clicking on the Close Button in the header of the document window.
In either case, if a document has been modified since it was last saved, OpenTrack asks
whether the document is to be saved before the closing.

9.2 Print
Print... activates the print window (Figure 115) which the user can use to control printing of
the selected worksheet.
Figure 115: Print Window
PDF-Printer (save document as PDF file)

The installation of a PDF printer (product CutePDF) is recommend. CutePDF is available on
the OpenTrack CD (folder Shareware). It can also be downloaded from the internet:
http://www.cutepdf.com/Products/CutePDF/writer.asp
After the installation, CutePDF appears as a (postscript compatible) printer in OpenTrack. To

create a file:
• Open document (infrastructure document or train diagram)

• Check settings in Format  Document Setup
• Use menu item Print
• Select CutePDF as printer
• PDF file will be created
9.3 Menu Info
Infopanel
Info  Info Panel brings the information window of OpenTrack in the foreground (Figure
116). The OpenTrack version number among other data is shown in the Info Panel.

Figure 116: Info Panel
Registration
Info  Registration activates the Registration Window (Figure 117). The Registration
Window shows the program status (licensed, not licensed) of the OpenTrack version currently
being used. The license agreements require that OpenTrack software be licensed in order to be
used. Unlicenced versions have a very limited range of functions.
Figure 117: Registration Window
In order to receive a license key valid for the computer being used, the text represented in the
Registration Window must be sent to the email address info@opentrack.ch.
OpenTrack can also be de-registered on a computer, e.g. when transferring a license to another
computer. In this case the deregistration code must be sent to the above-mentioned address.
Release Notes
Info  Release Notes causes the release notes for the current OpenTrack version to be dis-
played in a window.

Manual
Info  Manual causes the manual for the current OpenTrack version to be displayed in a
window.
9.4 Menu Edit
Undo
OpenTrack includes an Undo (Edit  Undo) feature. This affects actions on the Open Track
workspace (user actions made with the mouse, move, copy, delete, setting elements and attri-
bute changes in the inspector), but not to actions made in the databases (timetable, courses,
stations, etc.) and the itinerary definitions (routes, paths, itineraries).
Note that the Undo function is quite powerful. For example, you can use it to return a set of
changes made in the Inspector to their original state.
Select All
Edit  Select All causes all objects on the selected worksheet to be selected.
Subselect Edges
Edit  Subselect Edges selects the edges from the selected elements of the active worksheet
and deselects all other elements.
Subselect Vertices
Edit  Subselect Vertices selects the vertices from the selected elements of the active works-
heet and deselects all other elements.
Subselect Switches
Edit  Subselect Switches selects the switches from the selected elements of the active works-
Subselect Signals (Main Signals, Distant Signals, Shunting Signals, Balises)

Edit  Subselect Signals selects the signals (all types) from the selected elements of the active
worksheet and deselects all the other elements.
Subselect Routes
Edit  Subselect Routes displays a table of all routes, which begin at the selected elements in
the active worksheet. The route's most important attributes may be edited directly in this table.
The list can also be sorted by various criteria using the (sort by) function.

Subselect Shuntings/Overlaps
The function Edit  Subselect Shuntings/Overlaps presents a table of all shuntings and over-
laps that begin at the selected elements of the active worksheet. The attributes speed (Speed
[km/h]) and release time (Release Time [s]) can be edited directly in the table.
The list can also be sorted by various criteria using the (sort by) function.
Subselect Stations
Edit  Subselect Stations selects the stations from the selected elements of the active works-
Subselect Instruments
Edit  Subselect Instruments selects the measurement instruments from the selected elements of
the active worksheet and deselects all other elements.
Subselect Graphics
Edit  Subselect Graphics selects all graphic elements (rectangle, circle, line) from a set of
selected elements and deselects all other elements.
Subselect Labels, Subselect temp. Labels

Edit  Subselect Labels selects the labels from the selected elements of the active worksheet
Edit  Subselect temp. Labels selects the temporary labels from the selected elements of the
active worksheet and deselects all other elements.
Subselect Images
Edit  Subselect Images selects the images from the selected elements of the active worksheet
Selection of Objects with same Parameters

The function Select Edges with same … allows you to select other edges that have the same
value (user entered parameter), for example, the same gradient, radius or speed.
The Select Edges / Vertices with same… allows you to select not only the corresponding edges,
but also the associated vertices. This feature is very handy if you want to move elements that
belong together around on the worksheet.
Select Edges with same Line Name, Track Name, Line Name and Track Name
Edit  Select Edges with same Line Name and/or Track Name selects all edges in a document,
that have the same attribute in the Line Name and/or Track Name as the selected edge.

Review Kilometre Data

Edit  Select Edges with Kilometre Point Conflict allows users to select all edges where the
edge length does not equal the corresponding vertex-to-vertex Kilometre-post difference.
Place Image
Edit  Place Image allows the user to select a diagram file to be inserted in the document.
The user can also simply Drag&Drop an image file into the document.
Remove Images
Edit  Remove Images will remove all the images (Images) from the document.
Remove PDF-Images (only in MacOS)

Removes all graphic elements in pdf format (e.g. for the exchange with a Windows version of
OpenTrack).
9.5 Menu Format

The format menu contains some standard commands for font, text and graphics as well some
OpenTrack-specific commands.
Zoom
The zoom feature (Format  Zoom In and Format  Zoom Out) can be used to increase or
decrease the size of the worksheet representation. The zoom factor can also be set at the lower
edge of the document (Zoom-Menu) and using the Magnifying Glass tool in the toolbox.
Document Setup
The document setup feature (Format  Document Setup) cause a window to open that can be
used to set the size of the worksheet area (setting the worksheet size can also be done using the
Page Layout command).
In the Document Setup Window users can specify the width (Width w) and height (Height h)
of the worksheet in points (10 <= w <= 50000; 10 <= h <= 50000). If the Automatic Resize
option is selected, the worksheet will be automatically sized to fit in the open worksheet
window.
The Window Size button changes the worksheet size to the size of the window. The Paper Size
button changes the worksheet size to the paper size defined in Page Layout (Format  Page
Layout). Autoscale scales the worksheet size so as to provide room for all the worksheet ele-
ments.
In the section Printing Pagination, you can now define how OpenTrack distributes the works-
heet onto pages while printing.

• Auto Pagination: OpenTrack breaks-up the worksheet into equally-sized rectangles and
prints it as a series of pages.
• Fit Pagination: OpenTrack scales the worksheet so that it fits on a single page.
• Clip Pagination: OpenTrack breaks-up the worksheet to produce a column or row of
pages.
Worksheet Layout (Page Layout)

Format  Page Layout activates the Page Layout Window (Figure 118). The Page Layout
Window can be used to set the paper format, the margins and the orientation of the worksheet
(Portrait/Landscape).
Figure 118: Page Layout Window
9.6 Menu Tools
Colors
Tools  Colors brings the color window to the foreground.
Open Track Tool Palette

Tools  Palette brings the OpenTrack Tool Palette (Figure 119) to the foreground. The tool
palette can also be activated by pressing the combination of keys Ctrl-0 (Mac: Cmd-0),
whereby the highest tool (pointer) is then selected automatically.

Figure 119: OpenTrack Tool Palette
Finder
Tools  Finder activates the finder tool. Objects can be localized on the worksheet by means
of the finder (input: ID of the object, document; output: type of object, display on the works-
heet).
The extended Finder Tool functionality allow users to search for an Element ID, a Vertex
Name, a Kilometre Point or a Signal Name.
Messages
Tools  Messages opens the reporting window that displays messages generated during the
simulation.
Calculator
Tools  Calculator brings the conversion window in the foreground, with which e.g. day
seconds can be transformed into time strings and vice versa.
9.7 Menu Functions
Group Station Area

Functions  Group  Station Area assigns the selected vertices to a station zone.
Before the function is activated, the user must select exactly one station and at least one vertex
on the worksheet. It is important that station areas include station vertices and the last exit

signal (outer exit) of a station. Each station has to show a station zone (minimum = station ver-
tex). After the assignment of a vertex to a station the vertex display is changed. Membership
of vertices in a station area can also be checked using the Vertex Inspector (Tools  Inspec-
tor).
Ungroup Station Area

Functions  Ungroup  Station Area cancels the station membership of selected vertices.
Group Power Supply Area

Functions  Group  Power Supply Area assigns a section of track (vertices and edges) to a
power supply zone.
Before the function is activated, the user must select exactly one power supply element icon
and at least one edge on the worksheet.
Ungroup Power Supply Area

Functions  Ungroup  Power Supply Area cancels the power supply area membership of
selected vertices and edges.
Group Propulsion Segment Group

This function can only be used for magnetically levitated (Maglev) trains. The function Group
Propulsion Segment Group enables users to group individual propulsion segments into a pro-
pulsion segment group. It is also possible to specify how many propulsion segments can be
active within a group (using the attribute: max. active), and thus set a ceiling on the number of
trains moving within the group.
Propulsion segment groups are created using the Power Supply Inspector. In the System menu,
select Propulsion Segment Group. This causes the designation G to appear on the worksheet at
the selected power-supply object(s).
Now select one propulsion segment group object (marked G) and the propulsion segments you
want to include in the group. To create the group, use Functions  Group  Propulsion Seg-
ment Group.
You can specify how many of the propulsion segments can be active at once. Select the group
object (marked G). Then, using the Inspector - Power Supply, set the maximum number of
active propulsion segments in the max. field in the Propulsion Segment Group box. Setting the
maximum to: 3 of 5 active means, for example, that of the five propulsion segments in the
selected group, only three can be active at once.
Ungroup Propulsion Segment Group

Functions  Ungroup  Propulsion Segment Group removes the selected propulsion seg-
ments from the propulsion segment group.

Search all Routes, Search/Fetch all Routes

Functions  Routes  Search all Routes selects all possible routes from valid route starting
points in the document in question. This function merely automates the manual search for all
routes.
Functions  Search/Fetch all Routes identifies all routes from a valid route starting points in
the open document and transfers the results to the route selection inspector.
Quick Assignment of Signal Aspects to Routes

Functions  Routes  Add all Signal Aspects to Routes allows users to assign all possible
signal aspects for routes where the starting vertex is selected.
Add all Overlaps to Routes

Functions  Routes  Add all Overlaps to Routes attempts to add overlaps to all the routes
starting at the selected vertices. Overlaps will be assigned if the route does not already have an
overlap and there is exactly one possible overlap at the end of the route.
Insulated Joints and Axle Counters for Route Release Groups

Functions  Routes  Place Insulated Joints for Route Release Groups and Functions 
Routes  Place Axle Counters for Route Release Groups can be used to place an insulated
joint or axle counter at the beginning of a route release group for all routes with the selected
start vertex. If no vertices are selected then the function is used on all routes of the document.
Adjusting Route Release Groups based on the Position of Isolation Joints and
Axle Counters
Functions  Routes  Adjust Route Release Groups based on Insulated Joints and Axle
Counters allows users to form new route release groups based on the positions of insulated
joints and axle counters for all the routes starting at the selected vertices. If no vertices are
selected the route release groups will be formed at all routes in the current document.
Delete all Routes

Functions  Routes Delete all Routes deletes all routes, which begin their itineraries at the
selected vertex.
Pathfinding
Functions  Paths  Search all Paths (Exit Signal to Exit Signal) starts a path search for all
selected vertices in the current document, or from all vertices in the document when no ver-
tices are selected.
This function looks for all possible paths that begin at one exit signal and end at the next exit
signal. The identified paths are stored in the list of paths from the corresponding vertex and
given the default name (P:<Station ID Startstation>_<Name Startvertex>_<Signal Name Start-
signal>-<Station ID Endstation>_<Name Endvertex>_ <Signal Name Endsignal>).

Functions  Paths  Search all Paths (for Treno) has the same function, but stores path
names according to the specifications of the Treno analysis tool.
Functions Paths Search all Paths (Exit Signal to Home Signal) and Functions Paths
 Search all Paths (Home Signal to Exit Signal) search all paths (which start at the selected
vertex), that correspond to the selected signal sequence (Exit Signal to Home Signal or Home
Signal to Exit Signal). If no vertex is selected, the function is applied to all vertices of the
document.
Delete all Paths

Functions  Paths  Delete all Paths deletes all paths that begin at the selected vertices in
the current document. If no specific vertices are selected all paths in the document are deleted.
Connect selected Vertices

Functions  Connect selected Vertices connects selected vertices via edges. The selected ver-
tices may not have any adjacent edges. Vertices with vertical justification and vertices with
horizontal justification are interconnected.
Expand or Compress Selected Elements

The functions Functions  Expand Vertices and Functions  Compress Vertices either
expand or compress the selected elements in the workspace. This function can be used if the
elements on the workspace are too close together (e.g., after being imported from railML) to
push the elements apart (Expand) or move them closer together if they are too far apart (Com-
press).
Cut Double Vertex

Functions  Cut Double Vertex splits a double vertex into two double vertices without an
edge between them.
Automatic Kilometre Calculation

Functions  Calculate Kilometre Points calculates the kilometre distance (Kilometre Point)
based on previously defined Kilometre values for other vertices and edge lengths. The existing
kilometre distances are not changed.
It is recommended that users model all kilometre break points before applying the function
(using vertices with two different kilometre values) and that they perform a check using Func-
tions  Markers  Mark Edges with Kilometre Point Conflict after applying the function.
Kilometre Transformation
Functions  Change Kilometre Points can be used to increase or decrease the kilometre
values (Kilometre Point) for all selected vertices by entering a positive (increase) or negative
(decrease) value.

Merge Elements
Functions  Merge Elements merges the selected safety elements.
Reset Elements
Functions  Reset Elements splits safety elements that have been previously merged and sets
them at the default value.
Set Switch Default Positions

Functions  Set Switch Default Position makes the current switch (points) setting the default
switch position.
Create Instruments at Switches

Functions  Create Instruments at Switch Locations places measuring instruments at all
selected switches (if no switches are selected then measuring instruments are placed at all
switches in the document).
Create Instruments at Main Signal Locations

Functions  Create Instruments at Main Signal Locations places measuring instruments at all
selected main signals (if no main signals are selected then measuring instruments are placed at
all main signals in the document).
9.7.1 Functions  Labels

Labels are temporary text fields with layout information and are displayed directly on the cor-
responding elements of the track systems. The labels are generated for all selected elements in
accordance with their function. If no applicable element is selected, the operation is applied to
all valid elements of the active worksheet.
Create all ID Labels

Functions  Labels Create all ID Labels creates a temporary label per edge, vertex, signal
and station, which shows the ID of the object.
Create Vertex ID Labels

Functions  Labels  Create Vertex ID Labels creates a temporary label per vertex, which
shows the ID of the object.

Create Vertex Name Labels

Functions  Labels  Create Vertex Name Labels creates a temporary label per vertex which
shows the vertex name.
The functions:
• Functions Labels  Create Vertex Name Labels (at Signals)

• Functions Labels  Create Vertex Name Labels (at Switches)
limit the create vertex name labels command to vertices at signals or switches only.
Create Vertex Kilometre Point Labels

Functions  Labels  Create Vertex Kilometre Point Labels creates a temporary label per ver-
tex, which shows the kilometre reference point for vertices.
Create Signal Name Labels

Functions  Labels  Create Signal Name Labels generates signal name labels for all
selected vertices where a signal name has been previously defined.
Create Edge ID Labels

Functions  Labels  Create Edge ID Labels creates a temporary label per edge, which
shows the ID of the object.
Create Edge Element Labels

Functions  Labels  Create Edge Element Labels creates a temporary label per edge, which
shows the ID of the safety element.
Create Edge Length Labels

Functions  Labels  Create Edge Length Labels creates a temporary label per edge, which
comprises the edge length in metres.
Create Edge Gradient Labels

Functions  Labels  Create Edge Gradient Labels creates a temporary label per edge, which
comprises the edge gradient in per mill.
Create Edge Radius Labels

Functions  Labels  Create Edge Radius Labels creates a temporary label per edge which
comprises the edge radius.
Create Edge Speed Labels

Functions  Labels  Create Edge Speed Labels creates a temporary label per edge, which
comprises the speed of a train type to be selected.

Create Edge Overlap Labels

Functions  Labels  Create Edge Overlap Labels marks overlaps in the current document or
within of the selected region of the document. Overlaps which are modelled as an edge pro-
perty (attribute: Overlap / Slip) are marked with the text “E: Ov./Sl.” (E: for edge). Edges
which belong to an overlap of a route (attribute: Overlap of a route) are marked with the text
“R: Ov.” (R: for route).
Create Edge Name Labels

Functions  Labels  Create Edge Name Labels creates a temporary label per edge which
comprises the edge name.
Create Edge Line Name Labels, create Edge Track Name Labels
The functions:
• Functions  Labels  Create Edge Line Name Labels

• Functions  Labels  Create Edge Track Name Labels
• Functions  Labels Create Edge Line Name and Track Name Labels
are used to create a label for each edge with the edge attribute “Line Name” and/or “Track
Name”.
Create Station Labels

Functions  Labels  Create Station Labels creates a temporary label at each station display-
ing the full station name.
Functions  Labels  Create Station Labels (colored) creates a label with the full station
name in white letters on a blue background.
Remove temp. Labels

Functions  Labels  Remove temp. Labels deletes all temporary labels from the active
worksheet.
Markers
Markers (Functions  Markers  ...) are indicators that show which objects meet certain
conditions, such as edges whose length is not equal to the difference of the kilometer points
(endpoint minus starting point) (Functions Markers  Mark Vertices with Kilometre Point
Conflict, Functions Markers  Mark Edges with Kilometre Point Conflict,).
Functions  Mark ungrouped Station Vertices highlights station vertices (Station Vertices),
which do not belong to a station area.
Functions  Mark Main Signals without Routes highlights main signals from where no rou-
tes are starting.

Functions  Markers  Mark Vertices with different Kilometre Points can highlight (double)
vertices that have two different kilometre points (Kilometre Point) or vertices that have incor-
rect kilometre points (i.e., the kilometre points are not consistent with those from neighbou-
ring vertices).
Functions Markers  Mark Vertices with Shuntings or Overlaps highlights vertices where
shuntings or overlaps begin.
Functions  Markers  Mark Vertices with Routes having Overlaps highlights the starting
vertices for route segments that have overlaps.
Functions Remove Markers deletes all markers from the active worksheet.
9.8 Data Exchange

OpenTrack offers interfaces to general data formats (such as ASCII and XML) and to some
railway-specific formats (including railML, Treno, trafIT, Simu VII and others).
The following functions are used to transfer data.
9.8.1 Export Active Database

The command Functions  Export all Databases exports the 6 active databases (see Info 
Preferences) into a user-specified directory.
9.8.2 Exchange Rolling Stock Data

Functions  Exchange Rolling Stock Data  Import Data or Export Data can be used to
import or export rolling stock data to/from OpenTrack.
OpenTrack Databases
Functions:
Functions  Exchange Rolling Stock Data  Export Engines (OpenTrack Database)
Functions  Exchange Rolling Stock Data  Import Engines (OpenTrack Database)
Similar to other databases, the locomotive database (Engines, *.depot) can be exported or indi-
vidual locomotives can be imported from an existing database.
railML
Functions:
Functions  Exchange Rolling Stock Data  Export Rolling Stock (railML-Format)
Functions  Exchange Rolling Stock Data Import Rolling Stock (railML-Format)
Open Track supports railML version 2.2 for the import and export of rolling stock data.

9.8.3 Exchange Timetable Data

Functions  Exchange Timetable-Data  Export Timetable can be used to export OpenTrack
timetable data in various formats (see table).
Functions  Exchange Timetable-Data  Import Timetable can be used to import various

forms (see table) of timetable data to OpenTrack.
It is possible to import/export timetable data in the following data formats:
Format Type Description

XML OpenTrack’s proprietary XML-Format
railML A general XML format used for the exchange of railway data
(see also: http://www.railml.org)
OpenTrack Database OpenTrack’s proprietary database format (*.timetable)
OpenTrack Format OpenTrack’s proprietary ASCII-Format (Tab-separated)
Text Format General ASCII format (Tab separated)
trafIT Format Export data for the applications of trafIT
TRENO Format Export data for the application TRENO
SIMU VII Format Timetable data from the application SIMU VII
Protim Format Timetable data in Protim-Format (UK)
Also under this menu item are exchange functions for courses, distribution functions, and inci-
dents data.
railML
Functions:
Functions  Exchange Timetable Data  Export Timetable (railML-Format)
Functions  Exchange Timetable Data Import Timetable (railML-Format)
Open Track supports railML versions 1.0 and 2.2 for the import and export of timetable data.
Import and Export of Timetable Data

Function:
Functions  Exchange Timetable Data  Export Timetable (OpenTrack-Format)
Functions  Exchange Timetable Data  Import Timetable (OpenTrack-Format)
This function can be used to import an ASCII text file of timetable data into OpenTrack.
The first block of data following the optional comment lines (comment lines begin with //)
must be formatted with the following values (tab-separated):

• courseID (courseID of train)

• intervalCourseID (courseID of the original interval train family; 0, if train is not part of
interval train family or if it is the first train in the interval train family)
• timeToIntervalReference (time difference from original train in interval train family; 0, if
train is not part of interval train family or if it is the first train in the interval train family)
• stationIndex (stationsindex; continually increasing index, beginning with 0, for the current
train)
• stationSign (station ID or station abbreviation for current timetable entry)
• trackName (optional track name / platform)
• arrTimeDayOffset (day offset for the arrival time; 0 is the default value and stands for the
first day of the simulation)
• arrTime (arrival time in format HH:MM:SS)
• depTimeDayOffset (day offset for the departure time; 0 is the default value and stands for
the first day of the simulation)
• depTime (departure time in format HH:MM:SS)
• useDepTime (time comparison station; 1, when station is a time comparison station, other-
wise 0, default value is 1)
• dwell (minimum dwell time in seconds)
• stopAtStation (1, when station stop is planned, otherwise 0)
• meanDelay (mean delay in seconds)
• Distribution (delay distribution; name of a defined delay distribution, default is "")
• deltaMass (change of mass in tons)
Any number of comment lines is allowed between the first and second blocks of data. One of
these comment lines must have the following form:
// Connections:
The second block of data (connection definitions) must provide the following values (tab-
separated):
• courseID (courseID of the train that waits for the connecting train)
• connCourseID (courseID of the connecting train, i.e., the train for which the waiting train
is waiting)
• station index (index of the station where the connection takes place  this index corre-
sponds with the data in the schedule table defined above)
• connStationSign (StationID the station at which the connecting train must wait to enable
the connection to take place, default: the same station where the courseID train is waiting)
• connTimeType (type of time comparison, 0 if the comparison is made with the arrival or
passing
• time of the connecting course, 1 if the comparison is made with the departure time)
• connChangeTime (defined connection time in HH:MM:SS)
• connMaxChangeTime (maximum connection time in HH:MM:SS)
• connection type (connection type)

Calculation of connection type:
Initial value: Connection Type = 0

Join: Connection Type = Connection Type + 1
Split: Connection Type = Connection Type + 2
Connection at exit signal: Connection Type = Connection Type + 0
Connection at home signal: Connection Type = Connection Type + 16
9.8.4 Exchange Infrastructure Data

Functions  Exchange Infrastructure Data  Export... can be used to produce ASCII files,
into which the itinerary information of all currently open documents is placed. The user can
select different combinations of routes, paths and itinerary descriptions.
The exchange functions support several standardized topology and infrastructure data
interchange formats, as well as data exchange formats for specific railway IT applications.
Functions  Exchange Infrastructure Data  Export Document Description can be used to

produce an ASCII file with the description of all objects contained in the selected document.
Functions  Exchange Infrastructure Data  Import Infrastructure Data  ... can be used to
import general or application-specific infrastructure data. Several of these data exchange for-
mats have been developed by OpenTrack especially for specific applications (when the appli-
cation's data format is not public).
Functions  Exchange Infrastructure Data  Import Itinerary Info ... can be used to import
itinerary data from an OpenTrack database of the type ( *.dest) into the current itinerary data
base.
railML
Functions:
Functions  Exchange Infrastructure Data  Export Infrastructure Data (railML-Format)
Functions  Exchange Infrastructure Data  Import Infrastructure Data (railML-Format)
Open Track supports railML versions 1.0 and 2.2 for the import and export of infrastructure
data.
Importing infrastructure data from the format IVT

Function:
Functions  Exchange Infrastructure Data  Import Infrastructure Data (IVT-Format)
The infrastructure data must be in the form of ASCII-text data (tab separated) with the follo-
wing format:
• Position [m]
• Name of node (vertex) in ascending direction (optional)

• Name of node (vertex) in descending direction (optional)

• Location (Kilometre-post) of node (vertex) in ascending direction (optional)
• Location (Kilometre-post) of node (vertex) in descending direction (optional)
• Speed limit (speed 1) in ascending direction [km/h]
• Speed limit (speed 1) in descending direction [km/h]
• Gradient [‰]
• Curve radius (0 for straight track) [m]
• Tunnel type (optional) [string, using words from OpenTrack-Inspector (e.g. Tunnel single,
smooth) and/or the value of the tunnel factor (e.g. 2.7); no data indicates that the track seg-
ment is type: No Tunnel]
• Signal type in ascending direction (optional) [string, using words from OpenTrack Signal
Inspector (e.g. Main/Distant Signal); no data indicates that this node has no signal]
• Signal type in descending direction (optional) - see above.
• Station name (optional) [String, the same used in the OpenTrack-Stationstool (e.g. Basel
SBB)]
Data Import from Bentley Rail Track

Functions:
Functions  Exchange Infrastrastructure Data  Convert Bentley Rail Track Vertical-Data
to IVT Format
Functions  Exchange Infrastrastructure Data  Convert Bentley Rail Track Horizontal-
Data to IVT Format
These commands can be used to convert files that have been exported in tab-delimited ASCII
text format from Bentley Rail Track (Vertical Integrity Report and Horizontal Integrity
Report) into OpenTrack’s IVT format so that the resulting files can be imported into Open
Track.
Vertical Integrity Report:

• Column 1: String “Linear”.
• Column 3: Position in kilometres (three decimal places).
• Column 5: Gradient in per thousands.
Horizontal Integrity Report:
• Column 1: String: “Linear” for straight track, “Circular” for curves.

• Column 3: Position in kilometres (three decimal places).
• Column 12: For straight track: empty cell; for curved track: curve radius in meters.

9.8.5 Exchange Station Data

Functions  Exchange Station Data  Export Stations can be used to export the OpenTrack
station database into a tab-separated ASCII file, XML-file or to Google Earth (.kml format).
Functions  Exchange Station-Data  Import Stations can be used to import station data
from an ASCII file or XML-file.
railML
Functions:
Functions  Exchange Station Data  Export Station Data (railML-Format)
Functions  Exchange Station Data Import Station Data (railML-Format)
Open Track supports railML versions 1.0 (export only) and 2.2 for the import and export of
infrastructure data.
When exporting data, a railML infrastructure file is created containing all stations (in railML:
element ocp) from the station database.
When importing data, the railML infrastructure file is read from which all stations are
extracted (in railML: element ocp) and inserted into the station database in OpenTrack.
9.9 Menus Hide and Quit

Hide deactivates OpenTrack including all its windows and panels. A mouse-click on the appli-
cation icon in the task bar reactivates the application.
Quit terminates the application.
When the user quits OpenTrack, the program makes a note of all open documents and allows
the user to re-open these documents the next time the program is started (Document  Open
recent Documents ... ).

9.10 Checklist for OpenTrack Projects
Project Preparation
• Collect all the infrastructure, rolling stock and timetable data
Project Tasks
• Plan the track layout (candidates for vertex locations are grade changes, changes in curva-
ture, speed changes, signal locations and switches)
• Create or edit station database (Tools Stations)
• Create the track infrastructure (double vertex graph of the infrastructure)
- Define vertices and edges
- Define station vertices (at the center of every station, one station vertex per track /
platform)
- Create main and distant signals
- Create stations (station icons), connect them to an entry of the station database
- Define station areas and stopping positions within station areas
- Name vertices (vertex name) and signals (signal name) with self-explaining names
(e.g. track names, signal numbers, ... )
• Definition of routes (Tools  Routes) including the definition of all technical data of the
routes
• Definition of paths (Tools  Paths)
• Definition of itineraries (Tools  Itineraries)
• Check the correctness of the infrastructure (show labels, export infrastructure to export
files, ...)
• Add the needed engines to your depot (locomotive database) (Tools  Engines)
• Create train sets (Tools  Trains)
• Create courses/services (Tools  Courses)
• Add timetable data to courses (Tools  Courses, press "New" next to "Timetable: First
Departure" and Tools  Timetable)
• Create train graphs (Tools  Train Diagram)
• Define outputs (Tools  Simulation  Output)
• Run single simulation runs (Tools  Simulation)
• Define simulation scenarios (incl. delays, failures and incidents) (Tools  Timetable,
Tools  Incidents)
• Optional: run multiple simulation runs (Tools  Simulation)
• Create outputs, analyze results
Postprocessing
• Project documentation
• Backup of the project data and the results


Final Remark 189
10. Final Remark
OpenTrack was developed between 1995 and 2000 as a research project by Dr. Daniel Huerli-
mann at Swiss Federal Institute of Technology Institute for Transport Planning and Systems
(ETH IVT) under the supervision Professor Heinrich Braendli [Hue 01].
Three students from the ETH Zurich computer science department made fundamental contri-
butions to OpenTrack as part of their diploma thesis and end-of-term projects. Markus Ullius,
integrated the finder tool and the measuring instrument objects into OpenTrack (as an end-of-
term project) and integrated the tools for the representation of train graphs into OpenTrack as
his diploma thesis. Thomas Burri and Markus Fretz developed the Depot application for the
representation of locomotive data as their end-of-term project.
Version 1.0 of OpenTrack was released in 2000 once basic conditions of functionality were
reached. This version was used by railway companies, consulting firms, and research units to
simulate and analyze the processes of railway business operations with a good degree of
accuracy.
Over the past years, OpenTrack has been continuously improved based on comments from
users. The program has increased its functionality to become a comprehensive tool for the
simulation of railway and Maglev train systems.
The latest version of OpenTrack has been extended to enable users to model streetcar and
metro rail systems.
In 2006, the company OpenTrack Railway Technology GmbH was founded as an ETH spin-
off firm, which, among other projects, will focus on the development and marketing of the
OpenTrack application.
Naturally, development of OpenTrack is not ended with the current version. Together with our
research partners we will continue to improve OpenTrack by adding functions, improving
evaluation processes, and increasing input/output possibilities. We are committed to suppor-
ting and improving OpenTrack in a meaningful way in the coming years.
Zurich, in June 2017
Daniel Huerlimann
Manual translated from German to English by Andrew Nash, 2017

190 Final Remark

Literature 191
11. Literature
[Arm 94] J. Armstrong. The Railroad: What It Is, What It Does. 3rd edition, Simmons
Boardman Pub Co, 1994, ISBN 978-0911382044
[Bai 95] C. Bailey (ed.). European Railway Signalling. Institution of Railway Signal
Engineers and A&C Black, London, 1995.
[Bru 88] P. Brunner. MacTrac 0.1 - Interaktives Programm für Zuglaufrechnungen. IVT
publication series No. 69, IVT ETH Zurich, 1988.
[Brü 95] O. Brünger. Konzeption einer Rechnerunterstützung für die Feinkonstruktion

von Eisenbahnfahrplänen. Dissertation at the Traffic Scientific Institute of the
Technical University of Aachen, 1995.
[Fil 91] Z. Filipovic. Elektrische Bahnen. Grundlagen, Triebfahrzeuge, Stromversor-

gung. Springer Verlag, 1991.
[FN 98] W. Fenner, P. Naumann. Verkehrssicherungstechnik - Steuern, Sichern und

Überwachen von Fahrwegen und Fahrgeschwindigkeiten im Schienenverkehr.
Siemens AG, Berlin und München, 1998.
[Gan 92] W. Gander. Computermathematik. Birkhäuser Verlag, Basel, 1992.
[Geo 89] W. George. Transporttechnologie Eisenbahn: Volume 2. Transpress, VEB Ver-

lag für Verkehrswesen , Berlin 1989.
[Gig 94] P. Giger. Simulation von Eisenbahnsystemen mit RWS-1. ETH Zurich, Institute
of Transportation, Traffic, Highway and Railway Engineering (IVT), 1994.
[Hau 00] D. Hauptmann. Automatische und diskriminierungsfreie Ermittlung von Fahr-

plantrassen in beliebig grossen Netzen spurgeführter Systeme. Dissertation am
Institut für Verkehrswesen, Eisenbahnbau und -betrieb der Universität Hanno-
ver. Hestra-Verlag, Darmstadt, 2000.
[Hue 01] D. Hürlimann. Objektorientierte Modellierung von Infrastrukturelementen und

Betriebsvorgängen im Eisenbahnwesen. Dissertation am Institut für Verkehr-
splanung und Transporttechnik (IVT) der ETH Zürich, 2001.
[Kla 94] V. Klahn. Simulation grosser Eisenbahnnetze. Dissertation at the Institute for
Traffic, Railway Construction and Operation of the University of Hannover,
1994.
[Kuh 96] C. Kuhn. Rechnergestützte Vergabe von Fahrplantrassen bei Eisenbahnen.

Dissertation am Inst. für Verkehrswesen, Eisenbahnbau und -betrieb der Uni-
versität Hannover, 1996.

192 Literature
[Lüb 08] D. Lübke, Siegmann. Handbuch - Das System Bahn. Eurailpress 2008, ISBN
978-3-7771-0374-7
[Mon 92a] M. Montigel. Representation of Track Topologies with Double Vertex Graphs.
In T.K.S. Murthy, F.E. Young, S. Lehman, W.R. Smith, editor, Computers in
Railway, volume 2, Washington D.C., 1992. Computational Mechanics Publi-
cations.
[Mon 92b] M. Montigel. Elemente eines computergestützten Werkzeugs zur Entwicklung

von Eisenbahnsicherungsanlagen mit Petri-Netzen. Schriftenreihe des IVT Nr.
92, ETH Zürich, IVT, 1992.
[Mon 94] M. Montigel. Modellierung und Gewährleistung von Abhängigkeiten in Eisen-

bahnsicherungsanlagen. IVT publication series No. 102, ETH Zurich, IVT,
1994.
[Pac 09] J. Pachl. Railway Operation and Control. 2nd edition, VTD Rail Publishing
(USA) 2009, ISBN 978-0-9719915-8-3
[Pac 13] J. Pachl. Systemtechnik des Schienenverkehrs Bahnbetrieb planen, steuern und
sichern. 7. Auflage, Verlag Springer Vieweg 2013, ISBN 978-3-8348-2586-5
[Pot 70] G. Potthoff. Verkehrsströmungslehre. Band 1. Die Zugfolge auf Strecken und in
Bahnhöfen. Transpress Verlag, Berlin, 1970.
[The 09] G. Theeg, S. Vlasenko. Railway Signalling & Interlocking. International Com-
pendium 1st edition, Eurailpress, 2009, ISBN 978-3-7771-0394-5
[Wei 91] U. Weidmann. Fahrdynamik und Fahrzeitermittlung. Chapter I2 from the

lecture notes „Bases of Public Transport". IVT, ETH Zurich, 1991.
[Wen 03] D. Wende. Fahrdynamik. Teubner, Stuttgart, 2003.
[Win 09] P. Winter, UIC. Compendium on ERTMS European Rail Traffic Management
System. 1st edition, Eurailpress, 2009, ISBN 978-3-7771-0369-9
[Vuc 05] R. Vuchic, R. Vukan. Urban Transit Operations, Planning and Economics. 1st
edition, John Wiley & Sons, 2005, ISBN 978-0-471-63265-8
[Vuc 07] R. Vuchic, R. Vukan. Urban Transit Systems and Technology. 1st edition, John
Wiley & Sons, 2007, ISBN 978-0-471-75823-5

Summary of Menu Operations 193
12. Summary of Menu Operations
Info Info Panel .................................................................................................168

Info Preferences ...............................................................................................127
Info Registration ..............................................................................................169
Info Release Notes ...........................................................................................169
Info Manual .....................................................................................................170
Document Document Sets................................................................................167

Document Open ...............................................................................................165
Document Open Recent Documents ................................................................165
Document Open Special Open without Images...........................................165
Document Open Special Open Property List (plist)....................................165
Document Open Special Open all Documents in Directory........................165
Document New.................................................................................................165
Document Save ................................................................................................165
Document Save As ..........................................................................................165
Document Save To ..........................................................................................165
Document Save Special Save as Property List (plist) .................................166
Document Save Special Save all Documents .............................................166
Document Rename...........................................................................................166
Document Refresh............................................................................................166
Document Revert to Saved...............................................................................166
Document Close...............................................................................................167
Edit Undo.........................................................................................................170
Edit Cut..............................................................................................................49
Edit Copy ...........................................................................................................49
Edit Paste...........................................................................................................49
Edit Select All ....................................................................................................48
Edit Subselect Edges........................................................................................170
Edit Subselect Vertices.....................................................................................170
Edit Subselect Switches ...................................................................................170
Edit Subselect Signals (Main-, Distant-, Shunting Signals, Balises)...............171
Edit Subselect Routes.......................................................................................170
Edit Subselect Shuntings/Overlaps..................................................................171
Edit Subselect Stations.....................................................................................171
Edit Subselect Instruments...............................................................................171
Edit Subselect Graphics...................................................................................171
Edit Subselect Images......................................................................................171
Edit Subselect Labels.......................................................................................171
Edit Subselect temp. Labels .............................................................................171
Edit Select Edges with same... ........................................................................171
Edit Select Edges/Vertices with same... ..........................................................171
Edit Place Image .............................................................................................172
Edit Remove Images ........................................................................................172

194 Summary of Menu Operations
Edit Remove PDF-Images ...............................................................................172
Format Font.......................................................................................................45
Format Text........................................................................................................45
Format Grid.......................................................................................................48
Format Zoom In / Zoom Out............................................................................172
Format Show Edgedirection ..............................................................................17
Format Hide Edgedirection...............................................................................17
Format Show Small Vertices..............................................................................13
Format Show Big Vertices .................................................................................13
Format Page Layout........................................................................................173
Format Document Setup..................................................................................172

Summary of Menu Operations 195
Tools Colors.....................................................................................................173
Tools Toolbox / Palette ....................................................................................173
Tools Messages ................................................................................................149
Tools Finder.....................................................................................................174
Tools Calculator ..............................................................................................174
Tools Inspector...................................................13, 18, 25, 37, 39, 41, 44, 46, 47
Tools Routes.......................................................................................................54
Tools Paths.........................................................................................................60
Tools Itineraries.................................................................................................62
Tools Stations.....................................................................................................34
Tools Engines.....................................................................................................71
Tools Trains .......................................................................................................67
Tools Train Categories ......................................................................................87
Tools Courses/Services ......................................................................................95
Tools Distributions.............................................................................................93
Tools Incidents .................................................................................................134
Tools Timetable................................................................................................100
Tools Train Diagram........................................................................................142
Tools Headway Calculator ..............................................................................154
Tools Simulation ..............................................................................................113
Functions Group Station Area.....................................................................174

Functions Group Power Supply Area.........................................................175
Functions Ungroup Station Area................................................................175
Functions Ungroup Power Supply Area.....................................................175
Functions Routes Search all Routes ...........................................................176
Functions Routes Search/Fetch all Routes .................................................176
Functions Routes Add all Signal Aspects to Routes ...................................176
Functions Routes Add all Overlaps to Routes ............................................176
Functions Routes Place Insulated Joints for Route Release Groups ........176
Functions Routes Place Axle Counters for Route Release Groups ............176
Functions Routes Adjust Route Release Groups based on ... .....................176
Functions Routes Delete all Routes ...........................................................176
Functions Paths Search all Paths (Exit Signal to Home Signal) ...............176
Functions Paths Search all Paths (Home Signal to Exit Signal) ...............176
Functions Paths Search all Paths (Exit Signal to Exit Signal) ..................176
Functions Paths Search all Paths (for Treno) ............................................176
Functions Paths Delete all Paths ...............................................................177
Functions Connect selected Vertices ..............................................................177
Functions Expand Vertices .............................................................................177
Functions Compress Vertices ..........................................................................177
Functions Cut Double Vertex ........................................................................ 177
Functions Merge Elements ............................................................................ 178
Functions Reset Elements .............................................................................. 178
Functions Calcualte Kilometre Points ............................................................177
Functions Change Kilometre Points ...............................................................177
Functions Set Switch Default Positions ..........................................................178

196 Summary of Menu Operations
Functions Create Instruments at Switch Locations .........................................178

Functions Create Instruments at Main Signal Locations ................................178
Functions Labels Create all ID Labels ......................................................178
Functions Labels Create Vertex ID Labels .................................................178
Functions Labels Create Vertex Name Labels ............................................179
Functions Labels Create Vertex Kilometre Point Labels ...........................179
Functions Labels Create Edge ID Labels ..................................................179
Functions Labels Create Edge Element Labels ..........................................179
Functions Labels Create Edge Length Labels ...........................................179
Functions Labels Create Edge Gradient Labels ........................................179
Functions Labels Create Edge Speed Labels .............................................179
Functions Labels Create Edge Line/Track Name Labels ...........................180
Functions Labels Create Station Labels ....................................................180
Functions Labels Remove temp. Labels .....................................................180
Functions Markers  Mark... .........................................................................180
Functions Markers Remove Markers .........................................................180
Functions Exchange Rolling Stock Data Export Rolling Stock Data .........181
Functions Exchange Rolling Stock Data Import Rolling Stock Data .........181
Functions Exchange Timetable Data Export Timetable Data.....................182
Functions Exchange Timetable Data Import Timetable Data.....................182
Functions Exchange Infrastructure Data Export Infrastructure Data........184
Functions Exchange Infrastructure Data Import Infrastructure Data........184
Functions Exchange Station Data Export Stations ....................................186
Functions Exchange Station Data Import Stations ....................................186
Functions Dispatching Rules Import Dispatching Rules ............................158
Functions Dispatching Rules Import Recent Dispatching Rules ...............158
Functions Dispatching Rules Produce Dispatching Rules File .................158
Functions Dispatching Rules Delete all Dispatching Rules .....................158
Print .....................................................................................................................168
Hide......................................................................................................................186
Quit ......................................................................................................................186

Index
Index
A
Acceleration Resistance ................................................................................................... 83
Application ......................................................................................................................... 9
Approach Zone ................................................................................................................ 57
Area ................................................................................................................................ 145
B
Balise ............................................................................................................................... 29
Beacon ............................................................................................................................. 29
Block ................................................................................................................................ 56
Braking Behaviour ......................................................................................................... 115
Braking Percent ................................................................................................................ 83
C
Calculator ....................................................................................................................... 174
CBTC ........................................................................................................................ 98, 99
Checklist for OpenTrack Projects .................................................................................. 187
Colors ............................................................................................................................. 168
Connect selected Vertices .............................................................................................. 177
Connection .............................................................................................................. 22, 106
Connector ......................................................................................................................... 22
Context Menu .................................................................................................................. 49
Copy ................................................................................................................................. 49
Corridor .......................................................................................................................... 142
Course .............................................................................................................................. 95
Course Management ........................................................................................................ 95
Course Sets ...................................................................................................................... 98
Curve Resistance .............................................................................................................. 80
D
Data ............................................................................................................................... 3, 7
Data Exchange ............................................................................................................... 181
Database ............................................................................................................................. 7
Day Offset ...................................................................................................................... 101
Delete ............................................................................................................................... 49
Departure Process Time ................................................................................................... 90
Discrete Block ................................................................................................................ 119
Dispatching ............................................................................................................. 91, 123
Dispatching Rules .......................................................................................................... 158
Distance Resistance ......................................................................................................... 79
Distribution ...................................................................................................................... 93

Index
Distribution Function ....................................................................................................... 94

Document .................................................................................................................. 7, 165
Double Vertex Graphs ..................................................................................................... 11
E
Edge ................................................................................................................................. 17
Engine .............................................................................................................................. 71
ETCS Level 2 ................................................................................................................... 84
Euler’s Method .............................................................................................................. 113
Evaluations ................................................................................................................ 5, 150
Exchange Station Data ................................................................................................... 186
Exclusion Link ................................................................................................................. 21
Export Network Data ..................................................................................................... 184
Export Stations ............................................................................................................... 186
Export Timetable ........................................................................................................... 182
F
Finder ............................................................................................................................. 174
G
Gradient Resistance ......................................................................................................... 79
Graphic Inspector ............................................................................................................. 44
Graphical Elements .......................................................................................................... 44
Group Station Area ........................................................................................................ 174
H
Headway Calculator ....................................................................................................... 154
I
Image Inspector ................................................................................................................ 47
Images .............................................................................................................................. 47
Import Stations ............................................................................................................... 186
Import Timetable ........................................................................................................... 182
Incident Set .................................................................................................................... 139
Incidents ......................................................................................................................... 134
Infopanel ........................................................................................................................ 168
Initial Delay ................................................................................................................... 139
Inspector for Train Diagrams ......................................................................................... 144
Interlocking .................................................................................................................... 117
Itinerary ............................................................................................................................ 62
J
Joining of Trains ............................................................................................................ 108

Index
L
Labels ............................................................................................................................. 178
Layout ............................................................................................................................ 173
Loco Management ........................................................................................................... 71
M
Measuring Instrument ...................................................................................................... 39
Measuring Instrument Inspector ...................................................................................... 39
Merge Elements ............................................................................................................. 178
Messages ............................................................................................................... 149, 174
Move ................................................................................................................................ 49
Moving Block ................................................................................................................ 121
O
Occupation ..................................................................................................................... 133
Occupied Entry .............................................................................................................. 109
Open Document ............................................................................................................. 165
Operating System ............................................................................................................... 9
Output ............................................................................................................................ 133
Overlap ............................................................................................................................. 59
P
Page Layout ................................................................................................................... 173
Palette ............................................................................................................................. 173
Paste ................................................................................................................................. 49
Path .................................................................................................................................. 60
Performance ................................................................................................................... 131
Performance Distribution ................................................................................................. 92
Picture .............................................................................................................................. 47
Plot ................................................................................................................................. 151
Plot Inspector ................................................................................................................... 41
Position in Train ............................................................................................................... 71
Power Loss Function ....................................................................................................... 74
Power Supply ................................................................................................................... 36
Preferences ..................................................................................................................... 169
Print ................................................................................................................................ 168
Propulsion Segment Group ............................................................................................ 175
Protection Systems ......................................................................................................... 117
R
Resetting Safety Elements ...................................................................................... 21, 178
Resistance ........................................................................................................................ 75
Rolling Resistance ........................................................................................................... 76
Rolling Stock ..................................................................................................................... 3

Index
Route reservation ........................................................................................................... 119

Routes .............................................................................................................................. 54
S
Safety Element ................................................................................................................. 20
Save Document .............................................................................................................. 165
Scriptmode ....................................................................................................................... 51
Search all Routes ........................................................................................................... 176
Select ................................................................................................................................ 48
Shuntings ......................................................................................................................... 58
Signal ............................................................................................................................... 23
Signal Indication .............................................................................................................. 56
Signal Types .................................................................................................................... 24
Simulation ................................................................................................................. 5, 113
Simulation Flow ................................................................................................................. 1
Slow Speed Zone ............................................................................................................. 57
Split of Trains ................................................................................................................ 108
Starting Rolling Resistance .............................................................................................. 82
Station ....................................................................................................................... 31, 34
Station Area ................................................................................................................... 174
Station Database .............................................................................................................. 34
Station Inspector .............................................................................................................. 31
Station Vertex .................................................................................................................. 16
Subselections ................................................................................................................. 170
T
Text .................................................................................................................................. 45
Text Inspector .................................................................................................................. 46
Time Format .................................................................................................................. 101
Timetable ....................................................................................................................... 100
Timetable Data ................................................................................................................... 4
Timetable Database ........................................................................................................ 100
Track Layout ...................................................................................................................... 3
Track Name ............................................................................................................. 90, 102
Track name .................................................................................................................... 102
Track Topology ................................................................................................................ 10
Traction Resistance .......................................................................................................... 76
Train ................................................................................................................................. 67
Train Categories ............................................................................................................... 87
Train Graph .................................................................................................................... 146
Train Inspector ................................................................................................................. 68
Train Management ........................................................................................................... 67
Train Resistance ............................................................................................................... 75
Tunnel Resistance ............................................................................................................ 78
Turnround ...................................................................................................................... 109

Index
U
Undo ............................................................................................................................... 170
Ungroup Station ............................................................................................................. 175
V
Vertex ............................................................................................................................... 11
Vertex Inspector ............................................................................................................... 13
W
Worksheet ........................................................................................................................ 10
Z
Zoom .............................................................................................................................. 172

OpenTrack - Manual EN.1.9 PDF

Uploaded by

Copyright:

Available Formats

OpenTrack - Manual EN.1.9 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenTrack - Manual EN.1.9 PDF

Uploaded by

Copyright:

Available Formats

Daniel Huerlimann, Andrew B.

Simulation of Railway Networks

OpenTrack Railway Technology Ltd.

2. Structure of OpenTrack ........................................................................... 3

3. OpenTrack Application ............................................................................ 9

4. Train Operations: Routes, Paths and Itineraries ..................... 53

5. Train Management (Trains) .................................................................. 67

6. Courses and Timetables........................................................................ 95

OpenTrack Simulation of Railway Networks

6.1 Course Management (Courses)................................................................ 95

7. Simulation in Open Track ................................................................... 113

8. Running an OpenTrack Simulation ............................................... 127

9. Further Tools and Settings ................................................................ 165

10. Final Remark .............................................................................................. 189

11. Literature ...................................................................................................... 191

12. Summary of Menu Operations ......................................................... 193

OpenTrack Simulation of Railway Networks

The main modules of OpenTrack are illustrated in Figure 1.

Input Simulation Output

Rolling Stock Interactivity Diagrams

(111) 221 (113)

Infrastructure (112) 222

08:00 08:30 09:00

IC 5000 OBE HH:MM:SS 08:31:00 30

IC 5000 AAT HH:MM:SS 08:38:00 60

IC 5000 WED 08:55:00 HH:MM:SS 60

Timetable Animation Statistics

Figure 1: OpenTrack Process: Input-Simulation-Output

OpenTrack Simulation of Railway Networks

OpenTrack Simulation of Railway Networks

2.1 Input Data

2.1.1 Rolling Stock: Locomotives and Wagons

2.1.2 Track Layout Data

Figure 2: Example OpenTrack Station Layout

OpenTrack Simulation of Railway Networks

2.1.3 Timetable Data

2.1.4 Train Operations

Infrastructure Related Terms

OpenTrack Simulation of Railway Networks

Timetable Oriented Movement Terms

OpenTrack Simulation of Railway Networks

08.00 .10 .20 .30 .40 .50 09.00

Figure 4: Train Graph (Space-Time Diagram)

OpenTrack Simulation of Railway Networks

IC4001 RE10001 IC4003 FR35001 IC4005 RE10003 IC4007 FR35003

RE10000 IC4000 FR35000 IC4002 RE10002 IC4004 FR35002 IC4006

08:00 08:30 09:00 09:30 10:00 Time

Figure 5: Track Occupations

2.4 Data Management in Open Track

Documents Output (ASCII-Text)

*.opentrack *.otsimcor *.vs *.as *.tt

*.depot *.trains *.courses *.timetable *.stations *.dest

Figure 6: OpenTrack Input-Output Data Management

OpenTrack Simulation of Railway Networks

OpenTrack Simulation of Railway Networks

Figure 7: OpenTrack User Interface

OpenTrack Simulation of Railway Networks

3.1 Starting OpenTrack and File Management

3.2 OpenTrack Worksheet

.opentrack .otsimcor .vs .as *.tt

.depot .trains .courses .timetable .stations .dest