PDF Download - DB Netz AG

Imprint
DB Netz AG
Theodor-Heuss-Allee 7
D-60486 Frankfurt am Main
Editor
DB Netz AG
Market and Product Planning
Mainzer Landstraße 201-203
D-60326 Frankfurt am Main
Subject to alterations.
The validity of the network access as
amended is not affected.
Individual details supplied without
liability.
as of: April 2011
www.dbnetze.com/track
Photos:
Axel Hartmann (front page, last page,
“Settlement” page 3 at the bottom); Günter
Jazbek (front page), Roland Horn (1st flap);
“Schematic overview” from left to right: Axel
Hartmann, Christian Bedeschinski, Ralf Braum,
Günter Jazbek; Ralf Braum (“Registration”:
both photos); Saarbourg (“coding”); DB AG
(flap “Influenceable causes of delay DB Netz
AG”); Thomas Rittelmann (flap “Influenceable
causes of delay railway undertaking”); Heiner
Müller-Elsner (“Monitoring” left and right);
Mario Vedder (“Monitoring” in the middle);
Joachim Donath (“Settlement” at the top);
Claus Weber (“Settlement” bottom left); Ralf
Braum (“Settlement” at the bottom in the
middle and on the right); Fotolia (“Settlement”
page 2 and 3)
The train path incentive
system by DB Netz AG:
the systematic approach to
punctuality
The basis of the future. DB Netze.

Schematic overview
Planned
time
Additional delay
From departure to settlement
The following diagram gives a clearly
structured impression and explanation
of the train path incentive system.
Berlin
Departure: 10:31 hrs
Braunschweig
11:58 hrs
15 minutes delay
Door closing device
defective
Code 62: RU
Passenger coach
The example is based on a fictitious
passenger train from Berlin to Frankfurt.
Kassel-Wilhelmshöhe
13:16 hrs
10 minutes delay
Line blocked
Code 31: DB Netz AG
Engineering work
Three delays are ascertained for this
route. Each delay is given its own code,
with a clear definition of the cause and
corresponding responsibility.
Fulda
13:47 hrs
8 minutes delay
Journey to command
Code 25: DB Netz AG
Command and control
systems
At the end of the year, the coded delay
minutes are settled between the railway
undertaking and DB Netz AG.
Frankfurt am Main
Arrival: 14:44 hrs
Delay!
Actual arrival:
15:17 hrs
Hourly record
Train number 277
Code 62 RU: 15 minutes
Code 31 DB Netz AG: 10 minutes
Code 25 DB Netz AG: 8 minutes
Settlement
The delays generated by the RU
and DB Netz AG are then settled
on the basis of a settlement model.
One delay minute corresponds to
10 Ct.
How DB Netz AG makes punctuality calculable
DB Netz AG‘s ultimate aim is to warrant
maximum punctuality for all its
train paths. Nevertheless, certain
imponderables and special situations
can mean that it is not always possible
to achieve this aim right down to
the last minute. The train path incentive
system by DB Netz AG takes a
comprehensive, precisely elaborated
systematic approach with transparent,
comprehensible ascertainment and
allocation of causes for possible hindrances.
The train path incentive system has
been developed to bring about a constant,
consistent improvement in the
quality of rail transport and acts as future-oriented
motivation for satisfying
all railway customers and railway undertakings
in the best possible manner.
Example:
Punctuality degree of 80%
The punctuality for all trains of the
railway undertakings is calculated on
a daily basis. To this end, en route
punctuality is calculated for passenger
trains. Passenger trains are still
deemed punctual with delays of up to
5:59 minutes.
The punctuality of freight trains is calculated
according to arrival at the terminus.
Freight trains are still deemed
punctual with delays of up to 30:59
minutes.
The degree of punctuality then results
from the ratio of punctual trains to the
total number of trains.
80 punctual trains
20
delayed
trains

Registration Coding
Registration: 20% selected and announced early on
For data recording, 20% of the train
paths allocated in the working timetable
are viewed, which you select
according to your own criteria and
send to us. These routes have to be
Please note:
Consideration is not given to the DC
S-Bahn networks in Hamburg and Berlin,
ad hoc traffic and journeys that
need a special form of timetable (e.g.
train control operation) because of the
registered rolling stock, track conditions
of other parameters.
registered about two months before
the working timetable begins. The
routes are then viewed and measured
throughout the whole year according
to our parameters.
Coding: Precise detection and allocation of the causes
Coding gives DB Netz AG an instrument
for precise allocation of delay
causes.
A coding key stipulates the two prime
aspects:
1. the cause of the delay, such as signal
faults or vehicle faults, and
2. the entity responsible for the delay,
such as the railway undertaking or
DB Netz AG.
Most delay causes can be clearly allocated
and are the responsibility either
of DB Netz AG or of the railway undertaking.
A corresponding catalogue of delay
causes has been drawn up to facilitate
allocation. (see example on the righthand
flap).
Coding is based on the coding list and
Code of Practice 420.9001 with the
explanations.
The coding list can be viewed on the
internet as Annex 7 to the Network
Statement (SNB): www.dbnetze.com/
networkstatement
Code Delay cause
10
Timetable design
(Sales)
12 Scheduling faults
13 Preparation (Operations)
18 DB Netz operational staff
19 DB Netz other operational issues
21 Telecommunications systems
22 Structures
23 Track
24 Level crossing safety systems
25 Command and control systems
28 DB Netz technical staff
29 DB Netz other technical issues
30
Influenceable causes
DB Netz AG
Temporary speed restriction
for repairs
31 Engineering work
32 Irregularities in engineering works

Influenceable causes of delay
RU
Code Delay cause
50 Stopping time exceeded
51 RU application
52 Loading work
53 Irregularities with the load
57 No report from RU
58 RU�s traffic staff
60 Block/deployment planning
62 Passenger coach
63 Wagon
64 Traction unit
68 RU technical staff
Monitoring
Delay monitoring: transparent and
comprehensible
The train path incentive system gives
great significance to the maximum
possible transparency, with corresponding
records kept to ensure that
the railway undertakings are always
supplied with the latest information.
This ensures that you have an overview
at all times of all trains that
have been registered in the incentive
system, in terms of delay, cause and
responsibility.
Explanations about the records can be
found on the internet:
www.dbnetze.com/incentivesystem
Correcting the delay causes: flexible and fair
The train path incentive system offers
the railway undertakings a fair, flexible
correction procedure that works
quickly without any undue complications.
Correction requests always have
to be implemented in the framework
of the hourly and daily records. When
accepted, they are then included in the
weekly records. Detailed reasons are
provided if the corrections are not ac-
cepted. (The following diagram shows
exactly how the correction procedures
work.)
The processes are stipulated in Code
of Practice 420.9001. This can be
consulted as Annex 7 in the Network
Statement: www.dbnetze.com/
networkstatement
� � � � � � � �
Delay!
Validation
In the validation phase,
additional findings regarding
the disruption
can be asserted by DB
Netz AG and the railway
undertaking for a period
of 24 hours. The coding is
also changed.
* Only for customers without data exchange licence
9 1
12
hour
6
Day of the incident:
Hourly record*
The hourly record is
sent by 2 a.m. of the
following day.
3
Hourly record
Recoding
request
The railway undertaking
can submit a recoding request
via the KUNAS database
(kunas.db.netz@
deutschebahn.com) up
to 3 days after the end
of the validation phase.
DB Netz AG then reacts
within 2 days.
1 day
Daily record
The daily record is sent
by 2 a.m. on the second
following day after the
incident day.
Mo Di Mi Do Fr Sa So
1 calendar
week
Weekly record
The weekly record is sent
by the second working
day of the following week.
It is settlement-relevant,
no correction procedures
take place.
Cumulation
1
365
52
year
Annual record
The annual record is sent
by the 4th week of the following
year.

Settlement
Evaluation: Ascertaining annual punctuality
The settlement procedure for the train
path incentive system always takes
place at the end of the year. To start
with, the annual punctuality is ascertained
for every railway undertaking.
Punctuality objective
(less 1% bandwidth)
Long-distance
traffic
If this is more than 1% of the stipulated
punctuality value, a credit note
or invoice is issued in the incentive
system.
Regional traffic Freight traffic
81.5 % 92.5 % 80.0 %
Measurement concept En route punctuality
Threshold quota for
punctuality measurement
Punctuality objectives
Share of registered trains 20 %
Terminus
punctuality
5:59 minutes 30:59 minutes
Settlement: Balancing the accounts
The delay minutes of unpunctual trains
are collected throughout the whole
year and allocated to the railway undertaking
or to DB Netz AG.
The settlement procedure is then
based on the delay minutes collected
Example 1: Credit note for the railway undertaking
on those days where the punctuality
objective was missed. The delay minutes
collected in each case are added
or balanced accordingly. Every delay
minute is charged at 10 Ct.
Account total for DB Netz AG: 280,000 delay minutes
Account total for railway undertaking: − 250,000 delay minutes
Difference: + 30,000 delay minutes x 10 Ct.
The railway undertaking receives a credit note for €3,000.
Example 2: Invoice for the railway undertaking
Account total for DB Netz AG: 490,000 delay minutes
Account total for railway undertaking: − 530,000 delay minutes
Difference: − 40,000 delay minutes x 10 Ct.
The railway undertaking receives an invoice for €4,000.
Example 3: Balanced accounts
Account total for DB Netz AG: 300,000 delay minutes
Account total for railway undertaking: − 300,000 delay minutes
Difference: 0 delay minutes
The railway undertaking merely receives notification that the accounts balance each other out.

Settlement Contacts and other sources of information
Example:
Ceiling: Keeping the costs manageable
To keep possible payments within a
manageable framework for both the
railway undertakings and DB Netz
AG, an upper ceiling has been implemented
for calculation of the delay
Million delay
minutes
10 million minutes
(maximum limit for
delay minutes)
13
10
5
0
Total delay
minutes. The ceiling has been set at
10 million minutes. If this value is exceeded,
the so-called ceiling factor is
ascertained.
13 million minutes
(total delay of the : =
trains)
Maximum limit
10/13 = 0.77
(ceiling factor)
All settlement
variables are
multiplied by 0.77.
Ceiling
Central headquarters
Customer Management
Passenger traffic
Ralph Grassel
Phone: +49 (0) 69 265-30530
Fax: +49 (0) 69 265-30505
ralph.grassel@deutschebahn.com
Freight traffic
Monika Roth
Phone: +49 (0) 69 265-30540
Fax: +49 (0) 69 265-30505
monika.roth@deutschebahn.com
E-mail address for submitting
recoding requests:
Kunas.db.netz@deutschebahn.com
Regional Unit North
Operations Centre
Torsten Scheer
Phone: +49 (0) 511 286-49847
Customer Management
Jürgen Motzkau
Phone: +49 (0) 511 286-49112
Fax: +49 (0) 511 286-49110
juergen.motzkau@deutschebahn.com
Regional Unit East
Operations Centre
Jürgen Wolter
Phone: +49 (0) 30 297-41909
Customer Management
Bernhard Buchhagen
Phone: +49 (0) 30 297-40150
Fax: +49 (0) 30 297-40197
bernhard.buchhagen@deutschebahn.com
For more information on the incentive
system: www.dbnetze.com/incentivesystem
Regional Unit South East
Operations Centre
Gudrun Czeyka
Phone: +49 (0) 341 968-6522
Customer Management
Thomas Kleinsteuber
Phone: +49 (0) 341 968-7007
Fax: +49 (0) 341 968-7609
thomas.kleinsteuber@deutschebahn.com
Regional Unit South
Operations Centre
Peggy Hanke
Phone: +49 (0) 89 1308-71010
Customer Management
Dirk Rothe
Phone: +49 (0) 89 1308- 72110
Fax: +49 (0) 89 1308-72102
dirk.rothe@deutschebahn.com
Regional Unit South West
Operations Centre
Katharina Raab
Phone: +49 (0) 721 938-7764
Customer Management
Rüdiger Scherer
Phone: +49 (0) 721 938-7110
Fax: +49 (0) 721 938-7119
ruediger.scherer@deutschebahn.com
The Network Statement: www.
dbnetze.com/networkstatement
Regional Unit Central
Operations Centre
Heiko Schlufter
Phone: +49 (0)69 265-19818
Customer Management
Harald Hartmann
Phone: +49 (0) 69 265-19171
Fax: +49 (0) 69 265-19045
harald.hartmann@deutschebahn.com
Regional Unit West
Operations Centre
Joachim Reinhard Pautz
Phone: +49 (0) 203 3017-1501
Customer Management
Frank Rossi
Phone: +49 (0) 203 3017-4101
Fax: +49 (0) 203 3017-4110
frank.rossi@deutschebahn.com
All contacts for regional customer
management can also be found on the
internet at www.dbnetze.com/contact.
The coding list can be viewed on the
internet as Annex 7 to the Network
Statement: www.dbnetze.com/
networkstatement